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 151-175 of 867 flagged pages
Hdinsight Non-interactive authentication .NET application - Azure HDInsight ...ate-non-interactive-authentication-dotnet-applications.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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias towards Windows environments. All code and tooling examples are for C#/.NET, which is historically Windows-centric, and NuGet package installation is shown using the Windows PowerShell syntax. There are no examples or guidance for running the application or managing dependencies on Linux or macOS, nor any mention of cross-platform .NET Core/SDK usage. The instructions for role assignment and authentication reference the Azure portal and PowerShell, both of which are more commonly used in Windows environments, with no mention of Azure CLI or Bash alternatives.
Recommendations
  • Add explicit instructions and examples for Linux and macOS environments, including .NET Core/SDK installation and usage.
  • Provide NuGet package installation examples using the dotnet CLI (cross-platform) instead of or in addition to PowerShell.
  • Include authentication and role assignment steps using Azure CLI commands, which are cross-platform, alongside or before PowerShell examples.
  • Clarify that the .NET application can be developed and run on Linux/macOS as well as Windows, and provide any necessary platform-specific notes.
  • Mention alternative editors and development environments (e.g., VS Code) that are available on Linux/macOS.
GitHub Create Pull Request
Hdinsight Apache Hadoop architecture - Azure HDInsight ...in/articles/hdinsight/hdinsight-hadoop-architecture.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 Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by referencing PowerShell cmdlets (e.g., Restore-AzDataLakeStoreDeletedItem) for file recovery in Azure Data Lake Storage Gen 1, without providing equivalent Linux/Unix CLI examples. The page also omits Linux-specific tools or commands for interacting with Azure storage, and does not mention cross-platform alternatives. This may hinder Linux users seeking parity in operational guidance.
Recommendations
  • Include Linux/Unix CLI examples (such as Azure CLI or REST API usage) alongside PowerShell cmdlets for all operations, especially file recovery and management.
  • Explicitly mention cross-platform tools (e.g., az CLI, curl for REST API) and provide usage examples for both Windows and Linux environments.
  • Where PowerShell is referenced, add a note or section for Linux users describing how to perform the same task using their preferred tools.
  • Review all operational guidance to ensure both Windows and Linux workflows are covered equally, and avoid assuming PowerShell as the default interface.
GitHub Create Pull Request
Hdinsight Apache Hadoop & secure transfer storage - Azure HDInsight ...oop-create-linux-clusters-with-secure-transfer-storage.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 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is given a dedicated section before Azure CLI, and the PowerShell cmdlet is described in detail. The CLI section is present, but PowerShell is listed first, and there are no explicit Linux shell or scripting examples (e.g., Bash). The documentation references Windows-centric tools (PowerShell) and patterns, with no mention of Linux-specific tools or workflows. There are no explicit Linux command-line examples or references to Linux shell environments.
Recommendations
  • Provide Bash or Linux shell examples for managing storage accounts, especially for secure transfer settings.
  • Alternate the order of PowerShell and Azure CLI sections, or present them together to avoid implying priority.
  • Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Add references to Linux-native tools or workflows where applicable (e.g., scripting with Bash, using curl for REST API calls).
  • Clarify that HDInsight clusters are Linux-based and provide guidance for Linux users where relevant.
GitHub Create Pull Request
Hdinsight Customize Azure HDInsight cluster configurations using bootstrap ...nsight/hdinsight-hadoop-customize-cluster-bootstrap.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 page demonstrates a strong Windows bias by providing extensive PowerShell examples and referencing the .NET SDK, both of which are Windows-centric tools. The only programmatic example is in PowerShell, and the appendix contains a full PowerShell script. There are no Linux shell (Bash) or cross-platform CLI examples for customizing HDInsight clusters. The prerequisites and instructions focus on Windows tools, and Linux alternatives are only mentioned in passing or in 'See also' links, not in the main instructional flow.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts to demonstrate cluster customization on Linux or cross-platform environments.
  • Include prerequisites and installation instructions for Linux tools (e.g., Azure CLI) alongside PowerShell.
  • Reorder sections so that cross-platform or Linux-native methods (such as Azure CLI or ARM templates) are presented before or alongside Windows/PowerShell methods.
  • Provide links to Linux-focused documentation in the main instructional flow, not just in 'See also' sections.
  • Explicitly state which methods are cross-platform and which are Windows-specific, helping users choose the appropriate tooling for their environment.
