Hdinsight

878
Total Pages
777
Linux-Friendly Pages
101
Pages with Bias
11.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

200 issues found
Showing 151-175 of 200 flagged pages
Hdinsight Quickstart: Query Apache HBase in Azure HDInsight - HBase Shell ...ticles/hdinsight/hbase/query-hbase-with-hbase-shell.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by referencing PowerShell and browser methods for cluster deletion before mentioning Azure CLI, and by using Windows-style SSH command formatting. However, the main workflow (using SSH and HBase Shell) is platform-neutral and suitable for Linux/macOS users.
Recommendations
  • Explicitly mention Linux/macOS methods for cluster deletion, such as Azure CLI or Bash commands, and provide example commands.
  • When referencing SSH, clarify that the command works on Linux/macOS terminals as well as Windows (with WSL or an SSH client).
  • Avoid listing Windows/PowerShell/browser methods before Linux equivalents; present cross-platform options together or in parallel.
  • Add a note or section on using HBase Shell from Linux/macOS, including any prerequisites or differences.
GitHub Create Pull Request
Hdinsight Customize Azure HDInsight clusters by using script actions .../hdinsight/hdinsight-hadoop-customize-cluster-linux.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides examples and instructions for both Azure PowerShell and Azure CLI, but PowerShell (a Windows-centric tool) is consistently presented before CLI. PowerShell examples are more detailed and include output samples, while CLI instructions are less emphasized and sometimes lack equivalent detail. The .NET SDK (Windows-preferred) is also highlighted. There are no Linux-specific shell examples (e.g., Bash scripts run locally), and the documentation does not mention Linux-native tools for managing script actions outside of Azure CLI. The overall pattern prioritizes Windows tools and workflows, creating mild friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform.
  • Ensure CLI examples are as detailed as PowerShell ones, including sample outputs and advanced usage.
  • Add explicit Bash shell examples for managing script actions (e.g., using curl with REST API), especially for Linux users.
  • Clarify that PowerShell is available cross-platform, but highlight CLI and Bash as native options for Linux/macOS.
  • Mention Linux-native editors/tools for script development and management.
GitHub Create Pull Request
Hdinsight Plan a virtual network for Azure HDInsight ...hdinsight/hdinsight-plan-virtual-network-deployment.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for network resource inspection and management, but PowerShell commands are consistently listed before CLI commands. There is a noticeable pattern of presenting Windows-centric tooling (PowerShell) first, which may subtly signal a preference for Windows environments. However, Linux-compatible Azure CLI examples are present for all critical operations, and the HDInsight cluster creation examples explicitly reference Linux clusters. No Windows-only tools or missing Linux examples are found.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first to better serve Linux/macOS users.
  • Explicitly state that both PowerShell and CLI are supported on Windows, Linux, and macOS, and provide links to installation guides for each platform.
  • Where possible, include Bash script examples for common tasks to further improve parity.
  • Add a short section clarifying that all operations can be performed from Linux/macOS using Azure CLI.
GitHub Create Pull Request
Hdinsight Quickstart: Create Interactive Query cluster using Bicep - Azure HDInsight ...ticles/hdinsight/interactive-query/quickstart-bicep.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and managing resources, but PowerShell examples are consistently presented alongside CLI examples, sometimes immediately after. While Azure CLI is cross-platform, PowerShell is primarily associated with Windows, and no Linux/macOS-specific shell examples (e.g., Bash scripts) or explicit Linux guidance are provided. The documentation does not mention Linux-specific considerations or tools, and the ordering sometimes places PowerShell examples before or at parity with CLI examples, which may subtly reinforce a Windows-centric workflow.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
  • Consider showing CLI examples first, as they are cross-platform, and clarify PowerShell is Windows-centric.
  • Add notes or sections for Linux/macOS users, such as how to install Azure CLI on those platforms.
  • If relevant, provide Bash script examples or mention use in native Linux shells.
  • Clarify that all steps can be performed on Linux/macOS using Azure CLI, and highlight any differences if they exist.
