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 26-50 of 200 flagged pages
Hdinsight Overview of enterprise security in Azure HDInsight ...hdinsight/domain-joined/hdinsight-security-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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 references Windows-centric technologies such as Active Directory and Microsoft Entra Domain Services as the primary authentication mechanism, and mentions PowerShell as a client tool for cluster interaction. There are no explicit Linux/macOS authentication or management tool examples, nor are alternative directory services or Linux-native patterns discussed. The documentation assumes familiarity with Windows enterprise paradigms and omits Linux/macOS-specific guidance for tasks like authentication, cluster access, and auditing.
Recommendations
  • Include examples of authenticating and managing HDInsight clusters using Linux/macOS tools (e.g., SSH, curl, Linux CLI).
  • Mention alternative directory services or clarify if only Active Directory is supported.
  • Provide parity in client tool examples: show how to interact with clusters using Linux shell commands, not just PowerShell.
  • Clarify whether features like RBAC and auditing are accessible via Linux-native tools and document those workflows.
  • Explicitly state platform requirements and limitations for security features (e.g., if ESP requires Windows-based infrastructure).
GitHub Create Pull Request
Hdinsight LDAP sync in Ranger and Apache Ambari in Azure HDInsight ...lob/main/articles/hdinsight/domain-joined/ldap-sync.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (e.g., ldp.exe, net ads) for testing LDAP filters, and by focusing on Microsoft Entra ID and Domain Services (Windows-centric identity solutions). There are no Linux/macOS equivalents or examples for LDAP filter testing, and Windows tools are mentioned first and exclusively in relevant sections.
Recommendations
  • Include Linux/macOS alternatives for LDAP filter testing, such as ldapsearch (OpenLDAP) or other CLI tools.
  • Provide example commands for both Windows (ldp.exe, net ads) and Linux (ldapsearch) when discussing LDAP filter validation.
  • Clarify which steps are platform-agnostic and which require platform-specific tools, offering guidance for both environments.
  • Mention Samba/Winbind configuration specifics for Linux clusters, if applicable.
  • Ensure parity in troubleshooting and log access instructions for Linux/macOS users.
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-12 00:00
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, with explicit instructions and paths for Windows (e.g., REM, set, C:\HDI\jq-win64.exe). It notes that 'slight variations will be needed for other environments' but does not provide any Linux/macOS equivalents. This creates friction for non-Windows users, who must adapt the commands themselves. All other steps (Jupyter, Scala, bash) are cross-platform, but the initial cluster info retrieval is Windows-centric.
Recommendations
  • Provide equivalent Linux/macOS shell commands for host information retrieval, including example jq and curl usage with typical Linux paths.
  • List both Windows and Linux/macOS examples side-by-side or clearly indicate how to adapt the commands for non-Windows environments.
  • Avoid using Windows-specific syntax (e.g., REM, set) without alternatives.
  • Reference generic jq installation paths or provide installation instructions for Linux/macOS.
GitHub Create Pull Request
Hdinsight Apache Ambari heartbeat issues in Azure HDInsight .../hadoop/apache-ambari-troubleshoot-heartbeat-issues.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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. The only explicit command for disabling Azure Monitor logging uses a PowerShell cmdlet, with no Linux or Bash equivalent provided. The reference to PowerShell is prominent and not accompanied by cross-platform alternatives. While most troubleshooting steps use Linux-style commands (ps, top, service), the monitoring section is Windows-centric, and Windows tools are mentioned before any Linux options.
Recommendations
  • Provide equivalent Bash or Azure CLI commands for disabling Azure Monitor logging, such as using 'az hdinsight monitor disable'.
  • Clarify whether the PowerShell cmdlet can be run on Linux/macOS (via PowerShell Core), or offer platform-specific instructions.
  • Add notes or examples for Linux/macOS users wherever PowerShell is referenced.
  • Ensure that cross-platform alternatives are presented side-by-side, or Linux examples are given equal prominence.
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-12 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 demonstrates a notable Windows bias by prioritizing Visual Studio (Windows-centric) for building C# applications, referencing Data Lake Tools for Visual Studio for uploading files, and providing a dedicated PowerShell section for job submission. Linux/macOS alternatives for building, uploading, and running jobs are not described, and Windows tools are mentioned before any Linux equivalents. While SSH and bash commands are included for running jobs, the overall workflow assumes a Windows development environment.
Recommendations
  • Add instructions for building C# applications on Linux/macOS using Mono and the dotnet CLI.
  • Provide examples for uploading files to HDInsight storage using cross-platform tools such as Azure CLI, azcopy, or Hadoop fs commands.
  • Include a section for submitting MapReduce jobs using Azure CLI or REST API, which are platform-agnostic.
  • Mention alternative IDEs (e.g., VS Code) and workflows for non-Windows users.
  • Reorder examples so that platform-neutral or Linux/macOS options are presented alongside or before Windows-specific tools.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page shows moderate Windows bias, especially in the 'Ingest file storage and result storage' section. Data ingestion into Azure Storage is described as typically performed via PowerShell, the Azure Storage SDK, or AzCopy, all of which are Windows-centric tools (with PowerShell and AzCopy being most commonly used on Windows). Linux alternatives (such as Bash, CLI, or Hadoop-native tools) are not mentioned in this context, and Windows tools are listed first. However, for Data Lake Storage, more cross-platform options (DistCp, Sqoop, SDKs) are mentioned, and the rest of the document is generally platform-neutral.
