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 201-225 of 867 flagged pages
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/apache-domain-joined-configure-using-azure-adds.md ...ned/apache-domain-joined-configure-using-azure-adds.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several areas. The only explicit code example for certificate creation uses PowerShell, with no Linux or cross-platform alternative. Network validation and troubleshooting steps recommend joining a Windows VM to the domain and using Windows-specific tools like ldp.exe, with no mention of Linux equivalents (e.g., OpenLDAP tools, Linux domain join). The documentation consistently presents Windows-based procedures and tools first or exclusively, and omits Linux-focused instructions for key steps such as certificate generation, domain joining, and LDAP testing.
Recommendations
  • Provide Linux-based examples for certificate creation (e.g., using openssl) alongside PowerShell.
  • Include instructions for joining a Linux VM to the domain and validating connectivity, not just Windows.
  • Suggest Linux tools for LDAP testing (e.g., ldapsearch, ldapwhoami) as alternatives to ldp.exe.
  • Ensure troubleshooting steps include both Windows and Linux approaches, especially for network and domain validation.
  • Where possible, use cross-platform commands (e.g., nslookup, ping) and clarify any OS-specific differences.
  • Add parity in screenshots or walkthroughs for Linux environments where relevant.
GitHub Create Pull Request
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-09 00:34
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 emphasizing Windows-centric tools (Visual Studio Code, Visual Studio Tools, Power BI, Excel), referencing PowerShell as an example external tool, and omitting explicit Linux command-line or open-source alternatives in examples. There are no Linux-specific instructions or screenshots, and Windows tools are mentioned before or instead of cross-platform or Linux-native options.
Recommendations
  • Include Linux-specific instructions and examples, such as using the Linux terminal, SSH, and open-source editors (e.g., VS Code on Linux, or command-line tools like Beeline and Livy from Bash).
  • When listing tools (e.g., Visual Studio Tools, Power BI, Excel), also mention cross-platform or Linux alternatives (e.g., DBeaver, Apache Zeppelin, Tableau for Linux, or generic ODBC/JDBC clients).
  • Provide explicit Linux command-line examples for connecting to clusters, running jobs, and managing users, alongside or before Windows/PowerShell examples.
  • Clarify which tools and steps are cross-platform, and provide parity in screenshots and instructions for both Windows and Linux environments.
  • Avoid referencing Windows tools (e.g., PowerShell, Visual Studio Tools) as the only or primary method for external access; always provide a Linux equivalent.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides troubleshooting steps for Apache Ambari heartbeat issues in Azure HDInsight. While most operational examples use Linux commands (ps, top, service), the only explicit scripting/tooling example for disabling Azure Monitor logging is given as a PowerShell cmdlet (Disable-AzHDInsightMonitoring), with no Bash/CLI/Linux-native equivalent. This prioritizes Windows tooling and assumes user familiarity with PowerShell, which may not be the case for Linux-focused users. There is also no mention of how to perform the same action using Azure CLI or REST API, which are cross-platform.
