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 126-150 of 867 flagged pages
Hdinsight Extract, transform, and load (ETL) at scale - Azure HDInsight ...rticles/hdinsight/hadoop/apache-hadoop-etl-at-scale.md
High Priority View Details →
Scanned: 2026-01-10 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 moderate Windows bias, particularly in the sections on data ingestion. Windows-centric tools and patterns such as PowerShell and AzCopy are mentioned first or exclusively for uploading data to Azure Storage, with no equivalent Linux CLI or shell script examples provided. The ingestion section emphasizes PowerShell and Windows SDKs, while Linux-native tools (e.g., Bash, curl, Linux AzCopy, Hadoop CLI) are not referenced or are mentioned later. There is a lack of explicit Linux command examples for common ETL tasks, and the documentation assumes familiarity with Windows tools and workflows.
Recommendations
  • Provide Linux/Bash CLI examples alongside PowerShell for data ingestion (e.g., using Azure CLI, AzCopy for Linux, curl, or Hadoop fs commands).
  • Mention Linux-native tools and SDKs (such as Python SDK, Bash scripts, or Hadoop CLI) equally or before Windows-specific tools.
  • Include explicit Linux command-line examples for uploading, downloading, and transforming data.
  • Clarify cross-platform compatibility for all tools and services mentioned, noting where Windows and Linux workflows differ.
  • Add references to Linux-focused documentation or quickstarts where available.
Hdinsight C#, Apache Hive & Apache Pig on Apache Hadoop - Azure HDInsight ...ght/hadoop/apache-hadoop-hive-pig-udf-dotnet-csharp.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias by primarily using Visual Studio (a Windows-centric IDE) for all development steps, recommending Windows tools (Visual Studio, Data Lake Tools for Visual Studio, Azure PowerShell) for building, uploading, and running jobs, and providing step-by-step instructions only for these tools. There are no equivalent instructions or examples for Linux-native workflows, such as using Mono directly, building with dotnet CLI, or uploading/running jobs via Linux command line or open-source tools. Linux usage is only mentioned in passing, and the actual development and deployment process is described exclusively with Windows tooling.
Recommendations
  • Provide step-by-step instructions for building C# UDFs using cross-platform tools such as dotnet CLI and Mono on Linux.
  • Include examples of uploading .exe files to HDInsight clusters using Azure CLI, azcopy, or other Linux-friendly methods.
  • Offer guidance for running Hive and Pig jobs from the Linux command line, including sample commands and expected outputs.
  • Mention and demonstrate alternative IDEs (such as VS Code or JetBrains Rider) that are available on Linux and macOS, not just Visual Studio.
  • Ensure that all major steps (build, upload, run) have parity between Windows and Linux workflows, with examples for both.
Hdinsight Use C# with MapReduce on Hadoop in HDInsight - Azure ...oop/apache-hadoop-dotnet-csharp-mapreduce-streaming.md
High Priority View Details →
Scanned: 2026-01-10 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 toward Windows environments by prioritizing Visual Studio and PowerShell for development, build, upload, and job submission workflows. Windows-specific tools (Visual Studio, Data Lake Tools for Visual Studio) are mentioned exclusively or before any Linux alternatives. PowerShell is featured as a primary automation method, while Linux-native alternatives (such as Bash scripting, CLI tools, or Mono command-line usage) are missing or underrepresented. There are no examples of building C# applications on Linux or using Linux-native upload methods.
Recommendations
  • Add instructions for building C# MapReduce applications using Mono and .NET CLI on Linux (e.g., using 'mcs' or 'dotnet build').
  • Include Linux-native upload workflows, such as using Azure CLI, azcopy, or Hadoop's hdfs dfs command.
  • Provide Bash script examples for job submission and result retrieval, alongside PowerShell examples.
  • Mention cross-platform editors (e.g., VS Code) and how to use them for C# development on Linux.
  • Ensure that Linux workflows are presented with equal prominence and detail as Windows/PowerShell workflows.
