Hdinsight

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

Bias Trend Over Time

Pages with Bias Issues

200 issues found
Showing 51-75 of 200 flagged pages
Hdinsight Non-interactive authentication .NET application - Azure HDInsight ...ate-non-interactive-authentication-dotnet-applications.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page focuses exclusively on .NET and C# examples, which are most commonly developed and run on Windows. The NuGet package installation instructions use the 'Install-Package' command, typically run in the Windows PowerShell or Visual Studio Package Manager Console, with no mention of Linux/macOS alternatives. There are no examples or guidance for running the application or installing dependencies on Linux or macOS, nor is there mention of cross-platform development considerations.
Recommendations
  • Add explicit instructions for installing .NET SDK and NuGet packages on Linux and macOS (e.g., using 'dotnet add package').
  • Include notes or examples for running the C# application on Linux/macOS, such as using the 'dotnet run' command.
  • Clarify that .NET Core/.NET 5+ is cross-platform and provide guidance for non-Windows environments.
  • Ensure that prerequisite steps (such as Azure CLI usage) are platform-neutral or include Linux/macOS alternatives.
  • Where PowerShell is referenced, also provide Bash/Azure CLI equivalents.
GitHub Create Pull Request
Hdinsight Azure HDInsight for Visual Studio Code ...s/blob/main/articles/hdinsight/hdinsight-for-vscode.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-style paths (e.g., C:\HD\HDexample) in examples and instructions, and does not provide equivalent Linux/macOS paths or examples. While prerequisites mention Mono for Linux/macOS, all step-by-step instructions and screenshots use Windows conventions, with no Linux/macOS-specific guidance for common tasks like opening folders or saving files. Only one brief note mentions a Linux-specific tool (xclip), but otherwise Linux/macOS users must infer how to adapt Windows-centric instructions.
Recommendations
  • Provide Linux/macOS equivalents for all file path examples (e.g., /home/user/HDexample).
  • Include screenshots or instructions showing Visual Studio Code dialogs on Linux/macOS.
  • Explicitly state how to perform key actions (opening folders, saving files) on Linux/macOS, noting any differences.
  • Add a section or callouts for Linux/macOS users, highlighting platform-specific considerations.
  • Ensure keyboard shortcuts and menu navigation are accurate for Linux/macOS (where they may differ).
GitHub Create Pull Request
Hdinsight Add additional Azure Storage accounts to HDInsight ...ain/articles/hdinsight/hdinsight-hadoop-add-storage.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a detailed PowerShell example for verifying storage accounts, but does not offer equivalent Linux/macOS CLI or shell examples. The verification section is Windows/PowerShell-centric, and PowerShell is mentioned in prerequisites before any Linux alternatives. There is no Linux shell or Azure CLI example for verification, which may hinder Linux/macOS users.
Recommendations
  • Add equivalent verification instructions using Bash and Azure CLI, such as 'az hdinsight' or direct REST API calls via curl.
  • Present Linux/Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Clarify that the Bash script for adding storage accounts is cross-platform and provide explicit instructions for running it on Linux/macOS.
  • Include troubleshooting or verification steps for Linux users, such as using SSH and grep/cat on core-site.xml.
GitHub Create Pull Request
Hdinsight Customize Azure HDInsight cluster configurations using bootstrap ...nsight/hdinsight-hadoop-customize-cluster-bootstrap.md
Medium Priority View Details →
Scanned: 2026-01-12 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 is heavily biased towards Windows, with all code samples and walkthroughs using Azure PowerShell, a Windows-centric tool. There are no Linux/macOS CLI or Bash examples, and the .NET SDK is mentioned only briefly without sample code. The appendix provides a full PowerShell script, but there is no equivalent for Linux users. While ARM templates are platform-neutral, the practical, step-by-step guidance is Windows-first and PowerShell-heavy.
Recommendations
  • Add equivalent Azure CLI (az hdinsight ...) examples for all PowerShell commands.
  • Provide Bash script samples for cluster configuration and verification.
  • Include instructions for installing and using Azure CLI on Linux/macOS.
  • Offer .NET SDK sample code for Linux/macOS environments.
  • Clearly indicate which steps/tools are cross-platform and which are Windows-specific.
  • Reorder sections so platform-neutral approaches (ARM templates, REST API) are presented first.
