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 651-675 of 867 flagged pages
Hdinsight
Enable Private Link on an Azure HDInsight cluster
...blob/main/articles/hdinsight/hdinsight-private-link.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation exhibits a moderate Windows bias. In the connectivity testing section, the only VM example provided uses Windows 10, with RDP as the access method and a checkbox for Windows licensing. The instructions for testing SSH access start from a Windows command prompt, implicitly assuming a Windows environment. PowerShell is mentioned before Azure CLI in the cluster creation step, and no explicit Linux/macOS VM example or SSH client guidance is provided. There are no references to Linux tools, and the workflow for Linux users is not described.
Recommendations
- Provide parallel examples for deploying a Linux VM (e.g., Ubuntu) in the client VNET, including SSH access instructions.
- Show how to test Ambari and SSH access from a Linux/macOS terminal, including browser and SSH client usage.
- List Azure CLI examples before or alongside PowerShell, and clarify that both Windows and Linux/macOS users can use the CLI.
- Avoid assuming Windows-only workflows (e.g., RDP, Windows licensing) and mention alternatives for Linux/macOS users.
- Add notes or sections highlighting cross-platform compatibility and any OS-specific considerations.
Create Pull Request
Hdinsight
Tutorial: Create an end-to-end ETL pipeline to derive sales insights in Azure HDInsight
...ain/articles/hdinsight/hdinsight-sales-insights-etl.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Bash and Azure CLI examples for most steps, but when it comes to triggering the Data Factory pipeline, it gives detailed PowerShell instructions first, with only a brief mention of the Azure portal as an alternative. There are no Linux-native or cross-platform CLI examples for this critical step, and Power BI Desktop (a Windows-only tool) is required for visualization, with no mention of alternatives for Linux/macOS users.
Recommendations
- Provide Azure CLI or REST API examples for triggering and monitoring Data Factory pipelines, not just PowerShell.
- Explicitly mention that Power BI Desktop is Windows-only, and suggest alternatives for Linux/macOS users, such as Power BI web or open-source BI tools.
- When listing options for triggering pipelines, present cross-platform methods (CLI, REST API, portal) before Windows-specific (PowerShell) methods.
- Wherever PowerShell is used, provide equivalent Bash or CLI commands for Linux/macOS users.
Hdinsight
Restrict access using Shared Access Signatures - Azure HDInsight
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-storage-sharedaccesssignature-permissions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, especially in the sections on creating SAS tokens and configuring HDInsight clusters. PowerShell is presented as the primary method, and Azure CLI examples use Windows (cmd.exe) variable syntax without providing equivalent bash/Linux syntax. There is no explicit Linux shell example for Azure CLI, and the creation/configuration steps for clusters are only shown in PowerShell, with no Linux-native alternatives. The Python and Ambari sections are cross-platform, but critical provisioning steps lack Linux parity.
Recommendations
- Provide Azure CLI examples using bash syntax (e.g., export VAR=VALUE) alongside Windows cmd.exe syntax.
- Include Linux shell (bash) equivalents for all Azure CLI commands, especially for variable assignment and file paths.
- Offer cluster creation/configuration examples using Azure CLI or ARM templates, which are cross-platform, not just PowerShell.
- Clearly indicate which commands/scripts are platform-specific and offer alternatives where possible.
- Reorder examples so that cross-platform or Linux-native methods are presented first or equally with Windows methods.
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
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page lists Azure PowerShell and .NET SDK (both Windows-centric tools) before Azure CLI, which is more cross-platform and commonly used on Linux/macOS. There is no explicit mention of Linux-native tools or Bash examples, and the PowerShell option is highlighted before CLI, suggesting a Windows-first approach. The lack of Linux-specific examples or guidance may create friction for non-Windows users.
Recommendations
- List Azure CLI before Azure PowerShell, as CLI is cross-platform and widely used on Linux/macOS.
- Include explicit mention of Bash or Linux shell options where relevant.
- Ensure that Linux/macOS users are guided to equivalent tools and documentation, such as Bash scripts or Linux command-line instructions.
- Balance the order and visibility of examples to avoid implying Windows is the primary or preferred environment.
Hdinsight
Use Apache Spark REST API to submit remote jobs to an Entra enabled HDInsight Spark cluster
...-entra-authentication/run-spark-jobs-using-rest-api.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently uses Windows command prompt syntax (cmd) for environment variables and file paths, and provides examples with Windows-style paths (e.g., C:\Temp\input.txt). There are no explicit Linux/macOS shell examples, nor guidance for adapting commands to non-Windows environments. The instructions and examples assume a Windows environment by default, which may create friction for Linux/macOS users.
Recommendations
- Add equivalent Linux/macOS shell examples (e.g., using export for environment variables, and POSIX-style file paths like /tmp/input.txt).
- When showing file paths, provide both Windows and Linux/macOS variants.
- Explicitly state how to adapt commands for Linux/macOS environments in each relevant section.
- Use generic shell syntax (e.g., $VARIABLE) alongside Windows syntax where environment variables are set.
- Note that cURL commands are cross-platform, but clarify any OS-specific differences in usage.
Hdinsight
What is Interactive Query in Azure HDInsight?
...eractive-query/apache-interactive-query-get-started.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias by prioritizing Windows-centric tools (Power BI, Visual Studio, Excel with Hive ODBC) in its examples and guidance. Linux-native tools (Beeline, Ambari Hive View) are mentioned, but Windows tools are listed first and described in greater detail. There are no explicit Linux/macOS-specific examples or instructions, and the use of Microsoft Hive ODBC and Visual Studio may exclude Linux/macOS users from some workflows.
Recommendations
- Include explicit examples for Linux/macOS users, such as using Beeline from a Linux terminal.
- Provide parity in tool recommendations, e.g., mention alternatives to Power BI and Visual Studio for non-Windows platforms (such as Apache Zeppelin, Jupyter Notebooks, or DBeaver).
- Reorder the examples so that cross-platform or Linux-native tools (Beeline, Ambari Hive View, Zeppelin) are listed before Windows-only tools.
- Clarify which tools are cross-platform and which are Windows-only, so users can quickly identify relevant options.
- Add instructions for connecting via JDBC/ODBC from Linux/macOS clients.
Hdinsight
Connect HDInsight Kafka cluster with client VM in different VNet on Azure HDInsight
...in/articles/hdinsight/kafka/connect-kafka-with-vnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Linux and Windows instructions for connecting a client VM to an HDInsight Kafka cluster in a different VNet. However, Windows-specific details (such as editing the hosts file at the Windows path and logging into Ambari with Windows credentials) are given more prominence and detail, especially in the 'Windows OS' section. The Linux section is shorter and lacks parity in step-by-step guidance for Kafka topic operations, which are shown in detail for Windows. Windows terminology and file paths are mentioned explicitly, while Linux equivalents are less emphasized.
Recommendations
- Ensure both Linux and Windows sections provide equivalent detail and step-by-step instructions for all operations, including Kafka topic creation, production, and consumption.
- Present Linux and Windows instructions side-by-side or in parallel sections, rather than Windows-first.
- Include explicit Linux commands for editing /etc/hosts and accessing Ambari, matching the detail given for Windows.
- Add Linux-specific troubleshooting tips and clarify any differences in network or DNS setup for Linux VMs.
- Use neutral language and avoid assuming Windows as the default platform.
Hdinsight
Enable automatic topic creation in Apache Kafka - Azure HDInsight
...les/hdinsight/kafka/apache-kafka-auto-create-topics.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation mentions configuring Kafka during cluster creation through PowerShell or Resource Manager templates, but does not provide equivalent Linux/macOS CLI examples (such as Azure CLI or Bash). PowerShell is referenced before any cross-platform alternatives, and no Linux-specific instructions or parity examples are given for cluster creation. The Ambari Web UI section is platform-neutral, but the initial mention of PowerShell and lack of Linux examples creates a Windows-first impression.
Recommendations
- Add Azure CLI and Bash examples for configuring Kafka during cluster creation, alongside the PowerShell example.
- Explicitly mention cross-platform tools (e.g., Azure CLI) before or alongside PowerShell.
- Clarify that Ambari Web UI and REST API are platform-neutral and accessible from any OS.
- Provide guidance or links for Linux/macOS users to achieve the same configuration steps.
Hdinsight
Connect to Kafka using virtual networks - Azure HDInsight
...es/hdinsight/kafka/apache-kafka-connect-vpn-gateway.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing only PowerShell-based setup instructions for Azure resources, with no equivalent Bash, Azure CLI, or Linux-native examples for critical steps. The initial resource creation, networking, and HDInsight cluster setup are exclusively shown in PowerShell, which is primarily used on Windows. While Azure CLI is briefly mentioned for retrieving node information, the main workflow is Windows-centric. There is no guidance for Linux/macOS users on how to perform these steps using their native tools, creating friction for non-Windows users.
Recommendations
- Provide full Azure CLI and/or Bash script equivalents for all PowerShell examples, especially for resource creation and configuration steps.
- Clearly indicate cross-platform options at the start of each major section, and link to Linux/macOS-specific guides where available.
- Ensure that instructions for installing and using VPN clients are platform-agnostic, or provide platform-specific subsections.
- Where PowerShell is used, add notes or sidebars explaining how Linux/macOS users can accomplish the same tasks.
- Consider reordering examples so that CLI/Bash and PowerShell are presented side-by-side, or alternate which comes first.
Hdinsight
Azure Toolkit for Eclipse: Create Scala apps for HDInsight Spark
...es/hdinsight/spark/apache-spark-eclipse-tool-plugin.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the section on running Spark Scala applications locally. It discusses the need for WinUtils.exe and setting the HADOOP_HOME environment variable, which are Windows-specific requirements. There is no mention of Linux/macOS equivalents or instructions for running locally on non-Windows platforms. The troubleshooting guidance and prerequisites for local execution are exclusively Windows-focused, with no parallel advice for Linux or macOS users.
Recommendations
- Add instructions for running Spark Scala applications locally on Linux and macOS, including any required environment variables or dependencies.
- Clarify that WinUtils.exe is only needed on Windows, and explain that Linux/macOS do not require this step.
- Provide troubleshooting steps or common issues for Linux/macOS users when running Spark locally.
- Ensure that examples and prerequisites for local execution cover all major platforms, not just Windows.
- Where platform-specific steps are needed, clearly label them and provide alternatives for other OSes.
Hdinsight
Azure Toolkit: Debug Apache Spark apps remotely - Azure HDInsight
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-intellij-tool-plugin-debug-jobs-remotely.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific instructions and tools (e.g., Notepad, WinUtils.exe, Cygwin) are mentioned explicitly and often before or instead of Linux/macOS equivalents. PowerShell is referenced for VPN setup, and the hosts file editing is described only for Windows. The workaround for WinUtils.exe is Windows-only, and there is no guidance for Linux/macOS users for these steps. While some steps (e.g., SSH, IntelliJ usage) are cross-platform, critical configuration and troubleshooting steps lack Linux/macOS parity.
Recommendations
- Provide explicit instructions for editing the hosts file on Linux/macOS (e.g., /etc/hosts with sudo and a text editor like nano or vi).
- Clarify that the WinUtils.exe workaround is only needed for Windows, and explain that Linux/macOS do not require this step.
- Include Linux/macOS alternatives for copying files (e.g., using native scp in the terminal, not Cygwin).
- Add VPN setup instructions using Azure CLI or portal for Linux/macOS users, not just PowerShell.
- Review all file path examples and provide Linux/macOS equivalents (e.g., forward slashes, home directories).
- Explicitly state cross-platform compatibility for IntelliJ and Azure Toolkit steps, and highlight any OS-specific differences.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page shows evidence of Windows bias by mentioning SQL Server Integration Services (SSIS) and its Azure Feature Pack as a method for running Pig jobs, which is a Windows-centric tool. There are no equivalent Linux/macOS integration examples or alternative tools suggested. The documentation also references Windows tools and patterns (SSIS) before any Linux-native options, and does not provide walkthroughs or examples for running Pig jobs from Linux/macOS environments or using common cross-platform tools (e.g., SSH, Bash, curl).
Recommendations
- Add examples and walkthroughs for running Pig jobs from Linux/macOS terminals, including using SSH and Bash.
- Mention cross-platform tools (e.g., curl, SSH) for job submission and management.
- Provide parity by listing Linux-native or cross-platform alternatives to SSIS for job orchestration (e.g., Apache Oozie, AzCopy, Azure CLI).
- Ensure that Windows-specific tools are not presented as the only or primary option, and balance their mention with Linux/macOS equivalents.
Hdinsight
Quickstart: Create Apache Hadoop cluster in Azure HDInsight using Bicep
...doop/apache-hadoop-linux-tutorial-get-started-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment and resource management, but PowerShell is given equal prominence to CLI, and is presented as a primary alternative rather than, for example, Bash or other Linux-native tools. There are no explicit Linux shell (bash) examples, and PowerShell is a Windows-centric tool, which may disadvantage Linux users. The documentation does not mention Linux-specific patterns or tools, and does not clarify that Azure CLI is cross-platform and preferred for Linux environments.
Recommendations
- Explicitly state that Azure CLI is cross-platform and preferred for Linux and macOS environments.
- Add bash-specific examples (e.g., using bash scripts to run Azure CLI commands) to demonstrate Linux-native workflows.
- Clarify that PowerShell is primarily for Windows users, and provide guidance for Linux users to use Azure CLI.
- Consider reordering examples to present Azure CLI (Linux-friendly) before PowerShell (Windows-centric), or add a note about platform suitability.
- Include troubleshooting or environment setup notes for Linux users, such as installing Azure CLI on Ubuntu or other distributions.
Hdinsight
Tutorial: Apache Spark Streaming & Apache Kafka - Azure HDInsight
...t/hdinsight-apache-kafka-spark-structured-streaming.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the section where users are instructed to gather Kafka host information. The example commands are written specifically for the Windows command prompt, using Windows-style environment variable syntax and referencing a Windows jq executable path. There is no equivalent Linux/macOS example provided, nor is there guidance for adapting the commands for Bash or other Unix shells. The rest of the tutorial is platform-neutral, focusing on Jupyter Notebook and Scala code, but the initial setup step may hinder Linux/macOS users.
Recommendations
- Provide equivalent Linux/macOS shell commands for gathering Kafka host information, using Bash syntax and typical jq installation paths.
- Add a note or table explicitly showing the differences in command syntax between Windows CMD and Bash shells.
- Reference jq installation instructions for Linux/macOS, not just Windows.
- Ensure all command-line examples are presented for both major platforms, or use platform-neutral syntax where possible.
Hdinsight
Optimize Hive queries in Azure HDInsight
...cles/hdinsight/hdinsight-hadoop-optimize-hive-query.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page displays mild Windows bias by mentioning Azure PowerShell and the Azure portal as primary tools for cluster management, with no explicit mention of Linux-native tools (such as Azure CLI on Bash, SSH, or scripting via Linux shells). The examples and screenshots focus on the Azure portal, which is platform-agnostic but often associated with Windows workflows. There are no explicit Linux command-line examples or references to Linux-specific management patterns, despite HDInsight clusters being Linux-based by default.
Recommendations
- Add explicit examples using Azure CLI commands for cluster creation and scaling, demonstrating usage on Linux/macOS terminals.
- Mention Linux-native management tools (e.g., SSH, Bash scripting) where relevant, especially for post-deployment operations.
- Balance references to Azure PowerShell with Azure CLI, and clarify that both can be used cross-platform.
- Include screenshots or walkthroughs for both Azure portal and command-line interfaces.
- Where possible, provide sample scripts for common operations in both PowerShell and Bash.
Hdinsight
How to get the host names of Azure HDInsight cluster nodes
...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/jq and PowerShell examples for retrieving host names via the Ambari REST API, but the PowerShell example is given immediately after the Bash example and references Windows-specific tools (ConvertFrom-Json, Invoke-WebRequest). There is a slight Windows-first bias in mentioning PowerShell and its tools alongside the cross-platform jq, and no Linux-specific command-line alternatives to PowerShell are discussed. The Ambari Web UI section does not show bias, as it is platform-agnostic.
Recommendations
- Explicitly mention that both Bash/jq and PowerShell examples are provided for cross-platform usage.
- Add Linux-specific instructions for authentication (e.g., using curl with --user or .netrc for credentials).
- Provide more detailed Linux shell examples, such as using wget or httpie as alternatives to curl.
- Clarify that jq is available on both Linux and Windows (via WSL or native installs), and offer installation guidance for both platforms.
- Consider listing the Bash/jq example first to emphasize Linux parity.
Hdinsight
Use Apache Hadoop Hive with Curl in HDInsight - Azure
...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/cURL and PowerShell/Invoke-WebRequest examples for all major steps, but PowerShell is consistently presented second, and Windows tools (Invoke-WebRequest, PowerShell credential pop-up) are described in detail. The Bash examples are present and functional, but some explanations and setup steps (such as credential handling) are more elaborate for Windows/PowerShell. The mention of Azure CLI for downloading results is cross-platform, but no explicit Linux-first or Linux-only instructions are given.
Recommendations
- Present Bash/cURL examples before PowerShell examples to avoid implicit Windows-first bias.
- Ensure explanations and setup instructions are equally detailed for both Bash and PowerShell, including credential management.
- Add explicit notes about running Bash examples on native Linux, not just WSL.
- Where possible, include troubleshooting or environment setup tips for Linux users (e.g., installing curl and jq).
- Clarify that Azure CLI is cross-platform and provide example commands for both Linux and Windows terminals.
Hdinsight
Create HBase clusters in a Virtual Network - Azure
...rticles/hdinsight/hbase/apache-hbase-provision-vnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates Windows bias by exclusively referencing the creation of a Windows Server VM when describing how to connect to the HBase cluster, without mentioning or providing instructions for creating a Linux VM. This is notable given that the HBase cluster itself is Linux-based. Additionally, the example for verifying connectivity uses the generic 'ping' command, but the VM creation instructions are Windows-specific, potentially leading Linux users to feel unsupported.
Recommendations
- Add parallel instructions and links for creating a Linux VM in Azure, such as referencing the 'Create a Virtual Machine Running Linux' documentation.
- Explicitly state that either Windows or Linux VMs can be used for connecting to the HBase cluster, and provide guidance for both.
- Ensure that command-line examples (e.g., ping, curl) are shown in the context of both Windows and Linux environments, clarifying any differences.
- Review other sections for similar platform-specific references and update them to maintain parity.
Hdinsight
Quickstart: Apache HBase & Apache Phoenix - Azure HDInsight
...les/hdinsight/hbase/apache-hbase-query-with-phoenix.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page shows mild Windows bias by presenting command-line examples using Windows command prompt syntax (e.g., 'cmd' code blocks for curl and ssh), and by referencing deletion via PowerShell before mentioning Azure CLI. There is a lack of explicit Linux shell examples for commands like curl and ssh, and no mention of Linux-specific tools or patterns, despite the prerequisites referencing SSH clients and Linux tutorials.
Recommendations
- Provide Linux/bash equivalents for all command-line examples, especially for curl and ssh commands (e.g., use '$' or 'bash' code blocks).
- When referencing deletion methods, mention Azure CLI and browser methods before PowerShell, or present all options equally.
- Explicitly state that commands work on both Windows and Linux, or note any platform-specific differences.
- Include instructions or notes for installing SQLLine and Phoenix client on Linux systems, if relevant.
- Ensure that examples and instructions do not assume a Windows environment unless necessary, and clarify any platform-specific requirements.
Hdinsight
HBase cluster replication in virtual networks - Azure HDInsight
...n/articles/hdinsight/hbase/apache-hbase-replication.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation generally focuses on Linux-based workflows (Ubuntu VMs, Bash scripts, Bind DNS setup, SSH usage), but there is a notable Windows bias in the section describing how to obtain the SSH utility. Windows tools and patterns are listed first and in more detail than their Linux equivalents, including Azure Cloud Shell, Bash on Ubuntu on Windows 10, Git for Windows, and OpenSSH for Windows. This could give the impression that Windows is the primary platform, despite the actual technical steps being Linux-centric.
Recommendations
- When listing SSH options, mention Linux/macOS first, as these platforms natively include SSH and are the default for most Hadoop/HBase deployments.
- Provide parity by listing Linux and macOS SSH instructions before Windows alternatives.
- If Windows tools are mentioned, ensure equivalent Linux instructions are present and given equal prominence.
- Consider adding explicit notes that all core steps (VM setup, Bind installation, script actions) are performed on Linux, and clarify that Windows instructions are only for users connecting from a Windows workstation.
- Review other sections to ensure that Linux tools and patterns are not overshadowed by Windows-specific recommendations.
Hdinsight
Open-source components and versions - Azure HDInsight
...n/articles/hdinsight/hdinsight-component-versioning.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely neutral and Linux-centric in its technical content, as all supported HDInsight clusters use Ubuntu as the VM OS. However, there is a subtle Windows bias in the 'Next steps' section, where a link to 'Work in Apache Hadoop on HDInsight from a Windows PC' is listed, and no equivalent Linux/macOS guidance is provided. Additionally, in the introduction, 'PowerShell' is mentioned as a deployment method before 'CLI', which may suggest a Windows-first perspective.
Recommendations
- Add equivalent links or guidance for working with HDInsight from Linux and macOS clients in the 'Next steps' section.
- When listing deployment methods, mention cross-platform tools (such as Azure CLI) before or alongside Windows-specific tools like PowerShell.
- Ensure that any tooling or workflow guidance is provided for all major platforms, not just Windows.
- Review linked pages (e.g., 'hdinsight-hadoop-windows-tools.md') to ensure Linux/macOS parity or provide alternative links.
Hdinsight
Authorize users for Ambari Views - Azure HDInsight
...icles/hdinsight/hdinsight-authorize-users-to-ambari.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both PowerShell (Windows) and curl/bash (Linux/macOS) examples for adding users to Ambari, but the PowerShell example is presented first and in greater detail. There is a slight Windows-first bias in the ordering and depth of scripting examples, with PowerShell receiving more explanation and code comments. The curl/bash example is present and functional, but is described as requiring 'slight modifications' for Windows, implying Linux is not the primary platform. No Linux-specific tools or patterns (e.g., shell scripts, Linux CLI utilities) are discussed beyond curl, and no Linux desktop screenshots or instructions are given.
Recommendations
- Present Linux/bash and Windows/PowerShell examples side-by-side, or alternate which comes first to avoid implicit prioritization.
- Provide equal detail and commentary for both PowerShell and bash/curl examples, including error handling and output verification.
- Explicitly mention Linux as a supported platform in introductory sections, and clarify which instructions apply to Linux, macOS, and Windows.
- Include Linux-specific troubleshooting tips or references to common Linux tools (e.g., wget, jq) where appropriate.
- Add screenshots or instructions for Linux desktop environments if relevant to the Ambari UI access steps.
Hdinsight
Create virtual networks for Azure HDInsight clusters
...articles/hdinsight/hdinsight-create-virtual-network.md
Medium Priority
View Details →
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 given before CLI, and the PowerShell script is more detailed. There is an implicit Windows-first bias in the ordering and depth of examples. However, Linux is acknowledged in the DNS configuration section, and CLI examples are present, which are cross-platform. No explicit Windows-only tools or patterns are used, and Linux-specific instructions are included for DNS setup.
Recommendations
- Present Azure CLI examples before PowerShell, or interleave them to emphasize parity.
- Ensure both PowerShell and CLI examples are equally detailed and comprehensive.
- Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Add Bash shell script examples where appropriate, especially for Linux users.
- Highlight Linux usage in the prerequisites and throughout the document, not just in DNS sections.
- Consider a table or side-by-side format for PowerShell and CLI commands to reinforce equal support.
Hdinsight
Azure HDInsight for Visual Studio Code
...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 bias primarily by presenting Windows-specific paths (e.g., C:\HD\HDexample) as the default in examples and instructions, without providing equivalent Linux/macOS paths. The workflow for opening folders and files uses Windows conventions exclusively, and there are no Linux/macOS command-line or file path examples. Linux is mentioned only in passing (e.g., Mono prerequisite, xclip for clipboard), but not in core usage instructions or code samples.
Recommendations
- Provide parallel examples for Linux/macOS, such as using ~/HD/HDexample or /home/user/HDexample for file paths.
- Explicitly mention how to perform folder and file operations on Linux/macOS, including screenshots if possible.
- Add notes or tables summarizing differences in prerequisites and setup steps between Windows, Linux, and macOS.
- Ensure that all code and workflow examples include both Windows and Linux/macOS variants where relevant.
- Highlight any platform-specific limitations or features, and offer workarounds for non-Windows users.
Hdinsight
Customize Azure HDInsight clusters by using script actions
.../hdinsight/hdinsight-hadoop-customize-cluster-linux.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples and guidance for using script actions in Azure HDInsight clusters, but consistently lists Windows-centric tools (Azure PowerShell, .NET SDK) before Linux-friendly options (Azure CLI, REST API). PowerShell examples are more detailed and appear before CLI examples, and output snippets use PowerShell cmdlets. There is a lack of parity in example depth and order, favoring Windows tools and workflows.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to better support Linux users.
- Expand CLI examples to match the detail and output shown in PowerShell sections.
- Include REST API and Bash scripting examples where appropriate, especially for automation scenarios.
- Clarify that script actions are Bash scripts and highlight Linux-native workflows and tools.
- Balance the order of tool presentation (CLI, PowerShell, SDK) to avoid implicit prioritization of Windows tools.
- Add troubleshooting and usage notes specific to Linux environments.