GitHub Create Pull Request
Hdinsight How to get the host names of Azure HDInsight cluster nodes ...re-docs/blob/main/articles/hdinsight/find-host-name.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash (Linux/macOS) and PowerShell (Windows) examples for retrieving host names via the Ambari REST API. However, the PowerShell example is given immediately after the Bash example, and Windows-specific tools (ConvertFrom-Json, Invoke-WebRequest) are mentioned alongside Linux tools (jq). There is a slight ordering bias, but both platforms are covered. No critical sections are Windows-only, and Linux users can complete all tasks.
Recommendations
  • Explicitly state that both Bash and PowerShell examples are provided for cross-platform usage.
  • Consider listing the Bash (Linux/macOS) example first to avoid perceived Windows-first bias.
  • Add a note clarifying that 'jq' is available on Linux/macOS and can be installed on Windows as well.
  • Provide installation instructions or links for 'jq' for all platforms.
  • Ensure parity in explanation and troubleshooting for both Bash and PowerShell approaches.
GitHub Create Pull Request
Hdinsight Storage: Migrate on-premises Apache Hadoop to Azure HDInsight ...he-hadoop-on-premises-migration-best-practices-storage.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Minor Windows Path Reference
Summary
The documentation page is largely platform-neutral, focusing on Hadoop and Azure-specific concepts. However, there are minor signs of Windows bias: Windows-style environment variable (%HADOOP_HOME%) and path notation are used when describing where configuration files are stored, and references to tools like Azure PowerShell are included in lists of data copy methods before Linux-native alternatives. No PowerShell-specific examples or Windows-only instructions are present; most command-line examples use bash and Java tools, which are cross-platform.
Recommendations
  • Replace Windows-style environment variable and path notation (e.g., %HADOOP_HOME%) with platform-neutral or Linux-style equivalents, or mention both styles.
  • When listing tools (e.g., for copying data), ensure Linux-native options (DistCp, ADLCopy) are mentioned before or alongside Windows tools like Azure PowerShell.
  • Explicitly state that all command-line examples (openssl, keytool, hadoop credential) work on both Linux and Windows, or provide platform-specific notes if there are differences.
  • Add a brief section clarifying that HDInsight and Hadoop are cross-platform and can be managed from Linux, macOS, and Windows environments.
GitHub Create Pull Request
Hdinsight HBase cluster replication in virtual networks - Azure HDInsight ...n/articles/hdinsight/hbase/apache-hbase-replication.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation provides a brief note on how Windows users can obtain the SSH utility, listing several Windows-specific options before mentioning that Linux/macOS already include SSH. This section gives Windows-specific guidance and tools (Azure Cloud Shell, Bash on Ubuntu on Windows, Git for Windows, OpenSSH for Windows) before mentioning Linux/macOS. However, the main technical instructions, examples, and scripts are all Bash/Linux-oriented, and the overall workflow is designed for Linux environments (Ubuntu VMs, Bash scripts, Bind DNS setup).
Recommendations
  • Move the Windows SSH guidance after the statement that Linux/macOS include SSH by default, or present all platform options together for parity.
  • Explicitly mention that all examples and scripts are Bash/Linux-based and that Windows users should use WSL or a Linux VM for these steps.
  • Provide a short note at the start clarifying that the workflow is Linux-centric and recommend WSL for Windows users.
  • If possible, add a link to a guide for setting up WSL/OpenSSH on Windows for users unfamiliar with Linux tools.
GitHub Create Pull Request
Hdinsight Tutorial - Use Apache HBase in Azure HDInsight ...sight/hbase/apache-hbase-tutorial-get-started-linux.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation displays a mild Windows bias, especially in the prerequisites section, where Bash usage is described in the context of Windows 10 and Windows Subsystem for Linux (WSL) is recommended first. Windows Command Prompt and PowerShell alternatives are mentioned, with PowerShell's Invoke-RestMethod cmdlet linked. However, most command-line examples throughout the tutorial use Bash and SSH, which are native to Linux/macOS. There are no Linux-specific examples missing, but Windows tools and patterns are referenced before their Linux equivalents.
Recommendations
  • Present Linux/macOS instructions and examples before Windows-specific alternatives.
  • Clarify that Bash and SSH are native to Linux/macOS and that WSL is only needed for Windows users.
  • Provide explicit Linux/macOS command-line examples where Windows alternatives are mentioned.
  • Move references to Windows Command Prompt and PowerShell to a dedicated 'Windows users' section.
  • Ensure parity in troubleshooting and tool recommendations for Linux/macOS users.
