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 51-75 of 867 flagged pages
Hdinsight Use Curl to export data with Apache Sqoop in Azure HDInsight ...icles/hdinsight/hadoop/apache-hadoop-use-sqoop-curl.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a clear Windows bias: all command-line examples use Windows batch syntax (set VAR=), Windows environment variable notation (%VAR%), and Windows paths for jq (C:\HDI\jq-win64.exe). There are no Linux or macOS shell examples (e.g., export VAR=, $VAR, ./jq), nor are Linux-specific instructions or parity notes provided. The prerequisites and instructions assume a Windows environment, with only a brief mention to 'revise as needed for your environment.'
Recommendations
  • Provide equivalent Linux/macOS shell examples using bash syntax (export VAR=, $VAR, ./jq).
  • Include notes or sections explicitly addressing Linux/macOS usage, such as how to install and invoke jq and curl.
  • Present both Windows and Linux/macOS commands side-by-side or in tabs to ensure parity.
  • Avoid assuming Windows as the default environment; clarify instructions for multiple platforms.
  • Reference cross-platform SQL clients, not just Windows-centric tools like SQL Server Management Studio.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates Windows bias by prioritizing Windows-centric tools and workflows, such as SQL Server Integration Services (SSIS), Excel, PowerShell, and C# examples, while omitting equivalent Linux tools and examples. Linux-native ETL orchestration tools (e.g., cron, shell scripts) and desktop alternatives (e.g., LibreOffice, Python) are not mentioned, and the order of presentation favors Windows technologies over cross-platform or Linux-first solutions.
Recommendations
  • Include Linux-native ETL orchestration examples, such as using cron jobs or shell scripts to automate Hive queries.
  • Provide examples of loading data into open-source relational databases (e.g., PostgreSQL, MySQL) using Sqoop or other tools.
  • Mention and demonstrate Linux desktop alternatives to Excel, such as LibreOffice Calc, or using Python/pandas for data analysis.
  • Add cross-platform code samples (e.g., Python, Bash) for interacting with Hive, in addition to C# and PowerShell.
  • Present cross-platform and Linux tools (e.g., Oozie, Airflow) before or alongside Windows tools like SSIS and PowerShell.
  • Clarify which steps and tools are platform-agnostic and which are Windows-specific, to help users on Linux systems.
GitHub Create Pull Request
Hdinsight Unable to access Data Lake storage files in Azure HDInsight ...sight/hadoop/hdinsight-troubleshoot-data-lake-files.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell scripts for certificate management and cluster updates, referencing Windows-centric tools and patterns (e.g., New-SelfSignedCertificate, .pfx files, PowerShell cmdlets). There are no equivalent Linux/bash examples for certificate creation, management, or cluster interaction, and the Windows/PowerShell approach is presented as the default method. This may hinder users working in Linux environments or with bash scripting.
Recommendations
  • Provide equivalent bash or Linux command-line examples for certificate creation and management (e.g., using openssl for .pfx generation).
  • Include Azure CLI commands for cluster updates and service principal credential management, as Azure CLI is cross-platform.
  • Explicitly mention Linux-compatible workflows and tools alongside PowerShell examples.
  • Reorder examples or provide parallel instructions so that Linux and Windows approaches are presented with equal prominence.
  • Clarify any OS-specific requirements or limitations for each method.
GitHub Create Pull Request
Hdinsight Use MapReduce and Curl with Apache Hadoop in HDInsight - Azure ...s/hdinsight/hadoop/apache-hadoop-use-mapreduce-curl.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments. Examples for setting environment variables and using curl are shown using Windows command syntax (cmd.exe 'set' commands, Windows-style variable expansion), and jq is referenced with a Windows path. PowerShell is given a dedicated section with full examples, while there are no Linux shell (bash) equivalents for setting variables, running curl, or using jq. The prerequisites mention Windows PowerShell before curl/jq, and the curl examples are tailored to Windows usage. There are no bash or Linux-native command examples, nor guidance for Linux users on adapting the commands.
Recommendations
  • Add Linux/bash examples for setting environment variables (e.g., 'export CLUSTERNAME=...'), running curl, and using jq (e.g., 'jq .id').
  • Present both Windows and Linux command examples side-by-side, or clearly label which environment each example is for.
  • Reference Linux-native tools and patterns (e.g., bash, sh, Linux paths) alongside Windows tools.
  • In the prerequisites, mention Linux shell usage before or alongside Windows PowerShell.
  • Ensure all command examples are provided for both platforms, with notes on differences in syntax and tool usage.
