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 576-600 of 867 flagged pages
Hdinsight Granular role-based access Azure HDInsight cluster configurations ...insight-migrate-granular-access-cluster-configurations.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page shows moderate Windows bias. It provides migration guidance for several SDKs and tools, but Windows-centric tools (PowerShell, Visual Studio, Data Lake Tools for Visual Studio) are given dedicated sections and detailed migration steps. The PowerShell section is the only command-line automation example outside of Azure CLI, and Windows tools are listed before their Linux/macOS equivalents (e.g., Visual Studio before IntelliJ/Eclipse). There are no Bash or Linux-specific examples for automation, and no mention of Linux-native scripting or management tools.
Recommendations
  • Add migration guidance for Linux/macOS users, such as Bash scripts or examples using the Azure CLI for all relevant operations (not just role assignment).
  • Include parity for Linux-native tools (e.g., instructions for using SDKs on Linux, or alternatives to PowerShell for automation).
  • Reorder tool sections to avoid consistently listing Windows tools first; alternate ordering or group by platform.
  • Provide explicit notes or links for Linux/macOS users where Windows-only tools (PowerShell, Visual Studio) are referenced.
  • Add troubleshooting guidance for common Linux/macOS issues (e.g., permissions, environment setup).
GitHub Create Pull Request
Hdinsight Enable Private Link on an Azure HDInsight cluster ...blob/main/articles/hdinsight/hdinsight-private-link.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas: the only explicit VM deployment example for connectivity testing uses a Windows 10 image and RDP, with no mention of Linux VM options or SSH port configuration. The PowerShell example for cluster creation is mentioned before the Azure CLI, and there are no Linux/macOS-specific instructions or examples for connectivity testing or command-line usage. This may create friction for Linux/macOS users, especially those who prefer or require non-Windows environments.
Recommendations
  • Include a Linux VM deployment example for connectivity testing, specifying an appropriate image (e.g., Ubuntu) and SSH port configuration.
  • Present Azure CLI and PowerShell examples together, or list CLI first to avoid Windows-first ordering.
  • Add instructions for testing Ambari and SSH access from Linux/macOS terminals, including relevant commands and screenshots.
  • Clarify that the procedures are platform-agnostic where possible, and note any platform-specific differences.
  • Ensure all steps that reference Windows tools (e.g., RDP, Windows licensing) have Linux/macOS equivalents or alternatives.
GitHub Create Pull Request
Hdinsight Restrict access using Shared Access Signatures - Azure HDInsight ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-storage-sharedaccesssignature-permissions.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. PowerShell is the primary method shown for most critical tasks, including cluster creation and SAS configuration, with no equivalent Bash or Linux shell examples. Azure CLI instructions use Windows-style variable setting (set VAR=VALUE) and reference Windows environments, without providing Bash/Linux alternatives. The Python and C# sections are platform-neutral, but the overall flow and critical steps (especially cluster creation and storage configuration) are Windows-centric. There is no guidance for Linux/macOS users on how to perform these tasks using Bash, shell scripting, or cross-platform tools.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell examples, especially for cluster creation and storage configuration.
  • Update Azure CLI sections to show both Windows (set VAR=VALUE) and Bash (export VAR=VALUE) variable syntax, and clarify differences in command usage between platforms.
  • Explicitly mention and demonstrate how to perform all steps on Linux/macOS, including prerequisites and environment setup.
  • Where possible, use cross-platform tools and commands first, or present them alongside Windows-specific instructions.
  • Add notes or callouts indicating which commands/scripts are Windows-only and provide alternatives for other platforms.
GitHub Create Pull Request
Hdinsight Azure HDInsight supported node configurations ...es/hdinsight/hdinsight-supported-node-configuration.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary scripting tool for cluster deployment and by instructing users to format VM SKU identifiers specifically for use in PowerShell and 'other scripts.' There are no explicit Linux or macOS shell (e.g., Bash) examples or references, and Windows-centric terminology appears before any mention of cross-platform alternatives.
Recommendations
  • Explicitly mention Bash/Azure CLI usage alongside PowerShell in scripting contexts.
  • Provide example commands for both PowerShell and Bash/Azure CLI when discussing VM SKU identifiers.
  • Clarify that Azure CLI is cross-platform and provide links or examples for Linux/macOS users.
  • Avoid phrasing that implies PowerShell is the default or only scripting environment.