GitHub Create Pull Request
Hdinsight Quickstart: Apache HBase & Apache Phoenix - Azure HDInsight ...les/hdinsight/hbase/apache-hbase-query-with-phoenix.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page shows a mild Windows bias by presenting command examples in Windows command prompt syntax (e.g., 'cmd' blocks for curl and ssh) and referencing deletion via PowerShell before mentioning Azure CLI. Linux/macOS equivalents (e.g., bash syntax for curl/ssh) are not explicitly shown, and the initial command examples use Windows-centric notation, which may cause minor friction for non-Windows users.
Recommendations
  • Provide both Windows (cmd/PowerShell) and Linux/macOS (bash) command examples for curl and ssh commands.
  • Explicitly mention that commands work on Linux/macOS terminals and clarify any syntax differences.
  • List Azure CLI as an equal or first-class option for cluster deletion, not after PowerShell.
  • Where possible, use platform-neutral command syntax or clarify platform-specific steps.
GitHub Create Pull Request
Hdinsight Open-source components and versions - Azure HDInsight ...n/articles/hdinsight/hdinsight-component-versioning.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is generally neutral and focused on HDInsight versions and support. However, in the 'Next steps' section, a Windows-specific guide ('Work in Apache Hadoop on HDInsight from a Windows PC') is listed, and there is no equivalent Linux/macOS guide. This subtly prioritizes Windows tooling and may suggest to users that Windows is the preferred or primary platform for client-side interaction, despite HDInsight clusters themselves running on Ubuntu.
Recommendations
  • Add equivalent guidance for working with HDInsight from Linux and macOS clients, such as connecting via SSH, using Linux-native tools, or configuring Hadoop/Spark clients.
  • Ensure that any platform-specific tooling (e.g., Windows tools) is presented alongside Linux/macOS alternatives, or at least mention their existence.
  • In 'Next steps', list Linux/macOS guides before or alongside Windows guides to avoid implicit prioritization.
  • Review linked pages (e.g., 'hdinsight-hadoop-windows-tools.md') for similar bias and provide parity in examples and instructions.
GitHub Create Pull Request
Hdinsight Create virtual networks for Azure HDInsight clusters ...articles/hdinsight/hdinsight-create-virtual-network.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for managing network security groups and DNS settings, but consistently lists PowerShell (Windows-centric) examples before CLI (cross-platform) ones. The PowerShell examples are more verbose and detailed, potentially implying a preference for Windows tooling. However, Linux-specific guidance is present in the DNS configuration sections, and CLI examples are provided for all major tasks.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to emphasize cross-platform support.
  • Explicitly state that Azure CLI works on Windows, Linux, and macOS, and encourage its use for non-Windows users.
  • Add Bash script examples for common tasks where appropriate.
  • Where PowerShell is used, clarify that it can run on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
  • Ensure parity in depth and detail between PowerShell and CLI examples.
GitHub Create Pull Request
Hdinsight Tips for using Hadoop on Linux-based HDInsight - Azure ...ticles/hdinsight/hdinsight-hadoop-linux-information.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Mention 🔧 Windows Tools Windows Examples
Summary
The documentation is primarily focused on Linux-based HDInsight clusters and uses Linux-native tools and examples (curl, jq, bash, SSH). However, there are minor mentions of Windows-specific tools and patterns, such as PowerShell and Data Lake Tools for Visual Studio, and some links to Windows-oriented SDKs and utilities. These are presented as options rather than defaults, and Linux alternatives are generally provided first or exclusively.
Recommendations
  • Ensure that all tool and SDK lists provide Linux/macOS equivalents alongside Windows options.
  • Where PowerShell is mentioned, clarify if Bash/CLI alternatives exist and provide parallel examples.
  • For tools like Data Lake Tools for Visual Studio, mention Linux-friendly alternatives (e.g., VS Code extensions, CLI tools).
  • Explicitly state platform compatibility for all listed utilities and SDKs.
  • If possible, add more Linux/macOS-specific usage notes where Windows tools are referenced.
