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 276-300 of 867 flagged pages
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/apache-domain-joined-manage.md ...hdinsight/domain-joined/apache-domain-joined-manage.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 demonstrates a bias toward Windows environments by prioritizing Windows-centric tools (Visual Studio Code, Visual Studio Tools, Power BI, Excel), referencing Active Directory and AAD-DS without mentioning Linux equivalents, and omitting Linux-specific instructions or examples (e.g., no Linux command-line or open-source alternatives for cluster management). There are no explicit Linux or cross-platform examples for connecting, managing, or automating tasks, and the workflow assumes familiarity with Windows-based enterprise tooling.
Recommendations
  • Provide explicit Linux command-line examples for connecting to clusters (e.g., using Beeline, SSH, or curl for REST APIs).
  • Include references to open-source, cross-platform tools (e.g., DBeaver, Apache Zeppelin, Jupyter alternatives) alongside Visual Studio Tools and Power BI.
  • Clarify which steps and tools are cross-platform, and offer parity in instructions for Linux/macOS users (e.g., how to install and use Beeline or Ambari on Linux).
  • Mention how Linux users can interact with Active Directory (e.g., via Kerberos, SSSD, or Samba) and manage authentication.
  • Balance the order of tool mentions (e.g., list cross-platform or Linux-native tools before or alongside Windows tools).
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/domain-joined-authentication-issues.md ...t/domain-joined/domain-joined-authentication-issues.md
High Priority View Details →
Scanned: 2026-01-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 shows evidence of Windows bias in several areas: Windows tools and patterns (such as 'standard Windows AD tools') are mentioned before Linux equivalents, and some troubleshooting steps assume access to a domain-joined Windows machine. Linux alternatives (e.g., using Samba or kinit) are mentioned but often as secondary options, and there are missing Linux-specific examples for some tasks (like browsing AD from Linux).
Recommendations
  • Provide Linux-first examples for directory browsing and account discovery, such as using ldapsearch, samba, or other native Linux tools.
  • Ensure all troubleshooting steps have both Windows and Linux instructions, presented in parallel or with equal prominence.
  • Avoid assuming access to a Windows machine; clarify how tasks can be performed from Linux-only environments.
  • Add explicit Linux command-line examples for tasks like password changes, Kerberos ticket management, and AD attribute lookup.
  • Review the order of instructions to avoid listing Windows solutions first unless there is a technical reason.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/component-version-validation-error-arm-templates.md ...ht/component-version-validation-error-arm-templates.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation mentions PowerShell explicitly and lists it before Azure CLI and other automation tools, suggesting a Windows-first approach. No Linux-specific tools or examples (such as Bash, shell scripts, or Linux command-line usage) are provided. There are no examples using Linux-native automation methods, and the troubleshooting steps and code snippets are platform-neutral but lack Linux parity.
Recommendations
  • Include Linux-specific automation examples, such as Bash scripts or usage with Azure CLI on Linux.
  • Mention Linux command-line tools and workflows alongside PowerShell, ensuring equal prominence.
  • Provide explicit examples for both Windows (PowerShell) and Linux (Bash/Azure CLI) environments.
  • Clarify that ARM templates and Azure CLI are cross-platform, and show usage on both Windows and Linux terminals.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/apache-domain-joined-create-configure-enterprise-security-cluster.md ...in-joined-create-configure-enterprise-security-cluster.md
High Priority View Details →
Scanned: 2026-01-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 strong Windows bias. All examples and instructions for setting up the environment, configuring users/groups, and managing certificates are based on Windows tools and workflows (e.g., Remote Desktop, Server Manager, MMC, PowerShell scripts). There are no Linux equivalents or cross-platform alternatives provided for key steps such as domain controller access, certificate management, or network configuration. PowerShell is used exclusively for scripting, and Windows-centric terminology and UI navigation are prevalent throughout the guide.
Recommendations
  • Provide equivalent instructions for Linux environments, such as using Samba/SSSD for domain joining, OpenLDAP for directory management, and Linux command-line tools for certificate creation and management.
  • Include Bash or Azure CLI examples alongside PowerShell scripts for network and resource configuration.
  • Document how to access and manage Azure VMs and domain controllers from Linux clients (e.g., using SSH instead of RDP).
  • Mention cross-platform tools and approaches where possible, and clarify which steps are Windows-specific.
  • Add notes or sections explaining how Linux administrators can adapt or perform each major step.
  • Ensure parity in screenshots and UI walkthroughs by including Linux desktop or CLI alternatives where relevant.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-ambari-troubleshoot-heartbeat-issues.md .../hadoop/apache-ambari-troubleshoot-heartbeat-issues.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 Tools Windows First
