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 176-200 of 200 flagged pages
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/includes/hdinsight-selector-use-sqoop.md ...les/hdinsight/includes/hdinsight-selector-use-sqoop.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 PowerShell and .NET examples alongside SSH and Curl, but PowerShell (a Windows-centric tool) is given its own section and is mentioned before .NET, which is also more common on Windows. The ordering places Windows tools before Linux equivalents, and the presence of a dedicated PowerShell section suggests a Windows bias.
Recommendations
  • Reorder the examples so that platform-neutral or Linux/macOS tools (SSH, Curl) appear before Windows-specific tools (PowerShell, .NET).
  • Ensure that Linux/macOS instructions are as detailed and prominent as Windows instructions.
  • Add explicit notes clarifying cross-platform applicability for each method.
  • Consider grouping examples by platform or providing parity in depth and clarity for each.
GitHub Create Pull Request
Hdinsight Cluster management best practices - Azure HDInsight ...rticles/hdinsight/cluster-management-best-practices.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 Azure PowerShell as a primary method for cluster creation and management, with PowerShell examples and links appearing alongside Azure CLI and cURL. In several tables, Windows-centric tools (PowerShell) are mentioned before Linux-native alternatives (Azure CLI, cURL). However, Linux options are present and documented, and most examples refer to 'Linux-based clusters.'
Recommendations
  • List Azure CLI and cURL before PowerShell in tables and sections to avoid Windows-first ordering.
  • Explicitly mention Linux/macOS compatibility for each method/tool.
  • Ensure example commands are provided for both PowerShell and CLI/cURL in all relevant sections.
  • Add a note clarifying that PowerShell is primarily for Windows, while CLI/cURL are cross-platform.
  • Consider grouping cross-platform tools together and separating Windows-only tools.
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-11 06:20
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, but the PowerShell example is given immediately after the Bash example and includes more detailed credential handling. There is a slight Windows-first bias in the ordering and depth of examples, and the mention of ConvertFrom-Json links to PowerShell documentation, while jq is referenced only by its homepage. No critical Linux/macOS functionality is missing, but Windows tools are presented with more context.
Recommendations
  • Ensure equal depth and explanation for both Bash and PowerShell examples, including credential handling for Bash (e.g., using curl -u or environment variables).
  • Provide links to jq documentation similar to the PowerShell ConvertFrom-Json link.
  • Consider alternating the order of examples or explicitly stating that both platforms are supported equally.
  • Add a note clarifying that both examples work on their respective platforms and provide guidance for macOS users if needed.
GitHub Create Pull Request
Hdinsight Connect Azure HDInsight to your on-premises network ...main/articles/hdinsight/connect-on-premises-network.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates mild Windows bias by frequently listing Windows-centric tools (PowerShell) before Linux alternatives, providing PowerShell examples in critical sections, and referencing Windows Server DNS documentation before Linux equivalents. However, Linux usage is well-supported throughout, with explicit instructions for creating and configuring a Linux-based DNS server using Bind, and Azure CLI examples are provided alongside PowerShell. The bias is mostly in ordering and emphasis, not in missing functionality.
Recommendations
  • Present Azure CLI and Linux examples before or alongside PowerShell/Windows examples, especially in sections where both are relevant.
  • Reference Linux/BIND DNS documentation before or alongside Windows Server DNS documentation in the 'Configure on-premises DNS server' section.
  • Where PowerShell scripts are provided, ensure equivalent Azure CLI or Bash scripts are shown with equal prominence.
  • Explicitly mention that all steps can be completed on Linux/macOS unless a step is Windows-specific.
  • Add more cross-platform notes, e.g., for SSH, clarify that macOS and Linux users have built-in SSH clients.
GitHub Create Pull Request
Hdinsight Cluster creation fails with DomainNotFound error in Azure HDInsight ...hdinsight/domain-joined/troubleshoot-domainnotfound.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation presents Windows VM troubleshooting steps before Linux (Ubuntu) equivalents, and references domain join via Windows Control Panel UI, a Windows-specific tool. While an Ubuntu example is provided, the Windows approach is described first and in more familiar terms, suggesting a slight preference for Windows workflows.
Recommendations
  • Present Linux (Ubuntu) troubleshooting steps before or alongside Windows steps to avoid order bias.
  • Provide explicit Linux command-line examples for domain joining, not just a reference to a script.
  • Describe the Ubuntu workflow with equal detail as the Windows workflow (e.g., explain what the script does, prerequisites, etc.).
  • Mention macOS if relevant, or clarify its support status.
  • Avoid referencing Windows-specific tools (like Control Panel UI) without Linux equivalents.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias by referencing Windows-style environment variables (e.g., %HADOOP_HOME%) and mentioning file paths in Windows format before Linux equivalents. However, all command-line examples (openssl, keytool, hadoop) use bash syntax, which is cross-platform and more common on Linux/macOS. There are no PowerShell-specific examples, and Linux users can follow the instructions without significant friction.