GitHub Create Pull Request
Hdinsight Use SSH with Hadoop - Azure HDInsight ...icles/hdinsight/hdinsight-hadoop-linux-use-ssh-unix.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation provides a balanced overview of SSH usage across Windows, Linux, and macOS. However, there is a slight Windows bias: Windows tools and installation methods are listed in detail, including graphical clients (PuTTY, MobaXterm) and PowerShell cmdlets, while Linux/macOS are mostly referenced generically. PowerShell examples and parameters are given before CLI equivalents in cluster creation sections. Some configuration instructions (e.g., SSH agent forwarding) mention Linux/Bash first but clarify Windows support only as an aside.
Recommendations
  • Provide explicit Linux/macOS command-line examples for cluster creation and SSH key usage, not just generic references.
  • List Linux/macOS tools and installation steps with the same detail as Windows (e.g., mention how to install OpenSSH on Ubuntu, Fedora, macOS).
  • When showing Azure PowerShell and CLI commands, present CLI (cross-platform) examples before PowerShell (Windows-centric) ones.
  • Include graphical SSH client options for Linux/macOS (e.g., GNOME Terminal, Konsole, FileZilla for SCP) alongside Windows tools.
  • Clarify which instructions apply equally to all platforms, and highlight any platform-specific differences.
GitHub Create Pull Request
Hdinsight Use Azure Monitor logs to monitor Azure HDInsight clusters ...insight/hdinsight-hadoop-oms-log-analytics-tutorial.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Azure PowerShell and Azure CLI instructions for enabling Azure Monitor logs on HDInsight clusters, but PowerShell (a Windows-centric tool) is consistently presented before CLI, and receives more detailed, multi-step examples. There is a slight emphasis on Windows tools and patterns, with PowerShell prerequisites and examples listed before CLI, and no explicit mention of Linux/macOS-specific nuances or alternative shell environments. However, CLI examples are present and use bash syntax, which is cross-platform.
Recommendations
  • Alternate the order of PowerShell and CLI instructions so that CLI (Linux/macOS-friendly) is sometimes presented first.
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows, and provide any necessary notes for shell differences.
  • Add a short section or note for Linux/macOS users, clarifying that PowerShell is available cross-platform but CLI may be more familiar.
  • Ensure parity in example detail and troubleshooting steps for both PowerShell and CLI.
  • Mention that the Azure portal is OS-agnostic and can be used from any browser.
GitHub Create Pull Request
Hdinsight Use Azure Data Lake Storage Gen2 with Azure HDInsight clusters ...insight/hdinsight-hadoop-use-data-lake-storage-gen2.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page lists Windows-specific tools (PowerShell) as a primary method for cluster creation, with a direct link to PowerShell instructions. Linux/macOS equivalents (such as Bash or shell scripting) are not mentioned in the same section. However, the data access and usage examples are based on SSH and Unix-style commands, which are Linux/macOS-friendly. The order of cluster creation methods puts the Portal first, then Azure CLI (cross-platform), and then PowerShell (Windows-centric), but does not provide explicit Linux shell or Bash examples for cluster creation.
Recommendations
  • Add explicit Bash or shell scripting examples for cluster creation using Azure CLI.
  • Clarify that Azure CLI is cross-platform and provide installation/use instructions for Linux/macOS.
  • Include links or instructions for cluster creation on Linux/macOS environments, not just PowerShell.
  • Ensure parity in tool recommendations by mentioning Linux-native tools or scripts where PowerShell is referenced.
GitHub Create Pull Request
Hdinsight Managed identities in Azure HDInsight ...ain/articles/hdinsight/hdinsight-managed-identities.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists Azure PowerShell as a primary method for creating managed identities before Azure CLI, which is more cross-platform. There is a subtle Windows-first ordering in tool references, but Linux/macOS users are not blocked from completing any tasks, as Azure CLI and ARM methods are also mentioned.
Recommendations
  • List Azure CLI before Azure PowerShell when describing creation methods, as CLI is cross-platform.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide direct links or examples for those platforms.
  • Ensure examples and instructions are balanced between PowerShell and CLI, or provide parallel examples for both.
  • Avoid implying PowerShell is the default or preferred method unless there is a technical reason.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/includes/hdinsight-selector-use-hive.md ...cles/hdinsight/includes/hdinsight-selector-use-hive.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page lists multiple ways to interact with Hive on HDInsight, including platform-neutral tools (Beeline, Curl) and Windows-centric tools (.NET, PowerShell, Visual Studio). Windows tools are mentioned alongside cross-platform options, and Visual Studio and PowerShell are highlighted, which are primarily Windows-based. However, Linux options (Beeline, Curl) are present, and the order does not strictly prioritize Windows tools.
Recommendations
  • Ensure Linux/macOS equivalents are provided for all Windows-specific tools (e.g., suggest VS Code or JetBrains IDEs alongside Visual Studio).
  • Add explicit mention of Linux/macOS compatibility for each tool.
  • Consider listing platform-neutral tools first, or grouping tools by platform.
  • Provide links or instructions for using PowerShell Core on Linux/macOS if relevant.
