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 251-275 of 867 flagged pages
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-with-entra-authentication/run-spark-jobs-using-rest-api.md ...-entra-authentication/run-spark-jobs-using-rest-api.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting all command-line examples using Windows-specific syntax (cmd), referencing Windows file paths (e.g., C:\Temp\input.txt), and using Windows environment variable setting (set). There is no mention of Linux/macOS equivalents, nor are Linux shell commands (e.g., export, /tmp/input.txt) provided. The use of AzCopy is neutral, but the examples and instructions assume a Windows environment throughout.
Recommendations
  • Provide parallel Linux/macOS examples for all command-line snippets, using bash syntax and Linux file paths (e.g., /tmp/input.txt, export clustername=CLUSTERNAME).
  • Explicitly mention that the instructions apply to both Windows and Linux/macOS, and highlight any differences in environment variable setting or file path conventions.
  • Include notes or sections for Linux users, such as how to create input files, set environment variables, and run curl commands in bash.
  • Where Windows tools or patterns are referenced (e.g., C:\Temp), offer Linux alternatives (e.g., /tmp).
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-09 00:34
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) as primary options for interacting with HDInsight MapReduce, alongside SSH and Curl. PowerShell is explicitly called out, and .NET SDK is typically associated with Windows development. The ordering places Windows tools before Linux equivalents, and there are no explicit Linux-specific tools or examples (e.g., Bash scripts, Linux CLI utilities) mentioned.
Recommendations
  • Add explicit Linux/Bash scripting examples and links, such as using Bash scripts to interact with HDInsight.
  • Include Linux-native tools (e.g., Hadoop CLI, SCP, rsync) in the selector list.
  • Balance the ordering of options so Linux and cross-platform tools (SSH, Curl) are listed before or alongside Windows-specific tools.
  • Provide parity in documentation depth and examples for both Windows and Linux environments.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/kafka/connect-kafka-with-vnet.md ...in/articles/hdinsight/kafka/connect-kafka-with-vnet.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy 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 a noticeable Windows bias: Windows instructions (editing the hosts file, accessing Ambari, running Java commands) are presented in a dedicated section after the Linux section, but the Windows steps are more detailed and include specific Windows paths and behaviors. The Linux section is brief and lacks parity in troubleshooting and command examples. The documentation references Windows-specific tools and patterns (e.g., editing C:\Windows\System32\drivers\etc\hosts) and does not provide equivalent PowerShell or Linux shell commands for some steps. There are also more screenshots and step-by-step guidance for Windows users.
Recommendations
  • Ensure Linux and Windows instructions are equally detailed and parallel in structure.
  • Provide explicit Linux shell commands for all steps, including editing /etc/hosts and troubleshooting connectivity.
  • Add troubleshooting tips and screenshots for Linux users similar to those provided for Windows.
  • Include PowerShell commands only where necessary and always provide Bash equivalents.
  • Present Linux and Windows instructions side-by-side or in a tabbed format to avoid implicit prioritization.
  • Mention Linux tools (e.g., nano, vi, curl) wherever Windows tools (e.g., Notepad, browser) are referenced.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/service-endpoint-policies.md ...b/main/articles/hdinsight/service-endpoint-policies.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 both Azure PowerShell and Azure CLI examples, but the CLI example uses Windows-style variable assignment and scripting syntax (e.g., $variable), which is not compatible with Bash or Linux shells. The PowerShell example is given in full, while there is no true Bash/Linux shell example. There is an implicit assumption that users are working in a Windows environment or using PowerShell, with no mention of Linux-specific patterns, tools, or shell scripting.
Recommendations
  • Provide a true Bash/Linux shell example for Azure CLI commands, using standard Bash variable assignment (e.g., subscriptionId="<subscription id>") and arrays.
  • Clarify which examples are for Windows/PowerShell and which are for Linux/Bash, and present them side-by-side for parity.
  • Avoid using Windows-style variable assignment ($variable) in CLI examples intended for cross-platform use.
  • Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and provide instructions or examples for each platform where relevant.
  • Add notes or sections for Linux users, including troubleshooting tips or differences in command syntax.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/interactive-query/apache-interactive-query-get-started.md ...eractive-query/apache-interactive-query-get-started.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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, Visual Studio Code, Hive ODBC/Excel) in the list of methods for executing Hive queries. These tools are either Windows-only or have a strong Windows association. Linux-native methods (Beeline, Ambari Hive View) are mentioned, but appear after Windows tools and without explicit Linux usage examples. There are no command-line Linux examples or references to Linux-specific workflows, and the page lacks parity in demonstrating how Linux users would interact with Interactive Query clusters.