Recommendations
  • Provide equivalent Azure CLI and/or Bash examples for disabling Azure Monitor logging, such as using 'az hdinsight monitor disable' or REST API calls.
  • Mention both PowerShell and CLI options side by side, or default to CLI first for cross-platform parity.
  • Clarify that the PowerShell cmdlet is one option and link to documentation for other platforms.
  • Audit other troubleshooting steps to ensure all administrative actions can be performed from Linux environments, not just Windows/PowerShell.
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-09 00:34
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 (Excel, ODBC, Microsoft 365/Office), and by providing step-by-step instructions only for connecting to Hive from Excel on Windows. There are no examples or instructions for Linux or cross-platform alternatives, such as using Linux-based ODBC clients, command-line tools, or open-source spreadsheet applications. The documentation also references Windows-specific UI elements and authentication dialogs, and does not mention or prioritize Linux workflows.
Recommendations
  • Include parallel instructions for connecting to Hive from Linux environments, such as using isql or other ODBC clients available on Linux.
  • Provide examples for querying Hive using command-line tools (e.g., Beeline, Hive CLI) on Linux, especially for testing Ranger policies.
  • Mention and demonstrate open-source or cross-platform spreadsheet alternatives (e.g., LibreOffice Calc) and how to connect them to Hive via ODBC or JDBC.
  • Balance the order of presentation so that Linux and Windows workflows are given equal prominence, or clearly indicate that the instructions are Windows-specific and link to Linux alternatives.
  • Add a section on using JDBC (which is cross-platform) with sample commands and connection strings for both Windows and Linux.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. It references Windows-centric tools and patterns (e.g., Active Directory, Kerberos, Ambari UI, Microsoft Entra Domain Services) and administrative concepts that are primarily relevant to Windows environments. Windows terminology and tools are mentioned first or exclusively (e.g., domain join, OU, SAMAccountName, NTLM/Kerberos authentication, AD Connect, and references to Windows Server Active Directory). There is a lack of Linux-specific examples or alternative approaches, and the troubleshooting and configuration steps assume familiarity with Windows/AD paradigms. While some Linux commands (e.g., ktutil, ssh, crontab) are mentioned, they are presented in the context of integrating with Windows-based identity infrastructure.
Recommendations
  • Provide equivalent Linux-focused examples for identity management, authentication, and cluster administration, such as using OpenLDAP, MIT Kerberos, or SSSD.
  • Include guidance for environments that use Linux-native identity providers or federated authentication systems not based on Active Directory.
  • Clarify which steps are OS-agnostic and which are specific to Windows/AD, and offer alternatives for Linux-centric deployments.
  • Add troubleshooting and configuration instructions for Linux tools and patterns (e.g., systemd, Linux file permissions, Linux-based certificate management).
  • Explicitly state any platform dependencies and suggest cross-platform best practices where possible.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a Windows bias by referencing Windows Server VMs as the platform for the ID Broker node, mentioning domain-joining to Microsoft Entra Domain Services (which is typically associated with Windows environments), and omitting explicit Linux setup or management instructions. All authentication infrastructure and troubleshooting guidance assume a Windows-centric Active Directory and VM environment, with no mention of Linux equivalents or alternative patterns for non-Windows clusters. There are no Linux-specific examples or references to Linux-native tools for cluster administration, authentication, or troubleshooting.
Recommendations
  • Provide explicit instructions and examples for Linux-based clusters, including how to set up and manage the ID Broker node on Linux VMs if supported.
  • Mention Linux-native authentication patterns (e.g., integration with MIT Kerberos, sssd, or other Linux domain join mechanisms) alongside or before Windows/Active Directory approaches.
  • Include Linux command-line examples for cluster administration, authentication (such as kinit, ssh, and keytab usage), and troubleshooting.
  • Clarify whether the ID Broker node must be Windows-based, or if Linux is supported, and provide parity in documentation for both platforms.
  • Reference Linux tools (such as OpenSSH, curl, or native Hadoop CLI tools) equally with Windows tools, and avoid assuming a Windows-only environment.
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-09 00:34
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 a Windows bias by prioritizing Windows-centric tools and workflows such as Visual Studio and PowerShell. Examples and instructions for uploading files and building applications are provided exclusively for Visual Studio, with no mention of Linux alternatives (e.g., MonoDevelop, dotnet CLI, or command-line builds). The PowerShell example is given as the only scripted automation method, with no Bash or Linux shell script equivalent. The use of Windows file paths and .exe binaries further reinforces the Windows-first approach, and Linux-native development patterns are absent.
Recommendations
  • Add instructions for building C# MapReduce applications using cross-platform tools such as dotnet CLI or MonoDevelop, including Linux-specific build commands.
  • Provide examples for uploading files to HDInsight storage using Azure CLI or Hadoop FS commands from Linux/macOS terminals.
  • Include a Bash or shell script example for running MapReduce jobs and downloading results, paralleling the PowerShell example.
  • Clarify that .exe files produced by Mono/.NET can be built and run on Linux, and provide guidance for Linux users.
  • Reorder sections or add notes to ensure Linux workflows are presented alongside or before Windows-specific instructions.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively using Visual Studio (a Windows-centric IDE) for all development steps, recommending Data Lake Tools for Visual Studio and Azure PowerShell for file upload and job submission, and providing step-by-step instructions only for these Windows tools. Linux alternatives (such as using Mono directly, building with `msbuild`, or uploading files via SCP/SFTP) are not mentioned, and the only Linux-specific step is the SSH connection for running Pig jobs. There are no examples of building or deploying from Linux environments, nor are cross-platform CLI workflows described.
