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 801-825 of 867 flagged pages
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-customize-cluster-linux.md .../hdinsight/hdinsight-hadoop-customize-cluster-linux.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples and instructions for both Azure PowerShell and Azure CLI, but PowerShell is consistently presented before CLI, and PowerShell examples are more detailed and prominent. There are multiple references to PowerShell-specific cmdlets and scripts, with CLI examples and commands appearing later or with less emphasis. There is no explicit Windows-only tooling, but the ordering and depth of PowerShell coverage suggest a subtle Windows-first bias.
Recommendations
  • Present Azure CLI and PowerShell examples in parallel or alternate their order to avoid implying preference.
  • Ensure that CLI examples are as detailed and comprehensive as PowerShell examples, including output samples and step-by-step instructions.
  • Add explicit notes that PowerShell can be used cross-platform, but highlight that Azure CLI is often preferred on Linux/macOS.
  • Where possible, provide Bash shell script snippets for common tasks, especially in sections focused on Linux-based clusters.
  • Review and balance the depth of coverage for PowerShell and CLI to ensure Linux users are equally supported.
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
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation provides a balanced overview of SSH usage across platforms, but there is a subtle Windows bias in the ordering and emphasis of SSH client options. Windows-specific tools and installation instructions are given more detailed attention, and Windows alternatives (including graphical clients) are listed before or with more explanation than their Linux equivalents. However, Linux/Unix commands and patterns are present throughout, and most command-line examples use standard ssh/scp syntax applicable to all platforms.
Recommendations
  • When listing SSH clients, mention Linux/Unix/macOS built-in support first, as these platforms natively include SSH tools, then describe Windows options.
  • Provide equal detail for Linux/Unix/macOS SSH client usage and configuration, not just for Windows installation.
  • Include explicit Linux/Unix/macOS command-line examples where possible, especially for tasks like SSH key generation, agent forwarding, and file copying.
  • When referencing graphical SSH clients, note that such tools are available on Linux/macOS as well (e.g., GNOME Terminal, Konsole, or FileZilla for SCP/SFTP).
  • Ensure that any PowerShell or Windows-specific instructions are accompanied by equivalent Linux/Unix/macOS instructions, or clearly state when a step is platform-specific.
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
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for enabling and managing Azure Monitor logs on HDInsight clusters. However, PowerShell (a Windows-centric tool) is consistently presented before Azure CLI (which is more cross-platform and Linux-friendly) in all code example sections. There are no explicit Linux shell or OS-specific instructions, but the ordering and emphasis on PowerShell may suggest a Windows-first approach. No exclusive use of Windows tools or missing Linux examples were found, as Azure CLI is included throughout.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to reflect the prevalence of Linux-based HDInsight clusters.
  • Explicitly state that Azure CLI commands work natively on Linux, macOS, and Windows, and that PowerShell is available cross-platform but is traditionally associated with Windows.
  • Where relevant, add notes or examples for running commands in a Linux shell environment (e.g., bash), especially for common operational tasks.
  • Consider including a short section on choosing between PowerShell and Azure CLI, highlighting cross-platform compatibility.
  • Ensure that any OS-specific prerequisites or behaviors (such as file paths, permissions, or agent installation) are documented for both Windows and Linux environments.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-use-external-metadata-stores.md ...es/hdinsight/hdinsight-use-external-metadata-stores.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a bias towards Windows/Azure-centric tooling by exclusively referencing Azure SQL Database as the external metastore option, with no mention of open-source or Linux-native alternatives (such as MySQL, PostgreSQL, or MariaDB, which are supported by Apache Hive and Oozie). All configuration steps, screenshots, and instructions are based on the Azure Portal and Azure SQL Database, with no examples or guidance for users who may wish to use non-Microsoft databases or command-line (Linux) tools. There are no PowerShell or Windows command-line examples, but the absence of Linux-native options and the exclusive focus on Azure SQL Database constitutes a form of Windows/Microsoft ecosystem bias.
