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 551-575 of 867 flagged pages
Hdinsight
Infrastructure: On-premises Apache Hadoop to Azure HDInsight
...op-on-premises-migration-best-practices-infrastructure.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page exhibits Windows bias primarily in the 'Customize HDInsight configs using Bootstrap' section, where only a PowerShell example using the AZ module is provided for cluster configuration. There is no equivalent example for Linux/macOS users (e.g., Bash/CLI/ARM template), and the PowerShell tool is Windows-centric. Additionally, the PowerShell example appears before any mention of alternatives, and there is no guidance for Linux users in this critical configuration step.
Recommendations
- Provide equivalent examples using Azure CLI (az hdinsight ...), Bash scripts, or ARM templates for cluster configuration and customization.
- Explicitly mention cross-platform alternatives to PowerShell, especially for Linux/macOS users.
- Reorder examples so that platform-neutral or Linux-native approaches are presented first or alongside Windows/PowerShell methods.
- Add notes clarifying which tools are cross-platform and which are Windows-only.
- Ensure all critical configuration steps can be completed from Linux/macOS environments.
Create Pull Request
Hdinsight
Security: Migrate on-premises Apache Hadoop to Azure HDInsight
...p-on-premises-migration-best-practices-security-devops.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively referencing Microsoft Entra Domain Services, Active Directory, and related Windows-centric tools and patterns for cluster security and management. There are no examples or guidance for Linux-native identity management or integration with non-Windows authentication systems. All instructions and terminology assume a Windows/AD environment, with no mention of Linux alternatives or parity.
Recommendations
- Include guidance for integrating HDInsight clusters with Linux-based identity providers (e.g., LDAP, Kerberos, FreeIPA) for authentication and RBAC.
- Provide examples and instructions for cluster deployment and management using Linux-native tools and command-line interfaces.
- Clarify whether HDInsight supports non-AD authentication and document any limitations or alternatives for Linux/macOS users.
- Add parity in documentation for Linux/macOS environments, such as SSH key management, local user/group management, and open-source security tools.
- Explicitly state any platform requirements or limitations at the beginning of the documentation.
Hdinsight
Use MapReduce and Curl with Apache Hadoop in HDInsight - Azure
...s/hdinsight/hadoop/apache-hadoop-use-mapreduce-curl.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias: command examples use Windows-specific syntax (cmd 'set' for variables, caret '^' for line continuation), Windows paths for jq, and PowerShell is the only scripting language shown. There are no Linux/macOS shell examples for variable setting, line continuation, or jq invocation, making it harder for non-Windows users to follow. Windows tools and patterns are mentioned first and exclusively, with no Linux equivalents provided.
Recommendations
- Provide Linux/macOS shell examples for all curl commands, including variable setting (e.g., 'export'), line continuation (using '\'), and jq usage (e.g., 'jq .id').
- Show Linux-friendly jq invocation (e.g., 'jq .id' instead of 'C:\HDI\jq-win64.exe .id').
- Include Bash or shell script examples alongside PowerShell, especially for variable assignment and command chaining.
- Explicitly mention how Linux/macOS users should adapt the examples, or provide side-by-side Windows and Linux/macOS sections.
- Avoid Windows-centric phrasing like 'This example is based on a Windows environment' unless immediately followed by Linux/macOS alternatives.
Hdinsight
Using Apache Hive as an ETL Tool - Azure HDInsight
...doop/apache-hadoop-using-apache-hive-as-an-etl-tool.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. It references Windows-specific tools (SQL Server Integration Services, Excel, PowerShell) and patterns before mentioning cross-platform or Linux-native alternatives. Examples and automation recommendations (PowerShell, Excel, SSIS) are Windows-centric, with no equivalent Linux/macOS instructions or examples provided. Linux tools like Sqoop and Oozie are mentioned, but only after Windows options and without parity in example detail.
Recommendations
- Provide Linux/macOS equivalents for automation (e.g., Bash scripts, cron jobs, Apache Airflow, or Oozie for scheduling Hive queries).
- Include examples of loading data into non-Windows databases (e.g., PostgreSQL, MySQL) using Sqoop.
- Offer instructions for querying Hive from Linux/macOS clients (e.g., Beeline, JDBC, Python scripts) instead of only Excel or C#.
- Present Linux tools and workflows (e.g., shell scripts, Oozie) alongside or before Windows tools to ensure parity.
- Add explicit Linux/macOS command-line examples for each major step, especially for automation and data loading.
Hdinsight
What is Apache Hive and HiveQL - Azure HDInsight
...b/main/articles/hdinsight/hadoop/hdinsight-use-hive.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation lists Windows-specific tools (Visual Studio, PowerShell, SSIS) as primary options for interacting with Hive on HDInsight, sometimes before or in addition to cross-platform alternatives. Windows tools are mentioned explicitly and given dedicated sections, while Linux/macOS equivalents are not always provided or are grouped generically. However, most core Hive usage (via Beeline, REST API, browser-based tools) is cross-platform, and Linux/macOS users are not blocked from completing tasks.
Recommendations
- Ensure Linux/macOS alternatives are mentioned alongside Windows tools (e.g., alternatives to PowerShell for automation, such as Bash scripts or Azure CLI).
- Present cross-platform tools (Beeline, REST API, VS Code) before Windows-only tools in lists and tables.
- Add explicit Linux/macOS examples or links for tasks currently described only with Windows tools (e.g., running Hive queries via automation).
- Clarify which tools are cross-platform and which are Windows-only in all tables and descriptions.
- Provide links to Linux/macOS-specific guides where available (e.g., using Oozie, Bash, or Azure CLI for scheduling and automation).
Hdinsight
Unable to access Data Lake storage files in Azure HDInsight
...sight/hadoop/hdinsight-troubleshoot-data-lake-files.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation provides a detailed PowerShell script for certificate management, which is Windows-centric and does not offer equivalent Linux/macOS CLI or automation examples. All certificate creation and assignment steps are described using PowerShell, with no mention of alternatives like Azure CLI, OpenSSL, or Bash scripting. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
- Provide equivalent Azure CLI and Bash/OpenSSL examples for certificate creation, export, and assignment.
- Include instructions for performing certificate management tasks on Linux/macOS, such as using OpenSSL to generate certificates and Azure CLI to update cluster identity.
- Clearly indicate which steps are platform-specific and offer cross-platform alternatives where possible.
- Reorder examples so that cross-platform (CLI/Bash) options are presented before or alongside PowerShell scripts.
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 is heavily featured, with extensive scripts and troubleshooting focused on Windows tooling. PowerShell examples are more detailed and cover remote job submission, while Linux/macOS examples are limited to basic shell commands. Troubleshooting for line endings is Windows-centric, and there is no mention of macOS-specific issues or tools. PowerShell is presented as the primary remote automation method, with Linux alternatives (e.g., Azure CLI, Bash scripting) missing or underrepresented.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell scripts, enabling Linux/macOS users to automate tasks without PowerShell.
- Include troubleshooting steps for common Linux/macOS issues (e.g., file permissions, SSH key problems), not just Windows line endings.
- Present shell (Linux/macOS) and PowerShell examples side-by-side, rather than giving PowerShell more space and detail.
- Mention and link to cross-platform tools (Azure CLI, REST API) in the prerequisites and throughout the guide.
- Clarify that PowerShell is optional and provide guidance for users on non-Windows platforms.
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 demonstrates a notable Windows bias. All initial examples use Windows tools (cmd.exe, Notepad), and Windows-specific commands and file paths are shown first and exclusively. The PowerShell workflow is described in detail, with no equivalent Linux shell scripting or automation guidance. Linux/macOS users are expected to adapt Windows-centric instructions, and there are no explicit Linux shell (bash) or editor (vim/nano) examples for key steps like file creation, editing, or directory management.
Recommendations
- Provide Linux/macOS equivalents for all command-line steps, including directory creation, file deletion, and editing (e.g., use mkdir, rm, vim/nano).
- Include Linux/macOS file paths and command syntax alongside Windows examples, or present both in parallel.
- Offer a bash script or workflow for uploading JARs and running jobs, similar to the PowerShell module.
- Use cross-platform editors (e.g., VS Code, nano, vim) in examples, or mention alternatives.
- Clearly indicate which steps are OS-specific and provide adaptation notes or links.
- Consider presenting Linux/macOS instructions first, or in equal prominence, to balance the experience.
Hdinsight
Tutorial - Use Apache HBase in Azure HDInsight
...sight/hbase/apache-hbase-tutorial-get-started-linux.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates some Windows bias, especially in the prerequisites section, where Bash usage is described in the context of Windows 10 and Windows Subsystem for Linux (WSL) is recommended before mentioning Unix shells. Windows PowerShell's Invoke-RestMethod is referenced as an alternative to curl, and modifications for Windows Command Prompt are mentioned, but no explicit Linux/macOS examples are provided. The ordering and tool references may create friction for Linux/macOS users.
Recommendations
- Present Linux/macOS instructions and examples before or alongside Windows-specific guidance.
- Include explicit Linux/macOS command examples where Windows alternatives (PowerShell, Command Prompt) are mentioned.
- Clarify that Bash/curl commands work natively on Linux/macOS, and provide links to relevant Linux/macOS documentation.
- Avoid framing Bash usage primarily in the context of Windows/WSL.
- If mentioning Windows tools (PowerShell), also mention Linux/macOS equivalents (e.g., curl, wget) with example syntax.
Hdinsight
Run Apache Sqoop jobs with Azure HDInsight (Apache Hadoop)
.../main/articles/hdinsight/hadoop/hdinsight-use-sqoop.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. The description and metadata emphasize Azure PowerShell usage from a workstation, with PowerShell and .NET SDK methods highlighted for Windows clients. Linux/macOS methods (SSH) are mentioned but not prioritized, and example walkthroughs or code snippets for Linux are missing. The limitations section focuses on Linux-based HDInsight, but does not provide Linux-specific guidance or parity for PowerShell/SDK workflows.
Recommendations
- Provide equivalent walkthroughs and code examples for Linux/macOS users, especially for Sqoop job submission via SSH or command line.
- Reorder examples and client OS tables to present Linux/macOS options first or equally.
- Include explicit instructions for running Sqoop jobs from Linux/macOS workstations, not just Windows/PowerShell.
- Add parity for SDKs or CLI tools available on Linux/macOS, or clarify limitations and alternatives.
- Ensure that limitations and troubleshooting sections address both Windows and Linux scenarios.
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 page lists three main methods for submitting Hadoop jobs: .NET SDK, curl, and PowerShell. The inclusion of .NET SDK and PowerShell as primary options reflects a Windows-centric approach, as both are traditionally Windows-first technologies. PowerShell examples are provided as a distinct section, but there is no mention of Linux/macOS equivalents (e.g., Bash scripts, CLI tools). The ordering (.NET SDK, curl, PowerShell) also places Windows technologies before more cross-platform options like curl.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users.
- Include Azure CLI instructions, which are cross-platform.
- Clarify which methods are cross-platform and which are Windows-specific.
- Reorder examples to highlight cross-platform tools (e.g., curl, CLI) before Windows-specific ones.
- Mention alternatives to PowerShell for non-Windows environments.
Hdinsight
InvalidNetworkConfigurationErrorCode error - Azure HDInsight
...idnetworkconfigurationerrorcode-cluster-creation-fails.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page is mostly neutral and Linux-focused in its troubleshooting steps (e.g., SSH, Linux commands like nslookup, dig, and resolv.conf). However, there is a notable Windows bias in the final section: the only explicit mention of a deprecated parameter is for PowerShell (EnableVmProtection), and the resolution refers exclusively to the Az PowerShell SDK. Additionally, when discussing DNS server VM deployment, Windows is mentioned before Linux as an option. There are no Linux/macOS equivalents or CLI examples for the PowerShell-specific troubleshooting, and Windows VM is listed before Linux VM in one section.
Recommendations
- Include Azure CLI or REST API equivalents for PowerShell-specific troubleshooting steps, especially for checking or updating network configuration parameters.
- When mentioning VM deployment for DNS forwarding, list Linux and Windows equally or mention Linux first, as HDInsight clusters are Linux-based.
- Provide guidance for users who do not use PowerShell (e.g., macOS/Linux users) on how to check for deprecated parameters or manage network configuration.
- Add explicit notes or examples for Linux/macOS users in sections that currently only reference Windows tools or PowerShell.
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
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. All package installation instructions use PowerShell, and the authentication flow references the PowerShell client GUID. Command-line examples for cluster management are absent, and the only shell commands shown (for HBase balancing) use Windows batch syntax (%HBASE_HOME%\bin), not Linux/Mac equivalents. There are no Linux/macOS-specific instructions or examples for .NET SDK usage, and Windows tools/patterns are mentioned exclusively or first.
Recommendations
- Provide equivalent Linux/macOS instructions for installing .NET SDK packages (e.g., using dotnet CLI or NuGet CLI on bash/zsh).
- Include Linux/Mac shell syntax for HBase commands (e.g., $HBASE_HOME/bin/hbase shell).
- Clarify that the .NET SDK can be used cross-platform and provide guidance for non-Windows environments.
- Avoid referencing Windows-specific GUIDs or tools unless alternatives for other platforms are given.
- Present examples for both Windows and Linux/macOS, or use platform-neutral instructions where possible.
Hdinsight
Authorize users for Ambari Views - Azure HDInsight
...icles/hdinsight/hdinsight-authorize-users-to-ambari.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides three methods for adding users: via the portal, PowerShell, and Curl. The PowerShell example is given in full before the Curl (bash) example, and is much more detailed, with explanatory comments and output handling. The Curl example is presented as an alternative, but notes that it is designed for bash and would require modifications for Windows command prompt. There is a notable emphasis on PowerShell and Windows tooling, with more attention and detail given to the Windows approach. Additionally, tools like ODBC and PowerShell are mentioned as cluster interaction endpoints before REST APIs, which are more cross-platform.
Recommendations
- Present Linux/bash (Curl) examples before or alongside PowerShell examples to avoid Windows-first bias.
- Ensure both PowerShell and bash examples have equivalent detail, comments, and output handling.
- Explicitly mention Linux/macOS compatibility in all relevant sections, and provide troubleshooting notes for non-Windows platforms.
- Include REST API examples with generic HTTP tools (e.g., curl, httpie) as primary cross-platform options.
- Avoid language that assumes Windows as the default environment (e.g., 'Slight modifications would be needed for a Windows command prompt' could be rephrased to treat bash as a first-class citizen).
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 page provides instructions and code samples exclusively for .NET (C#) applications, which are most commonly developed and run on Windows. Package installation is shown using NuGet's Install-Package command, typically used in Windows environments. There are no Linux/macOS-specific instructions, examples, or alternative tooling mentioned. The 'Next steps' section references PowerShell-based authentication guides, which are Windows-centric, and does not mention CLI or Bash alternatives.
Recommendations
- Add equivalent examples and instructions for Linux/macOS environments, such as using .NET Core/SDK on Linux.
- Include package installation instructions using the dotnet CLI (e.g., 'dotnet add package ...'), which works cross-platform.
- Reference Azure CLI or Bash-based authentication guides in addition to PowerShell.
- Explicitly state platform compatibility for the code samples and tools.
- Provide troubleshooting notes for common Linux/macOS issues (e.g., SecureString limitations, environment setup).
Hdinsight
Apache Hive libraries during cluster creation - Azure HDInsight
...icles/hdinsight/hdinsight-hadoop-add-hive-libraries.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page references a PowerShell script as the primary method for adding Hive libraries, and mentions Azure PowerShell and .NET SDK as cluster creation options before Linux alternatives. Windows tools like Azure Storage Explorer are suggested for file uploads, with no mention of Linux-native equivalents. Although Linux Bash script instructions are provided, the initial emphasis and tooling recommendations favor Windows environments.
Recommendations
- Provide explicit Linux/macOS command-line examples for uploading files to Azure Blob Storage (e.g., using azcopy, Azure CLI, or curl).
- Mention cross-platform alternatives to Azure Storage Explorer, such as the Azure CLI or web portal, and clarify their usage on Linux/macOS.
- List Linux Bash script options and cluster creation steps before or alongside Windows/PowerShell methods to avoid Windows-first ordering.
- Clarify which instructions are platform-specific and ensure parity in guidance for Linux/macOS users.
Hdinsight
Azure HDInsight configuration settings reference
...main/articles/hdinsight/hdinsight-config-for-vscode.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page displays Windows bias primarily in the configuration examples for HDInsight Spark.NET settings. Paths and tool references (7z.exe, winutils.exe, JAVA_HOME, SCALA_HOME, SPARK_HOME) are given only in Windows format (e.g., C:\Program Files\...), and winutils.exe is explicitly marked as 'windows OS only' without mentioning Linux/macOS alternatives. No Linux/macOS paths or equivalents are provided, and Windows tools are referenced first and exclusively in these sections.
Recommendations
- Add Linux/macOS path examples for JAVA_HOME, SCALA_HOME, SPARK_HOME, and 7z (e.g., /usr/bin/java, /usr/share/scala, /opt/spark, /usr/bin/7z).
- Clarify which settings are Windows-specific and provide Linux/macOS alternatives or note when a setting is not required on non-Windows platforms.
- Include notes or links to documentation for setting up HDInsight Spark.NET on Linux/macOS, including any differences in required tools (e.g., winutils.exe is not needed on Linux).
- Present examples for both Windows and Linux/macOS side-by-side or in separate sections for parity.
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 moderate Windows bias. PowerShell and Visual Studio (Windows-centric tools) are mentioned before Azure CLI and REST API options. The PowerShell deployment method is described before the cross-platform Azure CLI, and Visual Studio is highlighted as a deployment tool, with no mention of Linux/macOS equivalents (such as VS Code or command-line editors for deployment). There are no explicit Linux/macOS examples or screenshots, and the .NET client library example links to a Windows-specific page. While Azure CLI is mentioned, parity in examples and tooling guidance is lacking.
Recommendations
- Provide Linux/macOS-specific examples and screenshots for deployment steps.
- Highlight Azure CLI as the primary cross-platform deployment method before PowerShell.
- Include guidance for using VS Code or other cross-platform editors for template deployment.
- Link to .NET client library examples that are not Windows-specific, or provide equivalent examples for Linux/macOS.
- Explicitly state which steps/tools are cross-platform and which are Windows-only.
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
Windows Tools
Summary
The documentation provides examples and guidance for both Azure PowerShell and Azure CLI, but PowerShell (a Windows-centric tool) is consistently presented before CLI and receives more detailed coverage, including output samples and cmdlet tables. The .NET SDK (primarily used on Windows) is also highlighted. Although Linux is referenced as the OS for clusters and Bash scripts are used, the documentation workflow and examples favor Windows tools and patterns, with PowerShell examples shown first and in more detail than CLI equivalents.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, especially for tasks that are equally supported on Linux/macOS.
- Expand Azure CLI sections to include output samples and detailed command tables, matching the depth of PowerShell coverage.
- Explicitly mention cross-platform compatibility for all tools and clarify which steps are OS-agnostic.
- Add guidance for using REST API and .NET SDK from Linux/macOS environments, or highlight Python SDK alternatives.
- Ensure all screenshots and walkthroughs are not Windows-specific (e.g., avoid showing only Windows UI elements).
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 tutorial relies exclusively on Azure PowerShell scripts for all command-line operations, including resource creation and file copying. No Bash, Azure CLI, or Linux/macOS shell alternatives are provided. The instructions and prerequisites assume PowerShell is available, which is native to Windows but requires extra setup on Linux/macOS. This creates friction for non-Windows users and may block those unfamiliar with PowerShell.
Recommendations
- Provide equivalent Azure CLI (az) commands for all PowerShell script steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention how Linux/macOS users can install and use PowerShell if PowerShell is required, or offer Bash script alternatives.
- Add a section or selector for Linux/macOS users, showing how to perform resource creation and file operations using native tools or Azure CLI.
- Ensure screenshots and portal instructions do not assume Windows-only conventions (e.g., file paths, UI layout).
Hdinsight
Apache Hadoop & secure transfer storage - Azure HDInsight
...oop-create-linux-clusters-with-secure-transfer-storage.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure portal, PowerShell, and Azure CLI. PowerShell (a Windows-centric tool) is given a dedicated section before Azure CLI, and the CLI section does not mention Linux or macOS specifically. There are no explicit Linux shell or macOS Terminal examples, and PowerShell is presented as a primary method, which may create friction for non-Windows users.
Recommendations
- Add explicit Bash/shell examples for Linux/macOS users, especially for storage account management.
- Clarify that Azure CLI works cross-platform and provide example commands run from Bash or macOS Terminal.
- Reorder sections to present Azure CLI before PowerShell, as CLI is more universally accessible.
- Include notes or links for Linux/macOS users on installing and using Azure CLI.
- Avoid presenting PowerShell as the default scripting tool unless necessary for Windows-specific tasks.
Hdinsight
Use SSH with Hadoop - Azure HDInsight
...icles/hdinsight/hdinsight-hadoop-linux-use-ssh-unix.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation provides a balanced overview of SSH usage across platforms, but exhibits some Windows bias. Windows-specific tools (OpenSSH Client, Bash on Ubuntu on Windows, Azure Cloud Shell, Git, PuTTY, MobaXterm) are listed in detail, while Linux/macOS SSH usage is described generically. Azure PowerShell examples and parameters are mentioned before Azure CLI equivalents, and PowerShell is referenced more frequently than Linux shell commands for cluster creation and management. Some sections (e.g., SSH key generation) use 'azurepowershell-interactive' code blocks, which may suggest a Windows-centric approach.
Recommendations
- Provide explicit Linux/macOS command-line examples for cluster creation and management, especially where PowerShell is used.
- List Linux/macOS tools and usage examples with equal detail as Windows tools.
- Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Clarify that all SSH commands and key management steps apply equally to Linux/macOS, and provide platform-specific notes where behavior differs.
- Include screenshots or walkthroughs for Linux/macOS environments, not just Windows.
Hdinsight
Use Azure Monitor logs to monitor Azure HDInsight clusters
...insight/hdinsight-hadoop-oms-log-analytics-tutorial.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page presents both Azure PowerShell and Azure CLI instructions for enabling Azure Monitor logs on HDInsight clusters. However, PowerShell (a Windows-centric tool) is consistently mentioned before Azure CLI, and its examples are more detailed. There is a notable emphasis on PowerShell prerequisites and usage, which may create friction for Linux/macOS users. The CLI examples use bash syntax, but there are no explicit Linux/macOS-specific notes or parity checks. Windows tools and patterns (PowerShell, Az Module) are referenced more prominently than their cross-platform equivalents.
Recommendations
- Alternate the order of PowerShell and CLI instructions, or present CLI examples first to avoid Windows-first bias.
- Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Provide parity checks, clarifying that all steps and commands work identically on Linux/macOS.
- Add troubleshooting notes or links for Linux/macOS users where relevant (e.g., permissions, environment setup).
- Consider including screenshots or terminal output from Linux/macOS environments to reinforce cross-platform support.
Hdinsight
Understand and resolve WebHCat errors on HDInsight - Azure
...ght/hdinsight-hadoop-templeton-webhcat-debug-errors.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references Windows-centric tools (Azure PowerShell, Data Lake Tools for Visual Studio) as primary client-side interfaces for WebHCat, without mentioning Linux/macOS alternatives (e.g., curl, Python requests, Bash scripting). The introduction positions Windows tools first, which may imply they are the default or preferred method, creating a subtle Windows bias.
Recommendations
- Explicitly mention cross-platform tools for interacting with WebHCat, such as curl, wget, or Python scripts.
- Provide example commands for submitting jobs or querying status using Linux/macOS-friendly tools.
- Clarify that WebHCat is accessible via standard REST APIs from any OS, and link to relevant cross-platform usage guides.
- If possible, add troubleshooting steps or configuration modification instructions using Linux shell or CLI tools (e.g., Ambari REST API via curl).
Hdinsight
Manage logs for an HDInsight cluster - Azure HDInsight
...ob/main/articles/hdinsight/hdinsight-log-management.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is frequently mentioned as a primary scripting tool for log management and archiving, with references to Azure PowerShell cmdlets and .NET SDKs for job submission and log access. Windows-centric tools (Visual Studio, Power Query for Excel, Azure Storage Explorer) are listed for log analysis and forecasting before Linux alternatives. While SSH and Ambari (Linux-based) are covered, Linux-native tools and scripting approaches (e.g., Bash, Python, Linux CLI utilities) are rarely mentioned, and PowerShell examples are given more prominence. Some sections (e.g., log archiving) offer PowerShell scripting as the main automation method, with no Linux shell or cross-platform alternatives. Linux tools like logrotate are mentioned only briefly and late in the document.
Recommendations
- Provide equivalent Linux/Bash scripting examples for log management and archiving tasks, especially where PowerShell is featured.
- List cross-platform or Linux-native tools (e.g., Azure CLI, Python SDK, Bash scripts, Linux file utilities) alongside or before Windows tools.
- Expand on the use of Linux utilities (e.g., logrotate, cron, rsync, grep) for log rotation, collection, and archiving.
- Include examples using Linux-based editors and analysis tools (e.g., Vim, nano, awk, sed, pandas in Python) for log review and forecasting.
- Clarify which instructions and tools are cross-platform, and explicitly note when a tool is Windows-only.
- Add links to Linux/macOS-specific documentation where available.