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 776-800 of 867 flagged pages
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-rotate-storage-keys.md
...in/articles/hdinsight/hdinsight-rotate-storage-keys.md
Medium Priority
View Details →
Detected Bias Types
Linux First
Missing Windows Example
Summary
The documentation exclusively provides Linux-based instructions and examples (e.g., Bash script, references to 'Script Action' for Linux, and links to Linux-specific pages) without mentioning or providing equivalent steps for Windows-based HDInsight clusters. There are no PowerShell, Windows command-line, or Windows script examples, nor any guidance for users managing Windows-based clusters.
Recommendations
- Add equivalent instructions and examples for updating storage account access keys on Windows-based HDInsight clusters, including PowerShell scripts or Windows batch files.
- Clearly indicate whether the provided Bash script and process are only applicable to Linux-based clusters, and provide a parallel section for Windows users if supported.
- Include references or links to documentation for managing storage keys on Windows HDInsight clusters, if available.
- Ensure that both Linux and Windows users can follow the documentation without ambiguity about platform support.
Create Pull Request
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-troubleshoot-guide.md
...ain/articles/hdinsight/hdinsight-troubleshoot-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page lists several development tools for Apache Spark on HDInsight, including IntelliJ, Eclipse, VS Code, and Visual Studio. While IntelliJ, Eclipse, and VS Code are cross-platform, Visual Studio is a Windows-only tool and is included alongside the others without clarification. Additionally, the order in which tools are presented (with Visual Studio last) may subtly prioritize Windows development environments. However, there are no explicit PowerShell-heavy examples, and Linux-specific troubleshooting resources are present, especially in the 'HDInsight troubleshooting resources' section.
Recommendations
- Clearly indicate platform compatibility for each tool (e.g., specify that Visual Studio is Windows-only, while IntelliJ, Eclipse, and VS Code are cross-platform).
- When listing tools, avoid grouping Windows-only tools with cross-platform tools without clarification.
- Consider providing equivalent Linux-native tools or workflows if available, or explicitly state when a tool is only available on Windows.
- Ensure that any code snippets or step-by-step guides referenced in the linked articles include both Windows and Linux command-line examples where applicable.
- Continue to highlight Linux-specific troubleshooting resources and ensure parity in depth and visibility with Windows resources.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-use-external-metadata-stores.md
...es/hdinsight/hdinsight-use-external-metadata-stores.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows/Azure-centric tools by exclusively referencing Azure SQL Database as the external metastore solution, with no mention of Linux-native or open-source alternatives (such as MySQL, PostgreSQL, or on-premises SQL Server). There are no command-line examples (neither Windows nor Linux), but all configuration guidance assumes use of Azure Portal or Ambari UI, both of which are platform-agnostic but tightly coupled to Azure's ecosystem. There are no Linux-specific instructions or examples, and the documentation does not address scenarios outside of Azure SQL Database.
Recommendations
- Include examples of configuring external metastores using open-source databases commonly used in Linux environments, such as MySQL or PostgreSQL, which are supported by Hive and Oozie.
- Provide command-line examples for metastore configuration using Linux shell tools (e.g., using the Azure CLI, curl, or Hive/Oozie configuration files), not just portal or UI steps.
- Mention and document support for on-premises or self-hosted SQL Server, MySQL, or PostgreSQL as external metastores, if supported by HDInsight.
- Clarify whether the guidance applies only to Azure SQL Database or if other database engines are supported, and provide parity in documentation for those options.
- Add troubleshooting and configuration steps relevant to Linux-based deployments, such as firewall configuration using iptables or ufw, and database connectivity testing from Linux hosts.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/interactive-query/hdinsight-grafana.md
...icles/hdinsight/interactive-query/hdinsight-grafana.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates mild Windows bias by referencing Visual Studio Hadoop tools (a Windows-centric tool) in the 'Next steps' section and by primarily describing access patterns (Azure portal, web browser) that are platform-neutral but often more familiar to Windows users. There are no explicit Linux command-line or SSH examples, and no mention of Linux-specific tools or workflows, despite HDInsight clusters being Linux-based.
Recommendations
- Include Linux command-line examples for accessing Grafana (e.g., using curl or SSH tunneling).
- Provide parity by referencing cross-platform tools (such as VS Code with Azure extensions) alongside Visual Studio.
- Clarify that the web browser and Azure portal steps are platform-agnostic, and suggest CLI alternatives (e.g., Azure CLI commands for resource management).
- Add a note or section on accessing Grafana from Linux environments, including any relevant authentication or network considerations.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/interactive-query/hdinsight-connect-hive-zeppelin.md
...t/interactive-query/hdinsight-connect-hive-zeppelin.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page subtly prioritizes Windows-centric tools and workflows. While the main quickstart is platform-agnostic (browser-based Zeppelin), the 'Next steps' section promotes Visual Studio and Data Lake Tools for Visual Studio, which are primarily Windows tools. Additionally, the cleanup section lists 'browser, PowerShell, or the Azure CLI' for deleting clusters, mentioning PowerShell (a Windows tool) before Azure CLI (cross-platform), and does not mention Bash or Linux-native alternatives.
Recommendations
- In the 'Clean up resources' section, mention Bash or Linux shell commands for deleting clusters, or clarify that Azure CLI can be used from any platform.
- In 'Next steps', provide links to cross-platform or Linux-friendly tools (such as VS Code, Jupyter Notebooks, or CLI-based Hive clients) alongside or before Visual Studio.
- Ensure that any references to PowerShell or Visual Studio are balanced with Linux/macOS equivalents or alternatives.
- Explicitly state when instructions are platform-agnostic, and provide OS-specific notes where relevant.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/kafka/apache-kafka-auto-create-topics.md
...les/hdinsight/kafka/apache-kafka-auto-create-topics.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation references PowerShell and Resource Manager templates for cluster creation, but does not provide Linux/CLI examples or mention cross-platform tools like Azure CLI. Windows-centric tooling is mentioned first, and there is no parity in instructions for Linux users.
Recommendations
- Add equivalent examples using Azure CLI for Linux/macOS users when discussing cluster creation.
- Avoid mentioning PowerShell or Windows-specific tools first; instead, present cross-platform or Linux-native options alongside or before Windows tools.
- Include explicit instructions or links for performing the same configuration steps from Linux environments.
- Clarify that Resource Manager templates can be deployed from any OS, not just Windows, and provide examples using cross-platform deployment methods.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/interactive-query/quickstart-bicep.md
...ticles/hdinsight/interactive-query/quickstart-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for deploying and managing resources, but PowerShell (a Windows-centric tool) is consistently presented alongside CLI, and sometimes before or with equal prominence. There are no explicit Linux shell (bash) examples or mentions of Linux-specific tools or workflows, and PowerShell is highlighted as a primary option, which may suggest a bias toward Windows users.
Recommendations
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and clarify that PowerShell is primarily for Windows users (unless using PowerShell Core).
- Add bash shell examples or clarify that the CLI examples are suitable for Linux/macOS terminals.
- Where PowerShell is presented, consider listing CLI (bash) examples first, as CLI is cross-platform.
- Include a note or section for Linux/macOS users, confirming that all steps can be performed on those platforms using Azure CLI.
- Avoid implying parity between PowerShell and CLI unless both are equally cross-platform.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/overview-azure-storage.md
...blob/main/articles/hdinsight/overview-azure-storage.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias by referencing the Windows-style environment variable (%HADOOP_HOME%) when describing the location of the core-site.xml file, and by using Windows path notation. There are no explicit Linux or cross-platform examples, and Linux path notation is not mentioned. However, the page does not provide command-line examples or scripts that are Windows- or PowerShell-specific, and most of the content is conceptual and platform-agnostic.
Recommendations
- When referencing file paths, provide both Windows and Linux path formats (e.g., %HADOOP_HOME%/conf/core-site.xml and $HADOOP_HOME/conf/core-site.xml).
- Explicitly mention that the location of configuration files applies to both Windows and Linux clusters, and clarify any differences.
- If providing environment variable examples, show both Windows (%VAR%) and Linux ($VAR) syntax.
- Add a note or section clarifying that HDInsight clusters are typically Linux-based, and that most commands and paths use Linux conventions.
- Review for any other implicit Windows assumptions and ensure parity in documentation for Linux users.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/kafka/apache-kafka-quickstart-bicep.md
...icles/hdinsight/kafka/apache-kafka-quickstart-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and managing resources, but PowerShell is consistently presented alongside (and sometimes before) CLI, which is more cross-platform. There are no explicit Linux-only command-line tool examples for resource management (e.g., Bash scripting), and the initial deployment steps may implicitly favor Windows users by highlighting PowerShell. However, the Kafka management and SSH sections use Linux-native commands and workflows, which helps balance the bias.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more familiar to Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily for Windows (unless using PowerShell Core).
- Consider providing Bash script examples for automation, especially in the deployment and cleanup sections.
- Clarify in the prerequisites or deployment sections that all SSH and Kafka management commands are intended for a Linux shell environment.
- If possible, provide a table or callout summarizing which tools/commands are best for each OS.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-intellij-tool-failure-debug.md
...ight/spark/apache-spark-intellij-tool-failure-debug.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias, particularly in the prerequisites section where download links and instructions reference Windows versions of IntelliJ IDEA and tools, with no mention of Linux or macOS equivalents. There are no Linux-specific instructions, screenshots, or troubleshooting steps, and the workflow assumes a Windows environment throughout. No Linux command-line or desktop environment examples are provided.
Recommendations
- Include download links and installation instructions for IntelliJ IDEA and other tools (e.g., Azure Storage Explorer) for Linux and macOS, not just Windows.
- Add notes or sections describing any differences in workflow or UI for Linux users.
- Provide at least one example or screenshot from a Linux environment to demonstrate parity.
- Explicitly state that the instructions are cross-platform if they are, or call out any Windows-specific steps.
- Mention any additional dependencies or setup steps required for Linux users (e.g., Java installation, file paths, permissions).
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-templeton-webhcat-debug-errors.md
...ght/hdinsight-hadoop-templeton-webhcat-debug-errors.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references client-side tools such as Azure PowerShell and Data Lake Tools for Visual Studio, both of which are Windows-centric. There are no examples or mentions of Linux-native tools or command-line usage (e.g., curl, wget, or Linux shell scripts) for interacting with WebHCat. The documentation does not provide parity for Linux users in terms of tooling or usage patterns.
Recommendations
- Include examples of using Linux-native tools (such as curl or wget) to interact with the WebHCat REST API.
- Mention cross-platform or Linux-friendly clients (e.g., Azure CLI, Python scripts) alongside Windows tools.
- Provide sample commands or scripts for common troubleshooting steps that can be run on Linux or macOS terminals.
- Ensure that references to client-side tools are balanced, listing cross-platform or Linux tools before or alongside Windows-specific ones.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-script-actions-linux.md
...les/hdinsight/hdinsight-hadoop-script-actions-linux.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is primarily focused on Linux (Ubuntu) scripting and usage, with all code examples and best practices centered on Bash and Linux tools. However, there is a subtle Windows bias in the way that Windows-based tools (Azure PowerShell, .NET SDK) are listed as primary methods for applying script actions, and in the troubleshooting section, where the root cause of common errors is attributed to authoring scripts on Windows. The documentation does not provide Linux CLI (az CLI) examples for managing script actions, and Windows-centric tools are often mentioned before Linux equivalents.
Recommendations
- Add examples and instructions for using the Azure CLI (az CLI), which is cross-platform and preferred by many Linux users, for applying script actions.
- When listing methods for applying script actions, mention cross-platform tools (like Azure CLI) before or alongside Windows-specific tools (PowerShell, .NET SDK).
- In troubleshooting sections, provide guidance for both Windows and Linux users, such as how to convert line endings on both platforms.
- Where possible, avoid assuming scripts are authored on Windows; instead, provide neutral language that addresses both Windows and Linux development environments.
- Include links to Linux-native tools and documentation for managing HDInsight clusters, not just PowerShell or .NET SDK references.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/overview-azure-storage.md
...blob/main/articles/hdinsight/overview-azure-storage.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias by referencing the Windows-style environment variable (%HADOOP_HOME%) in the file path for core-site.xml, and by using Windows path notation. There are no explicit Linux or cross-platform examples, and the only file path example uses Windows conventions. However, there are no command-line examples (PowerShell or otherwise), and most of the content is platform-neutral.
Recommendations
- When referencing file paths, provide both Windows and Linux/macOS formats (e.g., %HADOOP_HOME%/conf/core-site.xml and $HADOOP_HOME/conf/core-site.xml).
- Clarify that the location of configuration files applies to both Windows and Linux-based HDInsight clusters, or specify if it is Windows-only.
- If including environment variable references, use cross-platform notation or mention both (%VAR% for Windows, $VAR for Linux/macOS).
- Add Linux/macOS-specific notes or examples where relevant, especially if there are differences in file paths or commands.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-plan-virtual-network-deployment.md
...hdinsight/hdinsight-plan-virtual-network-deployment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for network resource queries, but PowerShell examples are consistently presented first. There are no Linux-specific shell examples (e.g., Bash with Azure CLI), and the use of PowerShell as the primary scripting language may implicitly favor Windows users. However, Azure CLI commands are included, which are cross-platform, mitigating some bias. No Windows-only tools or patterns are mentioned, but the ordering and scripting language preference suggest a mild Windows-first bias.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI (which is cross-platform) first to better support Linux users.
- Explicitly note that Azure CLI commands can be run in Bash on Linux/macOS, and provide example shell prompts (e.g., $ for Bash, PS> for PowerShell) to clarify context.
- Where possible, include Bash script snippets for common tasks, especially in sections where PowerShell scripting is shown.
- Add a brief section or note highlighting that all Azure CLI commands are fully supported on Linux, macOS, and Windows.
- Review linked documents to ensure Linux parity in examples and instructions.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-troubleshoot-guide.md
...ain/articles/hdinsight/hdinsight-troubleshoot-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page lists several development tools, including Visual Studio, IntelliJ, Eclipse, and VS Code, with a specific mention of 'HDInsight Visual Studio tool'—a Windows-only IDE—alongside cross-platform tools. The ordering of tools in the 'Tools' section places Visual Studio last, but its inclusion without a Linux equivalent (e.g., no mention of Linux-specific editors or command-line tools) introduces a subtle Windows bias. There are no explicit PowerShell or Windows command examples, but the presence of Visual Studio as a recommended tool and the lack of parity for Linux-native tooling or workflows suggest a mild Windows-first perspective.
Recommendations
- Add explicit mention of Linux-compatible development tools and workflows, such as command-line interfaces, Emacs, or Linux-specific editors.
- Clarify which tools are cross-platform and which are Windows-only (e.g., note that Visual Studio is Windows-only, while VS Code, IntelliJ, and Eclipse are cross-platform).
- Provide Linux-specific troubleshooting examples or links alongside any Windows-specific tools or instructions.
- Consider reordering the 'Tools' list to lead with cross-platform options or group by platform compatibility.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-40-component-versioning.md
...rticles/hdinsight/hdinsight-40-component-versioning.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page is largely neutral and platform-agnostic in its main content, focusing on open-source component versions. However, in the 'Next steps' section, a link specifically highlights working with HDInsight from a Windows PC and references Windows tools, without an equivalent mention or link for Linux or cross-platform tools. This suggests a subtle Windows-first and Windows-tools bias.
Recommendations
- Add a parallel link in the 'Next steps' section for working with HDInsight from Linux or macOS, or a general cross-platform guide.
- Ensure that references to client tools or setup guides include both Windows and Linux (and optionally macOS) instructions, or clearly indicate cross-platform compatibility.
- Review other related documentation to ensure Linux users are equally supported and not required to infer steps from Windows-specific guides.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-5x-component-versioning.md
...rticles/hdinsight/hdinsight-5x-component-versioning.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page lists a 'Work in Apache Hadoop on HDInsight from a Windows PC' link in the 'Next steps' section, highlighting Windows tooling. There is no equivalent Linux-specific guidance linked, and the Windows PC workflow is mentioned before any Linux alternatives, indicating a subtle Windows-first bias.
Recommendations
- Add a parallel link or section for 'Work in Apache Hadoop on HDInsight from a Linux PC' to provide Linux users with equivalent guidance.
- Ensure that Linux tools and workflows are mentioned alongside Windows options, not just in secondary documentation.
- Review cross-references and 'Next steps' to balance platform-specific guidance, so Linux users are not left out or made to feel like a secondary audience.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/enterprise-security-package.md
...main/articles/hdinsight/enterprise-security-package.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page exhibits mild Windows bias, particularly in the 'Next steps' section where the Windows PC tooling guide is listed before any Linux-specific guidance. Additionally, there is a direct link to 'Work in Apache Hadoop on HDInsight from a Windows PC', but no equivalent Linux-focused resource is mentioned. The main content does not provide OS-specific examples, but the navigation and resource emphasis favor Windows.
Recommendations
- Add a parallel link in the 'Next steps' section for working with Apache Hadoop on HDInsight from a Linux or macOS environment.
- Ensure that any tooling or workflow documentation for Windows is matched with Linux (and optionally macOS) equivalents.
- Review the order of links in 'Next steps' to avoid consistently listing Windows resources before Linux ones.
- Consider including a brief section or note clarifying cross-platform support and linking to platform-agnostic or platform-specific guides as appropriate.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/find-host-name.md
...re-docs/blob/main/articles/hdinsight/find-host-name.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash (with jq) and PowerShell examples for retrieving host names via the Ambari REST API. However, the PowerShell example is more detailed, including credential prompts, and is presented immediately after the Bash example. There is a slight bias in that the PowerShell example uses Windows-specific cmdlets and patterns, and the Bash example does not include instructions for Windows users who may use WSL or Git Bash. The documentation does not mention Linux tools or environments explicitly, nor does it provide troubleshooting or installation guidance for jq on Linux.
Recommendations
- Ensure that both Bash and PowerShell examples are equally detailed and cover authentication and output parsing.
- Explicitly mention that the Bash example works on Linux, macOS, and Windows (with WSL or Git Bash), and provide installation instructions for jq.
- Consider presenting the Bash (Linux/macOS) example first, or clarify that both are supported equally.
- Add troubleshooting tips for common issues on both Linux and Windows platforms.
- Where possible, provide parity in explanation and context for both operating systems, including any OS-specific caveats.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-apache-kafka-spark-structured-streaming.md
...t/hdinsight-apache-kafka-spark-structured-streaming.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides host information retrieval commands specifically for Windows command prompt, with explicit references to Windows paths and tools (e.g., C:\HDI\jq-win64.exe), and notes that 'slight variations will be needed for other environments' without providing Linux/macOS equivalents. No Linux or cross-platform example is given for this step, which may hinder users on non-Windows systems.
Recommendations
- Provide equivalent Linux/macOS command examples for retrieving Kafka ZooKeeper and broker hosts, using standard Unix shell syntax and typical jq installation paths (e.g., /usr/bin/jq).
- Clearly label both Windows and Linux/macOS command blocks, so users can easily find the instructions relevant to their environment.
- Avoid referencing only Windows-specific paths (such as C:\HDI\jq-win64.exe); instead, use environment variables or note typical installation locations for different platforms.
- Where possible, use cross-platform command syntax or provide guidance on adapting commands for different shells (cmd, PowerShell, Bash, etc.).
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-component-versioning.md
...n/articles/hdinsight/hdinsight-component-versioning.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page is largely neutral and focused on HDInsight versions and support policies, with most technical details referencing Ubuntu as the cluster OS. However, in the 'Next steps' section, the link 'Work in Apache Hadoop on HDInsight from a Windows PC' is called out specifically, while no equivalent Linux or cross-platform guidance is highlighted. Additionally, in the introduction, deployment methods are listed as 'Azure portal and other deployment methods like PowerShell, CLI and the .NET SDK', with PowerShell (a Windows-centric tool) mentioned before the cross-platform CLI, which may suggest a subtle Windows-first bias.
Recommendations
- Add a 'Work in Apache Hadoop on HDInsight from a Linux PC' or 'Work in Apache Hadoop on HDInsight from macOS/Linux' link in the 'Next steps' section to provide parity for non-Windows users.
- When listing deployment methods, mention cross-platform tools (such as Azure CLI) before or alongside PowerShell to avoid implying a Windows-first workflow.
- If there are any platform-specific tools or guides, ensure that both Windows and Linux (and optionally macOS) equivalents are referenced and linked with equal prominence.
- Consider a general 'Accessing HDInsight from your local machine' guide that covers Windows, Linux, and macOS, rather than platform-specific links.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-create-virtual-network.md
...articles/hdinsight/hdinsight-create-virtual-network.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for network security group configuration, but consistently lists PowerShell (a Windows-centric tool) before CLI. The most detailed, step-by-step example is given in PowerShell, with CLI following. There are no Linux shell (bash) script examples for Azure CLI, and no explicit mention of using CLI on Linux, though CLI is cross-platform. However, the DNS configuration section is Linux-focused, and the 'Test your settings' section recommends using a Linux VM, partially balancing the bias.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present CLI first to avoid implicit Windows-first bias.
- Explicitly state that Azure CLI commands can be run on Linux, macOS, and Windows, and provide bash shell script examples where appropriate.
- Add a short section or callout for Linux users, highlighting that all CLI steps are fully supported on Linux.
- Where possible, provide bash script blocks for Azure CLI steps to demonstrate parity and usability for Linux users.
- Consider including a table or quick reference comparing PowerShell and CLI commands, clarifying platform compatibility.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-custom-ambari-db.md
.../main/articles/hdinsight/hdinsight-custom-ambari-db.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias towards Windows/Azure-centric tooling and patterns. It exclusively references Azure SQL Database (a Microsoft-managed service) as the only supported external database for Ambari, with no mention of Linux-native or open-source alternatives (such as PostgreSQL or MySQL). All command-line examples use Azure CLI, which, while cross-platform, is tightly coupled with Azure's ecosystem. There are no examples or guidance for Linux-native database management, nor are there references to Linux tools or shell commands for database setup or connectivity.
Recommendations
- Include examples or guidance for using open-source, Linux-native databases (such as PostgreSQL or MySQL) as external Ambari databases, if supported.
- Provide Linux shell (bash) command examples for database setup, user creation, and permission granting, alongside or instead of SQL Server-specific commands.
- Clarify whether only Azure SQL Database is supported, or if other database engines can be used, and document their setup if possible.
- Add references to Linux-native tools (e.g., psql, mysql CLI) for database management tasks.
- Ensure parity in instructions and examples for both Windows and Linux users, especially for database provisioning and connectivity.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-for-vscode.md
...s/blob/main/articles/hdinsight/hdinsight-for-vscode.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias, primarily by using Windows-style paths (e.g., C:\HD\HDexample) in all file and folder examples, and not providing equivalent Linux/macOS examples. There are no explicit Linux command-line or file path examples, and the only Linux-specific mention is a note about installing xclip for copy-table data. The documentation assumes a Windows environment for directory navigation and file creation, which can be confusing for Linux/macOS users.
Recommendations
- Provide parallel Linux/macOS examples for file paths (e.g., use /home/user/HDexample alongside C:\HD\HDexample).
- When giving instructions for opening folders or creating files, include both Windows and Linux/macOS navigation steps.
- Explicitly mention that all steps apply to Linux/macOS unless otherwise noted, and highlight any differences.
- Include screenshots or terminal snippets from Linux/macOS environments where relevant.
- Add a section or callouts for common Linux/macOS issues or prerequisites (e.g., permissions, Mono installation, xclip usage).
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-sdk-dotnet-samples.md
...ain/articles/hdinsight/hdinsight-sdk-dotnet-samples.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page focuses exclusively on .NET samples for Azure HDInsight, which are typically associated with Windows development environments (e.g., Visual Studio). There are no examples or guidance for Linux users or alternative development environments. The only prerequisite and tooling mentioned is the Azure HDInsight SDK for .NET, and Visual Studio subscriber benefits are highlighted, reinforcing a Windows-centric approach.
Recommendations
- Include instructions for setting up and using the .NET SDK on Linux and macOS, such as using VS Code or JetBrains Rider.
- Provide examples of running the .NET samples using cross-platform .NET CLI commands, not just Visual Studio.
- Mention alternative editors and tools that are available on Linux (e.g., VS Code, command-line tools).
- Add a note clarifying that .NET Core/.NET 5+ is cross-platform and can be used on Linux and macOS.
- Where Visual Studio is mentioned, also mention equivalent Linux-friendly workflows.