Recommendations
  • Document how to use open-source databases (e.g., MySQL, PostgreSQL, MariaDB) as external metastores for Hive, Oozie, and Ambari, including any limitations or support caveats in HDInsight.
  • Provide example configuration steps for setting up and connecting to non-Azure SQL Database metastores, including Linux command-line (e.g., mysql, psql) instructions.
  • Include guidance for configuring firewall/network access for non-Azure databases, possibly running on Linux VMs or on-premises.
  • Add troubleshooting and backup/restore instructions for open-source database metastores.
  • Clarify in the documentation whether only Azure SQL Database is supported, or if other databases are possible, and if so, provide parity in documentation.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/use-managed-identity-for-sql-database-authentication-in-azure-hdinsight.md ...ity-for-sql-database-authentication-in-azure-hdinsight.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on using the Azure Portal UI and SQL query editor for configuring Managed Identity authentication, without providing any command-line examples or guidance for Linux users (e.g., Azure CLI, Bash scripting). There is no mention of PowerShell, but the absence of Linux/CLI alternatives and the reliance on portal screenshots and SQL commands may disadvantage users working in Linux-first or automated/scripted environments.
Recommendations
  • Add step-by-step instructions for configuring Managed Identity authentication using the Azure CLI, including relevant Bash commands.
  • Provide examples for automating the process (e.g., using Azure CLI scripts) suitable for Linux environments.
  • Clarify that the process can be performed from any OS, and explicitly mention Linux compatibility where relevant.
  • Include references or links to cross-platform tools and documentation (e.g., Azure CLI, az sql commands) alongside portal-based instructions.
GitHub Create Pull Request
Hdinsight Cluster management best practices - Azure HDInsight ...rticles/hdinsight/cluster-management-best-practices.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page lists multiple options for cluster management, with Azure PowerShell (a Windows-centric tool) featured alongside Azure CLI and cURL. PowerShell is mentioned before cURL, and there is a dedicated link for PowerShell-based cluster creation, which may suggest a Windows-first approach. However, Linux-based cluster creation is referenced in several places, and most options are cross-platform. There are no explicit Linux/macOS examples missing, but the ordering and inclusion of PowerShell as a primary method may create a perception of Windows bias.
Recommendations
  • Ensure that Linux/macOS equivalents (such as Bash/CLI/cURL) are presented before or alongside PowerShell examples.
  • Clarify in each method's description which platforms are supported (e.g., 'Azure CLI: works on Windows, Linux, and macOS').
  • Add explicit Linux/macOS usage notes or examples where PowerShell is mentioned.
  • Consider grouping cross-platform tools together and separating Windows-specific tools like PowerShell.
GitHub Create Pull Request
Hdinsight Connect Azure HDInsight to your on-premises network ...main/articles/hdinsight/connect-on-premises-network.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows (PowerShell) and Linux (Azure CLI, SSH, Bind) examples, but there is a noticeable Windows bias: PowerShell is mentioned before Azure CLI in prerequisites and example sections, and Windows-specific tools (like Add-DnsServerConditionalForwarderZone) are referenced before or more prominently than their Linux equivalents. The documentation does include Linux instructions for DNS setup and cluster connection, but Windows tooling is often presented first or with more detail.
Recommendations
  • Present Azure CLI and Linux-native instructions before or alongside PowerShell/Windows examples, especially in prerequisites and example sections.
  • Include explicit instructions or links for configuring DNS forwarding on common Linux DNS servers (Bind, dnsmasq) before referencing Windows Server tools.
  • Balance example ordering so that Linux and Windows users see their relevant tools with equal prominence.
  • Where PowerShell scripts are given, provide equivalent Bash/Azure CLI scripts for Linux/macOS users.
  • Add a summary table comparing steps for Windows and Linux environments where applicable.
GitHub Create Pull Request
Hdinsight Authentication issues in Azure HDInsight ...t/domain-joined/domain-joined-authentication-issues.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page shows a mild Windows bias. Windows tools for browsing Active Directory are mentioned explicitly, and Windows domain-joined machines are referenced before Linux alternatives. Linux methods (e.g., using SAMBA commands) are included, but not always with full example syntax or parity. Some troubleshooting steps reference Windows-centric workflows (e.g., password change via Azure portal, which may be less direct for Linux users).
Recommendations
  • Provide explicit Linux/macOS examples for all troubleshooting steps, especially for directory browsing and account management.
  • List Linux command-line alternatives (e.g., ldapsearch, realm, klist) alongside Windows tools, and show example usage.
  • When referencing Windows tools, mention Linux/macOS equivalents in parallel, not as secondary options.
  • Clarify steps for password changes and account management for users not on Windows, including links to relevant Azure CLI or web interfaces.
  • Ensure all scripts (e.g., RegisterKerbTicketAndOAuth.sh) have usage notes for non-Windows environments.
