Hdinsight

878
Total Pages
777
Linux-Friendly Pages
101
Pages with Bias
11.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

200 issues found
Showing 76-100 of 200 flagged pages
Hdinsight Apache Ambari heartbeat issues in Azure HDInsight .../hadoop/apache-ambari-troubleshoot-heartbeat-issues.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides Linux-oriented troubleshooting steps for Ambari agent issues, but in the 'Heartbeat lost for Ambari' scenario, it exclusively references a PowerShell cmdlet (Disable-AzHDInsightMonitoring) for disabling Azure Monitor logging, with no Linux or Bash equivalent. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer Bash/Azure CLI. Additionally, the documentation does not mention or prioritize Linux alternatives for Azure Monitor management.
Recommendations
  • Provide Azure CLI or Bash commands for disabling Azure Monitor logging alongside the PowerShell example.
  • Explicitly state platform requirements for each command, and offer cross-platform alternatives where possible.
  • Include links or references to Linux/macOS documentation for Azure Monitor management.
  • Consider the order of examples, ensuring Linux/Bash commands are presented first or in parallel with Windows/PowerShell commands.
GitHub Create Pull Request
Hdinsight Quickstart: Query Apache HBase in Azure HDInsight - HBase Shell ...ticles/hdinsight/hbase/query-hbase-with-hbase-shell.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily uses Windows-style SSH connection syntax and does not provide explicit Linux/macOS command examples or guidance. The SSH command is shown in Windows CMD formatting, and there is no mention of Linux/macOS terminal usage or differences. References to PowerShell and Azure CLI for cluster deletion are present, but not detailed in this page.
Recommendations
  • Provide both Windows and Linux/macOS SSH command examples, clarifying any differences in syntax or prerequisites (e.g., using PuTTY on Windows, native terminal on Linux/macOS).
  • Explicitly mention how to open a terminal on Linux/macOS and run the SSH/HBase shell commands.
  • Where cluster deletion is referenced, ensure Linux/macOS Azure CLI instructions are included or linked.
  • Avoid using Windows CMD formatting for commands unless accompanied by equivalent bash examples.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides host information retrieval commands specifically for Windows command prompt, using Windows-style paths and syntax, and explicitly states that 'slight variations will be needed for other environments.' No Linux/macOS equivalent commands are given, and the Windows example is presented first and exclusively. Other steps (Jupyter, Scala, bash) are platform-neutral, but the initial cluster info retrieval is Windows-biased.
Recommendations
  • Provide Linux/macOS versions of the host information retrieval commands, using standard Linux paths and syntax (e.g., jq, curl).
  • Present both Windows and Linux/macOS examples side-by-side, or default to Linux/macOS first, given the prevalence of these platforms in data engineering.
  • Clarify any platform-specific differences in command usage, such as path separators and executable invocation.
  • Consider using cross-platform tools or scripting approaches (e.g., Python) for steps that require OS-specific commands.
GitHub Create Pull Request
Hdinsight Customize Azure HDInsight clusters by using script actions .../hdinsight/hdinsight-hadoop-customize-cluster-linux.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page provides examples and instructions for using script actions in Azure HDInsight clusters. While the underlying script actions are Bash scripts (Linux-centric), the documentation frequently presents Windows-oriented tools (Azure PowerShell, .NET SDK) before Linux-friendly equivalents (Azure CLI, REST API). PowerShell examples are more detailed and appear first in several sections, and references to Windows tools (.NET SDK, PowerShell) are more prominent than Linux-native workflows.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, especially in sections where both are applicable.
  • Expand Azure CLI usage examples to match the detail and coverage of PowerShell examples.
  • Add explicit instructions for running script actions from Linux/macOS environments, including shell commands and automation patterns.
  • Clarify that all script actions are Bash scripts and can be managed from Linux systems using Azure CLI and REST API.
  • Reduce emphasis on Windows-specific tools (PowerShell, .NET SDK) or balance with Linux-native alternatives.
  • Include troubleshooting and history retrieval examples using Azure CLI and REST API, not just PowerShell.