Recommendations
  • Add instructions for building C# projects using cross-platform tools such as `dotnet` CLI or `msbuild` on Linux/macOS.
  • Provide examples for uploading files to HDInsight storage using Linux-native tools (e.g., `azcopy`, `az storage blob upload`, `scp`, or `sftp`).
  • Include steps for running Hive queries using Azure CLI or REST API, rather than only through Visual Studio.
  • Mention and demonstrate the use of cross-platform editors (e.g., Visual Studio Code) and workflows.
  • Clarify which steps are Windows-specific and provide Linux/macOS equivalents where possible.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-on-premises-migration-best-practices-data-migration.md ...op-on-premises-migration-best-practices-data-migration.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 listing Windows-centric tools (Azure Storage Explorer, AzCopy, Azure PowerShell) before cross-platform or Linux-native alternatives, and by not providing Linux-specific or command-line examples for data transfer. The only command-line example given is for Hadoop DistCp, which is platform-agnostic, but there are no Linux CLI equivalents for Azure-specific tools. Additionally, the documentation references Azure PowerShell without mentioning Bash or Linux shell alternatives, and does not provide parity in example commands for Linux users.
Recommendations
  • Include Linux-specific examples for data transfer, such as using Azure CLI from Bash, or mounting Azure Blob Storage via blobfuse.
  • List cross-platform tools (e.g., Azure CLI, AzCopy) before Windows-only tools like Azure PowerShell and Storage Explorer.
  • Provide example commands for both Windows (PowerShell) and Linux (Bash) environments when discussing Azure tools.
  • Mention and link to Linux-native utilities and patterns for data migration, such as rsync, curl, or blobfuse, where appropriate.
  • Clarify which tools are cross-platform and which are Windows-only, to help users choose the best option for their environment.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows environments, requiring a Windows workstation and Microsoft Excel for Power Query integration. All instructions and prerequisites assume Windows OS and Microsoft Office, with no mention of Linux or cross-platform alternatives for connecting to HDInsight from non-Windows systems. The tools and workflows described (Excel, Power Query) are Windows-centric, and there are no examples or guidance for Linux users.
Recommendations
  • Provide equivalent instructions for Linux users, such as using LibreOffice Calc or other open-source spreadsheet tools, if possible.
  • Include examples of connecting to HDInsight from Linux using alternative BI tools (e.g., Apache Zeppelin, Jupyter Notebooks, or Python libraries like pandas).
  • Clearly state platform limitations and suggest cross-platform or web-based alternatives where available.
  • Add a section comparing Windows and Linux approaches for accessing HDInsight data, highlighting any differences and available tooling.
  • Reference documentation for Linux-compatible BI workflows, such as connecting to HDInsight via ODBC/JDBC from Linux.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several areas. Data ingestion into Azure Storage is described primarily via PowerShell, AzCopy, and the Azure Storage SDK, with no mention of Linux-native tools or CLI usage. Windows-centric tools and patterns (PowerShell, .NET SDK) are mentioned before or instead of Linux equivalents. There are no explicit Linux or bash examples for common tasks like uploading data, and the documentation does not provide parity in guidance for Linux users. The focus on PowerShell and Windows tools may make it harder for Linux users to follow or replicate the steps.
