Hdinsight

439
Total Pages
279
Linux-Friendly Pages
160
Pages with Bias
36.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

867 issues found
Showing 826-850 of 867 flagged pages
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/includes/hdinsight-selector-use-mapreduce.md ...hdinsight/includes/hdinsight-selector-use-mapreduce.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation navigation lists 'PowerShell' and '.NET SDK' (both Windows-centric tools) before providing any explicit Linux or cross-platform alternatives. While SSH and Curl are included (which are cross-platform), the ordering and inclusion of PowerShell and .NET SDK without explicit mention of Linux-specific tools or examples indicates a mild Windows bias.
Recommendations
  • Add explicit Linux/macOS tool examples (e.g., Bash scripts, Linux CLI tools) to the navigation.
  • Reorder the list so that cross-platform tools (SSH, Curl) appear before Windows-specific tools (PowerShell, .NET SDK).
  • Include a section or links for Linux/macOS users, highlighting equivalent workflows.
  • Clarify in the documentation which tools are cross-platform and which are Windows-only.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias in the 'Create a virtual machine' section, where it exclusively links to instructions for creating a Windows Server VM, without mentioning or providing guidance for creating a Linux VM. This may lead Linux/macOS users to believe that only Windows VMs are supported or recommended for connecting to HBase clusters, despite the rest of the guide being focused on Linux-based clusters and providing Linux-oriented examples (e.g., curl, bash commands).
Recommendations
  • Include a link or instructions for creating a Linux VM in Azure alongside the Windows VM link.
  • Clarify that either Windows or Linux VMs can be used to connect to the HBase cluster, depending on user preference.
  • Present VM creation options for both platforms equally, or mention Linux first to match the cluster OS.
  • Add examples or notes for connecting from Linux/macOS environments where relevant.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation provides a note on how to obtain the SSH utility, listing Windows-specific options (Azure Cloud Shell, Bash on Ubuntu on Windows 10, Git, OpenSSH) before mentioning that Linux, Unix, and macOS include SSH by default. This section prioritizes Windows users and lists multiple Windows tools, while Linux/macOS users are only briefly acknowledged. No PowerShell examples or Windows-only commands are present, and all technical steps use Bash/Linux commands.
Recommendations
  • Present SSH instructions in a platform-neutral way, mentioning that Linux/macOS/Unix have SSH by default, and then listing Windows options.
  • Add explicit confirmation that all steps are applicable to Linux/macOS, and clarify any platform-specific differences if they exist.
  • If mentioning Windows tools, also mention equivalent Linux/macOS tools (even if SSH is built-in, note how to access it).
  • Consider reordering instructions so that Linux/macOS are not treated as an afterthought.
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-14 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, with Ubuntu/Linux as the underlying OS for clusters. However, in the 'Next steps' section, a Windows-specific link ('Work in Apache Hadoop on HDInsight from a Windows PC') is included, while Linux/macOS equivalents are absent. This subtly prioritizes Windows tooling and may imply Windows as the default client environment.
Recommendations
  • Add equivalent guidance for Linux and macOS users in the 'Next steps' section, such as 'Work in Apache Hadoop on HDInsight from a Linux/macOS PC'.
  • Ensure that any tooling or client instructions are provided for all major platforms, not just Windows.
  • Review linked content (e.g., 'hdinsight-hadoop-windows-tools.md') to confirm Linux/macOS parity and cross-link where appropriate.
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-14 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 always presented alongside CLI, and sometimes CLI is shown first. However, PowerShell is a Windows-centric tool, and its inclusion may suggest a Windows bias, especially since no Linux/macOS-specific shell examples (e.g., Bash scripts) are given. All instructions are cross-platform via Azure CLI, but the presence of PowerShell throughout may create friction for Linux/macOS users unfamiliar with it.
Recommendations
  • Clearly indicate that Azure CLI commands work on Linux, macOS, and Windows, and are the recommended cross-platform approach.
  • Consider moving PowerShell examples to a separate section or tab labeled 'Windows only', or add a note clarifying PowerShell is for Windows users.
  • Add explicit Bash shell script examples for Linux/macOS users, especially for tasks like saving files and running commands.
  • Where PowerShell is mentioned, provide context about its platform specificity.
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-13 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 cluster creation and management, and it is mentioned before Linux-native tools (like Azure CLI and cURL) in several places. While Linux-based cluster creation is referenced, Windows tools and patterns (PowerShell) are given equal or higher prominence, and examples for Linux-specific workflows are not always shown first.
Recommendations
  • List cross-platform tools (Azure CLI, cURL, SDKs) before Windows-specific tools like PowerShell in tables and examples.
  • Explicitly note which tools are cross-platform and which are Windows-only, to help users choose appropriately.
  • Provide Linux/macOS-specific examples and workflows alongside or before Windows/PowerShell examples.
  • Clarify in documentation sections when a method is Windows-specific (e.g., PowerShell) and offer alternatives for Linux/macOS users.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation presents Windows VM domain join instructions before Ubuntu/Linux, and references the Windows Control Panel UI for domain joining, which is a Windows-specific tool. While Linux instructions are present, Windows is prioritized and its tools are mentioned explicitly.