GitHub Create Pull Request
Hdinsight Azure Monitor Agent (AMA) migration guide for Azure HDInsight clusters ...cs/blob/main/articles/hdinsight/azure-monitor-agent.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. The PowerShell approach is described in detail before the Azure CLI approach, and PowerShell is explicitly required for some cross-subscription scenarios. Windows-centric tools (PowerShell, azcopy) and patterns are referenced more frequently and with more detail than Linux-native equivalents. While Azure CLI instructions are provided, PowerShell is often presented as the default or prerequisite, and Linux-specific nuances (such as shell scripting or alternative tools) are not discussed. There are no explicit Linux/macOS examples or troubleshooting notes.
Recommendations
  • Add explicit Linux/macOS instructions and examples, especially for steps involving PowerShell or azcopy.
  • Clarify when PowerShell is required and provide alternatives for Linux/macOS users (e.g., Bash, REST API calls via curl).
  • Present Azure CLI instructions before or alongside PowerShell to avoid Windows-first impression.
  • Include notes on installing and using required tools (e.g., jq, azcopy) on Linux/macOS.
  • Provide troubleshooting tips for common Linux/macOS issues (e.g., file permissions, environment variables).
GitHub Create Pull Request
Hdinsight Manage Enterprise Security Package clusters - Azure HDInsight ...hdinsight/domain-joined/apache-domain-joined-manage.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 frequently references Windows-centric tools (Visual Studio Code, Power BI, Visual Studio Tools, Excel) and provides examples or instructions for these before mentioning cross-platform or Linux-native alternatives. There are no explicit Linux/macOS command-line examples, and tools like PowerShell are referenced for external job execution, while Linux equivalents (e.g., Bash, Linux desktop tools) are not mentioned. The documentation does not provide parity for Linux/macOS users in terms of examples or tool recommendations.
Recommendations
  • Include Linux/macOS-specific instructions and examples for cluster management, such as using terminal commands, Linux desktop tools, or open-source alternatives.
  • Provide examples using Linux-native tools (e.g., Bash, curl, or Linux-based IDEs like Kate, Gedit, or VS Code on Linux) for connecting to clusters.
  • Mention cross-platform alternatives to Windows-only tools (e.g., alternatives to Power BI, Visual Studio Tools, or Excel) and clarify which tools are available on Linux/macOS.
  • Ensure that examples and tool recommendations are presented in a platform-neutral order, or explicitly call out platform-specific steps for both Windows and Linux/macOS users.
GitHub Create Pull Request
Hdinsight Authentication issues in Azure HDInsight ...t/domain-joined/domain-joined-authentication-issues.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation mentions Windows AD tools as a way to browse for sAMAccountName, listing them before Linux alternatives. There is a link to a tutorial for creating a domain-joined Windows VM, but no equivalent guidance for Linux. In the 'Kinit fails' section, Windows tools are referenced first, and Linux (Samba) commands are mentioned only after. There are no PowerShell-specific examples, but Windows-centric tools and workflows are prioritized or exclusively mentioned in some places.
Recommendations
  • Provide equivalent instructions for browsing AD from Linux/macOS (e.g., using ldapsearch, samba, or other open-source tools).
  • Include links or steps for creating a domain-joined Linux VM for management tasks.
  • Present Linux/macOS methods before or alongside Windows methods when listing troubleshooting steps.
  • Ensure all examples (such as searching for sAMAccountName) have both Windows and Linux/macOS variants.
  • Avoid referencing Windows tutorials exclusively; offer cross-platform alternatives.
GitHub Create Pull Request
Hdinsight Azure HDInsight ID Broker (HIB) ...in/articles/hdinsight/domain-joined/identity-broker.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias. It repeatedly references Windows Server VMs as the hosting environment for the HDInsight ID Broker node, with no mention of Linux alternatives. The authentication infrastructure is described as running on Windows Server, and the domain join process is implicitly Windows-centric. Tooling examples (IntelliJ, VS Code) are cross-platform, but the underlying infrastructure and administrative patterns assume Windows environments. There are no explicit Linux or macOS setup instructions, nor is there discussion of Linux-based domain join or VM hosting.
Recommendations
  • Clarify whether the HDInsight ID Broker node must run on Windows Server, or if Linux-based VMs are supported.
  • If Linux is supported, provide equivalent instructions and examples for Linux VM setup, domain join, and administration.
  • Explicitly mention OS requirements and alternatives in the 'Enable HDInsight ID Broker' and infrastructure sections.
  • Include troubleshooting or operational notes for Linux/macOS users where relevant.
  • Ensure parity in administrative patterns (e.g., SSH, Kerberos) for Linux environments.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions and examples for rebooting HDInsight cluster VMs using PowerShell, a Windows-centric tool, with no equivalent CLI or shell examples for Linux/macOS users. The PowerShell method is presented first and in more detail, while the REST API method is more generic and lacks platform-specific guidance for Linux users. There are no Azure CLI, Bash, or Linux-native instructions or examples.