GitHub Create Pull Request
Hdinsight Tips for using Hadoop on Linux-based HDInsight - Azure ...ticles/hdinsight/hdinsight-hadoop-linux-information.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Mention Windows First
Summary
The documentation is generally Linux-focused, as expected for HDInsight on Linux, but there are some signs of Windows bias. Windows tools such as PowerShell and Visual Studio are mentioned as options for accessing Azure Data Lake Storage Gen1, and these are listed before or alongside Linux alternatives. The documentation also references the Azure portal (a web-based tool commonly used on Windows) and provides links to Windows-centric SDKs (.NET, Visual Studio) before some Linux-friendly options. However, most command-line examples use Bash and Linux utilities, and there is no exclusive use of Windows-only tools.
Recommendations
  • Provide Linux-specific alternatives for all Windows tools mentioned (e.g., alternatives to PowerShell and Visual Studio for Data Lake access).
  • When listing tools or SDKs, alternate the order or explicitly group Linux and Windows options to avoid implicit prioritization.
  • Include examples using Linux-native utilities (e.g., curl, jq, Bash scripts) wherever Windows tools are referenced.
  • Add explicit notes or sections for Linux users when referencing Windows-centric tools, clarifying how to achieve the same tasks on Linux.
  • Consider including cross-platform instructions for SDK installation and usage, highlighting both Linux and Windows environments.
GitHub Create Pull Request
Hdinsight Monitor and manage Hadoop with Ambari REST API - Azure HDInsight ...s/hdinsight/hdinsight-hadoop-manage-ambari-rest-api.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 demonstrates a moderate Windows bias. Windows and PowerShell are mentioned before Linux alternatives in prerequisites and examples. Windows-specific tools (PowerShell, Windows Subsystem for Linux) are highlighted, and some examples reference Windows paths and installation guides. While Bash examples are present, there is a tendency to frame Linux usage in the context of Windows (e.g., Bash on Ubuntu on Windows 10), and some PowerShell examples use jq in a Windows path. There is limited guidance for native Linux environments, and the documentation assumes Windows as the primary platform for many tasks.
Recommendations
  • Present Linux-native usage and examples before or alongside Windows/PowerShell equivalents, especially in prerequisites and setup sections.
  • Remove or de-emphasize references to 'Bash on Ubuntu on Windows 10' and instead provide instructions for native Linux shells.
  • Provide explicit instructions for installing and using jq and other tools on Linux, not just Windows.
  • Avoid Windows-specific paths (e.g., C:\HD\jq\jq-win64) in examples; provide Linux equivalents.
  • Clarify that all examples work natively on Linux, and provide troubleshooting tips for common Linux environments.
  • Mention Linux command-line tools and patterns where relevant, not just PowerShell or Windows alternatives.
  • Ensure parity in documentation for both platforms, including links to Linux-specific resources.
GitHub Create Pull Request
Hdinsight Use Azure Monitor logs to monitor Azure HDInsight clusters ...insight/hdinsight-hadoop-oms-log-analytics-tutorial.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 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are given in full detail and are presented before Azure CLI (Linux-friendly) examples in each relevant section. The use of PowerShell and references to the Az Module (a Windows-centric tool) are prominent, and the documentation assumes familiarity with Windows tooling. While Azure CLI examples are present, PowerShell is often listed first and in greater detail. There are no explicit Linux shell script examples beyond Azure CLI, and no mention of Linux-specific tools or patterns except for a brief reference to checking the OMI version with 'sudo'.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI (Linux-friendly) examples first.
  • Provide equivalent Linux shell script examples for common operations, especially for cluster management and monitoring tasks.
  • Explicitly mention that Azure CLI commands work natively on Linux/macOS and highlight their cross-platform nature.
  • Reduce reliance on PowerShell-specific instructions and provide parity in detail for Azure CLI examples.
  • Include troubleshooting or operational notes relevant to Linux environments (e.g., permissions, environment setup).
  • Reference Linux-native tools or patterns where appropriate (e.g., using bash scripts for automation).
