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 301-325 of 867 flagged pages
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/submit-apache-hadoop-jobs-programmatically.md ...t/hadoop/submit-apache-hadoop-jobs-programmatically.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by prominently featuring PowerShell as a primary method for submitting Hadoop jobs, listing it alongside .NET SDK (a Microsoft-centric technology) and curl. PowerShell is a Windows-native tool, and its inclusion without mention of Linux-native alternatives (such as Bash scripts or Linux command-line tools) suggests a preference for Windows environments. The order of presentation (.NET SDK, curl, PowerShell) also places Microsoft technologies before cross-platform or Linux-native options. There are no explicit Linux examples or references to Linux-specific tooling.
Recommendations
  • Add explicit Linux/Bash examples for submitting Hadoop jobs, especially for common Linux shell environments.
  • Include references to Linux-native tools (e.g., Bash scripts, shell commands) alongside PowerShell, and ensure parity in example depth.
  • Reorder the presentation to start with cross-platform or Linux-native methods (e.g., curl, Bash) before Windows-specific tools.
  • Clarify which methods are cross-platform and which are Windows-specific, helping users choose the best fit for their environment.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-visual-studio-tools-get-started.md ...adoop/apache-hadoop-visual-studio-tools-get-started.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation 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 examples, instructions, and screenshots are centered around Visual Studio workflows, with no mention of equivalent Linux tools or workflows. Windows-specific tools and patterns (Visual Studio, Server Explorer, VSIX Installer) are referenced exclusively, and there are no Linux or cross-platform alternatives presented.
Recommendations
  • Add equivalent instructions for Linux users, such as using VS Code with relevant extensions, command-line tools (Hive CLI, Beeline), or web-based interfaces (Ambari, Azure Portal).
  • Include examples of connecting to HDInsight clusters and running Hive queries from Linux environments, such as via SSH, Beeline, or REST APIs.
  • Mention and provide links to cross-platform or Linux-native tools for Hadoop/Hive development and management.
  • Clarify in the prerequisites and introduction that the described workflow is Windows-specific, and direct Linux/macOS users to alternative documentation.
  • Where possible, provide parity in screenshots and step-by-step guides for Linux tools (e.g., using Azure CLI, Hive CLI, or VS Code).
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-query-with-phoenix.md ...les/hdinsight/hbase/apache-hbase-query-with-phoenix.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Cmd Examples Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by presenting command-line examples in Windows Command Prompt (cmd) syntax first (e.g., curl and ssh commands), and by referencing 'command prompt' rather than 'terminal' or 'shell'. There are no explicit Linux-specific examples or instructions, and the use of 'cmd' code blocks may confuse Linux users. The deletion instructions mention PowerShell before Azure CLI, and do not provide direct Linux shell or Bash alternatives for cluster management.
Recommendations
  • Provide both Windows (cmd/PowerShell) and Linux/macOS (Bash) command examples side-by-side, especially for curl and ssh commands.
  • Use neutral terminology such as 'terminal' or 'shell' instead of 'command prompt' when referring to where commands should be entered.
  • Explicitly mention that the commands work on Linux/macOS terminals, and clarify any syntax differences if applicable.
  • Include instructions for deleting clusters using Bash/Azure CLI directly from Linux/macOS, not just PowerShell.
  • Add notes or sections for Linux users to ensure parity and clarity.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-use-mapreduce-curl.md ...s/hdinsight/hadoop/apache-hadoop-use-mapreduce-curl.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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. Examples for setting environment variables and running curl commands are shown using Windows CMD syntax (e.g., 'set VAR=' and '^' for line continuation), and jq is referenced with a Windows path (C:\HDI\jq-win64.exe). PowerShell examples are provided in detail, while Linux shell equivalents (e.g., bash, sh) are missing. There is no explicit Linux shell example for setting variables, running curl with jq, or handling output, despite HDInsight supporting Linux-based clusters.
