Hdinsight
878
Total Pages
777
Linux-Friendly Pages
101
Pages with Bias
11.5%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
200 issues found
Showing 126-150 of 200 flagged pages
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/Azure CLI and PowerShell options for triggering the Azure Data Factory pipeline, but PowerShell is the only scripted example for programmatic pipeline execution. Power BI Desktop, a Windows-only tool, is used exclusively for visualization, with no mention of cross-platform alternatives. The PowerShell method is described before the portal method, and there are no Linux/macOS equivalents for programmatic pipeline triggering or visualization.
Recommendations
- Provide a Bash/Azure CLI example for triggering Data Factory pipelines programmatically, such as using the Azure CLI or REST API from Linux/macOS.
- Mention and, if possible, provide steps for using Power BI web service or other cross-platform visualization tools (e.g., Apache Superset, Tableau Public) for users who do not have access to Power BI Desktop.
- Present portal-based (browser) methods before platform-specific (PowerShell) methods to avoid implicit Windows-first bias.
- Explicitly state platform requirements for Power BI Desktop and suggest alternatives for non-Windows users.
Create Pull Request
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 Windows bias by prioritizing Microsoft-centric tools such as Power BI, Visual Studio, and Hive ODBC (Excel) in the examples and tool recommendations. These tools are either Windows-only or have limited support on Linux/macOS. Linux-native options like Beeline and Ambari Hive View are mentioned, but appear later in the list and lack detailed Linux-specific guidance or parity in example depth. There are no explicit Linux/macOS usage examples or instructions, and the focus on Windows tools may create friction for non-Windows users.
Recommendations
- Provide explicit Linux/macOS usage examples for connecting to Interactive Query, such as using Beeline from a Linux shell.
- Include instructions for installing and using cross-platform tools (e.g., Beeline, JDBC) on Linux/macOS.
- Reorder the list of tools to present cross-platform and open-source options first, followed by Windows-specific tools.
- Mention alternatives to Power BI and Visual Studio for Linux/macOS users, such as Apache Zeppelin, DBeaver, or other BI tools.
- Clarify which tools are Windows-only and which are cross-platform.
Hdinsight
Quickstart: Apache Hive in Azure HDInsight with Apache Zeppelin
...t/interactive-query/hdinsight-connect-hive-zeppelin.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references Windows-centric tools (Visual Studio, PowerShell) for next steps and cluster deletion, and highlights Visual Studio integration before any Linux/macOS alternatives. There are no explicit Linux/macOS examples or tool recommendations, and PowerShell is mentioned as a deletion method without parity for Bash or Linux-native tools.
Recommendations
- Include examples or references for deleting clusters using Bash/Azure CLI on Linux/macOS.
- Provide next steps for running Hive queries using cross-platform tools (e.g., VS Code, command-line Hive, or Zeppelin on Linux/macOS).
- Mention Linux/macOS alternatives alongside Windows tools, not just after or as an afterthought.
- Clarify that Zeppelin and Hive are cross-platform and can be accessed from any OS with a browser.
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 relies heavily on Azure PowerShell for all resource creation and configuration steps, with no equivalent Bash, Azure CLI, or Linux-native instructions for these critical tasks. Windows/PowerShell examples are presented first and exclusively in most sections, especially for cluster setup and networking. While the Python client example is cross-platform, the initial steps to create and configure the environment are Windows-centric, creating friction for Linux/macOS users.
Recommendations
- Provide equivalent Azure CLI and/or Bash scripts for all PowerShell-based instructions, especially for resource group, network, storage, and HDInsight cluster creation.
- Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI, and link to relevant CLI documentation.
- Where PowerShell is used for querying resources (e.g., node IP addresses), provide Azure CLI alternatives and show both examples side-by-side.
- Clarify that the Python client code is platform-agnostic and can be run from any OS.
- Add a section or callout for Linux/macOS users, summarizing the recommended workflow and tools.
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
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 host file location and Ambari login steps) are given more prominence and detail, and Windows instructions are presented after Linux but with more step-by-step guidance. There is also a notable emphasis on Windows tools and patterns (e.g., referencing the Windows hosts file path, Windows Ambari login flow, and screenshots). Linux instructions are present but less detailed, and there is no mention of PowerShell, but the overall pattern favors Windows environments.
Recommendations
- Provide equally detailed step-by-step instructions for Linux users, including screenshots of Linux Ambari login and host file editing.
- Mention Linux tools and patterns (such as using nano/vim for editing /etc/hosts) alongside Windows equivalents.
- Ensure that troubleshooting and common issues for Linux/macOS are covered, not just Windows.
- Present Linux and Windows instructions in parallel sections, or clearly label them for parity.
- Include explicit macOS instructions for host file editing and Ambari access, if relevant.
Hdinsight
Configure service endpoint policies - Azure HDInsight
...b/main/articles/hdinsight/service-endpoint-policies.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring service endpoint policies, but the CLI example is written using PowerShell syntax and variable assignment, which is Windows-centric. The PowerShell example is given in full, while there is no explicit Bash/Linux shell example for Azure CLI usage. The variable assignment and scripting patterns shown are tailored for Windows/PowerShell users, making it less approachable for Linux/macOS users who would use Bash. There is no mention or demonstration of how to perform the same steps in a Linux shell environment.
Recommendations
- Provide a Bash/Linux shell example for Azure CLI usage, using standard Bash variable assignment and array syntax.
- Clearly separate Azure CLI and PowerShell examples, and ensure CLI examples use cross-platform shell syntax.
- Add notes or sections for Linux/macOS users, highlighting any differences or prerequisites.
- Consider listing CLI (cross-platform) examples before PowerShell (Windows-centric) ones.
Hdinsight
Azure Toolkit for IntelliJ: Debug Spark apps with SSH - HDInsight
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-intellij-tool-debug-remotely-through-ssh.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page displays a Windows-first bias, especially in the prerequisites and local run sections. It highlights Windows-specific issues (WinUtils.exe), provides detailed instructions for Windows users, and references Windows environment variables and file paths. Linux/macOS users are mentioned only briefly, with no equivalent troubleshooting or setup guidance. Windows tools and patterns (WinUtils.exe, C:\WinUtils, HADOOP_HOME) are described in detail, while Linux/macOS alternatives are not discussed.
Recommendations
- Add explicit troubleshooting steps for Linux/macOS users, such as handling permissions or environment variables relevant to those platforms.
- Include examples of environment variable setup for Linux/macOS (e.g., export HADOOP_HOME=/usr/local/hadoop).
- Clarify that WinUtils.exe and HADOOP_HOME are not required on Linux/macOS, and describe any Linux/macOS-specific requirements or common issues.
- Provide parity in example commands and screenshots for Linux/macOS users where relevant.
- Reorder sections so platform-neutral or Linux/macOS instructions are presented before or alongside Windows-specific guidance.
Hdinsight
Azure Toolkit for IntelliJ: Spark app - HDInsight
...s/hdinsight/spark/apache-spark-intellij-tool-plugin.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation displays Windows bias primarily in the 'Spark Local Console(Scala)' section, where it requires WINUTILS.EXE and HADOOP_HOME environment variables, both of which are Windows-specific. There are no Linux/macOS equivalents or instructions provided for running Spark locally on those platforms. The prerequisite for WINUTILS.EXE is mentioned without alternatives or guidance for non-Windows users. No PowerShell commands are present, but the reliance on Windows tools and lack of Linux/macOS parity is evident.
Recommendations
- Add instructions for running Spark locally on Linux and macOS, including any necessary environment variables or dependencies.
- Clarify that WINUTILS.EXE is only required for Windows, and provide alternative steps or note that it is not needed on Linux/macOS.
- Explicitly state platform differences in the Spark Local Console section, and provide troubleshooting tips for Linux/macOS users.
- Where possible, include screenshots or examples from Linux/macOS environments.
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 mild Windows bias. All command-line examples use Windows-style environment variable syntax (e.g., 'set var=value'), Windows file paths (e.g., 'C:\Temp\input.txt'), and explicitly states that examples are based on a Windows environment. There are no Linux/macOS equivalents shown for environment variable setting, file paths, or input file usage. Linux/macOS users must adapt commands themselves, which may cause confusion or friction.
Recommendations
- Provide equivalent Linux/macOS examples for environment variable setting (e.g., 'export var=value').
- Show Linux/macOS file path examples (e.g., '/tmp/input.txt') alongside Windows paths.
- Add notes or side-by-side code blocks indicating differences in command syntax and file system conventions.
- Clarify that cURL commands work cross-platform, but input file usage and environment variables differ.
- Consider using generic examples or explicitly labeling sections as 'Windows' and 'Linux/macOS'.
Hdinsight
What is Apache Spark - Azure HDInsight
...main/articles/hdinsight/spark/apache-spark-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page for Apache Spark in Azure HDInsight demonstrates a moderate Windows bias. Windows-centric tools (Azure PowerShell, .NET SDK, Power BI, VS Code) are mentioned before or instead of Linux/macOS alternatives. Examples and instructions for cluster creation highlight Azure PowerShell and the Azure portal, with no mention of Linux CLI or Bash scripting. Integration with BI tools focuses on Power BI, a Windows-first product, and developer tooling emphasizes Visual Studio Code and .NET SDK. There are no explicit Linux/macOS examples or references to Bash, SSH, or Linux-native workflows.
Recommendations
- Add explicit instructions and examples for Linux/macOS users, such as using Azure CLI or Bash scripts to create and manage clusters.
- Mention cross-platform alternatives to PowerShell and .NET SDK, like Azure CLI and REST API usage from Bash or Python.
- Include references to Linux-native BI tools (e.g., Tableau, Apache Superset) and clarify compatibility.
- Present examples for both Windows and Linux/macOS environments, or clearly indicate when instructions are cross-platform.
- List developer tools for Linux/macOS (e.g., PyCharm, Eclipse, IntelliJ IDEA) alongside VS Code and .NET SDK.
Hdinsight
Python UDF with Apache Hive and Apache Pig - Azure HDInsight
...main/articles/hdinsight/hadoop/python-udf-hdinsight.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation provides both shell (Linux/macOS) and PowerShell (Windows) examples for uploading files and running Hive/Pig jobs. However, PowerShell examples are more detailed, appear first in some sections, and troubleshooting is heavily PowerShell-centric. There is a notable emphasis on PowerShell tools and workflows, with specific troubleshooting steps only for Windows line endings and PowerShell scripts. Some advanced features (e.g., remote Pig jobs) are only documented for PowerShell, and limitations for Linux users are not fully addressed.
Recommendations
- Provide equivalent Bash or Linux/macOS shell scripts for all PowerShell examples, especially for remote job submission and error retrieval.
- Include troubleshooting steps for common Linux/macOS issues (e.g., file permissions, SSH key problems, line endings from macOS editors).
- Ensure Linux/macOS shell examples are presented before or alongside PowerShell examples to avoid Windows-first bias.
- Clarify any limitations or differences for Linux/macOS users (e.g., remote Pig job submission) and suggest workarounds.
- Add links to Linux/macOS tool documentation where PowerShell tools are referenced.
Hdinsight
Submit Apache Hadoop jobs in HDInsight
...t/hadoop/submit-apache-hadoop-jobs-programmatically.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation lists three main methods for submitting Hadoop jobs: .NET SDK, curl, and PowerShell. PowerShell, a Windows-centric tool, is given equal prominence to curl (cross-platform) and .NET SDK (primarily Windows, but can be cross-platform). The resource links for PowerShell are extensive, and there is no mention of Bash, Linux shell scripts, or Linux-specific tools. The ordering of examples (.NET SDK, curl, PowerShell) puts Windows-preferred technologies first, and the absence of Linux/macOS-specific guidance or parity in tooling suggests a Windows bias.
Recommendations
- Add explicit Bash or Linux shell script examples for job submission.
- Include guidance for Linux/macOS users, such as using the Azure CLI or native Hadoop command-line tools.
- Clarify cross-platform compatibility for the .NET SDK and curl, and provide installation instructions for non-Windows environments.
- Reorder examples to alternate or prioritize cross-platform tools (e.g., curl, Azure CLI) before Windows-specific tools like PowerShell.
- Add a section addressing Linux/macOS workflows for HDInsight job submission.
Hdinsight
Use Apache Maven to build a Java HBase client for Azure HDInsight
...hdinsight/hbase/apache-hbase-build-java-maven-linux.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. Windows-specific tools (Notepad, Command Prompt, PowerShell) are used exclusively or presented first in all local development steps. All file and directory commands use Windows syntax, and text editing is done with Notepad. The PowerShell workflow is described in detail, with custom modules and examples, while no equivalent Linux/macOS shell scripts or workflows are provided. There are no bash or Linux/macOS command-line examples for local development, file operations, or text editing, and Linux tools (e.g., nano, vim, bash) are not mentioned. The test environment is explicitly Windows 10, and Linux/macOS users must infer adaptations.
Recommendations
- Provide parallel Linux/macOS examples for all command-line steps, using bash syntax (mkdir, rm, nano/vim, etc.) and POSIX paths.
- Include instructions for editing files with common Linux/macOS editors (nano, vim, gedit, etc.), not just Notepad.
- Offer a Linux/macOS test environment setup section, or clarify adaptations needed for non-Windows platforms.
- Add bash shell scripts or equivalent for the PowerShell modules, or reference Azure CLI alternatives.
- Present cross-platform commands side-by-side or clearly label OS-specific sections.
- Avoid assuming Windows as the default; mention both platforms in prerequisites and throughout.
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 gathering commands specifically for Windows command prompt, with explicit mention that variations are needed for other environments. No Linux or macOS equivalents are given, and the jq path is hardcoded for Windows. This creates friction for Linux/macOS users, who must adapt the commands themselves.
Recommendations
- Provide equivalent Linux/macOS shell commands for host information gathering, using standard jq and curl syntax.
- List both Windows and Linux/macOS examples side-by-side, or default to cross-platform bash syntax where possible.
- Avoid hardcoding Windows-specific paths (e.g., jq-win64.exe) and instead use generic references or note platform differences.
- Explicitly mention how Linux/macOS users can adapt the commands, or link to platform-specific instructions.
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 presents PowerShell (Windows) automation for user management before the Linux-friendly curl/bash example. The PowerShell section is more detailed, with variable setup, credential handling, and output parsing, while the curl/bash section is shorter and notes that modifications are needed for Windows. This ordering and detail level may create friction for Linux/macOS users, though both platforms are ultimately supported.
Recommendations
- Present Linux/bash (curl) examples before or alongside PowerShell examples to avoid Windows-first bias.
- Expand the curl/bash example to match the detail and completeness of the PowerShell section (e.g., include output parsing, error handling, and privilege granting steps).
- Explicitly state platform compatibility for each example and provide guidance for macOS users where appropriate.
- Where possible, provide REST API examples in a platform-neutral way (e.g., using curl or HTTPie) as the primary automation method.
- Add a table or section summarizing all supported automation methods for user management, with platform notes.
Hdinsight
Manage Apache Hadoop clusters in HDInsight with .NET SDK - Azure
...icles/hdinsight/hdinsight-administer-use-dotnet-sdk.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. All package installation instructions use PowerShell, with no Linux/macOS equivalents (e.g., dotnet CLI or NuGet CLI). The code samples reference the PowerShell client GUID and use Windows-centric terminology (e.g., 'command prompt window'). In the Apache HBase section, balancing is described using Windows batch syntax (%HBASE_HOME%\bin), with no Linux shell equivalents. No Linux/macOS-specific instructions or examples are provided for any administrative tasks.
Recommendations
- Provide Linux/macOS equivalents for package installation, such as 'dotnet add package' or 'nuget install' commands.
- Include shell/bash examples alongside PowerShell, especially for cluster management and HBase balancing.
- Avoid Windows-centric terminology like 'command prompt window'; use platform-neutral terms or mention both 'command prompt' and 'terminal'.
- Reference both Windows and Linux environment variables (e.g., %HBASE_HOME% for Windows, $HBASE_HOME for Linux/macOS).
- Clarify that the .NET SDK is cross-platform and provide guidance for Linux/macOS users where workflows differ.
Hdinsight
Non-interactive authentication .NET application - Azure HDInsight
...ate-non-interactive-authentication-dotnet-applications.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation focuses exclusively on Windows-centric tools and workflows. All code examples are for .NET (C#), which is most commonly used on Windows, and NuGet package installation is shown using the PowerShell 'Install-Package' command. There are no Linux/macOS-specific instructions, nor are cross-platform alternatives (such as .NET CLI or Visual Studio Code) mentioned. The Azure portal workflow is platform-neutral, but the development and authentication steps assume a Windows environment.
Recommendations
- Add instructions for installing NuGet packages using the .NET CLI (e.g., 'dotnet add package ...'), which works on Linux/macOS.
- Mention that .NET Core/.NET 6+ and Visual Studio Code can be used on Linux/macOS for development.
- Provide sample code or guidance for running the application on Linux/macOS, including any environment setup or prerequisites.
- Include links to cross-platform authentication documentation, not just PowerShell-based guides.
- Explicitly state platform compatibility for the SDKs and tools used.
Hdinsight
Create Apache Hadoop clusters using templates - Azure HDInsight
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-create-linux-clusters-arm-templates.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page shows a mild Windows bias: PowerShell is mentioned and linked before Azure CLI, and Visual Studio (a Windows-centric tool) is highlighted as a deployment method, including references to PowerShell scripts. There are no explicit Linux/macOS command-line examples or references to Linux-native editors (e.g., vim, nano), and the .NET client library example links to a Windows-specific page. While cross-platform tools like VS Code and Azure CLI are mentioned, Windows tools and patterns are presented first or with more detail.
Recommendations
- Present Azure CLI examples and links before or alongside PowerShell to emphasize cross-platform support.
- Include explicit Linux/macOS command-line examples for template deployment (e.g., bash scripts, use of native editors).
- Mention Linux-native editors (vim, nano, gedit) as alternatives to VS Code for editing templates.
- Provide parity in client library examples, linking to both Windows and Linux/.NET Core documentation.
- Clarify that all deployment methods (CLI, REST API) work on Linux/macOS as well as Windows.
Hdinsight
Apache Hive libraries during cluster creation - Azure HDInsight
...icles/hdinsight/hdinsight-hadoop-add-hive-libraries.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation references a PowerShell script as the primary example for adding Hive libraries, with the script location and instructions given before the Linux bash script. The script provided is a .ps1 file (PowerShell), and Azure PowerShell/.NET SDK are mentioned as cluster creation methods before Linux-specific instructions. There is a separate bash script for Linux, but it is introduced later and less prominently. Windows tools like Azure Storage Explorer are mentioned for file uploads, with no Linux alternatives suggested.
Recommendations
- Present Linux (bash) and Windows (PowerShell) script options side-by-side, with equal prominence.
- List Linux-native tools for uploading files to Azure Blob Storage (e.g., azcopy, Azure CLI) alongside Azure Storage Explorer.
- Clarify which script to use based on the user's OS at the start of the instructions.
- Provide explicit instructions for cluster creation using Linux command-line tools (e.g., Azure CLI), not just PowerShell/.NET SDK.
- Avoid listing Windows/PowerShell options first unless there is a technical reason.
Hdinsight
Add additional Azure Storage accounts to HDInsight
...ain/articles/hdinsight/hdinsight-hadoop-add-storage.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides a detailed PowerShell example for verifying the additional storage account, but does not offer an equivalent example for Linux/macOS users (e.g., Bash, curl, or Python). The PowerShell method is presented first and in more detail, while Linux verification relies on using the Apache Ambari web UI, which may not be suitable for all users or automation scenarios. There are no CLI or script examples for Linux users, and the prerequisites mention PowerShell specifically.
Recommendations
- Add a Bash or Python example for verifying the storage account via REST API (using curl or requests) to match the PowerShell example.
- Include Azure CLI commands for verification, if possible.
- Present Linux/macOS-friendly methods before or alongside Windows/PowerShell examples.
- Clarify that the PowerShell example is for Windows users and provide parity for other platforms.
Hdinsight
Tutorial: On-demand clusters in Azure HDInsight with Data Factory
...dinsight/hdinsight-hadoop-create-linux-clusters-adf.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation relies exclusively on Azure PowerShell scripts for critical setup steps, such as creating the resource group, storage account, and copying files. No equivalent Bash/CLI examples are provided, and the PowerShell requirement is stated as a prerequisite. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer Bash/Azure CLI. Additionally, the tutorial refers to the PowerShell script repeatedly as the canonical method for setup, with no mention of alternatives.
Recommendations
- Provide equivalent Azure CLI (az) commands for all PowerShell script steps, including resource group, storage account, blob container creation, and file copying.
- Explicitly state that users can use either PowerShell or Azure CLI, and link to installation guides for both.
- Add a selector or toggle for Bash/Azure CLI vs. PowerShell throughout the tutorial, similar to other Azure docs.
- Clarify any platform-specific requirements (e.g., PowerShell Core on Linux/macOS) if PowerShell must be used, and provide installation instructions.
- Ensure screenshots and instructions are not Windows-centric (e.g., avoid assuming Windows file paths or UI layouts).
Hdinsight
Cluster management best practices - Azure HDInsight
...rticles/hdinsight/cluster-management-best-practices.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation lists Azure PowerShell as a primary method for cluster creation and management, alongside Azure CLI and cURL. PowerShell is a Windows-centric tool, and its inclusion as a top-level option reflects a mild Windows bias. Additionally, the PowerShell example is listed before cURL and SDKs, which are more cross-platform. There are no explicit Linux/macOS examples or mentions of Linux-specific tools, though most options (CLI, cURL, SDKs) are cross-platform.
Recommendations
- Ensure Linux/macOS parity by providing explicit Bash or shell script examples where PowerShell is mentioned.
- List cross-platform tools (Azure CLI, cURL, SDKs) before Windows-specific tools like PowerShell.
- Add a note clarifying which tools are cross-platform and which are Windows-specific.
- Provide links or guidance for Linux/macOS users for cluster management tasks.
Hdinsight
Connect Azure HDInsight to your on-premises network
...main/articles/hdinsight/connect-on-premises-network.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows (PowerShell) and Linux (Azure CLI, SSH) examples for most core tasks, but Windows/PowerShell examples are often listed first, and some advanced configuration (e.g., DNS conditional forwarders) references Windows Server documentation before Linux equivalents. The section on discovering HDInsight node FQDNs gives a PowerShell script first, then Azure CLI. There is a slight preference for Windows tools and patterns, though Linux parity is generally maintained.
Recommendations
- Present Azure CLI and Linux-native examples before or alongside PowerShell/Windows examples, especially in code blocks and step-by-step instructions.
- When referencing external documentation (e.g., DNS server configuration), link to Linux/BIND documentation before or alongside Windows Server documentation.
- Explicitly state that all tasks can be completed on Linux/macOS and highlight any OS-specific differences.
- Expand Linux/macOS sections with troubleshooting tips or common issues, matching the depth of Windows guidance.
- Ensure that all critical workflows (e.g., DNS configuration, cluster connection) have complete Linux/macOS instructions and verification steps.
Hdinsight
Cluster creation fails with DomainNotFound error in Azure HDInsight
...hdinsight/domain-joined/troubleshoot-domainnotfound.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Ubuntu (Linux) troubleshooting steps for domain joining, but the Windows VM example is listed first and described in more detail (mentioning the control panel UI), while the Ubuntu instructions are less detailed and rely on an external script. There is no exclusive use of Windows tools or missing Linux example, but the ordering and detail favor Windows.
Recommendations
- Present Windows and Linux (Ubuntu) troubleshooting steps with equal detail and clarity.
- Consider listing Linux and Windows examples side-by-side or alternating order in different sections.
- Expand the Ubuntu instructions to include more explicit steps (e.g., how to install required packages, join domain manually, etc.), not just referencing an external script.
- Clarify that both methods are equally valid and supported.
Hdinsight
Use Apache Hadoop Hive with Curl in HDInsight - Azure
...ticles/hdinsight/hadoop/apache-hadoop-use-hive-curl.md
Low 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 examples are consistently presented alongside Bash, and Windows tools (Invoke-WebRequest) are mentioned first in the prerequisites. The introductory REST client section lists PowerShell before cURL, and the PowerShell examples are fully fleshed out, sometimes with additional explanation (e.g., credential pop-up). However, Linux parity is generally maintained, and all tasks can be completed on Linux/macOS using the provided Bash/cURL commands.
Recommendations
- List Bash/cURL examples and tools before PowerShell/Windows equivalents in prerequisites and code blocks.
- Explicitly mention Linux/macOS compatibility in the introduction and throughout the document.
- Provide equal detail for Bash/cURL steps (e.g., credential handling, error handling) as is given for PowerShell.
- Add a note clarifying that all examples are cross-platform unless otherwise stated.