Hdinsight Java user-defined function (UDF) with Apache Hive Azure HDInsight ...ticles/hdinsight/hadoop/apache-hadoop-hive-java-udf.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. The test environment is explicitly Windows 10, all file and directory commands use Windows Command Prompt syntax (cmd), and file editing is done with Notepad. Troubleshooting uses PowerShell scripts for line ending conversion, with no Linux alternatives provided. Linux shell equivalents for directory creation, file editing, and troubleshooting are missing, despite HDInsight clusters themselves being Linux-based.
Recommendations
  • Add Linux shell (bash) equivalents for all file and directory commands (e.g., mkdir, cd, rm -rf).
  • Include instructions for editing files using common Linux editors (e.g., nano, vim) alongside Notepad.
  • Provide troubleshooting steps for line ending conversion using Linux tools (e.g., dos2unix, sed).
  • Present cross-platform commands in parallel, or default to Linux examples given HDInsight's Linux foundation.
  • Clarify that the steps are applicable on both Windows and Linux, and specify any OS-specific differences.
  • Avoid using Windows-specific tools (Notepad, PowerShell) exclusively; offer alternatives for Linux users.
Hdinsight Security: Migrate on-premises Apache Hadoop to Azure HDInsight ...p-on-premises-migration-best-practices-security-devops.md
High Priority View Details →
Scanned: 2026-01-10 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 exclusively referencing Microsoft Entra Domain Services (Active Directory), domain joining, and AD/DNS tools, which are Windows-centric technologies. There are no examples or mentions of Linux-native identity management (such as LDAP, Kerberos, or MIT Kerberos), nor are Linux-specific security patterns or tools discussed. All instructions and examples assume a Windows-style domain environment, and the documentation does not provide parity for organizations running Linux-based authentication or management systems.
Recommendations
  • Add examples and guidance for integrating HDInsight clusters with Linux-native identity providers, such as OpenLDAP or MIT Kerberos.
  • Include instructions for configuring cluster security using Linux tools and patterns, not just Microsoft Entra Domain Services.
  • Provide sample configurations for both Windows and Linux environments, ensuring that Linux administrators can follow migration and security best practices.
  • Mention and compare Linux equivalents (e.g., sssd, nsswitch, PAM) where Windows tools (AD, DNS) are referenced.
  • Clarify which steps are specific to Windows environments and offer alternative steps for Linux-based clusters.
Hdinsight Architecture: On-premises Apache Hadoop to Azure HDInsight ...doop-on-premises-migration-best-practices-architecture.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by listing Azure PowerShell as a primary command-line tool for cluster creation, mentioning Azure SQL Database monitoring via Azure portal (a Windows-centric tool), and not providing explicit Linux shell examples or highlighting Linux-native tools. Azure CLI and cURL are mentioned, but PowerShell is listed alongside them, and no Linux-specific patterns or examples are given. The documentation does not provide parity in example scripts or workflows for Linux users.
Recommendations
  • Provide explicit Linux shell (bash) examples for cluster creation and management, especially using Azure CLI and cURL.
  • List Linux-native tools (e.g., SSH, SCP, bash scripts) where relevant, and show how they can be used in HDInsight workflows.
  • Ensure that Azure CLI (cross-platform) is listed before Azure PowerShell in tables and examples to emphasize platform neutrality.
  • Include guidance for monitoring and managing clusters using Linux tools (e.g., command-line monitoring, open-source alternatives to Azure portal).
  • Add notes or sections clarifying that all HDInsight clusters run on Linux and that most management tasks can be performed from Linux environments.