GitHub Create Pull Request
Hdinsight Use SSH with Hadoop - Azure HDInsight ...icles/hdinsight/hdinsight-hadoop-linux-use-ssh-unix.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 🔧 Windows Tools
Summary
The documentation page provides a generally cross-platform overview of SSH usage with HDInsight, but exhibits subtle Windows bias. Windows tools and patterns (e.g., PowerShell, Windows-specific SSH clients) are mentioned before or more prominently than Linux equivalents in several places. Examples for cluster creation and management often use Azure PowerShell before Azure CLI, and the SSH key generation example is tagged as 'azurepowershell-interactive' despite being a standard Unix command. Windows SSH client installation is discussed in detail, while Linux/Unix/macOS are assumed to have the necessary tools. Graphical Windows SSH clients are listed, but no Linux GUI alternatives are mentioned. Some configuration instructions are explicitly stated to be for Linux/Unix, but Windows parity is not always clarified.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform and more common on Linux/macOS.
  • Remove or clarify the 'azurepowershell-interactive' tag from Unix commands like 'ssh-keygen' to avoid confusion.
  • Include Linux GUI SSH clients (e.g., GNOME Terminal, Konsole, Remmina) in the list of graphical clients, or note their existence.
  • Provide explicit instructions for installing SSH clients on Linux/macOS for completeness, even if they are usually pre-installed.
  • When discussing SSH configuration (e.g., agent forwarding), add equivalent steps or references for Windows clients (e.g., PuTTY, Windows OpenSSH config).
  • Ensure that all examples and instructions are presented in a platform-neutral order, or alternate the order to avoid implicit prioritization.