Recommendations
  • Include Linux/bash examples for data ingestion, such as using Azure CLI (az storage), curl, or Python SDK.
  • Mention Linux-native tools (e.g., hdfs dfs, distcp, rsync) for file operations alongside Windows tools.
  • Provide explicit instructions for both Windows and Linux environments, especially for common tasks like uploading data.
  • List cross-platform tools first, or present Windows and Linux options side-by-side.
  • Clarify when a tool or SDK is cross-platform, and provide links to Linux installation and usage guides.
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-09 00:34
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: the test environment is explicitly Windows 10, all setup and file manipulation commands use Windows Command Prompt syntax (cmd), Windows-specific tools like Notepad are referenced, and troubleshooting uses PowerShell scripts. There are no Linux shell equivalents or examples for common tasks such as directory creation, file editing, or line ending conversion. Linux users are only briefly mentioned and told to 'modify accordingly,' without concrete guidance.
Recommendations
  • Provide parallel Linux shell (bash) commands for all setup steps (e.g., mkdir, cd, rm -rf).
  • Suggest Linux-friendly editors (e.g., nano, vim) alongside Notepad.
  • Include Linux methods for fixing line endings (e.g., dos2unix, sed) in the troubleshooting section.
  • Clarify any OS-specific differences in Maven usage, file paths, and SSH/SCP commands.
  • Consider presenting Linux examples first or side-by-side with Windows examples to reflect HDInsight's Linux-based clusters.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-on-premises-migration-best-practices-architecture.md ...doop-on-premises-migration-best-practices-architecture.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates Windows bias by listing Azure PowerShell as a primary command-line tool for cluster creation, mentioning Azure SQL Database (a Microsoft/Windows-centric technology) exclusively for metadata stores, and generally listing Windows-oriented tools (PowerShell, .NET SDK) before Linux-native equivalents (Azure CLI, cURL, Python/Java SDKs). There is no explicit mention of Linux-specific tools or examples, and the documentation does not provide parity in Linux command-line usage or alternative open-source database options for metadata stores.
Recommendations
  • Provide Linux-specific command-line examples using Azure CLI and cURL, and ensure these are listed before or alongside PowerShell examples.
  • Include instructions or references for managing HDInsight clusters from Linux environments, such as using Bash scripts or Linux shell utilities.
  • Mention open-source alternatives for metadata stores (e.g., PostgreSQL) if supported, or clarify Azure SQL Database requirements for non-Windows users.
  • Ensure SDKs and tools are presented in a platform-neutral order, or explicitly note cross-platform compatibility.
  • Add a section or examples for cluster management and monitoring using Linux-native tools (e.g., SSH, Linux monitoring utilities) where applicable.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-use-mapreduce-curl.md ...s/hdinsight/hadoop/apache-hadoop-use-mapreduce-curl.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows environments. Examples for setting environment variables and using curl are given in Windows CMD syntax, with explicit references to Windows paths and tools (e.g., jq-win64.exe). PowerShell is presented as a primary method, while Linux shell equivalents (bash, sh) are not covered. There are no Linux-specific examples for variable setting, command chaining, or jq usage, and Windows tools and patterns are mentioned exclusively or before their Linux counterparts.