Recommendations
  • Present Linux and Windows domain join instructions in parallel, or list Linux first to balance representation.
  • Provide explicit Linux command-line steps for domain joining, not just a reference to a script.
  • Avoid referencing Windows-specific tools (e.g., Control Panel UI) without Linux equivalents.
  • Clarify that both Windows and Linux VMs can be used for debugging, and provide equal detail for both.
GitHub Create Pull Request
Hdinsight Authentication issues in Azure HDInsight ...t/domain-joined/domain-joined-authentication-issues.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page shows mild Windows bias. In the section about finding sAMAccountName, Windows AD tools are mentioned before Linux alternatives, and only Windows is explicitly referenced as a platform for browsing the directory. Linux methods (SAMBA commands) are mentioned but require prior Kerberos authentication, and no macOS alternatives are given. There are no PowerShell-specific examples, but Windows tools are referenced more prominently than Linux equivalents.
Recommendations
  • Add explicit Linux and macOS alternatives for browsing Active Directory, such as using 'ldapsearch' or other cross-platform tools.
  • Present Linux/SAMBA methods before or alongside Windows AD tools to avoid Windows-first ordering.
  • Clarify which steps are platform-agnostic and which require Windows, Linux, or macOS.
  • Where scripts or commands are referenced, ensure examples are provided for both Windows and Linux/macOS environments.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is generally neutral regarding OS bias, with all HDInsight versions listed as running on Ubuntu Linux. However, in the 'Next steps' section, a Windows-specific link ('Work in Apache Hadoop on HDInsight from a Windows PC') is provided, while no equivalent Linux/macOS guidance is offered. This subtly prioritizes Windows tooling and may suggest to users that Windows is the preferred or primary environment for client-side interaction.
Recommendations
  • Add links or sections for working with HDInsight from Linux and macOS clients, including recommended tools and setup guides.
  • Ensure parity in examples and tooling recommendations for all major platforms in 'Next steps' and related documentation.
  • If Windows tools are mentioned, provide Linux/macOS alternatives alongside or before them.
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-13 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 platforms, but exhibits mild Windows bias in several areas. Windows-specific tools and installation instructions are given more space and detail than Linux/macOS equivalents. PowerShell is referenced for cluster creation, and Windows tools like PuTTY and MobaXterm are highlighted. In some tables, Windows/PowerShell methods are listed before Linux/CLI alternatives.
Recommendations
  • Ensure Linux and macOS instructions/examples are given equal prominence and detail as Windows.
  • List Azure CLI and Linux-native methods before or alongside PowerShell/Windows methods in tables and sections.
  • Provide explicit Linux/macOS examples for cluster creation and SSH key usage, not just PowerShell and CLI.
  • Mention graphical SSH clients for Linux/macOS (e.g., GNOME Terminal, Konsole) alongside Windows options.
  • Clarify that Bash on Windows is available via WSL, and provide parity for native Linux/macOS environments.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation is generally Linux-focused, as expected for HDInsight on Linux, but there are subtle signs of Windows bias. In the section on accessing Azure Data Lake Storage Gen1, PowerShell and Visual Studio tools are mentioned before Linux-native alternatives, and some tooling (e.g., Data Lake Tools for Visual Studio) is Windows-only. There is also a tendency to mention Windows-centric tools (PowerShell, Visual Studio) alongside cross-platform options, which may create friction for Linux/macOS users.
Recommendations
  • When listing tools for accessing Azure Data Lake Storage, place cross-platform and Linux-native tools (Azure CLI, REST API, SDKs) before Windows-only options like PowerShell and Visual Studio.
  • Clearly indicate which tools are Windows-only and provide equivalent Linux/macOS alternatives where possible.
  • Add explicit Linux/macOS examples (e.g., Bash scripts, CLI usage) in sections where Windows tools are mentioned.
  • Consider adding a table or section summarizing tool availability by OS to help users quickly identify suitable options.