GitHub Create Pull Request
Hdinsight Create Apache Hadoop clusters using templates - Azure HDInsight ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-create-linux-clusters-arm-templates.md
Medium Priority View Details →
Scanned: 2026-01-12 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 moderate Windows bias. PowerShell is mentioned and linked before Azure CLI, and Visual Studio (a Windows-centric tool) is highlighted as a primary method for template deployment and creation. There are no explicit Linux/macOS-specific examples or instructions, and the .NET client library example links to a Windows-specific page. While Azure CLI is mentioned, it is not given equal prominence or detailed examples compared to PowerShell and Visual Studio.
Recommendations
  • Provide explicit Linux/macOS examples for template deployment, such as using Azure CLI on Linux.
  • Include instructions or screenshots for using cross-platform editors (e.g., VS Code) for template editing and deployment.
  • Balance the order of presentation so that Azure CLI and cross-platform tools are mentioned before or alongside PowerShell and Visual Studio.
  • Replace or supplement Windows/.NET-specific links with cross-platform alternatives where possible.
  • Highlight any differences or considerations for Linux/macOS users in troubleshooting and next steps.
GitHub Create Pull Request
Hdinsight Apache Hadoop & secure transfer storage - Azure HDInsight ...oop-create-linux-clusters-with-secure-transfer-storage.md
Medium Priority View Details →
Scanned: 2026-01-12 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 by providing PowerShell instructions and references before Azure CLI, and by mentioning PowerShell-specific tools and patterns. While Azure CLI (cross-platform) instructions are present, PowerShell is listed first and receives more detailed attention. There are no explicit Linux/macOS shell examples (e.g., Bash), and no mention of platform-specific considerations for Linux users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred for Linux/macOS users.
  • Add Bash shell examples for common tasks, especially for updating storage account settings.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide installation links.
  • Clarify any platform-specific differences or considerations for Linux/macOS users.
  • Avoid using Windows-centric terminology (e.g., 'cmdlet') without alternatives.
GitHub Create Pull Request
Hdinsight Monitor and manage Hadoop with Ambari REST API - Azure HDInsight ...s/hdinsight/hdinsight-hadoop-manage-ambari-rest-api.md
Medium Priority View Details →
Scanned: 2026-01-12 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 tasks, but Windows tools and patterns (PowerShell, Windows Subsystem for Linux, Windows-specific jq path) are mentioned first or exclusively in several places. The prerequisites and introductory sections emphasize Windows environments, and PowerShell is given equal or greater prominence than native Linux shells, despite HDInsight clusters being Linux-based. There are references to Windows-specific installation guides and usage patterns, and some examples assume Windows file paths for jq.
Recommendations
  • Reorder examples to show Bash/Linux commands first, reflecting the Linux-native nature of HDInsight clusters.
  • Clarify that Bash examples work natively on Linux/macOS and do not require Windows Subsystem for Linux.
  • Remove or de-emphasize Windows-specific prerequisites unless strictly necessary.
  • Provide explicit instructions for Linux/macOS users where Windows tools/paths are mentioned (e.g., jq path).
  • Add a note that PowerShell examples are for Windows users, and Bash examples are for Linux/macOS/WSL users.
  • Ensure that any references to Windows tools are balanced with Linux/macOS equivalents.