Hdinsight Data migration: On-premises Apache Hadoop to Azure HDInsight ...op-on-premises-migration-best-practices-data-migration.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows-centric tools (Azure Storage Explorer, AzCopy, Azure PowerShell) before mentioning cross-platform or Linux-native options. There are no explicit Linux command-line examples (e.g., Bash, Linux CLI tools) for data transfer, and the use of PowerShell is referenced without Linux alternatives. The only command-line example is for Hadoop DistCp, which is cross-platform, but other migration steps (such as using Azure CLI or scripting Hive metastore migration) lack Linux-specific guidance.
Recommendations
  • Add explicit Linux/Bash command-line examples for data transfer, such as using Azure CLI or AzCopy on Linux.
  • Mention cross-platform compatibility for tools like AzCopy and Azure CLI, and provide installation/use instructions for Linux.
  • Include Linux-native scripting examples for Hive metastore migration (e.g., Bash scripts) and clarify that wrapper scripts are available for Linux.
  • Avoid listing Windows tools first; present cross-platform tools (Azure CLI, AzCopy) before platform-specific ones (PowerShell, Storage Explorer).
  • Highlight any differences or considerations when performing migration steps on Linux vs. Windows.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing only Windows command prompt examples (using 'set' for environment variables and Windows-style variable expansion), referencing Windows-specific paths for tools (jq), and not offering equivalent Linux/bash examples. The prerequisites and instructions do not mention or show how to perform the same steps on Linux or macOS, despite HDInsight clusters being Linux-based by default.
Recommendations
  • Include parallel Linux/bash examples for all command-line instructions, using 'export' for environment variables and '$VARIABLE' for expansion.
  • Mention installation and usage of jq on Linux (e.g., 'jq' in PATH) rather than only referencing Windows paths.
  • Add a note or section explicitly addressing cross-platform usage, clarifying differences and providing examples for both Windows and Linux/macOS.
  • List SQL client options for Linux (such as Azure Data Studio, sqlcmd) alongside Windows tools.
  • Review and update all command blocks to ensure Linux parity, possibly using tabs or callouts to distinguish platform-specific instructions.
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-10 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 tool, for interacting with Azure HDInsight and running Hive queries. All instructions, screenshots, and workflows are centered around Visual Studio, with no mention of Linux-based alternatives or cross-platform tools. Windows tools and patterns are presented exclusively, and there are no examples or guidance for Linux users or those using non-Windows environments.
Recommendations
  • Add equivalent instructions for connecting to HDInsight and running Hive queries using cross-platform tools such as VS Code, Apache Zeppelin, Jupyter Notebooks, or command-line interfaces (e.g., SSH, Beeline, Hive CLI).
  • Include examples and screenshots for Linux and macOS environments, showing how to perform similar tasks without Visual Studio.
  • Mention and link to Linux-friendly tools (e.g., Azure CLI, HDInsight SDK for Python, Hive CLI) alongside Visual Studio, and provide parity in documentation structure.
  • Clarify in the prerequisites and introduction that the described workflow is Windows-specific, and direct Linux/macOS users to alternative documentation.
  • Provide a comparison table of available tools for different operating systems, highlighting feature parity and limitations.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Cmd Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a noticeable Windows bias. Curl examples are presented using Windows CMD syntax (set, ^ line continuation, Windows paths for jq), with no explicit Linux/bash equivalents. PowerShell is given as a primary alternative, but there are no bash or Linux shell script examples. Windows tools and patterns (e.g., jq-win64.exe, set) are referenced exclusively, and instructions assume a Windows environment by default.