GitHub Create Pull Request
Hdinsight Run MapReduce jobs on Entra enabled HDInsight cluster using REST API ...-with-entra-authentication/run-map-reduce-rest-jobs.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows tools (cmd, PowerShell) are featured prominently, with examples and variable setting syntax tailored to Windows environments (e.g., 'set TOKEN', caret line continuation, PowerShell scripts). Linux/macOS equivalents (e.g., bash variable assignment, line continuation) are not provided, and Windows-specific instructions precede PowerShell examples. There is no explicit Linux shell example for submitting jobs or checking status, and the curl examples use Windows cmd syntax.
Recommendations
  • Provide Linux/macOS shell examples for all curl commands, using bash syntax (e.g., export TOKEN, backslash line continuation).
  • Clearly separate Windows and Linux/macOS instructions, labeling each section.
  • Include PowerShell Core examples for cross-platform compatibility.
  • Add notes or tables comparing command syntax differences between Windows cmd, PowerShell, and bash.
  • Ensure that Linux/macOS users can follow the guide without needing to translate Windows-specific commands.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/includes/hdinsight-portal-management-selector.md ...sight/includes/hdinsight-portal-management-selector.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page lists Azure PowerShell and .NET SDK (both Windows-centric) before Azure CLI, and does not explicitly mention Bash, Linux shell, or Linux-specific tools. The ordering and lack of explicit Linux/Bash examples suggest a Windows-first and PowerShell-heavy bias.
Recommendations
  • Ensure that Linux/Bash examples are provided and referenced equally alongside PowerShell and .NET SDK.
  • List Azure CLI (which is cross-platform) before or alongside PowerShell/.NET SDK to avoid implying Windows is the primary platform.
  • Add explicit mention of Linux/macOS compatibility and provide links to Linux/Bash-specific guidance where relevant.
GitHub Create Pull Request
Hdinsight What is Interactive Query in Azure HDInsight? ...eractive-query/apache-interactive-query-get-started.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Microsoft-centric tools (Power BI, Visual Studio, Hive ODBC/Excel) in the list of query methods, mentioning them before cross-platform or Linux-native options like Beeline and Ambari Hive View. There are no explicit Linux/macOS examples or references to Linux-specific tools or command-line usage, and the guidance for connecting to the cluster is focused on browser-based access and Microsoft tools.
Recommendations
  • Add explicit examples for Linux/macOS users, such as connecting via Beeline from a Linux terminal.
  • Include instructions for using open-source BI tools (e.g., Apache Superset, DBeaver) on Linux/macOS.
  • Balance the order of tool presentation, listing cross-platform and open-source options before or alongside Microsoft tools.
  • Provide sample commands for connecting via JDBC/ODBC from Linux/macOS environments.
  • Clarify which tools are cross-platform and which are Windows-only.
GitHub Create Pull Request
Hdinsight Connect to Kafka using virtual networks - Azure HDInsight ...es/hdinsight/kafka/apache-kafka-connect-vpn-gateway.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. The step-by-step resource creation and configuration instructions are provided exclusively in PowerShell, with no Bash, Azure CLI, or Linux/macOS shell equivalents for critical setup tasks. While the text mentions that the VPN client can be used with both Windows and macOS, all automation and scripting examples are PowerShell-based, and the instructions for connecting to Azure and creating resources are tailored to Windows users. Only one Azure CLI snippet is provided, and it is for a minor task (listing NICs), not for the main workflow. Linux/macOS users are left to infer or translate the steps themselves, which creates friction and potential for error.
Recommendations
  • Provide equivalent step-by-step instructions using Azure CLI and/or Bash scripts for all major resource creation and configuration tasks.
  • Explicitly call out Linux/macOS workflows, including how to install and use the Azure CLI, and how to connect to Azure from non-Windows environments.
  • Where PowerShell is used, offer side-by-side examples in Bash/Azure CLI, or link to relevant cross-platform documentation.
  • Clarify any OS-specific requirements or limitations for VPN client installation and usage.
  • Reorder examples so that cross-platform or Linux/macOS instructions are presented alongside or before Windows/PowerShell instructions.