Summary
The documentation provides mostly Linux/Unix-style command-line examples for troubleshooting Ambari heartbeat issues, but when it comes to disabling Azure Monitor logging, it only references the PowerShell cmdlet (Disable-AzHDInsightMonitoring) without mentioning an equivalent Bash/Azure CLI command. This introduces a Windows/PowerShell bias, especially in the context of Azure, where both Windows and Linux users are common. The documentation also references PowerShell before any Linux/CLI alternatives, and does not provide parity for Linux users in this step.
Recommendations
  • Provide Azure CLI or Bash alternatives for the PowerShell cmdlet (Disable-AzHDInsightMonitoring), such as the equivalent az hdinsight monitor disable command.
  • When referencing Azure management tasks, always include both PowerShell and CLI examples, or explicitly state if a feature is only available in one environment.
  • Review the documentation for other places where only Windows/PowerShell tools are mentioned and add Linux/CLI equivalents.
  • Consider reordering examples so that Linux/Bash and Windows/PowerShell are presented together or in a way that does not prioritize one over the other.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/azure-monitor-agent.md ...cs/blob/main/articles/hdinsight/azure-monitor-agent.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. PowerShell is presented as the primary scripting example for enabling Azure Monitor Agent integration, with detailed step-by-step instructions and code snippets. Windows-centric tools and patterns (such as PowerShell cmdlets and references to Windows client device setup) are mentioned before their Linux equivalents. The Azure CLI section, which is more cross-platform, is provided after the PowerShell instructions, and some steps reference tools (like azcopy and jq) without clarifying their installation or usage on Linux. There are no explicit Linux shell (bash) or native Linux tool examples for common administrative tasks, nor are there instructions tailored for Linux users. The documentation also references Windows-specific resources (e.g., 'Set up the Azure Monitor agent on Windows client devices') without providing equivalent Linux guidance.
Recommendations
  • Provide Linux shell (bash) examples alongside or before PowerShell examples for all administrative tasks.
  • Explicitly mention and document installation and usage of cross-platform tools (e.g., azcopy, jq) on Linux systems.
  • Reference and link to Linux-specific documentation for Azure Monitor Agent setup, such as 'Set up the Azure Monitor agent on Linux client devices'.
  • Ensure that CLI instructions are presented as the default or first option, as CLI is cross-platform and more accessible to Linux users.
  • Add troubleshooting and migration guidance specific to Linux environments, including common issues and solutions.
  • Review all screenshots and UI references to ensure they are not Windows-specific and clarify any OS-dependent differences in the portal experience.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-dotnet-csharp-mapreduce-streaming.md ...oop/apache-hadoop-dotnet-csharp-mapreduce-streaming.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 bias toward Windows environments and tooling. Visual Studio is presented as the primary development environment, with no mention of Linux alternatives for building C# applications (such as MonoDevelop or command-line tools). Upload instructions rely on Visual Studio and Azure Data Lake Tools, both Windows-centric. PowerShell is highlighted as a method for running jobs and downloading results, while Linux alternatives (such as Bash scripts or Azure CLI) are not provided. The order of presentation favors Windows tools and workflows, and Linux-native patterns are missing or relegated to secondary status.
Recommendations
  • Add instructions for building C# applications on Linux using MonoDevelop, dotnet CLI, or msbuild.
  • Provide alternative upload methods using Azure CLI, azcopy, or Hadoop fs commands from Linux.
  • Include Bash script examples for running MapReduce jobs and downloading results, alongside PowerShell.
  • Reorder sections so that Linux-native workflows (SSH, Bash, CLI) are presented before or alongside Windows/PowerShell methods.
  • Explicitly mention cross-platform options for each step, ensuring parity for Linux and macOS users.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-hive-java-udf.md ...ticles/hdinsight/hadoop/apache-hadoop-hive-java-udf.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 strong Windows bias: all setup and file manipulation commands use Windows Command Prompt syntax (cmd), Windows file paths, and Windows tools (Notepad, PowerShell). The test environment is explicitly stated as Windows 10, and troubleshooting uses PowerShell scripts. There are no Linux shell (bash) equivalents for local development steps, nor are Linux editors or file path conventions mentioned. Linux users must infer how to adapt the instructions.