GitHub Create Pull Request
Hdinsight How to get the host names of Azure HDInsight cluster nodes ...re-docs/blob/main/articles/hdinsight/find-host-name.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash (Linux/macOS) and PowerShell (Windows) examples for retrieving host names via the Ambari REST API, but the PowerShell example is given immediately after the Bash example and references Windows-specific tools. The mention of ConvertFrom-Json links to PowerShell documentation before introducing jq, and the PowerShell example is more verbose, potentially suggesting a Windows-centric audience. However, both platforms are covered and no critical functionality is missing for Linux/macOS users.
Recommendations
  • Present Bash and PowerShell examples side-by-side or clarify platform applicability for each example.
  • Provide explicit instructions for macOS users if any platform-specific caveats exist.
  • Reference jq before ConvertFrom-Json when discussing JSON parsing, or provide equal prominence to both tools.
  • Add a note clarifying which example to use for which operating system.
GitHub Create Pull Request
Hdinsight Quickstart: Create Apache Hadoop cluster in Azure HDInsight using Bicep ...doop/apache-hadoop-linux-tutorial-get-started-bicep.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup. However, PowerShell examples are given equal prominence to CLI, and the term 'Azure PowerShell' is used without clarifying its cross-platform support. There is a subtle Windows-first bias in listing PowerShell as a primary option, which may cause confusion for Linux/macOS users who are less likely to use PowerShell. No Linux-specific tools or shell examples (e.g., Bash scripts) are provided, but the use of Azure CLI does ensure Linux compatibility.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform, but is most commonly used on Windows.
  • List Azure CLI examples first, as it is the default tool for Linux/macOS users.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI.
  • Consider adding a Bash script example for automation on Linux.
  • Add a note for Linux/macOS users about installing Azure CLI and using it in their native shell.
GitHub Create Pull Request
Hdinsight Storage: Migrate on-premises Apache Hadoop to Azure HDInsight ...he-hadoop-on-premises-migration-best-practices-storage.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Minor Windows Path Reference
Summary
The documentation is generally cross-platform, focusing on Hadoop and Azure integration, but there are subtle signs of Windows bias. Windows-style environment variables and paths (e.g., %HADOOP_HOME%) are referenced, and Windows terminology is used in describing configuration file locations. Azure PowerShell is mentioned as a data copy method before Linux equivalents. However, all command-line examples are given in bash, and no PowerShell-specific instructions or Windows-only tools are required for critical steps.
Recommendations
  • Replace Windows-style environment variable references (e.g., %HADOOP_HOME%) with platform-neutral or Linux-style ($HADOOP_HOME) equivalents, or mention both.
  • When listing data copy methods, mention Linux-native tools (e.g., DistCp, ADLCopy) before Azure PowerShell, or provide parity in example ordering.
  • Clarify that all steps and tools are available on Linux/macOS, and provide explicit notes or examples for non-Windows users where ambiguity exists.
  • Add a brief section or note confirming that all configuration paths and commands apply equally to Linux-based Hadoop clusters, or specify differences if any.
GitHub Create Pull Request
Hdinsight Use Apache Hadoop Hive with Curl in HDInsight - Azure ...ticles/hdinsight/hadoop/apache-hadoop-use-hive-curl.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash/cURL and PowerShell examples for all major steps, but consistently lists PowerShell (Windows) examples second and gives equal detail to both. However, the initial mention of REST clients lists PowerShell first, and the Bash instructions require an extra dependency (jq) not required for PowerShell. The documentation does not show exclusive use of Windows tools, but the parity is not perfect: Bash users must install jq, and some explanations (like credential handling) are more streamlined for PowerShell.
Recommendations
  • List Bash/cURL examples first or alternate order to avoid implicit Windows primacy.
  • Provide a brief explanation or example for installing jq on Linux/macOS, not just a link.
  • Clarify credential management for Bash users, perhaps suggesting use of environment variables or .netrc for parity with PowerShell's Get-Credential.
  • Explicitly mention that all examples work on Linux/macOS, and note any platform-specific caveats.
  • Consider adding a table comparing Bash and PowerShell workflows for clarity.