Recommendations
  • Add equivalent Azure CLI commands for listing and restarting HDInsight cluster nodes, with example syntax.
  • Provide Bash/cURL examples for invoking the REST API, including sample request bodies and authentication guidance.
  • Clarify cross-platform support for each method, explicitly noting which tools are available on Linux/macOS.
  • Reorder or balance the documentation so that Windows and Linux/macOS methods are presented with equal prominence.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for cluster creation and encryption management, but PowerShell is featured prominently, especially for ARM template deployment and enabling encryption at host. The ARM template deployment example is shown only with PowerShell, and PowerShell is mentioned in the FAQ for key recovery before the CLI equivalent. There are no Linux shell (bash) or macOS-specific examples, and PowerShell is a Windows-centric tool. The ordering of examples sometimes places PowerShell before CLI, and the use of PowerShell for ARM template deployment may create friction for Linux/macOS users.
Recommendations
  • Add bash (Linux/macOS) examples for ARM template deployment using Azure CLI (e.g., az deployment group create).
  • Where PowerShell is used, provide equivalent bash/CLI commands and mention cross-platform alternatives.
  • In the FAQ, list CLI and PowerShell recovery options together or put CLI first to avoid Windows-first ordering.
  • Clarify that Azure CLI is cross-platform and recommend it for Linux/macOS users.
  • Review and balance the ordering of examples so that CLI or bash examples are not always after PowerShell.
GitHub Create Pull Request
Hdinsight Configure clusters for Microsoft Entra integration ...ned/apache-domain-joined-configure-using-azure-adds.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 notable Windows bias. The only explicit command-line example is given in PowerShell for creating a self-signed certificate, with no Linux or cross-platform alternative. Network validation and troubleshooting steps are described exclusively using Windows VMs and Windows tools (e.g., ldp.exe), with no mention of Linux equivalents. Windows-centric terminology and instructions (such as joining a Windows VM to the domain and using Windows-specific utilities) appear before or instead of Linux approaches. No Linux/macOS command-line examples are provided for key steps such as certificate creation or LDAP testing.
Recommendations
  • Provide equivalent Linux/macOS command-line examples for certificate creation (e.g., using openssl).
  • Include instructions for validating domain connectivity and LDAP access from Linux VMs (e.g., using ldapsearch, openssl s_client).
  • Mention Linux tools and workflows alongside Windows tools, not just as an afterthought.
  • Ensure all critical steps (certificate creation, network validation, domain join) have Linux/macOS guidance.
  • Consider reordering examples so that cross-platform or Linux options are presented equally or first.
GitHub Create Pull Request
Hdinsight Apache Hive policies in Apache Ranger - Azure HDInsight ...insight/domain-joined/apache-domain-joined-run-hive.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 by exclusively describing how to test Ranger policies using Excel and the Microsoft Hive ODBC driver, both Windows-centric tools. All step-by-step examples focus on Windows/Excel workflows, with no mention of Linux/macOS alternatives (such as using Beeline, DBeaver, or other cross-platform SQL clients). The prerequisites and instructions assume access to Microsoft Office, and the ODBC driver dialog references Windows-specific UI. Linux/macOS users are left without guidance for verifying Ranger policies or connecting to Hive tables.
Recommendations
  • Add instructions and examples for testing Ranger policies using Linux/macOS tools, such as Beeline, DBeaver, or SquirrelSQL.
  • Include steps for connecting to Hive via JDBC from Linux/macOS, referencing the relevant documentation.
  • Provide parity in examples: show both Windows/Excel/ODBC and Linux/macOS/Beeline/JDBC workflows for verifying policy enforcement.
  • Clarify which steps are platform-specific and offer alternatives for non-Windows environments.
GitHub Create Pull Request
Hdinsight Enterprise security general guidelines in Azure HDInsight ...articles/hdinsight/domain-joined/general-guidelines.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page references several Windows-centric technologies and patterns, such as Active Directory, Kerberos, and LDAP, which are traditionally associated with Windows environments. It mentions administrative tools and concepts like 'domain join', 'OU', and 'SAMAccountName', and links to Windows Server Active Directory compatibility. The only explicit command-line example (ktutil for keytab generation) is Linux-based, but the overall guidance and terminology are heavily oriented toward Windows/Active Directory paradigms. There are no PowerShell-only examples, but Windows tools and concepts are presented as the default, with little mention of Linux/macOS equivalents or alternative approaches.
Recommendations
  • Add explicit notes or examples for Linux/macOS users where Windows/Active Directory tools or terminology are used.
  • Clarify which steps are OS-agnostic and which require Windows-specific tools, and provide alternatives or references for Linux/macOS environments.
  • Where administrative tasks reference Windows tools (e.g., Active Directory Users and Computers), mention equivalent approaches for Linux (e.g., using ldapsearch, samba-tool, etc.) if possible.
  • Ensure that any command-line instructions (such as keytab generation) are clearly marked as Linux/Unix commands, and provide guidance for Windows users if relevant.
  • Consider adding a section summarizing OS requirements and cross-platform considerations for cluster administrators.