Recommendations
  • Explicitly mention and provide examples for Linux/macOS users, such as using Azure CLI, Bash scripts, or Hadoop-native tools (e.g., hdfs dfs, DistCp) for data ingestion.
  • When listing ingestion tools, avoid listing Windows-centric tools first; present cross-platform options together or in parallel.
  • Add code snippets or links to Linux/macOS-specific ingestion workflows.
  • Clarify which tools are cross-platform (e.g., AzCopy is available for Linux/macOS) and provide installation/use instructions for those platforms.
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-12 00:00
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 towards Windows development environments, specifically Visual Studio, for building C# UDFs. All project creation, build, and upload steps are described using Visual Studio and its Azure integration, with no mention of Linux-native alternatives (e.g., MonoDevelop, command-line builds with msbuild, or file upload via SCP/Azure CLI). The only Linux-specific content is in the cluster environment and the SSH/Pig job section, but the development workflow is Windows-centric.
Recommendations
  • Add instructions for building C# projects using Mono and msbuild on Linux/macOS.
  • Include examples of using cross-platform editors (e.g., VS Code, MonoDevelop) and command-line build steps.
  • Provide alternative file upload methods (e.g., SCP, Azure CLI, azcopy) for users not using Visual Studio.
  • Reorder or parallelize instructions so Linux/macOS development workflows are presented alongside Windows/Visual Studio steps.
  • Clarify that Visual Studio is optional and highlight cross-platform development options.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits moderate Windows bias, primarily in the 'Customize HDInsight configs using Bootstrap' section, which provides only a PowerShell example using the AZ module for cluster configuration. There is no equivalent example for Linux/macOS users (e.g., Bash/CLI/ARM template), and the PowerShell approach is presented as the default. Additionally, references to Azure tools and modules are Windows-centric, and Windows-based configuration patterns are mentioned before Linux alternatives.
Recommendations
  • Provide equivalent Linux/macOS examples for cluster configuration, such as using Azure CLI, Bash scripts, or ARM templates.
  • Include explicit instructions or code samples for customizing HDInsight configs from Linux/macOS environments.
  • Balance the order of examples so that Linux and Windows approaches are presented together or Linux-first when appropriate.
  • Clarify that PowerShell is not required and mention cross-platform alternatives where possible.
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-12 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 demonstrates a notable Windows bias: command examples use Windows-specific syntax (cmd 'set', caret line continuation, Windows paths for jq), and PowerShell is presented as the only scripting alternative. There are no Linux/macOS shell examples for setting environment variables, line continuation, or using jq, which may confuse non-Windows users. The instructions and examples assume a Windows environment by default, with only brief notes to 'revise as needed for your environment' but no concrete Linux/macOS guidance.
Recommendations
  • Provide explicit Linux/macOS shell examples for setting environment variables (e.g., 'export'), line continuation (backslash), and jq usage (e.g., 'jq .id').
  • Include Linux/macOS command blocks alongside Windows/cmd and PowerShell examples.
  • Avoid hardcoding Windows paths (e.g., 'C:\HDI\jq-win64.exe') in generic curl/jq examples; use platform-neutral or platform-specific alternatives.
  • Clarify which commands are platform-specific and offer alternatives for each major OS.
  • Consider presenting Linux/macOS examples first or side-by-side with Windows examples to improve parity.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Windows command prompt examples, using Windows environment variable syntax (set, %VAR%), and referencing a Windows-specific jq executable path. There are no Linux/macOS shell examples, nor is there guidance for adapting the commands to non-Windows environments. Windows tools and patterns are presented exclusively and first, with no mention of Linux equivalents.