GitHub Create Pull Request
Hdinsight Tutorial: Use Azure Automation runbooks to create clusters - Azure HDInsight ...ob/main/articles/hdinsight/manage-clusters-runbooks.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses PowerShell for all automation runbook examples, with no mention of Bash, Python, or other cross-platform scripting options. All code samples, screenshots, and instructions assume PowerShell usage, which is most familiar to Windows users. There is no guidance for Linux/macOS users who may prefer or require alternatives, nor is there any reference to Azure Automation support for non-PowerShell runbooks.
Recommendations
  • Include equivalent examples using Python runbooks, which are supported in Azure Automation and widely used on Linux/macOS.
  • Add notes or sections explaining how Linux/macOS users can author and run Bash or Python scripts in Azure Automation.
  • Clarify that PowerShell Core is cross-platform and provide instructions for using it on Linux/macOS, if PowerShell must be used.
  • Present examples for both PowerShell and Python/Bash side-by-side, or at least mention alternatives.
  • Avoid language that implies PowerShell is the only or default option for Azure Automation runbooks.
GitHub Create Pull Request
Hdinsight Configure service endpoint policies - Azure HDInsight ...b/main/articles/hdinsight/service-endpoint-policies.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring service endpoint policies, but the CLI script uses Windows-style variable assignment and array syntax, and the PowerShell example is given in full. There are no explicit Linux/macOS shell (bash) examples, and the CLI example uses syntax that is not idiomatic for bash/zsh. The documentation does not mention Linux-specific considerations or provide parity for Linux users, potentially causing confusion or friction for those not using Windows.
Recommendations
  • Provide a Linux/macOS bash example using Azure CLI, with POSIX-compliant variable assignment and array handling.
  • Clarify that Azure CLI commands can be run on any OS, and show examples using bash/zsh syntax.
  • Avoid using Windows-style variable assignment (e.g., $var) in CLI examples intended for cross-platform use.
  • Add a note or section for Linux/macOS users, highlighting any differences or caveats.
  • Ensure that PowerShell examples are clearly marked as Windows-only, and that equivalent bash examples are present.
GitHub Create Pull Request
Hdinsight Azure Toolkit for Eclipse: Create Scala apps for HDInsight Spark ...es/hdinsight/spark/apache-spark-eclipse-tool-plugin.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias primarily in the 'Run a Spark Scala application locally' section, where only Windows-specific instructions (WinUtils.exe, HADOOP_HOME) are provided for resolving local Spark issues. There are no equivalent instructions or troubleshooting steps for Linux or macOS users. Additionally, Windows is mentioned first and exclusively in the local run prerequisite, and the overall troubleshooting guidance is Windows-centric.
Recommendations
  • Add explicit instructions for running Spark Scala applications locally on Linux and macOS, including common issues and solutions (e.g., permissions, environment variables, file system requirements).
  • Clarify whether WinUtils.exe is only required for Windows and what Linux/macOS users should expect or do in similar scenarios.
  • Include troubleshooting steps for local Spark execution on Linux/macOS, such as handling Hadoop dependencies and environment setup.
  • Where platform-specific instructions are needed, present them in parallel sections (Windows, Linux, macOS) for parity.
  • Review other sections for implicit Windows assumptions and ensure cross-platform applicability is clear.
GitHub Create Pull Request
Hdinsight Azure Toolkit: Debug Apache Spark apps remotely - Azure HDInsight ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-intellij-tool-plugin-debug-jobs-remotely.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several areas: Windows-specific issues (WinUtils.exe) and workarounds are described in detail, with no equivalent Linux/macOS troubleshooting; file path and tool references (Notepad, C:\ paths, hosts file location) are Windows-centric and presented first or exclusively; instructions for editing the hosts file and copying configuration files assume a Windows environment, with only a brief mention of Cygwin for scp, but no native Linux/macOS guidance. There are no Linux/macOS-specific examples for common tasks such as editing the hosts file or handling environment variables.
Recommendations
  • Provide Linux/macOS equivalents for all Windows-specific instructions, such as hosts file location and editing (e.g., /etc/hosts, using nano or vi).
  • Include troubleshooting steps for Linux/macOS environments, especially for issues like WinUtils.exe which are Windows-only.
  • When giving file paths or commands, show both Windows and Linux/macOS formats side by side.
  • Avoid assuming the user is on Windows; clarify which steps are OS-specific and offer alternatives.
  • Mention native Linux/macOS tools (e.g., scp, ssh, text editors) before or alongside third-party tools like Cygwin.