Recommendations
  • Provide parallel Linux/macOS examples for all local commands, including directory creation, file editing, and Maven usage (e.g., use mkdir, nano/vim, rm -r).
  • Include Linux file path conventions (e.g., /home/user/HDI) alongside Windows paths.
  • Offer troubleshooting steps using Linux tools (e.g., dos2unix, sed) for line ending issues.
  • Mention cross-platform editors (e.g., VS Code, Sublime Text) and how to configure line endings.
  • Clarify that the instructions apply to both Windows and Linux, and highlight any OS-specific differences.
  • Consider reordering examples so that Linux instructions are presented first or side-by-side with Windows instructions.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-on-premises-migration-best-practices-security-devops.md ...p-on-premises-migration-best-practices-security-devops.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing Microsoft Entra Domain Services (formerly Azure Active Directory Domain Services), Active Directory, and related Windows-centric tools and patterns for cluster security and management. All examples and instructions assume an AD-based environment, with no mention of Linux-native identity providers (such as LDAP, Kerberos, or MIT Kerberos), nor any Linux-specific security tooling or patterns. There are no examples or guidance for non-Windows authentication or cluster management scenarios.
Recommendations
  • Include examples and instructions for integrating HDInsight clusters with Linux-native identity providers (e.g., OpenLDAP, MIT Kerberos) where supported.
  • Provide parity in documentation by listing Linux-based authentication and authorization options alongside Microsoft Entra/AD options.
  • Add sample configurations and migration steps for organizations using Linux-based security infrastructure.
  • Explicitly mention any limitations or requirements regarding non-Windows environments, and offer alternative solutions where possible.
  • Ensure that monitoring, patching, and upgrade instructions are applicable to both Windows and Linux-based clusters, or clarify differences.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/apache-domain-joined-run-hive.md ...insight/domain-joined/apache-domain-joined-run-hive.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 page demonstrates a Windows bias by focusing exclusively on Windows-based tools and workflows, such as Excel and ODBC drivers, for testing Apache Ranger Hive policies. All example steps and screenshots are tailored for Microsoft Excel on Windows, and there is no mention of equivalent Linux tools or workflows (e.g., using Beeline, DBeaver, or other cross-platform SQL clients). The instructions for connecting and testing access are Windows-centric, and Linux users are not provided with alternative methods to validate Ranger policies.
Recommendations
  • Add parallel instructions and examples for Linux users, such as using Beeline or the Hive CLI to test Ranger policies.
  • Include examples of connecting to Hive from cross-platform SQL clients (e.g., DBeaver, SQuirreL SQL) that work on both Windows and Linux.
  • Provide sample commands for connecting to Hive via JDBC or ODBC from Linux, including how to install and configure drivers.
  • Mention and demonstrate how to test policy enforcement using SSH and command-line tools, not just GUI tools like Excel.
  • Ensure that prerequisites and tool recommendations include both Windows and Linux options.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/general-guidelines.md ...articles/hdinsight/domain-joined/general-guidelines.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page for Azure HDInsight Enterprise Security guidelines exhibits a moderate Windows bias. Windows-centric tools and concepts (Active Directory, Microsoft Entra Domain Services, Kerberos/NTLM, Ambari UI, and Windows Server AD) are referenced throughout, often without Linux equivalents or parity. Troubleshooting and configuration steps focus on Windows-based identity and management patterns, and examples for tasks like keytab generation and LDAP sync are given only for Linux but are embedded in a Windows-oriented context. Windows administrative tools are mentioned, and Windows terminology (OU, domain join, etc.) predominates, with little mention of Linux-native identity management or alternative approaches.