GitHub Create Pull Request
Hdinsight Run MapReduce jobs on Entra enabled HDInsight cluster using REST API ...-with-entra-authentication/run-map-reduce-rest-jobs.md
Medium Priority View Details →
Scanned: 2026-01-12 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 Windows bias by presenting Windows-specific tools (PowerShell, cmd) and examples first, using Windows command syntax (set, ^ line continuation), and providing detailed PowerShell instructions. Linux/macOS equivalents (bash, export, \\ line continuation) are not shown, and Linux-specific command patterns are missing. The curl examples use Windows cmd syntax, which is not directly usable on Linux/macOS. There is no explicit Linux shell walkthrough or parity for PowerShell steps.
Recommendations
  • Provide Linux/macOS-specific examples for all curl commands, using bash syntax (export, \ line continuation).
  • Include Linux shell variable setting (e.g., export TOKEN=...) and job status checking with jq.
  • Add a section for Linux users, showing how to perform all steps in bash/zsh.
  • Mention cross-platform tools (e.g., Azure CLI, REST API via Python) as alternatives to PowerShell.
  • Ensure all command snippets are clearly marked for their intended OS, or provide side-by-side Windows and Linux/macOS examples.
GitHub Create Pull Request
Hdinsight Set up clusters in HDInsight with Hadoop, Spark, and Kafka ...hdinsight/hdinsight-hadoop-provision-linux-clusters.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation references Azure PowerShell and Windows PowerShell cmdlets as a primary method for cluster customization and setup, and mentions 'Work in Apache Hadoop on HDInsight from a Windows PC' in the related content. While Azure CLI and cURL are also listed, PowerShell is given equal or greater prominence, and script actions are described as being available from the Azure portal, HDInsight Windows PowerShell cmdlets, or the .NET SDK, with no explicit mention of Linux shell equivalents or parity in scripting examples. The related content also highlights Windows tools before Linux alternatives.
Recommendations
  • Explicitly mention and provide examples for Linux shell scripting and Azure CLI wherever PowerShell is referenced.
  • Ensure that Linux/macOS command-line tools are listed before or alongside Windows tools in tables and related content.
  • Add links to Linux/macOS-specific tutorials and tools in the 'Related content' section.
  • Clarify that script actions can be invoked from Azure CLI and provide example commands.
  • Avoid using 'Windows PowerShell' as the default or primary scripting method; present cross-platform options equally.
GitHub Create Pull Request
Hdinsight Understand and resolve WebHCat errors on HDInsight - Azure ...ght/hdinsight-hadoop-templeton-webhcat-debug-errors.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references Azure PowerShell and Data Lake Tools for Visual Studio as primary client-side tools for interacting with WebHCat, both of which are Windows-centric. These tools are mentioned before any Linux or cross-platform alternatives, and there are no examples or guidance for Linux/macOS users or CLI usage outside of Windows tools.
Recommendations
  • Include examples of using WebHCat from Linux/macOS environments, such as using curl or other cross-platform REST clients.
  • Mention Linux-compatible tools (e.g., Azure CLI, Bash scripts) for interacting with WebHCat.
  • Reorder the introduction to present cross-platform options first or alongside Windows tools.
  • Add troubleshooting steps or references relevant to Linux/macOS environments.
GitHub Create Pull Request
Hdinsight Query data from HDFS-compatible Azure storage - Azure HDInsight ...rticles/hdinsight/hdinsight-hadoop-use-blob-storage.md
Medium Priority View Details →
Scanned: 2026-01-12 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-provided tools for accessing Azure Storage, including Azure PowerShell and AzCopy, with Azure PowerShell being Windows-only and AzCopy only supporting Linux and Windows (not macOS). The tools table lists Windows-only options (PowerShell) and presents AzCopy as available for Windows and Linux, but not macOS. The examples for cluster interaction are all based on SSH and bash commands, which are cross-platform, but the external tools section has a Windows bias by including PowerShell and not mentioning Linux/macOS equivalents (e.g., Bash scripting, Python SDK). The order of tools in the table also places Windows-specific tools before Linux alternatives.
Recommendations
  • Add explicit examples for Linux/macOS users where Windows-only tools (like PowerShell) are mentioned.
  • Include alternative cross-platform tools (e.g., Python SDK, REST API, Bash scripting) for storage operations.
  • Clarify AzCopy support for macOS and update documentation if available.
  • Reorder tool lists to present cross-platform tools (Azure CLI, AzCopy) before Windows-only tools.
  • Provide links to Linux/macOS-specific guides for common tasks (upload/download, management).
