Hdinsight

878
Total Pages
777
Linux-Friendly Pages
101
Pages with Bias
11.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

200 issues found
Showing 101-125 of 200 flagged pages
Hdinsight InvalidNetworkConfigurationErrorCode error - Azure HDInsight ...idnetworkconfigurationerrorcode-cluster-creation-fails.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page is generally cross-platform, with most troubleshooting steps using SSH and Linux commands (hostname, nslookup, dig). However, there is a notable Windows bias in the section discussing the deprecated 'EnableVmProtection' parameter, which references PowerShell and Azure Runbooks without mentioning Linux CLI or REST API equivalents. Additionally, VM deployment instructions mention both Linux and Windows, but PowerShell is referenced first and exclusively for network configuration validation, and the Az PowerShell SDK is linked without CLI parity.
Recommendations
  • Include Azure CLI and REST API equivalents for network configuration validation and troubleshooting, especially where PowerShell is referenced.
  • When mentioning VM deployment for DNS forwarding, provide parallel instructions for both Linux and Windows, and avoid listing Windows first unless contextually justified.
  • Add explicit Linux/macOS command examples for any Azure resource management steps currently shown only in PowerShell.
  • Ensure all troubleshooting steps that reference PowerShell or Windows tools also mention or link to Linux/macOS alternatives.
GitHub Create Pull Request
Hdinsight What is Apache Hive and HiveQL - Azure HDInsight ...b/main/articles/hdinsight/hadoop/hdinsight-use-hive.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation lists several client tools for interacting with Hive on HDInsight, including Windows-specific options like Visual Studio and PowerShell. Windows tools are mentioned explicitly and sometimes before Linux equivalents. There are dedicated sections for Windows PowerShell and Visual Studio, while Linux/macOS alternatives (VS Code, Beeline, REST API) are present but not always highlighted equally. Some integration examples (SSIS) are Windows-centric. However, most core Hive usage and examples are platform-neutral.
Recommendations
  • Ensure Linux/macOS tools (e.g., Beeline, REST API, VS Code) are listed before or alongside Windows tools in tables and lists.
  • Provide equivalent Linux/macOS command-line examples or links where Windows PowerShell is referenced.
  • Add more explicit guidance for Linux/macOS users, especially for scheduling and integration workflows.
  • Balance integration examples by mentioning Linux-native orchestration tools (e.g., cron, Airflow) alongside SSIS.
  • Where possible, avoid Windows-only terminology or clarify platform support for each tool.
GitHub Create Pull Request
Hdinsight Run Apache Sqoop jobs with Azure HDInsight (Apache Hadoop) .../main/articles/hdinsight/hadoop/hdinsight-use-sqoop.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. It emphasizes using Azure PowerShell from a workstation to run Sqoop jobs, with Windows-specific tools and patterns (PowerShell, .NET SDK) mentioned before or instead of Linux equivalents. There is no direct Linux command-line or SSH example in the main walkthrough, and Linux limitations are listed without corresponding Windows caveats. The guidance for running Sqoop jobs prioritizes Windows tooling, and the main workflow assumes a Windows environment.
Recommendations
  • Add explicit Linux/macOS command-line examples for running Sqoop jobs via SSH, including step-by-step instructions.
  • Present Linux/SSH and Windows/PowerShell methods side-by-side or in parallel sections, rather than prioritizing Windows tools.
  • Include Linux-specific troubleshooting, limitations, and workarounds where relevant.
  • Clarify which steps are OS-agnostic and which require platform-specific instructions.
  • Link to Linux/macOS walkthroughs more prominently, not just in the 'Next steps' section.