Recommendations
  • Provide explicit Linux-based examples for identity management, such as using openldap, sssd, or MIT Kerberos, where possible.
  • Include parity for Linux administrative tools and workflows (e.g., alternatives to Ambari UI, CLI-based management, or open source equivalents).
  • Add troubleshooting steps and configuration guidance for clusters managed primarily from Linux environments.
  • Mention Linux-first patterns and tools (such as SSH, cron, ktutil) earlier or alongside Windows tools to avoid Windows-first impression.
  • Clarify which steps are OS-agnostic and which are specific to Windows, and offer alternatives for Linux-only deployments.
  • Reference open source documentation or community best practices for Linux-based enterprise security in Hadoop/HDInsight clusters.
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-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, requiring a Windows workstation and Microsoft Excel. All instructions and examples use Windows-specific tools (Excel, Power Query add-in) with no mention of Linux-compatible alternatives or cross-platform workflows. The prerequisites and steps assume the user is on Windows, and there are no examples or guidance for Linux users or open-source BI tools.
Recommendations
  • Add instructions or links for accessing HDInsight data from Linux workstations, such as using LibreOffice Calc, Apache Zeppelin, or other open-source BI tools.
  • Include examples for connecting to HDInsight from non-Windows environments, possibly using Python (pandas, pyodbc), R, or command-line tools.
  • Clarify that Power Query and Excel are Windows-specific, and provide parity guidance for Linux users.
  • Mention and document open-source or cross-platform alternatives for data import and analysis.
  • Reorder prerequisites and examples to avoid assuming Windows as the default platform.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/identity-broker.md ...in/articles/hdinsight/domain-joined/identity-broker.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 demonstrates a Windows bias by referencing Windows Server VMs as the default/basis for the ID Broker node, focusing on Microsoft Entra Domain Services (which is tightly integrated with Windows AD), and omitting explicit Linux-based administrative or authentication examples. Tooling and authentication flows are described in a Windows-centric context, and there are no Linux-specific instructions or parity in examples (e.g., no Linux SSH setup, no Linux-native tools mentioned).
Recommendations
  • Add explicit Linux-based examples for cluster administration, authentication, and SSH access (e.g., using Linux SSH clients, kinit, and keytab management on Linux).
  • Mention Linux-compatible tools for development and administration, such as Linux command-line utilities, and clarify that the authentication flows are cross-platform where applicable.
  • Include instructions or notes on how to configure and use the HDInsight ID Broker node if the cluster is running on Linux-based VMs, or clarify if this is not supported.
  • Balance references to Windows Server with equivalent Linux VM options, or state platform requirements clearly.
  • Provide parity in troubleshooting and operational guidance for both Windows and Linux environments.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/cluster-reboot-vm.md ...docs/blob/main/articles/hdinsight/cluster-reboot-vm.md
High Priority View Details →
Scanned: 2026-01-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 Windows bias by providing detailed PowerShell examples for rebooting HDInsight cluster VMs, with no equivalent Linux CLI (e.g., Bash, Azure CLI) examples. The PowerShell method is presented first, and there is no mention of Linux-native tools or commands for managing VM reboots. The REST API section is platform-neutral, but the lack of Linux-specific guidance or parity in examples makes the documentation less accessible to Linux users.
Recommendations
  • Add equivalent examples using Azure CLI (az hdinsight ...) for listing and restarting nodes, which are cross-platform and commonly used on Linux.
  • Include Bash script snippets demonstrating how to interact with the REST API using curl or similar tools.
  • Explicitly mention that PowerShell examples are primarily for Windows users, and provide guidance for Linux users.
  • Reorder sections or provide parallel examples so that Windows and Linux approaches are presented with equal prominence.
  • Reference Linux tools or patterns (e.g., SSH, systemctl, etc.) where relevant for troubleshooting or rebooting nodes.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/connect-on-premises-network.md ...main/articles/hdinsight/connect-on-premises-network.md
