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 176-200 of 867 flagged pages
Hdinsight Tutorial: Use Azure Automation runbooks to create clusters - Azure HDInsight ...ob/main/articles/hdinsight/manage-clusters-runbooks.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All scripting examples use PowerShell, and the runbook creation process exclusively references PowerShell as the runbook type. There are no examples or mentions of Bash, Python, or other cross-platform scripting languages. The use of AzureRM PowerShell modules and the absence of Linux-native tools or CLI examples further reinforce the Windows-centric approach.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts, which are cross-platform and commonly used on Linux.
  • Mention and demonstrate how to create runbooks using Python, which is supported in Azure Automation and widely used in Linux environments.
  • Include instructions for installing necessary modules or packages on Linux systems, not just via the Azure portal.
  • Add a section comparing PowerShell and Bash/Python approaches, helping users choose the best fit for their environment.
  • Ensure screenshots and walkthroughs are not exclusively tied to Windows/PowerShell workflows.
GitHub Create Pull Request
Hdinsight Configure service endpoint policies - Azure HDInsight ...b/main/articles/hdinsight/service-endpoint-policies.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring service endpoint policies, but the CLI example uses Windows-style variable assignment and scripting, and the PowerShell example is given in full detail. There are no Linux-specific shell examples (e.g., Bash), and the CLI example is written in a way that is more familiar to Windows users. The use of PowerShell and Windows-centric scripting patterns may make it less accessible to Linux users.
Recommendations
  • Provide explicit Bash shell examples for Azure CLI commands, using Linux-style variable assignment and arrays.
  • Clarify that Azure CLI commands can be run natively on Linux/macOS and provide sample Bash scripts.
  • Avoid using Windows PowerShell variable syntax in CLI examples; use POSIX-compliant syntax for cross-platform parity.
  • Add notes or sections for Linux/macOS users, highlighting any differences in command usage or environment setup.
  • Ensure that examples and instructions are platform-neutral or provide parallel examples for both Windows and Linux environments.
GitHub Create Pull Request
Hdinsight Azure Toolkit for IntelliJ: Debug Spark apps with SSH - HDInsight ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-intellij-tool-debug-remotely-through-ssh.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the prerequisites and local run sections. Windows-specific issues (WinUtils.exe) and solutions are described in detail, including download instructions and environment variable setup, while Linux/macOS users are only briefly mentioned as not needing these steps. There are no equivalent troubleshooting or configuration examples for Linux/macOS users, and Windows instructions appear first and in more detail.
Recommendations
  • Provide explicit instructions for Linux/macOS users, including any common issues or environment variable setups relevant to those platforms.
  • Balance troubleshooting guidance by listing Linux/macOS steps before or alongside Windows steps, rather than after or as an aside.
  • Include Linux/macOS-specific examples or screenshots where appropriate, especially for local run and debug configurations.
  • Clarify any platform-specific differences in tool usage, configuration, or error handling, rather than focusing on Windows-only tools like WinUtils.exe.
  • Ensure parity in depth and detail for all supported platforms in prerequisites and setup sections.
GitHub Create Pull Request
Hdinsight Azure Toolkit for IntelliJ: Spark app - HDInsight ...s/hdinsight/spark/apache-spark-intellij-tool-plugin.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation demonstrates a bias towards Windows environments, primarily through the explicit requirement for WINUTILS.EXE (a Windows-only tool) for running Spark locally, and the lack of Linux-specific instructions or alternatives. Windows prerequisites and patterns (such as HADOOP_HOME and WINUTILS.exe location) are mentioned without Linux equivalents, and there are no examples or troubleshooting steps for Linux users. The documentation assumes a Windows setup for local Spark development and omits guidance for Linux users, despite HDInsight Spark clusters themselves being Linux-based.
Recommendations
  • Provide clear instructions for running Spark locally on Linux and macOS, including necessary environment variables and dependencies.
  • Replace or supplement WINUTILS.EXE requirements with Linux/macOS equivalents, or clarify when it is only needed for Windows users.
  • Add troubleshooting steps and configuration examples for Linux and macOS users, especially for local development and debugging.
  • Explicitly state OS-specific prerequisites and steps, and ensure Linux/macOS instructions are given equal prominence to Windows.
  • Review all examples and dialog instructions to ensure they are not Windows-centric, and add screenshots or notes for Linux/macOS where applicable.