Recommendations
  • Add explicit Linux/bash examples for all curl commands, using export for environment variables, \ for line continuation, and typical Linux jq paths (e.g., /usr/bin/jq).
  • Present Linux/bash examples before or alongside Windows CMD examples to avoid Windows-first bias.
  • Clarify tool installation and usage for Linux users (e.g., how to install jq and curl on Ubuntu/CentOS).
  • Avoid hardcoding Windows paths (e.g., C:\HDI\jq-win64.exe) in generic instructions; use platform-agnostic or Linux paths where appropriate.
  • Mention that PowerShell is primarily for Windows, and suggest bash or other Linux-native scripting alternatives for Linux users.
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-10 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 a Windows bias by referencing Windows-centric tools and workflows (e.g., SQL Server Integration Services, Excel, PowerShell, C#, Hive ODBC driver) for ETL operations and automation. Linux-native equivalents (such as Linux command-line tools, shell scripting, or open-source alternatives) are not mentioned, and examples are tailored to Windows environments. The order of presentation also places Windows tools before Linux options, and there are no Linux-specific code samples or automation patterns.
Recommendations
  • Include Linux-native ETL tools and workflows, such as using shell scripts, cron jobs, or Linux-based orchestration tools (e.g., Apache Airflow, Oozie) for automation.
  • Provide code examples for Linux environments, such as Bash scripts for automating Hive queries.
  • Mention open-source alternatives to Windows tools (e.g., use csvkit or pandas for CSV manipulation instead of Excel).
  • Reference Linux database clients and drivers (e.g., JDBC, Beeline) for accessing Hive and loading data.
  • Present Linux options alongside Windows tools, or alternate the order to avoid Windows-first bias.
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-10 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 primarily through the exclusive use of PowerShell scripts for certificate management and cluster updates, without providing equivalent Linux (bash/CLI) examples. The instructions assume access to Windows tools and patterns, such as PowerShell cmdlets and certificate handling via Windows APIs, and do not mention or prioritize Linux alternatives. This may hinder users operating in Linux environments or those using Azure CLI/bash for automation.
Recommendations
  • Provide equivalent Linux/bash/Azure CLI commands for certificate creation, management, and cluster updates.
  • Include instructions for using OpenSSL to generate certificates and associate them with service principals.
  • Add examples using Azure CLI (az hdinsight ...) for cluster identity certificate updates.
  • Clearly indicate platform-specific steps and offer parity for both Windows and Linux users.
  • Reference cross-platform tools and avoid assuming the use of Windows-only utilities.
Hdinsight What is Apache Hive and HiveQL - Azure HDInsight ...b/main/articles/hdinsight/hadoop/hdinsight-use-hive.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates some Windows bias by listing Windows-specific tools (Visual Studio, PowerShell) as distinct options for interacting with Hive, and by mentioning Windows tools before their Linux equivalents in several places. The inclusion of PowerShell and Visual Studio as dedicated sections, while Linux/Unix/macOS users are directed to more generic or cross-platform tools, may give the impression of Windows being a primary or preferred platform. Additionally, SQL Server Integration Services (SSIS) is highlighted for scheduling Hive jobs, which is a Windows-centric tool, and is described before Apache Oozie, a cross-platform alternative.
Recommendations
  • Ensure that Linux and macOS tools are given equal prominence and are listed before or alongside Windows tools, rather than after.
  • Provide Linux-specific examples or highlight Linux-native tools (such as command-line Hive, Bash scripting, or integration with cron for scheduling) where Windows tools (PowerShell, Visual Studio) are mentioned.
  • Expand documentation for cross-platform and browser-based tools, such as Hive View and Beeline, with example workflows for Linux/macOS users.
  • When discussing scheduling, introduce Apache Oozie and other cross-platform solutions before Windows-centric options like SSIS.
  • Add explicit Linux command-line examples for common Hive operations, including connecting, running queries, and scheduling jobs.
  • Review and balance the order of tool presentation to avoid implying Windows is the default or preferred environment.
Hdinsight Converting certificate contents to base-64 - Azure HDInsight ...-troubleshoot-converting-service-principal-certificate.md
High Priority View Details →
Scanned: 2026-01-10 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 exclusively provides PowerShell and C# examples for converting a certificate to base-64, both of which are Windows-centric. There are no Linux or cross-platform command-line examples (e.g., using OpenSSL or base64 utilities), nor is there mention of Linux tools or workflows. This creates a bias toward Windows users and may hinder Linux users from following the instructions.
Recommendations
  • Add Linux shell examples, such as using 'openssl' and 'base64' commands to convert a .pfx file to base-64.
  • Include instructions for macOS users, if applicable.
  • Present cross-platform solutions first, or at least alongside Windows-specific ones.
  • Explicitly mention that the process can be performed on Linux and provide equivalent commands.
  • Clarify any platform-specific caveats or differences in certificate handling.
Hdinsight Run Apache Sqoop jobs with Azure HDInsight (Apache Hadoop) .../main/articles/hdinsight/hadoop/hdinsight-use-sqoop.md
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias by focusing on Azure PowerShell as the primary method for running Sqoop jobs, with explicit mention of Windows as the client OS for PowerShell and .NET SDK examples. Linux and macOS are only referenced in the context of SSH, and no direct Linux command-line or shell examples are provided. The setup instructions and walkthroughs prioritize Windows-centric tools and workflows, and Linux limitations are listed without offering alternative solutions or parity.
Recommendations
  • Provide equivalent Linux shell (bash) and macOS command-line examples for running Sqoop jobs, not just SSH access.
  • Include walkthroughs for Sqoop job submission using Linux-native tools (e.g., shell scripts, CLI) alongside PowerShell.
  • Reorder examples so that Linux and cross-platform methods are presented before or alongside Windows-specific tools.
  • Expand documentation to cover Linux-specific workflows for setup, job management, and troubleshooting.
  • Address Linux limitations by suggesting workarounds or alternative approaches where possible.
Hdinsight Submit Apache Hadoop jobs in HDInsight ...t/hadoop/submit-apache-hadoop-jobs-programmatically.md
High Priority View Details →
Scanned: 2026-01-10 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 PowerShell and .NET SDK as primary options reflects a Windows-centric approach, as these tools are most commonly used on Windows platforms. PowerShell examples and references are given equal prominence to curl, but there are no mentions of Linux-native tools (e.g., Bash scripts, shell commands) or guidance for Linux users. The ordering of .NET SDK and PowerShell before curl also suggests a Windows-first bias.
Recommendations
  • Add explicit examples and references for submitting Hadoop jobs using Bash or shell scripts on Linux.
  • Include instructions for using Linux-native tools (e.g., wget, native Hadoop CLI) alongside .NET SDK and PowerShell.
  • Reorder the presentation so that cross-platform tools (like curl) are listed first, or clarify platform applicability for each method.
  • Add a section or note highlighting Linux support and parity, ensuring Linux users know how to perform equivalent actions.
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-10 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) instructions for uploading files and running Hive/Pig jobs. However, there is a strong emphasis on PowerShell throughout, with extensive PowerShell scripts and troubleshooting tips specific to Windows environments. PowerShell examples are more detailed and cover more scenarios than their shell counterparts. Troubleshooting advice is Windows-centric, focusing on CRLF line endings and using PowerShell to fix them. There is no mention of Linux-native tools for line ending conversion, and PowerShell is presented as the primary remote management tool, with limited discussion of Linux alternatives. The documentation also references deploying modules to 'Windows Azure HDInsight' in the next steps, reinforcing a Windows-first perspective.
Recommendations
  • Provide equivalent, detailed Bash/shell scripts for all PowerShell examples, including remote job submission and file upload.
  • Include troubleshooting steps for line ending issues using Linux tools (e.g., dos2unix, sed) alongside PowerShell solutions.
  • Mention and demonstrate use of Azure CLI for cluster management and job submission as a cross-platform alternative.
  • Reword sections to avoid implying PowerShell is the default or preferred method; present Bash/shell and PowerShell options equally.
  • Update references to 'Windows Azure HDInsight' to 'Azure HDInsight' to avoid reinforcing Windows-centric branding.
  • Add explicit guidance for Linux/macOS users, including editor recommendations and file transfer tips.