GitHub Create Pull Request
Hdinsight Troubleshoot a slow or failing job on Azure HDInsight cluster ...les/hdinsight/hdinsight-troubleshoot-failed-cluster.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. PowerShell is mentioned as a management option, and references to Azure PowerShell are provided before Linux alternatives. While Azure CLI examples are present (which are cross-platform), PowerShell is called out as a separate option, and there is no explicit mention of Bash or Linux shell equivalents for some tasks. Additionally, the script action log file path uses backslashes (\), which is a Windows convention, and could confuse Linux users. However, the majority of troubleshooting steps focus on Ambari (Linux-based) and command-line tools like curl and netstat, which are standard on Linux. There are no critical sections that are Windows-only, but Linux parity could be improved.
Recommendations
  • Provide explicit Bash/Linux shell examples alongside PowerShell commands.
  • Use forward slashes (/) for file paths when referring to storage locations, or clarify path conventions for both platforms.
  • When listing management tools, mention Azure CLI and Bash/Linux shell options before or alongside PowerShell.
  • Clarify that Azure CLI is cross-platform and provide links to Linux/macOS installation instructions.
  • Add troubleshooting steps or examples that use SSH and native Linux tools for cluster management.
GitHub Create Pull Request
Hdinsight Quickstart: Apache Kafka using Bicep - HDInsight ...icles/hdinsight/kafka/apache-kafka-quickstart-bicep.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell examples are given equal prominence and are presented immediately alongside CLI examples, which may suggest a Windows-centric approach. There is no explicit mention of Linux/macOS-specific tools or shell environments, and no guidance for users who may not have PowerShell available. All SSH and Kafka management instructions use standard Bash commands, which are cross-platform and appropriate for Linux/macOS users.
Recommendations
  • Clearly state that Azure CLI commands work on Windows, Linux, and macOS, and recommend CLI as the default for cross-platform users.
  • Present Azure CLI examples before PowerShell examples to reduce perceived Windows-first bias.
  • Add a note clarifying that PowerShell is primarily for Windows users, while CLI is recommended for Linux/macOS.
  • Consider including explicit instructions for running Azure CLI on Linux/macOS, if relevant.
  • Ensure that any future scripting or automation examples do not assume PowerShell availability.