Recommendations
  • Add explicit Linux command-line examples for connecting to Hive via Beeline, including sample commands and authentication steps.
  • Include references to Linux-native BI tools (e.g., Apache Zeppelin, DBeaver, SQuirreL SQL) and how to use them with Interactive Query.
  • Balance the order of tool presentation so that Linux-compatible methods are listed alongside or before Windows-centric tools.
  • Clarify platform compatibility for each tool, indicating which are cross-platform and which are Windows-only.
  • Provide guidance for Linux users on installing and configuring Beeline, Ambari, and JDBC clients.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/manage-clusters-runbooks.md ...ob/main/articles/hdinsight/manage-clusters-runbooks.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses PowerShell for all examples and instructions, with no mention of Bash, Python, or cross-platform alternatives. All automation steps, module installations, and runbook creation are described using PowerShell-specific modules and syntax, which are most familiar to Windows users. There is no guidance for Linux or macOS users, nor are Azure CLI or SDK alternatives presented. The documentation implicitly assumes a Windows-centric workflow, potentially excluding users who prefer or require Linux-native tools.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and widely used on Linux and macOS.
  • Include Bash script samples for runbook creation and cluster management.
  • Mention Python SDK or REST API options for automation, with code snippets.
  • Clearly state PowerShell is available on Linux and macOS, and provide installation instructions for non-Windows platforms.
  • Reorder sections or add parallel instructions so Linux-friendly tools are presented alongside or before Windows-specific ones.
  • Provide guidance on choosing between PowerShell and other automation tools based on user environment.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/monitor-hdinsight.md ...docs/blob/main/articles/hdinsight/monitor-hdinsight.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by mentioning PowerShell and Azure CLI as command-line options for enabling monitoring, but does not provide explicit Linux shell (bash) examples or clarify parity. The mention of PowerShell appears before Azure CLI, and there are no Linux-specific instructions or examples. The documentation assumes portal-based or Windows-centric workflows, with no guidance for Linux users beyond Ambari (which is only referenced as a web UI).
Recommendations
  • Provide explicit bash/Azure CLI examples for enabling and interacting with Azure Monitor integration, not just PowerShell.
  • When listing command-line options, mention Azure CLI (cross-platform) before PowerShell, or present both together with equal prominence.
  • Include Linux shell (bash) script examples for common monitoring tasks, such as enabling monitoring or querying logs.
  • Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide guidance for Linux users where appropriate.
  • If PowerShell is referenced, ensure that equivalent bash or shell commands are also provided.
  • Add a section or callout for Linux users, summarizing key steps or differences, especially since HDInsight clusters are Linux-based.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-eclipse-tool-plugin.md ...es/hdinsight/spark/apache-spark-eclipse-tool-plugin.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. The only platform-specific troubleshooting guidance for running Spark locally is for Windows (WinUtils.exe), with no mention of Linux or macOS equivalents. The instructions for setting environment variables and resolving local run issues are Windows-centric, and there are no examples or notes for Linux users. The documentation does not provide Linux-specific steps or acknowledge differences in local Spark setup on non-Windows platforms.
Recommendations
  • Add troubleshooting steps for running Spark locally on Linux and macOS, including common issues and environment setup.
  • Include instructions for setting environment variables on Linux/macOS (e.g., using export in bash/zsh).
  • Mention that WinUtils.exe is only required for Windows, and clarify that Linux/macOS do not need this file.
  • Provide parity in examples and screenshots, or add notes where platform-specific differences exist.
  • Explicitly state supported platforms for local Spark development and highlight any platform-specific requirements.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-intellij-tool-plugin-debug-jobs-remotely.md ...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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a Windows bias by providing explicit instructions and examples for Windows environments, such as editing the hosts file in C:\Windows\System32\Drivers\etc\hosts, using Notepad with elevated permissions, and referencing Windows-specific tools like WinUtils.exe and Cygwin for scp commands. PowerShell is mentioned as a primary method for network configuration, with no equivalent Bash or Linux CLI examples. Linux alternatives for editing the hosts file, handling environment variables, and resolving WinUtils.exe issues are absent or only referenced indirectly.