GitHub Create Pull Request
Hdinsight Apache Hadoop & Visual Studio Data Lake Tools - Azure HDInsight ...adoop/apache-hadoop-visual-studio-tools-get-started.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily focused on using Data Lake Tools for Visual Studio, a Windows-only IDE, to interact with Azure HDInsight and Apache Hadoop clusters. All examples, instructions, and screenshots are based on Visual Studio workflows, with no mention of equivalent Linux tools, command-line alternatives, or cross-platform solutions. Windows-centric tools and patterns are presented exclusively and without Linux parity.
Recommendations
  • Include instructions and examples for connecting to HDInsight clusters and running Hive queries using cross-platform tools such as VS Code, IntelliJ IDEA, Eclipse, or command-line interfaces (e.g., SSH, Beeline, Hive CLI).
  • Provide Linux-specific guidance for cluster management, job submission, and resource exploration, such as using Azure CLI, Hadoop command-line tools, or web-based interfaces.
  • Add references and links to documentation for Linux users, including tutorials for using HDInsight from Linux environments.
  • Where possible, offer side-by-side examples for both Windows (Visual Studio) and Linux (CLI or other IDEs) to ensure parity and inclusivity.
  • Clarify in the prerequisites and introduction that the described workflow is Windows-specific, and direct Linux/macOS users to alternative supported workflows.
GitHub Create Pull Request
Hdinsight Converting certificate contents to base-64 - Azure HDInsight ...-troubleshoot-converting-service-principal-certificate.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows 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 Bash or OpenSSL), and Windows-centric tools and patterns are mentioned exclusively.
Recommendations
  • Add equivalent Linux command-line examples, such as using 'base64' and 'openssl' to convert pfx files.
  • Include Bash shell snippets for certificate conversion.
  • Mention cross-platform tools and approaches before or alongside Windows-specific methods.
  • Clarify that the process can be performed on both Windows and Linux, and provide guidance for both environments.
GitHub Create Pull Request
Hdinsight Submit Apache Hadoop jobs in HDInsight ...t/hadoop/submit-apache-hadoop-jobs-programmatically.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page presents three main methods for submitting Hadoop jobs: .NET SDK, curl, and PowerShell. The inclusion of .NET SDK and PowerShell as primary options reflects a Windows-centric approach, as both are traditionally Windows-first technologies. PowerShell is a Windows-native tool, and the .NET SDK is closely associated with Windows development environments. There are no explicit Linux shell or Bash examples, nor are Linux-native tools (such as Bash scripts or Linux CLI utilities) mentioned. The ordering (.NET SDK, curl, PowerShell) also places Windows-oriented tools before more cross-platform options.
Recommendations
  • Add examples using Bash scripts or Linux shell commands for submitting Hadoop jobs.
  • Include references to Linux-native tools (e.g., using wget, or direct REST API calls via Bash).
  • Reorder the methods to present cross-platform options (like curl) before Windows-specific ones.
  • Explicitly state platform compatibility for each method, clarifying which are available on Linux and which are Windows-specific.
  • Provide parity in documentation links and examples for both Linux and Windows users.
GitHub Create Pull Request
Hdinsight MapReduce with Apache Hadoop on HDInsight ...n/articles/hdinsight/hadoop/hdinsight-use-mapreduce.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page shows evidence of Windows bias by listing Windows PowerShell as a distinct method for submitting MapReduce jobs, while Linux/Unix/macOS options are grouped under SSH and Curl. Windows PowerShell is mentioned as a dedicated tool, and the table lists Windows PowerShell as a primary method for Windows users, without mentioning Linux-specific tools (e.g., Bash scripts, Linux command line patterns) or giving parity to Linux-native approaches. The documentation does not provide Linux-specific examples or highlight Linux tools with the same prominence as Windows PowerShell.
Recommendations
  • Add explicit Linux command-line examples for submitting MapReduce jobs, such as using Bash scripts or the Hadoop CLI.
  • Provide parity in tooling by mentioning Linux-native tools (e.g., Bash, shell scripts, Linux CLI utilities) alongside Windows PowerShell.
  • Reorder or balance the table so that Linux/Unix/macOS methods are not grouped generically, but listed with the same specificity as Windows PowerShell.
  • Include walkthroughs or links for Linux-specific job submission methods, not just SSH and Curl.
  • Avoid presenting Windows tools (PowerShell) as the primary or exclusive method for job submission; ensure equal visibility for Linux approaches.
