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 326-350 of 867 flagged pages
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-sales-insights-etl.md ...ain/articles/hdinsight/hdinsight-sales-insights-etl.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates bias toward Windows environments by providing PowerShell as the only explicit CLI scripting example for triggering the Data Factory pipeline, referencing Power BI Desktop (Windows-only), and mentioning the Az PowerShell module in prerequisites. There is no Linux equivalent for triggering the pipeline (e.g., Bash/Azure CLI), and Windows tools/patterns are referenced before Linux alternatives. The tutorial does not offer parity for Linux users in key steps.
Recommendations
  • Provide Bash/Azure CLI examples for triggering Data Factory pipelines alongside PowerShell.
  • Explicitly mention and provide steps for using Power BI service (web-based) as an alternative to Power BI Desktop for non-Windows users.
  • List both Az PowerShell and Azure CLI as options in prerequisites for automation tasks.
  • Ensure that all major steps (especially automation and visualization) have Linux-compatible instructions and examples.
  • Where Windows-specific tools are referenced, add notes or alternatives for Linux/macOS users.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-log-management.md ...ob/main/articles/hdinsight/hdinsight-log-management.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 through frequent and early mention of PowerShell and Windows-centric tools (e.g., Visual Studio, Power Query for Excel, System Center), often before or instead of Linux equivalents. PowerShell is repeatedly suggested for log management and scripting, while Linux-native tools and scripting options are less emphasized or only mentioned later. Some examples and tool recommendations (e.g., AzCopy, Visual Studio Server Explorer) are Windows-focused, and Linux alternatives (such as Bash scripting, Linux log management utilities) are underrepresented or missing. Although SSH and Ambari (Linux-based) are mentioned, scripting and automation examples are predominantly Windows/PowerShell oriented.
Recommendations
  • Provide equivalent Linux/Bash scripting examples alongside PowerShell for all automation and log management tasks.
  • List Linux-native tools (e.g., rsync, scp, logrotate, cron jobs) for log collection, archiving, and rotation, and give them equal prominence.
  • When referencing tools like Visual Studio or Power Query for Excel, also mention cross-platform or Linux alternatives (e.g., Jupyter Notebooks, LibreOffice Calc, CLI-based analysis tools).
  • Include explicit examples of using Linux utilities (e.g., grep, awk, sed) for log analysis and management.
  • Ensure that third-party monitoring and log management solutions for Linux are highlighted equally with Windows-centric options.
  • Where PowerShell is referenced for scripting, provide parallel Bash or Python examples for Linux users.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-private-link.md ...blob/main/articles/hdinsight/hdinsight-private-link.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in several areas. When providing instructions for testing cluster connectivity, only a Windows 10 VM is used as the example, with RDP as the access method. The instructions for testing SSH access begin with opening a Windows command prompt, with no mention of Linux or cross-platform alternatives. References to PowerShell are present, and while Azure CLI is mentioned, the PowerShell example is listed first. There are no explicit Linux VM deployment examples, nor are Linux-specific tools or patterns discussed.
Recommendations
  • Include Linux VM deployment instructions and examples alongside Windows VM instructions for connectivity testing.
  • Provide SSH testing steps using native Linux/macOS terminals, not just Windows command prompt.
  • Present Azure CLI and PowerShell examples together, or alternate which is listed first.
  • Mention cross-platform tools (e.g., OpenSSH, Bash) where relevant, and avoid assuming Windows-only environments.
  • Clarify that the steps are applicable to both Windows and Linux environments, and provide parity in screenshots and configuration tables.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/includes/hdinsight-selector-use-mapreduce.md ...hdinsight/includes/hdinsight-selector-use-mapreduce.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page lists PowerShell and .NET SDK (Windows-centric tools) as primary options for interacting with HDInsight MapReduce, with PowerShell mentioned before Linux-native alternatives like SSH and Curl. There is an implicit Windows bias in the ordering and selection of tools, as Linux equivalents (e.g., Bash scripting, Python SDK) are not highlighted or provided as alternatives.