Hdinsight Tutorial - Use Apache HBase in Azure HDInsight ...sight/hbase/apache-hbase-tutorial-get-started-linux.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates some Windows bias, especially in the prerequisites section, where Bash on Windows 10 (via WSL) is mentioned before native Linux/Unix shells, and Windows PowerShell's Invoke-RestMethod is highlighted as an alternative for curl commands. There is a tendency to address Windows users first or provide Windows-specific guidance before Linux equivalents, despite the tutorial being focused on Linux-based HDInsight clusters. No explicit Linux examples are missing, but Windows tooling and patterns are referenced more prominently than strictly necessary.
Recommendations
  • Present Linux/Unix shell usage first in prerequisites and examples, as HDInsight clusters are Linux-based.
  • Mention Windows alternatives (WSL, PowerShell) after describing native Linux/Unix approaches, not before.
  • Provide explicit Linux command-line examples wherever possible, and only add Windows-specific notes as secondary guidance.
  • Avoid suggesting Windows PowerShell cmdlets unless there is a clear use case that cannot be accomplished with standard Linux tools.
  • Clarify that all examples are directly applicable to Linux/macOS environments, and provide separate, clearly marked sections for Windows-specific instructions if needed.
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-10 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 noticeable Windows bias. Windows-specific tools (Notepad, Command Prompt, PowerShell) are used exclusively or mentioned first throughout the setup and workflow. All file manipulation and project creation commands use Windows syntax (cmd, DEL, mkdir, Notepad), with no Linux equivalents provided. The PowerShell section is extensive and detailed, while there is no comparable Linux shell scripting guidance. The test environment is explicitly Windows 10, and readers are told to 'modify accordingly' for other environments, but no Linux-specific instructions or examples are given.
Recommendations
  • Provide equivalent Linux shell commands (e.g., mkdir, rm, nano/vim for editing files) alongside Windows cmd examples.
  • Include a Linux-based test environment example, or at least mention how to adapt the workflow for Linux users.
  • Offer a Bash shell script alternative to the PowerShell module for uploading JARs and running jobs.
  • Use cross-platform editors in examples (e.g., VS Code, nano, vim) rather than Notepad.
  • Clearly indicate which commands are platform-specific and provide alternatives for both Windows and Linux.
  • Consider reordering sections so that Linux instructions are not always secondary to Windows ones.
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-10 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 source of a REST API limitation. It does not mention Linux equivalents (e.g., Apache, Nginx) or provide troubleshooting steps/examples for Linux-based HDInsight clusters. The mitigation steps do not clarify OS-specific instructions, and all examples and terminology are Windows-centric.
Recommendations
  • Explicitly mention whether the issue affects both Windows and Linux HDInsight clusters, or clarify if it is Windows-only.
  • If Linux clusters are affected, provide examples or troubleshooting steps relevant to Linux environments (e.g., mention Linux gateway modules or REST server configurations).
  • Include references to Linux tools and patterns (such as Apache or Nginx gateways) if applicable.
  • Provide parity in examples and terminology, ensuring both Windows and Linux users can follow the guidance.
  • Clarify whether the mitigation steps (deploying on a VM in the same VNet) differ for Windows vs. Linux clusters, and provide OS-specific instructions if necessary.
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-10 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 Windows bias by exclusively providing PowerShell commands for NuGet package installation, referencing the PowerShell client GUID for authentication, and using Windows-style command prompts in the HBase scaling section. There are no Linux shell equivalents or cross-platform instructions for these steps, and Windows tools/patterns are mentioned first and exclusively in several places.
Recommendations
  • Provide Linux/Unix shell equivalents for NuGet package installation (e.g., dotnet CLI or manual NuGet commands).
  • Clarify that the .NET SDK can be used cross-platform and provide examples for Linux/macOS environments, including authentication flows.
  • Replace or supplement Windows command prompt examples (e.g., HBase scaling commands) with Bash shell equivalents for Linux clusters.
  • Avoid referencing Windows-specific GUIDs (such as PowerShell client) without explaining cross-platform alternatives.
  • Ensure all administrative tasks have Linux/macOS instructions or note any platform limitations.