Recommendations
  • Provide Linux/macOS shell examples using Bash syntax (export VAR=value, $VAR).
  • Show how to use jq on Linux/macOS (e.g., jq .status.state) without a Windows path.
  • Add notes or sections explicitly describing differences and adaptations for Linux/macOS users.
  • Present both Windows and Linux/macOS examples side-by-side, or default to cross-platform syntax where possible.
  • Mention Linux-compatible SQL clients (e.g., Azure Data Studio, sqlcmd) alongside Windows tools.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only PowerShell and C# examples for converting a certificate to base-64, both of which are Windows-centric. There are no Linux/macOS shell (e.g., Bash, OpenSSL, base64) examples, nor any mention of equivalent Linux tools or commands. The instructions implicitly assume a Windows environment, creating friction for Linux/macOS users.
Recommendations
  • Add Linux/macOS command-line examples using tools like openssl and base64 (e.g., `openssl pkcs12 -in cert.pfx -out cert.pem -nodes; base64 cert.pfx > cert.pfx.b64`).
  • Explicitly mention cross-platform alternatives and clarify that the conversion can be done on any OS.
  • Consider including Python or other cross-platform code snippets.
  • Reorder examples or provide OS-specific sections to ensure parity.
GitHub Create Pull Request
Hdinsight What is Apache Hive and HiveQL - Azure HDInsight ...b/main/articles/hdinsight/hadoop/hdinsight-use-hive.md
Medium Priority View Details →
Scanned: 2026-01-12 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 lists Windows-specific tools (Visual Studio, PowerShell, SSIS) prominently, sometimes before or without Linux/macOS equivalents. Windows PowerShell is given as a method for batch Hive queries, but no Linux shell example is provided. SSIS integration is described in detail, but Linux-native scheduling options (e.g., cron, shell scripts) are not mentioned. While cross-platform tools (VS Code, Beeline, REST API, Hive View) are included, Windows-only tools and workflows are highlighted, and Linux/macOS alternatives are less visible or missing.
Recommendations
  • Add explicit Linux/macOS shell examples for running Hive queries (e.g., using Beeline from Bash).
  • Include Linux-native scheduling methods (e.g., cron jobs, shell scripts) alongside SSIS and Data Factory.
  • Present cross-platform tools (VS Code, Beeline, REST API) before Windows-only tools in tables and lists.
  • Clarify which features are Windows-only and suggest Linux/macOS alternatives where possible.
  • Expand documentation on integrating Hive with Linux/macOS workflow automation tools.
GitHub Create Pull Request
Hdinsight Run Apache Sqoop jobs with Azure HDInsight (Apache Hadoop) .../main/articles/hdinsight/hadoop/hdinsight-use-sqoop.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. It emphasizes using Azure PowerShell from a workstation to run Sqoop jobs, with the description and metadata highlighting PowerShell and Windows-centric tools. The walkthroughs and examples prioritize Windows tools (PowerShell, .NET SDK) and mention them before Linux alternatives. There is a lack of direct Linux command-line examples, and Linux/macOS methods are referenced but not detailed on this page. Limitations for Linux-based HDInsight are listed, but workarounds or parity solutions are not provided.
Recommendations
  • Provide explicit Linux/macOS command-line examples for running Sqoop jobs, such as SSH usage and bash scripts.
  • Reorder walkthroughs to present cross-platform or Linux-native methods first, or in parallel with Windows methods.
  • Include direct links and summaries for Linux/macOS walkthroughs within this page, not just in the table.
  • Clarify limitations for Linux users and suggest alternatives or mitigation strategies.
  • Balance the use of PowerShell with bash or other Linux-native tools in examples and descriptions.