GitHub Create Pull Request
Hdinsight Overview of enterprise security in Azure HDInsight ...hdinsight/domain-joined/hdinsight-security-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It emphasizes Active Directory-based authentication (a Windows-centric technology) and references Microsoft Entra Domain Services and PowerShell as access methods before mentioning REST APIs. There are no explicit Linux/macOS-specific examples or alternative authentication methods, and the documentation does not address how Linux users might interact with HDInsight clusters (e.g., via SSH, Linux CLI tools, or Kerberos). The focus on Windows tools and patterns may create friction for Linux/macOS users.
Recommendations
  • Include examples of accessing HDInsight clusters using Linux/macOS tools (e.g., SSH, curl, Linux CLI for REST APIs).
  • Mention Kerberos or other non-Active Directory authentication options if available.
  • Provide parity in examples: show both PowerShell and Bash (or other Linux shell) commands for cluster management and data access.
  • Clarify how Linux/macOS users can authenticate and interact with clusters, especially in environments without Active Directory.
  • Explicitly state cross-platform compatibility for all features and tools mentioned.
GitHub Create Pull Request
Hdinsight Use C# with MapReduce on Hadoop in HDInsight - Azure ...oop/apache-hadoop-dotnet-csharp-mapreduce-streaming.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits a moderate Windows bias. Visual Studio is presented as the primary development environment, and the upload instructions rely heavily on Visual Studio's Azure integration, which is Windows-centric. PowerShell is highlighted as a scripting option, with no mention of Bash or Linux-native alternatives for job submission or file upload. Linux parity is partially addressed by including SSH-based job submission, but the overall workflow assumes Windows tools and patterns first.
Recommendations
  • Provide instructions for building C# projects using cross-platform tools like dotnet CLI or MonoDevelop, not just Visual Studio.
  • Include alternative methods for uploading files to HDInsight storage using Azure CLI, azcopy, or Hadoop fs commands, which work on Linux/macOS.
  • Offer Bash or shell script examples for job submission and result retrieval, alongside PowerShell.
  • Clarify which steps are platform-independent and which require Windows-specific tools.
  • Reorder sections so that cross-platform or Linux-native methods are presented before or alongside Windows-specific instructions.
GitHub Create Pull Request
Hdinsight Java user-defined function (UDF) with Apache Hive Azure HDInsight ...ticles/hdinsight/hadoop/apache-hadoop-hive-java-udf.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 notable Windows bias: all setup, file manipulation, and editor commands are shown using Windows tools (cmd, Notepad, PowerShell), with explicit reference to Windows 10 as the test environment. Linux/macOS equivalents (e.g., bash, nano/vim, rm, mkdir) are not provided, and Windows instructions are presented first and exclusively in critical sections. Troubleshooting also relies on PowerShell scripts for line ending fixes, with no Linux alternatives.
Recommendations
  • Provide parallel Linux/macOS command examples for all file and directory operations (e.g., mkdir, cd, rm -rf).
  • Include instructions for editing files using common Linux/macOS editors (e.g., nano, vim, emacs) alongside Notepad.
  • Offer troubleshooting steps for line ending issues using Linux tools (e.g., dos2unix, sed) in addition to PowerShell.
  • Clarify that the process is cross-platform and explicitly mention how Linux/macOS users should adapt each step.
  • Avoid stating only Windows as the test environment; mention that the process works on Linux/macOS and provide examples.