GitHub Create Pull Request
Hdinsight Manage logs for an HDInsight cluster - Azure HDInsight ...ob/main/articles/hdinsight/hdinsight-log-management.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell and Windows-centric tools (Visual Studio, Power Query for Excel, System Center) are mentioned frequently, often before or instead of Linux alternatives. Several examples and scripting recommendations use PowerShell, with limited or no Linux shell or Bash equivalents provided. Some sections refer to Windows-specific monitoring tools and workflows, while Linux tools (like logrotate) are only briefly mentioned. Although SSH and Ambari (Linux-based) are covered, scripting and automation examples favor Windows/PowerShell, and Linux users may need to infer or adapt solutions.
Recommendations
  • Provide Bash and Linux shell script examples alongside PowerShell for log management and automation tasks.
  • Mention and demonstrate Linux-native tools (e.g., cron, rsync, grep, awk) for log collection, archiving, and analysis.
  • Include Linux equivalents for Windows tools (e.g., alternatives to Visual Studio, Power Query for Excel, System Center).
  • Ensure that Linux-based workflows are described with equal detail and prominence as Windows/PowerShell workflows.
  • Add explicit instructions for using AzCopy, Azure CLI, and other cross-platform tools from Linux/macOS environments.
  • List Linux tools and patterns before or alongside Windows options, not after.
GitHub Create Pull Request
Hdinsight Granular role-based access Azure HDInsight cluster configurations ...insight-migrate-granular-access-cluster-configurations.md
Medium Priority View Details →
Scanned: 2026-01-12 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. It provides migration instructions for several Windows-centric tools (Visual Studio, Azure Data Lake and Stream Analytics Tools for Visual Studio, Az.HDInsight PowerShell) and lists PowerShell cmdlets for role assignment and cluster management. While cross-platform SDKs (Python, Java, Go) and Azure CLI are covered, Windows tools are mentioned first and in greater detail, and there are no explicit Linux/macOS-specific examples or guidance. PowerShell is presented as a primary automation method, with no Bash or shell script equivalents.
Recommendations
  • Add explicit Linux/macOS guidance for cluster configuration and role assignment tasks, such as Bash or shell script equivalents for PowerShell cmdlets.
  • Include migration steps for Linux/macOS users using cross-platform tools (e.g., VS Code on Linux, IntelliJ/Eclipse on macOS).
  • Present Azure CLI examples before or alongside PowerShell examples, emphasizing CLI as the preferred cross-platform solution.
  • Clarify which tools and SDKs are cross-platform and provide parity tables or notes for Linux/macOS users.
  • Add troubleshooting and update instructions for Linux/macOS environments, not just Windows/Visual Studio.
GitHub Create Pull Request
Hdinsight Enable Private Link on an Azure HDInsight cluster ...blob/main/articles/hdinsight/hdinsight-private-link.md
Medium Priority View Details →
Scanned: 2026-01-12 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 areas. The VM deployment example for connectivity testing exclusively uses a Windows 10 image and RDP, with no mention of Linux VM options or SSH port configuration. The PowerShell example for cluster creation is referenced before the Azure CLI example, and there is no explicit Linux shell or macOS terminal guidance. The instructions for testing SSH access are given from a Windows VM using a command prompt, with no mention of Linux/macOS terminal usage. Overall, the documentation assumes a Windows-centric workflow and omits Linux/macOS alternatives in critical steps.
Recommendations
  • Include Linux VM deployment instructions alongside Windows VM, specifying a popular Linux image (e.g., Ubuntu) and SSH port configuration.
  • Provide explicit Linux/macOS terminal examples for SSH connectivity testing, including command-line instructions.
  • Present Azure CLI examples before or alongside PowerShell examples, and clarify CLI usage on Linux/macOS.
  • Mention cross-platform tools and workflows where applicable, avoiding exclusive references to Windows tools (e.g., RDP).
  • Add notes or sections highlighting any OS-specific considerations for DNS configuration, endpoint management, and connectivity testing.