Hdinsight Install third-party applications on Azure HDInsight ...icles/hdinsight/hdinsight-apps-install-applications.md
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias by referencing Azure PowerShell and Azure Classic CLI as deployment tools, without mentioning Linux-native equivalents (e.g., Azure CLI on Bash, ARM templates via Linux shell). All procedural instructions are focused on the Azure portal (a web UI, often used from Windows), with no examples or guidance for Linux users (such as command-line installation, SSH-based deployment, or scripting). Windows tools and terminology (PowerShell, portal navigation) are mentioned before or instead of Linux alternatives. There are no explicit Linux command examples, and the only mention of SSH is in the context of connecting to the edge node, not for application installation or management.
Recommendations
  • Include Azure CLI (cross-platform) examples for deploying applications and managing clusters, with explicit Linux shell commands.
  • Provide step-by-step instructions for installing applications using SSH and Bash scripts, especially for custom or third-party apps.
  • Mention Linux-native tools (e.g., Bash, SCP, SFTP) alongside PowerShell and Azure portal, and clarify parity in capabilities.
  • Add a section or callouts for Linux users, highlighting differences or additional steps when using Linux environments.
  • Ensure that references to deployment tools and patterns do not prioritize Windows-specific options (PowerShell, portal) over cross-platform or Linux-native alternatives.