Recommendations
  • Add explicit instructions for Linux and macOS users, such as editing /etc/hosts with sudo and setting environment variables in ~/.bashrc or ~/.profile.
  • Provide Linux-native commands for copying files (e.g., using scp directly from a Linux terminal) and clarify that Cygwin is only needed for Windows.
  • Mention how to resolve the WinUtils.exe issue on Linux (i.e., that it is not required), and clarify platform-specific exceptions.
  • Include Bash or Azure CLI examples for network configuration alongside PowerShell instructions.
  • Ensure all file paths and configuration steps are presented for both Windows and Linux/macOS environments, either side-by-side or with clear platform notes.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-overview.md ...main/articles/hdinsight/spark/apache-spark-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. Windows-centric tools and patterns such as Azure PowerShell and Microsoft Power BI are mentioned before or instead of Linux alternatives. The instructions for cluster creation reference Azure PowerShell and the Azure portal, both of which are more commonly used on Windows. There is no mention of Linux command-line tools (e.g., Azure CLI) or Linux-specific workflows. Examples and integrations focus on Windows-based BI tools (Power BI) and IDEs (Visual Studio Code, IntelliJ, Eclipse), with no mention of Linux-native editors or tools. There are no explicit Linux shell or CLI examples, nor references to Linux package management or scripting.
Recommendations
  • Include Linux-specific instructions and examples, such as using Azure CLI or Bash scripts for cluster creation and management.
  • Mention Linux-native BI tools (e.g., Apache Superset, Grafana) alongside Power BI.
  • Provide examples using Linux command-line tools and workflows, such as SSH access, SCP, or working with Hadoop and Spark from a Linux terminal.
  • Clarify that HDInsight and Spark clusters can be managed from Linux environments and provide parity in documentation for both Windows and Linux users.
  • List Linux-compatible IDEs and editors (e.g., VS Code on Linux, Vim, Emacs) and provide guidance for their use.
  • Add explicit Linux shell examples for common tasks, such as submitting jobs, accessing storage, and monitoring clusters.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/use-pig.md ...ocs/azure-docs/blob/main/articles/hdinsight/use-pig.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 primarily by highlighting SQL Server Integration Services (SSIS) and its Azure Feature Pack as a method 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 (such as SSH, Bash, or Linux scripting) mentioned. The only external tool referenced for job submission is SSIS, and no Linux alternatives are provided or discussed.
Recommendations
  • Add examples for running Pig jobs from Linux environments, such as using SSH to connect to HDInsight and executing Pig scripts from the Bash shell.
  • Mention and provide walkthroughs for Linux-native tools (e.g., curl, scp, or the Azure CLI on Linux) for job submission and data upload.
  • Ensure that any Windows-specific integrations (such as SSIS) are balanced by equivalent Linux workflows, such as using Oozie, Bash scripts, or Python for orchestration.
  • Present cross-platform instructions in parallel, or clearly indicate which steps apply to Windows and which to Linux, to improve parity and accessibility for Linux users.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-use-bi-tools.md .../articles/hdinsight/spark/apache-spark-use-bi-tools.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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, which is primarily a Windows application, and does not provide Linux-specific guidance or alternatives for BI visualization. All examples and screenshots use Windows UI conventions and tools. There is no mention of Linux-compatible BI tools or how to perform similar tasks on Linux, nor are cross-platform alternatives discussed. The order of tool presentation and instructions assumes a Windows environment by default.
Recommendations
  • Include instructions for using Power BI on the web, which is accessible from Linux and macOS, or mention other cross-platform BI tools (e.g., Tableau, Apache Superset) that can connect to Spark.
  • Add explicit notes about Power BI Desktop's OS requirements and suggest alternatives for Linux users.
  • Provide examples or walkthroughs for connecting to Spark from Linux-based BI tools or via ODBC/JDBC from Linux.
  • Ensure that any references to deleting clusters or other management tasks include both Windows (PowerShell) and Linux (Azure CLI, Bash) examples, with equal prominence.
  • Add screenshots or UI references for web-based tools or Linux-compatible applications where possible.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/ldap-sync.md ...lob/main/articles/hdinsight/domain-joined/ldap-sync.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 referencing Windows-centric tools (such as ldp.exe and sAMAccountName), mentioning Samba/Winbind (Windows interoperability tools) as the mechanism for group membership projection, and suggesting Windows commands (net ads, ldp.exe) for LDAP filter testing. There are no Linux-native examples or equivalent Linux tools (e.g., ldapsearch) provided, and Windows patterns are mentioned before any Linux alternatives.