Recommendations
  • Reorder the options to alternate or group Windows and Linux tools equally, avoiding Windows-first presentation.
  • Add explicit Linux-native examples, such as Bash scripting or Python SDK usage, alongside PowerShell and .NET SDK.
  • Include a note clarifying cross-platform compatibility and suggesting equivalent Linux workflows.
  • Ensure that documentation for Linux tools is as detailed and prominent as that for Windows tools.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/interactive-query/apache-interactive-query-get-started.md ...eractive-query/apache-interactive-query-get-started.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows-centric tools (Power BI, Visual Studio, Excel with Hive ODBC) in the list of methods for executing Hive queries. These tools are mentioned before cross-platform or Linux-native options (Ambari Hive View, Beeline). There are no explicit Linux command-line examples or references to Linux-specific workflows, and the documentation lacks parity in showcasing Linux-friendly alternatives or examples.
Recommendations
  • Include explicit Linux command-line examples for connecting to Hive via Beeline, such as sample shell commands.
  • Highlight cross-platform tools (e.g., Apache Zeppelin, Beeline) earlier in the list, or group methods by platform to clarify parity.
  • Add references to Linux-native BI tools or open-source alternatives for data visualization and query execution.
  • Provide instructions for accessing Hive from a Linux terminal, including authentication and connection steps.
  • Balance the documentation by mentioning Linux workflows alongside Windows tools, ensuring equal visibility and guidance.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-managed-identities.md ...ain/articles/hdinsight/hdinsight-managed-identities.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell as a primary method for creating managed identities, referencing Windows-centric tools and patterns (PowerShell, certificates), and mentioning PowerShell before Azure CLI. There is no explicit Linux example or parity in scripting or tooling, and the use of certificates is described in a way that aligns more closely with Windows administration practices.
Recommendations
  • Provide explicit Linux examples for managed identity creation and usage, such as bash scripts or Linux-native tools.
  • List Azure CLI before Azure PowerShell when presenting cross-platform options, as CLI is available on both Windows and Linux.
  • Clarify certificate distribution steps for both Windows and Linux cluster nodes, including Linux-friendly methods (e.g., using OpenSSL, scp, or cloud-init).
  • Include troubleshooting and operational guidance for Linux users, ensuring that all instructions are platform-agnostic or have Linux-specific notes where appropriate.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-storage-sharedaccesssignature-permissions.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-storage-sharedaccesssignature-permissions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias by presenting PowerShell examples first and in greater detail, using Windows-centric variable syntax and tools (e.g., 'set' for environment variables), and referencing Visual Studio for C#. The Azure CLI section is written for Windows CMD, with only a brief mention that 'bash or other environments' require 'slight variations', but no actual bash/Linux examples are provided. There is no parity in Linux-specific instructions for Azure CLI or cluster creation, and the Python section is minimal compared to the extensive PowerShell walkthrough.
Recommendations
  • Provide Azure CLI examples using bash syntax (e.g., 'export VAR=value') alongside Windows CMD examples.
  • Include instructions for cluster creation using Azure CLI (not just PowerShell), with Linux shell commands.
  • Add Linux-specific notes or examples for file paths and environment setup, especially for Python and CLI usage.
  • Reference cross-platform editors (e.g., VS Code) in addition to Visual Studio for C# development.
  • Ensure all major workflows (SAS creation, cluster configuration) have both Windows and Linux command examples.
  • Explicitly call out differences in command usage between Windows and Linux environments, rather than assuming familiarity.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-troubleshoot-failed-cluster.md ...les/hdinsight/hdinsight-troubleshoot-failed-cluster.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 provides some Linux-centric instructions (e.g., Ambari UI, curl, netstat), it frequently references Windows tools and patterns. PowerShell is mentioned as a primary management option, and Windows-centric tools (Azure portal, PowerShell) are listed before Linux alternatives (Azure CLI, Ambari UI). Some instructions and log paths use Windows-style notation (backslashes), and there is a lack of parity in example commands for Linux vs. Windows environments.
