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 376-400 of 867 flagged pages
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-use-sqoop-dotnet-sdk.md
...hdinsight/hadoop/apache-hadoop-use-sqoop-dotnet-sdk.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio and .NET, with all code samples in C#. Instructions reference Windows-centric tools (Visual Studio, NuGet Package Manager Console) and workflows. There are no examples or guidance for Linux or cross-platform development environments, nor are alternative tools or command-line approaches mentioned. The only mention of Linux is in the limitations section, which focuses on feature gaps rather than usage guidance.
Recommendations
- Provide equivalent instructions and code samples for Linux and macOS users, such as using .NET Core/SDK and VS Code or JetBrains Rider as alternatives to Visual Studio.
- Include command-line examples for running Sqoop jobs using Bash or cross-platform .NET CLI, not just through Visual Studio and C#.
- Mention and demonstrate how to install the required SDKs and dependencies on Linux (e.g., using apt, yum, or dotnet CLI).
- Clarify which steps are platform-specific and offer alternatives for non-Windows users.
- Consider including Python or Java examples, which are more common in cross-platform and Linux-based big data environments.
Create Pull Request
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/Visual Studio-centric workflow, with all project creation, building, uploading, and job submission steps described using Visual Studio and Azure tools that are primarily Windows-based. While there is a brief mention of SSH for Pig jobs, there are no Linux-native or cross-platform alternatives for building, uploading, or running jobs, and no command-line or non-Visual Studio workflows are provided. Linux is only referenced as the HDInsight cluster OS, not as a development or client environment.
Recommendations
- Provide equivalent instructions for creating, building, and packaging the C# UDFs using cross-platform tools such as the dotnet CLI and MonoDevelop, which are available on Linux and macOS.
- Include examples of uploading .exe files to HDInsight storage using Azure CLI and/or azcopy, with command-line instructions suitable for Linux/macOS.
- Demonstrate how to submit Hive queries and Pig jobs using Azure CLI, SSH, or other cross-platform methods, not just through Visual Studio.
- Reorder or parallelize instructions so that Windows/Visual Studio and Linux/cross-platform workflows are presented equally, or at least mention Linux alternatives alongside Windows steps.
- Explicitly state that all steps can be performed from Linux/macOS, and provide guidance for users who do not have access to Visual Studio or Windows.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-using-phoenix-query-server-rest-sdk.md
...se/apache-hbase-using-phoenix-query-server-rest-sdk.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively providing installation instructions using the Visual Studio NuGet Package Manager Console (a Windows-centric tool), and all code examples are in C#/.NET, which is most commonly used on Windows. There are no instructions or examples for installing or using the SDK on Linux or macOS, nor any mention of cross-platform command-line alternatives. The documentation assumes the user is operating in a Windows/.NET environment, omitting Linux-native workflows or tools.
Recommendations
- Provide installation instructions using the dotnet CLI (e.g., 'dotnet add package Microsoft.Phoenix.Client'), which is cross-platform and works on Linux, macOS, and Windows.
- Explicitly mention that the SDK and examples work on Linux and macOS if supported, and provide any prerequisites or differences for those platforms.
- Include at least one example of running the SDK from a Linux shell or in a cross-platform .NET Core project.
- If the SDK is Windows-only, clearly state this limitation early in the documentation.
- Avoid referencing only Windows-specific tools (like Visual Studio NuGet Package Manager Console) as the primary installation method; present cross-platform alternatives first or alongside.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/hdinsight-use-hive.md
...b/main/articles/hdinsight/hadoop/hdinsight-use-hive.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation generally aims for cross-platform coverage but exhibits some Windows bias. Windows-specific tools (Visual Studio, PowerShell, SSIS) are mentioned as primary options, sometimes before or more prominently than Linux equivalents. PowerShell is listed as a method for running Hive queries, but there is no equivalent Bash or Linux shell example. Integration with Windows-centric tools like SQL Server Integration Services is described in detail, while Linux-native scheduling or orchestration tools (other than Oozie) are not highlighted. In some cases, Windows is listed first or exclusively in client OS support.
Recommendations
- Add explicit Linux shell (Bash) and macOS command-line examples for running Hive queries, especially where PowerShell is mentioned.
- Ensure parity in tool recommendations: for every Windows tool (e.g., Visual Studio, PowerShell), mention and provide equal detail for cross-platform or Linux-native alternatives (e.g., IntelliJ IDEA, VS Code, Bash scripts).
- When listing client operating systems, avoid putting Windows first unless there is a technical reason; use alphabetical or neutral ordering.
- Expand the scheduling section to include Linux-native options such as cron, Airflow, or other workflow tools commonly used in Linux environments.
- Where possible, provide code snippets or walkthroughs that are platform-agnostic or include both Windows and Linux/macOS variants.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-administer-use-dotnet-sdk.md
...icles/hdinsight/hdinsight-administer-use-dotnet-sdk.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 by providing only PowerShell commands for package installation, referencing Windows-specific tools and patterns (such as PowerShell client GUID and Windows-style prompts), and lacking equivalent Linux or cross-platform examples for setup and management. The only shell command example for HBase uses Windows batch syntax, and there are no Bash or Linux-native instructions for any step, despite HDInsight's strong Linux support.
Recommendations
- Provide equivalent Bash/Linux shell commands for installing .NET SDK packages (e.g., using dotnet CLI or NuGet on Linux).
- Include Linux/macOS authentication and setup instructions, clarifying any differences in environment variables or authentication flows.
- Replace or supplement Windows batch commands (e.g., HBase shell example) with Bash equivalents.
- Clarify that the .NET SDK and all code samples are cross-platform, and explicitly mention how to run them on Linux/macOS.
- Avoid referencing Windows-specific tools (such as PowerShell client GUID) without Linux alternatives or explanations.
- Where possible, use platform-neutral language and examples, or provide side-by-side instructions for both Windows and Linux users.
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 demonstrates a Windows bias by presenting all local development environment setup steps using Windows-specific commands (cmd, Notepad, DEL, MKDIR) and explicitly stating that the environment is Windows 10. There are no equivalent Linux (bash, nano/vim, rm, mkdir) instructions or examples, and Windows tools are referenced exclusively for editing and file management. While the Hadoop cluster interaction uses SSH and bash commands (which are cross-platform), the initial project creation and editing workflow is only documented for Windows users.
Recommendations
- Provide parallel Linux/macOS instructions for all environment setup steps, including directory creation, file deletion, and file editing (e.g., use 'mkdir', 'rm', 'nano' or 'vim').
- Present both Windows and Linux/macOS command examples side by side or in tabs, so users on any platform can follow along easily.
- Avoid referencing Windows tools (like Notepad) exclusively; mention cross-platform editors or provide alternatives (e.g., VS Code, nano, vim).
- Clarify that the instructions are applicable to all platforms, and explicitly state any platform-specific differences.
- Consider using platform-agnostic language and commands wherever possible, especially for Java/Maven-based workflows.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-capacity-planning.md
...main/articles/hdinsight/hdinsight-capacity-planning.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias. While most of the content is platform-neutral, the only automation example explicitly mentioned is PowerShell scripts, and Azure Automation is referenced (which is often used with PowerShell/Windows workflows). There are no examples or mentions of Linux-native scripting or tools (such as Bash, CLI, or ARM templates) for cluster lifecycle management. The order of mention also puts PowerShell before any Linux alternative, and no Linux-specific automation or scripting options are discussed.
Recommendations
- Include Linux-native automation examples, such as Bash scripts or Azure CLI commands, for provisioning and deleting clusters.
- Mention ARM/Bicep templates as a cross-platform, declarative alternative for cluster lifecycle management.
- When referencing automation, list both PowerShell and Bash/CLI options, or refer to 'scripting' in a platform-neutral way.
- Provide links to documentation for both Windows and Linux automation approaches.
- Avoid implying PowerShell is the only or primary automation method for HDInsight clusters.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-custom-ambari-db.md
.../main/articles/hdinsight/hdinsight-custom-ambari-db.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates bias toward Windows environments by exclusively referencing Azure SQL Database (a Microsoft/Windows-centric technology) as the only supported external Ambari database, omitting any mention of Linux-native or open-source database alternatives (such as PostgreSQL or MySQL). All SQL examples use T-SQL syntax specific to Azure SQL/SQL Server, and there are no examples or guidance for Linux-based database management or tooling. The deployment instructions focus on Azure CLI (cross-platform), but the overall pattern and requirements are tightly coupled to Windows-centric tools and services.
Recommendations
- Add guidance and examples for using open-source, Linux-native databases (e.g., PostgreSQL, MySQL) as external Ambari DBs, if supported.
- If only Azure SQL Database is supported, explicitly state this limitation and provide rationale.
- Include Linux-native command-line examples for database setup and management (e.g., using psql or mysql CLI tools) if/when support is added.
- Mention and provide parity for Linux-based firewall and networking configuration steps, not just Azure Portal/Windows-centric instructions.
- Ensure that any SQL code samples are clearly marked as T-SQL/Azure SQL-specific, and provide alternatives if other databases are supported.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/troubleshoot-invalidnetworkconfigurationerrorcode-cluster-creation-fails.md
...idnetworkconfigurationerrorcode-cluster-creation-fails.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation is generally Linux-oriented (reflecting HDInsight's Linux focus), but there are notable instances of Windows bias. PowerShell and Windows tooling are referenced without equivalent Linux CLI/Azure CLI examples, and Windows is sometimes mentioned before Linux. For example, the deprecated 'EnableVmProtection' parameter is discussed only in the context of PowerShell, and VM DNS forwarder setup mentions both Linux and Windows, but PowerShell is the only automation example provided. There are no Azure CLI or Bash scripting equivalents for network or VM management tasks.
Recommendations
- For every PowerShell example (such as checking or configuring network settings), provide an equivalent Azure CLI or Bash example.
- When mentioning VM setup for DNS forwarding, give step-by-step instructions for both Linux and Windows VMs, or link to relevant guides for each.
- If referencing Windows tools or patterns (e.g., PowerShell, Windows VMs), ensure Linux alternatives are described with equal prominence and detail.
- In sections where Windows and Linux are both possible (e.g., DNS forwarder VM), mention Linux first or present both options side-by-side.
- For automation or scripting, include Bash or Azure CLI scripts alongside PowerShell scripts to ensure Linux users are equally supported.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-config-for-vscode.md
...main/articles/hdinsight/hdinsight-config-for-vscode.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias, particularly in the configuration examples for HDInsight Spark.NET settings. Paths and tool references (such as 7z.exe, winutils.exe, JAVA_HOME, SCALA_HOME, SPARK_HOME) are given exclusively in Windows format (e.g., C:\Program Files\, D:\winutils), and there is no mention of Linux or macOS equivalents. Additionally, the documentation does not provide Linux-specific instructions or examples for these settings, nor does it clarify cross-platform differences.
Recommendations
- Provide Linux and macOS equivalents for all file paths and tool references (e.g., /usr/bin/7z, /usr/lib/jvm/java-8-openjdk-amd64, /home/user/spark).
- Explicitly state when a setting is Windows-only, and offer alternative instructions or notes for Linux/macOS users.
- Include examples or a table showing how to configure these settings on different operating systems.
- Mention any platform-specific requirements or limitations for tools like winutils.exe, and suggest alternatives or workarounds for non-Windows environments.
- Review all examples and ensure parity by including at least one Linux/macOS example wherever a Windows example is given.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-add-storage.md
...ain/articles/hdinsight/hdinsight-hadoop-add-storage.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides a detailed PowerShell example for verifying additional storage accounts but does not offer equivalent Linux CLI or Bash-based examples. PowerShell is presented as the primary (and only) script-based verification method, with no mention of Linux command-line tools or scripts for this task. This creates a Windows-first and PowerShell-heavy bias, despite the cluster itself being Linux-based.
Recommendations
- Add equivalent Linux/Bash command-line examples for verifying storage accounts, such as using curl, jq, or other standard Linux tools to query the cluster REST API and parse results.
- Present both PowerShell and Linux CLI examples side by side, or at least mention Linux alternatives before or alongside PowerShell.
- Clarify that PowerShell is optional and provide guidance for users on Linux or macOS systems.
- Ensure that all steps, especially those involving scripting or automation, have cross-platform parity to support the Linux-based nature of HDInsight clusters.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-add-hive-libraries.md
...icles/hdinsight/hdinsight-hadoop-add-hive-libraries.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page exhibits a moderate Windows bias. The primary script referenced for adding Hive libraries is a PowerShell (.ps1) script, and the script location provided at the top is for a PowerShell script, with the Bash (Linux) script URI only appearing later in a table. The instructions and examples reference Azure PowerShell and .NET SDK before mentioning Linux-based provisioning, and Windows tools like Azure Storage Explorer are suggested for file uploads without mentioning Linux-native alternatives. The documentation does not provide Linux CLI examples for uploading files or managing storage, and the ordering of information often puts Windows/PowerShell options first.
Recommendations
- List both PowerShell and Bash script URIs together at the start, with clear guidance for Windows and Linux users.
- Provide Linux-native CLI examples (e.g., using azcopy, Azure CLI, or blobfuse) for uploading files to Azure Storage, alongside Windows tools.
- When mentioning provisioning methods, present Linux and cross-platform options (Azure CLI, Bash) before or alongside Windows-specific options like PowerShell and .NET SDK.
- Explicitly state which script to use based on the OS/environment, and provide parity in instructions for both Windows and Linux users.
- Include references to Linux-friendly tools for managing Azure Storage, such as Azure CLI or azcopy, not just Azure Storage Explorer.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-create-non-interactive-authentication-dotnet-applications.md
...ate-non-interactive-authentication-dotnet-applications.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing C#/.NET examples, referencing NuGet and PowerShell commands, and omitting any Linux or cross-platform CLI alternatives. All instructions and code samples are tailored to Windows development environments, with no mention of equivalent steps or tooling for Linux users.
Recommendations
- Include equivalent examples using cross-platform tools such as the Azure CLI (az), which runs on both Windows and Linux.
- Provide instructions for installing required packages and dependencies on Linux (e.g., using dotnet CLI instead of NuGet/PowerShell).
- Add code samples or guidance for developing .NET applications on Linux (e.g., using VS Code, JetBrains Rider, or the dotnet CLI).
- Mention and link to Linux-compatible authentication and resource management workflows.
- Ensure that references to PowerShell are accompanied by Bash or shell script equivalents where possible.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-migrate-dotnet-to-linux.md
.../hdinsight/hdinsight-hadoop-migrate-dotnet-to-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 by focusing on Visual Studio and Windows-based development tools (e.g., .NET Portability Analyzer in Visual Studio 2015) without providing equivalent Linux-based workflows or examples. There are no instructions for performing portability analysis, building, or testing .NET applications using Linux-native tools or environments. The only explicit example of a file path uses a Windows-style path, and there is no mention of Linux file path conventions or Linux-based development environments.
Recommendations
- Provide examples of how to run the .NET Portability Analyzer or similar tools on Linux, such as using the command-line version or alternative open-source tools.
- Include instructions for building .NET/Mono projects on Linux using tools like msbuild, dotnet CLI, or Mono's xbuild, rather than only referencing Visual Studio.
- Show Linux file path conventions in code examples and highlight the need to update hardcoded Windows paths.
- Offer guidance for developers who use Linux-based editors (e.g., VS Code) or command-line workflows.
- Present Linux-native troubleshooting and logging techniques, not just references to Windows-based development and testing.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-create-standalone-application.md
...ht/spark/apache-spark-create-standalone-application.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Windows Tools
Summary
The documentation demonstrates a bias toward Windows environments by referencing Windows-style file paths (e.g., '\out\artifacts'), mentioning AzCopy (primarily a Windows tool) as the example for uploading files, and omitting explicit Linux/Mac instructions or examples. There are no terminal/command-line examples for Linux or Mac, nor are alternative tools (like scp, rsync, or Azure CLI) mentioned for non-Windows users. The steps and screenshots all assume a Windows environment, with no consideration for Linux or Mac users.
Recommendations
- Include Linux/Mac equivalents for file paths (e.g., '/out/artifacts') wherever Windows paths are shown.
- When mentioning AzCopy, also mention cross-platform alternatives such as Azure CLI (az storage blob upload), scp, or rsync, and provide example commands for each.
- Add notes or sections for Linux and Mac users, especially for steps involving file navigation, tool installation, and command-line operations.
- Ensure screenshots and instructions are not Windows-specific, or provide parallel screenshots for Linux/Mac where the UI differs.
- Explicitly state that IntelliJ IDEA and the Azure Toolkit are available cross-platform, and provide any OS-specific installation instructions if needed.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-backup-replication.md
...les/hdinsight/hbase/apache-hbase-backup-replication.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates some Windows bias by referencing and linking to Windows-centric tools (AzCopy, AdlCopy) for data movement, without mentioning or providing Linux-native alternatives. There are no explicit PowerShell or cmd.exe examples, but the data copy tooling and instructions assume the use of these Microsoft tools, which are most commonly used on Windows. Additionally, the documentation does not provide parity for Linux/Unix-native tools (such as rsync, scp, or hdfs dfs commands) for copying data, nor does it clarify cross-platform usage for AzCopy/AdlCopy. All command-line examples use SSH and standard HBase commands, which are cross-platform, but the omission of Linux-native data copy options and the exclusive mention of Windows tools constitutes a subtle bias.
Recommendations
- Include Linux-native data copy options (e.g., rsync, scp, hdfs dfs -cp) alongside AzCopy and AdlCopy, with example commands.
- Clarify that AzCopy and AdlCopy are available for Linux and provide installation/use instructions for Linux environments.
- When listing tools for copying data, avoid listing Windows-centric tools first or exclusively; present cross-platform options together.
- Explicitly state that all SSH and HBase commands are cross-platform, and provide any OS-specific caveats if applicable.
- Consider adding a table or section comparing available data movement tools for both Windows and Linux environments.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-create-linux-clusters-adf.md
...dinsight/hdinsight-hadoop-create-linux-clusters-adf.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation demonstrates a strong Windows/PowerShell bias. All command-line instructions for creating Azure resources (resource group, storage account, blob container, file copy) are provided exclusively as PowerShell scripts, with no equivalent Bash, Azure CLI, or Linux-native instructions. The prerequisites and workflow assume the use of PowerShell, a tool primarily associated with Windows environments, and reference Windows-centric patterns (e.g., 'Write-Host', PowerShell modules). There are no Linux shell or Azure CLI alternatives, and the documentation does not mention how to perform these steps from a Linux or cross-platform environment. This could hinder accessibility for users working on Linux or macOS systems.
Recommendations
- Provide equivalent Azure CLI (az) commands for all PowerShell scripts, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that the steps can be performed from Linux, macOS, or Windows, and provide guidance for each platform.
- Where PowerShell is referenced, add a parallel section or code block for Bash/Azure CLI users.
- Clarify in the prerequisites that either PowerShell or Azure CLI can be used, and link to installation instructions for both.
- Ensure that all portal navigation and screenshots are not Windows-specific and clarify that the Azure portal is web-based and OS-agnostic.
- Consider including a table or toggle that lets users select their preferred environment (Windows/PowerShell or Linux/Bash/Azure CLI) for code samples.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-restrict-outbound-traffic.md
...icles/hdinsight/hdinsight-restrict-outbound-traffic.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a mild Windows bias. Windows-related FQDNs and services (e.g., WindowsUpdate, login.windows.net, login.microsoftonline.com) are listed before Linux equivalents. There is a lack of explicit Linux-focused examples or guidance, and no mention of Linux-specific tools or patterns. While Ubuntu update endpoints are included, the overall framing and examples prioritize Windows services and tools, with no parity in Linux-specific configuration or troubleshooting steps.
Recommendations
- Provide explicit Linux-focused examples, such as referencing Linux package update endpoints (e.g., security.ubuntu.com, mirrors for other distributions) alongside WindowsUpdate.
- List Linux and Windows dependencies together, or alternate their order to avoid always placing Windows first.
- Include troubleshooting or configuration steps relevant to Linux users, such as using SSH from Linux/macOS terminals, or configuring iptables/firewalld if relevant.
- Mention Linux authentication endpoints or scenarios, if applicable, alongside Windows login endpoints.
- Clarify that the guidance applies equally to both Windows and Linux-based HDInsight clusters, and call out any differences in requirements.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-customize-cluster-linux.md
.../hdinsight/hdinsight-hadoop-customize-cluster-linux.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides comprehensive coverage of script actions for Azure HDInsight clusters, but it demonstrates a Windows bias by prioritizing Azure PowerShell and .NET SDK examples and instructions before Azure CLI and REST API equivalents. PowerShell cmdlets are featured prominently, often with more detailed examples, while Azure CLI instructions are less detailed or appear after PowerShell. There is also a focus on .NET SDK usage, which is more common in Windows-centric environments. Although the documentation is about Linux-based clusters and Bash scripts, the tooling and automation examples are skewed toward Windows/PowerShell users.
Recommendations
- Ensure that Azure CLI examples are provided with equal detail and prominence as PowerShell examples, especially for common tasks such as applying, promoting, and demoting script actions.
- Present Azure CLI and PowerShell instructions side-by-side or in parallel sections, rather than listing PowerShell first.
- Include REST API and ARM template examples with the same level of detail as PowerShell and .NET SDK.
- Highlight cross-platform tools (such as Azure CLI) as the default or preferred method for automation, given the Linux context.
- Add explicit notes or sections for Linux/macOS users, including any prerequisites or environment setup steps for non-Windows platforms.
- Where .NET SDK is mentioned, also reference Python or Java SDKs if available, or clarify that .NET is cross-platform.
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
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented towards Windows users: all file and directory commands use Windows Command Prompt syntax, file editing is done with Notepad, and troubleshooting uses PowerShell scripts. There are no equivalent Linux/macOS commands or editor suggestions, despite HDInsight clusters being Linux-based. Linux command-line patterns (e.g., mkdir, rm, nano/vi) are missing, and Windows tools are mentioned exclusively or first.
Recommendations
- Provide Linux/macOS equivalents for all command-line instructions (e.g., use mkdir, cd, rm -rf, nano/vi for file editing).
- Include both Windows and Linux/macOS command blocks side by side or in tabs for each step.
- Suggest cross-platform editors (e.g., VS Code, nano, vi) instead of only Notepad.
- For troubleshooting, provide Linux command-line solutions (e.g., dos2unix, sed) for fixing line endings, not just PowerShell.
- Clarify at the start that instructions are for Windows and provide a parallel set for Linux/macOS users.
- Where possible, use platform-neutral language and tools, especially since HDInsight clusters are Linux-based.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-private-link.md
...blob/main/articles/hdinsight/hdinsight-private-link.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates several forms of Windows bias. In the 'Check cluster connectivity' step, the only example for deploying a test VM uses a Windows 10 image, with RDP as the default access method, and requires a Windows license. The instructions for testing SSH access begin from a Windows command prompt, with no mention of Linux or cross-platform alternatives. In the cluster deployment section, the PowerShell example is mentioned before the Azure CLI example, and there are no explicit Linux shell or Bash examples. Throughout the page, tooling and workflows are described primarily in terms of the Azure portal and Windows-centric patterns, with no guidance for Linux users or those using non-Windows environments.
Recommendations
- Provide parallel Linux-based examples for deploying a test VM (e.g., Ubuntu or CentOS), including SSH access instructions from a Linux terminal.
- When referencing command-line tools, present Azure CLI (cross-platform) examples before or alongside PowerShell, and include Bash syntax where appropriate.
- In connectivity testing, show how to use SSH from both Windows (e.g., PowerShell or CMD) and Linux/macOS terminals.
- When describing VM deployment, offer both Windows and Linux image options, and clarify that either can be used for testing connectivity.
- Review all step-by-step instructions to ensure Linux users are not excluded or forced to adapt Windows-specific steps.
- Where GUI instructions are given (e.g., Azure portal), consider adding CLI alternatives for automation and scripting, which are platform-agnostic.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/connect-on-premises-network.md
...main/articles/hdinsight/connect-on-premises-network.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates some Windows bias by listing PowerShell as a primary automation tool, providing PowerShell examples before Azure CLI, and referencing Windows Server DNS configuration before Linux alternatives in some sections. While Linux is well-represented for the DNS server setup (using Bind on Ubuntu), automation and scripting guidance often defaults to PowerShell, and Windows Server DNS documentation is referenced before or more prominently than Linux equivalents.
Recommendations
- Ensure that Azure CLI examples are presented before or alongside PowerShell examples, especially in sections where both are relevant.
- Provide explicit Linux-based DNS server configuration examples and documentation references before or alongside Windows Server DNS references.
- Where PowerShell is mentioned as a prerequisite or tool, also mention Bash/Azure CLI as an equal alternative for Linux/macOS users.
- In sections discussing DNS server configuration, include links to documentation for popular Linux DNS servers (e.g., Bind, dnsmasq) before or alongside Windows Server DNS.
- Audit all example scripts and commands to ensure Linux and cross-platform parity, and avoid implying PowerShell is the default or preferred automation tool.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/apache-domain-joined-manage.md
...hdinsight/domain-joined/apache-domain-joined-manage.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools (such as Visual Studio Code, Power BI, Visual Studio Tools, and PowerShell) in examples and recommended access methods. Linux-native tools or workflows are not explicitly mentioned or illustrated, and there are no Linux-specific usage examples. The documentation assumes familiarity with Windows environments and omits equivalent Linux instructions or alternatives.
Recommendations
- Include explicit Linux-native tool examples (e.g., using command-line Beeline, SSH, or Linux-based editors like Vim/Emacs) alongside or before Windows tools.
- Provide Linux-specific instructions for connecting to clusters, managing users, and running jobs (e.g., using Linux shell commands instead of PowerShell or Visual Studio Tools).
- Mention cross-platform alternatives to Windows-only tools (e.g., DBeaver or SquirrelSQL instead of Power BI for ODBC/JDBC connections).
- Clarify that tools like VS Code and IntelliJ are cross-platform, and provide installation and usage notes for Linux users.
- Add sample command-line workflows for Linux (e.g., submitting jobs via curl, using native Hadoop/Spark CLI tools).
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
Summary
The documentation page provides detailed instructions and examples for rebooting HDInsight cluster VMs using PowerShell (a Windows-centric tool) and REST API, but does not include any Linux-native CLI examples (such as Azure CLI or Bash scripts). The PowerShell method is presented first, and there are no references to Linux tools or command-line patterns, which may disadvantage users working from Linux or macOS environments.
Recommendations
- Add equivalent Azure CLI (az hdinsight) commands for listing and restarting nodes, with example syntax.
- Include Bash script examples for interacting with the REST API using curl or httpie, demonstrating how to authenticate and send requests from Linux/macOS.
- Mention cross-platform tools (such as Azure CLI) before or alongside PowerShell to ensure parity.
- Clarify that PowerShell examples can be run on PowerShell Core (cross-platform), if applicable, or provide guidance for Linux/macOS users.
- Ensure that all steps and code samples are available for both Windows and Linux users to avoid platform bias.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/azure-monitor-agent.md
...cs/blob/main/articles/hdinsight/azure-monitor-agent.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: PowerShell is presented as the primary scripted method for enabling Azure Monitor Agent integration, with detailed PowerShell examples and references to Windows-specific tools and documentation. The PowerShell approach is described before the Azure CLI approach, and references to 'Set up the Azure Monitor agent on Windows client devices' are included. There is no mention of Linux shell scripting or Linux-specific tools (other than Azure CLI and jq), and no explicit Linux/Unix shell examples are provided, despite HDInsight clusters often running on Linux.
Recommendations
- Provide Linux shell/bash examples alongside or before PowerShell examples, especially for steps that can be performed on Linux-based HDInsight clusters.
- Avoid referencing Windows-specific documentation (such as 'Set up the Azure Monitor agent on Windows client devices') when the process is OS-agnostic or primarily relevant for Linux clusters.
- Clarify that Azure CLI and REST API steps are cross-platform and can be run from Linux, macOS, or Windows environments.
- Include explicit notes or sections for Linux users, especially for common operations like downloading files, editing JSON, or using tools like jq.
- Consider reordering the approaches so that the Azure CLI (cross-platform) method is presented before PowerShell, or present both methods in parallel.
- Where possible, provide sample scripts or commands that can be run natively on Linux (bash), and mention any required tools (e.g., curl, jq, azcopy) with installation instructions for Linux.