Recommendations
  • When referencing configuration file paths, provide both Windows and Linux/macOS formats (e.g., %HADOOP_HOME%/conf/core-site.xml and $HADOOP_HOME/conf/core-site.xml).
  • Clarify that all command-line examples work on Linux/macOS and Windows (with appropriate tools installed), or provide platform-specific notes where differences exist.
  • Avoid using Windows environment variable syntax exclusively; mention $HADOOP_HOME for Linux/macOS.
  • If any UI instructions differ between platforms, note those differences.
  • Consider including explicit Linux/macOS examples for any ambiguous steps.
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-11 06:20
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-line examples in Windows command prompt syntax (cmd) first, such as the curl and ssh commands, without providing explicit Linux/macOS equivalents or clarifying cross-platform usage. The deletion section references PowerShell before Azure CLI, but does mention both. There are no PowerShell-heavy or Windows-only tool dependencies, and most commands (curl, ssh, SQLLine) are cross-platform, but the initial presentation favors Windows users.
Recommendations
  • Provide both Windows and Linux/macOS command examples side-by-side, especially for curl and ssh commands.
  • Clarify that commands like curl and ssh work on Linux/macOS and provide bash syntax where appropriate.
  • When referencing deletion methods, list Azure CLI first or equally with PowerShell, and provide explicit Linux/macOS instructions.
  • Add notes or callouts for platform-specific differences, if any.
GitHub Create Pull Request
Hdinsight Create HBase clusters in a Virtual Network - Azure ...rticles/hdinsight/hbase/apache-hbase-provision-vnet.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias in the 'Create a virtual machine' section, where instructions and links are provided only for creating a Windows Server VM, with no mention of Linux VM creation. This may create friction for Linux users who wish to set up a Linux-based edge node or client VM in the same virtual network. The rest of the documentation is generally platform-neutral or Linux-oriented, especially regarding cluster creation and connectivity.
Recommendations
  • Add parallel instructions and links for creating a Linux VM in Azure, such as referencing the official 'Create a Virtual Machine Running Linux' documentation.
  • Clarify that either Windows or Linux VMs can be used for connecting to the HBase cluster, depending on user preference.
  • Where examples reference OS-specific commands (e.g., 'ping'), ensure they are valid for both Windows and Linux, or provide both syntaxes if they differ.
  • Review other sections for subtle platform assumptions and ensure parity in tooling and workflow descriptions.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates some Windows bias, especially in the prerequisites section. Bash on Windows 10 (via WSL) is mentioned first for running curl commands, and PowerShell's Invoke-RestMethod is referenced as an alternative. There is explicit guidance for Windows users to install WSL, while Linux/macOS users are only briefly mentioned as 'other Unix shells.' Although most command examples use Bash and SSH (which are cross-platform), the initial framing and tool recommendations prioritize Windows environments and tools.
Recommendations
  • Present Linux/macOS instructions and examples before or alongside Windows-specific ones.
  • Provide explicit examples for Linux/macOS terminal usage, not just Bash on Windows.
  • Avoid recommending Windows tools (e.g., PowerShell Invoke-RestMethod) without mentioning Linux/macOS equivalents (e.g., curl, wget).
  • Clarify that all commands work natively on Linux/macOS, and provide troubleshooting notes for those platforms if needed.
  • Add a dedicated section for Linux/macOS prerequisites and environment setup.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation provides guidance for both Linux and Windows users, but in the SSH section, it lists Windows options for obtaining the ssh utility before mentioning that Linux/macOS have it by default. Several Windows-specific tools (Azure Cloud Shell, Bash on Ubuntu on Windows, Git for Windows, OpenSSH for Windows) are mentioned, but no equivalent Linux tools are highlighted. However, all technical examples and commands use Bash and Linux utilities, and the overall workflow is Linux-centric.