GitHub Create Pull Request
Hdinsight Quickstart: Apache HBase & Apache Phoenix - Azure HDInsight ...les/hdinsight/hbase/apache-hbase-query-with-phoenix.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation shows a mild Windows bias. The initial curl and ssh commands are presented in 'cmd' code blocks, which may suggest Windows Command Prompt usage, even though these commands are cross-platform. The 'Delete an HDInsight cluster' section mentions PowerShell before Azure CLI and browser, and does not provide explicit Linux/macOS instructions or examples. There are no explicit Linux/macOS-specific examples or clarifications, and the documentation does not address platform-specific nuances for installing or running SQLLine.
Recommendations
  • Present command-line examples in a cross-platform manner, using generic shell blocks or specifying both Windows and Linux/macOS variants where needed.
  • Explicitly mention that curl and ssh commands work on Linux/macOS terminals as well as Windows (with WSL or appropriate tools).
  • In the 'Delete a cluster' section, provide explicit Linux/macOS instructions (e.g., using Azure CLI in bash) and avoid listing PowerShell first.
  • Clarify any platform-specific installation steps for SQLLine, if applicable.
  • Add notes or sections for Linux/macOS users to ensure parity and clarity.
GitHub Create Pull Request
Hdinsight Quickstart: Query Apache HBase in Azure HDInsight - HBase Shell ...ticles/hdinsight/hbase/query-hbase-with-hbase-shell.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation shows minor Windows bias by referencing PowerShell and browser methods before Azure CLI for cluster deletion, and by using the 'cmd' code block for the SSH example (which is more common on Windows). However, the main workflow uses SSH and HBase Shell, which are cross-platform and standard on Linux/macOS. Linux users are not blocked from completing any tasks.
Recommendations
  • Present Azure CLI and browser methods before PowerShell when listing deletion options, or list all equally.
  • Use 'bash' or generic code blocks for SSH commands instead of 'cmd', as SSH is native to Linux/macOS.
  • Explicitly mention that all steps work on Linux/macOS, and provide any OS-specific notes if needed.
  • If PowerShell is mentioned, also provide equivalent Bash/Azure CLI examples where applicable.
GitHub Create Pull Request
Hdinsight Cluster capacity planning in Azure HDInsight ...main/articles/hdinsight/hdinsight-capacity-planning.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page shows mild Windows bias by mentioning PowerShell scripting and Azure Automation as primary examples for cluster lifecycle management, without providing equivalent Linux/macOS alternatives (such as Bash scripting or cron). Windows-centric tools and terminology (PowerShell, Azure Automation) are referenced before any Linux-native options, and no Linux/macOS-specific examples or guidance are given for automation or scripting tasks.
Recommendations
  • Add examples for automating cluster provisioning and deletion using Bash scripts and Azure CLI, suitable for Linux/macOS users.
  • Mention Linux/macOS scheduling tools (e.g., cron) alongside Azure Automation for script scheduling.
  • Provide parity in scripting guidance by including both PowerShell and Bash/CLI examples where automation is discussed.
  • Explicitly state that HDInsight clusters run on Linux VMs, and clarify that management can be performed from any OS using Azure CLI or portal.
GitHub Create Pull Request
Hdinsight Install third-party applications on Azure HDInsight ...icles/hdinsight/hdinsight-apps-install-applications.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by exclusively providing instructions for installing HDInsight applications via the Azure portal (a graphical interface most commonly used on Windows), and mentioning Azure PowerShell and Azure Classic CLI as deployment options before referencing Linux-based alternatives. There are no explicit Linux command-line examples (such as Azure CLI or Bash), nor are Linux-native tools or workflows highlighted. The SSH section does reference Linux, but only as a link to another document.
Recommendations
  • Add explicit Azure CLI examples for installing and managing HDInsight applications, with step-by-step instructions suitable for Linux/macOS users.
  • Present both PowerShell and CLI/Bash methods side-by-side, or at least mention Azure CLI before or alongside PowerShell.
  • Include screenshots or terminal output from Linux environments where appropriate.
  • Clarify that the Azure portal is cross-platform, but provide alternative instructions for users who prefer command-line tools.
  • Expand troubleshooting and next steps to include Linux-specific guidance and common issues.
GitHub Create Pull Request
Hdinsight Create virtual networks for Azure HDInsight clusters ...articles/hdinsight/hdinsight-create-virtual-network.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for network security group configuration, but consistently lists PowerShell (Windows-centric) examples before CLI (cross-platform). The PowerShell section is more verbose and detailed, while the CLI section is more concise. There are no Linux shell (bash) or macOS-specific examples, but CLI coverage is sufficient for non-Windows users. DNS configuration examples are Linux-focused, and testing recommendations mention Linux VMs. Overall, the bias is minor, mainly in ordering and verbosity.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform parity.
  • Ensure CLI examples are as detailed as PowerShell ones, including explanations and step-by-step guidance.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows.
  • Consider adding bash script examples for common tasks, or clarify that CLI commands can be run in bash/zsh.
  • Add a note that PowerShell Core is available on Linux/macOS, if relevant.