GitHub Create Pull Request
Hdinsight Tutorial: Create an end-to-end ETL pipeline to derive sales insights in Azure HDInsight ...ain/articles/hdinsight/hdinsight-sales-insights-etl.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Bash/Azure CLI and PowerShell options for triggering the Data Factory pipeline, but only PowerShell is shown for command-line automation (no Linux/macOS equivalent using Azure CLI or REST API is given). Power BI Desktop is required for visualization, which is a Windows-only tool. PowerShell is mentioned before the portal method, and no Linux/macOS alternatives for pipeline automation or visualization are discussed.
Recommendations
  • Add Azure CLI or REST API examples for triggering Data Factory pipelines, so Linux/macOS users can automate without PowerShell.
  • Mention and provide instructions for using Power BI service (web-based) or other cross-platform visualization tools as alternatives to Power BI Desktop.
  • When listing options for triggering pipelines, present CLI/REST API methods before or alongside PowerShell, not after.
  • Explicitly state platform requirements for Power BI Desktop and suggest alternatives for non-Windows users.
GitHub Create Pull Request
Hdinsight Azure HDInsight supported node configurations ...es/hdinsight/hdinsight-supported-node-configuration.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page references PowerShell explicitly as a primary scripting tool for deploying HDInsight clusters and provides guidance on VM SKU naming conventions specifically for PowerShell and 'other scripts', without mentioning Linux shell or Bash alternatives. Windows-centric scripting is foregrounded, and no Linux/macOS-specific examples or tools are discussed.
Recommendations
  • Explicitly mention Bash/Azure CLI usage on Linux/macOS alongside PowerShell.
  • Provide example commands for both PowerShell (Windows) and Bash (Linux/macOS) when discussing deployment scripting.
  • Clarify that Azure CLI is cross-platform and show how VM SKU identifiers are used in Bash scripts.
  • Add notes or links for Linux/macOS users on how to perform equivalent tasks.
GitHub Create Pull Request
Hdinsight Use Apache Spark REST API to submit remote jobs to an Entra enabled HDInsight Spark cluster ...-entra-authentication/run-spark-jobs-using-rest-api.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently presents Windows-centric examples, such as using Windows environment variables (set), Windows file paths (C:\Temp\input.txt), and Windows command prompt syntax (cmd). There are no explicit Linux/macOS examples for environment variable setting, file paths, or shell usage, despite the use of cURL (which is cross-platform). This may create friction for Linux/macOS users who must adapt the instructions themselves.
Recommendations
  • Provide parallel Linux/macOS examples for setting environment variables (e.g., export clustername=CLUSTERNAME).
  • Show Linux/macOS file path usage (e.g., /tmp/input.txt) in cURL commands.
  • Clarify that cURL commands work on all platforms and highlight any platform-specific differences.
  • Avoid using Windows-specific syntax (cmd, set) exclusively; use generic shell syntax or provide both.
  • Add a note or section for Linux/macOS users outlining key differences and adaptations.
GitHub Create Pull Request
Hdinsight Tutorial: Use Azure Automation runbooks to create clusters - Azure HDInsight ...ob/main/articles/hdinsight/manage-clusters-runbooks.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses PowerShell for all automation examples, with no mention of Bash, Python, or other cross-platform scripting options. All runbook code samples are PowerShell, and the workflow assumes familiarity with PowerShell and Windows-centric tooling. There are no Linux/macOS-specific instructions or alternative examples, creating friction for users on those platforms.
Recommendations
  • Provide equivalent examples using Python runbooks, which are supported in Azure Automation and are cross-platform.
  • Include Bash or Azure CLI script examples for cluster creation and deletion, highlighting how Linux/macOS users can automate these tasks.
  • Explicitly mention that PowerShell Core is available on Linux/macOS and provide guidance for installing and using it outside Windows.
  • Reorder or parallelize examples so that Linux-friendly options are presented alongside PowerShell, not only after or instead of it.
