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 401-425 of 867 flagged pages
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 First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is used for ARM template deployment and for enabling encryption at host, with no equivalent Bash or Linux shell examples. PowerShell is mentioned before Azure CLI in some sections, and Windows-centric tools and patterns (such as PowerShell cmdlets and references to Undo-AzKeyVaultKeyRemoval) are used without always providing Linux or cross-platform alternatives. There are no explicit Linux shell script examples for common tasks, and the documentation assumes familiarity with Windows tooling.
Recommendations
- Provide Bash or Linux shell script equivalents for all PowerShell examples, especially for ARM template deployments and enabling encryption at host.
- When listing command-line options, present Azure CLI and Bash examples before or alongside PowerShell to ensure Linux parity.
- Include references to Linux-native tools or commands where possible, and avoid assuming the user is on Windows.
- For recovery operations (e.g., key recovery), provide both PowerShell and Azure CLI commands, and clarify which are cross-platform.
- Explicitly state that all features and procedures are supported on Linux-based clusters and environments, and provide guidance for Linux users where workflows may differ.
Create Pull Request
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/apache-domain-joined-run-hive.md
...insight/domain-joined/apache-domain-joined-run-hive.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Windows-based tools and workflows (Excel, ODBC driver, Windows authentication dialogs) for testing and accessing Hive data. There are no Linux or cross-platform alternatives provided for connecting to Hive or verifying Ranger policies, and the instructions assume the user is operating from a Windows environment.
Recommendations
- Include equivalent Linux-based instructions for connecting to Hive, such as using Beeline, Hive CLI, or DBeaver on Linux.
- Provide examples of using open-source ODBC/JDBC clients available on Linux (e.g., isql, SQuirreL SQL, DBeaver) to test Ranger policies.
- Show how to import data into LibreOffice Calc or other cross-platform spreadsheet tools using Hive ODBC/JDBC drivers.
- When describing authentication dialogs or connection steps, note differences for non-Windows environments or provide screenshots for Linux/macOS where applicable.
- Reorder or parallelize sections so that Linux and Windows workflows are presented together, rather than defaulting to Windows-first.
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-based examples or instructions for these steps, and Windows patterns/tools are mentioned before any Linux alternatives (if at all).
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 other standard Linux tools to verify domain connectivity and LDAP access.
- Mention Linux-based tools (e.g., ldapsearch, openssl) wherever Windows tools (e.g., ldp.exe, PowerShell) are referenced.
- Ensure that examples and instructions are presented in a cross-platform manner, or clearly indicate which steps are OS-specific.
- Add a section or callouts for Linux users, especially for common administrative tasks like joining a domain, testing connectivity, and troubleshooting.
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. All setup and configuration steps assume the use of Windows Server VMs, Windows domain controllers, and Windows-specific tools (such as MMC, Server Manager, and RDP). PowerShell is the only scripting language used for automation, and no Linux or cross-platform alternatives are provided for any step. There are no instructions or examples for performing these tasks from a Linux environment or using cross-platform tools.
Recommendations
- Provide equivalent instructions for setting up the required environment using Linux VMs, including domain controller alternatives (e.g., Samba/FreeIPA) where feasible.
- Include examples using Azure CLI (which is cross-platform) instead of only PowerShell for resource provisioning and configuration.
- Offer guidance for connecting to VMs using SSH (for Linux) in addition to RDP.
- Document how to manage users, groups, and certificates using cross-platform or Linux-native tools (e.g., ldapadd, openssl, certtool).
- Clarify which steps are Windows-only and provide Linux alternatives or workarounds where possible.
- Add a section summarizing platform requirements and explicitly state if only Windows is supported for certain features, with rationale.
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 bias toward Windows environments. It exclusively references Microsoft-centric identity solutions (Active Directory, Microsoft Entra Domain Services), and all command-line examples are provided only in PowerShell. There is no mention of Linux-based tools or command-line equivalents, nor are there any Linux/Unix shell examples for managing authentication or domain integration. The documentation assumes a Windows-first approach, both in terminology and tooling, with no guidance for Linux administrators.
Recommendations
- Provide equivalent Linux/Unix shell commands (e.g., using Azure CLI or REST API) alongside PowerShell examples for all administrative tasks.
- Include references to cross-platform tools (such as Azure CLI) and clarify which steps can be performed on non-Windows systems.
- Explicitly state the platform requirements for each step, and offer alternatives for Linux/macOS users where possible.
- Mention and, if possible, document how Linux-based clients or administrators can interact with HDInsight clusters using their native tools.
- Balance the order of presentation by not always listing Windows/PowerShell tools first, and ensure Linux options are equally visible.
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 page shows a mild Windows bias. In the section on finding the sAMAccountName, Windows AD tools are mentioned before Linux/SAMBA commands, and the Windows approach is described as 'standard'. There is no mention of Linux equivalents for browsing AD except for a brief reference to SAMBA commands, which are less detailed. Elsewhere, there are no explicit PowerShell or Windows command-line examples, but the overall troubleshooting flow assumes familiarity with Windows-centric tools and patterns, with Linux/SSH/kinit only appearing in later sections.
Recommendations
- Present Linux and Windows methods for directory browsing and user attribute discovery side-by-side, or give equal prominence to both.
- Provide explicit Linux command examples (e.g., using ldapsearch, getent, or samba-tool) for querying user attributes in addition to Windows AD tools.
- Avoid describing Windows tools as 'standard' without mentioning that equivalent Linux tools exist.
- Where SSH/kinit is mentioned, clarify that these are standard on Linux and provide Windows equivalents (e.g., using MIT Kerberos for Windows or WSL).
- Ensure that all troubleshooting steps and examples are cross-platform, or clearly indicate when a step is OS-specific.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/identity-broker.md
...in/articles/hdinsight/domain-joined/identity-broker.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation exhibits a Windows bias by referencing Windows Server VMs as the platform for the ID Broker node, mentioning domain-joining to Microsoft Entra Domain Services (a Windows-centric pattern), and omitting explicit Linux-focused setup or troubleshooting steps. No Linux-specific tools, commands, or patterns are provided, and the only command-line example is a generic curl command. There is no mention of Linux administration or parity in cluster node OS choices, and the documentation assumes a Windows-based Active Directory environment.
Recommendations
- Explicitly state whether the HDInsight ID Broker node can run on Linux-based VMs, or clarify if Windows Server is a hard requirement.
- Provide Linux-specific examples for SSH, kinit, and administrative tasks, including troubleshooting steps for common Linux environments.
- Mention Linux equivalents or alternatives for domain-joining and authentication infrastructure, if available.
- Include references to Linux-based tools (such as command-line utilities, editors, or configuration files) where appropriate.
- Clarify whether the described authentication flows and requirements differ for clusters running on Linux nodes versus Windows nodes.
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 demonstrates a Windows bias by emphasizing Active Directory (a Windows-centric technology) and Microsoft Entra Domain Services for authentication, with no mention of Linux-native alternatives (such as LDAP or MIT Kerberos). The authentication examples reference PowerShell as a client tool, but do not mention Linux command-line tools or SSH-based workflows. The documentation does not provide Linux-specific guidance or parity in examples, and Windows tools/patterns are referenced exclusively or before any Linux equivalents.
Recommendations
- Include Linux-native authentication options (such as integration with OpenLDAP or MIT Kerberos) or clarify if only Active Directory is supported.
- Provide examples of connecting to HDInsight clusters using Linux command-line tools (e.g., SSH, curl, or Linux-based JDBC/ODBC clients), not just PowerShell.
- Mention Linux-based administrative workflows and tools alongside Windows/PowerShell examples.
- Clarify any platform-specific requirements or limitations, and ensure that Linux users are not left without guidance.
- If PowerShell is referenced, also provide equivalent Bash or shell commands for Linux environments.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/ldap-sync.md
...lob/main/articles/hdinsight/domain-joined/ldap-sync.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools (such as ldp.exe and sAMAccountName), describing patterns and terminology specific to Microsoft Active Directory, and omitting Linux-native LDAP tools (like ldapsearch or openldap utilities) in examples or troubleshooting steps. The use of Samba/Winbind is mentioned, but no Linux alternatives or parity examples are provided. When suggesting how to test LDAP filters, Windows tools are mentioned first or exclusively.
Recommendations
- Include Linux-native LDAP tools (e.g., ldapsearch, ldaptool) alongside or before Windows tools like ldp.exe when demonstrating how to test LDAP filters.
- Provide example commands for both Windows (PowerShell, ldp.exe) and Linux (shell, ldapsearch) environments when discussing troubleshooting or configuration validation.
- Clarify that sAMAccountName is a Microsoft AD attribute and, if relevant, mention the equivalent or analogous attributes in other LDAP implementations.
- Where Samba/Winbind is referenced, briefly explain its role in projecting Windows group memberships onto Linux systems, and mention any Linux-native alternatives if applicable.
- Ensure that log file locations and configuration steps are described in a platform-agnostic way, or provide both Linux and Windows paths/examples where they differ.
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: all setup and usage instructions assume a Windows environment, referencing Windows-specific tools (ODBC Data Source Administrator, Excel, Windows menus) and providing no guidance for Linux or cross-platform scenarios. There are no Linux or macOS examples or alternatives mentioned for connecting to HDInsight via ODBC from non-Windows systems.
Recommendations
- Add instructions for configuring the Microsoft Hive ODBC driver on Linux and macOS, including how to set up DSNs using unixODBC or iODBC.
- Provide examples for connecting to HDInsight from Excel on macOS (if supported) or from alternative spreadsheet tools available on Linux.
- Mention and link to any cross-platform ODBC driver options, or clarify platform limitations if the driver is Windows-only.
- If Excel integration is only supported on Windows, explicitly state this and suggest alternative BI tools for Linux/macOS users.
- Reorder sections or add parallel Linux/macOS instructions so that Windows is not always presented first or exclusively.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-connect-hive-jdbc-driver.md
...sight/hadoop/apache-hadoop-connect-hive-jdbc-driver.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing only Windows-specific paths (e.g., C:\Program Files\squirrel-sql-4.0.0\lib), referencing Windows tools and conventions (such as using .cmd for command-line examples), and omitting explicit Linux/Mac instructions for tasks like locating SQuirreL SQL installation directories or running commands. There are no Linux-specific examples or notes, and Windows patterns are assumed throughout.
Recommendations
- Provide equivalent Linux/Mac instructions alongside Windows-specific steps, especially for file paths (e.g., /opt/squirrel-sql/lib or ~/squirrel-sql/lib).
- Use cross-platform command examples or clearly label which OS each command applies to (e.g., use generic 'scp' commands and clarify any OS-specific syntax).
- Include screenshots or instructions for Linux/Mac environments where UI or file navigation is involved.
- Explicitly mention that SQuirreL SQL and Java are cross-platform, and provide any OS-specific installation or troubleshooting notes.
- When referencing environment variables or commands, show both Windows (cmd/PowerShell) and Linux (bash) syntax.
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 moderate Windows bias. Data ingestion into Azure Storage is described as typically being performed via PowerShell, the Azure Storage SDK, or AzCopy, all of which are Windows-centric tools or are presented as such. There is no mention of Linux-native tools (e.g., Azure CLI, Bash scripts, or Linux file utilities) for these tasks, nor are Linux-specific examples provided. The ordering of tools and examples tends to favor Windows approaches, and Linux alternatives are either omitted or only implied. This may leave Linux users without clear guidance for common ETL operations.
Recommendations
- Explicitly mention and provide examples for Linux-native tools such as Azure CLI and Bash scripting for data ingestion and management.
- When listing ingestion tools (e.g., PowerShell, SDK, AzCopy), include Azure CLI and note cross-platform compatibility for each tool.
- Provide code snippets or command-line examples for both Windows (PowerShell) and Linux (Bash/Azure CLI) wherever possible.
- Avoid presenting Windows tools or workflows first by default; alternate or parallelize the presentation of Windows and Linux options.
- Clarify which tools are cross-platform (e.g., AzCopy, Azure CLI) and provide installation/use instructions for both Windows and Linux environments.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-use-hive-visual-studio.md
...insight/hadoop/apache-hadoop-use-hive-visual-studio.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes how to use Visual Studio and its Data Lake tools to run Hive queries on Azure HDInsight, with all instructions, screenshots, and workflows centered around Windows-only tooling. There are no examples or guidance for performing equivalent tasks on Linux or cross-platform environments, nor are alternative tools (such as VS Code, command-line, or Linux-based editors) mentioned.
Recommendations
- Provide equivalent instructions and examples for running Hive queries using cross-platform tools such as VS Code (with relevant extensions), Azure CLI, or directly via SSH and Hive command-line on Linux.
- Mention and link to Linux-compatible workflows, such as using Apache Beeline, Hive CLI, or Jupyter Notebooks for Hive queries on HDInsight.
- Reorganize the documentation to present cross-platform or Linux-native options alongside or before Windows/Visual Studio-specific instructions.
- Include screenshots and step-by-step guides for Linux users, ensuring parity in detail and clarity with the Visual Studio examples.
- Explicitly state the platform limitations of Visual Studio tooling and direct users to alternative resources if they are on Linux or macOS.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-connect-excel-power-query.md
...ight/hadoop/apache-hadoop-connect-excel-power-query.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows environments, specifically requiring a Windows workstation and Microsoft Excel with Power Query, both of which are not available on Linux. There are no instructions or alternatives provided for Linux users, and all tooling and workflows are based on Windows-only software.
Recommendations
- Acknowledge the Windows-only nature of Excel and Power Query, and explicitly state that the workflow is not available on Linux or macOS.
- Provide alternative methods for Linux users to access and analyze HDInsight/Hadoop data, such as using open-source BI tools (e.g., Apache Zeppelin, Jupyter Notebooks, LibreOffice Calc with ODBC/JDBC connectors).
- Include links or references to cross-platform tools and workflows for data import and analysis.
- If possible, add a section or a separate article for Linux/macOS users, outlining equivalent data access and analysis options.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-develop-deploy-java-mapreduce-linux.md
...p/apache-hadoop-develop-deploy-java-mapreduce-linux.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows-first bias: all local environment setup commands (directory creation, file deletion, file editing) are provided only in Windows Command Prompt (cmd) syntax, and Notepad is used as the default editor. There are no equivalent Linux/macOS shell commands or editor suggestions, despite the fact that HDInsight clusters themselves run on Linux and many developers use Linux or macOS. The only Unix-style commands appear later, once the user is SSHed into the cluster, but the local development workflow is Windows-centric.
Recommendations
- Provide equivalent Linux/macOS shell commands (e.g., mkdir, cd, rm) alongside Windows cmd commands for all file and directory operations.
- Suggest cross-platform or Linux-native text editors (e.g., nano, vim, gedit, VS Code) in addition to Notepad.
- Clearly indicate when a command is for Windows or Linux/macOS, using tabs or callouts to separate instructions.
- Consider using platform-agnostic instructions (e.g., 'open pom.xml in your preferred text editor') where possible.
- Explicitly mention that the workflow is cross-platform and provide parity in examples for both environments.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-connect-hive-power-bi.md
...dinsight/hadoop/apache-hadoop-connect-hive-power-bi.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented toward Windows environments, focusing exclusively on Microsoft Power BI Desktop (a Windows-only application) and the ODBC driver setup, with no mention of Linux-compatible BI tools or workflows. There are no Linux-specific instructions, nor are alternative cross-platform tools or methods discussed. The prerequisites and step-by-step instructions assume a Windows desktop environment, and the only visualization tool mentioned is Power BI Desktop, which is not available on Linux.
Recommendations
- Include instructions or references for connecting to Hive from cross-platform or Linux-native BI tools (e.g., Tableau, Apache Superset, or DBeaver).
- Explicitly state that Power BI Desktop is Windows-only, and suggest alternatives for Linux users.
- Provide example workflows for Linux users, such as using ODBC/JDBC-compatible tools available on Linux to connect to Hive data.
- Reorder or supplement the documentation to present Linux-compatible options alongside Windows options, rather than only after or not at all.
- Mention how to install and configure the Hive ODBC/JDBC driver on Linux, if supported.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-dotnet-csharp-mapreduce-streaming.md
...oop/apache-hadoop-dotnet-csharp-mapreduce-streaming.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools and workflows, such as Visual Studio and PowerShell, and by omitting Linux-native alternatives for key steps like building and uploading executables. While there is an SSH section for running jobs, the prerequisites and upload instructions assume a Windows development environment and do not provide equivalent guidance for Linux users.
Recommendations
- Add instructions for building the C# mapper and reducer using the 'dotnet' CLI or Mono's 'mcs' compiler on Linux.
- Provide examples of uploading files to HDInsight storage using cross-platform tools like Azure CLI, AzCopy, or Hadoop's hdfs dfs command.
- Include Linux-native editor/IDE options (e.g., VS Code, JetBrains Rider, or command-line editors) alongside Visual Studio.
- Present PowerShell and Bash (or Azure CLI) job submission and result retrieval examples side-by-side, rather than only after the Windows/PowerShell workflow.
- Reorder sections or provide parallel tracks so that Linux and Windows users can easily follow platform-appropriate instructions.
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 page is heavily oriented towards Windows users. It explicitly states that the steps must be performed from a Windows client and only provides instructions for using Visual Studio and the .NET SDK, both of which are primarily Windows-centric. There are no Linux or cross-platform examples, and the only mention of Linux is a pointer to a different article. The use of the NuGet Package Manager Console and references to pressing F5 further reinforce the Windows/Visual Studio bias.
Recommendations
- Provide equivalent instructions for Linux users, such as using .NET Core/SDK on Linux with VS Code or JetBrains Rider.
- Include command-line examples for installing the SDK and running the application on Linux (e.g., using dotnet CLI).
- Offer sample code and steps for submitting Hive queries from non-Windows environments, or at least link directly to such instructions.
- Clarify which parts of the process are Windows-specific and which can be performed cross-platform.
- If the .NET SDK is truly Windows-only, state this clearly and suggest alternative SDKs or tools for Linux users.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-ambari-troubleshoot-heartbeat-issues.md
.../hadoop/apache-ambari-troubleshoot-heartbeat-issues.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides mostly Linux/Unix-style command examples for troubleshooting Ambari heartbeat issues, but when it comes to disabling Azure Monitor logging, it only references the PowerShell cmdlet (Disable-AzHDInsightMonitoring) without mentioning an equivalent Azure CLI or REST API method. This introduces a Windows/PowerShell bias, as it assumes users have access to or prefer PowerShell, which is more common on Windows platforms. There is also no mention of how to perform this step on Linux or via cross-platform tools.
Recommendations
- Include Azure CLI and/or REST API examples for disabling Azure Monitor logging, not just the PowerShell cmdlet.
- Clarify that the PowerShell cmdlet can be run on any platform with PowerShell Core, or provide guidance for Linux users.
- Wherever possible, provide both Windows/PowerShell and Linux/CLI examples for administrative tasks.
- Add a note about platform compatibility for all commands, especially those that are platform-specific.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-hive-java-udf.md
...ticles/hdinsight/hadoop/apache-hadoop-hive-java-udf.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias: all setup and file manipulation commands use Windows Command Prompt (cmd) syntax, file paths are Windows-style, and Notepad is used as the default editor. The troubleshooting section provides only PowerShell solutions for line ending issues. There are no equivalent Linux/bash commands or instructions, despite HDInsight clusters being Linux-based.
Recommendations
- Provide parallel Linux/bash command examples for all steps (e.g., mkdir, cd, rm -rf, nano/vim for editing files).
- Include Linux file path examples alongside Windows paths.
- Offer troubleshooting steps using Linux tools (e.g., dos2unix, sed) for line ending issues.
- State explicitly that the instructions apply to both Windows and Linux, and indicate which commands are for which OS.
- Consider presenting Linux examples first, given that HDInsight clusters are Linux-based.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-hive-pig-udf-dotnet-csharp.md
...ght/hadoop/apache-hadoop-hive-pig-udf-dotnet-csharp.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively using Visual Studio (a Windows-centric IDE) for all development, build, and deployment steps. It recommends Windows tools (Visual Studio, Data Lake Tools for Visual Studio) and provides detailed, step-by-step instructions for these, while omitting equivalent Linux-native workflows (e.g., using Mono on Linux, building with dotnet CLI or msbuild, uploading via Azure CLI, or running jobs via SSH). Although the document states that HDInsight clusters are Linux-based and briefly mentions SSH for running Pig jobs, it does not provide Linux-based development or deployment examples, nor does it mention cross-platform alternatives in the main workflow.
Recommendations
- Provide parallel instructions for Linux users, including how to build C# projects using the dotnet CLI or msbuild on Linux with Mono.
- Include examples of uploading files to HDInsight using Azure CLI or azcopy, not just Visual Studio/Data Lake Tools.
- Demonstrate how to run Hive queries using Azure CLI, Beeline, or SSH, instead of only through Visual Studio.
- Mention and show how to use cross-platform editors like VS Code or JetBrains Rider, and clarify which steps are Windows-specific.
- Explicitly state that Visual Studio steps are optional and provide equivalent command-line or Linux-native alternatives.
- Add a section or callouts for Mac/Linux users, ensuring parity in development, deployment, and job submission workflows.
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 bias towards Windows-centric tools and patterns. It exclusively references Microsoft Entra Domain Services (formerly Azure Active Directory Domain Services), Active Directory, and related Windows authentication and management paradigms. There are no examples or guidance for Linux-native identity management (such as MIT Kerberos, OpenLDAP, or integration with Linux-based authentication systems). All security and RBAC examples are framed in terms of Windows/AD concepts, and there is no mention of Linux command-line tools or patterns for cluster management or security.
Recommendations
- Include equivalent guidance for organizations using Linux-native identity providers (e.g., MIT Kerberos, OpenLDAP) and describe how to integrate these with HDInsight where possible.
- Provide examples or references for configuring HDInsight security and RBAC using Linux tools and authentication mechanisms.
- When listing steps or options, mention Linux-based approaches alongside or before Windows/AD-based ones to avoid the impression that only Windows-centric solutions are supported.
- Clarify whether HDInsight supports non-AD authentication and, if so, provide documentation or links for those scenarios.
- Add sample commands or scripts using Linux shell (bash) for common administrative tasks, not just Windows/AD tools.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-on-premises-migration-best-practices-infrastructure.md
...op-on-premises-migration-best-practices-infrastructure.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the 'Customize HDInsight configs using Bootstrap' section, where only a PowerShell (Windows-centric) example is provided for cluster configuration. There is no equivalent Bash/CLI or Linux-native example, despite HDInsight clusters being Linux-based by default. The PowerShell example is also presented before any mention of Linux-native tooling. Other sections reference Linux (e.g., edge nodes), but the only code sample is Windows-oriented, and there is a lack of parity in scripting guidance for Linux users.
Recommendations
- Provide equivalent Bash/Azure CLI examples alongside PowerShell for all cluster configuration tasks, especially in the 'Customize HDInsight configs using Bootstrap' section.
- Explicitly mention that HDInsight clusters are Linux-based by default and highlight Linux-native management options (e.g., Azure CLI, Bash scripting, REST API) before or alongside Windows/PowerShell options.
- Ensure that all code samples and automation guidance are available for both Windows and Linux users to avoid platform bias.
- Where PowerShell is referenced, add a note or link to corresponding Linux/CLI documentation.
- Review other sections for subtle prioritization of Windows tools or terminology and ensure Linux parity throughout.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-use-mapreduce-dotnet-sdk.md
...sight/hadoop/apache-hadoop-use-mapreduce-dotnet-sdk.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented towards Windows users: it explicitly states that the steps must be performed from a Windows client, requires Visual Studio (a Windows-centric IDE), and uses PowerShell/NuGet Package Manager Console for package installation. There are no Linux or cross-platform alternatives or examples provided for developing or running the .NET SDK application.
Recommendations
- Provide equivalent instructions for Linux and macOS users, including how to set up a .NET development environment using VS Code or JetBrains Rider.
- Include .NET CLI commands (e.g., 'dotnet add package') as alternatives to the NuGet Package Manager Console.
- Clarify which steps are Windows-specific and which are cross-platform, and provide a clear path for Linux users to follow.
- Offer guidance on running and debugging .NET SDK applications on Linux (e.g., using Mono or .NET Core/5+/6+).
- Remove or rephrase the note that restricts the article to Windows clients, or provide a parallel Linux workflow.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-use-sqoop-curl.md
...icles/hdinsight/hadoop/apache-hadoop-use-sqoop-curl.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a clear Windows bias by providing only Windows command prompt examples (using 'set' for environment variables and Windows-style variable syntax), referencing Windows-specific jq binary paths, and not offering equivalent Linux/macOS shell examples. The prerequisites and command instructions assume a Windows environment, with no parallel bash or POSIX shell commands provided. Additionally, tools like SQL Server Management Studio and Visual Studio Code are mentioned as SQL clients, with no mention of common Linux alternatives.
Recommendations
- Provide parallel Linux/macOS examples for all command-line instructions, using bash syntax (e.g., 'export VAR=value', '$VAR' variable expansion).
- Reference Linux-compatible jq usage (e.g., 'jq .status.state' instead of a Windows path to the binary).
- Mention Linux-friendly SQL clients (e.g., sqlcmd, DBeaver, Azure Data Studio) alongside Windows tools.
- Explicitly state when an example is Windows-specific and offer a corresponding Linux/macOS alternative immediately after.
- Add a note or table summarizing environment variable syntax differences between Windows and Linux/macOS.