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 76-100 of 867 flagged pages
Hdinsight Understand and resolve WebHCat errors on HDInsight - Azure ...ght/hdinsight-hadoop-templeton-webhcat-debug-errors.md
High Priority View Details →
Scanned: 2026-01-11 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 referencing Azure PowerShell and Data Lake Tools for Visual Studio as primary client-side tools for interacting with WebHCat, both of which are Windows-centric. No Linux or cross-platform command-line examples (e.g., curl, wget, bash scripts) are provided for interacting with the WebHCat REST API. The documentation does not mention Linux-native tools or workflows, nor does it provide parity in examples or troubleshooting steps for Linux users.
Recommendations
  • Add examples of using Linux command-line tools (such as curl or wget) to interact with the WebHCat REST API.
  • Mention Linux-native client options (e.g., shell scripts, Python requests) alongside Windows tools.
  • Ensure troubleshooting steps and configuration instructions are platform-neutral or provide both Windows and Linux workflows.
  • Reference cross-platform editors and tools (e.g., VS Code) in addition to Visual Studio.
  • Clarify that Apache Ambari is accessible from any OS via web browser or REST API, and provide example REST API calls using curl.
GitHub Create Pull Request
Hdinsight Use .NET with Hadoop MapReduce on Linux-based HDInsight - Azure .../hdinsight/hdinsight-hadoop-migrate-dotnet-to-linux.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by primarily referencing Windows-based development tools (Visual Studio), providing step-by-step instructions only for Windows environments, and omitting equivalent Linux-based workflows or tools for .NET development and portability analysis. The use of Windows file paths as examples further reinforces this bias, and there is no guidance for Linux-native development or deployment processes.
Recommendations
  • Include instructions for performing portability analysis and building .NET applications using Linux-native tools such as MonoDevelop, JetBrains Rider, or command-line utilities (e.g., msbuild, dotnet CLI).
  • Provide examples of file paths and environment-specific considerations for Linux (e.g., /tmp/file.txt) alongside Windows examples.
  • Add guidance for installing and running the .NET Portability Analyzer or similar tools on Linux, if available, or suggest alternative approaches for Linux users.
  • Clarify how to build, test, and deploy .NET solutions on Linux systems without relying on Visual Studio.
  • Reorder sections or provide parallel instructions so that Linux workflows are presented alongside or before Windows-specific instructions.
GitHub Create Pull Request
Hdinsight Managed identities in Azure HDInsight ...ain/articles/hdinsight/hdinsight-managed-identities.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell before Azure CLI when describing methods to create managed identities, and by referencing Windows-centric tools and patterns (such as PowerShell and certificates) without providing equivalent Linux-specific guidance or examples. There is no mention of Linux shell commands or Linux-specific workflows, and the examples and terminology are more familiar to Windows administrators.
Recommendations
  • List Azure CLI before Azure PowerShell when describing cross-platform methods, or present both equally.
  • Include Linux shell (bash) examples for creating and managing managed identities, alongside PowerShell examples.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux users.
  • Provide guidance or examples for distributing certificates and managing identities using Linux-native tools and scripts.
  • Avoid Windows-centric terminology unless necessary, and ensure parity in instructions for both Windows and Linux environments.
GitHub Create Pull Request
Hdinsight Manage logs for an HDInsight cluster - Azure HDInsight ...ob/main/articles/hdinsight/hdinsight-log-management.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-centric tools (PowerShell, Visual Studio, System Center, .NET SDK, Power Query for Excel) are mentioned frequently and often before Linux alternatives. Many examples and scripting references use PowerShell, with limited or no equivalent Bash/Linux scripting examples. Some log access and management workflows are described in terms of Windows tools, with Linux approaches (such as Bash scripting or native Linux utilities) underrepresented or mentioned only briefly. The use of Ambari and SSH is covered, but scripting and automation examples are predominantly Windows-focused.
Recommendations
  • Provide Bash or shell script examples alongside PowerShell for log management and automation tasks.
  • Mention and describe Linux-native tools (e.g., rsync, scp, cron, logrotate, grep, awk, sed) for log collection, rotation, and analysis.
  • Include Linux/Unix command-line examples for accessing Azure Storage (e.g., azcopy, Azure CLI, s3cmd, rclone) and interacting with HDInsight clusters.
  • Balance references to Windows tools (Visual Studio, Power Query, System Center) with Linux alternatives (e.g., VS Code, LibreOffice Calc, Nagios, Zabbix).
  • Ensure that scripting and automation guidance is platform-neutral or provides parallel instructions for both Windows and Linux users.