GitHub Create Pull Request
Hdinsight Azure Toolkit: Debug Apache Spark apps remotely - Azure HDInsight ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-intellij-tool-plugin-debug-jobs-remotely.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by providing explicit instructions and examples for Windows environments, such as editing the hosts file at a Windows-specific path, using Notepad with elevated permissions, and referencing WinUtils.exe and HADOOP_HOME setup for Windows. PowerShell is mentioned for VPN setup, but Linux equivalents (e.g., Bash, CLI) are not provided or are referenced only indirectly. The use of Cygwin for scp commands suggests a workaround for Windows users rather than providing native Linux instructions. There is a lack of parallel Linux/macOS examples for key steps, such as editing the hosts file, setting environment variables, and handling exceptions.
Recommendations
  • Provide explicit instructions and examples for Linux/macOS environments, such as editing /etc/hosts, setting environment variables, and handling permissions.
  • Include Linux/macOS alternatives for downloading and configuring WinUtils.exe, or clarify that this step is only necessary for Windows.
  • Offer Bash/CLI examples for creating VPN connections and other Azure resource management tasks, not just PowerShell.
  • Avoid referencing Windows-specific tools (e.g., Notepad, Cygwin) as the default; instead, present cross-platform options or mention platform-specific steps in parallel.
  • Clearly indicate which steps are platform-dependent and provide guidance for each supported OS.
GitHub Create Pull Request
Hdinsight Quickstart: Create Apache Spark cluster using Bicep - Azure HDInsight ...dinsight/spark/apache-spark-jupyter-spark-use-bicep.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment and resource management, but PowerShell is featured equally and sometimes before Linux-native alternatives. There is no explicit mention of Linux shell (bash) or scripting environments, nor are Linux-specific instructions or screenshots provided. The examples and instructions assume familiarity with PowerShell, which is primarily a Windows tool, and do not offer parity for Linux users who may prefer bash or other shells.
Recommendations
  • Add explicit bash shell examples alongside Azure CLI and PowerShell, showing how to run the CLI commands in a Linux terminal.
  • Clarify that Azure CLI commands can be run natively on Linux/macOS and provide instructions for installing Azure CLI on those platforms.
  • Include screenshots or instructions for accessing HDInsight and Jupyter from Linux environments, not just via the Azure Portal.
  • Mention cross-platform considerations, such as differences in file paths, environment setup, or authentication between Windows and Linux.
  • Avoid presenting PowerShell as the default or primary method; instead, lead with Azure CLI (which is cross-platform) and supplement with PowerShell for Windows users.
GitHub Create Pull Request
Hdinsight What is Apache Spark - Azure HDInsight ...main/articles/hdinsight/spark/apache-spark-overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by consistently mentioning Windows-centric tools and workflows (such as Azure PowerShell, .NET SDK, and Power BI) before or instead of Linux equivalents. Examples and instructions reference Azure PowerShell and the Azure portal for cluster creation, with no mention of Linux CLI tools (e.g., Azure CLI/bash). The integration with BI tools is focused on Power BI, a Microsoft/Windows product, with only brief mention of Tableau as an alternative. There are no explicit Linux or bash command examples, nor references to Linux-native tools or workflows for cluster management or data analysis.
Recommendations
  • Add explicit examples using Azure CLI (cross-platform, commonly used on Linux) for cluster creation and management alongside PowerShell and portal instructions.
  • Include references to Linux-native tools and workflows for interacting with Spark clusters, such as SSH, bash scripting, or Hadoop command-line utilities.
  • Provide parity in BI tool integration examples, such as walkthroughs for connecting to Spark clusters from Tableau, Qlik, or open-source alternatives, not just Power BI.
  • Mention and demonstrate how to use Jupyter and Zeppelin notebooks from Linux environments, including setup instructions for non-Windows users.
  • Balance the order of tool mentions so that cross-platform or Linux-friendly options are listed alongside or before Windows-specific tools.