Recommendations
  • Provide equivalent Linux shell commands wherever PowerShell is referenced, and vice versa.
  • Ensure that Azure CLI examples are given equal prominence to PowerShell, and consider listing CLI examples before PowerShell to avoid 'windows_first' bias.
  • Use platform-agnostic notation for file paths (forward slashes for Linux, backslashes for Windows, or both).
  • Explicitly state which instructions apply to Linux-based clusters and which to Windows-based clusters, and provide examples for both where relevant.
  • Expand troubleshooting steps to include SSH-based access and Linux-native tools (e.g., journalctl, systemctl) where appropriate.
  • Review all sections for implicit assumptions about the user's operating system and clarify or balance them.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-with-entra-authentication/run-map-reduce-rest-jobs.md ...-with-entra-authentication/run-map-reduce-rest-jobs.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting command-line examples primarily in Windows-centric formats (CMD and PowerShell), referencing Windows environment variables (e.g., 'set TOKEN'), and using Windows-specific tools and syntax. Linux equivalents (such as Bash syntax for variable assignment and command chaining) are not provided, and the examples are explicitly stated to be 'based on a Windows environment.' There is no explicit guidance or examples for Linux/macOS users, despite mentioning curl and jq as prerequisites.
Recommendations
  • Provide parallel examples for Linux/macOS environments, including Bash syntax for variable assignment (e.g., 'TOKEN=<access_token>'), command chaining, and line continuation (using '\' instead of '^').
  • Clearly indicate which examples are for Windows and which are for Linux/macOS, or provide a unified cross-platform example.
  • Include instructions for installing curl and jq on both Windows and Linux/macOS.
  • Add PowerShell Core examples for cross-platform compatibility, or clarify when Windows-only PowerShell is required.
  • Avoid using Windows-specific command-line tools and patterns (such as 'set' and '^') without offering Linux alternatives.
  • Explicitly mention any differences in command usage or environment setup between Windows and Linux/macOS.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/kafka/apache-kafka-auto-create-topics.md ...les/hdinsight/kafka/apache-kafka-auto-create-topics.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references configuring Kafka via Ambari (web UI and REST API) and during cluster creation through PowerShell or Resource Manager templates. PowerShell is mentioned as a method for configuration, but there are no equivalent Linux CLI or Bash examples. The documentation does not provide Linux-centric instructions or mention Linux tools (such as Bash scripts or Azure CLI) for cluster creation or configuration, and Windows/PowerShell methods are referenced before any Linux alternatives.
Recommendations
  • Add examples for configuring Kafka using Azure CLI (cross-platform) and Bash scripts.
  • Mention Linux-compatible methods for cluster creation and configuration alongside PowerShell, such as using Bash or Azure CLI.
  • Ensure that instructions for both Windows and Linux environments are provided and presented with equal prominence.
  • Where PowerShell is referenced, also provide the equivalent Bash or shell commands.
  • Explicitly state that Resource Manager templates can be deployed from any OS, and provide sample deployment commands for both Windows (PowerShell) and Linux (Bash/Azure CLI).
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/kafka/rest-proxy.md ...-docs/blob/main/articles/hdinsight/kafka/rest-proxy.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily by referencing PowerShell and Azure Portal for management tasks, mentioning PowerShell before any Linux alternatives, and omitting explicit Linux command-line examples for cluster creation and security group management. The only CLI sample for cluster creation is deferred to a separate page, and there is no mention of Linux-specific tools or shell commands for authentication or resource management. The Python sample is cross-platform, but the overall workflow and instructions assume a Windows-centric environment.
Recommendations
  • Add explicit Linux shell (bash) examples for authentication and resource management, such as using Azure CLI for security group registration and OAuth token retrieval.
  • Reference Azure CLI and bash commands alongside PowerShell in all relevant sections, not just in a separate tutorial.
  • Include instructions for managing Microsoft Entra security groups and application registration using Azure CLI or REST API, with Linux-friendly command syntax.
  • Ensure that all screenshots and workflow descriptions are platform-neutral or provide alternatives for Linux users.
  • Clarify that the Python sample is cross-platform and provide Linux-specific instructions for installing dependencies and running the sample.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-intellij-tool-plugin.md ...s/hdinsight/spark/apache-spark-intellij-tool-plugin.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exhibits Windows bias primarily through the requirement and emphasis on WINUTILS.EXE for local Spark console execution, which is a Windows-only tool. The prerequisite and configuration steps for running Spark locally explicitly mention WINUTILS.EXE and HADOOP_HOME, both of which are relevant only for Windows environments. There are no equivalent instructions or troubleshooting steps for Linux or macOS users, nor is there guidance on how to run Spark locally on those platforms. Additionally, the documentation does not provide parity in examples or troubleshooting for non-Windows operating systems, and references to Power BI (a Windows-centric BI tool) reinforce the Windows-first approach.
Recommendations
  • Add explicit instructions for running Spark locally on Linux and macOS, including any required environment variables, dependencies, or troubleshooting steps.
  • Clarify that WINUTILS.EXE is only required for Windows, and provide alternative steps for Linux/macOS users (e.g., omitting WINUTILS.EXE and setting HADOOP_HOME appropriately).
  • Include example screenshots and configuration dialogs from Linux/macOS environments to ensure parity.
  • Mention cross-platform BI tools alongside Power BI, or provide Linux/macOS alternatives where appropriate.
  • Review all prerequisite and configuration sections to ensure that Linux and macOS users are not left out or confused by Windows-specific instructions.
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-08 00:53
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-centric tools (Visual Studio, PowerShell) and providing next steps that focus on Windows environments. There are no Linux-specific examples or mentions of Linux tools for cluster management or query execution, and Windows tools are mentioned before any Linux alternatives.
Recommendations
  • Include examples for managing HDInsight clusters using Linux tools and shell commands (e.g., Bash, Azure CLI on Linux).
  • Add next steps or links for running Hive queries from Linux environments, such as using Beeline, Hive CLI, or Zeppelin on Linux.
  • Mention Linux-compatible editors and IDEs (e.g., VS Code, IntelliJ) for Hive development.
  • Ensure parity in instructions for deleting clusters, showing both PowerShell (Windows) and Bash/Azure CLI (Linux/macOS) usage.
  • Balance references to Windows tools (Visual Studio, PowerShell) with Linux equivalents throughout the documentation.
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
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation navigation lists Windows-centric tools (PowerShell, .NET, Visual Studio) alongside cross-platform options (Beeline, Curl), but Windows tools are given equal or greater prominence and are listed before any explicit Linux shell or CLI examples. There is no clear Linux shell or Bash example, and Windows-specific tools are highlighted without Linux equivalents.
Recommendations
  • Add explicit Linux/Bash shell examples and links (e.g., using Hive CLI from Bash).
  • Ensure cross-platform tools (Beeline, Curl) are listed before Windows-specific tools.
  • Include Linux equivalents for PowerShell and Visual Studio, such as Bash scripts or VS Code usage.
  • Clearly indicate which tools are cross-platform and which are Windows-only.
  • Balance the documentation so that Linux and Windows users have equal guidance and visibility.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/service-endpoint-policies.md ...b/main/articles/hdinsight/service-endpoint-policies.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by providing both Azure PowerShell and Azure CLI examples, but the CLI example is written using PowerShell-style variable assignment and syntax, which is not compatible with Bash or Linux shells. The PowerShell example is given in full, while there is no example using Bash or native Linux shell scripting. The use of PowerShell is prominent and the CLI example is not Linux-friendly, making it difficult for Linux users to follow without translation.
Recommendations
  • Provide a Bash-native Azure CLI example, using standard Bash variable assignment and array syntax.
  • Clearly distinguish between PowerShell and Bash examples, labeling them appropriately.
  • Ensure that all CLI instructions are compatible with Linux shells, avoiding PowerShell-specific syntax in CLI sections.
  • Add a section explicitly for Linux users, demonstrating the process using Bash and Linux tools.
  • Review and update variable assignment and array usage in CLI examples to follow Bash conventions (e.g., VAR=value, arrays with parentheses, etc.).
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-intellij-tool-debug-remotely-through-ssh.md ...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-08 00:53
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 addressing Windows-specific issues (WinUtils.exe) prominently in the prerequisites, providing detailed steps for resolving them, and referencing Windows environment variables and paths (C:\WinUtils). There is no equivalent troubleshooting or setup guidance for Linux/macOS users, and the only explicit OS-specific instructions are for Windows. Linux and macOS are mentioned only to say that the Windows workaround is not needed, without further detail or parity in examples.
Recommendations
  • Add explicit instructions or troubleshooting steps for Linux/macOS users, even if only to confirm that no extra configuration is needed.
  • Provide Linux/macOS equivalents for environment variable setup and clarify where relevant files or configurations would reside.
  • Balance the order of presentation so that Windows-specific steps do not appear first or exclusively; consider grouping OS-specific instructions together.
  • Include notes or examples for common Linux/macOS SSH clients and any potential issues users might encounter on those platforms.
  • Ensure that all screenshots, paths, and configuration examples are either cross-platform or have platform-specific variants.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-overview.md ...main/articles/hdinsight/spark/apache-spark-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 in several ways: Windows-centric tools and patterns (Azure PowerShell, .NET SDK, Microsoft Power BI) are mentioned first or exclusively when describing cluster creation and BI integration. There is no mention of Linux-native tools or command-line examples (e.g., Bash, SSH, Azure CLI for Linux) for cluster management. The documentation focuses on Microsoft ecosystem tools, omitting Linux equivalents or open-source alternatives, and does not provide Linux-specific usage scenarios or examples.
Recommendations
  • Include Azure CLI (cross-platform) examples for cluster creation and management alongside or before Azure PowerShell and .NET SDK.
  • Provide explicit Bash or SSH command examples for interacting with HDInsight clusters from Linux environments.
  • Mention and demonstrate integration with Linux-friendly BI tools (e.g., Apache Superset, Grafana) in addition to Power BI.
  • Add guidance for accessing Jupyter and Zeppelin notebooks from Linux desktops, including browser and authentication tips.
  • Highlight open-source alternatives to Microsoft tools where appropriate, and clarify platform compatibility for all SDKs and plugins.
  • Ensure that all tutorials and quickstarts provide both Windows and Linux command-line instructions.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-eclipse-tool-plugin.md ...es/hdinsight/spark/apache-spark-eclipse-tool-plugin.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits Windows bias primarily in the 'Run a Spark Scala application locally' section, where only Windows-specific instructions and troubleshooting (WinUtils.exe, HADOOP_HOME environment variable) are provided. There is no mention of Linux or macOS equivalents, nor guidance for running locally on non-Windows systems. The prerequisites and setup steps do not clarify OS-specific differences, and the troubleshooting is exclusively for Windows users.
Recommendations
  • Add instructions for running local Spark Scala applications on Linux and macOS, including any required environment variables or dependencies.
  • Clarify OS-specific prerequisites and troubleshooting steps, such as how to resolve common issues on Linux/macOS (e.g., permissions, PATH settings).
  • Mention that WinUtils.exe is only required for Windows, and explain that Linux/macOS do not need this file.
  • Provide parity in examples and troubleshooting for all major platforms, not just Windows.
  • Explicitly state supported operating systems for the Azure Toolkit for Eclipse and any limitations or differences in behavior.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-intellij-tool-plugin-debug-jobs-remotely.md ...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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits several Windows-centric biases. It provides explicit instructions and examples for Windows environments, such as editing the hosts file using Notepad and handling WinUtils.exe errors, while omitting equivalent steps for Linux or macOS. PowerShell is mentioned as a primary method for networking setup, with no Bash or Linux CLI alternatives. The workaround for SPARK-2356 is described only for Windows, and the artifact paths and instructions use Windows-style paths. Linux-specific instructions are referenced only indirectly or in linked documents, not in the main workflow.
Recommendations
  • Add explicit instructions for editing the hosts file on Linux and macOS, including file paths and editor commands (e.g., using sudo nano /etc/hosts).
  • Provide Linux/macOS alternatives for the WinUtils.exe workaround, or clarify that it is not needed on those platforms.
  • Include Bash or Azure CLI examples alongside PowerShell for networking and VPN setup.
  • Use cross-platform file path examples (e.g., <project directory>/src) and clarify differences between Windows and Linux/macOS paths.
  • Mention and illustrate how to copy files from the cluster using native Linux/macOS tools (e.g., scp from a terminal) without requiring Cygwin.
  • Clearly state which steps are platform-specific and provide guidance for users on Linux and macOS throughout the workflow.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/use-pig.md ...ocs/azure-docs/blob/main/articles/hdinsight/use-pig.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively mentioning SQL Server Integration Services (SSIS) and its Azure Feature Pack as a method for running Pig jobs, without referencing any Linux-native or cross-platform alternatives. There are no examples or walkthroughs for running Pig jobs via Linux tools, command-line interfaces, or SSH, and Windows-centric tools are presented as the primary integration method.
Recommendations
  • Add examples and walkthroughs for running Pig jobs using Linux command-line tools (e.g., SSH, Bash, curl) and native Hadoop/Pig commands.
  • Include instructions for submitting Pig jobs from Linux or macOS environments, such as using the Pig shell or Hadoop CLI.
  • Mention and link to cross-platform tools (e.g., PuTTY for Windows, OpenSSH for Linux/macOS) for connecting to HDInsight clusters.
  • Balance the presentation of Windows-specific integration (SSIS) with Linux-native or open-source workflow options.
  • Ensure that any references to Windows tools are paired with equivalent Linux/macOS alternatives, and avoid presenting Windows tools first or exclusively.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-use-bi-tools.md .../articles/hdinsight/spark/apache-spark-use-bi-tools.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 and tools. All examples for connecting to Spark and visualizing data use Power BI Desktop, which is primarily a Windows application. There are no examples or guidance for Linux users or alternative BI tools available on Linux. The instructions for deleting clusters mention PowerShell and browser, but do not provide explicit Linux command-line examples or prioritize Azure CLI, which is cross-platform.
Recommendations
  • Include instructions and examples for using Power BI on the web, which is accessible from Linux and macOS.
  • Mention and provide examples for alternative BI tools that work on Linux (e.g., Tableau, Apache Superset, Grafana) for connecting to Spark clusters.
  • When discussing cluster deletion, provide explicit Azure CLI commands and examples, and mention that Azure CLI is cross-platform.
  • Add a section or note clarifying platform compatibility for each tool and step, and suggest Linux/macOS alternatives where appropriate.
  • Ensure screenshots and UI references are not exclusively Windows-centric, or provide parallel instructions for Linux/macOS users.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-connect-excel-power-query.md ...ight/hadoop/apache-hadoop-connect-excel-power-query.md
High Priority View Details →
Scanned: 2026-01-06 18:15
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows environments, requiring a Windows workstation and Microsoft Excel. All instructions and examples are tailored to Windows and Microsoft Office products, with no mention of Linux-compatible alternatives for connecting to HDInsight or accessing Hadoop data. The prerequisites and step-by-step guides exclusively reference Windows operating systems and tools, omitting any guidance for Linux users.
Recommendations
  • Provide equivalent instructions for Linux users, such as using LibreOffice Calc, OpenOffice, or other BI tools available on Linux to connect to HDInsight.
  • Include examples of accessing HDInsight data from Linux workstations, possibly via Python (pandas, pyodbc), R, or command-line tools.
  • Mention cross-platform alternatives to Power Query, or clarify that the described method is Windows-only and suggest Linux-compatible workflows.
  • Add a section comparing Windows and Linux approaches to connecting to HDInsight, ensuring parity in documentation.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-rest-sdk.md ...main/articles/hdinsight/hbase/apache-hbase-rest-sdk.md
High Priority View Details →
Scanned: 2026-01-06 18:15
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively providing installation instructions using the Visual Studio NuGet Package Manager Console (a Windows-centric tool), omitting Linux-specific installation guidance. All code examples are in C#/.NET, which is most commonly used on Windows, and there are no references to Linux development environments, cross-platform .NET usage, or alternative package managers. The documentation does not mention how to use the SDK from Linux, nor does it provide parity for Linux users in terms of setup or tooling.
Recommendations
  • Add instructions for installing the NuGet package using the dotnet CLI (cross-platform) and/or Mono for Linux environments.
  • Explicitly mention that the .NET SDK can be used on Linux and provide setup steps for Linux users, including prerequisites (e.g., .NET Core/SDK installation).
  • Include example commands for Linux shells (bash/zsh) and clarify that the SDK is not limited to Visual Studio or Windows.
  • Reference cross-platform development environments (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
  • Add a note or section on running the sample code on Linux, including any platform-specific considerations.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-etl-at-scale.md ...rticles/hdinsight/hadoop/apache-hadoop-etl-at-scale.md
High Priority View Details →
Scanned: 2026-01-06 18:15
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways. Data ingestion into Azure Storage is described as typically performed via PowerShell, the Azure Storage SDK, or AzCopy, all of which are Windows-centric tools, with no mention of Linux-native alternatives or CLI usage. Windows tools and patterns (PowerShell, AzCopy) are mentioned before any Linux equivalents, and Linux-specific examples or workflows are missing throughout the page. The orchestration and ingestion sections prioritize Windows approaches, and there is little guidance for Linux users on performing equivalent tasks.
Recommendations
  • Include Linux-native CLI examples for data ingestion, such as using Azure CLI, curl, or Python scripts.
  • Mention and provide examples for cross-platform tools (e.g., Azure CLI, REST API) alongside PowerShell and AzCopy.
  • Add explicit Linux and macOS usage instructions or references for all major workflows, especially in sections currently focused on Windows tools.
  • Ensure that examples and tool recommendations are presented in a platform-neutral order, or grouped by OS, rather than Windows-first.
  • Reference documentation pages that specifically address Linux/macOS scenarios where available.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-apps-install-applications.md ...icles/hdinsight/hdinsight-apps-install-applications.md
High Priority View Details →
Scanned: 2025-07-19 13:51
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by primarily referencing the Azure portal (a web GUI often associated with Windows workflows), mentioning Azure PowerShell and Azure Classic CLI as automation tools, and not providing equivalent Linux-native command-line examples (such as Azure CLI on Bash or Linux scripting). The order of mention puts PowerShell before CLI, and there are no explicit Linux shell or scripting examples, despite HDInsight clusters being Linux-based by default.
Recommendations
  • Include Azure CLI (az) command-line examples for installing and managing HDInsight applications, with sample Bash scripts.
  • When mentioning automation, list Azure CLI before or alongside PowerShell, and clarify cross-platform compatibility.
  • Provide explicit Linux/Bash examples for tasks such as deploying Resource Manager templates, not just PowerShell.
  • Reference Linux-native tools and workflows (e.g., SSH, Bash scripting) more prominently, especially since HDInsight clusters are Linux-based.
  • Ensure that all instructions and examples are validated on both Windows and Linux environments, and note any OS-specific differences.
GitHub Create Pull Request
← Previous Page 14 of 35 Next →