GitHub Create Pull Request
Hdinsight Azure Toolkit for IntelliJ: Spark app - HDInsight ...s/hdinsight/spark/apache-spark-intellij-tool-plugin.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally cross-platform, as IntelliJ IDEA and HDInsight Spark clusters are inherently cross-platform and the instructions are mostly OS-agnostic. However, there is a notable Windows bias in the 'Spark Local Console(Scala)' section, which requires WINUTILS.EXE—a Windows-specific tool. There are no instructions or alternatives provided for Linux/macOS users for local Spark console execution, nor is it clarified that this step is Windows-only. Elsewhere, the documentation refers to 'Spark clusters (Linux only)', but does not provide Linux/macOS-specific setup or troubleshooting guidance.
Recommendations
  • Explicitly state when a step or prerequisite (such as WINUTILS.EXE) is Windows-only, and provide equivalent instructions or alternatives for Linux/macOS users.
  • For the Spark Local Console section, add instructions for running local Spark jobs on Linux/macOS, including any required environment variables or dependencies.
  • Where possible, avoid referencing Windows-specific tools without mentioning cross-platform equivalents or noting OS limitations.
  • Add troubleshooting notes or links for common Linux/macOS issues (e.g., permissions, environment variables, missing dependencies) in relevant sections.
  • If a feature is not available on Linux/macOS, clearly state this and suggest alternative workflows.
GitHub Create Pull Request
Hdinsight Use Livy Spark to submit jobs to Spark cluster on Azure HDInsight ...es/hdinsight/spark/apache-spark-livy-rest-interface.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-style command syntax and file paths (e.g., C:\Temp\input.txt, set environment variables with 'set'), and explicitly states that examples are based on a Windows environment. There are no Linux/macOS equivalents for environment variable setting, file paths, or input file usage, and Windows-specific recommendations are made without Linux alternatives.
Recommendations
  • Provide Linux/macOS equivalents for all examples, including environment variable setting (e.g., 'export clustername=CLUSTERNAME'), file paths (e.g., '/tmp/input.txt'), and input file usage.
  • Add notes or sections clarifying differences in command syntax and file path conventions between Windows and Linux/macOS.
  • Where Windows is recommended (e.g., using input files), offer Linux/macOS alternatives or clarify how to achieve the same on those platforms.
  • Ensure that examples do not default to Windows syntax unless it is the majority use case, or present both options side-by-side.
GitHub Create Pull Request
Hdinsight Use Apache Pig ...ocs/azure-docs/blob/main/articles/hdinsight/use-pig.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It highlights SQL Server Integration Services (SSIS) and the Azure Feature Pack for SSIS as a method for running Pig jobs, which are Windows-centric tools. There are no explicit Linux/macOS alternatives or walkthroughs for running Pig jobs from a Linux shell, nor are Linux-native tools (such as SSH, Bash, or command-line examples) provided. The only tool linked in the references section is PuTTY, a Windows SSH client, with no mention of Linux/macOS equivalents. The order of presentation also places Windows tools before any mention of generic or cross-platform methods.
Recommendations
  • Add explicit walkthroughs for running Pig jobs from Linux/macOS terminals, using SSH and Bash.
  • Include examples using Linux-native tools (e.g., OpenSSH, curl) and clarify that HDInsight clusters are Linux-based.
  • Provide links to documentation for Linux/macOS SSH clients and command-line usage.
  • Reorder sections so that cross-platform or generic methods are presented before Windows-specific tools.
  • Mention that SSIS is a Windows-only solution and suggest open-source or cross-platform alternatives for orchestration.
GitHub Create Pull Request
Hdinsight Azure HDInsight architecture with Enterprise Security Package ...ght/domain-joined/apache-domain-joined-architecture.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples are provided exclusively in PowerShell, with no Linux shell or cross-platform alternatives. The instructions focus on Microsoft Entra Domain Services and Active Directory, which are Windows-centric technologies. There is no mention of Linux-compatible tools, nor guidance for users operating from Linux/macOS environments. The use of PowerShell modules is assumed, and no Bash or CLI equivalents are offered.
Recommendations
  • Provide equivalent instructions using Azure CLI or Bash where possible, especially for service principal and policy management.
  • Include explicit guidance for Linux/macOS users, such as how to install and use Azure CLI or REST API for relevant operations.
  • Clarify whether any steps (such as domain joining, Kerberos setup) can be performed from non-Windows environments, and document those workflows.
  • Add notes or links to cross-platform tools and documentation for identity management and cluster configuration.
  • Consider reordering examples so that cross-platform or Linux-native options are presented alongside or before Windows/PowerShell instructions.
