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 501-525 of 867 flagged pages
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-optimize-hive-query.md
...cles/hdinsight/hdinsight-hadoop-optimize-hive-query.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation shows a mild Windows bias by mentioning Azure PowerShell and the Azure portal as primary tools for cluster configuration and scaling, with no explicit mention of Linux-native command-line tools or examples (such as Bash, SSH, or Azure CLI on Linux). The workflow examples and screenshots focus on the Azure portal and PowerShell, and there are no Linux shell or script examples provided for common tasks. While the article does mention that Tez is enabled by default on Linux-based clusters, it does not provide Linux-specific operational guidance or parity in tooling examples.
Recommendations
- Include explicit examples using Azure CLI commands in Bash or Linux shell for cluster creation and scaling, alongside or before PowerShell examples.
- Add references or examples for managing HDInsight clusters from Linux environments, such as using SSH or Linux-native tools.
- Balance the order of tool mentions (e.g., mention Azure CLI before or alongside PowerShell and the Azure portal).
- Provide screenshots or walkthroughs for Linux-based workflows where applicable.
- Clarify when instructions or features are specific to Windows or Linux, and ensure Linux users are not left out of operational guidance.
Create Pull Request
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-supported-node-configuration.md
...es/hdinsight/hdinsight-supported-node-configuration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by specifically referencing PowerShell and providing instructions tailored to it (e.g., how to format VM SKU identifiers for use in PowerShell scripts). There are no equivalent examples or explicit mentions of Linux shell scripting or tools. The language and examples prioritize Windows/PowerShell usage, with Linux alternatives either omitted or only referenced generically as 'other scripts.'
Recommendations
- Include explicit examples for both PowerShell (Windows) and Bash (Linux/macOS) when referencing scripting tasks, such as how to use VM SKU identifiers in deployment scripts.
- Avoid language that prioritizes Windows tools (e.g., 'PowerShell or Azure CLI scripts'); instead, use neutral phrasing like 'deployment scripts using PowerShell, Bash, or Azure CLI.'
- Add a note or section demonstrating how to perform equivalent tasks on Linux, such as using Azure CLI in Bash or shell scripts.
- Where possible, provide cross-platform code snippets or links to platform-specific documentation for both Windows and Linux users.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-linux-ambari-ssh-tunnel.md
...rticles/hdinsight/hdinsight-linux-ambari-ssh-tunnel.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation provides both cross-platform (ssh command) and Windows-specific (PuTTY) instructions for creating SSH tunnels. However, it gives detailed, step-by-step instructions for PuTTY, a Windows-only tool, and highlights browser limitations specific to Windows (e.g., Edge, Internet Explorer, Chrome's reliance on Windows proxy settings). The PuTTY section is more extensive than the ssh command section, and no Linux GUI alternatives (such as GNOME Terminal, KDE Konsole, or Linux SSH GUI clients) are mentioned. The document also references Windows proxy settings and browser behaviors before discussing cross-platform solutions.
Recommendations
- Add step-by-step instructions for creating SSH tunnels using common Linux GUI SSH clients (e.g., GNOME Terminal, KDE Konsole, or tools like Remmina or OpenSSH GUI frontends).
- Balance the detail level between the ssh command section and the PuTTY section, ensuring Linux users have equally detailed guidance.
- Explicitly mention that the ssh command works on Linux, macOS, and Windows (via WSL or native OpenSSH), and provide example commands for these platforms.
- Include screenshots or walkthroughs for Linux-based SSH tunnel setup using graphical tools, if available.
- When discussing browser proxy settings, include Linux-specific instructions (e.g., for Firefox or Chrome on Linux) and note any differences.
- Avoid focusing on Windows proxy limitations first; instead, present cross-platform solutions up front, then note any OS-specific caveats.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-troubleshoot-failed-cluster.md
...les/hdinsight/hdinsight-troubleshoot-failed-cluster.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. PowerShell is mentioned as an option for cluster management, but no equivalent Bash or Linux shell example is provided. The Azure portal (a GUI, often associated with Windows workflows) is referenced first for cluster information, with Azure CLI (cross-platform) following, and PowerShell mentioned next. There are no explicit Linux command-line examples for common troubleshooting tasks (e.g., viewing logs, restarting services), except for the use of curl and netstat, which are standard on Linux. The documentation refers to the Ambari UI, which is Linux-based, but does not provide parity in command-line examples for Linux users. The directory path for script action logs uses backslashes (\), which is a Windows convention, not Linux.
Recommendations
- When mentioning PowerShell, also provide Bash or Linux shell equivalents for all commands.
- List cross-platform or Linux-native tools (e.g., Azure CLI, Bash scripts) before or alongside Windows/PowerShell tools.
- Use forward slashes (/) for directory paths when referring to Linux-based clusters.
- Add explicit Linux/Bash command examples for common troubleshooting tasks (e.g., viewing logs, restarting services, checking cluster health) to ensure Linux users have clear guidance.
- Clarify when instructions or tools are specific to Windows or Linux, and provide alternatives where possible.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-log-management.md
...ob/main/articles/hdinsight/hdinsight-log-management.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell and Windows-centric tools are frequently mentioned as primary or sole scripting/programmatic examples for log management, with Linux/Unix alternatives often omitted or mentioned only in passing. Windows tools (e.g., Visual Studio, Power Query for Excel, System Center) are listed before or instead of cross-platform or Linux-native tools. Linux-specific log management techniques (e.g., logrotate) are only briefly referenced, and there are few concrete Linux shell or scripting examples compared to the detailed PowerShell guidance.
Recommendations
- Provide equivalent Linux shell (bash) or Python scripting examples wherever PowerShell is referenced, especially for log collection, archiving, and Azure Storage access.
- List cross-platform or Linux-native tools (e.g., Azure CLI, AzCopy, Linux text processing utilities) before or alongside Windows tools like PowerShell, Visual Studio, and Excel.
- Expand on Linux log management techniques (e.g., logrotate, cron jobs, rsyslog) with concrete configuration and usage examples.
- Include explicit Linux/Unix command-line examples for common log management tasks, such as downloading logs from Azure Storage, rotating logs, and aggregating logs.
- Ensure third-party monitoring/logging tools mentioned include both Windows and Linux options, and clarify platform support where relevant.
- Where the Ambari UI or SSH is referenced, provide step-by-step Linux command-line alternatives for accessing and managing logs.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-migrate-granular-access-cluster-configurations.md
...insight-migrate-granular-access-cluster-configurations.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation demonstrates a moderate Windows bias. It references and provides migration details for several Windows-centric tools (Visual Studio, Visual Studio Code, Azure Data Lake and Stream Analytics Tools for Visual Studio, Az.HDInsight PowerShell) and .NET SDKs. PowerShell is given a dedicated migration section, and the only command-line examples for role assignment use Azure CLI (which is cross-platform, but often associated with Windows in Azure docs). Linux-specific tools, shell examples, or patterns are not mentioned. The order of tools and SDKs generally places Windows/PowerShell/.NET before Linux/Java/Python/Go equivalents.
Recommendations
- Include migration or usage examples for Linux-native environments, such as Bash shell scripts or references to Linux package managers for SDK installation.
- Provide parity in documentation for Linux tools (e.g., Azure CLI in Bash, or scripting examples in Bash/zsh, not just PowerShell).
- Add explicit mention of Linux and macOS compatibility for all tools and SDKs, especially Azure CLI and VS Code.
- Balance the order of presentation: alternate or group Windows and non-Windows tools/SDKs together, or explicitly call out cross-platform support.
- If possible, include examples or references for managing HDInsight access from Linux-based automation (e.g., using REST API with curl, Python scripts, or Bash).
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-overview.md
...ocs/blob/main/articles/hdinsight/hdinsight-overview.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 emphasizing Microsoft-centric BI tools (Power BI, Excel with Power Query, Microsoft Hive ODBC Driver), most of which require Windows. There are no equivalent Linux-based BI tool examples or instructions, and the documentation does not mention or recommend cross-platform alternatives. The development tools section also lists primarily Microsoft and Windows-friendly IDEs before others, and does not highlight Linux-native tools or workflows.
Recommendations
- Include examples and instructions for connecting to HDInsight from Linux-based BI tools (e.g., Tableau on Linux, Apache Superset, DBeaver, or other cross-platform SQL/ODBC clients).
- Explicitly mention and provide guidance for using open-source or cross-platform ODBC/JDBC drivers to connect to Hive/Spark from non-Windows environments.
- Balance the listing of development tools by including Linux-native editors (e.g., Emacs, Vim, Atom) and clarify that IntelliJ, Eclipse, and VS Code are cross-platform.
- Where features or integrations are Windows-only (such as Power Query in Excel), clearly label them as such and suggest Linux alternatives where possible.
- Add Linux-specific examples or walkthroughs for common tasks, such as submitting jobs, querying data, or visualizing results, to ensure parity with Windows instructions.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-operationalize-data-pipeline.md
...es/hdinsight/hdinsight-operationalize-data-pipeline.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting SCP and SSH commands in Windows (cmd) syntax first, and in some cases exclusively, while Linux/Unix equivalents are either not shown or are only implied. There is also mention of Windows-specific tools (e.g., Windows Subsystem for Linux, Bash on Windows 10, and Chrome with Foxy Proxy) before or instead of native Linux approaches. The documentation does not provide clear, parallel Linux command-line examples or instructions, which may hinder Linux users.
Recommendations
- For every command-line example, provide both Windows (cmd/PowerShell) and Linux/macOS (bash) syntax side by side.
- When referencing tools like SCP or SSH, clarify the command structure for both Windows and Linux environments, including any differences in syntax or prerequisites.
- Avoid mentioning Windows-specific tools (e.g., Windows Subsystem for Linux, Bash on Windows 10) as the primary or only method; instead, present native Linux workflows first or equally.
- Include explicit instructions for Linux users, such as how to install necessary tools (e.g., OpenSSH client, SCP) and how to use them in a Linux shell.
- Where GUI steps are described (e.g., using the Azure portal), clarify if there are differences for Linux users or provide CLI alternatives where possible.
- Review all code blocks and ensure that bash commands are not labeled as cmd, and vice versa, to avoid confusion.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-private-link.md
...blob/main/articles/hdinsight/hdinsight-private-link.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias in several areas: it provides a VM deployment example using only a Windows 10 image, references RDP and Windows licensing, and suggests using a command prompt for SSH access. PowerShell is mentioned before Azure CLI for cluster creation, and there are no explicit Linux or cross-platform examples for VM deployment or SSH testing. The documentation also references Windows-specific tools and patterns (RDP, Windows licensing) without Linux equivalents.
Recommendations
- Provide parallel Linux-based examples for deploying a test VM (e.g., Ubuntu Server) and accessing the cluster using SSH from a Linux terminal.
- When referencing VM images, include both Windows and popular Linux distributions, and clarify that either can be used.
- Present Azure CLI and PowerShell examples together, or default to Azure CLI for cross-platform parity.
- For SSH access instructions, use generic terminal language and avoid assuming a Windows command prompt; mention how to open a terminal on both Windows and Linux.
- When discussing remote access, mention both RDP (for Windows) and SSH (for Linux) as options, and clarify port usage for each.
- Remove or supplement Windows licensing notes with Linux-specific guidance where appropriate.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. The PowerShell approach is described in detail and appears before the Azure CLI approach, with extensive use of PowerShell cmdlets and scripts. There are multiple references to PowerShell and Windows-specific tools (such as references to the 'Set up the Azure Monitor agent on Windows client devices' documentation). The CLI approach is provided, but it is positioned after the PowerShell approach, and some instructions (such as using 'azcopy' and 'jq') assume familiarity with Linux tooling but are less detailed than the PowerShell section. There are no explicit Linux shell or Bash examples for direct agent management, and the documentation does not mention Linux-specific considerations, even though HDInsight clusters are often Linux-based.
Recommendations
- Reorder the instructions so that Azure CLI examples appear before or alongside PowerShell examples, reflecting the cross-platform nature of HDInsight clusters.
- Add explicit Bash/Linux shell examples for common operations, especially for agent management and DCR association, to better support Linux users.
- Avoid referencing Windows-specific documentation (such as 'Set up the Azure Monitor agent on Windows client devices') unless there is a Linux equivalent or a clear note about Linux applicability.
- Clarify that both PowerShell and CLI approaches are fully supported on Linux-based HDInsight clusters, and note any differences or prerequisites for Linux environments.
- Where possible, provide parity in detail and troubleshooting steps for both PowerShell and CLI/Bash workflows.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/cluster-management-best-practices.md
...rticles/hdinsight/cluster-management-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 Azure PowerShell as a primary method for cluster creation and management, and by referencing Windows-centric tools (PowerShell) before or alongside cross-platform or Linux-native alternatives. While Linux-based cluster creation is mentioned, and there are CLI and cURL options, the prominence and explicit mention of Azure PowerShell (a Windows-first tool) and the lack of explicit Linux shell (bash) examples or emphasis on Linux-native workflows suggest a subtle preference for Windows patterns.
Recommendations
- Ensure that Linux-native command-line examples (e.g., bash scripts) are provided and highlighted equally alongside PowerShell.
- When listing management options, alternate the order or explicitly state parity between PowerShell and CLI/cURL to avoid implying Windows-first workflows.
- Include explicit Linux shell (bash) usage examples where PowerShell is mentioned, especially in quickstart or how-to sections.
- Clarify that Azure CLI and cURL are fully cross-platform and may be preferable for Linux users.
- Consider adding a section or callout specifically for Linux users, summarizing recommended tools and workflows.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell-based instructions and examples for rebooting HDInsight cluster VMs, without offering equivalent CLI or Bash examples for Linux users. The PowerShell method is presented first and in detail, while no Azure CLI, SSH, or Linux-native tooling is mentioned. This may disadvantage users working from Linux or macOS environments.
Recommendations
- Add equivalent instructions and examples using Azure CLI (az hdinsight) for listing and rebooting nodes, as Azure CLI is cross-platform and widely used on Linux.
- Provide Bash or shell script examples for interacting with the REST API (e.g., using curl or httpie) to reboot nodes, including sample request bodies and authentication guidance.
- Explicitly mention that PowerShell examples are for Windows users, and provide parallel guidance for Linux/macOS users.
- Consider reordering or presenting PowerShell and CLI/Bash examples side-by-side to ensure parity and inclusivity.
- Reference relevant Linux tools or commands (such as SSH, if applicable) for troubleshooting or interacting with cluster VMs.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally provides both Linux and Windows options, but there is a tendency to mention or provide Windows/PowerShell examples before Linux/Azure CLI equivalents. PowerShell is often listed before Azure CLI, and Windows Server DNS configuration is referenced before Linux/BIND in some places. There is also a direct link to Windows Server DNS documentation, while Linux/BIND instructions are more detailed but not always referenced as the primary or only option.
Recommendations
- Present Azure CLI and Linux-based examples before or alongside PowerShell/Windows examples to avoid the appearance of Windows-first bias.
- When referencing DNS server configuration, provide equal prominence and links to both Windows Server and Linux/BIND documentation.
- Ensure that all steps and examples are available for both Linux and Windows environments, and that neither is presented as the default or primary approach.
- In sections where PowerShell is used, always provide an equivalent Azure CLI example immediately adjacent, or vice versa.
- Where possible, clarify that both Windows and Linux DNS servers are supported and provide clear, parallel instructions for each.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/disk-encryption.md
...e-docs/blob/main/articles/hdinsight/disk-encryption.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways: PowerShell is used as the only scripting example for deploying ARM templates and enabling encryption at host, with no equivalent Bash or Linux shell examples. Windows/PowerShell tooling (e.g., Undo-AzKeyVaultKeyRemoval) is mentioned before or instead of Linux/CLI alternatives. There is a lack of Linux-native command-line examples (e.g., Bash scripts) for ARM template deployment and key recovery. The documentation assumes familiarity with Windows tools and workflows, which may disadvantage Linux users.
Recommendations
- Provide Bash or Azure CLI script examples for all operations currently shown only in PowerShell, especially for ARM template deployment and enabling encryption at host.
- When referencing tools or commands for key recovery or management, include both PowerShell and Azure CLI (or Bash) equivalents, and list them in parallel or alternate order.
- Avoid assuming the user's platform; clarify when steps are platform-agnostic and when they are not.
- Add explicit Linux/Bash examples for common workflows, such as deploying ARM templates (e.g., using 'az deployment group create') and managing resources.
- Ensure that screenshots and UI walkthroughs are not specific to Windows unless unavoidable, and note any platform-specific differences.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-administer-use-dotnet-sdk.md
...icles/hdinsight/hdinsight-administer-use-dotnet-sdk.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell commands for package installation, referencing the PowerShell client GUID for authentication, and using Windows command prompt syntax (e.g., %HBASE_HOME%\bin) in the HBase section. There are no Linux/bash equivalents for these steps, and the .NET SDK usage is presented in a way that assumes a Windows development environment. Linux-specific instructions, tools, or examples are missing throughout.
Recommendations
- Provide Linux/bash equivalents for all PowerShell commands, such as using dotnet CLI or NuGet CLI for package installation.
- Include Linux shell syntax (e.g., $HBASE_HOME/bin) alongside Windows command prompt examples in the HBase section.
- Clarify that the .NET SDK can be used cross-platform and provide explicit instructions for Linux/macOS environments (e.g., using VS Code or dotnet CLI on Linux).
- Avoid referencing Windows-specific tools or GUIDs (such as the PowerShell client) without mentioning cross-platform alternatives.
- Add a section or callouts for Linux users, ensuring parity in setup, authentication, and usage instructions.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell and Azure Classic CLI as the primary automation/deployment tools, without mentioning Azure CLI (which is cross-platform and more commonly used on Linux). The instructions and examples focus exclusively on the Azure Portal (a GUI), which is more familiar to Windows users, and PowerShell/Classic CLI, with no command-line examples using Bash or Linux-native tools. There are no explicit Linux command-line examples or instructions, and the documentation does not provide parity for Linux users who may prefer scripting or automation via Bash or Azure CLI.
Recommendations
- Add examples and instructions using Azure CLI (az), which is cross-platform and widely used on Linux, for deploying and managing HDInsight applications.
- Include Bash shell command examples for common tasks, such as connecting via SSH, listing applications, or deploying templates.
- When mentioning automation or scripting options, list Azure CLI before or alongside PowerShell and Classic CLI to avoid Windows-first ordering.
- Explicitly state that all features are available and supported on Linux, and provide links to Linux-specific documentation where appropriate.
- Provide parity in troubleshooting and next steps sections by referencing Linux-native tools and workflows.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-restrict-outbound-traffic.md
...icles/hdinsight/hdinsight-restrict-outbound-traffic.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-related FQDNs (e.g., WindowsUpdate, login.windows.net), describing 'Windows login activity', and referencing Windows-centric services before Linux equivalents. There are no explicit Linux or cross-platform command-line examples (e.g., Bash, CLI), and the only Linux-specific mention is a single rule for Ubuntu updates, which is less emphasized. The documentation lacks parity in examples or guidance for Linux users, especially regarding SSH access, firewall rules for Linux tools, or Linux-specific update sources.
Recommendations
- Provide Linux-focused examples and explanations alongside Windows ones, such as referencing both Windows and Linux update sources and login endpoints.
- Include explicit Bash or Azure CLI command-line examples for configuring firewall rules, route tables, and network settings, not just portal-based instructions.
- Clarify that HDInsight clusters can run Linux and Windows workloads, and specify any differences in firewall or network configuration for each OS.
- Expand the 'Target FQDNs' section to include common Linux package repositories (e.g., for CentOS, Red Hat, or other supported distributions) if applicable.
- Add SSH access examples and troubleshooting steps relevant to Linux users, including how to configure firewall and NSG rules for Linux SSH clients.
- Ensure that all references to 'Windows login activity' are balanced with explanations of authentication flows for Linux-based clusters.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-authorize-users-to-ambari.md
...icles/hdinsight/hdinsight-authorize-users-to-ambari.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is presented as the primary scripting example for adding users, with a detailed, multi-step PowerShell script provided before the bash/curl example. Windows tools and patterns (PowerShell, Invoke-WebRequest, Set-ExecutionPolicy) are featured prominently, and the PowerShell example appears before the bash/curl example, suggesting a Windows-first approach. While a bash/curl example is included, it is described as requiring 'slight modifications' for Windows, reinforcing the Windows-centric perspective.
Recommendations
- Present bash/curl (Linux/macOS) and PowerShell (Windows) examples side-by-side or in parallel sections, rather than listing PowerShell first.
- Explicitly mention that both Linux and Windows users are supported, and provide equal detail and troubleshooting for both environments.
- Avoid Windows-specific terminology (e.g., Set-ExecutionPolicy) unless necessary, or provide equivalent Linux/macOS context.
- Where possible, use cross-platform tools (e.g., curl, REST API) as the primary example, and supplement with OS-specific scripts.
- Clarify any differences in behavior or requirements between Windows and Linux environments, especially for script execution.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-capacity-planning.md
...main/articles/hdinsight/hdinsight-capacity-planning.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page is generally platform-neutral but contains subtle Windows bias. It mentions creating PowerShell scripts and scheduling them with Azure Automation as an example for cluster lifecycle automation, without providing equivalent Linux/bash scripting guidance. The only scripting example is PowerShell, and no Linux shell or cross-platform CLI alternatives are mentioned. Additionally, the order of mention puts Windows tools (PowerShell, Azure Automation) before any Linux-native or cross-platform options. There are no explicit Linux examples or references to bash scripting, and the portal UI screenshots do not indicate platform, but the scripting guidance is Windows-centric.
Recommendations
- Provide equivalent Linux/bash scripting examples for cluster provisioning and deletion, alongside PowerShell.
- Mention cross-platform tools such as the Azure CLI (az hdinsight ...) for automation, and provide sample commands.
- When referencing automation, list both Azure Automation (which can run PowerShell or Python) and Linux-native schedulers (e.g., cron jobs) as options.
- Ensure scripting and automation guidance is presented in a platform-neutral or parallel fashion (e.g., 'You can use PowerShell scripts or bash scripts...').
- Add explicit Linux examples or links to Linux-focused automation documentation.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-create-non-interactive-authentication-dotnet-applications.md
...ate-non-interactive-authentication-dotnet-applications.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only C#/.NET examples, referencing NuGet (a Windows-centric package manager), and linking to PowerShell-based authentication guides. There are no Linux-specific instructions, CLI examples, or cross-platform considerations. The workflow assumes development on Windows and omits parity for Linux users or those using non-Windows tools.
Recommendations
- Add equivalent examples using Azure CLI and Bash scripts for authentication and resource management, which are cross-platform.
- Include instructions for setting up and running .NET applications on Linux (e.g., using dotnet CLI, installing dependencies on Ubuntu).
- Reference Linux-friendly package managers and development environments (e.g., dotnet CLI instead of only NuGet/Visual Studio).
- Provide links to documentation for authenticating service principals using Azure CLI or REST APIs, not just PowerShell.
- Explicitly state that the instructions are cross-platform, or provide separate sections for Windows and Linux/Mac users.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-config-for-vscode.md
...main/articles/hdinsight/hdinsight-config-for-vscode.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (e.g., 7z.exe, winutils.exe) and providing only Windows-style paths (e.g., C:\Program Files\, D:\winutils) for configuration settings. There are no Linux or macOS equivalents or examples provided for these settings, and the documentation does not mention how to configure these paths or tools on non-Windows platforms.
Recommendations
- For each configuration property that references a Windows-specific tool or path (such as 7z.exe, winutils.exe, JAVA_HOME, SCALA_HOME, SPARK_HOME), provide equivalent Linux/macOS examples (e.g., /usr/bin/7z, /usr/local/hadoop/bin, /usr/lib/jvm/java-8-openjdk-amd64, /usr/share/scala, /opt/spark).
- Explicitly state when a setting is Windows-only, and provide guidance or alternatives for Linux/macOS users.
- Add a section or table column for Linux/macOS paths and tool locations where applicable.
- Include notes or links to documentation on installing required tools (like 7-Zip, winutils) on Linux/macOS, or clarify if they are not needed on those platforms.
- Ensure that screenshots and instructions (such as keyboard shortcuts) are cross-platform, or provide platform-specific variants.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-restrict-public-connectivity.md
...es/hdinsight/hdinsight-restrict-public-connectivity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell automation examples for managing DNS records and cluster configuration, with no equivalent Bash, Azure CLI, or Linux-native scripting examples. References to PowerShell and Az.* modules are prominent, and PowerShell is mentioned before Azure CLI in the 'Create clusters' section. There is no guidance for users who may be working from Linux or macOS environments, and no mention of cross-platform tooling or alternative workflows.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for all PowerShell examples, especially for DNS record management and cluster configuration.
- When referencing automation, mention both PowerShell and CLI options together, or present CLI/Bash first to balance the order.
- Include explicit notes or sections for Linux/macOS users, clarifying that all operations can be performed cross-platform.
- Reference cross-platform tools (e.g., Azure CLI, REST API) wherever possible, and avoid assuming the user is on Windows.
- Where PowerShell is used, provide a parallel example using Azure CLI commands and/or Bash scripting.
- Audit the documentation for other areas where only Windows-centric tools or patterns are described, and add Linux-friendly alternatives.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-add-storage.md
...ain/articles/hdinsight/hdinsight-hadoop-add-storage.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides a detailed PowerShell script for verifying additional storage accounts but does not offer equivalent Linux/Unix shell (bash) or Azure CLI examples. The verification section leads with PowerShell and omits command-line or scripting guidance for Linux users, despite the cluster being Linux-based. This creates a Windows-first impression and leaves Linux users without parity in operational instructions.
Recommendations
- Add a Linux/bash example for verifying additional storage accounts, such as using curl and jq to query the HDInsight REST API and parse the results.
- Include Azure CLI examples for verification, as Azure CLI is cross-platform and commonly used on Linux.
- Present PowerShell and Linux/bash examples side-by-side or in parallel sections to ensure equal visibility.
- Explicitly mention that the PowerShell example is for Windows users and provide equivalent steps for Linux users.
- Review other sections for similar bias and ensure all operational steps have both Windows and Linux guidance where applicable.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-add-hive-libraries.md
...icles/hdinsight/hdinsight-hadoop-add-hive-libraries.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. The primary script referenced for adding Hive libraries is a PowerShell (.ps1) script, with the Bash script URI only appearing later in a table. The script location section exclusively highlights the PowerShell script, and the instructions for uploading files to Azure Storage recommend Azure Storage Explorer (a Windows-centric GUI tool) before mentioning any command-line or Linux-native alternatives. Additionally, the mention of Azure PowerShell and the .NET SDK as provisioning options precedes any Linux-native tooling.
Recommendations
- Present both PowerShell and Bash script locations equally and prominently, ideally side-by-side.
- Include Linux-native tools (such as azcopy, Azure CLI, or sftp) as alternatives for uploading files to Azure Storage, not just Azure Storage Explorer.
- When listing provisioning methods, mention Linux-friendly options (such as Azure CLI, ARM templates, or REST API) before or alongside Azure PowerShell and .NET SDK.
- Provide explicit Bash/Linux command-line examples for all steps, not just GUI or Windows-centric tools.
- Clarify which instructions or scripts are for Windows and which are for Linux, and ensure Linux instructions are not secondary.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-create-linux-clusters-adf.md
...dinsight/hdinsight-hadoop-create-linux-clusters-adf.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a bias toward Windows by exclusively providing Azure PowerShell scripts for resource creation and setup, with no equivalent Bash/CLI or Linux-native instructions. The use of PowerShell is assumed throughout, and there are no references to Azure CLI or Bash scripting, which are more common in Linux environments. This may hinder Linux users or those preferring cross-platform tools.
Recommendations
- Provide equivalent Azure CLI (az) commands and Bash script examples alongside PowerShell scripts for all resource creation and management steps.
- Explicitly mention that users can use either PowerShell or Azure CLI, and link to both installation guides.
- Where possible, use cross-platform tools and patterns (e.g., Azure CLI, REST API) in examples, or at least present them before or alongside Windows/PowerShell-specific instructions.
- Add a section or callout for Linux/macOS users, clarifying any differences or additional steps required.
- Review all step-by-step instructions to ensure parity between Windows and Linux environments, especially for scripting and automation tasks.