GitHub Create Pull Request
Hdinsight Using Apache Hive as an ETL Tool - Azure HDInsight ...doop/apache-hadoop-using-apache-hive-as-an-etl-tool.md
Medium Priority View Details →
Scanned: 2026-01-12 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 demonstrates a moderate Windows bias. It references Windows-centric tools (SQL Server Integration Services, Excel, PowerShell) and patterns before mentioning Linux equivalents. Examples for automating Hive queries specifically mention PowerShell and Azure Logic Apps, with no mention of Bash, Linux shell scripting, or cross-platform alternatives. The workflow and data loading steps highlight Windows tools and integration paths (Excel, SSIS) first, while Linux/macOS approaches (e.g., Sqoop, Oozie) are mentioned later or only in passing. There are no explicit Linux shell or macOS automation examples.
Recommendations
  • Add Linux/macOS shell scripting examples for automating Hive queries (e.g., using Bash, cron, or Airflow).
  • Include references to Linux-native ETL tools and workflows (e.g., Apache NiFi, Airflow, Bash scripts) alongside Windows tools.
  • Present cross-platform alternatives for data loading and orchestration (e.g., Python scripts, REST APIs) before or alongside Windows-specific tools.
  • Ensure that examples and tool recommendations are balanced between Windows and Linux/macOS environments.
  • Explicitly mention how Linux/macOS users can accomplish the same tasks (e.g., using Sqoop, Oozie, Bash, or Python) where PowerShell or Windows tools are referenced.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides a detailed PowerShell script for certificate management, which is Windows-centric and lacks equivalent Linux/macOS instructions. No Bash, CLI, or cross-platform alternatives are offered for critical certificate creation and assignment tasks, creating friction for non-Windows users.
Recommendations
  • Provide Bash or Azure CLI examples for certificate creation, assignment, and cluster update steps.
  • Explicitly mention platform requirements for PowerShell and offer installation guidance for PowerShell Core on Linux/macOS if necessary.
  • Include links to official Azure CLI documentation for managing service principal credentials and certificates.
  • Reorder examples to present cross-platform or Linux/macOS solutions before or alongside Windows/PowerShell instructions.
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-12 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 provides both shell (Linux/macOS) and PowerShell (Windows) examples for uploading files and running jobs on HDInsight. However, PowerShell is given significant prominence, with extensive scripts and troubleshooting focused on Windows tooling. Some troubleshooting steps (such as line ending fixes) are PowerShell-only, and there is no mention of equivalent Linux/macOS commands (e.g., using dos2unix). In several sections, PowerShell examples appear after shell examples, but the troubleshooting and advanced usage are Windows-centric. There is also a reference to deploying Python modules to 'Windows Azure HDInsight' in the next steps, which may confuse Linux users.
Recommendations
  • Provide Linux/macOS equivalents for all PowerShell troubleshooting steps, such as using 'dos2unix' or 'sed' to fix line endings.
  • Include Bash or shell scripts for uploading files and running jobs via Azure CLI, not just PowerShell.
  • Clarify that HDInsight clusters are Linux-based and that most operations can be performed from Linux/macOS terminals.
  • Avoid references to 'Windows Azure HDInsight' in contexts where the cluster OS is Linux.
  • Balance the depth of PowerShell and shell examples, ensuring Linux/macOS users have equally detailed guidance.
GitHub Create Pull Request
Hdinsight Submit Apache Hadoop jobs in HDInsight ...t/hadoop/submit-apache-hadoop-jobs-programmatically.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation lists PowerShell as a primary method for submitting Hadoop jobs in HDInsight, alongside .NET SDK and curl. PowerShell is a Windows-centric tool, and its inclusion as a main workflow (with multiple dedicated resources) suggests a Windows bias. The .NET SDK is also more commonly used on Windows, though cross-platform support exists. Linux-native equivalents (e.g., Bash scripts, Azure CLI) are not mentioned, and PowerShell is listed before Linux-friendly alternatives like curl.
Recommendations
  • Add examples and resources for submitting Hadoop jobs using Bash or Azure CLI, which are more native to Linux/macOS environments.
  • Clarify cross-platform support for the .NET SDK, and provide explicit instructions for Linux/macOS users.
  • Ensure that Linux/macOS-friendly tools (curl, CLI) are listed before or alongside Windows tools like PowerShell.
  • Consider adding a section on platform compatibility for each tool.