GitHub Create Pull Request
Hdinsight Use .NET with Hadoop MapReduce on Linux-based HDInsight - Azure .../hdinsight/hdinsight-hadoop-migrate-dotnet-to-linux.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 page demonstrates Windows bias by primarily referencing Windows-based tools and workflows, such as Visual Studio and the .NET Portability Analyzer (which is integrated into Visual Studio), and by providing step-by-step instructions that assume a Windows development environment. There are no examples or guidance for equivalent Linux-based development tools or workflows, and Windows file path conventions are mentioned without showing Linux alternatives.
Recommendations
  • Include instructions for using .NET Portability Analyzer or similar tools on Linux (e.g., via command line or cross-platform IDEs like VS Code).
  • Provide examples of building and testing .NET applications using Linux-native tools (e.g., Mono's command-line compiler, VS Code, JetBrains Rider).
  • Show file path examples using Linux conventions (e.g., /tmp/file.txt) alongside Windows examples.
  • Mention Linux alternatives for Visual Studio, or clarify cross-platform options for .NET development.
  • Add explicit steps for deploying and testing .NET solutions from a Linux development environment.
GitHub Create Pull Request
Hdinsight Managed identities in Azure HDInsight ...ain/articles/hdinsight/hdinsight-managed-identities.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 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by listing Azure PowerShell as a primary method for creating managed identities, referencing Microsoft Entra Domain Services (which is Windows-centric), and mentioning Windows authentication scenarios (LDAPS, ESP clusters) before Linux equivalents. There is no explicit Linux example or mention of Linux-specific tools or patterns, and PowerShell is highlighted before CLI, which is more cross-platform.
Recommendations
  • Provide explicit Linux-oriented examples and scenarios, such as using Azure CLI on Linux for managed identity creation and assignment.
  • List Azure CLI before Azure PowerShell when describing cross-platform steps, or clarify platform applicability for each method.
  • Include references to Linux authentication patterns and tools (e.g., Kerberos, PAM) where relevant.
  • Add a section or FAQ entry addressing managed identity usage and limitations on Linux-based HDInsight clusters.
  • Ensure parity in troubleshooting and operational guidance for both Windows and Linux clusters.
GitHub Create Pull Request
Hdinsight Plan a virtual network for Azure HDInsight ...hdinsight/hdinsight-plan-virtual-network-deployment.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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently presenting Azure PowerShell commands before Azure CLI commands, using PowerShell-heavy examples for resource discovery, and referencing Windows-centric tools and patterns. There is a lack of explicit Linux shell (bash) examples, and no mention of Linux-specific tools or workflows. The documentation assumes familiarity with PowerShell and Windows conventions, which may disadvantage Linux users.
Recommendations
  • Present Azure CLI (bash) examples before or alongside PowerShell examples to ensure parity for Linux users.
  • Include explicit bash shell command examples for resource discovery and management, not just Azure CLI syntax.
  • Reference Linux-native tools (e.g., curl, jq, grep) where appropriate, especially for tasks like DNS resolution or network troubleshooting.
  • Clarify that all operations can be performed from Linux environments, and provide guidance for Linux users where workflows differ.
  • Avoid Windows-centric terminology (e.g., 'enter the command' vs. 'run the command in your shell') and use neutral language.
  • Add a section or note on prerequisites for Linux users, such as installing Azure CLI and using bash.
  • Ensure that links to further documentation include Linux-focused resources and examples.
GitHub Create Pull Request
Hdinsight Manage logs for an HDInsight cluster - Azure HDInsight ...ob/main/articles/hdinsight/hdinsight-log-management.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 several signs of Windows bias. PowerShell is frequently mentioned as a primary scripting tool, often before or instead of Linux shell alternatives. Windows-centric tools (e.g., Visual Studio, Power Query for Excel, System Center) are referenced for log management and monitoring, while Linux-native tools and workflows are less emphasized or omitted. Examples and guidance for Linux command-line usage (aside from SSH and YARN CLI) are sparse, and scripting/automation is generally described with PowerShell as the default. The documentation also tends to mention Windows tools and approaches before their Linux equivalents, and does not provide parity in example scripts or tool recommendations.
Recommendations
  • Provide equivalent Linux shell script examples (e.g., Bash, Python) alongside PowerShell examples for log management tasks.
  • Mention Linux-native tools (e.g., grep, awk, sed, cron, rsync, logrotate) for log collection, rotation, and archiving, and give practical usage examples.
  • When referencing third-party monitoring tools, include Linux-friendly options and clarify platform compatibility.
  • Ensure that instructions for accessing logs via Azure CLI, SSH, and Ambari are as detailed as those for PowerShell and Windows tools.
  • Present Windows and Linux approaches in parallel, rather than listing Windows/PowerShell first or exclusively.
  • Expand guidance on automating log management with Linux scripting and open-source tools, not just PowerShell and .NET SDKs.
GitHub Create Pull Request
Hdinsight Enable Private Link on an Azure HDInsight cluster ...blob/main/articles/hdinsight/hdinsight-private-link.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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias in several ways: Windows is prioritized in VM deployment examples (with explicit use of Windows 10 Pro and RDP), PowerShell is mentioned before Azure CLI for cluster creation, and instructions for connectivity testing reference Windows tools (web browser, command prompt) without Linux equivalents. There are no Linux-specific examples or guidance for deploying or accessing clusters from Linux VMs, nor are SSH client instructions tailored for Linux users.
Recommendations
  • Include Linux VM deployment instructions and examples alongside Windows, such as using Ubuntu or CentOS images.
  • Provide Azure CLI examples before or alongside PowerShell, and clarify parity between the two.
  • Add Linux-specific steps for testing connectivity, such as using SSH from a Linux terminal and accessing Ambari via Firefox or Chromium.
  • Mention Linux tools (e.g., SSH, curl, browser options) and provide command-line examples for both Windows and Linux environments.
  • Ensure that all portal-based instructions are supplemented with CLI commands that work on Linux and Windows equally.
GitHub Create Pull Request
Hdinsight Manually scale a cluster - Azure HDInsight ...articles/hdinsight/hdinsight-scaling-best-practices.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 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. In the list of utilities for scaling clusters, PowerShell is listed first, and its example syntax is provided before Azure CLI (which is cross-platform). The use of PowerShell and references to Windows-centric tools (such as PowerShell Az and deprecated AzureRM) are prominent. While Linux/SSH examples are present for cluster management tasks, the initial emphasis on Windows tools and ordering suggests a Windows-first approach.
Recommendations
  • List cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell) in tables and examples.
  • Provide explicit Linux/macOS usage notes or examples where appropriate, especially for command-line utilities.
  • Clarify that Azure CLI is available on Windows, Linux, and macOS, and encourage its use for parity.
  • Reduce emphasis on deprecated Windows tools (e.g., AzureRM, Classic CLI) and focus on modern, cross-platform alternatives.
  • Where PowerShell examples are given, provide equivalent Bash or shell commands for Linux/macOS users.