Recommendations
  • Add Linux/bash examples for setting environment variables (e.g., export CLUSTERNAME=...) and command chaining.
  • Include Linux-compatible jq usage (e.g., jq .id) and avoid hardcoded Windows paths.
  • Present Linux shell examples before or alongside Windows/PowerShell examples to ensure parity.
  • Clarify tool availability and usage for both platforms, such as curl and jq installation instructions for Linux.
  • Avoid language that assumes a Windows environment by default; use cross-platform phrasing (e.g., 'In your shell environment...').
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-09 00:34
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 Windows bias by primarily referencing Windows-centric tools and workflows. Examples include recommending SQL Server Integration Services (SSIS), Excel, and PowerShell for automation, with no equivalent Linux alternatives or examples provided. Windows tools are mentioned first and more frequently, while Linux-native ETL tools and orchestration methods (other than a brief mention of Oozie) are omitted or relegated to secondary status.
Recommendations
  • Provide Linux-based ETL tool examples, such as using Apache NiFi, Airflow, or shell scripting for orchestration.
  • Include Linux command-line examples for Hive queries and automation, such as using Bash scripts or cron jobs.
  • Mention and demonstrate Linux-compatible data loading tools (e.g., csvkit, sqoop CLI usage on Linux, or Python scripts).
  • Balance references to Excel and SSIS with Linux-friendly alternatives like LibreOffice Calc, pandas, or direct database imports.
  • Show how to automate Hive queries using Linux scheduling tools (cron, systemd timers) instead of or alongside PowerShell.
  • Ensure that workflow orchestration examples include both Oozie and Linux-native options, not just external Windows scripts.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/python-udf-hdinsight.md ...main/articles/hdinsight/hadoop/python-udf-hdinsight.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides both shell (Linux/Unix) and PowerShell (Windows) examples for uploading files and running jobs on HDInsight. However, PowerShell examples are more detailed, cover more scenarios (including error handling and job output retrieval), and are presented in full script form. There are multiple references to Windows-specific issues (e.g., CRLF line endings) and solutions using PowerShell. In troubleshooting, only PowerShell solutions are given for line ending problems, with no mention of Linux tools (e.g., dos2unix). The PowerShell workflow is described as the main remote submission method, and some limitations (e.g., inability to use C Python remotely) are only discussed in the PowerShell context. Windows tools and patterns (PowerShell, Azure modules) are mentioned before or more prominently than Linux equivalents.
Recommendations
  • Provide equivalent Bash scripts for all PowerShell examples, including job submission, error retrieval, and file upload, using Azure CLI or REST API.
  • Include troubleshooting steps for CRLF issues using Linux tools (e.g., dos2unix, sed) alongside PowerShell solutions.
  • Clarify that both Linux and Windows environments are supported, and ensure that instructions for Linux users are as detailed and complete as those for Windows/PowerShell users.
  • Mention Azure CLI as a cross-platform alternative to PowerShell for remote job submission and management.
  • Where limitations exist (e.g., remote submission with C Python), explain if/how Linux users can work around them or provide parity.
  • Balance the order of presentation so that Linux/Bash workflows are not secondary to Windows/PowerShell workflows.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-on-premises-migration-best-practices-infrastructure.md ...op-on-premises-migration-best-practices-infrastructure.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page displays Windows bias primarily in the 'Customize HDInsight configs using Bootstrap' section, where only a PowerShell example using the AZ module is provided for cluster configuration, with no equivalent Linux CLI or Bash example. The PowerShell approach is presented first and exclusively, which may disadvantage Linux users or those working in non-Windows environments. Elsewhere, the documentation references SSH and Bash scripts for script actions, but the main configuration example is Windows-centric.