GitHub Create Pull Request
Hdinsight Plan a virtual network for Azure HDInsight ...hdinsight/hdinsight-plan-virtual-network-deployment.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently presenting Azure PowerShell commands before Azure CLI commands, using PowerShell for scripting examples, and referencing Windows-centric tools and domains (e.g., windowsupdate.com). There are no explicit Linux shell or Bash examples, and the guidance does not mention Linux-specific tooling or patterns for network management, despite HDInsight clusters being Linux-based by default.
Recommendations
  • Present Azure CLI (cross-platform) examples before or alongside PowerShell commands, as CLI is more commonly used on Linux and macOS.
  • Include Bash shell scripting examples for tasks such as querying network interfaces, security groups, and routes.
  • Reference Linux tools (e.g., ip, netstat, dig, nslookup) for troubleshooting network connectivity and DNS issues within HDInsight clusters.
  • Avoid Windows-centric terminology (such as windowsupdate.com) when listing generic internet resources; use neutral examples.
  • Clarify that all management operations can be performed from Linux/macOS environments and provide explicit instructions or notes for non-Windows users.
  • Add a section or callout for Linux administrators, highlighting any differences or considerations when managing HDInsight networking from Linux systems.
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
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias in several ways: PowerShell is presented as the primary or only CLI method for triggering Azure Data Factory pipelines, with no equivalent Bash or Linux-native example. Power BI Desktop, a Windows-only tool, is the sole visualization option discussed, and Windows authentication patterns (username/password) are assumed. The use of Azure Storage Explorer (primarily Windows) is mentioned for verification, and the documentation refers to Windows tools and workflows before Linux alternatives, if at all.
Recommendations
  • Provide Bash/Azure CLI examples for triggering Data Factory pipelines, not just PowerShell.
  • Mention and demonstrate visualization options available on Linux/macOS, such as Power BI web, Apache Superset, or Jupyter Notebook.
  • Include instructions for using cross-platform tools (e.g., azcopy, web portal) for verification instead of or alongside Azure Storage Explorer.
  • Clarify authentication steps for Linux SSH clients and avoid assuming Windows username/password patterns.
  • Ensure that Linux/macOS users are given equal consideration in all workflow steps, with explicit examples and tool recommendations.
GitHub Create Pull Request
Hdinsight Enable Private Link on an Azure HDInsight cluster ...blob/main/articles/hdinsight/hdinsight-private-link.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: Windows-based examples and tools (such as PowerShell and Windows 10 VM) are presented before or instead of Linux equivalents, and step-by-step instructions for connectivity testing use Windows images and RDP, with no mention of Linux VMs or SSH-based workflows. PowerShell is referenced for cluster creation, but Linux shell or Bash examples are not provided. There are no explicit Linux-focused instructions or parity in tooling or examples.
Recommendations
  • Provide explicit Linux VM deployment instructions and examples alongside Windows VM instructions for connectivity testing.
  • Include Bash/Azure CLI examples for cluster creation and management, not just PowerShell.
  • Mention SSH as a primary access method for both Linux and Windows VMs, and provide examples for both platforms.
  • When listing VM images for testing, include popular Linux distributions (e.g., Ubuntu, CentOS) and show how to use them for Ambari and SSH access.
  • Ensure that all tooling references (e.g., Azure CLI, PowerShell) are balanced and that Linux users are not required to use Windows-specific tools or workflows.