Recommendations
  • Include Linux-native command examples for LDAP filter testing, such as using ldapsearch.
  • Mention Linux equivalents to Windows tools (e.g., instead of ldp.exe, suggest ldapsearch or Apache Directory Studio).
  • Clarify that Samba/Winbind is used for Windows interoperability, and provide guidance for clusters that may not require Windows integration.
  • Ensure that documentation sections referencing Windows attributes (like sAMAccountName) also mention their relevance or mapping in Linux/Unix environments.
  • Add explicit Linux-focused troubleshooting steps and log locations where applicable.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/apache-domain-joined-configure-using-azure-adds.md ...ned/apache-domain-joined-configure-using-azure-adds.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: it provides only a PowerShell example for certificate creation, references Windows-specific tools (e.g., ldp.exe) for network testing, and recommends joining a Windows VM to the domain for validation. There are no equivalent Linux-based examples or instructions for these steps, and Windows tools and patterns are mentioned before any Linux alternatives (if at all).
Recommendations
  • Provide Linux-based examples for certificate creation, such as using OpenSSL to generate self-signed certificates with the required subject and SAN fields.
  • Include instructions for joining a Linux VM to the domain and validating domain connectivity using Linux tools (e.g., 'realm join', 'adcli', or 'sssd').
  • Suggest Linux alternatives for network testing, such as using 'ldapsearch' for LDAP connectivity instead of ldp.exe.
  • Ensure all steps that reference Windows tools or workflows are paired with equivalent Linux guidance, and present both options in parallel or in a platform-neutral order.
  • Explicitly mention cross-platform compatibility and provide links to Linux-specific documentation where relevant.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-on-premises-migration-best-practices-data-migration.md ...op-on-premises-migration-best-practices-data-migration.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows-centric tools (Azure Storage Explorer, AzCopy, Azure PowerShell) before mentioning cross-platform or Linux-native alternatives. There are no explicit Linux command-line examples or references to Linux-specific tools for data transfer, and PowerShell is mentioned without Bash or Linux shell equivalents. The only command-line example provided is for Hadoop DistCp, which is cross-platform, but there are no Linux-specific data migration tool examples or instructions.
Recommendations
  • Include Linux-native and cross-platform command-line examples for data transfer, such as using Azure CLI from Bash, SCP, rsync, or SFTP.
  • Mention Linux tools (e.g., curl, wget, rclone) alongside Windows tools when discussing data transfer options.
  • Provide Bash or shell script examples for common migration tasks, such as invoking AzCopy or Azure CLI from Linux.
  • Clarify which tools are cross-platform and provide installation instructions for both Windows and Linux environments.
  • Avoid listing Windows tools (e.g., PowerShell) before cross-platform or Linux alternatives; present them together or in parallel sections.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/apache-domain-joined-architecture.md ...ght/domain-joined/apache-domain-joined-architecture.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by focusing exclusively on Windows-centric identity providers (Active Directory, Microsoft Entra Domain Services), using only PowerShell for configuration examples, and referencing Windows tools and patterns (Active Directory, AD FS, PowerShell modules) without mentioning or providing Linux equivalents. There are no examples or guidance for Linux-based identity management, nor are cross-platform command-line alternatives (such as Bash, LDAP tools, or Kerberos utilities) discussed.
Recommendations
  • Provide equivalent configuration steps using Linux command-line tools (e.g., kinit, ldapsearch, realm, etc.) where possible.
  • Include examples for integrating HDInsight with non-Windows identity providers, or clarify if only Windows-based providers are supported.
  • Offer Bash or shell script alternatives to PowerShell commands for cross-platform administrators.
  • Explicitly state platform limitations and suggest workarounds or alternatives for Linux users.
  • Add documentation on how Linux administrators can interact with HDInsight clusters, especially for authentication and management tasks.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-on-premises-migration-best-practices-infrastructure.md ...op-on-premises-migration-best-practices-infrastructure.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates Windows bias primarily through the exclusive use of PowerShell examples (specifically the AZ module) for cluster configuration and bootstrap customization. There are no equivalent Linux shell (bash/CLI) or cross-platform examples provided for these operations. The documentation references Windows-centric tools and patterns before mentioning Linux alternatives, and does not provide parity for Linux users in key configuration sections.