GitHub Create Pull Request
Hdinsight Managed identities in Azure HDInsight ...ain/articles/hdinsight/hdinsight-managed-identities.md
Low Priority View Details →
Scanned: 2026-01-13 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, and mentions it before Azure CLI. This ordering and emphasis may subtly favor Windows users, as PowerShell is more commonly associated with Windows environments. However, Azure CLI is also mentioned, and no examples or instructions are given that are exclusive to Windows or PowerShell. No explicit Windows-only tools or patterns are present, and Linux users are not blocked from completing any tasks.
Recommendations
  • List Azure CLI before Azure PowerShell in creation methods, as CLI is cross-platform.
  • Explicitly state that both Azure CLI and PowerShell are supported on Linux, macOS, and Windows.
  • Provide example commands for both Azure CLI and PowerShell, or link to platform-specific guides.
  • Avoid language that implies PowerShell is the default or preferred method.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias. Windows tools and patterns (PowerShell, Windows Server DNS) are mentioned before or alongside Linux equivalents, and PowerShell examples are given before Azure CLI. Windows-specific references (e.g., Add-DnsServerConditionalForwarderZone) are present, but Linux instructions (Bind DNS, SSH, Ubuntu VM) are also well-covered. The order of presentation and tool choice can create friction for Linux/macOS users, but most critical tasks have Linux instructions.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform.
  • Explicitly mention Linux/macOS DNS server configuration options before Windows Server references.
  • Where possible, provide Bash/Linux command examples first or equally with PowerShell.
  • Clarify that all steps can be performed on Linux/macOS unless otherwise noted.
  • Add links to Linux/macOS DNS server documentation (e.g., Bind, Unbound) before Windows Server DNS.
  • Avoid assuming PowerShell as the default scripting environment.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for retrieving host names via the Ambari REST API, but the PowerShell example is shown second and is more detailed. There is a slight Windows-first bias in the mention of PowerShell tools (ConvertFrom-Json) alongside jq, and the PowerShell example uses Windows-specific patterns (Get-Credential, Invoke-WebRequest) without mentioning Linux equivalents for credential management or web requests.
Recommendations
  • Explicitly mention that both Bash and PowerShell examples are provided for cross-platform users.
  • Provide equivalent Linux/macOS credential management and web request examples (e.g., using curl with --user or environment variables).
  • Ensure that Linux tools (jq, curl) are described with equal detail as PowerShell tools.
  • Consider listing Bash/Linux examples first to signal parity.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Minor Powershell Reference
Summary
The documentation page demonstrates a mild Windows bias, primarily through references to Windows-style environment variables (e.g., %HADOOP_HOME%), storage paths, and mentions of Azure PowerShell as a data copy method. However, most configuration and example commands are platform-neutral (bash, Java tools), and Linux-compatible instructions are provided. Windows tools and conventions are mentioned before Linux equivalents in a few places, but Linux/macOS users can generally follow the guidance without significant friction.
Recommendations
  • Replace or supplement Windows-style environment variable references (e.g., %HADOOP_HOME%) with Linux/macOS equivalents ($HADOOP_HOME).
  • When listing tools for data copy (e.g., Azure PowerShell, ADLCopy, DistCp), present Linux-native tools first or provide parity in examples for both platforms.
  • Explicitly clarify that all bash and Java keytool commands are cross-platform and provide any necessary platform-specific notes.
  • Add explicit Linux/macOS examples where Windows tools (like PowerShell) are mentioned.
  • Review and balance the order of tool mentions to avoid implicit prioritization of Windows solutions.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash/cURL and PowerShell/Invoke-WebRequest examples for all main steps, but PowerShell is consistently presented alongside Bash, sometimes with more detailed credential handling. The REST client prerequisite lists PowerShell first and links to Bash via WSL, subtly prioritizing Windows. There is no missing Linux example, but the parity in explanation and tool coverage could be improved.
Recommendations
  • List Bash/cURL examples before PowerShell to reflect the Linux-first nature of HDInsight clusters.
  • Clarify that Bash/cURL commands work natively on Linux/macOS, not just via WSL on Windows.
  • Ensure that explanations and troubleshooting notes apply equally to Bash and PowerShell, and highlight any differences.
  • Provide explicit instructions for running Bash commands on macOS and Linux, not just WSL.
  • Consider adding a summary table comparing Bash and PowerShell workflows for quick reference.