GitHub Create Pull Request
Hdinsight C#, Apache Hive & Apache Pig on Apache Hadoop - Azure HDInsight ...ght/hadoop/apache-hadoop-hive-pig-udf-dotnet-csharp.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Visual Studio Heavy Missing Linux Example
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio, with all examples and step-by-step instructions assuming use of Visual Studio on Windows. There are no instructions or examples for building C# UDFs on Linux/macOS (e.g., using Mono's tools, .NET CLI, or VS Code on Linux). Upload and job submission steps are also tied to Visual Studio and Azure Data Lake Tools, with only minimal mention of alternatives (Azure CLI, PowerShell) and no Linux-specific workflows. This creates friction for Linux/macOS users who wish to develop and deploy C# UDFs for HDInsight.
Recommendations
  • Add instructions for building C# projects using Mono and/or .NET CLI on Linux/macOS.
  • Provide examples for using VS Code or other cross-platform editors, not just Visual Studio.
  • Include steps for uploading .exe files using Azure CLI or other cross-platform tools, with explicit Linux/macOS commands.
  • Document how to run Hive queries and Pig jobs using SSH, Azure CLI, or other non-Windows tools, rather than only through Visual Studio.
  • Consider reordering or parallelizing instructions so Linux/macOS workflows are presented alongside Windows ones.
GitHub Create Pull Request
Hdinsight Extract, transform, and load (ETL) at scale - Azure HDInsight ...rticles/hdinsight/hadoop/apache-hadoop-etl-at-scale.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates moderate Windows bias, especially in the 'Ingest file storage and result storage' section, where Windows-centric tools (PowerShell, AzCopy) are mentioned first and most prominently for data ingestion into Azure Storage. Linux alternatives (such as CLI, SDKs, or Hadoop-native tools) are mentioned later or not at all in some cases. The page also references Azure PowerShell for Data Lake Storage ingestion, again prioritizing Windows tooling. There is limited coverage of Linux/macOS-specific workflows or examples, and no explicit Linux shell command examples are provided.
Recommendations
  • Add explicit Linux/macOS command-line examples for data ingestion, such as using Azure CLI, Hadoop DistCp, or SDKs from Bash.
  • Mention Linux-native tools (e.g., curl, wget, hdfs dfs, distcp) alongside or before Windows tools when describing ingestion workflows.
  • Provide parity in tool recommendations: for every PowerShell/AzCopy mention, include equivalent Linux/macOS instructions.
  • Clarify that SDKs and REST APIs are cross-platform and provide example usage from Linux environments.
  • Consider reordering tool mentions to avoid Windows-first presentation, or group them by platform.
GitHub Create Pull Request
Hdinsight Infrastructure: On-premises Apache Hadoop to Azure HDInsight ...op-on-premises-migration-best-practices-infrastructure.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias, primarily in the 'Customize HDInsight configs using Bootstrap' section, where only PowerShell (Windows-centric) examples are provided for cluster configuration. The use of Azure PowerShell modules and cmdlets is highlighted without equivalent Bash, CLI, or Linux-native alternatives. While the rest of the document references Linux edge nodes and Bash script actions, the critical configuration example is Windows/PowerShell-only, and Windows tools are mentioned before Linux equivalents.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for customizing HDInsight configs, especially for cluster bootstrap and configuration tasks.
  • Explicitly mention Linux/macOS workflows and tools where PowerShell is referenced, and clarify cross-platform options.
  • Reorder examples to show Linux/Bash approaches first or side-by-side with Windows/PowerShell examples.
  • Add notes or links to documentation for Linux/macOS users on how to perform the same tasks without PowerShell.
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-11 06:20
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=), Windows environment variable notation (%VAR%), and reference a Windows-specific jq binary path (C:\HDI\jq-win64.exe). There are no Linux/macOS shell examples (e.g., export VAR=, $VAR, ./jq), nor is there guidance for adapting commands to bash/zsh environments. Windows tools and patterns are mentioned exclusively and first, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent Linux/macOS shell examples for all commands, using bash syntax (export VAR=, $VAR).
  • Mention both Windows and Linux/macOS jq installation and usage, including typical Linux paths (e.g., /usr/bin/jq).
  • Add a note or table summarizing environment variable syntax differences between Windows and Linux/macOS.
  • Ensure references to tools (SQL clients, jq) include cross-platform options and installation instructions.
  • Consider alternating or parallel presentation of examples for both platforms.
GitHub Create Pull Request
Hdinsight Unable to access Data Lake storage files in Azure HDInsight ...sight/hadoop/hdinsight-troubleshoot-data-lake-files.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides a detailed PowerShell script for certificate management, which is Windows-centric and does not mention or provide equivalent steps for Linux/macOS users. There is no guidance on using Azure CLI, OpenSSL, or other cross-platform tools for certificate creation and assignment. The PowerShell approach is presented as the only method, creating friction for non-Windows users.
Recommendations
  • Add equivalent instructions using Azure CLI for certificate assignment and management.
  • Provide OpenSSL-based steps for certificate creation, which work on Linux/macOS.
  • Explicitly state platform requirements for the PowerShell script and offer alternatives.
  • Reorder examples so that cross-platform methods (e.g., Azure CLI) are presented before or alongside PowerShell.
  • Include troubleshooting steps and commands that are platform-agnostic wherever possible.