Recommendations
  • List Linux/macOS SSH usage first, then Windows options to avoid 'Windows first' impression.
  • When mentioning tools for SSH on Windows, also briefly note that Linux and macOS users have native support, and provide parity by mentioning popular Linux SSH clients (if relevant).
  • Consider adding a short section or note confirming that all steps are tested and supported on Linux/macOS, and clarify any differences if they exist.
  • If Windows-specific tools are mentioned, ensure Linux equivalents are also referenced (e.g., mention PuTTY for Windows, but also OpenSSH for Linux).
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-11 06:20
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, with Ubuntu/Linux as the platform for clusters. However, in the 'Next steps' section, a link is provided specifically for 'Work in Apache Hadoop on HDInsight from a Windows PC', highlighting Windows tooling for client-side interaction. No equivalent Linux/macOS client guidance is offered or referenced, and Windows is mentioned before Linux in this context.
Recommendations
  • Add links or sections for working with HDInsight from Linux and macOS clients, including recommended tools and setup guides.
  • Ensure parity in 'Next steps' by providing Linux/macOS alternatives alongside Windows-specific instructions.
  • Review other documentation pages linked from here to ensure examples and tooling are not Windows-exclusive.
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-11 06:20
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 core tasks, but consistently lists PowerShell (Windows-centric) examples before CLI (cross-platform) ones. The PowerShell section is more verbose and detailed, potentially signaling a preference for Windows users. However, CLI examples are present and complete, and Linux-specific guidance is included for DNS configuration and network validation.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform parity.
  • Explicitly state that Azure CLI works on Windows, Linux, and macOS at the start of the examples section.
  • Ensure that all PowerShell examples have equivalent CLI examples, and vice versa.
  • Add a note or section for Bash scripting for users who prefer shell scripts.
  • Where possible, provide links to Linux/macOS-specific setup guides for Azure CLI and related tools.
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-11 06:20
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 platforms, but there is a mild Windows bias. Windows-specific tools (OpenSSH Client, Bash on Ubuntu on Windows, Azure Cloud Shell, Git, PuTTY, MobaXterm) are listed in detail, while Linux/macOS SSH usage is assumed and not elaborated. Azure PowerShell examples and parameters are mentioned before Azure CLI equivalents, and PowerShell is referenced as a primary method for cluster creation and management. Linux examples are present, but Windows tools and patterns are often described first or in more detail.
Recommendations
  • Provide explicit Linux/macOS command-line examples for cluster creation and SSH key usage, not just Azure CLI references.
  • List Linux/macOS SSH usage and tools before Windows-specific options in the SSH clients section.
  • Balance PowerShell and CLI examples, or provide Bash scripts for Linux/macOS users alongside PowerShell commands.
  • Include troubleshooting steps and configuration tips for Linux/macOS SSH clients, not just generic references.
  • Clarify when instructions are platform-specific, and offer parity in graphical client recommendations (e.g., mention Linux graphical SSH clients like GNOME Terminal, Konsole, etc.).
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Minor Windows Tools
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for enabling Azure Monitor logs on HDInsight clusters. PowerShell (Windows-centric) instructions are consistently presented before CLI (cross-platform) instructions, and PowerShell is referenced in prerequisites and examples. However, CLI instructions are present and use bash syntax, supporting Linux/macOS users. There are no Windows-only tools or steps, and Linux-specific considerations (e.g., performance counters, OMI agent) are mentioned. The bias is mainly in ordering and emphasis, not in actual functionality gaps.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI first to better support Linux/macOS parity.
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows, and that PowerShell is primarily for Windows users.
  • Add a short note for each example block clarifying platform compatibility.
  • Consider adding a table summarizing which tools are recommended for each OS.
  • Highlight Linux-specific considerations (e.g., agent installation, performance counters) more prominently.
GitHub Create Pull Request
Hdinsight Set up clusters in HDInsight with Hadoop, Spark, and Kafka ...hdinsight/hdinsight-hadoop-provision-linux-clusters.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by referencing Windows PowerShell as a primary method for cluster customization, mentioning Windows tools in related content, and listing Azure PowerShell alongside Azure CLI as command-line options. Linux is referenced, but Windows tools and patterns are sometimes mentioned first or exclusively, and Linux-specific examples or parity are not always explicit.
Recommendations
  • Ensure all command-line examples and instructions are provided for both Azure CLI (cross-platform) and Azure PowerShell, with Linux/macOS usage clearly documented.
  • Where PowerShell is mentioned, provide equivalent Bash or shell script examples for Linux/macOS users.
  • In related content, balance Windows-specific links (e.g., 'Work in Apache Hadoop on HDInsight from a Windows PC') with Linux/macOS equivalents, such as 'Work in Apache Hadoop on HDInsight from a Linux/Mac PC'.
  • Explicitly state when instructions or tools are cross-platform, and avoid implying Windows as the default environment.
  • Highlight Linux-based cluster management and customization options, especially in sections discussing script actions and edge nodes.