GitHub Create Pull Request
Hdinsight InvalidNetworkConfigurationErrorCode error - Azure HDInsight ...idnetworkconfigurationerrorcode-cluster-creation-fails.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page is mostly platform-neutral and uses Linux-centric troubleshooting commands (ssh, nslookup, dig, resolv.conf). However, there is a notable Windows bias in the mention of PowerShell and Azure Runbooks as sources of configuration errors, and the resolution refers only to the Az PowerShell SDK for correcting parameters. Additionally, Windows VMs are mentioned as possible DNS servers before Linux alternatives in one section. The order of examples sometimes lists Windows before Linux, and the PowerShell tool is referenced without equivalent CLI or REST API alternatives.
Recommendations
  • Include Azure CLI and REST API equivalents for PowerShell-based troubleshooting and configuration steps.
  • When mentioning VM-based DNS servers, list Linux and Windows options equally, or mention Linux first given HDInsight's Linux focus.
  • Provide explicit Linux/macOS alternatives for any PowerShell or Windows-specific instructions.
  • Clarify that most cluster troubleshooting is performed on Linux VMs, and ensure all examples are shown for both platforms where relevant.
GitHub Create Pull Request
Hdinsight Create HBase clusters in a Virtual Network - Azure ...rticles/hdinsight/hbase/apache-hbase-provision-vnet.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias in the 'Create a virtual machine' section, where instructions and links are provided only for creating a Windows Server VM, with no mention of Linux VM creation. This prioritizes Windows tools and patterns, potentially creating friction for Linux/macOS users who may wish to use a Linux VM for cluster management or connectivity testing.
Recommendations
  • Include instructions and links for creating a Linux-based virtual machine in Azure, such as Ubuntu or CentOS, alongside the Windows VM instructions.
  • Present both Windows and Linux VM creation options equally, or list Linux first given the context of HDInsight clusters being Linux-based.
  • Provide example commands for connectivity verification (e.g., 'ping', 'curl') that work on both Windows and Linux, and clarify any OS-specific differences.
GitHub Create Pull Request
Hdinsight Use Apache Maven to build a Java HBase client for Azure HDInsight ...hdinsight/hbase/apache-hbase-build-java-maven-linux.md
Medium Priority View Details →
Scanned: 2026-01-12 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 is notably Windows-centric: all file and directory commands use Windows Command Prompt syntax, Notepad is the only editor referenced, and the test environment is explicitly Windows 10. PowerShell is given an entire dedicated section for job submission, while Linux/macOS equivalents (e.g., Bash, shell scripts) are not covered. There are no examples of Linux/macOS file operations, editors, or alternative workflows, and Windows tools/patterns are mentioned first and exclusively in most cases.
Recommendations
  • Provide parallel examples for Linux/macOS users, including shell commands (mkdir, rm, nano/vim/emacs for editing files) and directory paths.
  • Mention and demonstrate using cross-platform editors (e.g., VS Code, nano, vim) instead of only Notepad.
  • Clarify that Maven and Java commands are cross-platform, and show them in both Windows and Linux/macOS contexts.
  • Add a section for Linux/macOS users describing how to upload JARs and run jobs using Bash and Azure CLI, not just PowerShell.
  • Rephrase the test environment to be platform-neutral or provide both Windows and Linux/macOS setup instructions.
  • Where PowerShell modules are described, offer equivalent Azure CLI or REST API instructions for non-Windows users.
GitHub Create Pull Request
Hdinsight Manage Apache Hadoop clusters in HDInsight with .NET SDK - Azure ...icles/hdinsight/hdinsight-administer-use-dotnet-sdk.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. All package installation instructions use PowerShell, and the code samples reference the PowerShell client GUID for authentication. There are no Linux/macOS-specific instructions or examples for installing dependencies, running code, or authenticating. The only command-line example for HBase balancing uses Windows batch syntax and environment variables, with no Linux equivalent provided. The documentation assumes a Windows development environment throughout.
Recommendations
  • Add Linux/macOS instructions for installing NuGet packages (e.g., using dotnet CLI or Mono).
  • Provide guidance for running .NET SDK code on Linux/macOS, including prerequisites (e.g., .NET Core/Mono).
  • Include Linux shell equivalents for command-line examples (e.g., HBase balancing commands using bash syntax and $HBASE_HOME).
  • Clarify that the .NET SDK is cross-platform and provide any necessary platform-specific notes.
  • Avoid referencing Windows-specific tools (such as PowerShell) exclusively; show parity with bash/zsh where appropriate.