GitHub Create Pull Request
Hdinsight Submit Apache Hadoop jobs in HDInsight ...t/hadoop/submit-apache-hadoop-jobs-programmatically.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation lists three main methods for submitting Hadoop jobs: .NET SDK, curl, and PowerShell. PowerShell is a Windows-centric tool and is presented as a primary option alongside .NET SDK (also Windows-focused) and curl. The examples and resource links for PowerShell and .NET SDK are given equal prominence to curl, but there is no mention of Linux-native tools (such as Bash scripts, Python SDKs, or CLI alternatives) or macOS-specific guidance. The ordering (.NET SDK, curl, PowerShell) also places Windows technologies first.
Recommendations
  • Add explicit Linux/macOS guidance, such as using Bash scripts or Python SDKs for job submission.
  • Include examples for submitting jobs using Azure CLI, which is cross-platform.
  • Clarify which tools are cross-platform and which are Windows-only.
  • Consider reordering examples to start with cross-platform tools (e.g., curl, CLI) before Windows-specific options.
  • Add notes or links for Linux/macOS users to equivalent documentation.
GitHub Create Pull Request
Hdinsight Use Apache Maven to build a Java HBase client for Azure HDInsight ...hdinsight/hbase/apache-hbase-build-java-maven-linux.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 notable Windows bias. All command-line examples use Windows Command Prompt syntax (e.g., `cmd` commands like `IF NOT EXIST`, `DEL`, and backslash paths), and file editing is done with Notepad, a Windows-only tool. The test environment is explicitly Windows 10, and PowerShell is featured heavily with a dedicated section and custom modules, while Linux/macOS equivalents (e.g., Bash scripts, Vim/Nano editing, Unix file paths) are absent. Linux users are expected to 'modify accordingly', but no concrete guidance or examples are provided for non-Windows platforms.
Recommendations
  • Provide parallel Linux/macOS examples for all command-line operations, using Bash syntax, forward-slash paths, and common editors like Vim, Nano, or VS Code.
  • Include a 'Test environment' note for Linux/macOS, with example commands for directory creation, file deletion, and editing.
  • Offer a Bash script or CLI workflow for uploading JARs and running jobs, similar to the PowerShell module.
  • List Linux/macOS commands before or alongside Windows commands to avoid 'windows_first' bias.
  • Explicitly mention and demonstrate how to use Maven, SSH, and SCP on Linux/macOS.
  • Replace or supplement Notepad instructions with cross-platform editors.
GitHub Create Pull Request
Hdinsight Manage Apache Hadoop clusters in HDInsight with .NET SDK - Azure ...icles/hdinsight/hdinsight-administer-use-dotnet-sdk.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Package installation instructions are provided only in PowerShell, with no Linux/macOS alternatives (e.g., dotnet CLI or NuGet CLI). The authentication example references the PowerShell client GUID and uses Windows-centric terminology. In the HBase section, balancing instructions use Windows command prompt syntax and environment variables, without Linux shell equivalents. No Linux/macOS-specific code samples or guidance are provided, and Windows tools/patterns are mentioned first or exclusively.
Recommendations
  • Add Linux/macOS equivalents for package installation, such as 'dotnet add package' or NuGet CLI commands.
  • Provide shell/bash command examples alongside Windows command prompt instructions, especially for HBase balancing.
  • Clarify that the .NET SDK and code samples are cross-platform, and note any OS-specific requirements or caveats.
  • Avoid referencing Windows-specific tools (e.g., PowerShell client GUID) without explaining their relevance for non-Windows users.
  • Where possible, present examples for both platforms or use platform-neutral instructions.
GitHub Create Pull Request
Hdinsight Install third-party applications on Azure HDInsight ...icles/hdinsight/hdinsight-apps-install-applications.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily by referencing Azure PowerShell and Azure Classic CLI for template deployment, without mentioning Linux-native equivalents (such as Azure CLI or Bash scripting) or providing Linux/macOS-specific instructions. The examples and instructions focus on using the Azure portal (web-based, cross-platform), but when mentioning command-line automation, Windows tools are listed first and exclusively. There are no explicit Linux/macOS command-line examples, and PowerShell is referenced without parity for Bash or Azure CLI. This may create friction for Linux/macOS users who prefer or require native tooling.
Recommendations
  • Include Azure CLI examples alongside or before Azure PowerShell, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
  • Explicitly mention Bash scripting or provide sample Bash commands for template deployment.
  • Clarify that the Azure portal is web-based and accessible from any OS, but also provide parity in automation instructions for Linux/macOS environments.
  • Add references or links to Linux/macOS-specific documentation where relevant (e.g., using SSH, Bash, Azure CLI).
  • Avoid listing Windows tools (PowerShell) before cross-platform alternatives unless there is a technical reason.