GitHub Create Pull Request
Hdinsight Understand and resolve WebHCat errors on HDInsight - Azure ...ght/hdinsight-hadoop-templeton-webhcat-debug-errors.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 references Windows-centric tools (Azure PowerShell, Data Lake Tools for Visual Studio) as primary examples of clients using WebHCat, without mentioning Linux/macOS alternatives (such as curl, Python scripts, or Linux CLI tools). The introduction positions Windows tools first, which may imply Windows is the default or preferred platform for interacting with WebHCat.
Recommendations
  • Mention Linux/macOS-compatible tools (e.g., curl, wget, Python requests, or Hadoop CLI) as examples of clients using WebHCat.
  • Provide example commands for interacting with WebHCat from Linux/macOS environments.
  • Clarify that WebHCat is accessible from any OS with HTTP capabilities, not just Windows-based tools.
  • Balance references to Windows and Linux/macOS tools in introductory and troubleshooting sections.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/includes/hdinsight-portal-management-selector.md ...sight/includes/hdinsight-portal-management-selector.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page lists Azure PowerShell and .NET SDK (both Windows-centric tools) before Azure CLI, which is cross-platform. The ordering and inclusion of Windows-specific tools (.NET SDK, PowerShell) ahead of CLI may signal a Windows-first bias. There is no explicit mention of Linux/macOS-specific tools or examples, nor is there an indication that the CLI is preferred for cross-platform use.
Recommendations
  • List Azure CLI before PowerShell and .NET SDK to emphasize cross-platform support.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide links to Linux/macOS-specific usage guides.
  • Add a note clarifying platform compatibility for each tool.
  • Consider including Bash or Linux shell examples where relevant.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents both Azure PowerShell and Azure CLI commands for key network management tasks, but PowerShell examples are consistently listed first. There is a notable emphasis on PowerShell scripting for resource discovery and configuration, which is more familiar to Windows users. While Azure CLI is cross-platform and examples are provided, the ordering and scripting focus may create friction for Linux/macOS users. No Windows-only tools or missing Linux examples are present, but the documentation subtly prioritizes Windows-centric patterns.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first to better support Linux/macOS users.
  • Explicitly state that Azure CLI is cross-platform and recommend it for Linux/macOS environments.
  • Provide Bash script examples for resource discovery and configuration tasks, especially where PowerShell scripting is shown.
  • Add a short section or note clarifying that all tasks can be performed on Linux/macOS using Azure CLI.
  • Where scripting is shown in PowerShell, offer equivalent Bash/CLI script snippets.
GitHub Create Pull Request
Hdinsight Azure HDInsight supported node configurations ...es/hdinsight/hdinsight-supported-node-configuration.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references PowerShell scripts as a primary method for deploying HDInsight clusters and provides instructions for obtaining VM SKU identifiers specifically for use in PowerShell and 'other scripts', with PowerShell mentioned first. There are no explicit Linux or Bash examples, nor is there mention of Linux-specific tools or patterns. The bias is subtle but present in the prioritization of Windows/PowerShell terminology and workflows.
Recommendations
  • Explicitly mention Bash/Azure CLI as an equal alternative to PowerShell for scripting deployments.
  • Provide example commands for both PowerShell and Bash/Azure CLI where scripting is referenced.
  • Clarify that VM SKU identifiers are used in both PowerShell and Bash/Azure CLI scripts, and show examples for each.
  • Add a note or section highlighting cross-platform compatibility and usage patterns.
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-11 06:20
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 and resource management, but consistently lists PowerShell examples immediately after CLI, and includes detailed PowerShell commands. There are no Linux-specific shell examples for Azure management (e.g., Bash scripts), and PowerShell is a Windows-centric tool, though it is available cross-platform. The SSH and Kafka management sections are Linux-oriented, but the initial deployment and cleanup steps show a mild Windows bias by presenting PowerShell as a primary option.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and recommend Bash for Linux/macOS users.
  • Include Bash script examples for deployment and cleanup steps, or clarify that Azure CLI commands are intended for Bash/Unix shells.
  • Consider listing CLI/Bash examples before PowerShell, or grouping them by platform (Windows vs. Linux/macOS).
  • Add a note about PowerShell Core being available on Linux/macOS, if PowerShell is shown.
  • Where appropriate, provide platform-specific guidance for prerequisites (e.g., installing Azure CLI on Linux/macOS).