GitHub Create Pull Request
Hdinsight Security: Migrate on-premises Apache Hadoop to Azure HDInsight ...p-on-premises-migration-best-practices-security-devops.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by focusing exclusively on Microsoft Entra Domain Services (formerly Azure AD DS), Active Directory, and related Windows-centric tools and patterns for cluster security and management. There are no examples or guidance for equivalent Linux-native identity management or authentication solutions, nor are alternatives like LDAP, Kerberos, or local Linux user management discussed. All examples and instructions assume a Windows-based domain environment, which may create friction for organizations with Linux-based infrastructure.
Recommendations
  • Include guidance or examples for integrating HDInsight clusters with Linux-native identity management solutions (e.g., OpenLDAP, MIT Kerberos).
  • Provide instructions for cluster security and RBAC using non-Active Directory methods, such as local users/groups or Linux PAM modules.
  • Add parity in examples, showing both Windows/Active Directory and Linux/LDAP/Kerberos approaches where possible.
  • Explicitly state any limitations or requirements for non-Windows environments, and link to relevant Linux documentation if available.
GitHub Create Pull Request
Hdinsight Use MapReduce and Curl with Apache Hadoop in HDInsight - Azure ...s/hdinsight/hadoop/apache-hadoop-use-mapreduce-curl.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. Command examples for Curl use Windows CMD syntax (set, ^ line continuation, Windows paths for jq), and PowerShell is presented as the only alternative scripting environment. There are no Linux/macOS shell examples (e.g., Bash), and the instructions for setting environment variables and using jq are Windows-specific. Linux users must adapt the examples themselves, which may cause confusion or friction.
Recommendations
  • Add Bash/Linux/macOS examples for all Curl commands, using export for environment variables and standard jq invocation (e.g., jq .id).
  • Present Linux/macOS examples before or alongside Windows examples to avoid Windows-first bias.
  • Clarify differences in command syntax and file paths between Windows and Linux/macOS environments.
  • Include notes or sections specifically for Linux/macOS users, especially regarding prerequisites and tool installation.
  • Mention alternative scripting environments (e.g., Bash, zsh) in the prerequisites.
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-11 06:20
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 Windows-centric examples (PowerShell and C#) for converting a certificate to base-64, with no mention of Linux/macOS tools or commands. This creates friction for non-Windows users who must find their own solutions.
Recommendations
  • Add Linux/macOS command-line examples, such as using 'base64' with OpenSSL:
  • openssl pkcs12 -in path-to-servicePrincipalCertificatePfxFile -nodes | base64
  • Or, for direct base64 encoding:
  • base64 path-to-servicePrincipalCertificatePfxFile
  • Explicitly mention that these commands work on Linux/macOS and provide step-by-step instructions.
  • Consider including a cross-platform scripting example (e.g., Python) for broader accessibility.
GitHub Create Pull Request
Hdinsight Python UDF with Apache Hive and Apache Pig - Azure HDInsight ...main/articles/hdinsight/hadoop/python-udf-hdinsight.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both shell (Linux/macOS) and PowerShell (Windows) examples for uploading files and running jobs, but PowerShell examples are more detailed, frequent, and sometimes presented first. Troubleshooting sections and some workflow recommendations focus on Windows-specific issues (e.g., CRLF line endings, PowerShell scripts for line ending conversion). There is a notable emphasis on PowerShell tooling and workflows, with Linux/macOS alternatives present but less elaborated.
Recommendations
  • Ensure Linux/macOS shell examples are as detailed and complete as PowerShell examples, including troubleshooting steps.
  • Present shell (Linux/macOS) and PowerShell examples side-by-side, or alternate which is shown first, to avoid implicit prioritization.
  • Add troubleshooting steps for common Linux/macOS issues (e.g., permissions, file transfer errors) alongside Windows-specific ones.
  • Clarify which steps are platform-agnostic and which are platform-specific, and provide parity in guidance for both.
  • Where PowerShell is used for tasks like file upload or job submission, provide equivalent Bash scripts or CLI commands.
GitHub Create Pull Request
← Previous Page 4 of 8 Next →