GitHub Create Pull Request
Hdinsight Tutorial: Analyze Azure HDInsight Apache Spark data with Power BI .../articles/hdinsight/spark/apache-spark-use-bi-tools.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Power BI Desktop, a Windows-only application, and does not mention or provide examples for Linux or cross-platform alternatives. All steps and screenshots assume the use of Windows tools and UI patterns. There are no instructions for using Power BI on Linux (e.g., via Power BI web service or alternatives), nor are Linux-specific tools or workflows discussed. The order of tool presentation and example selection implicitly prioritizes Windows environments.
Recommendations
  • Include instructions for accessing and visualizing Spark data using Power BI Service (web-based), which is cross-platform.
  • Mention and provide examples for connecting to Spark from Linux or macOS environments, possibly using open-source BI tools (e.g., Apache Superset, Grafana) as alternatives.
  • Clarify that Power BI Desktop is Windows-only and suggest Linux/macOS users use the Power BI web service or other supported tools.
  • Add a section on using Azure CLI or other cross-platform tools to manage HDInsight clusters, not just PowerShell.
  • Ensure screenshots and UI instructions are not exclusively Windows-centric; provide web-based or cross-platform alternatives where possible.
GitHub Create Pull Request
Hdinsight Use Apache Pig ...ocs/azure-docs/blob/main/articles/hdinsight/use-pig.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates bias towards Windows by exclusively mentioning SQL Server Integration Services (SSIS) and its Azure Feature Pack as a method for running Pig jobs, which are Windows-centric tools. There are no examples or walkthroughs for running Pig jobs from Linux environments, nor are Linux-native tools or command-line patterns (such as SSH, Bash, or Linux scripting) discussed. The only explicit integration example is with SSIS, and no comparable Linux alternatives (e.g., Oozie, Bash scripts, or direct SSH usage) are provided.
Recommendations
  • Add examples and walkthroughs for running Pig jobs from Linux environments, such as using SSH and Bash scripts.
  • Include references to Linux-native orchestration tools (e.g., Apache Oozie) for job scheduling and management.
  • Present Linux and Windows methods side-by-side, or ensure Linux options are mentioned first to balance the presentation.
  • Provide guidance for users who may be working from macOS or Linux workstations, including command-line instructions.
  • Avoid exclusive focus on Windows tools like SSIS; mention cross-platform or open-source alternatives where possible.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/troubleshoot-domainnotfound.md ...hdinsight/domain-joined/troubleshoot-domainnotfound.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 Windows bias by listing Windows VM troubleshooting steps before Linux (Ubuntu) equivalents, referencing Windows-specific tools and UI (Control Panel), and omitting Linux command-line details while providing more explicit instructions for Windows. The Linux example is less detailed and relies on an external script, whereas the Windows method is described as straightforward via UI.
Recommendations
  • Present Linux (Ubuntu) troubleshooting steps before or alongside Windows steps to avoid ordering bias.
  • Provide explicit Linux command-line instructions for domain joining, rather than referencing an external script.
  • Include equivalent Linux tools and commands (e.g., samba, realm, adcli) and describe their usage.
  • Avoid referencing Windows-specific UI elements (like Control Panel) without Linux equivalents.
  • Ensure parity in detail and clarity between Windows and Linux troubleshooting instructions.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-connect-excel-hive-odbc-driver.md ...hadoop/apache-hadoop-connect-excel-hive-odbc-driver.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows environments, with all setup and usage instructions assuming Windows OS and tools (such as ODBC Data Source Administrator and Excel). There are no examples or guidance for Linux or cross-platform scenarios, and Windows-specific patterns and UI steps are described exclusively.