GitHub Create Pull Request
Hdinsight Python UDF with Apache Hive and Apache Pig - Azure HDInsight ...main/articles/hdinsight/hadoop/python-udf-hdinsight.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides both shell (Linux/Unix) and PowerShell (Windows) examples for uploading files and running Hive/Pig jobs. However, there is a strong emphasis on PowerShell throughout, with extensive PowerShell scripts and troubleshooting steps tailored to Windows users. Windows-specific issues (like CRLF line endings) are discussed in detail, and Windows tools (PowerShell, Azure Cloud Shell) are mentioned frequently. In some sections, PowerShell examples are more detailed or appear before shell examples. There is limited coverage of Linux-specific workflows, and troubleshooting for Linux users is minimal.
Recommendations
  • Provide parity in troubleshooting steps for Linux users, such as how to fix line ending issues using Linux tools (e.g., dos2unix, sed).
  • Include more detailed Linux shell examples for uploading files and running jobs, matching the depth of PowerShell scripts.
  • Ensure that Linux/Unix workflows are presented first or equally alongside Windows/PowerShell workflows.
  • Mention Linux tools and editors (e.g., nano, vim, dos2unix) when discussing file editing and preparation.
  • Clarify which steps are platform-agnostic and which are platform-specific, and provide alternatives for both environments.
  • Add troubleshooting tips for common Linux issues (e.g., file permissions, SSH key problems) relevant to HDInsight usage.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a clear Windows bias: Windows tools (cmd, Notepad, PowerShell) are used exclusively or presented first throughout, with commands and file paths in Windows format. The test environment is explicitly Windows 10, and instructions for Linux or macOS users are absent or minimal. PowerShell is given a dedicated section with extensive scripts, while Linux equivalents (such as Bash scripts or CLI tools) are not provided. There are no examples of using Linux-native editors, file paths, or shell commands for project setup, file editing, or job submission, despite HDInsight clusters being Linux-based.
Recommendations
  • Add parallel Linux/macOS instructions for all steps, including using Bash shell commands, Linux file paths, and editors (e.g., nano, vim).
  • Provide examples for creating, editing, and deleting files using Linux tools.
  • Include instructions for running Maven and SCP commands in a Linux/macOS terminal.
  • Offer Bash or Azure CLI equivalents for PowerShell scripts, including uploading files and submitting jobs.
  • Clearly indicate cross-platform differences and suggest alternatives for non-Windows users.
  • Avoid assuming Windows as the default environment; present both Windows and Linux/macOS options side-by-side.
GitHub Create Pull Request
Hdinsight InvalidNetworkConfigurationErrorCode error - Azure HDInsight ...idnetworkconfigurationerrorcode-cluster-creation-fails.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. While most troubleshooting steps use Linux/SSH commands (hostname, nslookup, dig, resolv.conf), there are references to Windows tools and patterns, such as PowerShell cmdlets (Get-AzVirtualNetwork), Azure Runbooks, and the option to deploy a Windows VM as a DNS forwarder. The PowerShell/Windows-specific troubleshooting is mentioned without equivalent Linux CLI or Azure CLI examples, and the PowerShell SDK documentation is referenced directly. In some cases, Windows is mentioned before Linux as a VM option. There are no explicit Linux alternatives for the PowerShell/Runbook steps, and the documentation does not provide Azure CLI or REST API equivalents for network troubleshooting.
Recommendations
  • Provide equivalent Azure CLI or REST API commands for network troubleshooting and configuration, alongside PowerShell examples.
  • When mentioning VM deployment for DNS forwarding, list Linux and Windows options equally, or mention Linux first if the majority of HDInsight clusters are Linux-based.
  • For steps involving PowerShell or Azure Runbooks, add Linux shell script or Azure CLI alternatives.
  • Reference both Linux and Windows documentation for VM configuration and DNS forwarding, not just PowerShell SDK.
  • Ensure that examples and instructions are platform-neutral or provide parallel instructions for both Windows and Linux users.