GitHub Create Pull Request
Hdinsight Authorize users for Ambari Views - Azure HDInsight ...icles/hdinsight/hdinsight-authorize-users-to-ambari.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides three methods for adding users to Ambari: via the portal, PowerShell, and curl/bash. The PowerShell example is given in full detail and appears before the curl/bash example, which is described as requiring 'slight modifications' for Windows. The PowerShell script uses Windows-specific tooling (Invoke-WebRequest, Start-Sleep, etc.), and there is no equivalent Linux shell script or REST API example using common Linux tools (e.g., wget, httpie). The curl/bash example is present, but is positioned after the PowerShell example and is described as requiring modifications for Windows, implying a Windows-first approach. There are no macOS-specific notes or parity checks.
Recommendations
  • Present Linux/bash/curl examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Provide a full REST API example using generic tools (curl, wget, httpie) with explicit instructions for Linux/macOS users.
  • Clarify that the PowerShell example is for Windows and the curl/bash example is for Linux/macOS, and ensure both are equally detailed.
  • Add notes or examples for macOS users where relevant.
  • Avoid language that positions Windows tools as the default or primary method.
GitHub Create Pull Request
Hdinsight Non-interactive authentication .NET application - Azure HDInsight ...ate-non-interactive-authentication-dotnet-applications.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively providing C#/.NET examples, referencing NuGet (a Windows-centric package manager), and omitting any mention of Linux/macOS development workflows, tools, or alternative authentication methods. There are no examples or instructions for running .NET applications on Linux/macOS, nor are cross-platform considerations discussed.
Recommendations
  • Include instructions and examples for developing and running .NET applications on Linux/macOS, such as using .NET Core/SDK commands.
  • Mention cross-platform package management (e.g., dotnet CLI) alongside NuGet/Install-Package.
  • Provide guidance for authenticating and managing Azure resources from Linux/macOS terminals, including CLI or REST API alternatives.
  • Explicitly state that the .NET SDK and authentication flows work on Linux/macOS, and link to relevant cross-platform documentation.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., SecureString limitations, environment variables for secrets).
GitHub Create Pull Request
Hdinsight Azure HDInsight configuration settings reference ...main/articles/hdinsight/hdinsight-config-for-vscode.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page lists several configuration properties with Windows-specific paths and tools (e.g., 7z.exe, winutils.exe, JAVA_HOME, SCALA_HOME, SPARK_HOME) using Windows-style paths and explicitly notes 'windows OS only' for winutils.exe. There are no Linux/macOS equivalents or examples provided, nor any mention of how to configure these settings on non-Windows platforms. Windows paths and tools are shown first and exclusively.
Recommendations
  • Add equivalent Linux/macOS configuration examples for properties like 7z, JAVA_HOME, SCALA_HOME, SPARK_HOME, using typical Unix-style paths (e.g., /usr/bin/7z, /usr/lib/jvm/java-8-openjdk-amd64/).
  • Clarify which settings are Windows-only and provide alternatives or guidance for Linux/macOS users (e.g., note that winutils.exe is not required on Linux).
  • Where possible, provide cross-platform instructions or note platform-specific differences in the configuration table.
  • Add a section or callout for Linux/macOS users to ensure parity and reduce confusion.
GitHub Create Pull Request
Hdinsight Add additional Azure Storage accounts to HDInsight ...ain/articles/hdinsight/hdinsight-hadoop-add-storage.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 account addition, but does not offer an equivalent Linux/macOS CLI or script example. The PowerShell method is presented first and in more detail, while Linux users are only given a GUI-based verification via Apache Ambari, with no command-line alternative. This creates friction for Linux/macOS users who may prefer or require CLI-based verification.
Recommendations
  • Add an Azure CLI or Bash example for verifying the storage account addition, showing how to query cluster configuration from Linux/macOS.
  • Present verification methods for both Windows and Linux/macOS users side-by-side, or alternate which is shown first.
  • Clarify which methods are cross-platform and which are Windows-specific.
  • Consider including sample Bash scripts or commands that parse core-site.xml directly on the cluster for Linux users.