Recommendations
  • Provide equivalent examples using Azure CLI (az hdinsight ...) and Bash for cluster configuration, especially in the 'Customize HDInsight configs using Bootstrap' section.
  • Ensure that Linux-native tools and workflows (e.g., Bash scripts, Azure CLI) are presented alongside or before Windows/PowerShell examples.
  • Add explicit instructions or links for Linux users to perform the same tasks without requiring PowerShell.
  • Review other sections for subtle Windows-first language or tool references and ensure Linux parity in all examples and recommendations.
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-09 00:34
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 primarily through the use of Windows-style environment variables (e.g., %HADOOP_HOME%), references to Windows-centric configuration paths, and the absence of explicit Linux examples or Linux-specific instructions. Windows tools and patterns (such as referencing Azure PowerShell for data copy) are mentioned, while Linux equivalents (such as Bash scripts or Linux command-line tools) are either omitted or not given equal prominence. The documentation does not provide parity in examples or instructions for Linux users, despite Hadoop's strong presence in Linux environments.
Recommendations
  • Include Linux-specific examples for configuration paths (e.g., $HADOOP_HOME instead of %HADOOP_HOME%).
  • Provide explicit instructions and examples for both Windows and Linux environments when referencing file paths, environment variables, or command-line operations.
  • Mention and demonstrate Linux-native tools (such as azcopy, Bash scripts, or Linux CLI) alongside Windows tools like Azure PowerShell.
  • Ensure that any references to configuration files, directory structures, or scripts are shown in both Windows and Linux formats.
  • Add a section or callouts for common Linux migration patterns and troubleshooting steps.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias towards Windows environments. All command-line examples use Windows batch syntax (set VAR=), Windows environment variables (%VAR%), and reference Windows-specific paths (C:\HDI\jq-win64.exe). There are no Linux or macOS shell examples (e.g., export VAR=, $VAR, ./jq), nor instructions for running the commands on non-Windows platforms. The prerequisites and instructions assume Windows tools and patterns, and Linux equivalents are not provided.
Recommendations
  • Provide parallel examples for Linux/macOS shells, using export VAR=, $VAR, and typical jq invocation (e.g., jq .status.state).
  • Explicitly mention how to adapt command syntax for Linux/macOS users, including variable setting and referencing.
  • Reference Linux-compatible jq installation and usage (e.g., apt-get install jq, ./jq).
  • Where Windows paths are used (e.g., C:\HDI\jq-win64.exe), provide Linux/macOS alternatives (e.g., /usr/bin/jq or ./jq).
  • Consider reordering examples or providing both Windows and Linux/macOS examples side-by-side to ensure parity.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-visual-studio-tools-get-started.md ...adoop/apache-hadoop-visual-studio-tools-get-started.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 and Visual Studio, providing only instructions and examples for using Data Lake Tools within Visual Studio on Windows. There are no Linux or cross-platform alternatives mentioned, and all tooling, workflows, and screenshots are specific to Windows environments. Linux users are not provided with equivalent guidance or examples for connecting to HDInsight clusters, running Hive queries, or managing resources.
Recommendations
  • Add equivalent instructions for Linux users, such as using VS Code, command-line tools, or other IDEs compatible with Linux.
  • Provide examples of connecting to HDInsight clusters and running Hive queries using Linux-native tools (e.g., Hive CLI, Beeline, or web-based interfaces).
  • Include screenshots and workflows for Linux environments, or clarify cross-platform options where available.
  • Mention and link to alternative tools for non-Windows users, such as Azure CLI, Jupyter Notebooks, or browser-based Azure portal workflows.
  • Clearly state platform limitations and offer guidance for users on macOS and Linux at the beginning of the article.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/hdinsight-troubleshoot-data-lake-files.md ...sight/hadoop/hdinsight-troubleshoot-data-lake-files.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page provides a detailed PowerShell script for certificate renewal and management, with no equivalent Bash or Linux-native example. The use of PowerShell and Windows-centric tools (e.g., New-SelfSignedCertificate, AzureRm cmdlets) is exclusive, and Linux alternatives (such as OpenSSL, Azure CLI, or Bash scripting) are not mentioned. This creates a bias toward Windows users and may hinder Linux users who manage HDInsight clusters from non-Windows environments.
Recommendations
  • Provide equivalent Bash or Azure CLI examples for certificate creation, management, and assignment.
  • Include instructions for using OpenSSL to generate certificates on Linux.
  • Show how to use Azure CLI (az ad app credential, az hdinsight) for certificate/key management.
  • Explicitly state OS requirements for provided scripts, and offer cross-platform alternatives.
  • Ensure troubleshooting steps and commands are platform-agnostic or offer both Windows and Linux options.
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-09 00:34
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 focusing on Azure PowerShell as the primary method for running Sqoop jobs, mentioning Windows-specific tools (.NET SDK, PowerShell) before Linux alternatives, and lacking direct Linux command-line examples. The setup and walkthroughs are tailored to Windows users, with Linux options referenced but not detailed or prioritized.
Recommendations
  • Provide explicit Linux and macOS command-line examples for running Sqoop jobs, including SSH usage and Bash scripts.
  • Reorder the 'Run Sqoop jobs' section to present cross-platform or Linux-native methods (e.g., SSH, Bash) before Windows-specific tools.
  • Include walkthroughs or links for Linux and macOS users with step-by-step instructions, not just references.
  • Highlight any differences or limitations for Linux users in a dedicated section, and suggest workarounds where possible.
  • Ensure parity in tooling by mentioning Linux equivalents (e.g., Azure CLI, SSH) alongside Windows tools like PowerShell.