Recommendations
  • Provide equivalent examples using Azure CLI (az hdinsight ...) and Bash scripts for cluster configuration and bootstrap customization.
  • Include instructions for performing the same operations from a Linux or macOS environment, not just PowerShell.
  • When referencing tools or automation, mention cross-platform options first or alongside Windows tools (e.g., Azure CLI, REST API, Bash).
  • Add explicit Linux shell examples for customizing HDInsight configs and running script actions.
  • Review all code samples and ensure both Windows and Linux workflows are covered equally.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/hdinsight-troubleshoot-data-lake-files.md ...sight/hadoop/hdinsight-troubleshoot-data-lake-files.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page provides a detailed PowerShell script for certificate management and cluster updates, but does not offer equivalent Linux/bash examples or alternatives. The use of PowerShell and Windows-centric tools is exclusive, with no mention of how to perform these operations on Linux systems, which are common for HDInsight clusters. This creates a bias toward Windows users and may hinder Linux users from following the troubleshooting steps.
Recommendations
  • Provide bash or Azure CLI equivalents for all PowerShell commands, especially for certificate creation, management, and cluster updates.
  • Include explicit instructions for Linux users on how to generate certificates and interact with Azure resources.
  • Mention cross-platform tools (e.g., Azure CLI, REST API) before or alongside PowerShell, to ensure parity.
  • Add notes clarifying which steps are platform-specific and offer alternatives for non-Windows environments.
  • Ensure all troubleshooting steps can be performed on both Windows and Linux systems, or clearly state any limitations.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/hdinsight-troubleshoot-converting-service-principal-certificate.md ...-troubleshoot-converting-service-principal-certificate.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell and C# examples for converting certificate contents to base-64, both of which are primarily used on Windows. There are no Linux or cross-platform command-line examples (such as OpenSSL or base64 commands), and Windows tools/patterns are mentioned exclusively and first.
Recommendations
  • Add Linux shell examples using commands like 'openssl' and 'base64' to convert .pfx files to base-64.
  • Include instructions for macOS users, as their workflow may differ slightly from Linux.
  • Present cross-platform solutions (e.g., Python scripts) that work on both Windows and Linux.
  • Reorder examples so that platform-neutral or Linux examples are presented alongside or before Windows-specific ones.
  • Explicitly mention that the conversion can be performed on any OS and provide parity in troubleshooting steps.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-tutorial-get-started-linux.md ...sight/hbase/apache-hbase-tutorial-get-started-linux.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates some Windows bias, particularly in the prerequisites section, where Bash usage is described in the context of Windows 10 and Windows Subsystem for Linux (WSL) is referenced before mentioning native Unix shells. Windows PowerShell's Invoke-RestMethod is suggested as an alternative for curl commands, and there is guidance on adapting curl examples for Windows Command Prompt. While the main tutorial steps use SSH, Bash, and standard HBase/Hive tools (which are cross-platform), the initial orientation and tool suggestions prioritize Windows environments and tools, potentially making Linux users feel secondary.
Recommendations
  • Present Linux/Unix-native instructions and examples first, with Windows adaptations as secondary notes.
  • Avoid framing Bash usage primarily in the context of Windows/WSL; acknowledge Bash as a standard shell on Linux and macOS.
  • Provide explicit Linux/macOS instructions for REST API usage, and mention Windows alternatives (PowerShell, Command Prompt) only as optional adaptations.
  • If referencing PowerShell or Windows-specific tools, ensure equivalent Linux/macOS commands are given equal prominence.
  • Clarify that all examples work natively on Linux and macOS, and only require adaptation for Windows environments.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively using PowerShell scripts for all command-line operations, with no mention or examples of Bash, Azure CLI, or Linux-native workflows. The prerequisites and resource creation steps assume the reader is using PowerShell, which is most commonly available on Windows. There are no Linux-specific instructions or parity examples for users who may prefer Bash or Azure CLI on Linux or macOS. The documentation also references the Azure portal for verification and management, but does not provide alternative command-line options for non-Windows users.