GitHub Create Pull Request
Hdinsight Create Apache Hadoop clusters using templates - Azure HDInsight ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-create-linux-clusters-arm-templates.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 moderate Windows bias. PowerShell is mentioned and linked before Azure CLI, and Visual Studio (a Windows-centric tool) is promoted for template deployment, including references to PowerShell scripts. There is a lack of explicit Linux/macOS examples, and the .NET client library example links to a Windows-specific page. Although Azure CLI is referenced, it is not given equal prominence or example parity with PowerShell and Visual Studio.
Recommendations
  • Provide explicit Linux/macOS examples for template deployment, such as using Azure CLI from Bash.
  • Present Azure CLI instructions before or alongside PowerShell to avoid Windows-first ordering.
  • Include cross-platform editor recommendations (e.g., VS Code, vim, nano) equally with Visual Studio.
  • Replace or supplement Windows-specific .NET client library links with platform-neutral or Linux/macOS examples.
  • Clarify that all deployment methods (CLI, REST API, editors) are available and supported on Linux/macOS.
GitHub Create Pull Request
Hdinsight Apache Hadoop & secure transfer storage - Azure HDInsight ...oop-create-linux-clusters-with-secure-transfer-storage.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides instructions for managing secure transfer in Azure Storage accounts via the Azure portal, PowerShell, and Azure CLI. PowerShell (a Windows-centric tool) is given a dedicated section and mentioned before Azure CLI, which is more cross-platform. No Linux-specific shell examples (e.g., Bash) are provided, and PowerShell is presented as a primary method, which may create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred on Linux/macOS.
  • Add explicit Bash shell examples for common tasks, especially for Linux users.
  • Clarify that Azure CLI commands work on Linux/macOS and provide installation links.
  • Mention alternatives to PowerShell for Linux/macOS users, such as Bash or Python SDK.
  • Ensure that all critical operations can be performed using cross-platform tools.
GitHub Create Pull Request
Hdinsight Azure HDInsight for Visual Studio Code ...s/blob/main/articles/hdinsight/hdinsight-for-vscode.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-style paths (e.g., C:\HD\HDexample) in examples and instructions, and does not provide equivalent Linux/macOS paths or examples. While there is mention of Mono as a prerequisite for Linux/macOS, all file/folder navigation and workspace setup examples use Windows conventions, potentially causing confusion or friction for Linux/macOS users. There is a single Linux-specific note about installing xclip, but otherwise, Linux/macOS users are left to infer how to adapt instructions.
Recommendations
  • Provide parallel examples using Linux/macOS file paths (e.g., /home/user/HD/HDexample) wherever Windows paths are shown.
  • Explicitly mention how to perform folder/file operations on Linux/macOS (e.g., using Finder on macOS, Nautilus on Ubuntu, or command line).
  • Add notes or sections clarifying any differences in Visual Studio Code menus or shortcuts on Linux/macOS.
  • Where screenshots show Windows dialogs or paths, include Linux/macOS equivalents or annotate for cross-platform clarity.
  • Ensure all command-line or configuration examples (e.g., .vscode/settings.json) are platform-neutral or show both formats if differences exist.
GitHub Create Pull Request
Hdinsight Apache Hive libraries during cluster creation - Azure HDInsight ...icles/hdinsight/hdinsight-hadoop-add-hive-libraries.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation references both PowerShell (.ps1) and Bash (.sh) scripts for adding Hive libraries, but the PowerShell script is listed first and more prominently. The script location section only links to the PowerShell script, while the Bash script URI is buried in a table further down. There is no explicit Linux/macOS example for uploading files to Azure Storage; only Azure Storage Explorer (a GUI tool available on Windows and macOS, but most commonly used on Windows) is mentioned. The documentation refers to provisioning clusters on Linux, but the initial script action guidance is Windows-centric.
Recommendations
  • List both PowerShell and Bash script locations together, with equal prominence.
  • Provide explicit CLI examples for uploading files to Azure Storage using azcopy or Azure CLI, especially for Linux/macOS users.
  • Clarify which script to use for which OS/platform at the top of the documentation.
  • Include a table comparing Windows and Linux/macOS workflows for the entire process.
  • Mention Linux tools (e.g., azcopy, Azure CLI) alongside Azure Storage Explorer.