GitHub Create Pull Request
Hdinsight Azure HDInsight supported node configurations ...es/hdinsight/hdinsight-supported-node-configuration.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by referencing PowerShell scripts as the primary example for cluster deployment, mentioning 'PowerShell or Azure CLI scripts' but providing guidance (such as SKU naming) specifically for PowerShell. There are no Linux-specific examples or references to Bash scripting, and no mention of Linux tools or patterns. The guidance for scripting and VM SKU usage is tailored to Windows/PowerShell users, with Linux parity lacking in examples and instructions.
Recommendations
  • Add explicit Bash/Azure CLI examples for cluster deployment alongside PowerShell references.
  • Clarify SKU naming conventions for both PowerShell and Bash/Azure CLI contexts.
  • Include references to Linux tools and scripting patterns where relevant.
  • Ensure that instructions and notes do not assume PowerShell as the default scripting environment.
  • Provide links to Linux-focused documentation or quickstarts for HDInsight cluster configuration.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting Windows-specific command examples (cmd, PowerShell) and environment setup instructions before or instead of Linux equivalents. The curl examples are described as 'based on a Windows environment,' and use Windows command syntax (set, ^ for line continuation), with no explicit Linux/bash alternatives. PowerShell is given a dedicated section, while Linux shell scripting is not. There is also a lack of guidance for Linux users regarding environment variables, line continuation, and jq usage. Windows tools and patterns are mentioned exclusively or first, and Linux parity is not achieved.
Recommendations
  • Provide Linux/bash-specific examples alongside Windows/cmd and PowerShell, including correct syntax for environment variables (export TOKEN=...), line continuation (\), and jq usage.
  • Clearly label which examples are for Windows and which are for Linux, and ensure both platforms are covered in each step.
  • Add a dedicated section for Linux shell scripting, mirroring the PowerShell section, using bash syntax and idioms.
  • Avoid describing curl examples as 'based on a Windows environment' unless Linux alternatives are immediately provided.
  • Mention Linux tools and patterns (bash, sh, export, etc.) before or alongside Windows tools.
  • Review all command snippets to ensure they are cross-platform, or provide parallel examples for each OS.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page lists Azure PowerShell and .NET SDK (both Windows-centric tools) before Azure CLI, which is more cross-platform. There is no explicit mention of Linux shell or Bash examples, and the ordering suggests a Windows-first approach. The absence of Linux-specific tools or examples (e.g., Bash, SSH) indicates a bias toward Windows environments.
Recommendations
  • Add explicit Linux/Bash examples and instructions alongside PowerShell and .NET SDK.
  • Reorder the list to alternate or prioritize cross-platform tools (e.g., Azure CLI before PowerShell).
  • Include references to Linux-native administration methods (e.g., SSH, Bash scripts) where applicable.
  • Clarify which tools are cross-platform and provide guidance for both Windows and Linux users.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/includes/hdinsight-selector-use-mapreduce.md ...hdinsight/includes/hdinsight-selector-use-mapreduce.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page lists PowerShell and .NET SDK (Windows-centric tools) prominently among the options for interacting with HDInsight MapReduce, with PowerShell appearing before Linux-native tools like SSH and Curl. There is a noticeable emphasis on Windows tools and patterns, and no explicit mention of Linux-specific alternatives or parity in examples.
Recommendations
  • Ensure Linux-native tools (e.g., SSH, Curl) are listed before or alongside Windows tools to avoid implying Windows is the default or preferred platform.
  • Add explicit examples and guidance for Linux users, including Bash scripts and Linux command-line usage.
  • Include references to cross-platform SDKs and tools, such as Python or Java, to broaden accessibility.
  • Clearly indicate platform compatibility for each tool or example, helping users identify which instructions apply to their environment.