Recommendations
  • Add Linux shell (bash/sh) examples alongside Windows CMD and PowerShell, including variable setting (e.g., 'export VAR=value'), line continuation (using '\'), and jq usage (e.g., 'jq .id').
  • Reference jq generically or provide both Windows and Linux installation/usage paths.
  • Clarify in each example which OS the commands are intended for, and ensure Linux commands are presented at parity with Windows.
  • Consider listing Linux shell examples before or alongside Windows examples to avoid the perception of Windows-first bias.
  • Where possible, use cross-platform syntax or note differences explicitly.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-build-java-maven-linux.md ...hdinsight/hbase/apache-hbase-build-java-maven-linux.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 strong Windows bias: all initial examples use Windows command prompt syntax (cmd), Notepad is the only text editor referenced, and the test environment is explicitly Windows 10. PowerShell is given a dedicated section with extensive scripts and usage, while Linux equivalents (such as Bash, Vim, nano, or Linux file paths) are absent or only implied. There are no explicit Linux command examples for project setup, file editing, or file deletion, and Windows tools/patterns are mentioned exclusively or before any Linux alternatives.
Recommendations
  • Provide parallel Linux examples for all command-line instructions, using Bash syntax and Linux file paths.
  • Mention and show usage of common Linux text editors (e.g., nano, vim) alongside Notepad.
  • Include Linux-specific instructions for file deletion (e.g., rm) and directory creation (mkdir).
  • Add a Linux test environment section, or clarify cross-platform compatibility for all steps.
  • Balance PowerShell coverage with equivalent Bash/SSH workflows for uploading files and running jobs.
  • Use platform-neutral language and examples where possible, or clearly mark platform-specific steps.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/python-udf-hdinsight.md ...main/articles/hdinsight/hadoop/python-udf-hdinsight.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page provides both shell (Linux/Unix) and PowerShell (Windows) examples for uploading files and running Hive/Pig jobs. However, there is a notable emphasis on PowerShell throughout, with extensive PowerShell scripts and troubleshooting steps. Windows-specific issues (CRLF line endings) and solutions are highlighted, while Linux equivalents (e.g., dos2unix) are not mentioned. PowerShell is presented as a primary remote management tool, and Linux alternatives (such as Azure CLI or Bash scripting) are not covered. The troubleshooting section focuses on Windows editor problems and PowerShell fixes, further reinforcing Windows bias.
Recommendations
  • Add equivalent Azure CLI and Bash script examples for all PowerShell steps, including file upload and job submission.
  • Include troubleshooting steps for Linux users, such as using 'dos2unix' to fix line endings.
  • Mention and provide guidance for Linux-native tools (e.g., nano, vi, sed) for editing and preparing scripts.
  • Balance the prominence of PowerShell and shell examples, ensuring Linux methods are presented first or equally.
  • Clarify that HDInsight clusters are Linux-based and that most users will interact via SSH/bash, not PowerShell.
  • Provide links to Linux/Unix documentation for remote management and scripting with Azure HDInsight.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-create-non-interactive-authentication-dotnet-applications.md ...ate-non-interactive-authentication-dotnet-applications.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias by exclusively providing C#/.NET examples, referencing NuGet and PowerShell, and guiding users through Azure portal steps without mentioning Linux equivalents or cross-platform alternatives. There are no examples for Linux development environments, nor are CLI or scripting alternatives (such as Bash or Azure CLI) provided. The prerequisites and instructions assume a Windows-centric workflow, omitting guidance for Linux users.
Recommendations
  • Include equivalent examples using Azure CLI and Bash scripts for Linux users.
  • Mention cross-platform .NET development tools (e.g., dotnet CLI) and provide instructions for Linux and macOS environments.
  • Add guidance for installing required packages and dependencies on Linux (e.g., using apt-get, yum, or dotnet CLI).
  • Provide instructions for role assignment using Azure CLI or REST API, not just the Azure portal.
  • Clarify that the steps and code samples are cross-platform where applicable, or explicitly provide Linux/macOS alternatives.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-administer-use-dotnet-sdk.md ...icles/hdinsight/hdinsight-administer-use-dotnet-sdk.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 providing only PowerShell commands for NuGet package installation, referencing the PowerShell client GUID for authentication, and using Windows-centric command patterns (e.g., %HBASE_HOME% environment variable and command prompt syntax). There are no Linux-specific examples or instructions for equivalent tasks, such as installing packages via dotnet CLI or authenticating from Linux environments. The documentation assumes a Windows development environment throughout and omits Linux alternatives.
Recommendations
  • Add Linux-specific instructions for installing NuGet packages, such as using 'dotnet add package' or 'nuget' CLI commands.
  • Provide authentication examples that work on Linux and macOS, including guidance for non-Windows environments.
  • Replace or supplement Windows environment variable syntax (e.g., %HBASE_HOME%) with Linux equivalents (e.g., $HBASE_HOME).
  • Include code samples and command-line instructions that are tested and applicable on Linux and macOS.
  • Explicitly mention cross-platform compatibility and highlight any differences or additional steps required for Linux users.
  • Avoid referencing Windows-only tools (such as PowerShell client GUID) without noting alternatives for Linux.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-add-storage.md ...ain/articles/hdinsight/hdinsight-hadoop-add-storage.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a detailed PowerShell example for verifying storage accounts but does not offer an equivalent Linux/Unix shell or CLI example. The verification section leads with PowerShell, and there is no Bash, SSH, or Linux-native command alternative, despite HDInsight clusters being Linux-based. This prioritizes Windows tooling and leaves Linux users without parity in verification steps.
Recommendations
  • Add a Linux/Unix shell example for verifying storage accounts, such as using curl, jq, or other native tools.
  • Include Azure CLI commands for verification, as Azure CLI is cross-platform.
  • Present verification methods for both Windows and Linux users side-by-side, or lead with Linux examples given the cluster OS.
  • Clarify that PowerShell is optional and not required for most cluster operations.
  • Review other sections for similar bias and ensure Linux parity throughout.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-linux-use-ssh-unix.md ...icles/hdinsight/hdinsight-hadoop-linux-use-ssh-unix.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page generally aims for cross-platform coverage, but there are several signs of Windows bias. Windows SSH client options are listed first and in greater detail, including PowerShell cmdlets and graphical tools like PuTTY and MobaXterm. Azure PowerShell is mentioned before Azure CLI in cluster creation examples, and PowerShell-specific parameters are described in detail. Linux/Unix commands are present, but Windows tools and patterns are often introduced before their Linux equivalents, and some advanced SSH configuration steps are described as working 'with Bash on Windows 10', reinforcing a Windows-centric approach.
Recommendations
  • Present Linux/Unix examples and tools before Windows-specific ones to avoid implicit prioritization.
  • Include more explicit Linux/Unix command-line examples for cluster creation and management, not just Azure CLI.
  • Balance PowerShell and CLI coverage, ensuring CLI examples are as detailed and prominent as PowerShell ones.
  • List graphical SSH clients in a neutral order, and mention popular Linux graphical clients (e.g., GNOME Terminal, Konsole) if relevant.
  • Clarify which steps are universal and which are platform-specific, and avoid phrasing that centers Windows as the default environment.
  • Add troubleshooting and configuration notes for Linux/Unix SSH clients, not just for Windows.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-oms-log-analytics-tutorial.md ...insight/hdinsight-hadoop-oms-log-analytics-tutorial.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently presents Windows-centric tools and workflows first, such as Azure PowerShell and the Azure Portal, with detailed PowerShell examples and references to Windows-specific modules. While Azure CLI examples are provided (which are cross-platform), there is a notable emphasis on PowerShell and the Azure Portal, both of which are most commonly used on Windows. There is little to no mention of Linux-native tools, shell scripting, or guidance for Linux users outside of Azure CLI. The documentation does not provide parity for Linux-specific workflows or highlight Linux usage patterns, despite HDInsight clusters typically running on Linux.
Recommendations
  • Provide Linux shell (bash) examples alongside PowerShell, especially for cluster management and monitoring tasks.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and recommend CLI as the preferred cross-platform tool.
  • Include instructions for using Linux-native tools (e.g., curl, jq) to interact with Azure Monitor APIs where appropriate.
  • Add troubleshooting and agent management steps specific to Linux environments, such as log file locations, service management (systemctl), and permissions.
  • Reorder sections so that cross-platform (CLI) or Linux-native instructions appear before Windows/PowerShell examples.
  • Clarify that HDInsight clusters are Linux-based and provide guidance tailored to Linux administrators.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-apps-install-applications.md ...icles/hdinsight/hdinsight-apps-install-applications.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing the Azure portal (a web UI most commonly used from Windows), mentioning Azure PowerShell and Azure Classic CLI as deployment tools, and omitting explicit Linux-native command-line examples (such as Azure CLI or Bash scripting). The instructions and screenshots are portal-centric, with no parity for Linux users who may prefer command-line automation or non-GUI workflows. Linux tools and patterns (e.g., Azure CLI, Bash, SSH usage examples) are either missing or mentioned only in passing, and not as primary options.
Recommendations
  • Add step-by-step instructions for installing and managing HDInsight applications using Azure CLI, including example commands.
  • Provide Bash script examples for automating application installation and management on HDInsight clusters.
  • Include screenshots or terminal output for Linux command-line workflows, not just Azure portal UI.
  • Mention Linux-native tools (e.g., SSH, SCP, Azure CLI) before or alongside Windows tools (e.g., PowerShell), ensuring equal prominence.
  • Clarify that all instructions apply equally to Linux and Windows users, and highlight any OS-specific differences where relevant.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-provision-linux-clusters.md ...hdinsight/hdinsight-hadoop-provision-linux-clusters.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. It references Azure PowerShell and Windows PowerShell cmdlets as primary methods for cluster setup and customization, often listing them alongside or before Linux alternatives (such as Azure CLI or cURL). The 'Related content' section highlights working from a Windows PC and Windows tools, with no equivalent Linux-focused guidance. Script actions are described as available via the Azure portal, HDInsight Windows PowerShell cmdlets, or .NET SDK, but do not mention Linux-native automation tools or shell scripting. There is a lack of Linux-specific examples or parity in tool recommendations, despite HDInsight clusters themselves being Linux-based.
Recommendations
  • Provide Linux shell/bash examples and workflows alongside PowerShell examples for cluster setup and customization.
  • Include references and links to Linux tools (such as Azure CLI, cURL, and shell scripting) before or alongside Windows tools.
  • Add a 'Work in Apache Hadoop on HDInsight from a Linux PC' section in 'Related content', mirroring the Windows PC guidance.
  • Clarify that script actions can be invoked via Azure CLI or REST API, not just Windows PowerShell or .NET SDK.
  • Ensure that all automation and scripting instructions are available for both Linux and Windows environments, with equal prominence.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-capacity-planning.md ...main/articles/hdinsight/hdinsight-capacity-planning.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates some Windows bias, notably by mentioning PowerShell scripting and Azure Automation as the primary example for cluster lifecycle management. Windows-centric tools and patterns (PowerShell, Azure Automation) are referenced without equivalent Linux alternatives. The order of presentation also places Windows tools before any mention of Linux-native approaches, and there are no Bash or Linux CLI examples provided for cluster provisioning or management.
Recommendations
  • Include Bash or Azure CLI examples for cluster provisioning and deletion alongside PowerShell scripts.
  • Mention Linux-native scheduling options (such as cron jobs) for automating cluster lifecycle tasks.
  • Ensure that references to scripting and automation tools are presented in a cross-platform manner, listing both Windows and Linux options.
  • Add explicit examples or links for Linux users to achieve the same tasks described for Windows/PowerShell.
  • Review screenshots and UI instructions to ensure they do not assume a Windows environment unless necessary.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-optimize-hive-query.md ...cles/hdinsight/hdinsight-hadoop-optimize-hive-query.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. While the core Hive optimization content is platform-neutral, the 'Scale out worker nodes' section lists Windows-centric tools (Azure portal, Azure PowerShell) before mentioning the generic 'command-line interface' and does not specify or provide examples for Linux tools (such as Azure CLI or SSH). There are no explicit Linux command examples, and screenshots are of the Azure portal, which is platform-agnostic but often associated with Windows usage. No Linux-specific patterns or shell commands are demonstrated, and PowerShell is mentioned by name while Linux equivalents are not.
Recommendations
  • Explicitly mention and provide examples using Azure CLI for Linux users when discussing cluster scaling and management.
  • When listing tools, avoid Windows-first ordering; present Azure CLI and PowerShell together, or in alphabetical order.
  • Include sample commands for both PowerShell and Azure CLI (bash) when demonstrating cluster configuration or scaling.
  • Clarify that Azure portal is accessible from any OS and is not Windows-specific.
  • Add a note or section on using SSH for Hive query submission or cluster management from Linux environments.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-create-linux-clusters-with-secure-transfer-storage.md ...oop-create-linux-clusters-with-secure-transfer-storage.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented as a primary method for managing secure transfer settings, with detailed references to PowerShell cmdlets and update instructions. The Azure portal (a GUI often associated with Windows users) is described before CLI methods. While Azure CLI is mentioned, there are no explicit Linux shell (bash) or script examples, nor references to Linux-native tools or workflows. The troubleshooting and configuration steps reference Ambari (which is cross-platform), but overall, Windows-centric tools and patterns are prioritized.
Recommendations
  • Provide explicit bash or shell script examples for Linux users, especially for storage account management.
  • Include instructions for using Azure CLI in Linux environments, such as running commands in bash.
  • Mention Linux-native tools or workflows where relevant (e.g., using curl or REST API calls from Linux).
  • Balance the order of presentation so that Azure CLI and Linux-friendly methods are described before or alongside PowerShell and portal instructions.
  • Clarify cross-platform compatibility for all tools and steps, and avoid assuming PowerShell is the default for all users.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-config-for-vscode.md ...main/articles/hdinsight/hdinsight-config-for-vscode.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the configuration examples for HDInsight Spark.NET, where paths and tool references are exclusively Windows-centric (e.g., C:\Program Files\7-Zip, D:\winutils, .exe files). There are no Linux or macOS equivalents provided, and the mention of 'windows OS only' further emphasizes the lack of cross-platform consideration. The order of presentation also places Windows paths first, with no alternative shown.
Recommendations
  • Add equivalent Linux/macOS configuration examples for Spark.NET settings, such as paths to 7z, HADOOP_HOME, JAVA_HOME, SCALA_HOME, and SPARK_HOME.
  • Explicitly mention platform differences and provide guidance for users on Linux/macOS (e.g., use /usr/bin/7z, /usr/local/hadoop, etc.).
  • Where a setting is Windows-only (e.g., winutils.exe), clarify what Linux/macOS users should do or if the setting is not required.
  • Ensure all examples and instructions are presented for both Windows and Linux/macOS, or at least link to platform-specific setup guides.
  • Consider reordering or grouping settings by platform to make it clear which apply to which OS.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-add-hive-libraries.md ...icles/hdinsight/hdinsight-hadoop-add-hive-libraries.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides both PowerShell (.ps1) and Bash (.sh) script examples for adding Hive libraries, but the PowerShell script is presented first and more prominently. The script location section only lists the PowerShell script URI, while the Bash script is referenced later in a table. Additionally, Azure Storage Explorer—a Windows-centric tool—is mentioned as the recommended utility for uploading files, with no mention of Linux alternatives. The instructions for cluster creation mention Azure PowerShell and the .NET SDK before Bash scripting, indicating a Windows-first approach.
Recommendations
  • Present Bash and PowerShell script examples together, or list Bash first for Linux parity.
  • Include Linux-native tools (e.g., azcopy, Azure CLI, or rclone) as alternatives to Azure Storage Explorer for uploading files.
  • Explicitly mention that both Windows and Linux users are supported, and provide step-by-step instructions for both platforms.
  • Balance references to Azure PowerShell/.NET SDK with equivalent Azure CLI examples.
  • Clarify which script is appropriate for which OS, and ensure both are equally accessible in the documentation.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-linux-information.md ...ticles/hdinsight/hdinsight-hadoop-linux-information.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Mention Windows First
Summary
The documentation is primarily focused on Linux-based HDInsight clusters and provides Linux-centric examples (curl, jq, bash, SSH). However, there is some evidence of Windows bias: Windows tools (PowerShell, Visual Studio) are mentioned as options for accessing Azure Data Lake Storage, and in some lists, Windows-specific tools (PowerShell, Visual Studio) are mentioned before Linux alternatives. There are no PowerShell or Windows command examples for cluster management, but the inclusion and ordering of Windows tools in the 'How do I access files from outside HDInsight' section shows some Windows-first bias.
Recommendations
  • Provide parity by listing Linux-native tools (e.g., azcopy, sftp, Linux file browsers) alongside or before Windows tools in sections about accessing data.
  • Include explicit Linux command examples for all tasks where PowerShell or Visual Studio are mentioned.
  • Clarify which tools are cross-platform and highlight Linux alternatives where Windows tools are referenced.
  • Consider reordering lists to mention Linux tools first when the context is Linux-based HDInsight.
  • Add more examples using Linux-native SDKs and utilities for common operations.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-migrate-dotnet-to-linux.md .../hdinsight/hdinsight-hadoop-migrate-dotnet-to-linux.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing Windows-based HDInsight clusters as the starting point, providing only Visual Studio (Windows tool) instructions for portability analysis and building, and lacking examples or instructions for equivalent Linux-native workflows (such as using Mono tools or Linux editors). The guidance assumes the user is migrating from Windows and continues to use Windows-centric tools, without offering parity for Linux-first development environments.
Recommendations
  • Provide instructions for running .NET Portability Analyzer or similar tooling on Linux (e.g., via command line, Mono tools, or VS Code).
  • Include examples of building and testing .NET applications using Linux-native tools (e.g., Mono's xbuild, msbuild on Linux, or dotnet CLI).
  • Offer guidance for auditing and modifying code using Linux editors (e.g., VS Code, Vim, Emacs) and command-line utilities.
  • Add explicit examples of file path handling and other platform-specific code changes, with Linux equivalents shown.
  • Reorder sections to present Linux-native workflows first or in parallel with Windows-based approaches.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-architecture.md ...in/articles/hdinsight/hdinsight-hadoop-architecture.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias in the 'Soft delete' section, where only a PowerShell cmdlet (Restore-AzDataLakeStoreDeletedItem) is provided for Azure Data Lake Storage Gen 1, with no equivalent Linux/Unix CLI or REST API example. The page references Windows-centric tooling and omits Linux-native commands or patterns for file restoration and management. No Linux shell examples (e.g., Bash, Azure CLI) are given, and the PowerShell example is presented as the sole method for undeleting files in Data Lake Storage Gen 1.
Recommendations
  • Provide equivalent Linux/Unix command-line examples, such as using Azure CLI or REST API calls, for file restoration and management tasks.
  • Include Bash shell examples alongside PowerShell to ensure cross-platform parity.
  • Explicitly mention platform-agnostic approaches (e.g., REST API) before or alongside Windows/PowerShell-specific tools.
  • Clarify when a tool or command is Windows-specific and offer alternatives for Linux/macOS users.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-manage-ambari-rest-api.md ...s/hdinsight/hdinsight-hadoop-manage-ambari-rest-api.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a Windows bias by frequently referencing Windows-specific tools and environments (PowerShell, Bash on Ubuntu on Windows, Windows Subsystem for Linux) and often listing Windows options before Linux equivalents. PowerShell examples are provided for every scenario, sometimes with additional detail, and Windows-specific installation guides are referenced. There is an assumption that users are on Windows, with Linux mentioned as an alternative or afterthought. Some examples and instructions (e.g., jq pathing) are tailored for Windows users, and Azure PowerShell cmdlets are promoted without Linux CLI equivalents.
Recommendations
  • Provide native Linux shell examples and instructions, not just Bash on Ubuntu on Windows.
  • List Linux/Unix options first or equally alongside Windows options.
  • Include Linux-native installation and usage instructions for required tools (e.g., jq).
  • Reference Linux command-line tools and environments (e.g., curl, bash) without Windows context when describing Linux clusters.
  • Offer Azure CLI equivalents for PowerShell cmdlets where possible.
  • Clarify that all examples work on Linux and macOS, not just Windows Subsystem for Linux.
  • Remove or balance references to Windows-specific environments unless strictly necessary.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-migrate-granular-access-cluster-configurations.md ...insight-migrate-granular-access-cluster-configurations.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits moderate Windows bias. It lists and describes Windows-centric tools (Visual Studio, PowerShell, Data Lake Tools for Visual Studio) and provides explicit PowerShell migration guidance, while Linux-native equivalents (such as Bash scripts or Linux-specific CLI workflows) are not mentioned. Windows tools are listed before cross-platform or Linux-friendly tools (e.g., VS Code, IntelliJ, Eclipse), and PowerShell is given a dedicated migration section, whereas Bash or Linux shell scripting is absent. The Azure CLI is covered, which is cross-platform, but no Linux-specific usage notes or examples are provided.
Recommendations
  • Add migration examples using Bash scripts and Linux shell environments for role assignment and cluster configuration.
  • Include guidance for Linux users on updating and using the Azure CLI, with explicit mention of Linux package managers and shell usage.
  • Provide parity for PowerShell cmdlet migration by offering equivalent Azure CLI or REST API examples for all operations.
  • List cross-platform and Linux-friendly tools (VS Code, IntelliJ, Eclipse) before Windows-only tools in affected scenarios.
  • Explicitly state platform compatibility for each tool and SDK, and link to Linux installation guides where available.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-templeton-webhcat-debug-errors.md ...ght/hdinsight-hadoop-templeton-webhcat-debug-errors.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-centric tools (Azure PowerShell, Data Lake Tools for Visual Studio) as primary clients for WebHCat, without mentioning Linux equivalents (such as curl, wget, or Linux CLI usage). No Linux or cross-platform command-line examples are provided, and Windows tools are mentioned first and exclusively.
Recommendations
  • Include examples of interacting with WebHCat using Linux command-line tools (e.g., curl, wget, or Python requests).
  • Mention Linux-based client options (such as Bash scripts, Linux CLI, or Hadoop command-line utilities) alongside Windows tools.
  • Provide parity in troubleshooting steps and configuration modification instructions for both Windows and Linux environments.
  • Avoid listing Windows tools first or exclusively; ensure cross-platform tools are given equal prominence.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-create-linux-clusters-arm-templates.md ...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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is mentioned before Azure CLI in deployment instructions, and Visual Studio (a Windows-centric tool) is highlighted for template editing and deployment. The .NET client library example links to a Windows-specific page. Linux alternatives are present (Azure CLI, VS Code), but Windows tools and patterns are often listed first or given more detail.
Recommendations
  • Present Azure CLI examples and instructions before PowerShell, as CLI is cross-platform.
  • Highlight VS Code (cross-platform) as the primary editor for templates, with Visual Studio as an alternative.
  • Include links to .NET client library examples for Linux or platform-neutral documentation, not just Windows.
  • Ensure that all deployment methods (CLI, PowerShell, REST API) have equal prominence and detail.
  • Explicitly mention Linux compatibility and provide Linux-specific troubleshooting or usage notes where relevant.
GitHub Create Pull Request
← Previous Page 13 of 35 Next →