GitHub Create Pull Request
Hdinsight Azure HDInsight for Visual Studio Code ...s/blob/main/articles/hdinsight/hdinsight-for-vscode.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page shows a mild Windows bias, primarily by presenting Windows-style paths (e.g., C:\HD\HDexample) as the default in examples and instructions, without providing equivalent Linux/macOS paths. While prerequisites mention Mono for Linux/macOS and there is a brief Linux-specific note about installing xclip, most step-by-step instructions and screenshots use Windows conventions and do not offer Linux/macOS alternatives. No PowerShell or Windows-only tools are referenced, but the lack of Linux/macOS examples may cause minor friction for non-Windows users.
Recommendations
  • Provide Linux/macOS path examples (e.g., /home/user/HDexample) alongside Windows paths in all relevant instructions.
  • Include screenshots or notes showing folder selection and file creation on Linux/macOS.
  • Clarify any platform-specific differences in Visual Studio Code menus or behaviors.
  • Add a section or callouts for common Linux/macOS troubleshooting steps (e.g., permissions, Mono installation).
GitHub Create Pull Request
Hdinsight Tips for using Hadoop on Linux-based HDInsight - Azure ...ticles/hdinsight/hdinsight-hadoop-linux-information.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation is generally Linux-focused, as expected for HDInsight on Linux, but there are minor signs of Windows bias. In the section on accessing Azure Data Lake Storage Gen1, PowerShell and Visual Studio tools are mentioned before Linux-friendly alternatives, and there is no explicit mention of Linux/macOS equivalents for these tools. Additionally, some references to tools (like Data Lake Tools for Visual Studio) are Windows-only, and PowerShell is listed before Azure CLI in some places. However, the majority of command-line examples use Bash, curl, and jq, which are Linux-native.
Recommendations
  • For every mention of PowerShell or Visual Studio tools, explicitly list or link to Linux/macOS alternatives (e.g., Azure CLI, REST API, or cross-platform SDKs).
  • When listing tools or access methods, present cross-platform or Linux-native options (like Azure CLI, REST API, Python SDK) before Windows-specific ones (PowerShell, Visual Studio).
  • Add a note clarifying which tools are Windows-only and provide guidance for Linux/macOS users.
  • Where possible, provide example commands for both PowerShell and Bash/Azure CLI if a task is commonly performed with both.
GitHub Create Pull Request
Hdinsight Monitor and manage Hadoop with Ambari REST API - Azure HDInsight ...s/hdinsight/hdinsight-hadoop-manage-ambari-rest-api.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
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 major tasks, but Windows tools and patterns are frequently mentioned first or given special emphasis. Prerequisites and setup sections reference Windows-specific environments (Bash on Ubuntu on Windows, Windows Subsystem for Linux, Windows PowerShell) before mentioning generic Unix shells, and PowerShell is often presented as an equal or preferred alternative to Bash. There are references to Windows paths and tools (e.g., jq-win64), and Azure PowerShell cmdlets are highlighted for certain tasks. However, Linux users can complete all tasks using the provided Bash examples.
Recommendations
  • List Bash/Linux examples and prerequisites before Windows/PowerShell equivalents to reflect the Linux-native nature of HDInsight clusters.
  • Remove or de-emphasize references to Windows-specific environments (e.g., Bash on Ubuntu on Windows) in favor of standard Linux/macOS shells.
  • Clarify that all examples work natively on Linux/macOS, and provide explicit instructions for those platforms where needed.
  • Avoid mentioning Windows paths (e.g., C:\HD\jq\jq-win64) in mainline examples; use platform-agnostic paths or provide alternatives for Linux/macOS.
  • Move references to Azure PowerShell cmdlets to a dedicated Windows section or provide CLI alternatives for Linux users.
GitHub Create Pull Request
Hdinsight Set up clusters in HDInsight with Hadoop, Spark, and Kafka ...hdinsight/hdinsight-hadoop-provision-linux-clusters.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows tools (Azure PowerShell, Windows PowerShell cmdlets) are mentioned as cluster setup options and as script action mechanisms, sometimes before or alongside Linux alternatives (Azure CLI, cURL). The 'Related content' section highlights working from a Windows PC, but does not equally highlight Linux/macOS workflows. No explicit Linux/macOS command-line examples are shown, and PowerShell is referenced more than Bash or Linux-native tools.
Recommendations
  • Add explicit Linux/macOS command-line examples (e.g., Bash, Azure CLI) in relevant sections.
  • Ensure Linux tools (Azure CLI, cURL) are mentioned before or alongside Windows tools.
  • Include a 'Work in Apache Hadoop on HDInsight from a Linux/macOS PC' link in Related content.
  • Clarify that script actions can be invoked from Linux environments using Azure CLI or REST, not just Windows PowerShell.
  • Balance references to Windows and Linux tools throughout the documentation.