GitHub Create Pull Request
Hdinsight InvalidNetworkConfigurationErrorCode error - Azure HDInsight ...idnetworkconfigurationerrorcode-cluster-creation-fails.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page is generally Linux-focused, as HDInsight clusters run on Linux and most troubleshooting steps use Linux commands (ssh, nslookup, dig, resolv.conf). However, there is some Windows bias present: PowerShell and Azure Runbook are mentioned as sources of configuration errors, and the resolution refers to PowerShell cmdlets (Get-AzVirtualNetwork) without Linux CLI equivalents. Additionally, when discussing DNS server VMs, Windows is mentioned alongside Linux, and in some places, Windows tools or terminology appear first.
Recommendations
  • Provide Azure CLI or REST API equivalents for PowerShell commands and parameters, especially for network configuration validation.
  • When mentioning VM-based DNS servers, clarify Linux is the default/recommended option for HDInsight, and provide explicit instructions for both Linux and Windows setups.
  • If referencing PowerShell or Windows tools, always include Linux/CLI alternatives and present them with equal prominence.
  • Review the order of tool mentions to ensure Linux/CLI options are not secondary to Windows/PowerShell.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Cmd Prompt Examples
Summary
The documentation shows a slight Windows bias by presenting command-line examples using Windows Command Prompt syntax (cmd) before Linux/bash equivalents, especially for the curl and ssh commands. However, the core workflow (SSH, Phoenix, SQLLine) is inherently cross-platform and most commands are bash-compatible. There is no exclusive use of Windows tools or PowerShell, and Linux users can follow the instructions with minimal adaptation.
Recommendations
  • Provide both Windows (cmd/PowerShell) and Linux/macOS (bash) command examples side-by-side, especially for curl and ssh commands.
  • Clarify which commands are platform-agnostic and which require adaptation for different shells.
  • Explicitly mention that SQLLine and Phoenix client usage is identical across platforms.
  • Add notes or links for installing SSH and curl on Windows if not present.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates some Windows bias, particularly in the 'Prerequisites' section, where Bash usage is described in the context of Windows 10 (via WSL) before mentioning other Unix shells. Windows PowerShell's Invoke-RestMethod is referenced as an alternative for curl, and there is guidance for adapting curl examples to Windows Command Prompt. However, the main tutorial steps and code samples are Linux/Unix-centric, using SSH, Bash, and HBase shell commands, which are standard for HDInsight clusters (which run on Linux). There are no critical sections that are Windows-only, but Windows tools and patterns are mentioned first and given more explanation than their Linux equivalents.
Recommendations
  • Present Linux/macOS instructions and examples before Windows-specific adaptations in the prerequisites.
  • Clarify that HDInsight clusters are Linux-based and that Bash/SSH usage is native on Linux/macOS, with Windows users needing WSL or similar.
  • Provide explicit Linux/macOS command-line examples where Windows alternatives are mentioned.
  • Reduce emphasis on Windows PowerShell and Command Prompt unless necessary, and ensure parity in explanation for Linux/macOS users.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is generally Linux-focused, with Ubuntu VMs and Bash commands as the main examples. However, there is a notable Windows bias in the SSH instructions, where Windows tools and patterns are listed first and in detail, while Linux/macOS are mentioned only briefly. Windows-specific options (Azure Cloud Shell, Bash on Ubuntu on Windows, Git for Windows, OpenSSH for Windows) are enumerated, potentially giving Windows users more guidance and visibility. There are no PowerShell examples or Windows-only steps, but the ordering and tool recommendations show a mild Windows-first bias.
Recommendations
  • Present SSH instructions for Linux/macOS first, as these platforms are the default for HDInsight/HBase workloads.
  • List Windows SSH options after Linux/macOS, or in a separate section, to avoid implying Windows is the primary platform.
  • Include explicit instructions for macOS users if any platform-specific caveats exist.
  • Clarify that all steps are cross-platform unless otherwise noted, and avoid over-emphasizing Windows-specific tools.
  • If possible, provide parity in troubleshooting and tool recommendations for Linux/macOS users.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation shows mild Windows bias by referencing PowerShell and browser methods for cluster deletion before mentioning Azure CLI, and by using Windows-style SSH command syntax (sshuser@CLUSTERNAME-ssh.azurehdinsight.net) without explicit Linux/macOS examples. However, the core HBase Shell instructions are platform-neutral and the prerequisites mention SSH clients generically, with a link to Linux SSH usage.