GitHub Create Pull Request
Hdinsight Troubleshoot a slow or failing job on Azure HDInsight cluster ...les/hdinsight/hdinsight-troubleshoot-failed-cluster.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. While it does mention and provide examples for Azure CLI (cross-platform), it also references Azure PowerShell as a management option and links to PowerShell-specific documentation without providing equivalent Linux shell or Bash examples. The mention of PowerShell occurs before any Linux-specific command-line alternatives. Additionally, some instructions (such as accessing logs in storage accounts) use backslash notation, which is more familiar to Windows users. However, the page does acknowledge Linux-based clusters and tools like Ambari, and includes Bash/cURL examples in troubleshooting steps.
Recommendations
  • Provide Bash or Linux shell equivalents for all PowerShell examples, especially in cluster management and information gathering sections.
  • When listing management tools, mention cross-platform options (Azure CLI, Bash) before Windows-specific ones (PowerShell).
  • Ensure all file path examples use forward slashes or clarify platform differences.
  • Add explicit Linux command-line examples for common troubleshooting tasks (e.g., using SSH, SCP, or Bash scripts to gather logs).
  • Where PowerShell is referenced, include a note or link to Linux/Bash alternatives.
GitHub Create Pull Request
Hdinsight Upload data for Apache Hadoop jobs in HDInsight .../blob/main/articles/hdinsight/hdinsight-upload-data.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows-specific tools (Azure PowerShell, Cerulea, CloudXplorer, CloudBerry Explorer) are listed, some without Linux equivalents. Azure PowerShell is presented as a main utility for uploading data, but no Linux shell or Bash examples are given for equivalent tasks. Windows-only graphical clients are listed before cross-platform or Linux alternatives. The documentation lacks Linux-specific command-line examples for uploading data outside of the Hadoop command, and does not provide parity for PowerShell examples with Bash or Linux CLI equivalents.
Recommendations
  • Add Bash or Linux shell examples for uploading data to Azure Storage, especially where Azure PowerShell is mentioned.
  • Ensure that cross-platform tools (like Azure CLI and AzCopy) are emphasized before Windows-only tools.
  • Provide explicit Linux instructions for tasks currently only described with Windows tools (e.g., mounting Azure Storage as a local drive).
  • List graphical clients in order of cross-platform availability, or group by OS support, to avoid Windows-first presentation.
  • Include links to Linux-native or open-source alternatives where possible, and clarify any limitations for Linux users.
GitHub Create Pull Request
Hdinsight Connect Apache Kafka cluster with VM in different VNet on Azure HDInsight - Azure HDInsight ...fka/connect-kafka-cluster-with-vm-in-different-vnet.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows Example Present Linux Example Present Parity In Examples
Summary
The documentation provides instructions and examples for both Linux and Windows VMs when connecting to an HDInsight Kafka cluster across VNets. It includes explicit guidance for editing the hosts file on both platforms and demonstrates how to access the Ambari dashboard from each. However, the Linux example is presented first and in more detail (with command-line usage), while the Windows section is limited to a screenshot and a note about the hosts file location, lacking a concrete command or step-by-step instructions for accessing Ambari from Windows. There is no evidence of exclusive Windows bias; both platforms are mentioned, but Linux receives slightly more detailed treatment.
Recommendations
  • Provide explicit command-line instructions for accessing the Ambari dashboard from Windows (e.g., using PowerShell or curl for Windows).
  • Include a textual example of editing the Windows hosts file, similar to the Linux /etc/hosts example.
  • Ensure screenshots and step-by-step instructions are equally detailed for both Linux and Windows VMs.
  • Mention cross-platform tools (e.g., WSL, PowerShell Core) for users who may want to use Linux-style commands on Windows.
  • Clarify any platform-specific caveats for Kafka client usage, if applicable.
GitHub Create Pull Request
Hdinsight Quickstart: Apache Hive in Azure HDInsight with Apache Zeppelin ...t/interactive-query/hdinsight-connect-hive-zeppelin.md
High Priority View Details →
Scanned: 2026-01-11 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 bias toward Windows environments by referencing Visual Studio and PowerShell as tools for interacting with HDInsight clusters, while not providing equivalent Linux examples or alternatives. The 'Next steps' section directs users to Visual Studio, a Windows-centric tool, and the cluster deletion instructions mention PowerShell before Azure CLI, which is cross-platform. There are no explicit Linux or macOS instructions or examples, nor are Linux-native tools (e.g., Bash, SSH) mentioned.
Recommendations
  • Include instructions and examples for deleting clusters using Bash or Linux shell commands, in addition to PowerShell and Azure CLI.
  • Provide alternative next steps for Linux/macOS users, such as connecting via VS Code, Jupyter, or command-line tools.
  • Mention cross-platform tools first (e.g., Azure CLI) before Windows-specific tools like PowerShell or Visual Studio.
  • Add a note clarifying that Zeppelin and Hive queries can be run from any OS with a supported browser, not just Windows.
  • Reference Linux-native editors or IDEs (e.g., VS Code, Vim) for Hive development alongside Visual Studio.