GitHub Create Pull Request
Hdinsight Tutorial: On-demand clusters in Azure HDInsight with Data Factory ...dinsight/hdinsight-hadoop-create-linux-clusters-adf.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The tutorial relies heavily on Azure PowerShell scripts for all preliminary resource creation steps, with no mention or examples of equivalent Bash/CLI commands for Linux/macOS users. PowerShell is a Windows-centric tool, and its exclusive use creates friction for those on other platforms. Additionally, the documentation refers to the PowerShell script and its outputs as prerequisites for subsequent steps, reinforcing a Windows-first approach. There is no guidance for Linux users on how to perform these steps using Azure CLI or Bash.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all resource creation steps, including storage account and blob operations.
  • Add a section or callout for Linux/macOS users, clarifying how to perform each step using Bash and Azure CLI.
  • Where PowerShell scripts are referenced, offer alternative scripts or command snippets for non-Windows platforms.
  • Explicitly state cross-platform options in the prerequisites, e.g., 'You can use Azure PowerShell or Azure CLI.'
  • Ensure screenshots and instructions do not assume use of Windows-only tools.
GitHub Create Pull Request
Hdinsight Customize Azure HDInsight cluster configurations using bootstrap ...nsight/hdinsight-hadoop-customize-cluster-bootstrap.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page is heavily biased towards Windows and PowerShell. All code samples and the detailed walkthrough use Azure PowerShell, which is primarily a Windows tool. There are no equivalent examples or instructions for Bash, Azure CLI, or other Linux/macOS-friendly tools. The .NET SDK is mentioned but not demonstrated. The Resource Manager template section is more neutral, but the main actionable content is Windows-centric. Linux users are directed to a separate page for Script Actions, but no direct parity is provided here.
Recommendations
  • Add Azure CLI examples for customizing HDInsight cluster configurations, as CLI is cross-platform.
  • Provide Bash script samples for common configuration tasks.
  • Include instructions or code snippets for using Script Actions directly in this page, not just as a link.
  • Demonstrate .NET SDK usage on Linux/macOS where possible.
  • Reorder sections so that cross-platform methods (ARM templates, CLI, Script Actions) are presented before PowerShell.
  • Explicitly state which methods are cross-platform and which are Windows-only.
GitHub Create Pull Request
Hdinsight Use .NET with Hadoop MapReduce on Linux-based HDInsight - Azure .../hdinsight/hdinsight-hadoop-migrate-dotnet-to-linux.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 by exclusively referencing Windows tools (Visual Studio, .NET Portability Analyzer as a Visual Studio extension), providing step-by-step instructions only for Windows environments, and omitting Linux-native alternatives for portability analysis and building .NET solutions. Linux users are expected to adapt Windows-centric instructions without guidance for equivalent workflows on Linux.
Recommendations
  • Include instructions for running portability analysis on Linux, such as using the command-line version of .NET Portability Analyzer or alternative tools.
  • Provide examples of building .NET solutions with Mono on Linux, including command-line build steps (e.g., using msbuild or dotnet CLI).
  • Add guidance for Linux users on how to audit and modify code outside of Visual Studio, such as using VS Code or other editors.
  • Present Linux-native file path examples and highlight common cross-platform pitfalls.
  • Ensure parity by listing Linux workflows before or alongside Windows instructions.