GitHub Create Pull Request
Hdinsight https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/submit-apache-hadoop-jobs-programmatically.md ...t/hadoop/submit-apache-hadoop-jobs-programmatically.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 prominently featuring Microsoft-specific tools (.NET SDK and PowerShell) alongside curl. PowerShell, a Windows-centric tool, is given equal footing with curl, but there are no Linux shell or scripting examples (e.g., Bash). The .NET SDK is also Windows-oriented. Linux-native tools and workflows are missing or not mentioned, and the ordering of resources places Windows tools first.
Recommendations
  • Add examples using Bash scripts and Linux command-line tools (e.g., wget, native Hadoop CLI).
  • Include instructions for submitting jobs from Linux environments, not just Windows/PowerShell.
  • Reorder examples so that cross-platform tools (like curl) are listed first, followed by platform-specific tools.
  • Explicitly mention Linux compatibility and provide parity in examples for both Windows and Linux users.
  • Consider adding Python SDK examples, which are widely used on Linux.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page shows some Windows bias, especially in the troubleshooting section for 'InvalidNetworkConfigurationErrorCode'. PowerShell and Windows VM options are mentioned explicitly, and the deprecated parameter 'EnableVmProtection' is referenced in the context of PowerShell and Azure Runbooks without equivalent Linux CLI or automation examples. While Linux commands (ssh, nslookup, dig) are present, Windows tools and patterns (PowerShell, Windows VM as DNS forwarder) are mentioned first or exclusively in some cases. There is a lack of parity in providing Linux CLI examples for network troubleshooting and automation.
Recommendations
  • Provide equivalent Azure CLI or Bash script examples alongside PowerShell commands for network troubleshooting and automation.
  • Explicitly mention Linux VM options before or alongside Windows VM options when discussing DNS forwarding setup.
  • Include references to Linux-native tools (e.g., nmcli, resolvectl) for network configuration validation.
  • Clarify that automation and scripting can be done with Azure CLI, Bash, or Ansible, not just PowerShell and Runbooks.
  • Ensure all troubleshooting steps have both Windows and Linux variants, especially for VM creation, DNS setup, and network validation.
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: 2026-01-09 00:34
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 exclusively referencing the Azure portal (a web GUI often associated with Windows workflows), mentioning Azure PowerShell and Azure Classic CLI as deployment options before any Linux-native tools, and omitting explicit Linux command-line examples (such as Bash, SSH, or Azure CLI usage). There are no step-by-step instructions for Linux users, and the troubleshooting and installation sections do not provide parity for Linux-based workflows.
Recommendations
  • Add explicit examples using Azure CLI commands for installing and managing HDInsight applications, as Azure CLI is cross-platform and preferred by many Linux users.
  • Include step-by-step instructions for performing tasks via SSH and Bash scripts, especially for connecting to edge nodes and managing applications.
  • Mention and demonstrate Linux-native tools and workflows (e.g., using curl, scp, or Linux package managers) where relevant.
  • Ensure that references to PowerShell or Windows-specific tools are balanced with Linux equivalents, and present both options side-by-side.
  • Clarify that HDInsight clusters are Linux-based by default and highlight Linux-friendly management options in the prerequisites and next steps.
GitHub Create Pull Request
← Previous Page 9 of 35 Next →