Recommendations
  • Add instructions for configuring Hive ODBC connections on Linux and macOS, including relevant tools (e.g., unixODBC, isql).
  • Provide examples for importing Hive data into open-source spreadsheet applications (e.g., LibreOffice Calc) on non-Windows platforms.
  • Include CLI-based configuration steps for ODBC data sources (e.g., editing odbc.ini) for Linux users.
  • Mention alternative ODBC drivers that support Linux/macOS, if available, and provide download links.
  • Clarify platform requirements and limitations early in the document to set user expectations.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/domain-joined-authentication-issues.md ...t/domain-joined/domain-joined-authentication-issues.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows AD tools and domain-joined Windows machines as primary methods for troubleshooting (e.g., finding sAMAccountName), while Linux alternatives (such as SAMBA commands) are mentioned secondarily and lack detailed instructions. There are no PowerShell-specific examples, but the overall troubleshooting flow assumes familiarity with Windows environments and tools, and Linux methods are less emphasized or detailed.
Recommendations
  • Provide step-by-step Linux examples for tasks currently described with Windows tools, such as browsing Active Directory for sAMAccountName.
  • Ensure Linux troubleshooting commands (e.g., using ldapsearch, samba, or kinit) are given equal prominence and detail as Windows methods.
  • Add explicit instructions for performing common tasks (like password changes, Kerberos ticket management) from Linux environments.
  • Where Windows tools are referenced, immediately follow with Linux equivalents, not as secondary options.
  • Include screenshots or command outputs from Linux systems to illustrate the process for non-Windows users.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-on-premises-migration-best-practices-security-devops.md ...p-on-premises-migration-best-practices-security-devops.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Microsoft Entra Domain Services (Active Directory), domain joining, and related Windows-centric identity and security patterns. All examples and instructions revolve around Windows-native tools and concepts (AD, DNS tools, LDAPS, Organizational Units), with no mention of Linux-native equivalents (such as MIT Kerberos, OpenLDAP, or local Linux user/group management). There are no Linux-specific examples or alternative approaches for organizations migrating from Linux-based Hadoop clusters.
Recommendations
  • Include guidance for organizations using Linux-native identity solutions (e.g., MIT Kerberos, OpenLDAP) and how to integrate them with HDInsight.
  • Provide examples of cluster deployment and security configuration using Linux authentication and authorization mechanisms.
  • Mention Linux command-line tools and patterns for managing Hadoop clusters, alongside Windows/AD-based instructions.
  • Clarify whether HDInsight supports non-AD authentication and, if so, provide documentation and examples for those scenarios.
  • Ensure parity in documentation by presenting both Windows/AD and Linux-native approaches where possible.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/ldap-sync.md ...lob/main/articles/hdinsight/domain-joined/ldap-sync.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 a Windows bias by referencing Windows-centric tools and patterns such as Samba/Winbind, sAMAccountName, ldp.exe, and Microsoft Entra ID/Domain Services. Windows tools (ldp.exe, net ads) are mentioned for testing LDAP filters, with no Linux alternatives provided or prioritized. The documentation does not offer Linux-specific examples or mention Linux-native LDAP tools (e.g., ldapsearch), and the configuration steps and terminology are tailored to Windows environments.
