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 226-250 of 867 flagged pages
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-09 00:34
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 clear Windows bias. All initial examples, file paths, and editor instructions use Windows conventions (e.g., Notepad, cmd, C:\ paths, DEL commands). The test environment is explicitly Windows 10, and PowerShell is given a dedicated, detailed section for uploading and running jobs, while Linux equivalents (such as Bash scripts or Linux editors) are not provided. There is no guidance for Linux users on how to adapt commands, file operations, or editor usage, and Linux tools are only mentioned in passing (e.g., SSH client).
Recommendations
  • Provide parallel Linux examples for all file operations, using Bash commands (e.g., mkdir, rm, nano/vim for editing files).
  • Include Linux file paths and conventions alongside Windows ones (e.g., ~/HDI/hbaseapp).
  • Offer instructions for running Maven and SCP commands in Linux environments, including terminal usage.
  • Add a section for uploading and running jobs using Bash scripts or Azure CLI, to match the detail given to PowerShell.
  • Mention cross-platform editors (e.g., VS Code, nano, vim) instead of only Notepad.
  • Clearly indicate which commands are OS-specific and provide adaptation notes for users on Linux/macOS.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-tutorial-get-started-linux.md ...sight/hbase/apache-hbase-tutorial-get-started-linux.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates some Windows bias, particularly in the prerequisites section, where Bash usage is described specifically in the context of Windows 10 and Windows Subsystem for Linux (WSL) is recommended. Windows tools and patterns (PowerShell's Invoke-RestMethod, Windows Command prompt) are mentioned before their Linux equivalents. There is also a reference to using Bash on Windows, rather than directly on Linux or macOS, and alternative Windows-specific tools are suggested. However, most command examples use Bash and SSH, which are cross-platform, and the cluster itself is Linux-based.
Recommendations
  • Present Linux and macOS usage equally alongside Windows, not as secondary options.
  • In prerequisites, mention Bash and SSH as available natively on Linux and macOS before referencing Windows/WSL.
  • Provide explicit Linux/macOS command examples where Windows alternatives are given (e.g., for REST API calls, clarify how to use curl on Linux/macOS).
  • Avoid suggesting Windows tools (PowerShell, Command prompt) before Unix/Linux tools; list all platforms equally.
  • Consider a dedicated section for platform-specific instructions, ensuring Linux/macOS parity.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/troubleshoot-rest-api.md ...main/articles/hdinsight/hbase/troubleshoot-rest-api.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 as the source of the security issue, which is a Windows-specific web server technology. There is no mention of Linux equivalents (such as Apache or Nginx), nor are troubleshooting steps or examples provided for Linux-based HDInsight clusters. The mitigation steps and cause analysis focus on Windows-centric infrastructure and do not address Linux scenarios, despite HDInsight supporting both Windows and Linux clusters.
Recommendations
  • Explicitly mention whether the issue applies to both Windows and Linux HDInsight clusters, or only to Windows (IIS Gateway).
  • If Linux clusters are affected, provide details about the equivalent gateway or REST server configuration and troubleshooting steps for Linux (e.g., Apache, Nginx).
  • Include examples and mitigation steps for Linux environments, such as how to bypass the REST server or configure direct RPC access on Linux worker nodes.
  • Clarify the role of IIS Gateway and whether Linux clusters use a different gateway technology, and how that impacts REST API usage.
  • Add troubleshooting steps and examples for both Windows and Linux users to ensure parity and inclusivity.
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-09 00:34
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 towards Windows environments by providing only PowerShell commands for package installation, referencing Windows-specific tools and patterns (e.g., PowerShell client GUID, %HBASE_HOME% environment variable), and omitting equivalent Linux/bash examples. Windows-centric terminology and instructions appear before or instead of Linux alternatives, making it less accessible for Linux users.
Recommendations
  • Provide equivalent Linux/bash commands for installing NuGet packages (e.g., using dotnet CLI or mono on Linux).
  • Include Linux-specific instructions and environment variables (e.g., $HBASE_HOME instead of %HBASE_HOME%).
  • Add bash shell examples for cluster management tasks alongside PowerShell examples.
  • Clarify cross-platform compatibility of the .NET SDK and explicitly mention how to use it on Linux/macOS.
  • Avoid referencing Windows-only tools or GUIDs unless absolutely necessary, and provide alternatives for other platforms.
  • Ensure that any command-line instructions are presented for both Windows and Linux, or use platform-agnostic approaches where possible.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates Windows bias primarily by referencing PowerShell scripts as the example for cluster provisioning and deletion automation, and by mentioning Azure Automation (a Windows-centric tool) as the scheduling solution. There are no equivalent Linux shell script or cron job examples, and Windows/PowerShell approaches are mentioned first and exclusively in the automation context.
Recommendations
  • Provide Linux shell script examples for cluster provisioning and deletion alongside PowerShell scripts.
  • Mention and link to Linux-native scheduling options such as cron or systemd timers in addition to Azure Automation.
  • Ensure that automation and scripting sections include both Windows and Linux approaches, with parity in detail and prominence.
  • Review other sections for implicit Windows-first assumptions and add explicit Linux guidance where applicable.
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-09 00:34
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 in several ways. Configuration examples for HDInsight Spark.NET settings (such as 7z, HADOOP_HOME, JAVA_HOME, SCALA_HOME, SPARK_HOME) exclusively use Windows-style paths and tools (e.g., C:\Program Files\7-Zip, D:\winutils, etc.), and explicitly mention 'windows OS only' for winutils.exe. There are no Linux equivalents or examples provided for these settings, nor any mention of how to configure these paths on Linux or macOS. The documentation also lists Windows paths first and does not provide parity for other platforms.
Recommendations
  • Add equivalent configuration examples for Linux and macOS, using appropriate paths and tools (e.g., /usr/bin/7z, /usr/local/hadoop, JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/).
  • Clarify which settings are platform-specific and provide guidance for each supported OS.
  • Where Windows-only tools are referenced (e.g., winutils.exe), explain their necessity and provide alternatives or workarounds for Linux/macOS users.
  • Ensure that documentation does not assume Windows as the default platform; present cross-platform examples side-by-side or in separate sections.
  • Review all configuration properties for implicit Windows assumptions and update descriptions to be inclusive of other platforms.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. The primary script action for adding Hive libraries is provided as a PowerShell (.ps1) script, with the Bash (.sh) script URI mentioned later and only in the context of cluster creation steps. Windows tools such as Azure Storage Explorer are referenced for uploading files, and instructions for creating storage accounts default to the Azure portal, which is more commonly used on Windows. The PowerShell script is listed before the Bash script, and there is no explicit Linux CLI example for uploading files or managing storage.
Recommendations
  • Provide Linux CLI examples for uploading files to Azure Blob Storage (e.g., using azcopy or Azure CLI).
  • List Bash script URIs and Linux instructions before or alongside PowerShell equivalents to avoid Windows-first ordering.
  • Mention cross-platform tools (e.g., Azure CLI, azcopy) for storage management and file uploads.
  • Clarify which script to use for which OS, and ensure parity in instructions for both Windows and Linux users.
  • Include explicit Linux-focused steps for all major actions, not just cluster provisioning.
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-09 00:34
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 .NET (C#) examples, referencing NuGet and PowerShell commands, and omitting any Linux-specific or cross-platform guidance. The instructions and tooling assume a Windows development environment, with no mention of Linux equivalents (such as .NET CLI, Bash, or cross-platform authentication patterns). There are no examples or notes for developing or running the application on Linux systems.
Recommendations
  • Add Linux-specific instructions for setting up the development environment, including .NET SDK installation and usage of the dotnet CLI.
  • Provide code examples and package installation steps using cross-platform tools (e.g., 'dotnet add package' instead of 'Install-Package').
  • Include guidance for authenticating and running the application on Linux, such as using environment variables for secrets and running the app from Bash.
  • Reference cross-platform editors (e.g., VS Code) and clarify that the instructions apply to both Windows and Linux.
  • If PowerShell is mentioned, also provide Bash or shell script equivalents for relevant steps.
  • Explicitly state platform compatibility and test the documented process on Linux.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-create-linux-clusters-adf.md ...dinsight/hdinsight-hadoop-create-linux-clusters-adf.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The tutorial demonstrates a strong Windows bias by exclusively providing PowerShell scripts for all command-line tasks, such as resource creation and file copying. There are no equivalent Bash or CLI examples for Linux/macOS users. The prerequisites and step-by-step instructions assume the use of PowerShell, and the workflow is presented with Windows tooling first and only. This limits accessibility for users on Linux or macOS platforms.
Recommendations
  • Provide equivalent Bash shell scripts for all PowerShell examples, using Azure CLI commands where possible.
  • Explicitly mention that the tutorial can be followed on Linux/macOS and provide platform-specific instructions or selectors.
  • Add a section in prerequisites for installing Azure CLI and using Bash, alongside PowerShell.
  • Where UI steps reference objects created by scripts, clarify how Linux users can create and verify these resources.
  • Ensure all code blocks and instructions have both PowerShell and Bash/Azure CLI versions, or use platform selectors.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page shows moderate Windows bias. PowerShell is mentioned before Azure CLI as a deployment method, 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 mentioned (e.g., Azure CLI, VS Code), but Windows tools and patterns are often presented first or exclusively.
Recommendations
  • Present Azure CLI examples and links before or alongside PowerShell to emphasize cross-platform parity.
  • Include explicit Linux workflow examples, such as using Bash scripts or Linux-native editors (e.g., Vim, nano) for template editing.
  • Highlight VS Code as the primary cross-platform editor, and clarify that Visual Studio is Windows-only, suggesting alternatives for Linux users.
  • Replace or supplement Windows/.NET-specific example links with cross-platform or Linux-oriented equivalents.
  • Add a section summarizing Linux-friendly deployment options and best practices.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. PowerShell is given a dedicated section for managing secure transfer settings, and is mentioned before Azure CLI, which is more commonly used on Linux. The PowerShell cmdlet is described in detail, while the Azure CLI command is presented afterwards. There are no explicit Linux shell examples (e.g., Bash), and no mention of Linux-specific tools or workflows. The troubleshooting steps reference Ambari, which is cross-platform, but the overall pattern prioritizes Windows-centric tools and ordering.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is platform-neutral and more common on Linux.
  • Include Bash shell examples for managing storage accounts, especially for Linux users.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows.
  • Add a note or section on using REST API or SDKs from Linux environments.
  • Ensure parity in troubleshooting steps by referencing Linux command-line tools where applicable.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is generally focused on Linux-based HDInsight clusters and uses Linux-native tools (curl, jq, SSH, Bash scripts) for most examples. However, there is evidence of Windows bias in several areas: PowerShell and Visual Studio tools are mentioned for Azure Data Lake Storage access, and Windows-specific tools (PowerShell, Visual Studio) are listed before or alongside Linux alternatives. There are missing Linux-specific examples for some tasks (e.g., accessing Data Lake Storage Gen1), and Windows-centric SDKs and tools are sometimes highlighted without Linux parity.
Recommendations
  • Provide explicit Linux command-line examples (e.g., using curl, jq, or Azure CLI) for all tasks where PowerShell or Visual Studio are mentioned.
  • List Linux-native tools and SDKs before Windows-specific ones, or group them by platform for clarity.
  • Where PowerShell is referenced, include equivalent Bash or shell script examples.
  • Highlight cross-platform SDKs and utilities (e.g., Python, Java, Node.js) and clarify their usage on Linux.
  • Add links or documentation for Linux alternatives to Windows-only tools (e.g., Data Lake Explorer for Linux, CLI-based management).
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a 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 Linux or cross-platform CLI alternatives. There are no Bash, Azure CLI, or REST API examples for Linux users, and the only explicit tool mentioned for restoring deleted items is PowerShell, which is traditionally associated with Windows environments. The overall documentation lacks parity in examples and instructions for Linux users.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for restoring deleted items in Azure Data Lake Storage Gen 1.
  • Include REST API instructions or references for all storage operations, not just for blobs.
  • Clearly indicate cross-platform tools and commands where possible, and avoid assuming PowerShell as the default.
  • Add notes or links to Linux-specific documentation or usage patterns for HDInsight and Hadoop storage operations.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-customize-cluster-bootstrap.md ...nsight/hdinsight-hadoop-customize-cluster-bootstrap.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 strong Windows bias by providing detailed PowerShell examples and a full PowerShell script in the appendix, while omitting equivalent Linux/bash examples. The use of Windows-centric tools (PowerShell, .NET SDK) is emphasized, and the order of presentation puts Windows methods first. There is only a passing reference to Linux-based customization via Script Actions, with no concrete examples or guidance for Linux users.
Recommendations
  • Add equivalent bash or shell script examples for customizing HDInsight clusters using bootstrap on Linux.
  • Provide guidance and code samples for using Azure CLI, which is cross-platform, alongside PowerShell.
  • Include links and examples for Linux-based tools and workflows, such as using Script Actions directly in the main content, not just in 'See also'.
  • Reorder sections to present cross-platform or Linux-native methods (e.g., ARM templates, Azure CLI, Script Actions) before or alongside Windows-specific methods.
  • Explicitly state which methods are platform-agnostic and which are Windows-specific, helping users choose the right approach for their environment.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: Windows and PowerShell are mentioned first or exclusively in prerequisites, examples, and tool recommendations. Bash is described as being used 'on Windows 10' via WSL, and PowerShell is repeatedly presented as an alternative to Bash, sometimes with more detail. Windows-specific installation guides and tools (e.g., Windows Subsystem for Linux, PowerShell, Windows paths for jq) are referenced before or instead of native Linux equivalents. There is little direct guidance for native Linux users, and the workflow assumes a Windows-centric environment.
Recommendations
  • Add explicit instructions and examples for native Linux environments, not just Bash on Windows.
  • Present Linux-native prerequisites (e.g., installing jq, using Bash on Ubuntu) before or alongside Windows/WSL/PowerShell instructions.
  • Avoid referencing Windows-specific installation guides as the primary method for accessing Bash; link to general Bash or Linux shell documentation.
  • Ensure parity in detail and troubleshooting for both Linux and Windows users.
  • Where PowerShell is used, provide equivalent Linux shell scripting examples (e.g., using curl, jq, and bash loops) and clarify any differences.
  • Remove or de-emphasize Windows-specific paths and tools unless strictly necessary, and always provide Linux alternatives.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation provides a balanced overview of SSH usage across platforms, but there is a slight Windows bias. Windows-specific SSH client options (OpenSSH, Bash on Ubuntu on Windows, Azure Cloud Shell, Git, PuTTY, MobaXterm) are listed in detail, while Linux/Unix/macOS are mentioned generically as having ssh/scp by default. Azure PowerShell is featured prominently in cluster creation examples, with parameters and cmdlets described before Azure CLI equivalents. Windows tools and patterns (PowerShell, graphical clients) are given more explanation and visibility than Linux-native alternatives.
Recommendations
  • Provide equal detail for Linux/Unix/macOS SSH client usage, including installation steps for less common distributions.
  • List Azure CLI examples before or alongside Azure PowerShell examples to avoid Windows-first ordering.
  • Include Linux-native graphical SSH clients (e.g., GNOME Terminal, Konsole, Remmina) in the SSH client section.
  • Add explicit Linux shell commands for cluster creation and management, not just Azure CLI.
  • Clarify that most examples are cross-platform and highlight any platform-specific differences.
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-09 00:34
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. When discussing cluster scaling, it lists Azure portal, Azure PowerShell, and command-line interface as options, but only visually illustrates the Azure portal (a GUI tool most commonly used on Windows) and mentions PowerShell (a Windows-centric tool) before CLI, without specifying or providing examples for Linux shell usage. There are no explicit Linux shell or script examples, nor are Linux-specific tools or patterns mentioned. The page does note that 'Linux-based HDInsight clusters have Tez enabled by default', but otherwise does not provide Linux parity in tooling or examples.
Recommendations
  • Include explicit examples using Azure CLI commands for scaling and management, with sample Linux shell usage.
  • When listing management tools, mention Azure CLI and Bash before or alongside Azure PowerShell to avoid Windows-first ordering.
  • Add screenshots or instructions for Linux terminal usage where appropriate, not just Azure portal GUI.
  • Clarify that HDInsight clusters are Linux-based by default, and provide links or tips for Linux users.
  • Where PowerShell is mentioned, also provide equivalent Bash or shell script examples.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for enabling Azure Monitor logs on HDInsight clusters. However, PowerShell instructions are consistently presented before CLI examples, and PowerShell is a Windows-centric tool. There is frequent mention of the Az PowerShell module, and no Linux shell-specific examples (e.g., Bash scripts, native Linux tools) are provided beyond Azure CLI. The portal instructions also implicitly assume a graphical interface, which is more common on Windows. There are no explicit Linux command-line or automation examples outside of Azure CLI, and no mention of Linux-specific patterns for cluster management or monitoring.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI first to better reflect cross-platform usage.
  • Explicitly mention that Azure CLI works natively on Linux/macOS and provide Bash-specific usage notes where relevant.
  • Add Linux-native command examples for cluster management tasks where possible (e.g., using SSH, Bash scripts, or Linux utilities for agent/version checks).
  • Clarify that the Azure portal is accessible from any OS/browser, and provide guidance for headless or non-GUI environments.
  • Where PowerShell is referenced, note that it is available on Linux/macOS, but CLI is often preferred for cross-platform automation.
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-09 00:34
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 mild Windows bias. It references Azure PowerShell and Windows PowerShell cmdlets as primary command-line options for cluster setup and customization, often listing them alongside or before Linux-friendly alternatives like Azure CLI and cURL. The 'Related content' section specifically highlights working from a Windows PC, and script actions are described as available via Windows PowerShell and .NET SDK, with no mention of Bash or Linux-native scripting. There is a lack of explicit Linux command-line examples or guidance, despite the clusters themselves being Linux-based.
Recommendations
  • Include Linux/Bash command-line examples for cluster setup and management, especially for script actions and customization.
  • Mention and prioritize Azure CLI and cURL usage before or alongside PowerShell in tables and instructions.
  • Add a 'Work in Apache Hadoop on HDInsight from a Linux PC' link to the Related content section.
  • Clarify that script actions and cluster management can be performed from Linux environments, not just Windows/PowerShell.
  • Where PowerShell is referenced, provide equivalent Azure CLI or Bash examples for parity.
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-09 00:34
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 Azure PowerShell and Data Lake Tools for Visual Studio as primary client-side tools for interacting with WebHCat, both of which are Windows-centric. There are no Linux-specific tools or examples mentioned, nor is there guidance for Linux command-line usage or integration. The documentation implicitly prioritizes Windows environments and omits parity for Linux users.
Recommendations
  • Include references to Linux-native tools (e.g., curl, wget, or Linux shell scripts) for interacting with WebHCat.
  • Provide example commands for submitting jobs and querying status using Linux command-line utilities.
  • Mention cross-platform alternatives to Azure PowerShell and Visual Studio, such as Azure CLI or REST API usage from Bash.
  • Ensure troubleshooting steps and configuration instructions are applicable to both Windows and Linux environments.
  • Add a section highlighting how Linux users can access and use WebHCat, including authentication and job management.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-log-management.md ...ob/main/articles/hdinsight/hdinsight-log-management.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits several Windows-centric biases. PowerShell is repeatedly mentioned as a primary scripting and automation tool for log management, with references to Azure PowerShell cmdlets and scripting log archiving in PowerShell. Windows-based tools (Visual Studio, Power Query for Excel, Azure Storage Explorer) are listed as examples for log analysis and management, often before or instead of Linux-native alternatives. While some Linux tools and workflows (SSH, logrotate, Ambari UI) are mentioned, there is a lack of parity in example scripts and tool recommendations for Linux users. Many sections provide Windows/PowerShell solutions without equivalent Bash or Linux CLI examples, and Windows tools are often listed first or exclusively.
Recommendations
  • Provide equivalent Bash or Linux shell script examples for all PowerShell scripts and automation tasks.
  • List Linux-native tools (e.g., grep, awk, sed, rsync, cron, logrotate, Linux CLI for Azure) alongside or before Windows tools for log management and analysis.
  • Include examples using Azure CLI and Bash for log archiving and management, not just PowerShell.
  • Highlight cross-platform tools and workflows, ensuring that Linux users have clear, actionable guidance.
  • Ensure that third-party tool recommendations include Linux-compatible options and that their usage is demonstrated.
  • Balance the order of tool presentation so that Linux and Windows approaches are given equal prominence.
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-09 00:34
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 a Windows bias by prominently featuring Windows-centric tools (Visual Studio, PowerShell), providing PowerShell migration instructions without equivalent Bash or Linux shell examples, and listing Windows tools before cross-platform or Linux alternatives. There are no explicit Linux-specific instructions or examples, and PowerShell is the only command-line scripting language shown for migration steps, with no Bash/Azure CLI script equivalents for Linux users.
Recommendations
  • Provide equivalent Bash or shell script examples for all PowerShell instructions, especially for migration steps and role assignments.
  • Include explicit references and instructions for using Azure CLI on Linux/macOS, not just in the context of role assignment but also for cluster configuration management.
  • Add parity for Linux tools (e.g., VS Code on Linux, Eclipse on Linux) and clarify cross-platform support for SDKs and toolchains.
  • Reorder tool and SDK sections to avoid listing Windows tools first; group by platform or present cross-platform tools before platform-specific ones.
  • Add troubleshooting and update instructions for Linux users, including package management and installation steps.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-plan-virtual-network-deployment.md ...hdinsight/hdinsight-plan-virtual-network-deployment.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. Windows-centric tools and patterns (Azure PowerShell) are consistently presented before their Linux equivalents (Azure CLI), and PowerShell examples are given equal or greater prominence. The use of Azure PowerShell is referenced first in command examples and troubleshooting, and the documentation does not provide Linux shell-specific guidance (e.g., Bash scripting) or mention Linux-native tools for network inspection. There is also a lack of explicit parity in instructions for Linux users, with no mention of OS-specific considerations for cluster creation or management.
Recommendations
  • Present Azure CLI (cross-platform) examples before or alongside Azure PowerShell examples to avoid Windows-first ordering.
  • Include Linux/Bash-native command examples for network inspection and troubleshooting (e.g., using curl, dig, or ip tools).
  • Add explicit notes or sections for Linux users, clarifying any OS-specific steps or differences in HDInsight cluster creation and management.
  • Reference Linux-native tools and patterns (such as SSH, Bash scripting, or Linux firewall management) where appropriate.
  • Ensure that troubleshooting and configuration guidance is equally accessible and detailed for both Windows and Linux environments.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-private-link.md ...blob/main/articles/hdinsight/hdinsight-private-link.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias in several ways: VM deployment instructions and examples exclusively use Windows images (Windows 10 Pro), RDP is the only inbound port mentioned, and the VM licensing checkbox is specific to Windows. The instructions for testing connectivity reference Windows tools (web browser, command prompt) and do not mention Linux alternatives. PowerShell is referenced before Azure CLI in cluster creation examples. There are no explicit Linux VM deployment instructions or examples, nor are SSH or Linux-native tools prioritized or equally presented.
Recommendations
  • Include Linux VM deployment instructions and examples (e.g., Ubuntu, CentOS) alongside or before Windows examples.
  • Mention SSH as a primary access method for both Ambari and cluster connectivity, and provide Linux command-line examples.
  • When listing cluster creation methods, present Azure CLI and ARM template examples before or alongside PowerShell, and ensure parity in detail.
  • For connectivity testing, describe how to use Linux terminals and browsers, and mention relevant Linux tools (e.g., curl, wget, OpenSSH).
  • Avoid Windows-specific licensing steps unless also providing Linux equivalents.
  • Ensure all portal screenshots and configuration tables are OS-agnostic or provide both Windows and Linux perspectives.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-upload-data.md .../blob/main/articles/hdinsight/hdinsight-upload-data.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. Windows-specific tools (Azure PowerShell, Cerulea, CloudXplorer, CloudBerry Explorer) are listed, some without Linux equivalents. Azure PowerShell is presented as a primary utility for uploading data, but no Linux shell or Bash examples are given. The graphical clients table is heavily weighted toward Windows-only applications, with fewer cross-platform or Linux-native options. While the Hadoop command line example is Linux-friendly, there are no Bash/Azure CLI code samples for Linux users, and PowerShell is mentioned in the initial tool list without parity for Linux shell scripts.
Recommendations
  • Add explicit Bash/Azure CLI examples for uploading data to Azure Storage, alongside PowerShell examples.
  • Ensure that Linux-compatible tools are listed first or equally with Windows tools in tables and lists.
  • Expand the graphical clients table to include more Linux-native or cross-platform applications.
  • Provide sample commands for Linux users (e.g., using AzCopy, Azure CLI) in addition to PowerShell.
  • Clarify in the documentation when a tool is Windows-only and suggest Linux alternatives where possible.
GitHub Create Pull Request
← Previous Page 10 of 35 Next →