GitHub Create Pull Request
Hdinsight Restrict access using Shared Access Signatures - Azure HDInsight ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-storage-sharedaccesssignature-permissions.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 demonstrates a Windows bias by presenting PowerShell examples first and in greatest detail, using Windows-specific CLI variable syntax, and referencing Visual Studio for C# development. The Azure CLI section uses Windows-style variable assignment (set VAR=VALUE) and notes that 'slight variations will be needed for bash or other environments' without providing actual bash/Linux equivalents. There are no explicit Linux shell examples for Azure CLI, nor is there parity in guidance for Linux users in the cluster creation steps, which are exclusively PowerShell-based.
Recommendations
  • Provide Azure CLI examples using bash syntax (e.g., export VAR=VALUE) alongside Windows examples.
  • Include cluster creation steps using Azure CLI or ARM templates, not only PowerShell.
  • Add instructions for using common Linux tools (e.g., VS Code, JetBrains Rider) for C# development, or clarify cross-platform options.
  • Ensure all code samples and variable assignments are shown for both Windows (cmd/PowerShell) and Linux (bash/zsh) environments.
  • Reorder sections or provide parallel examples so Linux and Windows users are equally supported.
  • Explicitly mention and link to Linux-specific documentation where relevant.
GitHub Create Pull Request
Hdinsight Troubleshoot a slow or failing job on Azure HDInsight cluster ...les/hdinsight/hdinsight-troubleshoot-failed-cluster.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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. While it does mention Linux-based clusters and Linux tools (Ambari, curl, netstat), it repeatedly references Windows-specific tools and patterns, such as Azure PowerShell and the Azure portal, often before or in addition to Linux equivalents. PowerShell is suggested as an alternative to Azure CLI, but no Linux shell or scripting examples are provided. The documentation also references Windows-style paths (e.g., backslashes in log file locations) and omits explicit Linux command-line examples for some tasks.
Recommendations
  • Provide Linux shell (bash) and scripting examples alongside or before PowerShell examples.
  • Clarify that Azure CLI and Ambari UI are cross-platform, and provide usage instructions for Linux and macOS.
  • Use platform-neutral path formats (forward slashes) when describing file locations.
  • Include instructions for accessing cluster information and logs from Linux terminals, not just via the Azure portal or PowerShell.
  • Explicitly mention Linux tools (e.g., SSH, SCP, tail, grep) for log analysis and troubleshooting.
  • Ensure that troubleshooting steps do not assume the use of Windows tools or interfaces.
GitHub Create Pull Request
Hdinsight Tutorial: ETL operations with Interactive Query - Azure HDInsight ...uery/interactive-query-tutorial-analyze-flight-data.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 🔧 Windows Tools
Summary
The documentation demonstrates mild Windows bias. While the main tutorial steps use Linux/Unix commands (scp, ssh, bash, FreeTDS, etc.), there are several signs of Windows prioritization: the instructions for deleting clusters mention Windows tools (PowerShell) before Linux equivalents (Azure CLI), and the phrase 'open a command prompt' is used instead of 'terminal', which is more neutral or Linux-friendly. There are no explicit Linux examples missing, but Windows terminology and tools are referenced first or exclusively in some places.
Recommendations
  • Use platform-neutral terminology such as 'terminal' instead of 'command prompt'.
  • When listing tools for cluster deletion, mention Azure CLI before or alongside PowerShell, and provide explicit Bash/Azure CLI examples.
  • Ensure that any references to Windows tools (e.g., PowerShell) are balanced with Linux equivalents, and provide step-by-step instructions for both platforms where relevant.
  • Review all links and references to ensure Linux users are equally supported, especially in sections about resource management and cleanup.
GitHub Create Pull Request
Hdinsight Enable automatic topic creation in Apache Kafka - Azure HDInsight ...les/hdinsight/kafka/apache-kafka-auto-create-topics.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 page demonstrates a Windows bias by referencing PowerShell and Resource Manager templates for cluster creation, without mentioning or providing equivalent Linux command-line examples (e.g., Bash, CLI). Windows tools and patterns (PowerShell, Azure portal) are mentioned first and exclusively, while Linux-native approaches are absent.
Recommendations
  • Add examples for enabling auto topic creation using Linux command-line tools, such as Bash scripts or Azure CLI.
  • Mention Linux-based cluster creation workflows alongside PowerShell and Resource Manager templates.
  • Provide parity in instructions for both Windows and Linux users, ensuring that steps are not limited to Windows-specific tools.
  • Include references to Linux-friendly management interfaces or automation methods, such as using curl for Ambari REST API or scripting with Bash.