Recommendations
  • Include Linux-native LDAP testing tools such as ldapsearch in examples and instructions.
  • Provide equivalent Linux command-line examples alongside Windows tools (e.g., show how to test LDAP filters with ldapsearch).
  • Clarify how Samba/Winbind integration works on Linux clusters and mention alternatives if available.
  • Add notes on how sAMAccountName maps to Linux user attributes and discuss any differences.
  • Ensure configuration steps reference both Windows and Linux UI/CLI paths where applicable.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/hdinsight-troubleshoot-converting-service-principal-certificate.md ...-troubleshoot-converting-service-principal-certificate.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 Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell and C# examples for converting certificate contents to base-64, both of which are primarily used on Windows. There are no Linux or cross-platform command-line examples (such as using OpenSSL or base64 utilities), and Windows tools/patterns are mentioned first and exclusively.
Recommendations
  • Add Linux shell examples, such as using 'openssl' and 'base64' commands to convert pfx files to base-64.
  • Include cross-platform instructions, specifying how to perform the conversion on macOS and Linux.
  • Present Linux and Windows examples side-by-side or in parallel sections to ensure parity.
  • Mention relevant Linux tools (e.g., OpenSSL, base64) and provide sample commands.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/hdinsight-use-hive.md ...b/main/articles/hdinsight/hadoop/hdinsight-use-hive.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 page demonstrates some Windows bias. Windows-specific tools (Visual Studio, PowerShell, SSIS) are highlighted as primary methods for interacting with Hive, sometimes before or in addition to cross-platform alternatives. Windows PowerShell is listed as a method for running Hive queries, but there is no equivalent Linux shell example. SQL Server Integration Services (SSIS) is mentioned for scheduling Hive jobs, but Linux-native alternatives (e.g., cron, shell scripts) are not discussed. While many tools are cross-platform, Windows-specific options are given prominence and Linux-specific workflows are underrepresented.
Recommendations
  • Add explicit Linux shell (bash) examples for running Hive queries, similar to the PowerShell example.
  • Include Linux-native scheduling options (e.g., cron jobs, shell scripts) alongside SSIS and Data Factory.
  • Ensure cross-platform tools (Beeline, REST API, VS Code) are listed before Windows-only tools in tables and lists.
  • Provide parity in examples and instructions for both Windows and Linux environments, especially for command-line usage.
  • Mention Linux package managers and installation steps for Hive clients where relevant.
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-09 00:34
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 the storage account addition, but does not offer equivalent Linux shell or CLI examples. The verification section lists PowerShell first, and omits Linux command-line alternatives such as SSH with curl, jq, or Azure CLI. This creates a bias toward Windows users and PowerShell workflows, despite HDInsight clusters being Linux-based.
Recommendations
  • Add Linux shell (bash) examples for verification, using curl and jq to query the cluster REST API.
  • Include Azure CLI commands for verification, as Azure CLI is cross-platform.
  • Present PowerShell and Linux/CLI examples in parallel, or alternate which is shown first.
  • Explicitly mention that the PowerShell example is for Windows users, and provide guidance for Linux/Mac users.
  • Review other sections for similar bias and ensure Linux parity throughout the documentation.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/interactive-query/hdinsight-connect-hive-zeppelin.md ...t/interactive-query/hdinsight-connect-hive-zeppelin.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 a bias toward Windows by referencing Windows-centric tools (Visual Studio, PowerShell) and providing next steps that focus on Windows environments. Linux equivalents (such as Linux command-line tools or editors) are not mentioned, and PowerShell is listed as a method for cluster deletion before Azure CLI or browser. There are no Linux-specific examples or guidance for users who may be working in a Linux environment.
Recommendations
  • Include Linux-specific instructions and examples, such as using the Azure CLI from a Linux shell to manage clusters.
  • Provide alternative next steps for Linux users, such as connecting to HDInsight and running Hive queries using VS Code, Jupyter, or command-line tools.
  • When listing tools or methods (e.g., for cluster deletion), present cross-platform options together or list Azure CLI (which is cross-platform) before PowerShell.
  • Add explicit notes or sections for Linux/macOS users to ensure parity and inclusivity.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/azure-monitor-agent.md ...cs/blob/main/articles/hdinsight/azure-monitor-agent.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 Windows bias in several ways. The PowerShell approach is presented before the Azure CLI approach, and PowerShell is referenced as the required method for enabling monitoring when the workspace is in a different subscription. The CLI instructions, while present, rely on tools (azcopy, jq) but do not provide explicit Linux shell examples or alternatives to PowerShell for common administrative tasks. References to Windows-specific documentation (e.g., 'Set up the Azure Monitor agent on Windows client devices') are included, and there is no mention of Linux-specific tools or shell scripting for equivalent operations. There are no Bash or Linux shell script examples for tasks like DCR creation, workspace management, or agent enablement, despite HDInsight clusters typically running on Linux.