GitHub Create Pull Request
Hdinsight Connect Apache Kafka cluster with VM in different VNet on Azure HDInsight - Azure HDInsight ...fka/connect-kafka-cluster-with-vm-in-different-vnet.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows Example Present Linux Example Present Windows Linux Parity
Summary
The documentation provides steps for both Linux and Windows VMs, including how to edit the hosts file on each OS and how to access the Ambari dashboard. Linux examples (curl command, /etc/hosts) are shown first, with Windows-specific instructions and screenshots following. Both platforms are acknowledged, but the Windows section is less detailed (no command-line example, only a screenshot and host file path). There is no evidence of exclusive Windows bias; parity is reasonable.
Recommendations
  • Add explicit command-line examples for Windows (e.g., using PowerShell's Invoke-WebRequest or curl for Windows) to match the Linux curl example.
  • Clarify any OS-specific differences in Kafka client usage, if applicable.
  • Ensure screenshots for both Linux and Windows outputs are equally detailed.
  • Consider grouping OS-specific instructions together for easier reference.
GitHub Create Pull Request
Hdinsight Connect HDInsight Kafka cluster with client VM in different VNet on Azure HDInsight ...in/articles/hdinsight/kafka/connect-kafka-with-vnet.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides both Linux and Windows instructions for connecting a client VM to an HDInsight Kafka cluster across VNets. However, there is a slight Windows bias: Windows instructions (editing hosts file, Ambari access) are presented after Linux but with more detail, and Windows-specific paths and credential steps are explicitly called out. The documentation references Windows tools and patterns (e.g., editing C:\Windows\System32\drivers\etc\hosts) and provides more step-by-step guidance for Windows users. Linux instructions are present and functional, but Windows users receive more granular help.
Recommendations
  • Ensure Linux and Windows instructions are equally detailed and parallel in structure.
  • Provide explicit Linux command-line steps for editing /etc/hosts (e.g., using sudo nano or echo), not just a copy-paste instruction.
  • Include troubleshooting tips for Linux users (e.g., permissions for /etc/hosts, verifying DNS resolution).
  • Present Linux and Windows instructions side-by-side or in clearly separated, equally weighted sections.
  • Add PowerShell or command prompt examples for Windows users if shell commands are given for Linux.
  • Clarify that the Java client commands work identically on both platforms, and note any OS-specific caveats.
GitHub Create Pull Request
Hdinsight Use Apache Hadoop Hive with Curl in HDInsight - Azure ...ticles/hdinsight/hadoop/apache-hadoop-use-hive-curl.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash/cURL and PowerShell examples for all major steps, but PowerShell (Windows) examples are consistently shown immediately after Bash, and Windows tools (Invoke-WebRequest) are referenced first in the prerequisites. The explanations and variable naming sometimes favor PowerShell workflows, and the Azure CLI is mentioned only for file retrieval, without explicit Linux/macOS parity guidance.
Recommendations
  • Alternate the order of Bash and PowerShell examples, or present Bash (Linux/macOS) first to reflect the default HDInsight OS.
  • Explicitly mention Linux/macOS compatibility in the prerequisites and throughout the guide.
  • Provide more context for Linux/macOS users, such as troubleshooting tips or alternative tools if needed.
  • Include a note that all examples work on Linux/macOS unless otherwise stated.
  • Ensure that any references to Azure CLI or other tools include installation and usage instructions for Linux/macOS.
GitHub Create Pull Request
Hdinsight Cluster capacity planning in Azure HDInsight ...main/articles/hdinsight/hdinsight-capacity-planning.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias by mentioning PowerShell scripting and Azure Automation as the primary automation/scheduling methods for cluster lifecycle management, without referencing Linux/macOS equivalents (such as Bash scripting or cron). Windows tools and terminology (PowerShell, Azure Automation) are introduced before any mention of cross-platform or Linux-native approaches. However, most of the page is platform-neutral, focusing on Azure portal and service-level concepts.
Recommendations
  • Add examples or references for Linux/macOS automation, such as Bash scripts and using cron for scheduling cluster provisioning/deletion.
  • Explicitly state that HDInsight clusters run on Linux and that all automation can be performed from Linux/macOS using Azure CLI or REST API.
  • Provide parity in scripting guidance: show both PowerShell and Bash/CLI examples for cluster management tasks.
  • Clarify that Azure Automation can invoke scripts from any OS, not just PowerShell.
GitHub Create Pull Request
Hdinsight Query data from HDFS-compatible Azure storage - Azure HDInsight ...rticles/hdinsight/hdinsight-hadoop-use-blob-storage.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page lists Microsoft tools for accessing Azure Storage, including Azure PowerShell and AzCopy. Azure PowerShell is marked as Windows-only, and AzCopy is shown as available for Windows and Linux, but not macOS. The table lists Windows in the last column, but Azure PowerShell is only available for Windows, which may suggest a Windows-first approach. However, the main usage examples (SSH, HDFS, Hive) are Linux-centric, and the overall workflow does not depend on Windows-specific tools.
Recommendations
  • Provide parity for AzCopy on macOS, or clarify its availability.
  • Include Linux/macOS equivalents for Azure PowerShell tasks, or recommend Azure CLI for cross-platform scripting.
  • Reorder tool tables to list platforms in a neutral or alphabetical order, rather than ending with Windows.
  • Explicitly mention that all core HDInsight operations are performed on Linux clusters, and that Windows tools are optional for external access.
GitHub Create Pull Request
Hdinsight Use Azure Data Lake Storage Gen2 with Azure HDInsight clusters ...insight/hdinsight-hadoop-use-data-lake-storage-gen2.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists Windows PowerShell as a primary method for cluster creation, with a dedicated link, while Linux/macOS equivalents (e.g., Bash, Azure CLI) are mentioned but not given equal prominence or example coverage. However, all data access and usage examples are shown using SSH and Bash commands, which are Linux/macOS friendly.
Recommendations
  • Provide explicit Linux/macOS examples for cluster creation, such as Bash scripts or direct Azure CLI commands.
  • List Azure CLI instructions before or alongside PowerShell to avoid Windows-first ordering.
  • Clarify that PowerShell is Windows-specific and offer parity for Linux/macOS users in all major workflow sections.
  • Ensure all referenced links (e.g., for cluster creation) contain Linux/macOS instructions or examples.
GitHub Create Pull Request
← Previous Page 7 of 8 Next →