High Priority View Details →
Scanned: 2026-01-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 displays a moderate Windows bias. Windows tools (PowerShell, Windows Server DNS) are mentioned before or more prominently than Linux equivalents. PowerShell examples and references appear before Azure CLI and Linux alternatives. The only explicit DNS server configuration example for on-premises is for Bind (Linux), but Windows Server DNS is referenced with a link, not shown inline. Some sections (e.g., discovering cluster node FQDNs) provide PowerShell first, then Azure CLI, but do not show Linux-native commands. There is a lack of parity in step-by-step examples for Linux administrators, especially for on-premises DNS configuration and network management.
Recommendations
  • Provide Linux/Bash-native examples (e.g., using dig, nslookup, or Linux DNS server configuration) alongside or before Windows/PowerShell examples.
  • Include explicit step-by-step instructions for configuring conditional forwarders in common Linux DNS servers (Bind, dnsmasq), not just a sample zone file.
  • When referencing tools, mention Azure CLI and Linux admin tools before or alongside PowerShell and Windows tools.
  • Add more detail for Linux on-premises environments, such as how to discover cluster node FQDNs using Bash/SSH, and how to manage network security with iptables or firewalld.
  • Ensure that all critical configuration steps have both Windows and Linux examples, not just links for one platform.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-connect-excel-hive-odbc-driver.md ...hadoop/apache-hadoop-connect-excel-hive-odbc-driver.md
High Priority View Details →
Scanned: 2026-01-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 Windows-centric, providing only instructions and screenshots for Windows tools such as ODBC Data Source Administrator and Excel. There are no examples or guidance for Linux or cross-platform alternatives, and all steps assume a Windows environment. The use of Microsoft Hive ODBC driver and references to Windows-specific UI elements further reinforce the bias.
Recommendations
  • Include instructions for connecting to HDInsight Hive from Excel on macOS and Linux, if supported.
  • Provide examples using open-source ODBC drivers (e.g., unixODBC, Simba ODBC) and show how to configure them on Linux.
  • Add command-line examples for ODBC configuration on Linux (e.g., editing odbc.ini, using isql for testing).
  • Mention and link to cross-platform tools for querying Hive (e.g., DBeaver, Tableau, or command-line clients).
  • Clarify platform limitations and provide parity guidance for non-Windows users.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-hive-pig-udf-dotnet-csharp.md ...ght/hadoop/apache-hadoop-hive-pig-udf-dotnet-csharp.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 demonstrates a Windows bias by exclusively using Visual Studio (a Windows-centric IDE) for all development steps, recommending Windows tools like Data Lake Tools for Visual Studio and Azure PowerShell, and providing step-by-step instructions for building, uploading, and running jobs via Visual Studio. Linux alternatives for development, file upload, and job submission are not described, even though the cluster itself is Linux-based. Only the Pig job section briefly mentions SSH, but no Linux-native development or upload workflow is covered.
Recommendations
  • Add instructions for building C# projects using cross-platform tools such as 'dotnet build' or MonoDevelop on Linux/macOS.
  • Provide examples for uploading .exe files using Azure CLI, azcopy, or SCP from Linux/macOS terminals.
  • Include steps for submitting Hive queries via SSH and command-line tools (e.g., Beeline, Hive CLI) on Linux, rather than only through Visual Studio.
  • Mention and demonstrate using VS Code or other cross-platform editors for development.
  • Reorder recommendations so that cross-platform and Linux-native tools are presented before or alongside Windows tools.
  • Clarify that Visual Studio is optional and highlight equivalent Linux workflows for all major steps.
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-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 page exhibits a moderate Windows bias. In the 'Ingest file storage and result storage' section, Windows-centric tools (PowerShell, AzCopy) are mentioned first and exclusively for Azure Blob Storage ingestion, with no Linux CLI or cross-platform alternatives provided. PowerShell is referenced as a primary method for data ingestion, and Linux equivalents (such as Azure CLI, Bash scripts, or Linux-native tools) are missing. The ordering and tool selection imply a Windows-first approach, and the lack of Linux-specific examples or parity in ingestion tooling further reinforces this bias.
Recommendations
  • Include Linux-specific examples for data ingestion, such as using Azure CLI, Bash scripts, or third-party Linux tools.
  • Mention cross-platform tools (e.g., AzCopy is available for Linux, so clarify its usage on both platforms).
  • Provide example commands for both Windows (PowerShell) and Linux (Bash/Azure CLI) when discussing ingestion workflows.
  • Reorder tool mentions to avoid Windows-first bias; present Windows and Linux options together or alternate their order.
  • Explicitly state platform compatibility for each tool, and link to installation guides for both Windows and Linux.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/hdinsight-use-sqoop.md .../main/articles/hdinsight/hadoop/hdinsight-use-sqoop.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 page demonstrates a Windows bias by emphasizing Azure PowerShell as the primary method for running Sqoop jobs, referencing Windows-specific tools (PowerShell, .NET SDK), and providing detailed instructions for Windows environments. Linux and macOS options are mentioned but not elaborated upon, and example walkthroughs or commands for Linux (SSH, Bash) are missing or deferred to other pages. Windows tools and patterns are presented before Linux equivalents, and the overall workflow assumes a Windows workstation.