Recommendations
  • Present Azure CLI and Bash/Linux shell examples before or alongside PowerShell examples, especially for HDInsight clusters which are Linux-based.
  • Avoid referencing Windows-specific documentation unless there is a Linux equivalent; provide links to Linux agent setup guides where relevant.
  • Include explicit Bash or Linux shell script examples for all steps, such as DCR creation, workspace management, and agent enablement.
  • Clarify that PowerShell is not required for Linux-based clusters and provide guidance for Linux administrators.
  • Where tools like jq or azcopy are used, specify installation instructions for Linux and provide alternative commands if available.
  • Add a section or notes on platform parity, highlighting any differences or limitations between Windows and Linux approaches.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/component-version-validation-error-arm-templates.md ...ht/component-version-validation-error-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 Missing Linux Example
Summary
The documentation mentions PowerShell explicitly as a method for submitting cluster creation requests before mentioning Azure CLI and other automation tools. No Linux-specific tools or examples (such as Bash, shell scripts, or Linux command-line usage) are provided, and there are no explicit Linux-oriented instructions or code snippets. The focus on PowerShell and lack of Linux examples suggests a Windows bias.
Recommendations
  • Include explicit Linux/Bash examples for cluster creation and troubleshooting, alongside PowerShell examples.
  • Mention Linux tools (such as Bash scripts or shell commands) equally or before Windows tools when listing automation options.
  • Provide parity in code snippets, showing both PowerShell and Bash/Azure CLI usage where relevant.
  • Clarify that HDInsight clusters are Linux-based and provide guidance tailored for Linux users.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/disk-encryption.md ...e-docs/blob/main/articles/hdinsight/disk-encryption.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 Windows bias in several ways. PowerShell is used for key deployment examples and for enabling encryption at host, with no equivalent Bash or Linux shell examples. Windows-centric tools (PowerShell, Azure portal) are mentioned and shown before their Linux equivalents, and there are no explicit Linux command-line examples for key operations or cluster creation. The ARM template deployment example is shown only with PowerShell, not with Bash or Linux CLI. Recovery instructions reference PowerShell cmdlets before CLI equivalents. Overall, Linux users are left without direct, platform-native instructions for several key tasks.
Recommendations
  • Provide equivalent Bash/Linux shell examples for all PowerShell code snippets, especially for ARM template deployments and cluster creation.
  • Include Linux-native command-line instructions (e.g., Bash scripts, az CLI with Bash) for key vault operations and cluster management.
  • Ensure that Azure CLI examples are given equal prominence and detail as PowerShell examples, and are not presented as secondary.
  • Reference Linux tools and workflows explicitly, such as using SSH, Bash, or Linux-based automation, where relevant.
  • When listing recovery options or operational steps, present CLI and Linux-native methods before or alongside PowerShell/Windows methods.
  • Add notes clarifying platform compatibility for all examples, and link to Linux-specific documentation where available.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/cluster-reboot-vm.md ...docs/blob/main/articles/hdinsight/cluster-reboot-vm.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 documentation page demonstrates a Windows bias by providing detailed PowerShell examples for rebooting HDInsight cluster VMs, listing PowerShell as the first and only CLI example. There are no equivalent Linux shell (bash/az CLI) examples, nor is there mention of Linux-specific tools or commands. The REST API section is platform-neutral, but the lack of Linux parity in CLI instructions is notable.