GitHub Create Pull Request
Hdinsight Query data from HDFS-compatible Azure storage - Azure HDInsight ...rticles/hdinsight/hdinsight-hadoop-use-blob-storage.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page lists Microsoft tools for accessing Azure Storage, with Azure PowerShell and AzCopy highlighted as Windows-only or Windows-first options. Azure PowerShell is only available for Windows, and AzCopy is listed as available for Windows and Linux, but not macOS. The tools table places Windows-specific tools alongside cross-platform ones, and PowerShell is given a dedicated mention. However, the main command-line examples for interacting with HDFS and storage use bash and Hadoop tools, which are Linux-centric and suitable for HDInsight's default Linux clusters. There are no explicit PowerShell or Windows command examples for core tasks, but the tools section does show a slight Windows bias.
Recommendations
  • Clarify that AzCopy is available for macOS as well as Linux and Windows.
  • Provide parity for PowerShell by mentioning Linux/macOS alternatives (e.g., Bash scripts, Python SDK).
  • List cross-platform tools (Azure CLI, AzCopy) before Windows-only tools (PowerShell) in tables and descriptions.
  • Explicitly state that HDInsight clusters are Linux-based and most examples use Linux shell commands.
  • Add a note for Windows users on how to run bash commands (e.g., via WSL or Azure Cloud Shell).
GitHub Create Pull Request
Hdinsight Plan a virtual network for Azure HDInsight ...hdinsight/hdinsight-plan-virtual-network-deployment.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for network resource discovery and management, but PowerShell commands are consistently listed first, and some scripting examples are PowerShell-heavy. There are no explicit Linux/macOS-only gaps, but the ordering and emphasis may subtly favor Windows users, especially those accustomed to PowerShell.
Recommendations
  • Alternate the order of Azure CLI and PowerShell examples, or present CLI first to better support Linux/macOS users.
  • Add explicit notes that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Where scripting is shown in PowerShell, provide equivalent Bash/CLI scripts for Linux/macOS users.
  • Clarify that all cluster creation and management steps can be performed from Linux/macOS using Azure CLI.
  • Consider adding a section or callout for Linux/macOS users, highlighting any platform-specific considerations.
GitHub Create Pull Request
Hdinsight Quickstart: Apache Kafka using Bicep - HDInsight ...icles/hdinsight/kafka/apache-kafka-quickstart-bicep.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, resource review, and cleanup, but consistently lists PowerShell (a Windows-centric tool) as an equal alternative to CLI, and sometimes presents it before or alongside CLI. There are no Linux-specific deployment examples (e.g., Bash scripts), but SSH and Kafka management instructions are Linux-oriented. The overall structure gives slight preference to Windows tooling in deployment and resource management sections.
Recommendations
  • List Azure CLI (cross-platform) examples before PowerShell in all sections to signal platform neutrality.
  • Explicitly mention that Azure CLI works on Linux/macOS/Windows, while PowerShell is primarily for Windows (with cross-platform support but less common on Linux/macOS).
  • Add Bash script examples for deployment and resource management for Linux users.
  • Include a note on how to install and use Azure CLI on Linux/macOS.
  • Clarify that SSH/Kafka management steps are Linux-native and provide any necessary Windows SSH guidance (e.g., using Windows Terminal or WSL).
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/includes/hdinsight-selector-use-hive.md ...cles/hdinsight/includes/hdinsight-selector-use-hive.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation navigation prominently lists Windows-specific tools (PowerShell, .NET, Visual Studio) alongside cross-platform options, and Windows tools appear before Linux/macOS equivalents. This ordering and inclusion may suggest a Windows-centric approach, potentially making Linux/macOS users feel secondary.
Recommendations
  • Ensure Linux/macOS tools (such as Bash scripting, Linux CLI examples) are equally represented and not overshadowed by Windows tools.
  • Reorder the list to alternate or group by platform-neutral and platform-specific tools, or clearly label which tools are Windows-only.
  • Add explicit Linux/macOS equivalents for every Windows-specific tool or workflow mentioned.
  • Consider including a note about cross-platform compatibility for each tool or example.
GitHub Create Pull Request
← Previous Page 33 of 35 Next →