GitHub Create Pull Request
Hdinsight Monitor and manage Hadoop with Ambari REST API - Azure HDInsight ...s/hdinsight/hdinsight-hadoop-manage-ambari-rest-api.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Bash and PowerShell examples for all tasks, but consistently lists Windows/PowerShell options first and includes explicit references to Windows tools and environments (e.g., Bash on Ubuntu on Windows 10, Windows Subsystem for Linux, Windows PowerShell, and jq for Windows). There are multiple mentions of Windows-specific setup and usage patterns, and PowerShell is presented as a primary alternative to Bash. Linux/macOS users are supported, but the documentation is clearly oriented towards Windows users.
Recommendations
  • List Bash/Linux examples before PowerShell/Windows examples to reflect the native platform for HDInsight clusters.
  • Remove or de-emphasize references to Windows Subsystem for Linux and Bash on Windows in prerequisites; instead, mention native Linux/macOS shells first.
  • Add explicit instructions for running commands on native Linux/macOS environments, including installation steps for jq and curl.
  • Clarify that all examples work natively on Linux/macOS and provide troubleshooting tips for those platforms.
  • Where Windows-specific tools (e.g., PowerShell, jq-win64) are mentioned, provide equivalent Linux/macOS instructions or alternatives.
  • Avoid implying that Windows is the default or preferred environment for cluster management tasks.
GitHub Create Pull Request
Hdinsight Manage logs for an HDInsight cluster - Azure HDInsight ...ob/main/articles/hdinsight/hdinsight-log-management.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 a moderate Windows bias. PowerShell is frequently mentioned as a primary scripting and automation tool, with references to Azure PowerShell cmdlets and .NET SDKs for log management and job submission. Windows-centric tools like Visual Studio, Power Query for Excel, and Azure Storage Explorer are listed for log analysis and management, often before or instead of Linux alternatives. While SSH and Ambari (Linux-based) are covered, Linux-native tools and scripting approaches (e.g., Bash, Python, Linux CLI utilities) are underrepresented or omitted in several key sections. Some examples and instructions are Windows-first or Windows-only, and Linux equivalents are missing or relegated to later sections.
Recommendations
  • Provide Linux/Bash script examples alongside PowerShell examples for log management and automation tasks.
  • List Linux-native tools (e.g., grep, awk, sed, rsync, cron) for log analysis, archiving, and rotation in addition to Windows tools.
  • Highlight cross-platform CLI tools (e.g., Azure CLI, AzCopy) and clarify their usage on Linux/macOS.
  • Include explicit instructions for accessing and managing logs using Linux/macOS environments, especially for tasks currently described only with PowerShell or Windows tools.
  • Reorder examples so that cross-platform or Linux-native methods are presented before or alongside Windows-specific approaches.
  • Reference Linux-based graphical tools (e.g., KDiff3, GNOME Logs) where appropriate.
GitHub Create Pull Request
Hdinsight Granular role-based access Azure HDInsight cluster configurations ...insight-migrate-granular-access-cluster-configurations.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. It provides detailed migration steps for Windows-centric tools such as PowerShell, Visual Studio, and Azure Data Lake/Stream Analytics Tools for Visual Studio, and mentions PowerShell cmdlets explicitly. While cross-platform SDKs (Python, Java, Go) and Azure CLI are covered, Windows tools are listed first and receive more detailed attention. There are no Linux/macOS-specific examples, nor are Linux-native tools (e.g., Bash scripts, shell commands) referenced.
Recommendations
  • Add explicit Linux/macOS instructions and examples, such as Bash scripts for role assignment and cluster configuration.
  • Include parity for Linux-native tools (e.g., demonstrate using Azure CLI from Bash, or mention cross-platform editors like VS Code in a Linux context).
  • Reorder sections so that cross-platform tools (Azure CLI, SDKs) are presented before Windows-specific tools.
  • Clarify which tools and commands are cross-platform, and note any platform-specific limitations.
  • Provide troubleshooting steps for Linux/macOS environments, especially for permission errors or SDK installation.