GitHub Create Pull Request
Hdinsight Azure Toolkit for Eclipse: Create Scala apps for HDInsight Spark ...es/hdinsight/spark/apache-spark-eclipse-tool-plugin.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 a Windows bias primarily in the section about running Spark Scala applications locally. It exclusively discusses the need for WinUtils.exe and setting HADOOP_HOME on Windows, without mentioning Linux or macOS equivalents or requirements. No Linux-specific troubleshooting or environment setup is provided, and the only local run example is Windows-centric. There are no examples or notes for Linux users, and Windows tools/patterns are mentioned exclusively and first.
Recommendations
  • Add instructions for running Spark Scala applications locally on Linux and macOS, including any required environment variables or troubleshooting steps.
  • Include notes on differences in local Spark setup between Windows, Linux, and macOS, such as the absence of WinUtils.exe requirement on non-Windows platforms.
  • Provide Linux/macOS-specific error messages and solutions if applicable.
  • Explicitly state platform compatibility for all steps, especially those that are Windows-specific.
  • Offer parity in troubleshooting and setup guidance for Linux users, ensuring examples and patterns are not Windows-exclusive.
GitHub Create Pull Request
Hdinsight What is Interactive Query in Azure HDInsight? ...eractive-query/apache-interactive-query-get-started.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 a Windows bias by prioritizing Microsoft-centric tools (Power BI, Visual Studio, Visual Studio Code, Hive ODBC/Excel) in its examples and tool recommendations. Linux-native tools and workflows (such as command-line Beeline, Ambari Hive View, Zeppelin) are mentioned after Windows tools or with less detail. There are no explicit Linux command-line examples or references to Linux-specific patterns for accessing Hive LLAP, and the documentation omits guidance for Linux users on connecting via CLI or scripting.
Recommendations
  • Provide explicit Linux command-line examples for connecting to Hive LLAP using Beeline, including sample commands and authentication methods.
  • Include instructions for using Linux-native BI tools (e.g., Apache Zeppelin, DBeaver, SquirrelSQL) to connect to Interactive Query clusters.
  • Balance the order of tool presentation so that Linux and cross-platform options (Ambari Hive View, Beeline, Zeppelin) are listed before or alongside Windows-specific tools.
  • Add a section or table clarifying which tools are cross-platform and which are Windows-only, helping users choose appropriate options for their OS.
  • Offer guidance for scripting and automation from Linux environments, such as using Bash scripts with Beeline or JDBC clients.
GitHub Create Pull Request
Hdinsight Connect HDInsight Kafka cluster with client VM in different VNet on Azure HDInsight ...in/articles/hdinsight/kafka/connect-kafka-with-vnet.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation provides instructions for both Linux and Windows client VMs, but there are signs of Windows bias. Windows-specific instructions (such as editing the hosts file at C:\Windows\System32\drivers\etc\) are called out in a dedicated section, and Windows steps are described in more detail (including screenshots and credential instructions). The Linux section is shorter and only provides a curl example, lacking parity in step-by-step guidance. Additionally, some generic instructions (e.g., using Ambari UI) are written in a way that assumes Windows users (browser-based, credential prompts), and Windows terminology ("overview page") is used before Linux equivalents. There is also a lack of Linux-specific troubleshooting or tool recommendations, and no PowerShell or Linux shell command examples for VM creation or configuration.
Recommendations
  • Provide Linux and Windows instructions in parallel, with equal detail and screenshots for both platforms.
  • Include Linux-specific troubleshooting steps, such as SELinux, firewall, or network configuration issues.
  • Add Linux shell command examples for VM creation, hosts file editing, and Kafka topic management.
  • Mention Linux tools (e.g., nano, vi, systemctl) where relevant, not just Windows tools.
  • Ensure terminology is platform-neutral (e.g., 'hosts file location' instead of only Windows path).
  • Add PowerShell and Bash examples for common tasks, and clarify differences between platforms.
  • Review the order of presentation so that Linux instructions are not always after Windows ones.
GitHub Create Pull Request
Hdinsight Apache Kafka REST proxy - Azure HDInsight ...-docs/blob/main/articles/hdinsight/kafka/rest-proxy.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 page demonstrates a Windows bias by referencing PowerShell and the Azure Portal as primary management interfaces, mentioning PowerShell before alternatives, and omitting explicit Linux shell or cross-platform command-line examples for cluster and security group management. While the client sample uses Python (cross-platform), administrative instructions and references favor Windows-centric tools and workflows.
Recommendations
  • Provide equivalent Linux shell (bash) and Azure CLI examples for all administrative tasks, such as registering applications, managing security groups, and cluster creation.
  • Explicitly mention that the Python client sample works on both Windows and Linux, and provide Linux-specific instructions for installing dependencies and running the script.
  • Include references to Linux tools and workflows (e.g., Azure CLI, bash scripts) alongside or before Windows/PowerShell instructions.
  • Add curl examples using bash syntax, and clarify usage on Linux systems.
  • Review all screenshots and instructions to ensure they are not Windows/PowerShell specific, or provide Linux alternatives where appropriate.