GitHub Create Pull Request
Hdinsight Tutorial - Use Apache HBase in Azure HDInsight ...sight/hbase/apache-hbase-tutorial-get-started-linux.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates some Windows bias, particularly in the prerequisites and example sections. Windows tools and patterns (such as Bash on Windows 10, Windows Subsystem for Linux, Windows Command Prompt, and PowerShell's Invoke-RestMethod) are mentioned before or instead of native Linux equivalents. There is an emphasis on using Bash via WSL on Windows, and PowerShell is referenced as an alternative for REST API calls, but there are no direct Linux-specific command-line examples or instructions for native Linux environments. The documentation lacks explicit Linux command-line examples for REST API usage and does not mention Linux package managers or native Linux shell environments beyond SSH.
Recommendations
  • Provide Linux-first instructions and examples, such as using native Bash shells on Ubuntu or CentOS, before mentioning Windows alternatives.
  • Include explicit Linux command-line examples for REST API usage, such as using curl from a native Linux terminal.
  • Mention Linux package managers and installation steps for required tools (e.g., curl, ssh) on popular distributions.
  • Avoid referencing Windows tools (such as PowerShell's Invoke-RestMethod or Windows Command Prompt) unless providing parity with Linux equivalents.
  • Clarify that all commands work natively on Linux and provide troubleshooting tips for common Linux environments.
  • Reorder sections so that Linux-native instructions appear before Windows-specific guidance.
GitHub Create Pull Request
Hdinsight REST API to query Apache HBase in Azure HDInsight ...main/articles/hdinsight/hbase/troubleshoot-rest-api.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page references IIS Gateway, a Windows-specific technology, as the cause of the REST API limitation. It does not mention Linux equivalents (such as Apache or Nginx gateways) or provide troubleshooting steps/examples for Linux-based HDInsight clusters. The mitigation steps and troubleshooting focus on Windows-centric infrastructure without acknowledging Linux scenarios or tools.
Recommendations
  • Explicitly mention whether the issue applies to both Windows and Linux HDInsight clusters, or clarify if it is Windows-only.
  • If Linux clusters are affected differently, provide Linux-specific troubleshooting steps and examples.
  • Reference Linux gateway technologies (e.g., Apache, Nginx) and discuss their behavior in similar scenarios.
  • Provide parity in examples and explanations for both Windows and Linux environments to ensure cross-platform relevance.
GitHub Create Pull Request
Hdinsight Non-interactive authentication .NET application - Azure HDInsight ...ate-non-interactive-authentication-dotnet-applications.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias towards Windows environments. It exclusively provides examples for .NET (C#) applications, which are most commonly developed and run on Windows. Package installation instructions use NuGet and the Install-Package command, which is typically executed in Windows PowerShell. There are no examples or guidance for Linux users, such as using .NET Core cross-platform tools, running the application on Linux, or alternative package managers. The prerequisites and instructions assume use of the Azure portal and PowerShell, with no mention of CLI or Linux-specific workflows.
Recommendations
  • Add examples for developing and running .NET applications on Linux, including using the .NET CLI (dotnet) for project creation and package management.
  • Provide instructions for installing required packages using the dotnet CLI (e.g., 'dotnet add package') instead of only NuGet/Install-Package.
  • Include guidance for authenticating and managing Azure resources using the Azure CLI, which is cross-platform, alongside PowerShell examples.
  • Clarify that .NET Core and .NET 5+ applications can run on Linux and macOS, and provide sample commands for these platforms.
  • Mention any platform-specific considerations for running HDInsight client applications on Linux, such as dependencies or environment setup.
  • Ensure that all code and instructions are validated to work on both Windows and Linux environments.
GitHub Create Pull Request
Hdinsight Manage Apache Hadoop clusters in HDInsight with .NET SDK - Azure ...icles/hdinsight/hdinsight-administer-use-dotnet-sdk.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively providing PowerShell commands for package installation, referencing the PowerShell client GUID for authentication, and using Windows-style command prompts in HBase examples. There are no Linux or cross-platform equivalents for these steps, and Windows tools/patterns are mentioned first or exclusively throughout the page.
Recommendations
  • Provide Linux and macOS equivalents for package installation, such as dotnet CLI commands (e.g., 'dotnet add package ...') and instructions for Mono or .NET Core on non-Windows platforms.
  • Replace or supplement PowerShell-specific references (such as the PowerShell client GUID) with cross-platform alternatives or clarify their applicability.
  • Include Linux shell examples for cluster management tasks, especially for HBase and other command-line operations.
  • Clearly indicate which steps are platform-specific and offer guidance for users on Linux or macOS.
  • Add notes or sections on how to run .NET SDK code on Linux/macOS, including prerequisites and environment setup.
GitHub Create Pull Request
Hdinsight Azure HDInsight configuration settings reference ...main/articles/hdinsight/hdinsight-config-for-vscode.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Azure HDInsight configuration settings shows evidence of Windows bias. Several configuration properties reference Windows-specific paths and tools (e.g., 7z.exe, winutils.exe, JAVA_HOME, SCALA_HOME, SPARK_HOME) with Windows-style paths (C:\, D:\), and the mention of 'windows OS only' for winutils.exe. There are no equivalent Linux examples, paths, or instructions, and the Windows tools are mentioned first and exclusively.
Recommendations
  • Add equivalent Linux configuration examples for properties such as 7z, JAVA_HOME, SCALA_HOME, SPARK_HOME, using Linux-style paths (e.g., /usr/bin/7z, /usr/lib/jvm/java-8-openjdk-amd64/).
  • Clarify which settings are OS-specific and provide guidance for both Windows and Linux users.
  • Include notes or tables showing both Windows and Linux default paths and installation instructions for required tools.
  • Avoid mentioning Windows tools exclusively; ensure Linux alternatives are referenced where applicable.
  • Where a tool is Windows-only (e.g., winutils.exe), explain its purpose and provide Linux equivalents or note that it is not required on Linux.
GitHub Create Pull Request
Hdinsight Apache Hive libraries during cluster creation - Azure HDInsight ...icles/hdinsight/hdinsight-hadoop-add-hive-libraries.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits Windows bias by primarily referencing PowerShell scripts (.ps1) and providing their location before the Bash/Linux equivalent. The script action example and URI for Windows/PowerShell is listed first, and the overall guidance assumes familiarity with Windows tools such as Azure Storage Explorer. There is minimal explanation or parity for Linux command-line alternatives, and the Bash script is mentioned after the PowerShell script.
Recommendations
  • Present Bash/Linux examples and script URIs before or alongside PowerShell examples to avoid implying Windows is the default.
  • Include instructions for using Linux-native tools (e.g., azcopy, Azure CLI, or standard shell commands) to upload jars to Azure Blob Storage, not just Azure Storage Explorer.
  • Clarify which script should be used for which OS, and provide equal detail for both Windows and Linux workflows.
  • Add explicit Linux command-line examples for all steps, including storage account creation and file upload.
  • Avoid assuming the user is operating from a Windows environment; mention cross-platform alternatives wherever possible.
GitHub Create Pull Request
Hdinsight Apache Hadoop & secure transfer storage - Azure HDInsight ...oop-create-linux-clusters-with-secure-transfer-storage.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented as a primary method for managing storage accounts, with explicit mention and example before Azure CLI. The use of PowerShell cmdlets and terminology (e.g., 'New-AzStorageAccount') reflects a Windows-centric approach. While Azure CLI is included, there are no Linux shell or scripting examples (such as Bash), nor is there mention of Linux-native tools or workflows. The troubleshooting and configuration steps reference Ambari (which is cross-platform), but do not provide OS-specific guidance or parity for Linux users.
Recommendations
  • Include Bash shell examples for storage account creation and updates using Azure CLI, demonstrating usage on Linux systems.
  • Present Azure CLI examples before PowerShell, or side-by-side, to avoid Windows-first ordering.
  • Mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Add notes or links for Linux users on installing and using Azure CLI.
  • Avoid exclusive use of Windows tools (like PowerShell) in examples; provide equivalent Linux commands or workflows.
  • Clarify that Ambari steps apply equally to Linux clusters, and provide any OS-specific caveats if relevant.
GitHub Create Pull Request
Hdinsight Customize Azure HDInsight cluster configurations using bootstrap ...nsight/hdinsight-hadoop-customize-cluster-bootstrap.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias by exclusively providing PowerShell examples for customizing HDInsight clusters, referencing Windows-centric tools (.NET SDK, PowerShell), and omitting equivalent Linux shell (bash/CLI) examples. The order of presentation prioritizes Windows tools and workflows, with Linux-specific customization only mentioned as a link in the 'See also' section. There are no bash, Azure CLI, or Linux-native script samples for the main workflow described.
Recommendations
  • Add equivalent Azure CLI and bash script examples for cluster customization, showing how to achieve the same configuration changes from Linux environments.
  • Present Linux and Windows approaches in parallel, or alternate their order to avoid implicit prioritization.
  • Reference Linux-native tools (e.g., curl, jq, bash scripting) alongside PowerShell and .NET SDK.
  • Include explicit instructions or links for Linux users in the main workflow, not just in 'See also'.
  • Clarify that HDInsight clusters are Linux-based and highlight cross-platform management options.
GitHub Create Pull Request
Hdinsight Create Apache Hadoop clusters using templates - Azure HDInsight ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-create-linux-clusters-arm-templates.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page shows mild Windows bias. PowerShell is mentioned before Azure CLI, and Visual Studio (a Windows-centric tool) is highlighted as a primary method for template deployment, with no mention of Linux-native IDEs or editors beyond a brief reference to Visual Studio Code. The .NET client library example links to a Windows-specific page. While Azure CLI is covered, examples and tool recommendations tend to favor Windows-first workflows.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more commonly used on Linux.
  • Include explicit Linux shell (bash) examples for template deployment.
  • Highlight Linux-native editors (e.g., Vim, Emacs, nano) alongside Visual Studio Code for editing templates.
  • Provide parity in client library examples, linking to both Windows (.NET) and Linux (Python, Java) sample deployments.
  • Clarify that Visual Studio Code is fully cross-platform and suggest its use on Linux and macOS.
  • Avoid linking only to Windows-specific documentation in 'Next steps'; include Linux-focused resources.
GitHub Create Pull Request
Hdinsight Tips for using Hadoop on Linux-based HDInsight - Azure ...ticles/hdinsight/hdinsight-hadoop-linux-information.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page is generally Linux-focused, as expected for HDInsight on Linux, but there are some signs of Windows bias. In the section on accessing Azure Data Lake Storage Gen1, PowerShell and Visual Studio tools are mentioned before or alongside Linux-friendly alternatives. Windows-specific tools (PowerShell, Visual Studio) are listed without equivalent Linux alternatives or with less emphasis. In SDK/tool lists, .NET and Visual Studio are featured, which are primarily Windows-centric, and PowerShell is referenced without Bash or Linux shell equivalents. The order of presentation sometimes puts Windows tools before Linux ones, and there is a lack of explicit Bash or Linux shell examples for some tasks (e.g., Data Lake Storage access).
Recommendations
  • For every mention of PowerShell or Visual Studio, provide equivalent Linux alternatives (e.g., Bash scripts, VS Code, or CLI tools).
  • When listing SDKs or tools, avoid putting Windows-centric options first; alternate or group by platform.
  • Add explicit Bash or Linux shell examples for accessing Azure Data Lake Storage Gen1, not just PowerShell.
  • Clarify which tools are cross-platform and which are Windows-only, and suggest alternatives for Linux users.
  • Consider adding a table or section summarizing access methods for both Windows and Linux, highlighting parity.
GitHub Create Pull Request
Hdinsight An introduction to Apache Kafka on HDInsight - Azure .../articles/hdinsight/kafka/apache-kafka-introduction.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page for Apache Kafka on HDInsight demonstrates a Windows bias by referencing Azure PowerShell and the Azure portal as primary management interfaces for scaling operations, without mentioning Linux-native tools or CLI alternatives. There are no examples or instructions for managing Kafka clusters from Linux environments, nor is there mention of Bash, SSH, or Linux command-line tools. The documentation also omits Linux-specific guidance for monitoring or interacting with Kafka on HDInsight.
Recommendations
  • Include examples using Azure CLI (cross-platform) alongside or before Azure PowerShell and portal instructions.
  • Explicitly mention Linux compatibility and provide steps for managing Kafka clusters from Linux environments (e.g., using Bash, SSH, Azure CLI).
  • Add Linux-specific monitoring instructions, such as using native Linux tools or integrating with open-source monitoring solutions.
  • Ensure that any references to management interfaces or tools are balanced between Windows and Linux, or use platform-neutral language where possible.
GitHub Create Pull Request
Hdinsight Monitor and manage Hadoop with Ambari REST API - Azure HDInsight ...s/hdinsight/hdinsight-hadoop-manage-ambari-rest-api.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a noticeable Windows bias. Windows tools and patterns (PowerShell, Windows Subsystem for Linux, Windows paths for jq) are mentioned first or exclusively in prerequisites and examples. PowerShell is presented as an equal or primary option alongside Bash, and Windows-specific installation steps are referenced. There is inconsistent mention of native Linux environments, and some examples (such as jq usage in PowerShell) assume a Windows file path. The documentation lacks explicit examples for native Linux environments and omits guidance for macOS users.
Recommendations
  • Reorder prerequisites and examples to mention native Linux environments first, followed by Windows and macOS.
  • Clarify that all Bash examples work natively on Linux and macOS, not just via Windows Subsystem for Linux.
  • Provide installation guidance for jq and other tools on Linux and macOS, not just Windows.
  • Remove or supplement Windows-specific file paths (e.g., jq-win64) with Linux/macOS equivalents.
  • Add explicit notes or sections for running commands on native Linux and macOS shells.
  • Ensure parity in troubleshooting and environment setup instructions for Linux and macOS users.
GitHub Create Pull Request
Hdinsight Use Azure Monitor logs to monitor Azure HDInsight clusters ...insight/hdinsight-hadoop-oms-log-analytics-tutorial.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided in detail and are listed before Azure CLI (Linux-friendly) examples in each section. The prerequisites repeatedly mention PowerShell and the Az Module, and the use of PowerShell cmdlets is described in depth. The portal instructions implicitly favor Windows users, as the Azure portal experience is more seamless on Windows. Linux-specific patterns, troubleshooting, or alternative tools are not discussed, and the CLI examples, while present, are always secondary to PowerShell. There is no mention of Linux shell scripting, nor are there references to Linux-specific monitoring tools or workflows outside of Azure CLI.
Recommendations
  • Present Azure CLI examples before PowerShell examples to prioritize cross-platform usage.
  • Add explicit Linux shell scripting examples (e.g., bash scripts) for common tasks, such as enabling/disabling monitoring.
  • Include troubleshooting steps or notes for Linux users, such as dealing with permissions or agent installation issues.
  • Mention that both Azure CLI and PowerShell are cross-platform, but highlight CLI as the default for Linux environments.
  • Reference Linux-native monitoring tools or patterns where relevant, and discuss integration points.
  • Ensure screenshots and UI instructions are not Windows-centric, or clarify that the portal is accessible from any OS.
  • Add a section summarizing OS-agnostic approaches and best practices for both Windows and Linux users.
GitHub Create Pull Request
Hdinsight Set up clusters in HDInsight with Hadoop, Spark, and Kafka ...hdinsight/hdinsight-hadoop-provision-linux-clusters.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates several Windows biases. Windows tools such as Azure PowerShell are mentioned as a primary method for cluster setup, and script actions are described as being available via Windows PowerShell cmdlets and the .NET SDK before mentioning Linux alternatives. The 'Related content' section highlights working from a Windows PC, but does not offer equivalent Linux guidance. There are references to Windows-centric patterns and tools without providing equal Linux command-line examples or guidance, despite HDInsight clusters themselves being Linux-based.
Recommendations
  • Ensure all examples and instructions that use Windows tools (e.g., PowerShell, .NET SDK) are paired with Linux equivalents (e.g., Azure CLI, Bash scripts).
  • In sections listing setup methods, present Linux-friendly options (Azure CLI, cURL) before or alongside Windows tools, rather than after.
  • Add a 'Work in Apache Hadoop on HDInsight from a Linux PC' link in the Related content section to match the Windows PC guidance.
  • When discussing script actions, explicitly mention how to invoke them from Linux environments and provide Bash/CLI examples.
  • Review all references to Windows-specific tools and ensure Linux alternatives are equally documented and discoverable.
GitHub Create Pull Request
← Previous Page 3 of 35 Next →