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 701-725 of 867 flagged pages
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-use-hive-curl.md ...ticles/hdinsight/hadoop/apache-hadoop-use-hive-curl.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 major steps, but consistently lists PowerShell (Windows) examples before Bash (Linux) ones. PowerShell is referenced by name and linked, while Bash is described as 'if you use Bash'. The Azure CLI is mentioned only for file retrieval, without explicit Linux parity guidance. There is no evidence of exclusive use of Windows tools, but the ordering and framing favor Windows/PowerShell users.
Recommendations
  • Alternate the order of examples, sometimes listing Bash first to avoid implicit prioritization of Windows.
  • Explicitly state that both Bash and PowerShell are supported equally, and clarify that Bash examples apply to native Linux and WSL environments.
  • Provide more context for Linux users, such as installation instructions for required tools (curl, jq) on common distributions.
  • Include a note that Azure CLI works on both Windows and Linux, with links to installation guides for both platforms.
  • Consider adding a table summarizing command equivalence across platforms for quick reference.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-replication.md ...n/articles/hdinsight/hbase/apache-hbase-replication.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is largely Linux/Ubuntu-focused for all hands-on examples and commands, but there is a notable Windows bias in the section describing how to obtain the SSH utility. Windows tools and workarounds are listed before Linux/macOS, and several Windows-specific solutions are mentioned, even though Linux is the primary platform for the actual cluster and VM operations.
Recommendations
  • When listing ways to obtain SSH, mention Linux/macOS first, as they are the native environments for these clusters. Place Windows-specific instructions after Linux/macOS.
  • Provide parity in tool recommendations: for example, if mentioning 'Bash on Ubuntu on Windows 10', also mention that Linux and macOS users have native terminals.
  • Avoid over-emphasizing Windows-specific tools (like PowerShell or Win32-OpenSSH) unless they are required for the workflow. If mentioned, clarify that these are for Windows users only.
  • Consider a short section or callout for Windows users, rather than interleaving Windows-specific advice in the main flow.
  • Ensure that all code examples and primary instructions are platform-neutral or Linux-first, given the context of HDInsight clusters running on Linux.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-component-versioning.md ...n/articles/hdinsight/hdinsight-component-versioning.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is generally neutral and Linux-focused in terms of HDInsight cluster OS (Ubuntu), but it displays Windows bias in the 'Next steps' section by specifically highlighting a guide for working from a Windows PC and referencing Windows tools. No equivalent Linux client guide is mentioned, and Windows is called out explicitly before any Linux alternatives.
Recommendations
  • Add a parallel guide for working in Apache Hadoop on HDInsight from a Linux PC, and reference it alongside the Windows guide.
  • Ensure that examples and tooling references throughout the documentation include both Windows and Linux options, or clarify cross-platform compatibility.
  • Review other linked pages (such as setup guides) to confirm Linux parity in examples and instructions.
  • In 'Next steps', list Linux and Windows options together, or in alphabetical order, to avoid implicit prioritization.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-migrate-dotnet-to-linux.md .../hdinsight/hdinsight-hadoop-migrate-dotnet-to-linux.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily describes migration from Windows-based HDInsight to Linux-based HDInsight, but most examples and tooling references (e.g., Visual Studio, .NET Portability Analyzer) are Windows-centric. The steps for portability analysis and building .NET solutions focus on Windows tools (Visual Studio) without mentioning Linux-native alternatives or cross-platform workflows. There are no examples of using Linux-based development environments or command-line tools for .NET development and analysis.