GitHub Create Pull Request
Hdinsight Connect to Kafka using virtual networks - Azure HDInsight ...es/hdinsight/kafka/apache-kafka-connect-vpn-gateway.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by providing extensive PowerShell-based setup instructions for Azure resources and HDInsight clusters, with no equivalent Bash or Linux CLI examples for resource creation. The VPN client configuration mentions Windows and macOS, but Linux is omitted. The Python client section does include an Azure CLI snippet, but the overall workflow for cluster and network setup is Windows/PowerShell-centric, making it less accessible for Linux users.
Recommendations
  • Add equivalent Bash/Azure CLI scripts for all resource creation and configuration steps currently shown only in PowerShell.
  • Explicitly mention Linux support for the VPN client and provide instructions for connecting from Linux systems.
  • Where possible, present cross-platform commands (e.g., Azure CLI) before or alongside PowerShell examples.
  • Include notes or sections for Linux users, highlighting any OS-specific considerations or alternative tooling.
  • Review referenced documents to ensure Linux parity and link to Linux-specific guides where available.
GitHub Create Pull Request
Hdinsight Connect HDInsight Kafka cluster with client VM in different VNet on Azure HDInsight ...in/articles/hdinsight/kafka/connect-kafka-with-vnet.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Linux and Windows instructions for connecting a client VM to an HDInsight Kafka cluster across VNets. However, there is evidence of Windows bias: Windows-specific instructions (editing C:\Windows\System32\drivers\etc\hosts) are given their own section and are described in more detail, while Linux instructions are less prominent and lack parity in some areas (e.g., no explicit Linux example for Ambari login). Windows terminology and paths are mentioned before or more prominently than Linux equivalents in some places. There is also a lack of Linux-specific troubleshooting or advanced examples, and some commands are only shown for Windows.
Recommendations
  • Ensure Linux and Windows instructions are presented with equal detail and prominence.
  • Provide explicit Linux examples for all steps, including Ambari login and host file editing.
  • Where possible, present Linux and Windows instructions side-by-side or in parallel sections.
  • Include troubleshooting tips and advanced usage for Linux environments, matching those given for Windows.
  • Avoid mentioning Windows tools or paths before their Linux equivalents; use neutral language or alternate between platforms.
  • Clarify that all Java-based Kafka commands work identically on both platforms, and provide sample shell commands for Linux as well as Windows.
GitHub Create Pull Request
Hdinsight Configure service endpoint policies - Azure HDInsight ...b/main/articles/hdinsight/service-endpoint-policies.md
High Priority View Details →
Scanned: 2026-01-11 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 both Azure CLI and PowerShell examples for configuring service endpoint policies, but the CLI example is written using PowerShell syntax (variables, arrays) and is not a pure Bash/Linux shell example. The PowerShell example is given in full, while there is no equivalent Bash/Linux shell script. This creates a bias toward Windows users and PowerShell environments, potentially making it harder for Linux users to follow along or automate the process using native tools.
Recommendations
  • Provide a pure Bash/Linux shell example using Azure CLI, with standard Bash variable assignment and array handling.
  • Clearly separate Azure CLI (cross-platform) and PowerShell (Windows-centric) examples, labeling them for their intended environments.
  • Ensure that all steps shown in PowerShell are also demonstrated in Bash, including resource list handling and policy assignment.
  • Add notes or links for Linux users on how to install and use Azure CLI in their environment.
  • Review other documentation pages for similar patterns and update them to ensure Linux parity.