Recommendations
  • Provide direct Linux and macOS command-line examples (e.g., SSH/Bash) alongside PowerShell examples within this page.
  • Ensure that walkthroughs for Linux and macOS are equally detailed and accessible, not just linked externally.
  • Present cross-platform options in a neutral order, or lead with platform-agnostic methods (e.g., SSH) before Windows-specific tools.
  • Clarify any limitations or differences for Linux users up front, and offer alternatives or workarounds where possible.
  • Add explicit instructions for setting up and running Sqoop jobs from Linux/macOS clients, including sample commands and expected outputs.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-using-apache-hive-as-an-etl-tool.md ...doop/apache-hadoop-using-apache-hive-as-an-etl-tool.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias by prioritizing Windows-centric tools and workflows. Examples and recommendations favor SQL Server Integration Services (SSIS), Excel, PowerShell, and C# (with Hive ODBC), all of which are primarily Windows-based. Linux alternatives, such as Sqoop and Oozie, are mentioned but not highlighted or exemplified. There are no Linux shell or CLI examples, and orchestration via PowerShell is suggested before mentioning Hadoop-native solutions like Oozie.
Recommendations
  • Provide Linux shell (bash) examples for Hive queries and ETL orchestration.
  • Highlight Hadoop-native tools (e.g., Oozie, Sqoop CLI) with usage examples, not just links.
  • Include Linux-friendly data loading and transformation workflows, such as using Python scripts or shell pipelines.
  • Balance recommendations for orchestration by giving equal prominence to Linux-native solutions (Oozie, cron, Airflow) alongside PowerShell and Logic Apps.
  • Mention cross-platform alternatives to Excel and SSIS, such as LibreOffice Calc, pandas (Python), or Apache NiFi.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-use-hive-curl.md ...ticles/hdinsight/hadoop/apache-hadoop-use-hive-curl.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 provides both Bash/cURL and PowerShell/Invoke-WebRequest examples for interacting with HDInsight's REST API, but consistently lists PowerShell (Windows) examples before Bash (Linux) ones, and gives more detailed explanations for Windows credential handling. The use of Windows-specific tools (Invoke-WebRequest, Get-Credential) is prominent, and some steps (like credential preservation) are more user-friendly for Windows users. There is a minor bias toward Windows in ordering and tool selection, though Linux examples are present.
Recommendations
  • Alternate the order of Bash and PowerShell examples, or present Bash examples first to balance visibility.
  • Provide equally detailed explanations for Bash/Linux credential handling and environment setup.
  • Include notes on using cURL and jq on native Linux systems, not just WSL.
  • Where possible, use cross-platform tools (e.g., cURL, Azure CLI) as primary examples, relegating platform-specific tools to secondary notes.
  • Clarify that all examples work on both Linux and Windows (with WSL), and provide troubleshooting tips for common Linux issues.
  • Ensure parity in the depth of explanation and user experience for both platforms, especially for authentication and environment setup.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-on-premises-migration-best-practices-storage.md ...he-hadoop-on-premises-migration-best-practices-storage.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 exhibits subtle Windows bias. Windows-style environment variables (e.g., %HADOOP_HOME%) are referenced before Linux equivalents, and Windows-centric tools like Azure PowerShell are mentioned for data copy operations, while Linux-native alternatives are not equally highlighted. There are no explicit Linux shell or configuration examples for common tasks such as editing Hadoop configuration files or using Linux command-line tools for storage management. The page lacks parity in showing Linux-specific workflows or tools, and Windows patterns are presented as defaults.