Recommendations
  • Include examples of using .NET Portability Analyzer or equivalent tools on Linux (e.g., via command-line or VS Code).
  • Describe how to build and test .NET applications using Linux-native tools (e.g., Mono's command-line compiler, dotnet CLI).
  • Provide guidance for developers who do not use Visual Studio, such as those working on Linux or macOS.
  • Add explicit examples of file path handling and other platform-specific issues, showing both Windows and Linux conventions.
  • Mention cross-platform editors (e.g., VS Code) and build systems that work on Linux.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/hdinsight-security-overview.md ...hdinsight/domain-joined/hdinsight-security-overview.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Active Directory-based authentication (Microsoft Entra Domain Services), referencing domain credentials, and listing PowerShell as a primary access method for cluster interaction. There are no examples or mentions of Linux-native authentication systems (such as LDAP, Kerberos outside AD, or PAM), nor are Linux command-line tools or shell examples provided for cluster access or management. The documentation assumes a Windows-centric enterprise environment and omits Linux-specific guidance.
Recommendations
  • Include examples of authenticating and managing HDInsight clusters using Linux-native tools (e.g., SSH, curl, Linux shell commands).
  • Mention and provide guidance for integrating with non-Active Directory identity providers (e.g., LDAP, MIT Kerberos) where possible.
  • Provide sample commands and workflows for Linux users, such as using bash scripts or Linux CLI utilities to interact with clusters.
  • Clarify whether features like ODBC/JDBC, REST APIs, and auditing are equally accessible from Linux environments, and provide relevant examples.
  • Balance references to PowerShell with equivalent bash or Linux shell examples for common administrative tasks.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/find-host-name.md ...re-docs/blob/main/articles/hdinsight/find-host-name.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash (Linux) 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 Windows-specific tools (ConvertFrom-Json) are mentioned alongside Linux tools (jq). There is a slight Windows-first bias in mentioning Windows tools and patterns (PowerShell, ConvertFrom-Json) at parity with Linux tools, rather than prioritizing Linux, which is more common in HDInsight clusters.
Recommendations
  • Explicitly state which example is for Linux/macOS and which is for Windows, rather than presenting them as equal alternatives.
  • Provide the Linux/Bash example first, as HDInsight clusters are typically Linux-based.
  • Add a note clarifying that most HDInsight clusters run on Linux and that the Bash/jq example is the default approach.
  • If possible, provide additional Linux-native tools or commands (e.g., Python, curl with grep/sed/awk) to increase parity.
  • Consider including troubleshooting tips or environment setup instructions for Linux users (e.g., installing jq).
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/hdinsight-use-mapreduce.md ...n/articles/hdinsight/hadoop/hdinsight-use-mapreduce.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page lists Windows PowerShell as a distinct method for submitting MapReduce jobs, with a dedicated link, while Linux/Unix/macOS users are directed to SSH and Curl methods. Windows-specific tooling (PowerShell) is mentioned explicitly and given its own section, whereas Linux equivalents (such as Bash scripts or CLI tools) are not highlighted in the same way. The table lists Windows PowerShell last, but it is the only OS-specific tool called out, suggesting a bias towards Windows tooling.
Recommendations
  • Add explicit examples and walkthroughs for submitting MapReduce jobs using Bash scripts or Linux CLI tools, similar to the PowerShell example.
  • If PowerShell is given a dedicated section, consider adding parallel sections for Bash or other Linux-native tools.
  • Highlight cross-platform tools first (such as SSH and Curl) before mentioning OS-specific tools like PowerShell.
  • Clarify that SSH and Curl methods are fully supported and provide equivalent functionality on Linux, macOS, and Windows.
  • Ensure that any OS-specific instructions are balanced with equivalents for other platforms.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-provision-vnet.md ...rticles/hdinsight/hbase/apache-hbase-provision-vnet.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by providing instructions for creating a Windows Server virtual machine first, without mentioning Linux alternatives. There are no examples or links for creating a Linux VM in the relevant section, despite the cluster itself being Linux-based. This may confuse or inconvenience users who prefer or require Linux environments for cluster management or client applications.
Recommendations
  • Include instructions or links for creating a Linux virtual machine in the same virtual network, alongside or before the Windows VM example.
  • Ensure parity in examples and guidance for both Windows and Linux environments, especially since the cluster is Linux-based.
  • Explicitly mention that either Windows or Linux VMs can be used for client connectivity, and provide references for both.
  • Review other sections for similar patterns and provide balanced coverage for Linux tools and workflows.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-query-with-phoenix.md ...les/hdinsight/hbase/apache-hbase-query-with-phoenix.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page shows mild Windows bias by presenting command-line examples using the Windows command prompt syntax (e.g., 'cmd' code blocks for curl and ssh), and by referencing deletion via PowerShell before mentioning Azure CLI. There are no explicit Linux shell examples for curl or ssh, and no mention of Linux-specific tools or patterns, despite HDInsight clusters being Linux-based. The documentation does not provide parity for Linux users in terms of example commands or tool usage.
Recommendations
  • Provide Linux shell examples (bash syntax) for curl and ssh commands, using appropriate code block annotations.
  • Explicitly mention Linux terminal usage for connecting to HDInsight clusters, as HDInsight is Linux-based.
  • When referencing cluster deletion, mention Azure CLI and browser methods before PowerShell, or provide equal prominence to all platforms.
  • Clarify any platform-specific requirements for SQLLine installation and usage, including instructions for both Windows and Linux.
  • Ensure all command examples are cross-platform or provide alternatives for both Windows and Linux users.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-apache-kafka-spark-structured-streaming.md ...t/hdinsight-apache-kafka-spark-structured-streaming.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides host information retrieval commands specifically for Windows command prompt, with references to Windows paths and instructions to enter commands in a Windows environment. There are no equivalent Linux/macOS shell examples, nor is there guidance for users on those platforms. This creates a Windows-first experience and leaves Linux users without direct instructions for a critical setup step.
Recommendations
  • Provide equivalent shell commands for Linux/macOS environments, including example paths for jq and usage of standard bash syntax.
  • Clearly indicate platform-specific instructions and group them so users can easily find the relevant steps for their OS.
  • Avoid language such as 'the commands are designed for a Windows command prompt' without immediately following with Linux/macOS alternatives.
  • Where possible, use cross-platform commands or note any differences in syntax or tool usage between Windows and Linux.
  • Add a table or section summarizing command differences for Windows, Linux, and macOS users.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-authorize-users-to-ambari.md ...icles/hdinsight/hdinsight-authorize-users-to-ambari.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents PowerShell as the first and most detailed scripting example for adding users to Ambari, with Linux/bash (curl) provided only after. The PowerShell example is more verbose and includes additional steps and explanations, while the Linux/bash example is shorter and described as requiring 'slight modifications' for Windows, implying Windows as the default environment. There is a general tendency to mention Windows tools and patterns before Linux equivalents.
Recommendations
  • Present Linux/bash (curl) and PowerShell examples side-by-side, or alternate which is shown first.
  • Ensure both examples are equally detailed, with similar explanation and context.
  • Explicitly state platform compatibility for both examples, rather than implying Windows as the default.
  • Add notes or links for using REST API with other scripting languages (e.g., Python, Bash, etc.) to improve cross-platform parity.
  • Avoid language that positions Windows tools as the default or primary method.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-create-virtual-network.md ...articles/hdinsight/hdinsight-create-virtual-network.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 examples for network security group configuration, but PowerShell examples are consistently shown before CLI examples. This ordering, along with extensive PowerShell scripting, may suggest a Windows-first or PowerShell-heavy bias. However, the DNS configuration examples are Linux-centric, and the network validation tool is recommended for Linux VMs, which helps balance the bias. No explicit Windows-only tools or missing Linux examples are present.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to improve parity for Linux users.
  • Explicitly state that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Add Bash shell script equivalents for network configuration steps where appropriate.
  • Include a short section highlighting platform-neutral approaches (e.g., using ARM templates or Terraform) for advanced users.
  • Clarify that PowerShell is available on Linux and macOS, but CLI may be more familiar to Linux users.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-for-vscode.md ...s/blob/main/articles/hdinsight/hdinsight-for-vscode.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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, primarily by presenting Windows-centric file paths (e.g., C:\HD\HDexample) as the default in examples and instructions, without providing equivalent Linux/macOS paths or guidance. While prerequisites mention Mono for Linux/macOS, most step-by-step instructions and screenshots use Windows conventions. Linux-specific notes are rare and appear only in isolated cases (e.g., xclip for copy-table data), and there are no Linux shell or macOS-specific examples for folder navigation or file creation.
Recommendations
  • Provide parallel examples using Linux/macOS file paths (e.g., /home/user/HDexample) alongside Windows paths in all relevant instructions.
  • Add explicit instructions or screenshots for opening folders and creating files in Visual Studio Code on Linux/macOS, noting any UI or shortcut differences.
  • Where Windows-specific tools or patterns are mentioned (such as C:\ paths), include a note or sidebar for Linux/macOS users describing the equivalent process.
  • Expand Linux/macOS troubleshooting notes beyond the xclip mention, covering common issues or differences in workflow.
  • Ensure all command-line or configuration file references (e.g., .VSCode\settings.json) use platform-agnostic or dual-path notation (e.g., .vscode/settings.json for Linux/macOS).
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-customize-cluster-linux.md .../hdinsight/hdinsight-hadoop-customize-cluster-linux.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell is consistently mentioned before Azure CLI in lists and examples, and PowerShell examples are more detailed and prominent than Azure CLI equivalents. The .NET SDK (Windows-centric) is also featured. While Bash scripts and Linux clusters are the technical focus, the documentation prioritizes Windows tools and patterns in its guidance and examples.
Recommendations
  • Present Azure CLI examples before or alongside Azure PowerShell examples, especially since HDInsight clusters are Linux-based.
  • Expand Azure CLI example sections to match the detail and coverage of PowerShell examples.
  • Include explicit Linux shell (Bash) command-line examples for common tasks, such as viewing script history or promoting/demoting scripts, where possible.
  • Clarify that both Windows and Linux users can use the Azure CLI and portal, and provide installation instructions for both platforms.
  • Where .NET SDK is mentioned, also reference Python SDK or other cross-platform alternatives if available.
  • Audit all command tables and lists to ensure CLI and PowerShell are given equal prominence and detail.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-use-blob-storage.md ...rticles/hdinsight/hdinsight-hadoop-use-blob-storage.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page generally maintains cross-platform parity, with most examples and instructions using Linux/Unix conventions (e.g., SSH, Bash, HDFS CLI). However, in the 'Access files from outside cluster' section, Windows-specific tools (Azure PowerShell) are listed, and AzCopy is noted as available only on Windows and Linux, with OS X omitted. Azure PowerShell is presented as a Windows-only tool, and the table lists Windows last, but the presence of a Windows-only tool (Azure PowerShell) without a Linux equivalent may suggest a slight Windows bias in tooling recommendations.
Recommendations
  • Provide Linux equivalents or alternatives for Azure PowerShell tasks, such as using Azure CLI or REST API.
  • Clarify that AzCopy is available on Linux and Windows, and note any OS X alternatives or limitations.
  • If possible, include example commands for both Linux and Windows environments where differences exist.
  • Ensure that tooling recommendations do not favor Windows-only tools unless absolutely necessary, and always mention cross-platform options first.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-managed-identities.md ...ain/articles/hdinsight/hdinsight-managed-identities.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 mentioning Azure CLI, which is more commonly used on Linux. There is a tendency to mention Windows-centric tools (PowerShell) before cross-platform or Linux-friendly alternatives (CLI). No explicit Linux examples or Linux-specific guidance are provided, and the documentation does not reference Linux shell commands or patterns.
Recommendations
  • List Azure CLI before Azure PowerShell when presenting creation methods, as CLI is cross-platform and widely used on Linux.
  • Include explicit Linux shell examples or guidance for common tasks, such as using Bash scripts for automation.
  • Add notes or sections clarifying parity between Windows and Linux environments, especially regarding managed identity usage and limitations.
  • Reference Linux tools and patterns where relevant, ensuring that instructions are not Windows-centric.
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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page lists Windows-centric tools (PowerShell, .NET, Visual Studio) alongside platform-neutral or Linux-friendly options (Beeline, Curl), but Windows tools are given equal or greater prominence. There is no explicit prioritization of Linux tools, and the inclusion of multiple Windows-specific options (PowerShell, Visual Studio, .NET) suggests a bias towards Windows environments.
Recommendations
  • Add explicit Linux shell examples (e.g., Bash scripts) and highlight their usage.
  • Include references to Linux-native tools (e.g., Hive CLI, SSH) and place them before or alongside Windows tools.
  • Ensure parity in depth and detail for Linux and Windows tool documentation.
  • Consider grouping platform-neutral tools first, followed by platform-specific options.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/cluster-management-best-practices.md ...rticles/hdinsight/cluster-management-best-practices.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page lists Azure PowerShell as a primary method for creating HDInsight clusters, which is a Windows-centric tool, and places it before cURL and SDK examples. While Linux-based cluster creation is referenced, and Azure CLI is included (which is cross-platform), the explicit mention and placement of Azure PowerShell and lack of equivalent Linux shell scripting examples indicate a mild Windows bias.
Recommendations
  • Add explicit Bash or shell script examples for cluster management tasks alongside PowerShell examples.
  • Ensure that Linux-native tools (e.g., Bash, SSH, cURL) are mentioned with equal prominence and ordering as Windows tools.
  • Clarify cross-platform compatibility for each tool (e.g., Azure CLI, PowerShell) and provide guidance for both Linux and Windows users.
  • Include troubleshooting and customization examples using Linux-native tools where possible.
  • Consider reordering examples so that cross-platform or Linux-native options are listed before Windows-specific tools.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/hdinsight-security-overview.md ...hdinsight/domain-joined/hdinsight-security-overview.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Active Directory-based authentication (Microsoft Entra Domain Services), which is a Windows-centric technology, and by mentioning PowerShell as a client tool for cluster access without listing Linux-native alternatives (e.g., SSH, curl, or Linux command-line tools). There are no examples or references to Linux authentication mechanisms (such as LDAP or Kerberos integration outside of AD), nor are Linux-specific tools or patterns discussed for cluster management or access.
Recommendations
  • Include examples and references to Linux-native authentication mechanisms, such as integration with standard LDAP or MIT Kerberos, where supported.
  • List Linux command-line tools (e.g., SSH, curl, wget, Hadoop CLI) alongside PowerShell when describing ways to interact with clusters.
  • Provide explicit Linux usage examples for cluster access, management, and auditing (e.g., how to view audit logs using Linux tools).
  • Clarify whether features like ESP and RBAC are compatible with non-Windows environments and document any Linux-specific setup steps.
  • Add guidance for Linux administrators on configuring and managing HDInsight security, including references to open-source tools commonly used in Linux environments.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-create-virtual-network.md ...articles/hdinsight/hdinsight-create-virtual-network.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 examples for network security group configuration, but consistently lists PowerShell examples before CLI, and provides more detailed PowerShell scripts. This ordering and emphasis may subtly prioritize Windows users and workflows, as PowerShell is primarily associated with Windows environments, despite its cross-platform availability. There are no explicit Linux shell (bash) examples for Azure resource management, though Linux is referenced in DNS and validation sections.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid implicit prioritization of Windows tooling.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users, and provide bash shell script examples where appropriate.
  • Add a section or callout for Linux users, clarifying recommended tools and workflows for managing Azure resources.
  • Ensure parity in detail and completeness between PowerShell and CLI examples.
  • Consider including sample scripts for resource management using bash or other Linux-native tools, where possible.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-apache-kafka-spark-structured-streaming.md ...t/hdinsight-apache-kafka-spark-structured-streaming.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing host information retrieval commands specifically for Windows command prompt, with explicit instructions and syntax tailored to Windows (e.g., REM, set, C:\HDI\jq-win64.exe). It notes that 'slight variations will be needed for other environments' but does not provide equivalent Linux/macOS examples. The rest of the tutorial uses Jupyter Notebook and bash cells, which are cross-platform, but the initial cluster host info step is Windows-centric.
Recommendations
  • Provide explicit Linux/macOS command examples for host information retrieval, including appropriate jq paths and shell syntax (e.g., export, $VARIABLE, ./jq).
  • Present Windows and Linux/macOS instructions side-by-side or in tabs, ensuring parity and clarity for users on all platforms.
  • Avoid language such as 'commands are designed for a Windows command prompt' without offering alternatives; instead, state platform-specific instructions.
  • Where file paths are referenced (e.g., C:\HDI\jq-win64.exe), also show typical Linux/macOS paths (e.g., /usr/local/bin/jq).
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-use-blob-storage.md ...rticles/hdinsight/hdinsight-hadoop-use-blob-storage.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page generally maintains cross-platform parity, with most examples and instructions using Linux/Unix conventions (e.g., SSH, Bash, HDFS commands). However, in the 'Access files from outside cluster' section, Windows-specific tools (Azure PowerShell, AzCopy for Windows) are listed, and Azure PowerShell is only available for Windows. The table lists Windows tools explicitly and sometimes before their Linux equivalents, which may suggest a slight Windows bias in tooling recommendations.
Recommendations
  • Provide explicit Linux alternatives for all listed Windows-only tools (e.g., suggest Bash scripts or Python SDK for tasks handled by Azure PowerShell).
  • Ensure that Linux tools are mentioned first or in parallel with Windows tools to avoid perceived prioritization.
  • Add more Linux/Unix command-line examples for interacting with Azure Storage outside of HDInsight (e.g., using Azure CLI, REST API, or SDKs).
  • Clarify in the tooling table that Azure PowerShell is Windows-only and suggest alternatives for Linux users.
  • Where possible, include example workflows for both Linux and Windows environments, especially in sections discussing external access and automation.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-component-versioning.md ...n/articles/hdinsight/hdinsight-component-versioning.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is generally neutral and describes HDInsight as running on Ubuntu Linux VMs. However, in the 'Next steps' section, the only platform-specific guidance is for Windows ('Work in Apache Hadoop on HDInsight from a Windows PC'), and Windows tools are referenced before any Linux equivalents. There are no Linux-specific examples or instructions, and Windows is highlighted as a client platform for interacting with HDInsight clusters.
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 PC' or 'from a Mac'.
  • Provide links to documentation or tutorials for using Linux-native tools (e.g., SSH, Hadoop CLI, Spark CLI) to interact with HDInsight clusters.
  • Ensure that platform-specific instructions are presented in parallel (e.g., 'Windows', 'Linux', 'macOS') rather than Windows-first.
  • Review other related documentation pages to ensure Linux parity in client-side tooling and examples.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-authorize-users-to-ambari.md ...icles/hdinsight/hdinsight-authorize-users-to-ambari.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents PowerShell instructions before Linux/bash equivalents for user management, and offers a detailed PowerShell script while the bash/curl example is less emphasized. The PowerShell section is labeled as a primary method, and Windows tooling is referenced before Linux alternatives, suggesting a Windows-first bias. However, Linux/bash instructions are present and functional, and a warning is included for Linux-specific behavior.
Recommendations
  • Present Linux/bash and Windows/PowerShell instructions in parallel, or alternate which platform is shown first.
  • Explicitly state that both PowerShell and bash/curl methods are supported and equivalent.
  • Expand the bash/curl example to match the detail and commentary of the PowerShell example.
  • Add notes on running PowerShell on Linux and bash on Windows (e.g., via WSL), to clarify cross-platform options.
  • Review other sections for implicit Windows-first ordering and ensure Linux parity in tool references and examples.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/find-host-name.md ...re-docs/blob/main/articles/hdinsight/find-host-name.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash (Linux) and PowerShell (Windows) examples for retrieving host names via the Ambari REST API. However, the PowerShell example is more elaborate and uses Windows-specific tooling (Invoke-WebRequest, ConvertFrom-Json, Get-Credential), while the Bash example is simpler. The mention of PowerShell tools (ConvertFrom-Json) appears before the Bash tool (jq) in the explanatory text, and the PowerShell example is given equal prominence despite HDInsight clusters typically being Linux-based.
Recommendations
  • Provide more detailed Bash/Linux examples, including authentication and error handling, to match the PowerShell example's depth.
  • Mention Linux tools (jq) before Windows tools (ConvertFrom-Json) in explanatory text, or present both together.
  • Clarify that most HDInsight clusters run on Linux and that Bash examples may be more directly applicable.
  • Consider adding examples for other platforms (e.g., Python scripts) to further reduce platform bias.
GitHub Create Pull Request
← Previous Page 29 of 35 Next →