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 676-700 of 867 flagged pages
Hdinsight
Query data from HDFS-compatible Azure storage - Azure HDInsight
...rticles/hdinsight/hdinsight-hadoop-use-blob-storage.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows Only Example
Summary
The documentation page generally maintains cross-platform parity, especially in its examples, which are based on SSH and Linux commands. However, in the 'Access files from outside cluster' section, the list of Microsoft-provided tools includes Azure PowerShell as a Windows-only option, and AzCopy is noted as available for Windows and Linux but not OS X. No Linux-specific tools (e.g., native hadoop/hdfs CLI, sftp, or third-party Linux utilities) are mentioned, nor are there examples for Linux-specific workflows outside of the cluster context. The ordering of tools does not show explicit Windows-first bias, but the inclusion of Azure PowerShell as a Windows-only tool and lack of Linux alternatives in that row is a mild Windows bias.
Recommendations
- Add examples or mention of Linux-native tools for accessing Azure Storage outside the cluster, such as sftp, curl, or third-party utilities.
- Include notes or links to Linux equivalents for PowerShell workflows, such as using Azure CLI or REST API from bash.
- Clarify that most examples are Linux-based and provide parity by offering any Windows-specific command-line examples (e.g., PowerShell, CMD) where relevant.
- Consider reordering or grouping tools by platform support rather than listing Windows-only tools in the same table as cross-platform tools.
- Explicitly state that the main workflow examples (SSH, hdfs dfs, Hive) are Linux-based, and provide guidance for Windows users if needed.
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 →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page lists Windows-centric tools (.NET, PowerShell, Visual Studio) alongside platform-neutral or Linux-friendly options (Beeline, Curl), but Windows tools are mentioned before their Linux equivalents and receive equal or greater prominence. There is no explicit Linux example or mention of Linux-specific tools (e.g., Bash scripting, Linux IDEs), and the ordering may suggest a Windows-first bias.
Recommendations
- Add explicit Linux examples and tools, such as Bash scripting or Linux IDEs (e.g., VS Code on Linux).
- Reorder the list to alternate or group platform-neutral and platform-specific options, ensuring Linux-friendly tools are not overshadowed.
- Include notes or sections highlighting how to use Hive with common Linux environments.
- Provide parity in depth and detail for Linux and Windows examples in linked documentation.
Hdinsight
Quickstart: Create Interactive Query cluster using Bicep - Azure HDInsight
...ticles/hdinsight/interactive-query/quickstart-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 deploying and managing resources, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and is always listed second. There are no explicit Linux-specific instructions or examples (e.g., Bash scripting, Linux package installation), nor is there mention of Linux-native tools. However, the use of Azure CLI is cross-platform, and the instructions do not require Windows-only tools. The documentation does not show explicit bias in tool choice, but the inclusion of PowerShell examples and terminology may subtly favor Windows users.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and recommend CLI as the default for cross-platform usage.
- Add explicit notes or examples for running commands in Bash or other Linux shells, especially for Linux users.
- Consider listing CLI examples before PowerShell, or grouping PowerShell as an alternative for Windows users.
- If relevant, mention installation steps for Azure CLI on Linux.
- Avoid assuming PowerShell is available on all platforms; clarify platform requirements for PowerShell examples.
Hdinsight
Quickstart: Create Apache Spark cluster using Bicep - Azure HDInsight
...dinsight/spark/apache-spark-jupyter-spark-use-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, resource review, and cleanup, but PowerShell (a Windows-centric tool) is consistently presented as an equal alternative to CLI, and sometimes appears before or alongside CLI. There are no Linux-specific shell examples (e.g., Bash scripts), nor is there mention of Linux-native tools or workflows. The documentation does not reference Linux-specific patterns or troubleshooting, and the use of PowerShell may imply a Windows bias, especially for users unfamiliar with it.
Recommendations
- Explicitly state that Azure CLI commands work natively on Linux, macOS, and Windows, while PowerShell is primarily for Windows (though available cross-platform).
- Provide Bash script examples for Linux users, especially for steps involving file manipulation or automation.
- Clarify prerequisites for running PowerShell on non-Windows platforms, or link to installation instructions for PowerShell Core on Linux/macOS.
- Add troubleshooting notes or tips relevant to Linux environments (e.g., file permissions, SSH key generation).
- Consider listing CLI (Bash) examples before PowerShell to reflect the cross-platform nature of Azure CLI.
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 consistently lists PowerShell (Windows) examples before Bash (Linux) ones. The REST client prerequisite mentions Windows PowerShell first, and PowerShell code is presented before Bash in every example block. There is a slight bias toward Windows tooling and workflow, with more detailed PowerShell credential handling and commentary. However, Linux examples are present and functional throughout.
Recommendations
- Alternate the order of Bash and PowerShell examples so that Linux/Bash is presented first in some sections.
- Explicitly state that both Windows and Linux are fully supported and encourage users to choose their preferred platform.
- Provide equal detail and commentary for Bash examples, especially regarding credential handling and troubleshooting.
- Consider adding a summary table comparing Bash and PowerShell commands for quick reference.
- Ensure that any referenced tools (like jq) are explained as thoroughly as their Windows counterparts.
Hdinsight
Quickstart: Query Apache HBase in Azure HDInsight - HBase Shell
...ticles/hdinsight/hbase/query-hbase-with-hbase-shell.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by presenting the SSH connection example using the Windows command prompt syntax (`cmd`) and not providing a Linux or macOS equivalent. The SSH client prerequisite links to a general SSH guide, but the example command is shown in a Windows context. No PowerShell-specific commands or Windows-only tools are mentioned, but the lack of explicit Linux/macOS examples may disadvantage non-Windows users.
Recommendations
- Provide SSH connection examples for both Windows (cmd/PowerShell) and Linux/macOS (terminal/bash).
- Clarify that the SSH command works across platforms and mention platform-specific nuances if any.
- Include references or links to platform-specific SSH client installation guides (e.g., PuTTY for Windows, OpenSSH for Linux/macOS).
- Ensure that all command examples are shown in a cross-platform manner, or explicitly state their applicability.
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 demonstrates mild Windows bias by mentioning Windows-specific tools (Azure PowerShell) and the Azure portal before Linux alternatives (command-line interface) when describing cluster scaling. No explicit Linux shell examples are provided, and screenshots exclusively show the Azure portal, which is platform-agnostic but often associated with Windows usage. However, the rest of the content is platform-neutral and references Linux clusters positively (e.g., Tez enabled by default).
Recommendations
- Provide explicit Linux shell (bash/CLI) examples alongside or before PowerShell examples for cluster management tasks.
- Clarify that the Azure portal and CLI are cross-platform, and include links or instructions for Linux users.
- Add screenshots or command snippets demonstrating cluster scaling using Azure CLI on Linux.
- Ensure that any references to PowerShell are balanced with equivalent bash/CLI instructions.
- Highlight Linux-specific advantages (such as Tez being enabled by default) more prominently.
Hdinsight
Cluster management best practices - Azure HDInsight
...rticles/hdinsight/cluster-management-best-practices.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation lists Azure PowerShell as a primary method for cluster creation and management, placing it alongside Azure CLI and other cross-platform tools. However, PowerShell is mentioned before cURL and SDKs, and there is no explicit mention of Linux shell scripting or Bash examples. The documentation does not provide Linux-specific command-line examples or highlight Linux-native tools, which may suggest a subtle Windows bias.
Recommendations
- Add explicit Bash or Linux shell examples for cluster management tasks, especially for creation and customization.
- Ensure that Linux-native tools (e.g., Bash, SSH, SCP) are mentioned and demonstrated alongside or before PowerShell where appropriate.
- Clarify cross-platform compatibility for each tool, indicating which are best suited for Linux environments.
- Consider reordering examples so that cross-platform or Linux-first tools (Azure CLI, Bash, cURL) are listed before Windows-centric tools like PowerShell.
- Provide links to Linux-specific documentation or tutorials where available.
Hdinsight
Cluster creation fails with DomainNotFound error in Azure HDInsight
...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 references Windows-specific tools and patterns (e.g., using the Control Panel UI for domain join). While Linux (Ubuntu) steps are included, the ordering and detail favor Windows, and there is no mention of Linux-native troubleshooting tools or commands beyond running a provided script.
Recommendations
- Present Linux (Ubuntu) troubleshooting steps before or alongside Windows steps to avoid implicit prioritization.
- Provide equivalent Linux-native troubleshooting commands (e.g., using realm, net ads join, or samba-tool) and explain their usage.
- Include references to Linux tools for DNS and domain join verification (e.g., dig, nslookup, realm list).
- Clarify that both Windows and Linux VMs can be used for troubleshooting, and provide parity in detail and guidance for both platforms.
Hdinsight
Apache Ambari heartbeat issues in Azure HDInsight
.../hadoop/apache-ambari-troubleshoot-heartbeat-issues.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation provides troubleshooting steps for Apache Ambari heartbeat issues in Azure HDInsight. While most examples use Linux commands (ps, top, service), the section on disabling Azure Monitor logging references only the PowerShell cmdlet Disable-AzHDInsightMonitoring, which is Windows-centric and does not mention an equivalent Bash/CLI command. No Linux or cross-platform alternatives are provided for this step, and the use of PowerShell is presented as the default approach.
Recommendations
- Include Azure CLI or Bash script equivalents for disabling Azure Monitor logging (e.g., az hdinsight monitoring disable).
- Clarify whether the PowerShell cmdlet can be run from Linux/macOS via Azure Cloud Shell or provide instructions for those platforms.
- Add explicit notes or examples for Linux users in all sections where a Windows/PowerShell tool is referenced.
- Ensure parity by listing Linux/CLI methods before or alongside PowerShell/Windows methods.
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 (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 is more detailed, including credential handling. The mention of ConvertFrom-Json links to PowerShell documentation, while jq is referenced only briefly. There is no explicit Linux tool parity discussion, and the Bash example lacks credential input guidance compared to PowerShell.
Recommendations
- Provide equal detail for both Bash and PowerShell examples, including credential handling for Bash (e.g., using read -s for password input).
- Mention Linux tools (such as curl and jq) with links to their documentation, similar to how PowerShell cmdlets are linked.
- Consider listing Linux/Bash examples first if the majority of HDInsight clusters run on Linux.
- Add a note on cross-platform usage, clarifying which examples apply to which OS and how to adapt them.
- Include troubleshooting tips for both Bash and PowerShell users, ensuring parity in guidance.
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, resource review, and cleanup. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented as a primary method alongside CLI, rather than as a secondary or alternative. There is no explicit mention of Linux shell scripting or native Linux tools, nor are there examples tailored for Linux users (e.g., bash scripts, environment setup notes for Linux). The documentation does not clarify that Azure CLI is cross-platform and preferred for Linux/macOS users, which may subtly reinforce a Windows/PowerShell bias.
Recommendations
- Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users, while PowerShell is primarily for Windows.
- Present Azure CLI examples before PowerShell examples to reinforce CLI as the default, especially for non-Windows platforms.
- Add a note or section on how to install and use Azure CLI on Linux/macOS, including any prerequisites.
- Consider removing PowerShell examples from the main flow and placing them in a separate 'Windows users' section, or clearly label them as Windows-specific.
- Include troubleshooting or environment setup tips for Linux users, such as SSH key generation or bash usage.
Hdinsight
MapReduce with Apache Hadoop on HDInsight
...n/articles/hdinsight/hadoop/hdinsight-use-mapreduce.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page lists Windows PowerShell as a dedicated method for submitting MapReduce jobs, with a specific walkthrough link, while Linux/Unix/macOS users are directed to more generic SSH and Curl methods. The table highlights Windows PowerShell as a distinct Windows-only tool, and Windows is mentioned explicitly as a client OS for all methods. There are no Linux-specific tools (e.g., Bash scripts, Linux command-line utilities) or examples given, and Windows tooling is presented as a primary option for remote job submission.
Recommendations
- Add Linux-specific examples, such as using Bash scripts or Linux command-line utilities to submit MapReduce jobs.
- Provide parity in tooling walkthroughs: if there is a dedicated PowerShell guide, offer a dedicated Bash or shell script guide for Linux/macOS.
- Avoid presenting Windows tools (PowerShell) as the only or primary remote submission method; ensure Linux methods are equally highlighted.
- Include explicit Linux command examples for running MapReduce jobs, not just generic SSH or Curl references.
- Clarify that all methods are cross-platform where applicable, and avoid segregating Windows tooling unless there is a unique capability.
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 provides host information retrieval commands specifically for Windows command prompt, with explicit instructions and syntax tailored to Windows (e.g., use of REM, set, and referencing jq-win64.exe). It notes that 'slight variations will be needed for other environments' but does not provide Linux/macOS equivalents. This prioritizes Windows and leaves Linux users to adapt on their own, which is a form of Windows-first bias and missing Linux example.
Recommendations
- Provide equivalent Linux/macOS command examples alongside Windows commands, including syntax for environment variable setting (e.g., export), path to jq (e.g., /usr/bin/jq), and shell comments (#).
- Explicitly mention the differences in command syntax between Windows and Linux/macOS, and offer guidance or links to resources for adapting commands.
- Consider presenting Linux/macOS examples first, or in parallel, to avoid implicit prioritization of Windows.
- Ensure all tooling references (such as jq) include installation instructions for both Windows and Linux/macOS.
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 page exhibits Windows bias primarily in the 'Create a virtual machine' section, where instructions link only to creating a Windows Server VM, with no mention or example for creating a Linux VM. This may lead users to assume Windows is the preferred or only option, despite the cluster itself being Linux-based. There are no PowerShell-heavy examples or exclusive use of Windows tools, but the ordering and omission of Linux VM instructions are notable.
Recommendations
- Add parallel instructions and links for creating a Linux-based virtual machine in the same Azure virtual network and subnet.
- Explicitly mention that either Windows or Linux VMs can be used for client connectivity, depending on user preference and application requirements.
- Ensure that examples and references do not implicitly prioritize Windows unless there is a technical reason.
- Review other sections for similar omissions and provide Linux parity where appropriate.
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 exhibits a mild Windows bias by presenting command-line examples using Windows Command Prompt syntax (e.g., 'cmd' code blocks for curl and ssh) and referencing deletion via PowerShell before mentioning Azure CLI. There are no explicit Linux shell examples for curl or ssh, and Linux tools/patterns are not highlighted. The SSH client prerequisite links to a Linux SSH guide, but the actual commands use Windows syntax, which may confuse Linux users.
Recommendations
- Provide both Windows and Linux/macOS command examples for curl and ssh, using appropriate shell syntax (e.g., Bash for Linux/macOS).
- When referencing cluster deletion, mention Azure CLI and browser methods before PowerShell, or present all options equally.
- Use generic code blocks (not 'cmd') for commands that are cross-platform, or provide separate tabs for Windows and Linux/macOS.
- Clarify any platform-specific steps or differences, especially for installing and running SQLLine on non-Windows systems.
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 provides guidance for both Linux and Windows users, but there is a subtle Windows bias in the section describing how to obtain the SSH utility. Windows tools and patterns (Azure Cloud Shell, Bash on Ubuntu on Windows 10, Git for Windows, OpenSSH for Windows) are listed explicitly and in detail, while Linux, Unix, and macOS are mentioned only briefly as having SSH 'provided as part of the operating system.' The Windows options are given more space and appear before Linux alternatives, which may suggest a Windows-first orientation.
Recommendations
- Present Linux, macOS, and Windows instructions with equal detail and prominence.
- List Linux/Unix/macOS SSH usage first, followed by Windows options, or group them together without prioritization.
- Include explicit Linux command-line examples for all relevant steps, and ensure parity in troubleshooting and tool recommendations.
- Where Windows-specific tools are mentioned, provide equivalent Linux/macOS alternatives (e.g., mention PuTTY for Windows and OpenSSH for Linux/macOS).
- Review all example commands and ensure they are cross-platform, or provide platform-specific variants as needed.
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 examples for adding users to Ambari using both PowerShell and curl/bash. However, the PowerShell example is presented before the Linux-friendly curl/bash example, and the PowerShell section is more detailed and prominent. This ordering and emphasis may suggest a bias towards Windows users and workflows, especially since PowerShell is primarily a Windows tool (though available on Linux, it is far less common in Linux environments). There are no Linux-specific CLI examples (e.g., using native Linux tools or shell scripts beyond curl), and the documentation does not mention Linux-first patterns or tools.
Recommendations
- Present Linux/bash/curl examples before PowerShell examples to better support Linux users, who are the majority for Apache Ambari/Hadoop.
- Add native Linux CLI examples (e.g., using wget, shell scripts, or Ambari CLI if available) to improve parity.
- Clearly indicate that PowerShell is available on Linux, but is not the default shell, and provide guidance for Linux users.
- Ensure that any Windows-specific instructions are matched with Linux equivalents, and avoid assuming Windows as the default environment.
- Consider adding a table or section comparing Windows and Linux approaches for common tasks.
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-focused in its main content, as all supported HDInsight versions use Ubuntu as the VM OS. However, there is evidence of Windows bias in the 'Next steps' section, where a link specifically highlights working with HDInsight from a Windows PC and references Windows tools before any Linux equivalents. Additionally, in the section listing deployment methods, 'PowerShell' is mentioned before 'CLI', which may subtly prioritize Windows tooling.
Recommendations
- In the 'Next steps' section, provide parallel guidance for Linux and macOS users, such as a link to a page about working with HDInsight from Linux or cross-platform tools.
- When listing deployment methods (e.g., 'PowerShell, CLI, and .NET SDK'), consider listing the Azure CLI first, as it is cross-platform, or clarify that all tools are available on multiple operating systems.
- If referencing Windows-specific tools or workflows, ensure Linux equivalents are mentioned with equal prominence and provide links to relevant documentation.
- Review other documentation pages linked from this one (such as 'hdinsight-hadoop-windows-tools.md') to ensure Linux parity in tooling and examples.
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 Azure PowerShell examples before Azure CLI examples in the key network security group (NSG) configuration section, which may suggest a Windows-first bias. The PowerShell section is more detailed and extensive, with full scripts, while the Azure CLI section is broken into stepwise commands. There are no Linux shell (bash) or cross-platform scripting examples for NSG configuration. However, the DNS configuration and network validation sections do acknowledge Linux and provide Linux-centric instructions.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Provide bash shell script examples for NSG configuration, leveraging Azure CLI, to improve parity for Linux users.
- Explicitly mention that Azure CLI works on Windows, macOS, and Linux, and encourage its use for cross-platform scenarios.
- Balance the detail level between PowerShell and CLI examples, ensuring both are equally comprehensive.
- Consider adding a table or section comparing PowerShell and CLI usage for common tasks, highlighting cross-platform options.
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 shows a Windows bias by consistently using Windows-style paths (e.g., C:\HD\HDexample) in all examples and instructions, without providing equivalent Linux/macOS examples (e.g., /home/user/HDexample). The only explicit Linux-specific mention is the requirement to install Mono and xclip, but these are presented as side notes rather than integrated into the main workflow. There are no Linux or macOS command-line examples, nor are Linux file system conventions shown alongside Windows ones.
Recommendations
- Provide parallel examples for Linux/macOS, such as using /home/user/HDexample or ~/HDexample in folder instructions.
- Include notes or sections that clarify how steps differ on Linux/macOS, especially for file paths and environment setup.
- Show screenshots or terminal commands from Linux/macOS environments where relevant.
- Mention Linux/macOS keyboard shortcuts if they differ from Windows.
- Highlight any platform-specific limitations or differences in the main workflow, not just in side notes.
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 both Azure PowerShell and Azure CLI, but PowerShell (a Windows-centric tool) is consistently mentioned before CLI, and PowerShell examples are more detailed and prominent. The CLI is covered, but with less depth and fewer example outputs. There is a slight 'Windows-first' ordering in tool presentation, and PowerShell cmdlets are shown with output samples, while CLI commands are not. There are no explicit Linux tool examples (e.g., Bash scripts run locally, SSH usage), and the .NET SDK (Windows-oriented) is also highlighted.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Provide equally detailed example outputs for Azure CLI commands as for PowerShell.
- Include examples of running Bash scripts locally on Linux or via SSH, to show Linux-native workflows.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Add troubleshooting and usage notes specific to Linux environments where relevant.
- Ensure parity in documentation depth between PowerShell and CLI sections.
Hdinsight
Query data from HDFS-compatible Azure storage - Azure HDInsight
...rticles/hdinsight/hdinsight-hadoop-use-blob-storage.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates mild Windows bias in the section 'Access files from outside cluster', where Windows-specific tools (Azure PowerShell, AzCopy for Windows) are listed, and Azure PowerShell is only available for Windows. Additionally, the table lists Windows as a supported platform for AzCopy before mentioning Linux, and Azure PowerShell is presented as a primary tool despite its lack of Linux support. However, most command-line examples use Linux/Unix conventions (ssh, bash, hdfs dfs), and the overall documentation is generally cross-platform.
Recommendations
- Provide equivalent Linux-native examples for all tools, especially where Windows-only tools like Azure PowerShell are mentioned.
- Explicitly mention Linux alternatives for Azure PowerShell tasks, such as using Azure CLI or REST API.
- Ensure that tool tables do not prioritize Windows tools or list Windows before Linux when both are supported.
- Add more Linux-focused usage scenarios and clarify when a tool is Windows-only.
- Consider including sample scripts for Linux environments where possible, especially for tasks currently only demonstrated with Windows tools.
Hdinsight
Use Livy Spark to submit jobs to Spark cluster on Azure HDInsight
...es/hdinsight/spark/apache-spark-livy-rest-interface.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting all environment variable and file path examples using Windows syntax (e.g., set, C:\Temp\input.txt) and explicitly stating that the example is based on a Windows environment. There are no Linux or macOS equivalents provided for environment variable setting or file path usage, and recommendations for Linux users are absent. While the main tool (curl) is cross-platform, the examples and instructions are tailored to Windows users.
Recommendations
- Provide parallel Linux/macOS examples for environment variable setting (e.g., export clustername=CLUSTERNAME) and file paths (e.g., /tmp/input.txt).
- Add notes or sections explicitly addressing Linux/macOS usage, including differences in shell commands and file path conventions.
- When recommending approaches (such as using an input file), clarify how this would be done on Linux/macOS.
- Ensure that instructions and examples do not assume a Windows environment by default, or present both Windows and Linux/macOS options side-by-side.
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 →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page lists both Windows (Azure PowerShell) and Linux-friendly (Azure CLI, cURL) tools for cluster creation and management. However, Azure PowerShell is mentioned as a distinct option, and Windows tools are referenced before Linux equivalents in some cases. There is a slight bias towards Windows tooling, but Linux options are present and documented.
Recommendations
- Ensure that Linux-friendly tools (Azure CLI, cURL) are listed before or alongside Windows tools (Azure PowerShell) to avoid perceived prioritization.
- Provide explicit Linux shell examples (bash/zsh) where PowerShell examples are given, ensuring parity in code samples.
- Add notes clarifying cross-platform compatibility for each tool, especially for Azure CLI and PowerShell.
- Where possible, include screenshots or walkthroughs for both Windows and Linux environments.