Hdinsight Cluster capacity planning in Azure HDInsight ...main/articles/hdinsight/hdinsight-capacity-planning.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias by mentioning PowerShell scripting and Azure Automation as primary methods for cluster lifecycle management, without referencing equivalent Linux-native tools or shell scripting. Windows-centric tools and patterns are mentioned before any Linux alternatives, and screenshots and UI instructions are tailored to the Azure Portal, which is platform-agnostic but often used from Windows environments. There are no explicit Linux shell examples or references to Linux automation tools.
Recommendations
  • Include examples of cluster provisioning and deletion using Bash scripts and Azure CLI, alongside PowerShell.
  • Mention Linux-native automation options, such as cron jobs or Ansible, for scheduling cluster operations.
  • Clarify that Azure Automation and scripting can be performed from both Windows and Linux environments.
  • Add explicit Linux shell script examples for lifecycle management tasks.
  • Ensure parity in tool recommendations by listing both PowerShell and Bash/CLI approaches for common administrative tasks.
Hdinsight Apache Hive libraries during cluster creation - Azure HDInsight ...icles/hdinsight/hdinsight-hadoop-add-hive-libraries.md
High Priority View Details →
Scanned: 2026-01-10 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 providing a PowerShell (.ps1) script as the primary example and referencing Windows-centric tools (Azure Storage Explorer) for file uploads. The PowerShell script is mentioned before the Bash script, and the script action section lists both but does not equally highlight Linux usage. There is also a lack of explicit Linux command-line examples for uploading files, and the guidance assumes familiarity with Windows tools and patterns.
Recommendations
  • Provide Linux command-line examples for uploading files to Azure Blob Storage, such as using azcopy or Azure CLI.
  • List Bash script examples before PowerShell examples when targeting Linux-based clusters.
  • Mention cross-platform tools (e.g., Azure CLI, azcopy) alongside or before Windows-specific tools like Azure Storage Explorer.
  • Clarify which script (PowerShell or Bash) is appropriate for which OS, and ensure Linux usage is equally or more prominently documented.
  • Add explicit instructions for Linux users on preparing and uploading JAR files, including sample commands.
Hdinsight Tutorial: On-demand clusters in Azure HDInsight with Data Factory ...dinsight/hdinsight-hadoop-create-linux-clusters-adf.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows usage, with all automation and scripting examples provided exclusively in PowerShell. There are no equivalent Bash or CLI examples for Linux users. The prerequisites and resource creation steps assume PowerShell, and the workflow is described in a way that prioritizes Windows tooling and patterns, with no mention of Linux alternatives or parity.
Recommendations
  • Provide equivalent Bash shell scripts or Azure CLI commands for all PowerShell examples, especially for resource creation and file copying.
  • Explicitly mention Linux support in the prerequisites and workflow, including installation instructions for Azure CLI on Linux.
  • Add a selector or toggle at the top of the tutorial to choose between Windows/PowerShell and Linux/Bash/CLI instructions.
  • Ensure screenshots and UI instructions are platform-neutral or provide Linux-specific guidance where relevant.
  • Highlight any differences or considerations for Linux users, such as authentication methods, file path formats, or tool installation.