Recommendations
  • Add equivalent Linux/bash/az CLI examples for listing and rebooting HDInsight cluster nodes.
  • Mention cross-platform tools (e.g., Azure CLI) before or alongside PowerShell, and provide usage instructions.
  • Clarify which steps or tools are available on both Windows and Linux, and highlight any platform-specific limitations.
  • Include troubleshooting or reboot instructions using SSH and native Linux commands where appropriate.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/connect-on-premises-network.md ...main/articles/hdinsight/connect-on-premises-network.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 moderate Windows bias. In several sections, Windows-centric tools and patterns (e.g., PowerShell, Windows Server DNS) are mentioned before or more prominently than their Linux equivalents. PowerShell examples are given before CLI, and the only explicit external DNS server documentation linked is for Windows Server. While Linux is supported and examples are present (e.g., Bind DNS setup, SSH usage), Windows tools and workflows are often referenced first or exclusively.
Recommendations
  • Provide Linux/BIND DNS server documentation links alongside Windows Server DNS references.
  • Ensure Azure CLI examples are given equal prominence to PowerShell, and consider listing CLI before PowerShell to avoid implicit Windows-first ordering.
  • Add explicit examples or links for configuring conditional forwarders in common Linux DNS servers (e.g., Bind, Unbound) in the 'Configure on-premises DNS server' section.
  • Where PowerShell is referenced, clarify that CLI or Bash alternatives are available and provide those commands.
  • Review all tool references to ensure Linux tools (e.g., nano, systemd, etc.) are given equal weight and explanation as Windows tools.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/apache-domain-joined-architecture.md ...ght/domain-joined/apache-domain-joined-architecture.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 strong Windows bias. It exclusively references Windows-centric technologies (Active Directory, Microsoft Entra Domain Services), and all example commands are given in PowerShell, with no Linux shell or cross-platform alternatives. Windows tools and patterns (such as PowerShell modules and service principals) are mentioned without reference to Linux equivalents or how Linux administrators might perform similar tasks. The documentation assumes a Windows-based environment and omits guidance for Linux-based workflows or tools.
Recommendations
  • Provide equivalent Linux shell (bash) commands or scripts for all PowerShell examples, where possible.
  • Mention and document how Linux administrators can interact with Azure HDInsight security features, including any available CLI tools (e.g., Azure CLI) or REST APIs.
  • Clarify whether the described procedures are platform-agnostic or specific to Windows, and offer alternative steps for Linux environments.
  • Include references to open-source identity providers or integration patterns that may be relevant for Linux-heavy organizations.
  • Add explicit notes about platform requirements and limitations, and suggest cross-platform best practices for managing HDInsight security.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/apache-domain-joined-create-configure-enterprise-security-cluster.md ...in-joined-create-configure-enterprise-security-cluster.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 is heavily oriented toward Windows environments, with all examples and instructions using Windows-specific tools (Remote Desktop, MMC, Server Manager, PowerShell). There are no Linux equivalents or alternative workflows provided, and Windows patterns are presented as the default or only option for key steps such as domain controller setup, certificate management, and network configuration.
Recommendations
  • Provide Linux-based alternatives for domain controller setup and management, such as using Samba/SSSD for domain services.
  • Include examples using Azure CLI and Bash scripts alongside PowerShell for resource creation and configuration.
  • Document how to connect to VMs using SSH rather than only Remote Desktop, and clarify how Linux admins can perform equivalent tasks.
  • Explain certificate creation and management using OpenSSL and Linux tools, not just MMC and Windows wizards.
  • Add guidance for managing users and groups in Microsoft Entra ID from Linux environments, possibly via Azure CLI or REST API.
  • Ensure all major steps have both Windows and Linux instructions/examples, or explicitly note platform limitations.
GitHub Create Pull Request
← Previous Page 8 of 35 Next →