Recommendations
  • Provide equivalent Azure CLI and Bash script examples for all PowerShell commands, especially for resource group and storage account creation and file copying.
  • Include a section in prerequisites for Linux/macOS users, specifying installation and usage of Azure CLI.
  • Add notes or callouts indicating that all steps can be performed on Linux/macOS, and provide links to relevant Azure CLI documentation.
  • Where PowerShell is used, offer side-by-side examples or a toggle for Bash/Azure CLI commands.
  • Ensure terminology and screenshots do not assume Windows-only environments (e.g., avoid referencing only PowerShell or Windows-specific UI elements).
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-customize-cluster-bootstrap.md ...nsight/hdinsight-hadoop-customize-cluster-bootstrap.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by providing detailed PowerShell examples and a full PowerShell script in the appendix, while omitting equivalent Linux/bash examples. The prerequisites and tooling focus on PowerShell and .NET SDK, both Windows-centric, and the order of presentation puts Windows tools first. There is only a passing mention of Linux via a link to a separate page, with no direct Linux/bash content or parity in example depth.
Recommendations
  • Add equivalent bash or Azure CLI examples for customizing HDInsight cluster configurations, especially for bootstrap actions.
  • Include Linux-focused prerequisites and instructions, such as installing Azure CLI and using shell scripts.
  • Balance the order of presentation by showing Linux/bash methods before or alongside PowerShell/.NET examples.
  • Provide a full Linux/bash sample script in the appendix, mirroring the PowerShell sample.
  • Explicitly mention cross-platform compatibility and guide users on choosing between Windows and Linux tools.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-plan-virtual-network-deployment.md ...hdinsight/hdinsight-plan-virtual-network-deployment.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Command-line examples for network configuration and resource discovery are consistently presented first in Azure PowerShell, followed by Azure CLI. There are no explicit Linux shell (bash) examples, and the PowerShell syntax is given prominence. The documentation refers to Windows-centric domains (e.g., windowsupdate.com) and does not mention Linux-specific tools or workflows for cluster/network management. The creation steps for HDInsight clusters reference PowerShell and 'Classic CLI', but do not provide parity for Linux-native tools or scripts.
Recommendations
  • Provide bash shell examples alongside PowerShell and Azure CLI, especially for resource discovery and network configuration tasks.
  • When listing command-line options, alternate the order or present Azure CLI (cross-platform) before PowerShell to avoid Windows-first bias.
  • Include references to Linux-native management tools or scripts where appropriate (e.g., using curl, jq, or bash for network diagnostics).
  • Explicitly state that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Add troubleshooting steps or examples relevant to Linux environments, such as using iptables, netstat, or systemd-resolved for DNS and network issues.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/includes/hdinsight-selector-use-sqoop.md ...les/hdinsight/includes/hdinsight-selector-use-sqoop.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation lists PowerShell and .NET examples prominently alongside SSH and Curl, with PowerShell specifically called out as a main method. This suggests a bias towards Windows tools and workflows, as PowerShell and .NET are primarily Windows-centric. The ordering also places Windows tools before Linux equivalents, and there is no explicit mention of Bash or Linux shell examples.
Recommendations
  • Add explicit Bash or Linux shell examples and links, ensuring parity with PowerShell.
  • Reorder the selector to alternate or randomize platform-specific tools, or group by platform to avoid implicit prioritization.
  • Include a note clarifying cross-platform support and equivalence between Windows and Linux workflows.
  • Ensure that Linux-native tools (e.g., Bash, native SSH) are given equal prominence and detail as Windows tools.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/disk-encryption.md ...e-docs/blob/main/articles/hdinsight/disk-encryption.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is used for key deployment and cluster creation examples, and is the only scripting language shown for ARM template deployment and enabling encryption at host. Windows-centric tools and patterns (PowerShell, Azure portal UI) are mentioned before their CLI or Linux equivalents, and there are no explicit Linux shell (bash) examples for cluster creation or key management. Recovery instructions reference PowerShell cmdlets before CLI commands. The documentation lacks parity for Linux users, who may prefer bash or other shell scripting approaches.
Recommendations
  • Add bash shell script examples for ARM template deployment and cluster creation, alongside PowerShell examples.
  • When listing command-line examples, present Azure CLI (cross-platform) before PowerShell, or at least in parallel.
  • Include instructions for Linux users, such as using bash, curl, or other native Linux tools for key management and deployment.
  • Reference Azure CLI and REST API as primary automation interfaces, with PowerShell as an alternative for Windows users.
  • Ensure recovery instructions (e.g., key recovery) include both CLI and PowerShell commands, with equal prominence.
  • Clarify that all operations can be performed from Linux, macOS, and Windows, and provide explicit cross-platform guidance.
GitHub Create Pull Request
← Previous Page 11 of 35 Next →