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 526-550 of 867 flagged pages
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-create-linux-clusters-arm-templates.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-create-linux-clusters-arm-templates.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is mentioned before Azure CLI, and Visual Studio (a Windows-centric tool) is highlighted as a primary development environment for deploying templates. The .NET client library example in the 'Next steps' section also links to a Windows-specific page. While Azure CLI is included, Linux-native tools and workflows are not given equal prominence or examples.
Recommendations
- Ensure Azure CLI examples and references are presented before or alongside PowerShell, emphasizing its cross-platform nature.
- Include examples or guidance for using Linux-native editors (such as Vim, Emacs, nano) and command-line tools for template editing and deployment.
- Highlight cross-platform development environments (e.g., Visual Studio Code) more prominently than Windows-only tools like Visual Studio.
- Provide links to .NET client library examples that are not Windows-specific, or include Python/Java SDK examples which are more common on Linux.
- Add a section or callout explicitly addressing Linux users, summarizing recommended tools and workflows for template deployment.
Create Pull Request
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-create-linux-clusters-with-secure-transfer-storage.md
...oop-create-linux-clusters-with-secure-transfer-storage.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing PowerShell instructions before Azure CLI, referencing PowerShell-specific cmdlets, and not providing explicit Linux shell or Bash examples. The use of 'PowerShell' as a primary automation tool and the lack of parity in example ordering or depth for Linux users may disadvantage those on non-Windows platforms.
Recommendations
- Present Azure CLI instructions before or alongside PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
- Include explicit Bash/shell command examples where appropriate, especially for common Linux administration tasks.
- Balance the depth and detail of PowerShell and Azure CLI sections to ensure Linux users receive equally comprehensive guidance.
- Consider adding a section or callout specifically for Linux/macOS users, highlighting any differences or best practices.
- Review linked resources to ensure they also provide Linux-friendly instructions and not just Windows/PowerShell guidance.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-scaling-best-practices.md
...articles/hdinsight/hdinsight-scaling-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by listing PowerShell as the first utility for scaling clusters, providing PowerShell-specific cmdlets, and referencing Windows-style paths in some command examples. While Azure CLI and SSH/bash commands are included, the ordering and emphasis on PowerShell and Windows tools suggest a preference for Windows environments. There are no missing Linux examples, but the documentation could better balance the presentation of Windows and Linux tools and workflows.
Recommendations
- List Azure CLI before PowerShell in the utilities table, as CLI is cross-platform and more commonly used on Linux/macOS.
- Explicitly mention that all CLI and SSH/bash commands work on Linux, macOS, and Windows (with WSL or compatible shells).
- Where Windows-style paths (e.g., %HBASE_HOME%\bin) are used, provide equivalent Linux-style paths (e.g., $HBASE_HOME/bin) or clarify that the instructions apply to both environments.
- Ensure that all PowerShell examples are paired with equivalent bash/CLI examples where applicable.
- Add a note or section highlighting Linux/macOS usage, especially for SSH and command-line operations.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-customize-cluster-bootstrap.md
...nsight/hdinsight-hadoop-customize-cluster-bootstrap.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page is heavily biased toward Windows and PowerShell usage. All code samples and detailed walkthroughs are provided exclusively in PowerShell, with no equivalent Bash, CLI, or Linux-native scripting examples. The prerequisites and appendix focus solely on Windows tooling (PowerShell, .NET SDK), and the only mention of Linux is a link to a separate page, rather than integrated examples. There is no demonstration of how to perform the same tasks using Azure CLI, Bash scripts, or Linux-native tools.
Recommendations
- Add equivalent examples using Azure CLI and Bash scripts for customizing HDInsight clusters, demonstrating parity with the PowerShell examples.
- Include Linux prerequisites (e.g., Azure CLI installation) alongside PowerShell/Az Module instructions.
- Present cross-platform options (Azure CLI, REST API, ARM templates) before or alongside Windows-specific tools like PowerShell.
- Integrate Linux-focused examples directly into the main documentation, rather than relegating them to separate pages.
- Explicitly mention that all approaches are cross-platform where applicable, and clarify any Windows-only limitations.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-sales-insights-etl.md
...ain/articles/hdinsight/hdinsight-sales-insights-etl.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Bash (Linux/macOS) and Azure CLI examples for most operations, but when it comes to triggering the Azure Data Factory pipeline, it gives a detailed PowerShell example and only mentions the Azure portal as an alternative. There is no equivalent Bash or Azure CLI example for triggering the pipeline, which may disadvantage Linux users. Additionally, Power BI Desktop (a Windows-only tool) is the only visualization tool mentioned, and its steps are detailed without Linux alternatives. PowerShell is presented before the portal method, reinforcing a Windows-first approach.
Recommendations
- Provide an Azure CLI or Bash example for triggering the Data Factory pipeline, not just PowerShell.
- Mention and, if possible, provide steps for using Power BI on the web or suggest open-source, cross-platform alternatives for data visualization.
- When listing ways to trigger pipelines, present CLI or cross-platform methods before or alongside PowerShell.
- Explicitly state which steps are cross-platform and which are Windows-only, and offer alternatives where possible.
- Consider including a table summarizing which tools/steps are available on Windows, Linux, and macOS.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-linux-information.md
...ticles/hdinsight/hdinsight-hadoop-linux-information.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation is generally Linux-focused, as expected for HDInsight on Linux, with Bash and Linux command-line examples (curl, jq, hdfs dfs). However, there are subtle Windows biases: Windows tools (PowerShell, Visual Studio) are mentioned as access methods for Azure Data Lake Storage, and in some lists, Windows-centric tools or SDKs (e.g., .NET, Visual Studio) are mentioned before Linux-native equivalents. PowerShell is listed as a primary method for accessing Data Lake Storage, and there is no explicit mention of Linux alternatives for some tasks (e.g., Data Lake Tools for Visual Studio).
Recommendations
- Where PowerShell or Visual Studio tools are mentioned, also explicitly list equivalent Linux-native tools or workflows (e.g., Bash scripts, Linux SDKs, cross-platform editors).
- When listing SDKs or tools, avoid putting Windows-centric tools (PowerShell, Visual Studio, .NET) before Linux-native options unless there is a technical reason; consider alphabetical or platform-neutral ordering.
- For every PowerShell example or reference, provide a Linux/Bash/CLI equivalent if possible.
- Highlight cross-platform tools (e.g., Azure CLI, Python SDKs) as primary options, and clarify when a tool is Windows-only.
- If a tool is only available on Windows (e.g., Data Lake Tools for Visual Studio), note this explicitly and suggest Linux alternatives where possible.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-migrate-dotnet-to-linux.md
.../hdinsight/hdinsight-hadoop-migrate-dotnet-to-linux.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows-first bias by focusing on migration from Windows-based HDInsight and providing instructions that rely exclusively on Windows tools (Visual Studio, .NET Portability Analyzer as a Visual Studio extension). There are no examples or guidance for performing portability analysis, building, or testing on Linux systems, nor are cross-platform or Linux-native tools mentioned.
Recommendations
- Include instructions for running portability analysis using cross-platform tools or command-line alternatives (e.g., .NET Portability Analyzer CLI, if available).
- Provide examples of building and testing .NET applications using Mono or .NET SDK on Linux (e.g., using dotnet CLI or msbuild on Linux).
- Mention Linux-native editors or IDEs (such as VS Code or JetBrains Rider) for users who may not have access to Visual Studio on Windows.
- Add explicit examples of file path handling and other platform-specific code considerations, with Linux path examples.
- Reorder sections or add parallel Linux workflows so that Linux-native approaches are presented alongside or before Windows-specific instructions.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-storage-sharedaccesssignature-permissions.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-storage-sharedaccesssignature-permissions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a clear Windows bias. PowerShell is the first and most detailed method shown for all major operations, with full scripts provided. The Azure CLI section uses Windows-style variable syntax (set VAR=VALUE, %VAR%), and explicitly notes that 'the use of variables in this section is based on a Windows environment', without providing a Bash/Linux equivalent. There are no Bash/Linux-native CLI examples, and no mention of Linux tools for scripting or automation. The C# example assumes Visual Studio, a Windows-centric IDE. While the prerequisites mention SSH and Python, the main automation and configuration flows are Windows/PowerShell-centric, and Linux users are left to adapt the examples themselves.
Recommendations
- Provide Azure CLI examples using Bash syntax (export VAR=VALUE, $VAR) alongside or before Windows CMD syntax.
- Include Bash shell scripts for automation tasks, especially for cluster creation and storage configuration.
- Offer guidance or examples using cross-platform editors/IDEs (e.g., VS Code) instead of only Visual Studio.
- Reorder sections to present cross-platform or Linux-native methods (Azure CLI with Bash, Python) before or alongside PowerShell and Windows-specific tools.
- Explicitly call out any differences or required adaptations for Linux users, and link to relevant Linux documentation where appropriate.
- Where PowerShell is used, note the availability of PowerShell Core on Linux, or provide equivalent Bash commands.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-upload-data.md
.../blob/main/articles/hdinsight/hdinsight-upload-data.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page shows a moderate Windows bias. Windows-specific tools (Azure PowerShell, Cerulea, CloudXplorer, CloudBerry Explorer) are listed, sometimes without Linux equivalents. Azure PowerShell is included as a main utility for uploading data, but no Linux shell or Bash/Azure CLI example is provided in parallel. In tool tables, Windows-only tools are present, and the order of presentation sometimes puts Windows tools before Linux alternatives. There are no explicit Linux command-line examples for uploading data outside of the Hadoop command, and no Bash/Azure CLI walkthrough is shown.
Recommendations
- Add explicit Linux/Bash/Azure CLI examples for uploading data to Azure Storage, not just Hadoop commands.
- Provide PowerShell and Bash/Azure CLI examples side-by-side where possible.
- Ensure that for every Windows-only tool mentioned, a Linux-compatible alternative is also listed or recommended.
- Reorder tool tables and examples so that cross-platform or Linux tools are not presented after Windows-only tools.
- Highlight cross-platform utilities (like AzCopy, Azure CLI, Azure Storage Explorer) before Windows-only tools.
- Consider adding a section specifically for Linux users, detailing common workflows and tools.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/manage-clusters-runbooks.md
...ob/main/articles/hdinsight/manage-clusters-runbooks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses PowerShell for all scripting and automation examples, with no mention of alternatives such as Python or Bash. All runbooks are created as PowerShell scripts, and the only tooling referenced is Azure PowerShell modules. There are no examples or guidance for users who may prefer or require Linux-native tools, Bash scripting, or cross-platform automation languages. The structure and language assume PowerShell as the default, which is historically associated with Windows environments, even though Azure Automation supports Python runbooks and HDInsight clusters are often Linux-based.
Recommendations
- Provide equivalent examples using Python runbooks, which are supported in Azure Automation and are cross-platform.
- Include Bash/CLI-based automation examples for users who prefer Linux-native scripting.
- Mention and link to Azure CLI and REST API alternatives for cluster management, not just PowerShell modules.
- Rephrase sections to refer to 'PowerShell or Python' runbooks, rather than only PowerShell.
- Add a note clarifying that PowerShell Core is cross-platform, but also highlight other supported scripting languages.
- Ensure screenshots and instructions are not exclusively tied to Windows/PowerShell environments.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/service-endpoint-policies.md
...b/main/articles/hdinsight/service-endpoint-policies.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples, but the CLI example is written in a way that is not fully cross-platform (it uses PowerShell-style variable assignment and arrays), and the PowerShell example is given in full. There are no explicit Linux shell (bash) examples, and the CLI example is not presented in a Linux-friendly format. PowerShell is mentioned and shown in detail, which may bias the documentation towards Windows users.
Recommendations
- Provide a true bash/Linux shell example using Azure CLI, with standard bash variable assignment and array handling.
- Clearly separate Azure CLI (cross-platform) and PowerShell (Windows-centric) examples, labeling them as such.
- Present the Azure CLI (bash) example before the PowerShell example to avoid Windows-first bias.
- Avoid using PowerShell array syntax in CLI examples; use bash-compatible syntax instead.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide guidance for each platform if necessary.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/use-pig.md
...ocs/azure-docs/blob/main/articles/hdinsight/use-pig.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias towards Windows by highlighting SQL Server Integration Services (SSIS) and the Azure Feature Pack—both Windows-centric tools—for running Pig jobs, without mentioning equivalent Linux-native options or command-line examples. There are no walkthroughs or examples for running Pig jobs from a Linux shell or using cross-platform tools, and the only integration scenario described is with a Windows-based toolset.
Recommendations
- Add examples for running Pig jobs directly from a Linux shell using SSH, Bash, or cross-platform tools like PuTTY or OpenSSH.
- Include walkthroughs for submitting Pig jobs via the Azure CLI, which is cross-platform.
- Mention and provide examples for using Linux-native scheduling and orchestration tools (e.g., cron, Airflow) to run Pig jobs.
- Balance integration examples by describing both Windows (SSIS) and Linux (shell scripting, CLI) approaches.
- Explicitly state that HDInsight clusters are Linux-based by default and provide guidance for both Windows and Linux users.
Hdinsight
Azure Monitor Agent (AMA) migration guide for Azure HDInsight clusters
...cs/blob/main/articles/hdinsight/azure-monitor-agent.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. The PowerShell approach is presented before Azure CLI, and PowerShell examples are more detailed and extensive. References to Windows-specific tools (e.g., PowerShell, azcopy) and links to Windows client documentation are present. While Azure CLI instructions are provided, PowerShell is emphasized and appears first, which may create friction for Linux/macOS users.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Expand Azure CLI instructions to match the detail and clarity of PowerShell examples.
- Explicitly mention Linux/macOS compatibility and prerequisites for CLI and tools (e.g., azcopy, jq).
- Avoid linking only to Windows-specific documentation (e.g., 'Set up the Azure Monitor agent on Windows client devices'); provide cross-platform links.
- Add troubleshooting notes or tips for Linux/macOS environments where commands or tools may differ.
Hdinsight
Configure clusters for Microsoft Entra integration
...ned/apache-domain-joined-configure-using-azure-adds.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a notable Windows bias. The only code example for certificate creation uses PowerShell, with no Linux or cross-platform alternative. Network validation and troubleshooting steps exclusively reference Windows VMs and Windows tools (e.g., ldp.exe), with no mention of Linux/macOS equivalents. The guidance for joining VMs to the domain and verifying connectivity is Windows-centric, and Windows tools are mentioned before any cross-platform options. Linux/macOS users are left to infer their own methods for these critical steps.
Recommendations
- Provide equivalent Linux/macOS commands for certificate creation (e.g., using OpenSSL).
- Include instructions for joining Linux VMs to the domain and verifying domain connectivity.
- Suggest Linux/macOS tools for LDAP testing (e.g., ldapsearch, openssl s_client) and network troubleshooting.
- Present cross-platform examples and tools alongside Windows examples, or in parallel sections.
- Clarify which steps are OS-agnostic and which require platform-specific instructions.
Hdinsight
Manage Enterprise Security Package clusters - Azure HDInsight
...hdinsight/domain-joined/apache-domain-joined-manage.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias by frequently referencing Windows-centric tools (e.g., Visual Studio Code, Visual Studio Tools, Power BI, Excel), and listing them before or in place of Linux/macOS alternatives. There is a lack of explicit Linux/macOS instructions or examples, especially for connecting to clusters or using Beeline. While some tools are cross-platform (e.g., VS Code, IntelliJ, Eclipse), the documentation does not clarify this or provide Linux-specific guidance, which may create friction for non-Windows users.
Recommendations
- Explicitly mention cross-platform compatibility for tools like VS Code, IntelliJ, and Eclipse, and provide Linux/macOS installation or usage notes where relevant.
- Include Linux/macOS-specific examples for connecting to clusters (e.g., Beeline usage from a Linux terminal, SSH commands).
- Balance references to Windows-only tools (e.g., Visual Studio Tools, Power BI, Excel) with Linux/macOS alternatives (e.g., DBeaver, Tableau, or open-source BI tools).
- Where possible, provide screenshots or UI instructions from Linux/macOS environments, or note any differences.
- Clarify any prerequisites or steps that are Windows-specific, and provide equivalent instructions for Linux/macOS.
Hdinsight
Apache Hive policies in Apache Ranger - Azure HDInsight
...insight/domain-joined/apache-domain-joined-run-hive.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, specifically using Excel and the Microsoft Hive ODBC driver for data import and policy testing. All step-by-step examples and screenshots are for Windows tools (Excel, ODBC driver setup), with no mention of Linux/macOS alternatives or equivalent workflows. The prerequisites and instructions assume the user has access to Microsoft Office products, and there are no examples for connecting to Hive from Linux or macOS clients (e.g., via Beeline, DBeaver, or other cross-platform tools).
Recommendations
- Add parallel instructions for Linux/macOS users, such as connecting to Hive via Beeline, JDBC, or cross-platform database clients.
- Include examples and screenshots for non-Windows tools (e.g., LibreOffice, DBeaver, or command-line SQL clients).
- Mention and link to relevant documentation for Linux/macOS ODBC/JDBC driver installation and usage.
- Clarify that the described workflow is Windows-specific and provide guidance for users on other platforms.
- Reorder or balance examples so that Windows and Linux/macOS approaches are presented equally.
Hdinsight
Overview of enterprise security in Azure HDInsight
...hdinsight/domain-joined/hdinsight-security-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Authentication and enterprise security are described primarily in terms of Active Directory and Microsoft Entra Domain Services, which are Windows-centric technologies. PowerShell is mentioned as a client tool for cluster access, but no equivalent Linux/macOS command-line tools (e.g., SSH, curl, or Linux CLI examples) are provided. The documentation does not offer examples or guidance for Linux/macOS users regarding authentication, authorization, or auditing, nor does it mention cross-platform alternatives to Windows tools.
Recommendations
- Include Linux/macOS-specific examples for cluster authentication and access (e.g., SSH, curl, Linux CLI).
- Mention and provide guidance for using cross-platform tools (such as Kerberos, LDAP, or SSSD) for authentication where applicable.
- When listing client tools (PowerShell, ODBC, JDBC, REST APIs), ensure Linux/macOS equivalents are described and shown in examples.
- Clarify which features and procedures are platform-agnostic and which require Windows-specific infrastructure.
- Add explicit instructions or links for Linux/macOS users to perform common tasks (e.g., accessing clusters, configuring security features).
Hdinsight
LDAP sync in Ranger and Apache Ambari in Azure HDInsight
...lob/main/articles/hdinsight/domain-joined/ldap-sync.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-centric tools (e.g., ldp.exe, sAMAccountName, Samba/Winbind) and suggesting Windows-specific patterns for LDAP testing and sync verification. Linux alternatives (such as ldapsearch) are not mentioned, and Windows tools are listed before or instead of cross-platform equivalents. This may create friction for Linux/macOS users who need to perform similar tasks.
Recommendations
- Include Linux/macOS equivalents for all Windows tools mentioned (e.g., suggest ldapsearch instead of or alongside ldp.exe).
- Provide examples of how to test LDAP filters using Linux-native commands.
- Clarify Samba/Winbind usage and provide guidance for environments where these are not present or alternatives are preferred.
- Ensure that instructions and troubleshooting steps are platform-neutral or offer parallel steps for both Windows and Linux/macOS users.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page for Azure HDInsight ID Broker (HIB) demonstrates a moderate Windows bias. The architecture and authentication infrastructure are described as running on a Windows Server VM, with no mention of Linux alternatives or parity. Windows-centric tools (Active Directory Federation Services, Microsoft Entra Domain Services) are referenced exclusively. While some examples (e.g., curl) are cross-platform, the underlying infrastructure and administrative patterns are Windows-focused, and Linux-specific guidance is missing.
Recommendations
- Explicitly state whether the HDInsight ID Broker node can run on Linux, or clarify why Windows Server is required.
- Provide guidance for Linux/macOS administrators on managing and troubleshooting the ID Broker node.
- Include Linux-specific examples for SSH, Kerberos, and client integration (e.g., using kinit, keytab, or Linux-based automation).
- Mention Linux equivalents or alternatives to Windows tools (such as AD FS), or clarify if none exist.
- Ensure parity in troubleshooting and operational instructions for non-Windows environments.
Hdinsight
Cluster creation fails with DomainNotFound error in Azure HDInsight
...hdinsight/domain-joined/troubleshoot-domainnotfound.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Control Panel Ui Reference
Missing Linux Example
Summary
The documentation presents Windows VM troubleshooting steps before Ubuntu/Linux, and references the Windows Control Panel UI for domain joining, while the Linux instructions are less detailed and rely on an external script. There is no explicit Linux command-line example for domain joining, and the Windows method is described in more familiar, user-friendly terms.
Recommendations
- Provide Linux (Ubuntu) domain join instructions with explicit command-line steps (e.g., using realmd, samba, or adcli) instead of referencing an external script.
- Present Windows and Linux troubleshooting steps in parallel, or start with a neutral introduction before listing OS-specific instructions.
- Avoid referencing Windows-specific UI elements (like Control Panel) without Linux equivalents.
- Ensure both Windows and Linux examples are equally detailed and actionable.
Hdinsight
Apache Ambari heartbeat issues in Azure HDInsight
.../hadoop/apache-ambari-troubleshoot-heartbeat-issues.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias by referencing PowerShell cmdlets (Disable-AzHDInsightMonitoring) for disabling Azure Monitor logging, without providing an equivalent Bash, Linux CLI, or REST API example. Windows-specific tooling is mentioned exclusively in the logging section, and the PowerShell solution is presented first and solely. However, the majority of troubleshooting steps use Linux-native commands (ps, top, service, kill), which are suitable for Linux/macOS users.
Recommendations
- Provide equivalent Linux/Bash/CLI or REST API instructions for disabling Azure Monitor logging, alongside the PowerShell example.
- Clarify whether the PowerShell cmdlet must be run from a Windows machine or if cross-platform alternatives exist.
- When mentioning Windows-specific tools, always offer Linux/macOS alternatives in parallel.
- Consider listing Linux-native solutions first when the cluster nodes are Linux-based, as is typical for HDInsight.
Hdinsight
Extract, transform, and load (ETL) at scale - Azure HDInsight
...rticles/hdinsight/hadoop/apache-hadoop-etl-at-scale.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates moderate Windows bias, particularly in the 'Ingest file storage and result storage' section. Windows-centric tools (PowerShell, AzCopy) are mentioned first and most prominently for data ingestion into Azure Storage, with no explicit Linux/macOS CLI examples or parity. While some Linux-compatible tools (DistCp, Sqoop) are referenced for Data Lake Storage, the overall pattern prioritizes Windows workflows and tools, which may create friction for Linux/macOS users.
Recommendations
- Provide explicit Linux/macOS CLI examples for data ingestion (e.g., using Azure CLI, curl with WebHDFS, or Python SDK).
- Mention cross-platform tools (Azure CLI, REST APIs) before or alongside Windows-specific tools like PowerShell and AzCopy.
- Clarify which ingestion tools are cross-platform and provide links to their Linux/macOS usage documentation.
- Add example workflows for Linux/macOS users, especially in sections where only Windows tools are currently referenced.
Hdinsight
Use C# with MapReduce on Hadoop in HDInsight - Azure
...oop/apache-hadoop-dotnet-csharp-mapreduce-streaming.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a notable Windows bias by relying heavily on Visual Studio for building and uploading executables, referencing Data Lake Tools for Visual Studio, and providing PowerShell as the only scripted automation example. Linux alternatives for building C# code (e.g., using Mono or .NET CLI) and uploading files (e.g., Azure CLI, azcopy, or SCP) are not mentioned. The order of presentation also places Windows-centric tools before any Linux equivalents, and PowerShell is the only automation script provided.
Recommendations
- Add instructions for building C# projects on Linux/macOS using Mono or .NET CLI.
- Include examples for uploading files to HDInsight storage using Azure CLI, azcopy, or SCP.
- Provide a Bash script example for running MapReduce jobs and downloading results, alongside the PowerShell script.
- Mention cross-platform editors (e.g., VS Code) as alternatives to Visual Studio.
- Reorder sections to present platform-neutral or Linux/macOS options alongside or before Windows-specific tools.
Hdinsight
Java user-defined function (UDF) with Apache Hive Azure HDInsight
...ticles/hdinsight/hadoop/apache-hadoop-hive-java-udf.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is notably Windows-centric: all local environment setup commands use Windows Command Prompt syntax, file editing is shown with Notepad, and troubleshooting provides only PowerShell solutions for line ending issues. There are no equivalent Linux/macOS shell commands or editor suggestions, and the test environment is explicitly stated as Windows. This creates friction for Linux/macOS users, especially in the setup and troubleshooting steps.
Recommendations
- Provide parallel Linux/macOS shell commands (e.g., mkdir, cd, rm -rf) alongside Windows Command Prompt commands.
- Suggest cross-platform or Linux-native editors (e.g., nano, vim, VS Code) in addition to Notepad.
- Include Linux/macOS troubleshooting steps for line ending issues (e.g., using dos2unix or sed).
- Note that Maven and Java commands are cross-platform, but clarify any OS-specific differences.
- Explicitly state when a command or tool is Windows-only and provide alternatives for other platforms.
- Consider reordering examples or providing tabs for Windows and Linux/macOS instructions.
Hdinsight
C#, Apache Hive & Apache Pig on Apache Hadoop - Azure HDInsight
...ght/hadoop/apache-hadoop-hive-pig-udf-dotnet-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Visual Studio Heavy
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio, for building C# UDFs. All project creation, build, and upload steps are described using Visual Studio and its Azure integration, with no mention of Linux-native alternatives (e.g., MonoDevelop, command-line builds with msbuild, or uploading via azcopy/CLI). While the runtime is Linux-based, the developer workflow assumes Windows, creating friction for Linux/macOS users.
Recommendations
- Add instructions for building C# projects using MonoDevelop or command-line tools (e.g., msbuild) on Linux/macOS.
- Provide examples for uploading .exe files using Azure CLI, azcopy, or other cross-platform tools, not just Visual Studio.
- Mention alternative IDEs and workflows for non-Windows users, and clarify that Visual Studio is optional.
- Reorder prerequisites and examples so that cross-platform methods are presented before or alongside Windows-specific ones.