GitHub Create Pull Request
Hdinsight Install third-party applications on Azure HDInsight ...icles/hdinsight/hdinsight-apps-install-applications.md
Medium Priority View Details →
Scanned: 2026-01-12 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 exclusively referencing the Azure portal (a web GUI most commonly used on Windows), mentioning Azure PowerShell and Azure Classic CLI as deployment tools, and omitting Linux-native tools (such as Azure CLI or SSH-based workflows) in the main instructions. Examples and step-by-step guides are portal-centric, which is more familiar to Windows users. Linux-specific instructions, such as using Azure CLI or scripting, are only referenced in the 'Next steps' section and not integrated into the main workflow.
Recommendations
  • Include Azure CLI examples alongside or before Azure PowerShell/Classic CLI references.
  • Provide step-by-step instructions for installing applications using command-line tools on Linux/macOS (e.g., Azure CLI, SSH).
  • Explicitly mention Linux/macOS compatibility in the prerequisites and workflows.
  • Balance the order of tool references (e.g., mention Azure CLI before PowerShell when both are supported).
  • Add screenshots or terminal output examples for Linux/macOS environments.
GitHub Create Pull Request
Hdinsight Authorize users for Ambari Views - Azure HDInsight ...icles/hdinsight/hdinsight-authorize-users-to-ambari.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides three methods for adding users: via the portal, PowerShell, and curl/bash. The PowerShell example is given in full detail before the curl/bash example, and the PowerShell script is significantly more elaborate, suggesting a Windows-centric workflow. PowerShell is a Windows-specific tool, and its prominence (including credential handling and scripting) indicates a bias toward Windows users. The curl/bash example is provided, but with a note that 'slight modifications would be needed for a Windows command prompt,' further centering Windows as the default. No Linux-specific tools (e.g., Python, shell scripts, or Linux command-line utilities) are mentioned, and the ordering places Windows methods first.
Recommendations
  • Provide Linux/macOS shell script examples before or alongside PowerShell, not after.
  • Offer parity in detail and explanation for both PowerShell and bash/curl methods.
  • Explicitly mention Linux/macOS compatibility and provide troubleshooting notes for those platforms.
  • Include examples using other cross-platform tools (e.g., Python requests, generic REST clients) to broaden accessibility.
  • Avoid language that assumes Windows as the default (e.g., 'slight modifications needed for Windows command prompt').
GitHub Create Pull Request
Hdinsight Apache Hive libraries during cluster creation - Azure HDInsight ...icles/hdinsight/hdinsight-hadoop-add-hive-libraries.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page shows a moderate Windows bias. The primary script example is a PowerShell (.ps1) script, with the Bash/Linux script URI mentioned only in the cluster creation section. Windows tools like Azure Storage Explorer are referenced for uploading files, and Windows/PowerShell methods (Azure PowerShell, .NET SDK) are mentioned before Linux equivalents. The page does reference Linux clusters and Bash scripts, but Windows-centric patterns and tools are prominent.
Recommendations
  • Present Bash/Linux script examples and URIs alongside PowerShell examples in the 'The script' section, not just in cluster creation.
  • Mention Linux CLI tools (e.g., azcopy, Azure CLI, or native Linux file upload methods) for uploading files to Azure Blob Storage.
  • List Linux-based methods (e.g., Azure CLI, REST API) for cluster creation before or alongside Windows/PowerShell/.NET SDK options.
  • Clarify which instructions apply to Windows vs. Linux clusters, and provide parity in examples for both platforms.
GitHub Create Pull Request
Hdinsight Tutorial: On-demand clusters in Azure HDInsight with Data Factory ...dinsight/hdinsight-hadoop-create-linux-clusters-adf.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The tutorial relies exclusively on Azure PowerShell scripts for critical setup steps, such as creating resource groups and storage accounts, without providing equivalent Bash/CLI instructions for Linux/macOS users. The prerequisites and workflow assume PowerShell is installed, and all code samples are PowerShell-only. There is no mention of Azure CLI or Bash alternatives, and the PowerShell approach is presented first and exclusively.
Recommendations
  • Provide Azure CLI (az) or Bash script equivalents for all PowerShell commands, especially for resource creation and file copy steps.
  • Update prerequisites to include both PowerShell and Azure CLI options, with links to installation guides for each.
  • Clearly indicate which steps can be performed via the Azure portal, CLI, or PowerShell, and offer parity in instructions.
  • Add notes or callouts for Linux/macOS users, highlighting any differences in command syntax or required tools.
  • Consider reordering examples so that CLI/Bash and PowerShell are presented side-by-side, or at least alternate which is shown first.
GitHub Create Pull Request
← Previous Page 2 of 8 Next →