GitHub Create Pull Request
Hdinsight Double encryption for data at rest ...e-docs/blob/main/articles/hdinsight/disk-encryption.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
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 key deployment and cluster creation examples, with no equivalent bash or Linux shell examples. Windows tools (PowerShell cmdlets) are referenced for key recovery and cluster deployment, and these examples are presented before or alongside Azure CLI, but never with Linux-native alternatives. There are no explicit Linux/macOS shell examples for tasks like ARM template deployment or resource management, which may create friction for non-Windows users.
Recommendations
  • Provide bash or Linux shell equivalents for all PowerShell examples, especially for ARM template deployment and resource management.
  • Include explicit instructions for Linux/macOS users on how to perform key recovery and other operations using Azure CLI or REST API.
  • Ensure that CLI examples (which are cross-platform) are presented before or alongside PowerShell examples.
  • Reference Linux-native tools and workflows where appropriate, and clarify that Azure CLI commands work on all platforms.
  • Add notes or sections highlighting Linux/macOS compatibility for all major steps.
GitHub Create Pull Request
Hdinsight Reboot VMs for Azure HDInsight clusters ...docs/blob/main/articles/hdinsight/cluster-reboot-vm.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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 lists this method first. There are no equivalent CLI or Bash examples for Linux/macOS users. The REST API method is platform-neutral, but lacks explicit Linux command-line usage examples (e.g., curl). Overall, the page demonstrates a Windows bias by prioritizing PowerShell and omitting Linux-specific guidance.
Recommendations
  • Add Azure CLI examples for listing and restarting HDInsight cluster nodes, as Azure CLI is cross-platform.
  • Provide Bash/curl examples for invoking the REST API from Linux/macOS terminals.
  • Mention platform-neutral tools (e.g., Azure CLI, REST API via curl/Postman) before or alongside PowerShell.
  • Clarify that PowerShell examples are for Windows users and offer equivalent steps for Linux/macOS users.
GitHub Create Pull Request
Hdinsight Converting certificate contents to base-64 - Azure HDInsight ...-troubleshoot-converting-service-principal-certificate.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only PowerShell and C# examples for converting a certificate to base-64, both of which are Windows-centric. There are no Linux or macOS command-line examples (e.g., using openssl or base64), and Windows tools are mentioned exclusively. This creates friction for non-Windows users.
Recommendations
  • Add a Linux/macOS example using openssl and base64 commands, e.g., `base64 -w 0 path-to-servicePrincipalCertificatePfxFile` or `openssl base64 -in path-to-servicePrincipalCertificatePfxFile`.
  • Explicitly mention that the PowerShell example is for Windows and provide equivalent bash/zsh commands for Linux/macOS.
  • Consider including a Python snippet, which is cross-platform, as an additional example.
GitHub Create Pull Request
Hdinsight Use Curl to export data with Apache Sqoop in Azure HDInsight ...icles/hdinsight/hadoop/apache-hadoop-use-sqoop-curl.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias: all command-line examples use Windows batch syntax (set, %VAR%), and the jq path is given as a Windows executable (C:\HDI\jq-win64.exe). There are no Linux/macOS shell examples (e.g., export, $VAR, ./jq), nor is there guidance for Linux users on adapting the commands. Windows tools and patterns are referenced exclusively and first, making it harder for Linux/macOS users to follow along.
Recommendations
  • Provide Linux/macOS shell examples alongside Windows batch examples, using export VAR=value and $VAR syntax.
  • Mention that jq is available on Linux/macOS and show usage with ./jq or jq installed via package managers.
  • Include a note or table summarizing environment variable syntax differences between Windows and Linux/macOS.
  • When referencing tools (like SQL clients), suggest cross-platform alternatives or clarify platform-specific instructions.
  • Avoid language like 'this example is based on a Windows environment' without providing parity for other platforms.
GitHub Create Pull Request
Hdinsight Tutorial: Apache Spark Streaming & Apache Kafka - Azure HDInsight ...t/hdinsight-apache-kafka-spark-structured-streaming.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides host information gathering commands specifically for Windows command prompt, using Windows-style paths and instructions. It notes that 'slight variations will be needed for other environments' but does not provide Linux/macOS equivalents or guidance. All other steps are platform-neutral (Jupyter, Scala, bash), but the initial cluster info retrieval is Windows-centric.
Recommendations
  • Provide equivalent Linux/macOS commands for host information gathering, including example usage of jq and curl on those platforms.
  • Document the differences in command syntax and path conventions between Windows and Linux/macOS.
  • Explicitly mention that jq and curl are available on Linux/macOS by default, and show how to install jq if needed.
  • Consider presenting Linux/macOS examples first or side-by-side with Windows examples.