GitHub Create Pull Request
Hdinsight Quickstart: Create Apache Spark cluster using Bicep - Azure HDInsight ...dinsight/spark/apache-spark-jupyter-spark-use-bicep.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 Azure CLI and Azure PowerShell examples for deploying and managing resources, but PowerShell examples are consistently presented alongside CLI, and sometimes with more detail. PowerShell is a Windows-centric tool, and its inclusion may suggest a slight Windows bias. However, Azure CLI is cross-platform and shown first in all code tabs, and all steps can be completed on Linux/macOS using CLI. No Windows-only tools or patterns are mentioned, and Linux is referenced in the Bicep template name. There are no missing Linux examples, and no exclusive use of Windows tools.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add a note clarifying that PowerShell Core is available on Linux/macOS, but Azure CLI is typically preferred.
  • Consider including a brief section or callout for Linux/macOS users, confirming that all steps are supported on those platforms.
  • Ensure screenshots and portal instructions do not assume a Windows environment (e.g., file paths, browser recommendations).
GitHub Create Pull Request
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-10 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 the SSH connection example using the Windows command prompt format (`cmd`) and not providing explicit Linux/macOS terminal examples. The SSH client prerequisite links to a Unix-focused guide, but the actual example uses Windows syntax. No PowerShell or Windows-specific tools are mentioned beyond this, and the HBase shell usage is platform-neutral.
Recommendations
  • Provide both Windows (cmd/PowerShell) and Linux/macOS (bash) SSH connection examples, or use a platform-neutral format.
  • Clarify that the SSH command works on Linux/macOS terminals as well as Windows, and mention common SSH clients for each OS.
  • If referencing deletion via PowerShell, also show equivalent Azure CLI and portal steps for Linux/macOS users, or link directly to cross-platform instructions.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates mild Windows bias by mentioning PowerShell scripting and Azure Automation as methods for cluster lifecycle management, without providing equivalent Linux/macOS CLI or scripting examples. Windows tools are referenced before any Linux alternatives, and no Bash or Azure CLI examples are given for provisioning or deleting clusters. However, the majority of the documentation is platform-neutral and focuses on Azure portal usage and general concepts.
Recommendations
  • Include Azure CLI and Bash script examples for cluster provisioning and deletion alongside PowerShell.
  • Explicitly mention that Azure Automation can run scripts written in Bash or Python, not just PowerShell.
  • Add links or references to Linux/macOS-specific guidance for HDInsight cluster management.
  • Ensure that scripting examples are provided for both Windows and Linux environments in future updates.
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-10 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 creating and configuring virtual networks and network security groups, but consistently lists PowerShell (Windows-centric) examples before CLI (cross-platform). The PowerShell script is more detailed and comprehensive, while the CLI steps are more segmented. There are no Linux shell or Bash examples for Azure management tasks, though DNS configuration examples are Linux-focused. The prerequisites mention both PowerShell and CLI, but PowerShell is listed first. Overall, Windows/PowerShell is given slight precedence, but Linux users can complete all tasks using Azure CLI and DNS instructions.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform parity.
  • Add Bash shell examples for Azure CLI usage where appropriate.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
  • Balance the detail level between PowerShell and CLI examples, ensuring CLI instructions are as comprehensive.
  • Consider adding a table comparing PowerShell and CLI commands for each major step.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples and guidance for both Azure PowerShell and Azure CLI, but PowerShell examples and references are consistently presented before CLI equivalents. Output and cmdlet examples are shown for PowerShell, while CLI examples are present but less detailed. There is a slight Windows-first bias in the ordering and depth of examples, but Linux parity is mostly maintained since Bash scripts are the core mechanism and CLI instructions are included.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, especially in sections where both are supported.
  • Expand Azure CLI examples to match the detail and output shown for PowerShell, including sample outputs and step-by-step instructions.
  • Explicitly state that Azure CLI is cross-platform and highlight its usage for Linux/macOS users.
  • Add a summary table comparing PowerShell and CLI commands for common tasks.
  • Ensure that all code samples and walkthroughs are available for both PowerShell and CLI, with equal prominence.
GitHub Create Pull Request
← Previous Page 8 of 8 Next →