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 351-375 of 867 flagged pages
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/apache-domain-joined-configure-using-azure-adds.md
...ned/apache-domain-joined-configure-using-azure-adds.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing only a PowerShell example for certificate creation, referencing Windows-specific tools (e.g., ldp.exe), and instructing users to test network setup by joining a Windows VM and using Windows tools. There are no equivalent Linux examples or instructions for performing these tasks on Linux-based systems, despite HDInsight clusters often being Linux-based.
Recommendations
- Provide equivalent Linux command-line examples for certificate creation (e.g., using OpenSSL) alongside the PowerShell example.
- Include instructions for testing network setup from a Linux VM, such as using 'ping', 'ldapsearch', or 'openssl s_client' for LDAPS connectivity.
- Mention Linux tools and workflows (e.g., using 'nslookup', 'dig', or 'host' for DNS resolution) in parallel with Windows tools.
- Avoid assuming the use of Windows VMs for validation steps; explicitly state that either Windows or Linux VMs can be used, and provide guidance for both.
- Ensure that all critical configuration and validation steps are documented for both Windows and Linux environments to support cross-platform users.
Create Pull Request
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/apache-domain-joined-architecture.md
...ght/domain-joined/apache-domain-joined-architecture.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits a strong Windows bias. All command-line instructions are provided exclusively using PowerShell, with no mention of Bash, Linux CLI, or cross-platform alternatives. The focus is on Microsoft Entra Domain Services (which is Windows Server Active Directory-compatible), and tools and patterns referenced (such as PowerShell modules and service principals) are specific to Windows environments. There are no Linux or open-source identity provider examples, and the documentation assumes a Windows-centric infrastructure throughout.
Recommendations
- Provide equivalent command-line instructions using Azure CLI (az), which is cross-platform, alongside PowerShell examples.
- Include guidance for users managing clusters from Linux or macOS environments, such as using Bash scripts or REST APIs.
- Mention and, where possible, document integration patterns with non-Windows identity providers (e.g., MIT Kerberos, OpenLDAP) or clarify their (non-)support.
- Avoid assuming the reader is operating from a Windows environment; explicitly state platform requirements and offer alternatives.
- Reorder sections or examples so that cross-platform or neutral tooling (e.g., Azure Portal, Azure CLI) is presented before or alongside Windows-specific tools.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/includes/hdinsight-portal-management-selector.md
...sight/includes/hdinsight-portal-management-selector.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page lists Azure PowerShell and .NET SDK (both Windows-centric tools) before Azure CLI, and does not explicitly mention Linux-native tools or provide Linux-specific examples. The ordering and tool selection suggest a Windows-first approach, with limited visibility for Linux users.
Recommendations
- Ensure that Linux-native tools (such as Bash scripts or Linux command-line examples) are included and highlighted equally.
- Reorder the list or randomize the order to avoid always placing Windows tools first.
- Add explicit Linux examples or links to Linux-specific documentation.
- Clarify in the documentation that Azure CLI and Portal are cross-platform, and provide usage notes for both Windows and Linux environments.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-overview.md
...ocs/blob/main/articles/hdinsight/hdinsight-overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias toward Windows environments in the 'Business intelligence on HDInsight' section, where only Windows-based tools (Power Query, Microsoft Hive ODBC Driver, Excel integration) are mentioned or explicitly required. There are no Linux or cross-platform BI tool examples provided. Additionally, the development tools section lists Visual Studio and other Microsoft-centric tools before mentioning cross-platform options, and there is no mention of Linux alternatives or parity for BI integration.
Recommendations
- Include examples and guidance for connecting to HDInsight from BI tools available on Linux, such as Tableau, Qlik, or open-source alternatives (e.g., Apache Superset, DBeaver).
- Provide instructions for using ODBC/JDBC drivers on Linux and macOS, not just Windows.
- When listing development tools, give equal prominence to cross-platform IDEs (e.g., VS Code, IntelliJ, Eclipse) and clarify their OS compatibility.
- Explicitly state when a feature or tool is Windows-only, and offer Linux/macOS alternatives where possible.
- Add sample walkthroughs or links for BI/reporting integration from non-Windows environments.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-troubleshoot-guide.md
...ain/articles/hdinsight/hdinsight-troubleshoot-guide.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page lists several development tools (IntelliJ, Eclipse, VS Code, Visual Studio) for configuring Apache Spark applications, but only the Visual Studio tool is Windows-specific and is mentioned alongside cross-platform tools. There is a lack of explicit Linux command-line or shell examples, and the documentation does not provide parity in showing Linux-native troubleshooting steps or tools. The ordering of tools and examples sometimes places Windows-centric options (Visual Studio) before or alongside cross-platform ones, without clarifying platform support.
Recommendations
- Clearly indicate which tools are cross-platform and which are Windows-only (e.g., Visual Studio).
- Provide explicit Linux shell/command-line examples for common troubleshooting tasks, not just tool-based workflows.
- When listing tools, group or order them by platform (cross-platform first, then Windows-only), or clearly label them.
- Add more Linux-specific troubleshooting steps and highlight any differences in workflows between Windows and Linux environments.
- Ensure that all examples and guides are available for both Windows and Linux users, or provide equivalent alternatives.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-supported-node-configuration.md
...es/hdinsight/hdinsight-supported-node-configuration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell explicitly as the primary scripting tool for deploying HDInsight clusters, both in the introduction and in the note about VM SKU identifiers. There are no Linux shell (bash) examples or explicit mentions of Linux-native tools or workflows. The guidance assumes familiarity with PowerShell, and Linux alternatives are not provided or mentioned.
Recommendations
- Include explicit bash/Azure CLI examples alongside PowerShell references for deploying HDInsight clusters.
- Rephrase instructions to mention both PowerShell and bash equally (e.g., 'when creating deployment scripts using PowerShell or bash').
- Add notes or examples for Linux users, such as how to obtain VM SKU identifiers using bash or Azure CLI.
- Avoid assuming PowerShell as the default scripting environment; use neutral language or provide parity.
- Where possible, provide links to both Windows and Linux scripting documentation for Azure.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/interactive-query/apache-hadoop-connect-hive-power-bi-directquery.md
...ery/apache-hadoop-connect-hive-power-bi-directquery.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation assumes the use of Microsoft Power BI Desktop, which is only available for Windows, and does not mention or provide alternatives for Linux users. All instructions and screenshots are specific to Power BI Desktop, with no discussion of cross-platform or Linux-compatible visualization tools. The prerequisites and workflow are Windows-centric, and there is no guidance for users on Linux or macOS.
Recommendations
- Explicitly state that Power BI Desktop is Windows-only and mention this limitation in the prerequisites.
- Provide alternative instructions or recommendations for Linux users, such as using Power BI Service (web), Apache Zeppelin, Jupyter Notebooks, or other cross-platform BI tools.
- Include links or references to Linux-compatible visualization tools that can connect to Hive/HDInsight, such as Apache Superset, Tableau (if available), or open-source alternatives.
- Add a section comparing available visualization options for different operating systems, with step-by-step guides for at least one Linux-compatible tool.
- Ensure that future documentation includes parity in examples and screenshots for both Windows and Linux environments where possible.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-scaling-best-practices.md
...articles/hdinsight/hdinsight-scaling-best-practices.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as the first utility for scaling clusters, providing explicit PowerShell cmdlet examples, and referencing Windows-style paths in some command snippets. While Azure CLI and SSH/bash commands are included, the prominence and ordering of PowerShell and Windows tools suggest a Windows-centric approach. There is also a lack of explicit Linux-specific guidance or parity in some sections, such as not providing Linux command-line equivalents for all PowerShell actions.
Recommendations
- List Azure CLI before PowerShell in the utilities table, as CLI is cross-platform and more commonly used on Linux.
- Provide explicit Linux/bash command examples wherever PowerShell examples are given, ensuring parity.
- Avoid using Windows-style paths (e.g., %HBASE_HOME%\bin) in command snippets; use Linux-style paths or provide both.
- Clarify that all command-line examples (e.g., SSH, hadoop fs, hdfs dfsadmin) are intended for Linux environments, and provide any necessary Windows equivalents if relevant.
- Add a section or note highlighting Linux usage patterns and tools, ensuring Linux users feel equally supported.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/kafka/apache-kafka-introduction.md
.../articles/hdinsight/kafka/apache-kafka-introduction.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell and the Azure portal as primary management interfaces for scaling Kafka clusters, without mentioning Linux-native tools or CLI examples. There are no Linux shell or cross-platform CLI examples, and Windows-centric management patterns are presented first and exclusively.
Recommendations
- Include Azure CLI (az) examples for scaling and managing Kafka clusters, as it is cross-platform and widely used on Linux.
- Mention Linux-native management tools or interfaces (such as SSH, Bash, or REST API usage) alongside or before Windows-specific tools like PowerShell.
- Provide explicit Linux shell command examples for common tasks, ensuring parity with any PowerShell or portal instructions.
- Clarify that all management operations can be performed from Linux, macOS, or Windows, and link to relevant cross-platform documentation.
- Review and update all procedural sections to ensure Linux users are not excluded or made secondary in the workflow.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-livy-rest-interface.md
...es/hdinsight/spark/apache-spark-livy-rest-interface.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing command-line examples and environment variable usage in Windows syntax (e.g., 'set' for variables, Windows file paths like C:\Temp\input.txt), and by recommending Windows-specific approaches (such as using input files with Windows paths). There are no Linux/macOS equivalents for environment variables, file paths, or alternative tools, and the only file upload tool mentioned by name is AzCopy, which is Windows-centric.
Recommendations
- Provide parallel Linux/macOS examples for all command-line snippets, including environment variable setting (e.g., 'export clustername=CLUSTERNAME') and file paths (e.g., '/tmp/input.txt').
- When referencing input files, show both Windows (C:\Temp\input.txt) and Linux (/tmp/input.txt) path formats.
- Mention and provide examples for Linux-native tools for file upload (such as 'Azure CLI', 'hadoop fs', or 'scp'), not just AzCopy.
- Avoid language that recommends a Windows-specific approach as the default; instead, offer platform-neutral guidance or dual instructions.
- Explicitly state that the examples are shown for Windows and provide equivalent commands for Linux/macOS users.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/cluster-reboot-vm.md
...docs/blob/main/articles/hdinsight/cluster-reboot-vm.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for command-line operations and referencing Windows-centric tools first. There are no examples or instructions for performing the same tasks using Linux-native tools (such as Bash, Azure CLI, or SSH), which are commonly used in HDInsight clusters that often run on Linux VMs. The REST API section is platform-neutral, but the lack of Linux command-line parity is notable.
Recommendations
- Add equivalent examples using Azure CLI (az hdinsight ...) for listing and restarting nodes, as Azure CLI is cross-platform and widely used on Linux.
- Include Bash or shell script examples for interacting with the REST API, such as using curl or httpie, to demonstrate how Linux users can perform the same operations.
- Reorganize the documentation to present cross-platform or Linux-native options before or alongside PowerShell, rather than PowerShell first.
- Explicitly mention that the PowerShell examples are for Windows users and provide clear alternatives for Linux/macOS users.
- Consider referencing SSH-based troubleshooting or reboot commands for scenarios where the VM is still accessible via SSH.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/service-endpoint-policies.md
...b/main/articles/hdinsight/service-endpoint-policies.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples, but the CLI example is written in a way that uses Windows/PowerShell variable syntax (e.g., $variable), and the PowerShell example is given in full. There are no explicit Linux/bash-native examples, and the CLI example is not shown in a cross-platform shell style (e.g., bash arrays or environment variables). This may confuse or disadvantage Linux users, as the CLI example is not directly copy-pastable into a bash shell.
Recommendations
- Provide a true bash/Linux example for the Azure CLI commands, using bash variable syntax (e.g., export SUBSCRIPTION_ID=..., arrays with parentheses, etc.).
- Clarify which code blocks are for PowerShell and which are for bash, and ensure both are present where relevant.
- Avoid using PowerShell array syntax (e.g., [String[]]$resources = @(...)) in CLI examples; instead, show how to pass multiple --service-resources arguments in bash.
- Add a section or note specifically for Linux/macOS users, demonstrating the same workflow in a bash shell.
- Ensure the order of examples does not always present Windows/PowerShell first; consider alternating or presenting both in parallel.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-sales-insights-etl.md
...ain/articles/hdinsight/hdinsight-sales-insights-etl.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias, particularly in the section on triggering the Data Factory pipeline, where PowerShell is presented as the primary scripted method, with no equivalent Bash/Azure CLI example for Linux users. Power BI Desktop, a Windows-only tool, is the only visualization option described, and its use is assumed throughout. The documentation refers to Windows tools and patterns (PowerShell, Power BI Desktop) before or instead of cross-platform or Linux-native alternatives.
Recommendations
- Provide an Azure CLI or Bash example for triggering and monitoring the Data Factory pipeline, ensuring Linux users have a first-class scripted option.
- Explicitly mention that Power BI Desktop is Windows-only and suggest alternatives for Linux users, such as Power BI web, Azure Data Studio, or open-source BI tools.
- When presenting multiple options (e.g., scripting vs. portal), avoid listing Windows/PowerShell options first by default; consider parallel presentation or alternating order.
- Include notes or links to documentation for connecting to HDInsight from Linux or macOS environments, especially for visualization and data access.
- Audit for other sections where only Windows tools or workflows are described, and add Linux/macOS equivalents where possible.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/hdinsight-security-overview.md
...hdinsight/domain-joined/hdinsight-security-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows/Active Directory-centric approach to enterprise security in Azure HDInsight. It emphasizes Microsoft Entra Domain Services (formerly Azure AD DS) and Active Directory-based authentication as the primary method for identity and access management. PowerShell is mentioned as a client tool for cluster access, but there is no mention of Linux-native authentication mechanisms (such as LDAP, Kerberos outside of AD context, or integration with non-AD identity providers), nor are there examples or references to Linux command-line tools or workflows. The documentation does not provide parity for Linux-first or cross-platform environments, and Windows-centric tools and patterns are presented as the default or only option.
Recommendations
- Include examples and guidance for integrating with non-Active Directory identity providers, such as generic LDAP or MIT Kerberos, to support Linux-centric enterprises.
- Mention and provide examples for Linux-native client tools (e.g., SSH, curl, kinit, beeline, etc.) alongside or instead of PowerShell.
- Clarify whether authentication and access control features are compatible with Linux-based identity systems or if there are workarounds.
- Add explicit Linux command-line examples for common administrative and user tasks (e.g., connecting to clusters, submitting jobs, managing access).
- Balance references to Windows tools with equivalent Linux tools in all sections, especially where PowerShell or Windows authentication is mentioned.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-connect-excel-hive-odbc-driver.md
...hadoop/apache-hadoop-connect-excel-hive-odbc-driver.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily Windows-centric, providing only instructions and screenshots for Windows tools such as the ODBC Data Source Administrator and Excel on Windows. There are no Linux or cross-platform alternatives or instructions, and all steps assume a Windows environment.
Recommendations
- Add instructions for configuring ODBC data sources on Linux and macOS, including using unixODBC and relevant configuration files (e.g., odbc.ini).
- Provide examples for connecting to Hive from Excel on macOS (if supported) or from alternative spreadsheet tools available on Linux.
- Include command-line examples for setting up ODBC connections (e.g., using isql or similar tools) for non-Windows users.
- Mention and link to any cross-platform ODBC drivers or tools, if available.
- Clearly indicate platform-specific steps and provide parity where possible, or explicitly state if a feature is Windows-only.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/domain-joined-authentication-issues.md
...t/domain-joined/domain-joined-authentication-issues.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. In sections discussing how to find the sAMAccountName, Windows AD tools are mentioned before Linux/SAMBA alternatives, and the only explicit tool reference is to 'standard Windows AD tools.' There is no mention of Linux GUI tools or command-line alternatives for directory browsing, and the Windows approach is described in more detail. Some troubleshooting steps (e.g., password changes) reference the Azure portal, which is platform-neutral, but there are no PowerShell-specific commands or examples. However, Linux commands (e.g., kinit, net ads search, export KRB5_TRACE) are present, but not always introduced with parity to Windows methods.
Recommendations
- When listing ways to find sAMAccountName, mention Linux/SAMBA command-line methods before or alongside Windows tools.
- Provide explicit Linux GUI or CLI alternatives for browsing Active Directory (e.g., using 'ldbsearch', 'ldapsearch', or 'adcli').
- If referencing Windows AD tools, also reference equivalent Linux tools with example commands.
- Ensure that all troubleshooting steps that mention Windows-specific tools or portals also mention Linux-friendly methods where possible.
- Consider adding a table or section summarizing both Windows and Linux approaches for common administrative tasks.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-use-mapreduce-curl.md
...s/hdinsight/hadoop/apache-hadoop-use-mapreduce-curl.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing command-line examples that use Windows-specific syntax (e.g., 'set' for environment variables, caret '^' for line continuation, and Windows paths for jq). There are no explicit Linux/bash examples, and the instructions for using curl are tailored to Windows environments. PowerShell is also presented as a primary method, with no mention of bash or Linux shell equivalents. Tools and patterns (like jq path and environment variable setting) are shown only for Windows.
Recommendations
- Provide parallel Linux/bash examples for all curl commands, using 'export' for environment variables, backslash '\' for line continuation, and typical Linux jq paths (e.g., '/usr/bin/jq').
- Clearly separate Windows and Linux command blocks, labeling them accordingly.
- Avoid using Windows-specific syntax in generic sections, or provide both Windows and Linux alternatives.
- Mention bash or Linux shell as an equivalent to PowerShell for users on non-Windows systems.
- Include a note or table summarizing differences in command syntax and tool locations between Windows and Linux.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-on-premises-migration-best-practices-security-devops.md
...p-on-premises-migration-best-practices-security-devops.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows-centric bias by exclusively referencing Microsoft Entra Domain Services (formerly Azure AD DS), Active Directory, and related tooling for authentication, authorization, and cluster management. There are no examples or guidance for integrating with Linux-native identity providers (such as LDAP, MIT Kerberos, or FreeIPA), nor are there instructions for managing HDInsight clusters in environments that do not use Microsoft identity solutions. The documentation assumes a Windows/Active Directory environment as the default, omitting Linux-first or open-source alternatives.
Recommendations
- Provide equivalent guidance for integrating HDInsight clusters with Linux-native identity providers (e.g., OpenLDAP, FreeIPA, MIT Kerberos), including configuration steps and security best practices.
- Include examples and workflows for environments that do not use Microsoft Entra Domain Services or Active Directory, such as those using open-source directory services.
- Explicitly mention any limitations or requirements for non-Windows environments, and offer workarounds or alternatives where possible.
- Ensure that documentation sections referencing authentication, authorization, and cluster management do not assume Microsoft tooling as the only or primary option.
- Add Linux command-line examples (e.g., using SSH, kinit, or open-source tools) alongside or in place of Windows/PowerShell-centric instructions.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-etl-at-scale.md
...rticles/hdinsight/hadoop/apache-hadoop-etl-at-scale.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. Data ingestion into Azure Storage is described as typically done via PowerShell, the Azure Storage SDK, or AzCopy, with no mention of Linux-native tools or CLI workflows. PowerShell and .NET SDKs are referenced before cross-platform or Linux-friendly options. There is a lack of explicit Linux or bash command examples, and the ordering of tool mentions often puts Windows-centric tools first. While some open-source Hadoop tools are mentioned, the overall guidance and examples favor Windows environments.
Recommendations
- Include Linux-native and cross-platform CLI examples (e.g., Azure CLI, Bash scripts, Hadoop CLI tools) alongside or before PowerShell examples.
- Explicitly mention and provide examples for Linux-based ingestion tools, such as Azure CLI az storage commands, Hadoop fs commands, or Linux-compatible SDKs.
- When listing ingestion or orchestration tools, avoid putting Windows-centric tools (PowerShell, .NET SDK) first unless there is a technical reason; alternate or randomize order, or group by platform.
- Add sample commands or code snippets for Linux users, especially for common ingestion and orchestration tasks.
- Clarify which tools are cross-platform and which are Windows-only, to help users on Linux identify their best options.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/apache-domain-joined-create-configure-enterprise-security-cluster.md
...in-joined-create-configure-enterprise-security-cluster.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias throughout. All setup and configuration steps are described using Windows-centric tools and workflows, such as Remote Desktop, Server Manager, Microsoft Management Console (MMC), and PowerShell scripts. There are no examples or guidance for performing equivalent tasks on Linux-based systems or using cross-platform tools. The documentation assumes the use of Windows VMs and does not mention or provide alternatives for Linux environments, even though HDInsight clusters themselves run on Linux by default.
Recommendations
- Provide equivalent instructions for Linux environments, including how to set up and manage users, groups, and certificates using Linux tools (e.g., OpenLDAP, command-line utilities).
- Offer Bash/Azure CLI examples alongside PowerShell scripts for network and resource provisioning.
- Clarify which steps are Windows-specific and which can be performed from any OS, and provide cross-platform alternatives where possible.
- Include guidance for connecting to the domain controller and managing Entra ID from Linux or macOS clients, possibly using RDP alternatives or Azure portal exclusively.
- Document how to generate and manage certificates for LDAPS using OpenSSL and Linux-based certificate stores.
- Explicitly state any prerequisites or limitations if only Windows is supported for certain steps, and suggest workarounds or alternatives for Linux users.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/apache-domain-joined-architecture.md
...ght/domain-joined/apache-domain-joined-architecture.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples are provided exclusively in PowerShell, with no mention of Linux or cross-platform alternatives. The focus is on Windows-native tools (PowerShell modules, Active Directory, Microsoft Entra Domain Services), and there are no instructions or guidance for users on Linux or macOS. The documentation assumes a Windows-centric environment and does not address Linux administration scenarios.
Recommendations
- Provide equivalent command-line examples using Azure CLI and/or Bash scripts, which are cross-platform and commonly used on Linux.
- Mention and document how Linux administrators can perform required tasks, such as managing service principals and policies, using non-Windows tools.
- Clarify whether any steps require Windows specifically, and if so, suggest workarounds or alternatives for Linux/macOS users.
- Include references to Linux-compatible tools (e.g., Azure CLI, REST API) alongside PowerShell, and avoid assuming the user is on Windows.
- Add a section or notes for Linux/macOS users to ensure parity and inclusivity.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/manage-clusters-runbooks.md
...ob/main/articles/hdinsight/manage-clusters-runbooks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively uses PowerShell for all scripting and automation examples, with no mention of alternatives such as Python or Bash. All runbook examples, module installations, and code snippets are PowerShell-based, and the workflow assumes familiarity with Windows-centric tools and patterns. There are no Linux-native scripting examples or references to cross-platform automation options, and the 'Next step' also points to a PowerShell-specific guide.
Recommendations
- Provide equivalent examples using Python runbooks (supported in Azure Automation) for creating and deleting HDInsight clusters.
- Include Bash/CLI examples where possible, especially for users who may prefer Linux-native scripting.
- Mention and link to Azure CLI and REST API documentation as alternative, cross-platform ways to automate HDInsight cluster management.
- Balance the order of presentation so that PowerShell and Linux-friendly options are introduced together, or alternate which is presented first.
- Clarify that PowerShell runbooks can be authored and executed from non-Windows platforms using PowerShell Core, and provide guidance for Linux/macOS users.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-using-apache-hive-as-an-etl-tool.md
...doop/apache-hadoop-using-apache-hive-as-an-etl-tool.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools and workflows (such as SQL Server Integration Services, Excel, PowerShell, and Azure Logic Apps) for ETL orchestration and data loading. There is a lack of Linux/Unix command-line examples, and Linux-native tools or workflows are not mentioned or are referenced only after Windows equivalents. The documentation does not provide Linux-specific guidance or parity in examples.
Recommendations
- Include Linux/Unix command-line examples for orchestrating Hive ETL workflows (e.g., using Bash scripts, cron jobs, or Apache Oozie).
- Mention and provide examples for Linux-native tools for data loading and orchestration, such as Apache NiFi, Airflow, or Sqoop CLI usage from Linux.
- When listing tools (e.g., SSIS, Excel, PowerShell), also mention Linux alternatives (e.g., csvkit, pandas, shell scripting, or open-source ETL tools).
- Avoid presenting Windows tools and workflows first or exclusively; provide parallel Linux options or structure sections by platform.
- Demonstrate how to automate Hive queries using Linux-native scheduling (cron) or workflow tools (Oozie, Airflow), not just PowerShell or Logic Apps.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/disk-encryption.md
...e-docs/blob/main/articles/hdinsight/disk-encryption.md
High 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 used for several automation examples, including ARM template deployment and enabling encryption at host, without providing equivalent Bash or Linux shell examples. Windows-centric tools and patterns (e.g., PowerShell cmdlets, references to Undo-AzKeyVaultKeyRemoval) are mentioned, sometimes before or instead of cross-platform or Linux-native alternatives. There are no explicit Linux shell (bash) command examples for key operations, and the documentation assumes familiarity with Windows tooling.
Recommendations
- For every PowerShell example, provide an equivalent Bash (Linux shell) example, especially for ARM template deployment and cluster creation.
- When referencing recovery or management tools (e.g., Undo-AzKeyVaultKeyRemoval), also mention and provide examples for the Azure CLI or REST API equivalents.
- Avoid assuming the use of Windows tools by default; clarify that both Windows and Linux users are supported and provide parity in instructions.
- Where possible, use Azure CLI as the primary example, as it is cross-platform, and supplement with both PowerShell and Bash examples.
- Explicitly mention that HDInsight clusters are Linux-based by default, and provide guidance for Linux users where relevant.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-use-hive-dotnet-sdk.md
.../hdinsight/hadoop/apache-hadoop-use-hive-dotnet-sdk.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation is heavily oriented toward Windows users, requiring a Windows client and Visual Studio, and provides only C#/.NET and NuGet/PowerShell-based instructions. There are no equivalent Linux or cross-platform examples, and Linux users are referred elsewhere rather than given parity in this guide.
Recommendations
- Provide equivalent instructions and code samples for Linux users, such as using .NET Core/SDK on Linux and alternative editors (e.g., VS Code, JetBrains Rider, or command-line tools).
- Include Linux-specific setup steps, such as installing the .NET SDK and running the sample from the terminal.
- Replace or supplement PowerShell/NuGet Package Manager Console commands with cross-platform .NET CLI commands (e.g., 'dotnet add package').
- Clarify which steps are Windows-specific and offer direct alternatives for Linux/macOS users within the same article, rather than referring them to other documentation.
- Highlight cross-platform compatibility of the .NET SDK where applicable, and provide troubleshooting tips for non-Windows environments.