GitHub Create Pull Request
Hdinsight Customize Azure HDInsight cluster configurations using bootstrap ...nsight/hdinsight-hadoop-customize-cluster-bootstrap.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page is heavily biased towards Windows and PowerShell. All code examples and the detailed walkthrough use Azure PowerShell, a Windows-centric tool, with no equivalent Bash, CLI, or Linux-native examples. The .NET SDK is mentioned but not demonstrated, and Resource Manager templates are shown only briefly. There is no guidance for Linux/macOS users on how to perform the same tasks using Azure CLI, Bash, or other cross-platform tools. The appendix provides a complete PowerShell script, further reinforcing the Windows-first approach.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell code snippets.
  • Provide Bash scripts or instructions for Linux/macOS users.
  • Include .NET SDK sample code, not just a link.
  • Clearly indicate which methods are cross-platform and which are Windows-specific.
  • Reorganize sections so that cross-platform methods (ARM templates, CLI) are presented before Windows-specific tools.
  • Reference Linux/macOS prerequisites and installation steps for required tools.
GitHub Create Pull Request
Hdinsight Use .NET with Hadoop MapReduce on Linux-based HDInsight - Azure .../hdinsight/hdinsight-hadoop-migrate-dotnet-to-linux.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows tools (Visual Studio, .NET Portability Analyzer for Visual Studio), providing step-by-step instructions only for Windows environments, and omitting equivalent Linux-based workflows or tools for analyzing, building, or testing .NET applications. Linux users are expected to adapt Windows-centric instructions without guidance, which may create friction and confusion.
Recommendations
  • Include instructions for running portability analysis on Linux/macOS, such as using the command-line version of the .NET Portability Analyzer or alternative tools.
  • Provide guidance for building .NET applications with Mono on Linux, including command-line build steps (e.g., using msbuild or dotnet CLI).
  • Offer examples of common Linux file paths and highlight platform-specific differences more thoroughly.
  • Mention Linux-native editors (e.g., VS Code, JetBrains Rider) and how to configure/build/test .NET projects with them.
  • Reorder sections or add parallel instructions so Linux workflows are presented alongside Windows ones, not only as migration targets.
GitHub Create Pull Request
Hdinsight Add additional Azure Storage accounts to HDInsight ...ain/articles/hdinsight/hdinsight-hadoop-add-storage.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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/macOS CLI or scripting examples. The verification section prioritizes PowerShell, and there is no mention of Linux shell commands (e.g., Bash, curl, jq) or Azure CLI usage for Linux/macOS users. This creates friction for non-Windows users who may not have access to PowerShell.
Recommendations
  • Add equivalent verification instructions using Bash shell commands (e.g., curl and jq) for Linux/macOS users.
  • Provide Azure CLI examples for verifying storage accounts, as Azure CLI is cross-platform.
  • Ensure that examples are presented in parallel (PowerShell and Bash/Azure CLI) or alternate which platform is shown first.
  • Explicitly mention that PowerShell is available cross-platform, but also provide native Linux/macOS alternatives.
GitHub Create Pull Request
Hdinsight Tutorial: Create an end-to-end ETL pipeline to derive sales insights in Azure HDInsight ...ain/articles/hdinsight/hdinsight-sales-insights-etl.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Bash and Azure CLI examples for most steps, making it accessible to Linux/macOS users. However, when it comes to triggering the Data Factory pipeline, the only scripted example is in PowerShell, and the documentation explicitly refers to using PowerShell and the Az PowerShell module. The portal (GUI) alternative is mentioned, but there is no Bash/Azure CLI example for this critical step. Power BI Desktop is also referenced as the only visualization tool, which is primarily a Windows application.
Recommendations
  • Add an Azure CLI or REST API example for triggering the Data Factory pipeline, so Linux/macOS users can complete the tutorial without PowerShell.
  • Explicitly mention that Power BI Desktop is Windows-only and suggest alternatives for Linux/macOS users, such as Power BI web or other visualization tools.
  • Where PowerShell is referenced in prerequisites, clarify that it is optional and provide equivalent instructions for Bash/Azure CLI.
  • Ensure that for every PowerShell example, a Bash/Azure CLI or REST API equivalent is provided.
GitHub Create Pull Request
← Previous Page 24 of 35 Next →