Recommendations
  • Explicitly provide Linux/macOS SSH command examples, including common terminal usage and authentication patterns.
  • List Azure CLI as the first option for cluster deletion, or provide parity in instructions for Linux/macOS users.
  • Clarify that all HBase Shell commands are platform-agnostic and can be run from any OS with SSH access.
  • Add a note or section highlighting any OS-specific considerations (e.g., SSH key formats, terminal differences).
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-13 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 network security group creation and DNS configuration, but consistently lists PowerShell (Windows-centric) examples before CLI (cross-platform). The PowerShell section is more verbose and detailed, and the CLI examples are provided as a secondary option. There are no Linux shell (bash) or macOS-specific examples for local scripting, but Azure CLI is cross-platform. No Windows-only tools are required, and DNS configuration examples are Linux-focused.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform support.
  • Explicitly state that Azure CLI works on Linux/macOS/Windows and is recommended for non-Windows users.
  • Add bash script examples for common tasks where appropriate.
  • Balance the detail and explanation between PowerShell and CLI sections.
  • Add a note about PowerShell Core availability on Linux/macOS if PowerShell is needed.
GitHub Create Pull Request
Hdinsight Create Apache Hadoop clusters using templates - Azure HDInsight ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-create-linux-clusters-arm-templates.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias by referencing PowerShell and Visual Studio (Windows-centric tools) before Azure CLI and cross-platform editors. The PowerShell deployment method is described before the Azure CLI method, and Visual Studio is highlighted as a deployment tool with no equivalent mention of Linux/macOS IDEs. There are no explicit Linux/macOS command-line examples, and the .NET client library example links to a Windows-specific page. However, the page does mention cross-platform tools like VS Code and Azure CLI.
Recommendations
  • Present Azure CLI deployment instructions before PowerShell, as CLI is cross-platform.
  • Include explicit Linux/macOS command-line examples for template deployment.
  • Mention Linux/macOS compatible IDEs (e.g., JetBrains Rider, VS Code) alongside Visual Studio.
  • Ensure example links (such as .NET client library) point to platform-neutral or Linux/macOS-relevant documentation.
  • Clarify that PowerShell Core is available cross-platform, if referenced.
GitHub Create Pull Request
Hdinsight Apache Hadoop & secure transfer storage - Azure HDInsight ...oop-create-linux-clusters-with-secure-transfer-storage.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides instructions for managing secure transfer settings in Azure Storage accounts using the Azure portal, PowerShell, and Azure CLI. PowerShell (a Windows-centric tool) is given a dedicated section before Azure CLI, and no explicit Linux/macOS shell examples (e.g., Bash) are provided. While Azure CLI is cross-platform, the ordering and prominence of PowerShell may subtly favor Windows users.
Recommendations
  • Present Azure CLI instructions before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Add explicit Bash shell examples for Azure CLI commands to demonstrate usage on Linux/macOS.
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS.
  • Consider mentioning other Linux-native tools or scripting approaches if relevant.
GitHub Create Pull Request
Hdinsight Monitor and manage Hadoop with Ambari REST API - Azure HDInsight ...s/hdinsight/hdinsight-hadoop-manage-ambari-rest-api.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Bash and PowerShell examples for all operations, but consistently lists Windows/PowerShell examples immediately after or alongside Bash, and sometimes refers to Windows tools (e.g., PowerShell, Windows Subsystem for Linux, Windows paths for jq) in prerequisites and example setup. Windows-specific instructions and references (such as using Bash on Windows 10, PowerShell, and Windows paths for jq) are given prominence, and Azure PowerShell cmdlets are mentioned as alternatives for some tasks. Linux/macOS users are supported, but Windows patterns and tools are frequently foregrounded.
Recommendations
  • List Bash/Linux/macOS examples first, as HDInsight clusters are Linux-based.
  • Clarify that Bash examples work natively on Linux/macOS, not just via Windows Subsystem for Linux.
  • Provide explicit instructions for running Bash examples on Linux/macOS (e.g., mention that jq is available via package managers).
  • Reduce references to Windows-specific tools and paths (e.g., avoid hardcoding Windows jq paths in PowerShell examples).
  • Add a section summarizing cross-platform usage, highlighting Linux/macOS parity.
  • Where Azure PowerShell is mentioned, also mention Azure CLI as a cross-platform alternative.
GitHub Create Pull Request
← Previous Page 34 of 35 Next →