GitHub Create Pull Request
Hdinsight Upload data for Apache Hadoop jobs in HDInsight .../blob/main/articles/hdinsight/hdinsight-upload-data.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation lists several Windows-specific tools (Azure PowerShell, Cerulea, CloudXplorer, CloudBerry Explorer) and graphical clients that are only available on Windows, with no Linux equivalents or alternatives suggested. Azure PowerShell is mentioned as a key utility for uploading data, but is only available on Windows. Some tables list Windows-only tools before cross-platform or Linux options. There are no explicit Linux command-line examples for uploading data outside of the Hadoop command, and no parity for PowerShell examples on Linux/macOS.
Recommendations
  • Provide Linux/macOS alternatives or equivalents for Windows-only tools (e.g., suggest Bash scripts or CLI commands where PowerShell is used).
  • Ensure that cross-platform tools (like Azure CLI and AzCopy) are given prominence and examples for all platforms.
  • Add explicit Linux/macOS command-line examples for uploading data, not just Hadoop commands.
  • Reorder tables and lists to present cross-platform or Linux-compatible tools before Windows-only options.
  • Clearly indicate when a tool is Windows-only and suggest alternatives for other platforms.
GitHub Create Pull Request
Hdinsight Run MapReduce jobs on Entra enabled HDInsight cluster using REST API ...-with-entra-authentication/run-map-reduce-rest-jobs.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 notable Windows bias: Windows-specific tools (PowerShell, cmd.exe) are featured prominently, with examples and variable setting instructions tailored to Windows environments. PowerShell examples are given in detail, while Linux/macOS shell equivalents (bash) are either missing or only briefly referenced. Variable setting and command continuation use Windows syntax (set, ^), and there is no explicit bash/Linux alternative for several steps. The documentation assumes a Windows environment for scripting and command-line usage, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent bash/Linux/macOS examples for all command-line steps, including variable setting and command continuation.
  • Show Linux/macOS syntax (e.g., export TOKEN=..., line continuation with \) alongside Windows/cmd examples.
  • Add explicit notes or sections for Linux/macOS users, clarifying any differences in command usage.
  • Ensure that curl/jq usage is demonstrated in a cross-platform manner, not assuming Windows paths or conventions.
  • Present examples for both platforms side-by-side, or alternate which platform is shown first.
GitHub Create Pull Request
Hdinsight Enable Private Link on an Azure HDInsight cluster ...blob/main/articles/hdinsight/hdinsight-private-link.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 in several areas. The VM deployment example for connectivity testing exclusively uses a Windows 10 image and RDP, with no mention of Linux VM alternatives. The PowerShell example for cluster creation is referenced before the Azure CLI example, and there is no explicit Linux/macOS shell example for cluster creation or connectivity testing. The instructions for SSH access are generic, but the context is a Windows VM, and there are no Linux-specific notes or parity in the walkthrough.
Recommendations
  • Include a Linux VM deployment example (e.g., Ubuntu) alongside the Windows VM example for connectivity testing, with SSH port (22) enabled.
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform.
  • Add explicit instructions for Linux/macOS users on how to test SSH connectivity from a Linux terminal.
  • Mention that both Windows and Linux VMs can be used for testing, and provide configuration details for both.
  • Ensure that all code snippets and portal instructions are platform-neutral or provide alternatives for Linux/macOS users.
GitHub Create Pull Request
Hdinsight Restrict public connectivity in Azure HDInsight ...es/hdinsight/hdinsight-restrict-public-connectivity.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides detailed PowerShell automation for DNS setup and cluster management, with no equivalent Bash, Azure CLI, or Linux/macOS scripting examples. PowerShell is presented as the primary automation method, and Windows-centric tools are referenced first and exclusively in critical workflow sections. While Azure CLI is mentioned for cluster creation, no CLI or Linux-native DNS automation is shown.
Recommendations
  • Add equivalent Azure CLI and Bash examples for DNS automation and cluster management.
  • Explicitly mention cross-platform alternatives to PowerShell for Linux/macOS users.
  • Present Azure CLI and Bash examples alongside or before PowerShell to improve parity.
  • Clarify which steps can be performed using CLI or REST API, and link to relevant documentation.
GitHub Create Pull Request
← Previous Page 5 of 8 Next →