GitHub Create Pull Request
Hdinsight What is Apache Spark - Azure HDInsight ...main/articles/hdinsight/spark/apache-spark-overview.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias primarily by referencing Windows-centric tools (Azure PowerShell, .NET SDK, Power BI) before or instead of Linux alternatives. Examples and instructions for cluster creation mention Azure PowerShell and the Azure portal, with no mention of Linux command-line tools (e.g., Azure CLI, Bash scripts) or Linux desktop BI tools. The integration section highlights Microsoft IDEs (VS Code, IntelliJ with Azure Toolkit, Eclipse with Azure Toolkit) but does not mention Linux-native workflows or tools. There are no explicit Linux shell examples or references to Linux-specific patterns for cluster management or data access.
Recommendations
  • Add Linux-focused examples for cluster creation and management, such as using Azure CLI or Bash scripts.
  • Include references and examples for Linux desktop BI tools (e.g., Tableau on Linux, or open-source alternatives) alongside Power BI.
  • Mention and provide examples for using HDInsight Spark clusters from Linux environments, including SSH access, Linux-based notebooks, and Linux-native IDEs.
  • Ensure that instructions for SDKs and APIs include both Windows and Linux installation and usage steps.
  • Balance the order of tool mentions so that Linux and cross-platform options are presented alongside or before Windows-specific tools.
GitHub Create Pull Request
Hdinsight Azure Toolkit for IntelliJ: Debug Spark apps with SSH - HDInsight ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-intellij-tool-debug-remotely-through-ssh.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page displays Windows bias by addressing Windows-specific issues (WinUtils.exe) prominently in the prerequisites, providing detailed steps for Windows users, and referencing Windows environment variables and file paths. There is no equivalent troubleshooting or setup guidance for Linux/macOS users, and Windows solutions are described before noting they are unnecessary on other platforms.
Recommendations
  • Add explicit troubleshooting steps for Linux/macOS users, even if fewer issues are expected.
  • Provide Linux/macOS equivalents for environment variable setup and file paths where relevant.
  • Reorder platform-specific instructions so that Windows, Linux, and macOS are treated equally, or group them under clear platform headings.
  • Clarify that certain steps (e.g., WinUtils.exe) are only needed for Windows, and provide a brief explanation of why Linux/macOS do not require them.
  • Include links or references to common Linux/macOS Spark setup issues, if any, to ensure parity in support.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias in several areas: Windows-specific workarounds (WinUtils.exe) are described in detail without Linux equivalents; instructions for editing the hosts file are given only for Windows (Notepad, file path), with no mention of Linux/Mac workflows; PowerShell-based Azure networking instructions are listed before any Linux alternatives; and Cygwin is suggested for running scp commands on Windows, implying a Windows-centric audience. There is little to no guidance for Linux or Mac users in these key setup and troubleshooting steps.
Recommendations
  • Provide explicit instructions for editing the hosts file on Linux and Mac (e.g., using sudo nano /etc/hosts).
  • Include Linux/Mac-specific troubleshooting steps for remote debugging, and clarify that WinUtils.exe is not required on non-Windows platforms.
  • List Azure CLI or Bash-based networking setup options alongside or before PowerShell instructions.
  • Mention that scp is natively available on Linux and Mac, and provide examples for those platforms.
  • Review all steps to ensure parity for Linux/Mac users, including file paths, environment variable setup, and tool usage.
GitHub Create Pull Request
Hdinsight Azure Toolkit for IntelliJ: Spark app - HDInsight ...s/hdinsight/spark/apache-spark-intellij-tool-plugin.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily through the requirement for WINUTILS.EXE for local Spark console execution, which is a Windows-only tool. There are no equivalent instructions or troubleshooting for Linux or macOS users regarding local Spark execution. Additionally, the prerequisite steps and examples do not mention Linux-specific setup, nor do they provide parity for Linux environments where WINUTILS.EXE is not applicable. The documentation also lacks explicit Linux or macOS command-line examples, focusing instead on GUI steps that are platform-neutral but omitting platform-specific caveats.
Recommendations
  • Add instructions for running Spark locally on Linux and macOS, including any necessary environment variable setup and troubleshooting (e.g., HADOOP_HOME, permissions).
  • Clarify that WINUTILS.EXE is only required for Windows, and provide alternative steps or note that it is not needed for Linux/macOS.
  • Include Linux/macOS-specific prerequisites and troubleshooting sections, especially for local Spark execution.
  • Where platform-specific requirements exist (such as WINUTILS.EXE), mention them early and provide guidance for all supported platforms.
  • Consider adding a table or section comparing platform requirements and steps for Windows, Linux, and macOS users.