GitHub Create Pull Request
Hdinsight Azure Toolkit for IntelliJ: Debug Spark apps with SSH - HDInsight ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-intellij-tool-debug-remotely-through-ssh.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page displays a Windows bias in the prerequisites section, where Windows-specific issues (WinUtils.exe) and solutions are described first and in detail. Windows environment variables and tools are mentioned explicitly, while Linux/macOS users are only briefly referenced as not needing these steps. No Linux/macOS troubleshooting or equivalent examples are provided, and Windows download links and instructions appear before any mention of other platforms.
Recommendations
  • Add a dedicated section for Linux/macOS users, clarifying that WinUtils.exe and HADOOP_HOME are not required, and describing any platform-specific setup or troubleshooting steps.
  • Provide Linux/macOS-specific examples or notes for local Spark development, even if only to confirm that no additional configuration is needed.
  • Reorder the prerequisites to present platform-neutral requirements first, then split out platform-specific instructions under clear subheadings (e.g., 'Windows setup', 'Linux/macOS setup').
  • Include links to official documentation for Spark on Linux/macOS for completeness.
GitHub Create Pull Request
Hdinsight What is Apache Spark - Azure HDInsight ...main/articles/hdinsight/spark/apache-spark-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 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 moderate Windows bias. Windows-specific tools (Azure PowerShell, .NET SDK, Power BI, VS Code) are mentioned before or instead of Linux/macOS equivalents. The cluster creation instructions reference Azure PowerShell and the .NET SDK, but do not mention Azure CLI or Bash scripts, which are more common on Linux/macOS. Examples and tutorials focus on Microsoft-centric tools, with little explicit guidance for Linux users. No Linux/macOS-specific instructions or parity notes are provided.
Recommendations
  • Include Azure CLI and Bash script examples for cluster creation and management alongside Azure PowerShell and .NET SDK.
  • Mention cross-platform BI tools (e.g., Tableau, Apache Superset) equally with Power BI.
  • Add explicit notes or sections for Linux/macOS users, clarifying supported tools and workflows.
  • Ensure IDE recommendations include Linux-friendly options (e.g., PyCharm, JupyterLab) and provide setup instructions for those platforms.
  • Order tool and example mentions so that cross-platform or Linux-native options are not always listed after Windows-centric ones.
