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 751-775 of 867 flagged pages
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/set-up-pyspark-interactive-environment.md
...es/hdinsight/set-up-pyspark-interactive-environment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page assumes Windows as the default environment, only providing detailed setup steps for non-Windows (Linux/macOS) users as a special case. There are no explicit Linux command-line examples for common tasks (such as launching VS Code or running Spark commands), and the guidance for Linux users is limited to troubleshooting package installation. Windows tools and workflows are implicitly prioritized.
Recommendations
- Provide parallel setup instructions for both Windows and Linux/macOS users, not just for non-Windows as an exception.
- Include Linux/macOS-specific command-line examples for launching VS Code, running Spark commands, and managing Python environments.
- List Linux and Windows instructions side-by-side or in clearly separated sections to ensure parity.
- Mention Linux package managers and tools (e.g., apt, yum, brew) where relevant, not just in troubleshooting.
- Explicitly state when steps differ between platforms, and ensure Linux/macOS users are not treated as an afterthought.
Create Pull Request
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-40-component-versioning.md
...rticles/hdinsight/hdinsight-40-component-versioning.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page lists a 'Next steps' link specifically for working with HDInsight from a Windows PC, highlighting Windows tools. There is no equivalent mention or link for Linux or cross-platform tools, and the Windows-specific guidance appears before any Linux-specific guidance. No Linux or cross-platform command-line examples or tools are mentioned.
Recommendations
- Add a 'Work in Apache Hadoop on HDInsight from a Linux PC' link in the 'Next steps' section, parallel to the Windows PC link.
- Ensure that any platform-specific tooling or setup guides are provided for both Windows and Linux users.
- Consider reordering or grouping platform-specific links together to avoid the appearance of prioritizing Windows.
- If possible, provide cross-platform examples or note when instructions are applicable to both Windows and Linux.
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 →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page is largely neutral and focused on HDInsight versioning, but in the 'Next steps' section, the only platform-specific workflow highlighted is 'Work in Apache Hadoop on HDInsight from a Windows PC', which appears before any Linux-specific guidance. There is also a reference to Windows tools, but no equivalent mention of Linux or cross-platform tooling, which may suggest a subtle Windows bias.
Recommendations
- Add a parallel 'Work in Apache Hadoop on HDInsight from a Linux PC' link in the 'Next steps' section, or a cross-platform guide.
- Ensure that references to platform-specific tools or workflows are balanced, with Linux and macOS options given equal prominence to Windows.
- Review other linked documentation (such as the Windows tools page) to ensure Linux alternatives are mentioned and linked.
- Consider reordering or grouping platform-specific links together, or prefacing with a cross-platform option.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/connect-install-beeline.md
...n/articles/hdinsight/hadoop/connect-install-beeline.md
Medium Priority
View Details →
Detected Bias Types
Wsl Heavy
Windows First
Summary
The documentation is generally cross-platform in its usage examples, with all command-line instructions provided in bash syntax suitable for Linux or macOS. However, the 'Install Beeline client' section is heavily oriented towards Windows users by focusing on installation via Windows Subsystem for Linux (WSL), mentioning Windows file paths, and not providing native Linux or macOS installation instructions. This creates a bias towards Windows environments, especially for users seeking to install Beeline on non-Windows systems.
Recommendations
- Add a dedicated subsection for installing Beeline natively on Linux distributions (e.g., Ubuntu, CentOS) and macOS, with appropriate package manager commands and environment variable setup.
- Clarify that the WSL-based instructions are specific to Windows users and provide parallel instructions for other operating systems.
- Avoid referencing Windows-specific paths (e.g., /mnt/c/Users/user/) as the default; instead, use generic Unix-style paths and note Windows-specific paths only in a dedicated section.
- Explicitly state OS prerequisites or differences at the start of the installation section to guide users to the most relevant instructions for their platform.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/use-pig.md
...ocs/azure-docs/blob/main/articles/hdinsight/use-pig.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page references SQL Server Integration Services (SSIS) and the Azure Feature Pack for SSIS as a method for running Pig jobs, which are Windows-centric tools. There are no examples or walkthroughs for running Pig jobs from Linux environments, nor are Linux-native tools or command-line examples provided. The documentation omits Linux/Unix command-line usage, which is common for Hadoop/Pig workflows.
Recommendations
- Add examples of running Pig jobs using SSH and the Linux command line, such as using the pig command in Bash.
- Include references to cross-platform tools (e.g., PuTTY for Windows, OpenSSH for Linux/macOS) for connecting to HDInsight clusters.
- Provide walkthroughs for submitting Pig jobs from both Windows and Linux environments to ensure parity.
- Mention and link to documentation for running Pig scripts directly from the cluster's head node using standard Hadoop/Pig commands.
- Balance the mention of Windows-specific tools (like SSIS) with Linux-native or cross-platform alternatives.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-templeton-webhcat-debug-errors.md
...ght/hdinsight-hadoop-templeton-webhcat-debug-errors.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references Windows-centric tools (Azure PowerShell, Data Lake Tools for Visual Studio) as primary client-side interfaces for WebHCat, without mentioning Linux or cross-platform alternatives. No Linux-specific tools or command-line examples are provided, and there is no guidance for users working from Linux environments.
Recommendations
- Mention cross-platform or Linux-native tools (such as curl, wget, or the Linux command line) for interacting with the WebHCat REST API.
- Provide example commands for submitting jobs or querying status using Linux shell tools.
- Reference Hadoop command-line utilities (e.g., hadoop, hive, or beeline) where appropriate.
- Include guidance for Linux users on how to modify configurations or troubleshoot issues, possibly via SSH or Ambari CLI.
- Ensure that any mention of Windows-specific tools is balanced with Linux equivalents, and avoid implying that Windows tools are the primary or only supported method.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-intellij-tool-plugin.md
...s/hdinsight/spark/apache-spark-intellij-tool-plugin.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation is generally cross-platform, as HDInsight Spark clusters are Linux-based and IntelliJ IDEA is available on both Windows and Linux. However, there is a notable Windows bias in the Spark Local Console section, where the prerequisite for WINUTILS.EXE is mentioned without any Linux equivalent or guidance for Linux users. No Linux-specific instructions or troubleshooting are provided, and the documentation does not clarify that WINUTILS.EXE is only required on Windows. This omission may confuse Linux users and suggests an implicit Windows-first assumption for local development.
Recommendations
- Clearly state that WINUTILS.EXE is only required on Windows, and that Linux/macOS users do not need this prerequisite.
- Add a section or note for Linux/macOS users explaining any differences or confirming that no extra steps are needed for local Spark console usage.
- Where platform-specific configuration is required (e.g., environment variables like HADOOP_HOME), provide examples for both Windows and Linux/macOS (e.g., using export in bash for Linux).
- Review the documentation for other subtle Windows assumptions (such as file paths or keyboard shortcuts) and provide Linux/macOS equivalents where relevant.
- Consider adding a troubleshooting section for common platform-specific issues encountered on Linux/macOS.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/kafka/apache-kafka-quickstart-bicep.md
...icles/hdinsight/kafka/apache-kafka-quickstart-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell commands for deployment and resource management, but consistently lists PowerShell as the second option, which is a subtle 'windows_first' ordering. There is a notable presence of PowerShell examples throughout, which may be unnecessary for Linux-focused users. However, the SSH and Kafka management sections are Linux/Unix-centric, with all examples using Bash commands and Linux tools. There are no exclusive Windows tools or missing Linux examples, but the dual presentation of PowerShell and CLI, with CLI first, may still suggest a slight Windows bias due to the inclusion of PowerShell in all steps.
Recommendations
- Consider clearly labeling which command sets are for Windows and which are for Linux/macOS, especially for Azure CLI and PowerShell, to help users quickly find relevant instructions.
- If PowerShell is not required for Linux/macOS users, clarify this in the documentation and possibly move PowerShell sections to an appendix or a separate tab for Windows users.
- Ensure parity by providing Bash equivalents for any PowerShell commands if new steps are added in the future.
- Explicitly state that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, to encourage non-Windows users.
- If possible, provide a summary table at the top indicating which tools are recommended for each OS.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/enterprise-security-package.md
...main/articles/hdinsight/enterprise-security-package.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias, particularly in the 'Next steps' section, where working from a Windows PC is explicitly mentioned and linked before any Linux equivalent. Additionally, there is a reference to Windows-specific tools without parallel Linux guidance. No Linux-specific examples or tools are highlighted, and the documentation does not provide parity in guidance for Linux users.
Recommendations
- Add explicit Linux examples and guidance alongside or before Windows-specific instructions.
- Include a 'Work in Apache Hadoop on HDInsight from a Linux PC' link in the 'Next steps' section, mirroring the Windows PC guidance.
- Ensure that any references to tools or workflows are presented in a cross-platform manner, or provide equivalent instructions for both Windows and Linux environments.
- Review all linked articles to ensure Linux parity is maintained throughout the documentation set.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/troubleshoot-domainnotfound.md
...hdinsight/domain-joined/troubleshoot-domainnotfound.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents Windows VM troubleshooting steps before Linux (Ubuntu) steps, and specifically references using the Windows Control Panel UI for domain join, which is a Windows-specific tool. While both Windows and Ubuntu examples are given, the ordering and tool references indicate a mild Windows bias.
Recommendations
- Present Linux (Ubuntu) and Windows troubleshooting steps in parallel or alternate the order to avoid always listing Windows first.
- For the Windows example, mention command-line alternatives (e.g., PowerShell or command prompt) in addition to the Control Panel UI.
- Provide equal detail for both Windows and Linux steps, ensuring parity in the depth of instructions.
- Where possible, generalize instructions to be OS-agnostic, or clearly separate platform-specific guidance under distinct headings.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/enable-private-link-on-kafka-rest-proxy-hdi-cluster.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/enable-private-link-on-kafka-rest-proxy-hdi-cluster.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page provides instructions primarily through Azure Portal UI steps and does not reference any command-line tools or scripts. There is no mention of Linux CLI tools (such as Azure CLI or Bash), nor are there PowerShell or Windows-specific commands, but the lack of any CLI examples means Linux users do not have parity or guidance for automating these steps outside the portal.
Recommendations
- Add Azure CLI examples for creating private endpoints and configuring DNS, as these are cross-platform and widely used on Linux.
- Include Bash script snippets for automating the process, where applicable.
- Explicitly mention that the steps can be performed via CLI or ARM templates, and provide links or examples.
- Ensure that any references to tools or commands are cross-platform or provide both Windows (PowerShell) and Linux (Bash/Azure CLI) equivalents.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash (with jq) and PowerShell examples for retrieving host names via the Ambari REST API. However, the PowerShell example is more detailed, including credential prompts and parsing, while the Bash example is more minimal. The mention of 'ConvertFrom-Json' (PowerShell) appears before the Bash 'jq' tool in the explanatory text, and the PowerShell example is given immediately after the Bash example, suggesting a slight Windows-first and PowerShell-heavy bias. There are no Linux-specific tools or patterns highlighted beyond the basic Bash/jq example.
Recommendations
- Provide equally detailed Bash/Linux examples, including credential handling and error checking, to match the PowerShell example's depth.
- Mention Linux/Bash tools (like jq) before or alongside Windows/PowerShell tools in explanatory text.
- Add a note about installing jq on Linux if not present, similar to how PowerShell modules are referenced.
- Consider including examples for other shells/environments (e.g., zsh, fish) or scripting languages (e.g., Python) to broaden platform parity.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash (Linux) and PowerShell (Windows) examples for all major steps, but consistently lists PowerShell/Windows examples after Bash/Linux ones. However, there is a slight bias in the 'Prerequisites' section, where 'Invoke-WebRequest' (PowerShell) is mentioned before 'Curl' (Bash), and the general pattern of referencing Windows-specific tools (like PowerShell) is present. The documentation does not omit Linux examples, but does sometimes give more detailed context or explanation for PowerShell commands.
Recommendations
- Ensure that Linux/Bash tools (curl, jq) are mentioned before or alongside Windows/PowerShell tools in all sections, including prerequisites.
- Provide equal depth of explanation and context for both Bash and PowerShell examples.
- Where possible, use cross-platform tools (like curl) as the primary example, with OS-specific alternatives clearly secondary.
- Explicitly state that all examples are available for both Linux and Windows, and avoid implying a default preference for Windows tools.
- Consider adding a table at the start summarizing equivalent commands for both platforms to reinforce parity.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally focuses on Linux-based clusters and provides Linux-centric instructions for cluster creation and management. However, in the 'Create a virtual machine' section, the only explicit example and link provided is for creating a Windows Server VM, with no mention or link for creating a Linux VM. This prioritizes Windows and omits Linux VM creation guidance, which is relevant for users seeking end-to-end Linux parity.
Recommendations
- Add parallel instructions and a link for creating a Linux virtual machine in Azure, ideally before or alongside the Windows VM example.
- When referencing VM creation, use neutral language or provide both Windows and Linux options equally.
- Review other sections for similar omissions and ensure that Linux examples are always present when Windows examples are given.
- Consider adding a note highlighting that both Windows and Linux VMs can be used, with links to both sets of instructions.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-40-component-versioning.md
...rticles/hdinsight/hdinsight-40-component-versioning.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page lists a 'Next steps' link specifically for working from a Windows PC, highlighting Windows tooling. There is no equivalent mention of Linux or cross-platform tools in the same section, and the Windows link appears before any Linux-specific guidance. This suggests a subtle Windows-first and Windows-tools bias.
Recommendations
- Add a 'Work in Apache Hadoop on HDInsight from a Linux PC' link in the 'Next steps' section, or a general 'Work from Linux or macOS' link.
- Ensure parity in tooling documentation by providing equivalent Linux/macOS guidance wherever Windows-specific tools or workflows are mentioned.
- Consider reordering or grouping platform-specific links together to avoid the appearance of prioritizing Windows.
- Explicitly mention cross-platform tools and workflows where possible, to reinforce platform neutrality.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-5x-component-versioning.md
...rticles/hdinsight/hdinsight-5x-component-versioning.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page is mostly neutral and platform-agnostic, focusing on open-source component versions. However, in the 'Next steps' section, a link specifically highlights working with HDInsight from a Windows PC and references Windows tools before any mention of Linux or cross-platform alternatives. There is no explicit Linux example or parity in the suggested next steps.
Recommendations
- Add a parallel link or section for 'Work in Apache Hadoop on HDInsight from a Linux PC' or 'from macOS', ensuring Linux users are equally supported.
- In the 'Next steps' section, list cross-platform or Linux resources before or alongside Windows-specific resources to avoid the impression of Windows being the default or preferred environment.
- Wherever Windows tools are mentioned, provide equivalent Linux tool guidance or references.
- Review other related documentation to ensure Linux and cross-platform usage is consistently represented.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides host information gathering commands specifically for Windows command prompt, with explicit references to Windows paths and syntax (e.g., REM, set, C:\HDI\jq-win64.exe), and notes that 'slight variations will be needed for other environments.' However, it does not provide equivalent Linux/macOS shell examples or guidance. This prioritizes Windows and leaves Linux users to adapt on their own.
Recommendations
- Provide equivalent Linux/macOS shell commands for gathering Kafka host information, using bash syntax (e.g., export, $HOME/jq, forward slashes).
- Explicitly show both Windows and Linux/macOS command blocks side by side or in tabs, so users on any platform can follow without guesswork.
- Avoid Windows-specific pathing (e.g., C:\HDI\jq-win64.exe) in generic instructions, or always provide the alternative (e.g., ~/jq/jq or /usr/bin/jq) for Linux.
- Clarify any differences in command usage or output formatting between platforms.
- Consider adding a note or section on cross-platform compatibility for all prerequisite tools and steps.
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 →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page is largely neutral and Linux-focused in its main content, as all HDInsight clusters are shown to use Ubuntu as the VM OS. However, in the 'Next steps' section, the only platform-specific guidance provided is for Windows ('Work in Apache Hadoop on HDInsight from a Windows PC'), and there is no equivalent Linux or cross-platform guidance. Additionally, in the introduction, deployment methods are listed as 'Azure portal and other deployment methods like PowerShell, CLI and the .NET SDK', with PowerShell (a Windows-centric tool) mentioned before the cross-platform CLI, which may suggest a subtle Windows-first ordering.
Recommendations
- Add equivalent Linux/macOS guidance in the 'Next steps' section, such as 'Work in Apache Hadoop on HDInsight from a Linux PC' or a general 'Work in Apache Hadoop on HDInsight from any OS' guide.
- When listing deployment methods, mention cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools (e.g., PowerShell) to avoid implying Windows is the primary or preferred platform.
- Ensure that all platform-specific instructions or tools are paired with alternatives for other major platforms, or clarify when instructions are cross-platform.
- Consider reviewing linked articles (such as 'hdinsight-hadoop-windows-tools.md') to ensure Linux parity in tooling and documentation.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by consistently using Windows-style paths (e.g., C:\HD\HDexample) in all file and folder examples, and by referencing Windows directory structures (e.g., .VSCode\settings.json) without providing equivalent Linux/macOS examples. While there is a brief mention of Mono as a prerequisite for Linux/macOS and a single note about installing xclip on Linux, the step-by-step instructions, screenshots, and code samples overwhelmingly assume a Windows environment. There are no explicit Linux or macOS command examples, nor are alternative file paths or UI differences for those platforms discussed.
Recommendations
- For every file/folder path example, provide both Windows (e.g., C:\HD\HDexample) and Linux/macOS (e.g., /home/user/HD/HDexample) equivalents.
- When referencing configuration files (e.g., .VSCode\settings.json), mention the path format for both Windows and Linux/macOS (e.g., .vscode/settings.json).
- Include screenshots or notes highlighting any UI or shortcut differences on Linux/macOS, especially where menu navigation or keyboard shortcuts may differ.
- Add explicit step-by-step instructions or callouts for Linux/macOS users where the process diverges (e.g., Mono installation, permissions, terminal usage).
- Where relevant, mention any platform-specific prerequisites or troubleshooting tips beyond Mono and xclip (e.g., Python environment setup, file permissions).
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-linux-use-ssh-unix.md
...icles/hdinsight/hdinsight-hadoop-linux-use-ssh-unix.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally maintains cross-platform parity, but there is a subtle Windows bias in the ordering and emphasis of SSH client options. Windows-specific tools and installation instructions are given more prominence and detail, and Windows options are listed before Linux equivalents in some sections. However, Linux/Unix commands and workflows are well represented throughout, and most command-line examples use standard ssh/scp syntax applicable to all platforms.
Recommendations
- When listing SSH client options, mention Linux/Unix/macOS built-in support first, as these platforms natively include SSH, then follow with Windows installation instructions.
- Ensure that graphical SSH clients (e.g., PuTTY, MobaXterm) are not described as primary or default for Windows, but as alternatives, and clarify their cross-platform availability if relevant.
- Where PowerShell or Windows-specific command-line tools are referenced (e.g., New-AzHdinsightCluster), provide equivalent Linux/macOS CLI commands or note their parity.
- In authentication and SSH key generation sections, clarify that ssh-keygen and ssh-agent are available on all major platforms, including Windows (via OpenSSH or WSL), to reinforce parity.
- Review the order of presentation in all sections to avoid consistently mentioning Windows before Linux/Unix/macOS, as this subtly prioritizes the Windows experience.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for managing script actions, but PowerShell is consistently presented before CLI in all sections, and PowerShell code samples are more detailed and prominent. There are no Linux shell or Bash-based management examples (other than the Bash scripts themselves), and the .NET SDK is also highlighted, which is more common in Windows-centric environments. The CLI is covered, but with less emphasis and detail than PowerShell.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid implying PowerShell is the primary or preferred method.
- Ensure CLI code samples are as detailed and prominent as PowerShell samples.
- Consider including Bash or shell script examples for invoking REST APIs or managing clusters, especially for Linux users.
- Explicitly state that all management operations can be performed from Linux/macOS environments using the Azure CLI.
- Balance .NET SDK references with Python SDK or REST API examples, which are more cross-platform.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Azure PowerShell examples before Azure CLI examples in the main workflow for creating network security groups, which can be perceived as a 'Windows-first' approach. There is a detailed, multi-step PowerShell script, while the Azure CLI section is presented after and in a more step-by-step, fragmented manner. While Linux is acknowledged in the DNS configuration sections (with explicit Linux/BIND instructions), the primary workflow for network setup is biased toward Windows/PowerShell users.
Recommendations
- Present Azure CLI and PowerShell examples side-by-side or in parallel sections, rather than listing PowerShell first. This helps avoid the perception that Windows/PowerShell is the primary or preferred method.
- Ensure that CLI examples are as comprehensive and consolidated as the PowerShell examples, rather than being broken into many small steps.
- Add explicit notes that both Azure CLI and PowerShell are fully cross-platform and supported on Windows, Linux, and macOS.
- Consider providing Bash shell script examples for common Linux automation scenarios, especially for tasks like network setup.
- Where possible, clarify that Azure CLI is often the preferred tool for Linux users and can be used interchangeably with PowerShell for all documented tasks.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/includes/hdinsight-portal-management-selector.md
...sight/includes/hdinsight-portal-management-selector.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation lists Azure PowerShell and .NET SDK (both Windows-centric tools) before Azure CLI, which is cross-platform and more commonly used on Linux. There is no explicit mention of Linux-native tools or shell examples, and the ordering suggests a Windows-first approach.
Recommendations
- Reorder the options to list cross-platform tools (such as Azure CLI) before Windows-specific tools.
- Include explicit Linux shell (bash) examples or references where possible.
- Clarify in the text which tools are cross-platform and which are Windows-specific.
- Add links or sections for Linux-native administration methods if available.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-templeton-webhcat-debug-errors.md
...ght/hdinsight-hadoop-templeton-webhcat-debug-errors.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references Windows-centric tools (Azure PowerShell, Data Lake Tools for Visual Studio) as primary client-side interfaces for WebHCat, without mentioning Linux or cross-platform alternatives. This positions Windows tools as the default or preferred method for interacting with WebHCat, potentially excluding Linux users or those using non-Windows environments.
Recommendations
- Include examples or references to Linux-native tools (such as curl, wget, or Python scripts) for interacting with the WebHCat REST API.
- Mention cross-platform clients (e.g., Azure CLI, REST clients) alongside or before Windows-specific tools.
- Provide troubleshooting steps or configuration guidance that is not tied to Windows-only environments.
- Add explicit notes or sections for Linux/macOS users, ensuring parity in tool recommendations and usage patterns.
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 →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation navigation lists Windows-centric tools (PowerShell, .NET, Visual Studio) alongside cross-platform options, and places them before or at the same level as Linux-native tools. There is no explicit prioritization of Linux tools or mention of Linux command-line interfaces beyond Curl and Beeline, which are cross-platform.
Recommendations
- Ensure Linux-native tools (such as Bash scripts, SSH, or Linux CLI examples) are included and given equal prominence.
- Reorder the list to alternate or group by platform, or clearly indicate which tools are cross-platform.
- Add explicit Linux/Unix shell examples and documentation links, not just Windows-centric tools.
- Clarify in each tool's description which platforms are supported to help users identify relevant options.