GitHub Create Pull Request
Hdinsight Use Apache Pig ...ocs/azure-docs/blob/main/articles/hdinsight/use-pig.md
High Priority View Details →
Scanned: 2026-01-11 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 exclusively mentioning SQL Server Integration Services (SSIS) and its Azure Feature Pack as a way to run Pig jobs, which are Windows-centric tools. There are no examples or walkthroughs for running Pig jobs from Linux environments, nor are Linux-native tools or command-line patterns (e.g., SSH, Bash, curl) described. The only integration example provided is for SSIS, with no mention of Linux alternatives or parity.
Recommendations
  • Add examples for running Pig jobs from Linux terminals, including SSH access and command-line execution.
  • Include walkthroughs using Linux-native tools (e.g., Bash scripts, curl, or Hadoop command-line utilities) to submit Pig jobs.
  • Mention cross-platform options first, or provide parallel instructions for both Windows and Linux users.
  • Reference Linux-friendly editors and environments (e.g., VS Code, Vim) for editing Pig Latin scripts.
  • Clarify that HDInsight clusters are typically Linux-based and provide guidance for both Windows and Linux users to connect and interact with them.
GitHub Create Pull Request
Hdinsight Tutorial: Analyze Azure HDInsight Apache Spark data with Power BI .../articles/hdinsight/spark/apache-spark-use-bi-tools.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Power BI Desktop, a Windows-only tool, and all step-by-step instructions and screenshots are for Windows environments. There are no examples or guidance for Linux users, such as using Power BI on the web, connecting via alternative BI tools, or using Linux-native workflows. Additionally, the prerequisites and clean-up instructions mention PowerShell and browser, but do not provide Linux-specific commands or alternatives (e.g., Bash, Azure CLI on Linux).
Recommendations
  • Add explicit instructions and screenshots for using Power BI Service (web) from Linux/macOS environments, including how to connect to HDInsight Spark clusters.
  • Mention and provide examples for alternative BI tools that are cross-platform (e.g., Tableau, Apache Superset, Grafana) and how to connect them to HDInsight Spark.
  • In the clean-up section, provide Linux/Bash/Azure CLI commands for deleting clusters, not just PowerShell or browser-based instructions.
  • Clarify which steps are Windows-specific and offer Linux/macOS equivalents where possible.
  • Include a note in the prerequisites about platform limitations of Power BI Desktop and recommend alternatives for non-Windows users.
GitHub Create Pull Request
Hdinsight Azure HDInsight ID Broker (HIB) ...in/articles/hdinsight/domain-joined/identity-broker.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure HDInsight ID Broker (HIB) demonstrates a Windows bias by referencing Windows Server as the platform for the ID Broker node, mentioning domain joining to Microsoft Entra Domain Services (a Windows-centric pattern), and omitting explicit Linux setup or tool examples. Tool integration highlights Visual Studio Code and IntelliJ, but does not mention Linux-specific tools or workflows. SSH/Kerberos access is described generically, but there are no Linux-specific authentication or troubleshooting examples. The documentation does not provide parity for Linux administrators or environments.
Recommendations
  • Include explicit instructions and examples for Linux-based clusters and environments, such as how to configure HIB on Linux VMs.
  • Add Linux-specific tool recommendations (e.g., command-line utilities, Linux-based IDEs) and workflows for cluster administration and authentication.
  • Provide troubleshooting steps and authentication flows for Linux users, including integration with Linux-based identity providers.
  • Clarify whether the ID Broker node can run on Linux, and if not, explain the rationale and alternatives for Linux-centric deployments.
  • Ensure examples (such as SSH, kinit, curl) are shown in both Windows and Linux contexts, highlighting any platform-specific considerations.
GitHub Create Pull Request
← Previous Page 4 of 35 Next →