GitHub Create Pull Request
Hdinsight Monitor Azure HDInsight ...docs/blob/main/articles/hdinsight/monitor-hdinsight.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates mild Windows bias by referencing PowerShell and Azure CLI as the primary command-line tools for enabling monitoring integration, without mentioning Linux-native alternatives or providing Bash examples. The Azure portal (a web UI) is emphasized, which is cross-platform, but command-line instructions are Windows-centric. There are no explicit Linux/Bash examples or references to Linux-specific tools for cluster monitoring, despite HDInsight clusters being Linux-based and Ambari being available only on Linux.
Recommendations
  • Provide Bash shell examples alongside PowerShell and Azure CLI for enabling and managing Azure Monitor integration.
  • Explicitly mention that Azure CLI is cross-platform and can be used from Linux, macOS, and Windows, and provide sample commands for Linux users.
  • Include references to Linux-native monitoring tools or scripts where relevant, especially since HDInsight clusters are Linux-based.
  • Ensure that instructions for script actions, log management, and selective logging include both Windows (PowerShell) and Linux (Bash) command examples.
  • Clarify any platform-specific requirements or differences in the monitoring workflow for Linux users.
GitHub Create Pull Request
Hdinsight Connect to Kafka using virtual networks - Azure HDInsight ...es/hdinsight/kafka/apache-kafka-connect-vpn-gateway.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 page demonstrates a significant Windows bias. Most infrastructure setup and resource management steps are provided exclusively as PowerShell scripts, with no equivalent Bash or Linux shell examples. The instructions for connecting to Azure and configuring resources assume the use of PowerShell, which is primarily a Windows tool. While there is a brief mention that the VPN client can be used with both Windows and macOS, there are no explicit Linux instructions or examples for the setup process. The Python client example does include a Bash pip install command, but all Azure resource queries and setup are shown in PowerShell first, with only one Azure CLI example provided as an alternative. There are no Linux-native or cross-platform shell scripts for the main setup workflow.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for all PowerShell examples, especially for resource creation and management steps.
  • Explicitly mention Linux as a supported platform for VPN client configuration and provide step-by-step instructions for Linux users.
  • Include Linux-specific guidance for certificate management and VPN client installation.
  • Ensure that Azure CLI commands are presented alongside PowerShell commands, not just as an afterthought.
  • Add troubleshooting and usage notes for Linux environments, such as differences in file paths, permissions, and tool availability.
GitHub Create Pull Request
Hdinsight Quickstart: Apache Kafka using Bicep - HDInsight ...icles/hdinsight/kafka/apache-kafka-quickstart-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 deployment and resource management instructions using both Azure CLI and Azure PowerShell, but PowerShell examples are always presented alongside or immediately after CLI examples, suggesting parity but still giving Windows users equal prominence. There is no explicit mention of Linux-specific tools or shell environments (e.g., Bash scripting, Linux package managers beyond 'apt'), nor are Linux desktop workflows (such as using native terminals or editors) discussed. The use of SSH and Bash commands for Kafka management is platform-neutral, but the initial deployment steps and resource management examples could be perceived as Windows-biased due to the inclusion and prominence of PowerShell. There are no examples or guidance for Linux users who might prefer Bash scripting for resource deployment, nor is there mention of cross-platform differences in Azure CLI or PowerShell usage.
Recommendations
  • Present Azure CLI examples before PowerShell examples, or clearly indicate CLI as the cross-platform/default option.
  • Add explicit guidance for Linux users, such as using Bash scripts for deployment and resource management.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and provide installation links for each platform.
  • Include a note that PowerShell examples are primarily for Windows users, and suggest Bash alternatives for Linux/macOS.
  • Where possible, add Linux desktop workflow tips (e.g., using native terminals, editors, or package managers).
GitHub Create Pull Request
← Previous Page 7 of 35 Next →