GitHub Create Pull Request
Hdinsight Azure Toolkit for IntelliJ: Spark app - HDInsight ...s/hdinsight/spark/apache-spark-intellij-tool-plugin.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exhibits Windows bias primarily in the Spark Local Console section, where the use of WINUTILS.EXE is required and referenced as a prerequisite. WINUTILS.EXE is a Windows-only tool, and no Linux/macOS alternatives or instructions are provided. Additionally, environment variables such as HADOOP_HOME are mentioned without platform-specific guidance. The ordering and phrasing in some sections (e.g., 'Ensure you've satisfied the WINUTILS.EXE prerequisite' before running locally) may confuse non-Windows users, and there is a lack of explicit Linux/macOS instructions or troubleshooting steps for local Spark execution.
Recommendations
  • Clearly indicate that WINUTILS.EXE is only required for Windows, and provide alternative instructions or troubleshooting for Linux/macOS users.
  • Add explicit steps for setting up local Spark execution on Linux and macOS, including any required environment variables or dependencies.
  • Where platform-specific requirements exist, use headings or callouts to separate Windows and Linux/macOS instructions.
  • Review all examples and configuration steps to ensure Linux/macOS users are not left out or confused by Windows-centric language.
  • Consider adding a table or section summarizing platform differences for local Spark development.
GitHub Create Pull Request
Hdinsight Use Apache Pig ...ocs/azure-docs/blob/main/articles/hdinsight/use-pig.md
Medium Priority View Details →
Scanned: 2026-01-12 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 referencing SQL Server Integration Services (SSIS) and its Azure Feature Pack as a method for running Pig jobs, which are Windows-centric tools. There are no Linux/macOS equivalents or alternative methods mentioned for running Pig jobs from non-Windows environments. Additionally, the order of presentation puts Windows tooling before any mention of cross-platform or Linux-native approaches, and there are no command-line examples (e.g., Bash, SSH, or Linux tools) for running Pig jobs.
Recommendations
  • Add examples showing how to run Pig jobs using SSH and the Linux command line, which is the default environment for HDInsight clusters.
  • Include instructions for using cross-platform tools such as curl, PuTTY (already referenced), or Azure CLI to submit Pig jobs.
  • Present Windows and Linux/macOS methods side-by-side, or clearly indicate platform applicability for each method.
  • Reference Linux-native scheduling or orchestration tools (e.g., cron, shell scripts) for automating Pig jobs.
GitHub Create Pull Request
Hdinsight Azure HDInsight architecture with Enterprise Security Package ...ght/domain-joined/apache-domain-joined-architecture.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples are provided exclusively in PowerShell, with no Linux shell (bash) or cross-platform CLI alternatives. The instructions reference Windows-centric tools and patterns (Active Directory, PowerShell modules), and do not mention or provide guidance for Linux/macOS users. The focus on Microsoft Entra Domain Services and Windows Server Active Directory further reinforces the Windows-first approach, while omitting any Linux-native identity or authentication integration options.
Recommendations
  • Provide equivalent command-line instructions using Azure CLI or REST API, which are cross-platform.
  • Include notes or sections specifically addressing Linux/macOS users, clarifying how to perform required steps without PowerShell.
  • Mention any limitations or requirements for non-Windows environments explicitly.
  • If possible, offer guidance on integrating with Linux-based identity providers or explain why only Windows-based solutions are supported.
  • Reorder examples or add parity so Linux/macOS instructions are presented alongside or before Windows/PowerShell examples.
GitHub Create Pull Request
Hdinsight LDAP sync in Ranger and Apache Ambari in Azure HDInsight ...lob/main/articles/hdinsight/domain-joined/ldap-sync.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools (e.g., ldp.exe, sAMAccountName, Samba/Winbind, net ads) and providing examples or troubleshooting steps that are either Windows-specific or mention Windows tools before Linux equivalents. There are no explicit Linux/macOS command examples for testing LDAP filters or sync operations, and the documentation assumes familiarity with Windows Active Directory concepts and tools.
Recommendations
  • Include Linux/macOS equivalents for all Windows tools mentioned (e.g., suggest ldapsearch or Apache Directory Studio instead of only ldp.exe).
  • Provide example commands for testing LDAP filters using Linux utilities (e.g., ldapsearch, net ads) alongside Windows examples.
  • Clarify how Samba/Winbind is configured and used on Linux nodes, and provide troubleshooting steps for Linux environments.
  • Ensure that references to attributes like sAMAccountName are contextualized for both Windows AD and possible LDAP implementations on Linux.
  • Present examples and instructions for both platforms in parallel, rather than defaulting to Windows-first.
GitHub Create Pull Request
Hdinsight Using Apache Hive as an ETL Tool - Azure HDInsight ...doop/apache-hadoop-using-apache-hive-as-an-etl-tool.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-centric tools (SQL Server Integration Services, Excel, PowerShell) and patterns (ODBC driver for Excel/C#) before mentioning Linux-friendly alternatives. Linux-native ETL tools and orchestration options are underrepresented, and examples for Linux/macOS users (e.g., Bash, shell scripts, Linux-based data loading tools) are missing. PowerShell is suggested for automation without mentioning Bash or Linux equivalents.
Recommendations
  • Add Linux/macOS-specific examples for automating Hive queries (e.g., Bash scripts, cron jobs).
  • Mention Linux-native ETL tools (e.g., Talend, Pentaho, Airflow) alongside SSIS.
  • Provide examples for connecting to Hive from Linux environments (e.g., using Beeline, JDBC, or Python scripts).
  • List Linux-friendly orchestration options (e.g., Apache Oozie, Airflow) before or alongside Windows tools.
  • Ensure that references to Excel, PowerShell, and SSIS are balanced with alternatives available on Linux/macOS.
GitHub Create Pull Request
← Previous Page 3 of 8 Next →