Recommendations
  • Include Linux-style environment variable references (e.g., $HADOOP_HOME) alongside Windows ones.
  • Provide Linux shell command examples for editing configuration files, managing credentials, and interacting with storage.
  • Highlight Linux-native tools (such as az CLI, hdfs dfs, or shell scripting) for data migration and management, not just Azure PowerShell.
  • Ensure examples and instructions are presented for both Windows and Linux platforms, or clarify platform-specific differences.
  • Add explicit notes or sections for Linux users, especially for common administrative tasks and troubleshooting.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/troubleshoot-invalidnetworkconfigurationerrorcode-cluster-creation-fails.md ...idnetworkconfigurationerrorcode-cluster-creation-fails.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 page exhibits mild Windows bias. While most troubleshooting steps use Linux/SSH commands (hostname, nslookup, dig), there are several references to Windows-specific tools and patterns: PowerShell cmdlets (Get-AzVirtualNetwork), mention of Azure Runbooks (typically Windows-centric), and instructions that mention deploying either Linux or Windows DNS VMs but provide more detail for Linux. The PowerShell example is given without a corresponding Azure CLI or Linux-native alternative. Windows tools and terminology (PowerShell, Runbook) are mentioned before or instead of Linux equivalents.
Recommendations
  • Provide Azure CLI or Bash alternatives for PowerShell commands (e.g., show az network vnet commands alongside Get-AzVirtualNetwork).
  • When referencing DNS server deployment, give equal detail for both Linux and Windows options, including example configuration steps for each.
  • Avoid mentioning Windows tools (PowerShell, Runbook) exclusively; always pair with Linux-native or cross-platform alternatives.
  • Where troubleshooting steps involve command-line tools, ensure both Windows (e.g., PowerShell, CMD) and Linux (e.g., Bash) examples are present.
  • Explicitly state that both Linux and Windows VMs are supported for DNS forwarding, and provide configuration examples for both.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-use-sqoop-curl.md ...icles/hdinsight/hadoop/apache-hadoop-use-sqoop-curl.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 page demonstrates a clear Windows bias by providing only Windows command prompt examples (using 'set' for environment variables and Windows-style variable expansion), referencing Windows-specific paths for jq, and not including equivalent Linux/bash examples. The instructions and examples are tailored to Windows users, with Linux users only briefly mentioned as needing to 'revise as needed for your environment.' There is no explicit guidance or code samples for Linux/bash users, nor are Linux tools or patterns discussed.
Recommendations
  • Provide parallel Linux/bash examples for all commands, using 'export' for environment variables and '$VARIABLE' for expansion.
  • Show how to install and use jq on Linux, referencing typical Linux paths (e.g., '/usr/bin/jq').
  • Add explicit notes or sections for Linux users, including troubleshooting tips and environment setup.
  • Avoid language such as 'this example is based on a Windows environment' without immediately providing the Linux equivalent.
  • Ensure that tool recommendations (e.g., SQL clients) include popular Linux options, such as Azure Data Studio or sqlcmd.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/hdinsight-use-hive.md ...b/main/articles/hdinsight/hadoop/hdinsight-use-hive.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific tools (Visual Studio, PowerShell, SSIS) are mentioned explicitly and sometimes before their Linux equivalents. Windows PowerShell is listed as a method for running Hive queries, but there is no equivalent Linux shell example. The use of Visual Studio and SSIS for Hive jobs is highlighted, while Linux-native alternatives (such as command-line scripting or cron scheduling) are not discussed. However, many tools and examples are cross-platform, and Linux is referenced in several places.
Recommendations
  • Add explicit Linux shell (bash) examples for running Hive queries, similar to the PowerShell example.
  • Mention Linux-native scheduling options (e.g., cron, systemd timers) alongside SSIS and Data Factory.
  • Ensure that cross-platform tools (e.g., Beeline, REST API) are presented before or alongside Windows-specific tools.
  • Provide parity in examples and instructions for both Windows and Linux environments, especially for common tasks.
  • Highlight open-source and platform-neutral tools (e.g., Apache Oozie, Beeline) more prominently.
GitHub Create Pull Request
← Previous Page 12 of 35 Next →