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 476-500 of 867 flagged pages
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-sdk-dotnet-samples.md
...ain/articles/hdinsight/hdinsight-sdk-dotnet-samples.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on .NET (C#) samples, referencing Visual Studio subscriber benefits, and omitting any mention of Linux tools, environments, or equivalent workflows. There are no examples or instructions for running the SDK or samples on Linux, nor are cross-platform .NET Core/CLI instructions provided. The emphasis on Visual Studio and .NET implicitly prioritizes Windows users.
Recommendations
- Add explicit instructions and examples for running the .NET SDK and samples on Linux, including .NET Core/CLI usage.
- Mention and link to cross-platform development tools (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
- Clarify that the .NET SDK and samples can be used on Linux and macOS, not just Windows.
- Provide parity in prerequisites and setup steps for Linux users, such as package installation commands for .NET SDK on Ubuntu or other distributions.
- Include notes or links to Linux-specific troubleshooting or environment setup guides.
Create Pull Request
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 demonstrates a Windows bias by providing detailed PowerShell and Windows Command Prompt examples first, using Windows-specific environment variable syntax in Azure CLI sections, and referencing Visual Studio and Windows-centric workflows. There is a lack of parity for Linux/bash users, especially in the Azure CLI section, which only shows Windows-style commands and does not provide bash equivalents. PowerShell is the primary scripting language throughout, and Linux-native tools or patterns are not equally represented.
Recommendations
- Provide bash/Linux equivalents for all Azure CLI examples, using export for environment variables and bash syntax.
- Add explicit bash examples alongside PowerShell for all scripting steps, especially for cluster creation and SAS configuration.
- Clarify in each section whether the example is for Windows or Linux, and ensure both are covered.
- Include instructions for using cross-platform editors and tools, not just Visual Studio (e.g., VS Code, JetBrains Rider, etc.).
- Where PowerShell is used, offer bash or shell script alternatives for Linux users.
- Review all code snippets and ensure that Linux users can follow the guide without needing to translate Windows-specific 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
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell is listed as a primary tool for uploading data, but it is only available on Windows, with no Linux equivalent or alternative PowerShell Core mention. Several graphical clients are Windows-only, and the table lists more Windows-specific tools than Linux ones. Some tools (e.g., AzCopy) are available on both, but the documentation does not highlight Linux installation or usage. There are no explicit Linux command-line examples (e.g., using Azure CLI or AzCopy on Linux), and the 'Mount Azure Storage as Local Drive' section links to a resource that is typically Windows-centric, with no mention of Linux mounting options.
Recommendations
- Provide explicit Linux command-line examples for uploading data using Azure CLI and AzCopy, including installation and usage instructions.
- Mention and demonstrate PowerShell Core (cross-platform) if PowerShell examples are included, or provide Bash equivalents.
- Balance the graphical client table by highlighting Linux-compatible tools and noting when a tool is Windows-only.
- For mounting Azure Storage as a local drive, include Linux-specific methods (e.g., blobfuse, rclone) and provide links to relevant documentation.
- When listing tools/utilities, avoid listing Windows-only tools before cross-platform or Linux tools, or clearly indicate platform support.
- Ensure that all major workflows (upload, mount, SDK usage) have Linux parity in documentation and examples.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/includes/hdinsight-selector-use-mapreduce.md
...hdinsight/includes/hdinsight-selector-use-mapreduce.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation navigation lists 'PowerShell' and '.NET SDK' prominently, both of which are traditionally associated with Windows environments. 'PowerShell' is given as a top-level option alongside more cross-platform tools like SSH and Curl, and appears before any mention of Linux-specific tools or workflows. There is no explicit mention of Linux command-line tools or examples, suggesting a bias towards Windows-centric tools and workflows.
Recommendations
- Add explicit Linux/Bash examples or sections, such as 'Bash' or 'Linux CLI', to the navigation.
- Ensure that Linux-native tools (e.g., Bash scripts, Linux command-line utilities) are given equal prominence to PowerShell and .NET SDK.
- If possible, reorder the navigation to alternate or balance Windows and Linux tools, or group them by platform.
- Include a note clarifying cross-platform compatibility for each tool or script, and provide equivalent instructions for both Windows and Linux users.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/interactive-query/apache-hadoop-connect-hive-power-bi-directquery.md
...ery/apache-hadoop-connect-hive-power-bi-directquery.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page assumes the use of Microsoft Power BI Desktop, which is only available on Windows, and provides no mention of Linux alternatives or guidance for non-Windows users. All instructions and screenshots are based on the Windows version of Power BI Desktop, and there is no discussion of how to perform similar tasks on Linux or macOS platforms. This creates a Windows-centric experience and excludes users on other operating systems.
Recommendations
- Explicitly state that Power BI Desktop is only available on Windows and provide guidance for Linux/macOS users, such as using Power BI Service (web) where possible.
- Include alternative workflows for Linux users, such as using open-source BI tools (e.g., Apache Superset, Grafana) to connect to HDInsight Hive data.
- Add a section or note about connecting to HDInsight from non-Windows platforms, including any available ODBC/JDBC drivers and compatible BI tools.
- Provide links to cross-platform tools or documentation for visualizing Hive data from HDInsight on Linux/macOS.
- Where possible, use neutral language and avoid assuming the reader is on Windows; present Windows and Linux options in parallel.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/interactive-query/apache-interactive-query-get-started.md
...eractive-query/apache-interactive-query-get-started.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by prioritizing and exclusively mentioning Windows-centric tools (Power BI, Visual Studio, Excel with Hive ODBC) for interacting with Interactive Query in Azure HDInsight. Linux-native tools or workflows are not highlighted or are mentioned after Windows tools, and there are no explicit Linux command-line examples or references to Linux-based workflows.
Recommendations
- Include explicit examples and instructions for using Linux-native tools (e.g., Beeline CLI, Apache Zeppelin, or Hive CLI) to connect and query Interactive Query clusters.
- Present cross-platform options in a balanced way, listing Linux and open-source tools (such as Beeline, Zeppelin, or Jupyter Notebooks) before or alongside Windows tools.
- Add sample commands for connecting to Interactive Query from a Linux terminal using Beeline or JDBC.
- Mention how to use open-source BI tools (e.g., Apache Superset, DBeaver) that are available on Linux, in addition to Power BI and Excel.
- Clarify which tools are cross-platform and provide guidance for both Windows and Linux users.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/kafka/apache-kafka-introduction.md
.../articles/hdinsight/kafka/apache-kafka-introduction.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell and the Azure portal as primary management interfaces for scaling Kafka clusters, without mentioning Linux-native tools or CLI examples. There are no Linux shell or cross-platform CLI examples provided, and Windows-centric management patterns are mentioned before any Linux alternatives (if at all).
Recommendations
- Include Azure CLI examples alongside or before Azure PowerShell examples, as Azure CLI is cross-platform and commonly used on Linux.
- Explicitly mention Linux and macOS compatibility for management tasks, and provide bash shell command examples where relevant.
- Avoid listing Windows tools (such as PowerShell) before cross-platform alternatives, or present them in parallel.
- Reference Linux-native monitoring and management tools (such as systemd, journalctl, or native Kafka scripts) where appropriate.
- Add a section or callout for Linux users, highlighting any differences or additional steps required.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/kafka/apache-kafka-connect-vpn-gateway.md
...es/hdinsight/kafka/apache-kafka-connect-vpn-gateway.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a strong Windows/Powershell bias. All infrastructure provisioning and configuration steps are provided exclusively using Azure PowerShell scripts, with no equivalent Bash, Azure CLI, or Linux-native instructions for resource creation. The instructions for connecting to the VPN gateway reference Windows-centric tools and workflows. While macOS is briefly mentioned as supported for VPN clients, there are no explicit Linux client instructions or examples. The only non-Windows command-line example is a single Azure CLI snippet for listing NICs, but all other automation is Powershell-based. There are no Linux shell or Bash examples for resource creation, and the document does not mention or link to Linux-native tools for VPN or resource management.
Recommendations
- Provide equivalent Azure CLI and Bash examples for all resource creation and configuration steps, especially for creating resource groups, virtual networks, subnets, storage accounts, and HDInsight clusters.
- Include explicit instructions for Linux users to connect to the VPN gateway, such as using OpenVPN or native Linux VPN clients, and provide links to relevant Azure documentation.
- Ensure that all PowerShell scripts are accompanied by Azure CLI or REST API equivalents, and present them side-by-side or in separate tabs/sections.
- Mention and link to Linux-native tools and workflows where appropriate, and avoid assuming the user is on Windows.
- When referencing VPN client downloads or configuration, include Linux as a supported platform and provide setup instructions.
- Review the order of presentation to avoid always listing Windows/PowerShell first; consider a more platform-neutral or parallel structure.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/kafka/connect-kafka-cluster-with-vm-in-different-vnet.md
...fka/connect-kafka-cluster-with-vm-in-different-vnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Linux Example
Parity Note
Summary
The documentation provides both Linux and Windows VM instructions for connecting to an HDInsight Kafka cluster across VNets. Linux is presented first, with explicit command-line examples (curl, /etc/hosts), while Windows instructions are limited to a screenshot and a note about editing the hosts file. There is no PowerShell or Windows command-line example for testing connectivity (e.g., using 'curl' or 'Invoke-WebRequest'), and the Windows section is less detailed. The documentation does mention both platforms, but Linux receives more explicit, actionable guidance.
Recommendations
- Provide a Windows command-line example (e.g., using PowerShell's 'Invoke-WebRequest' or 'curl' if available) to test connectivity to the Ambari dashboard, similar to the Linux 'curl' example.
- Include step-by-step instructions for editing the Windows hosts file (e.g., using Notepad as Administrator), not just a screenshot.
- Ensure parity in troubleshooting steps and verification commands for both Linux and Windows VMs.
- Consider presenting both Linux and Windows instructions in parallel sections or tables for clarity and equal prominence.
- Explicitly mention any differences in required tools or commands between platforms, and provide links to relevant documentation for both.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/kafka/connect-kafka-with-vnet.md
...in/articles/hdinsight/kafka/connect-kafka-with-vnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation generally maintains parity between Linux and Windows, but there are subtle signs of Windows bias. Windows-specific instructions (such as editing the hosts file path) are called out in a dedicated section, and the Windows workflow is described in more detail. The Linux example for /etc/hosts is less explicit, and the Linux curl example is buried within a larger HTML output, making it less accessible. There is also a tendency to mention Windows paths and tools (like C:\Windows\System32\drivers\etc\) before or more prominently than their Linux equivalents. The documentation does not provide PowerShell or CMD commands, but the structure and notes suggest a Windows-first mindset.
Recommendations
- Ensure that Linux and Windows instructions are presented with equal prominence and detail.
- Provide explicit Linux examples for editing /etc/hosts, not just a mention.
- Include step-by-step Linux workflow instructions similar to the Windows section (e.g., how to open and edit /etc/hosts with sudo).
- When referencing file paths or tools, always mention both Linux and Windows equivalents together, or alternate their order in different sections.
- Where possible, provide command-line examples for both platforms (e.g., using nano/vim for Linux, Notepad for Windows).
- Avoid assuming the reader is more familiar with Windows by default.
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 First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively uses PowerShell for all scripting and automation examples, with no mention of Bash, Python, or other cross-platform scripting options. All runbook creation steps assume PowerShell as the language, and only PowerShell modules and cmdlets are referenced. There are no examples or guidance for users who prefer or require Linux-native tools or languages. The documentation also references Azure PowerShell as the next step, reinforcing a Windows-centric approach.
Recommendations
- Provide equivalent examples using Azure CLI and/or Python runbooks, which are cross-platform and commonly used on Linux.
- Explicitly mention that Azure Automation supports Python and Bash runbooks, and link to relevant documentation.
- Include a section or callout for Linux users, outlining how to achieve the same tasks using Linux-native tools and scripting languages.
- Balance the order of presentation so that PowerShell and cross-platform alternatives are given equal prominence.
- Reference Azure CLI modules and commands for HDInsight cluster management alongside PowerShell examples.
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 scripting style and variable assignment syntax in the Azure CLI section is heavily influenced by PowerShell conventions (e.g., use of $variable, [String[]] arrays), which are not idiomatic for Bash or Linux shells. The PowerShell example is given in full, but there is no dedicated Bash/Linux shell script or example. The documentation assumes familiarity with PowerShell scripting, which is Windows-centric, and does not provide Linux-native command or scripting patterns.
Recommendations
- Provide a dedicated Bash/Linux shell example using Azure CLI, with variable assignment and array handling in Bash style (e.g., VAR=value, arrays with parentheses).
- Avoid using PowerShell variable syntax ($var) and array notation ([String[]]) in Azure CLI examples; use syntax that is idiomatic for the target shell.
- Explicitly mention that Azure CLI commands can be run from any OS, and provide examples in both Windows (PowerShell) and Linux (Bash) scripting styles.
- Add a section or callout for Linux users, clarifying how to adapt the steps for Bash or other common Linux shells.
- Ensure parity in the depth and completeness of examples for both Windows and Linux environments.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-create-standalone-application.md
...ht/spark/apache-spark-create-standalone-application.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-style file paths (e.g., '\out\artifacts'), mentioning AzCopy (primarily a Windows tool) for uploading files, and omitting any Linux/macOS-specific instructions or examples. There are no terminal/command-line examples for Linux or macOS, and all screenshots and instructions implicitly assume a Windows environment.
Recommendations
- Include Linux/macOS equivalents for file paths (e.g., '/out/artifacts') wherever Windows paths are mentioned.
- Provide alternative instructions for uploading files using cross-platform tools such as Azure CLI, Hadoop CLI, or native OS commands (e.g., curl, scp, or Azure Storage Explorer), not just AzCopy.
- Add notes or screenshots showing IntelliJ IDEA on Linux/macOS, or clarify that the steps are the same across platforms.
- Explicitly mention that IntelliJ IDEA, Maven, and Java are cross-platform, and provide installation links or brief instructions for Linux/macOS users.
- If referencing command-line actions, provide both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) command examples.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-custom-library-website-log-analysis.md
...rk/apache-spark-custom-library-website-log-analysis.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates log analysis using a custom Python library for IIS (Internet Information Services) logs, which are specific to Windows web servers. The sample data, parser, and log schema are all based on IIS, with no mention of Linux-based web server logs (such as Apache or Nginx) or their parsing. The only log format and parser discussed are Windows-centric, and there are no examples or guidance for Linux log formats. Additionally, the documentation references BI tools like Power BI (a Microsoft product) before others, reinforcing a Windows-first perspective.
Recommendations
- Include examples and sample data for common Linux web server logs (e.g., Apache access.log, Nginx access.log).
- Provide or reference a Python log parser for Apache/Nginx logs and demonstrate its use in Spark, similar to the IIS example.
- Explicitly mention that the approach can be adapted for non-IIS logs and provide guidance or links for Linux users.
- Balance the mention of BI tools by listing cross-platform or Linux-friendly options (e.g., Grafana, Kibana) alongside Power BI and Tableau.
- Clarify in the prerequisites or introduction that the example is IIS-specific, and suggest alternatives for Linux-based environments.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-intellij-tool-plugin.md
...s/hdinsight/spark/apache-spark-intellij-tool-plugin.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation exhibits a Windows bias, particularly in the 'Spark Local Console(Scala)' section, where the use of WINUTILS.EXE and the HADOOP_HOME environment variable is required and discussed without any mention of Linux or macOS alternatives. There are no instructions or troubleshooting steps for running Spark locally on non-Windows platforms, and the prerequisite for WINUTILS.EXE is presented as a universal requirement, which is only true for Windows. No Linux or macOS-specific guidance or examples are provided throughout the document, and Windows-specific tools and patterns are referenced without parity.
Recommendations
- Add explicit instructions for running Spark locally on Linux and macOS, clarifying that WINUTILS.EXE is only required for Windows and not for other platforms.
- Include troubleshooting steps and environment variable setup examples for Linux and macOS (e.g., setting HADOOP_HOME, permissions).
- Where platform-specific requirements exist (such as WINUTILS.EXE), clearly indicate which OS they apply to and provide equivalent guidance or note the absence of such requirements on other platforms.
- Review all steps and screenshots to ensure they are not Windows-centric, or supplement with Linux/macOS equivalents where appropriate.
- Consider adding a 'Platform differences' section summarizing any OS-specific steps or caveats.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-eclipse-tool-plugin.md
...es/hdinsight/spark/apache-spark-eclipse-tool-plugin.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the 'Run a Spark Scala application locally' section, where only Windows-specific troubleshooting (WinUtils.exe) is discussed, and no equivalent Linux/Mac guidance is provided. The instructions for resolving local Spark issues are Windows-centric, and there is no mention of Linux or Mac requirements or differences. Additionally, the documentation refers to 'Windows computer' first and exclusively when discussing local runs, omitting cross-platform considerations.
Recommendations
- Add explicit instructions or notes for running Spark Scala applications locally on Linux and Mac, including any prerequisites or common issues (e.g., permissions, environment variables, or file system differences).
- When mentioning Windows-specific tools like WinUtils.exe, also clarify that these are not required on Linux/Mac and briefly describe any platform-specific setup steps.
- Wherever possible, use platform-neutral language (e.g., 'your computer' instead of 'Windows computer') and provide parity in troubleshooting steps for all major operating systems.
- Consider including a table or section that summarizes platform-specific requirements for local Spark development (Windows, Linux, Mac).
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-jupyter-notebook-install-locally.md
...spark/apache-spark-jupyter-notebook-install-locally.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing command-line examples and file path conventions that are specific to Windows (e.g., use of `cmd` blocks, backslashes in paths, and Windows-style environment variable instructions). There are no explicit Linux/macOS command examples or notes on differences for non-Windows users, and all instructions implicitly assume a Windows environment.
Recommendations
- For every command-line example, provide both Windows (cmd/PowerShell) and Linux/macOS (bash) equivalents, using appropriate code blocks and syntax.
- When referencing file paths (e.g., home directory, .sparkmagic folder), include both Windows (e.g., C:\Users\username) and Linux/macOS (~/.sparkmagic) formats.
- Clarify platform-specific steps, such as how to add Anaconda to PATH on different operating systems.
- Use neutral language and examples that do not assume the user is on Windows; explicitly mention when steps differ for Linux/macOS.
- Add troubleshooting notes for common issues on Linux/macOS, such as permissions or different default Python/Jupyter locations.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-intellij-tool-debug-remotely-through-ssh.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-intellij-tool-debug-remotely-through-ssh.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by addressing Windows-specific issues (such as the need for WinUtils.exe and setting HADOOP_HOME) prominently in the prerequisites and local run sections, without providing equivalent troubleshooting or setup guidance for Linux or macOS users. Windows tools and environment variables are discussed in detail, while Linux and macOS are only briefly mentioned as not needing these steps, with no further elaboration or examples for those platforms.
Recommendations
- Provide explicit instructions or troubleshooting steps for Linux and macOS users, even if the steps are simpler (e.g., confirm that no additional setup is needed, or mention common issues and their solutions).
- Include Linux/macOS-specific examples or notes in parallel with Windows instructions, rather than only stating that certain steps are not needed.
- Reorganize the prerequisites and local run sections to present platform-specific requirements in a balanced way, possibly using tabbed or side-by-side formatting for Windows, Linux, and macOS.
- Mention Linux and macOS tools or environment variables where relevant, and provide links to official documentation for those platforms.
- Ensure that download links (such as for IntelliJ IDEA) are not Windows-specific, or provide links for all supported platforms.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-intellij-tool-plugin-debug-jobs-remotely.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-intellij-tool-plugin-debug-jobs-remotely.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by providing detailed instructions and file paths for Windows (e.g., editing the hosts file at C:\Windows\System32\Drivers\etc\hosts), referencing Windows-specific tools (WinUtils.exe, Notepad), and mentioning PowerShell-based Azure VNet setup before any Linux alternatives. There is no equivalent guidance or examples for Linux or macOS users for key steps such as editing the hosts file, handling WinUtils.exe issues, or using native Linux tools for file transfer and configuration.
Recommendations
- Provide parallel instructions and file paths for Linux and macOS users, especially for editing the hosts file (e.g., /etc/hosts) and setting environment variables.
- Include Linux/macOS alternatives for tools and workarounds, such as explaining that WinUtils.exe is not needed on non-Windows systems.
- When listing Azure VNet creation steps, mention CLI/Bash or Linux-native methods before or alongside PowerShell and portal options.
- Avoid assuming the use of Notepad or Windows-specific editors; suggest cross-platform editors (e.g., nano, vim, VS Code) where appropriate.
- Clarify when steps are Windows-only and provide explicit Linux/macOS instructions for all major actions.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-livy-rest-interface.md
...es/hdinsight/spark/apache-spark-livy-rest-interface.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing environment variable examples and file path conventions specific to Windows (e.g., set commands, C:\Temp\input.txt), and by recommending the use of AzCopy (a Microsoft tool) for file uploads without mentioning Linux alternatives. There are no explicit Linux/macOS shell examples (e.g., export, $HOME/input.txt), and the guidance for adapting commands to non-Windows environments is minimal and non-specific.
Recommendations
- Provide parallel Linux/macOS shell examples for setting environment variables (e.g., export clustername=CLUSTERNAME) and for file paths (e.g., ~/input.txt).
- Explicitly mention and demonstrate how to use Linux-native tools for uploading files, such as Azure CLI (az storage blob upload) or standard SCP/rsync.
- When referencing input files, show both Windows (C:\Temp\input.txt) and Linux/macOS (~/<path>/input.txt) formats.
- Instruct users on how to adapt the curl commands for bash/zsh shells, including variable substitution (e.g., $clustername, $password).
- Where Windows-specific recommendations are made (e.g., 'using an input file is the recommended approach'), clarify if this is also true for Linux/macOS or provide alternative best practices.
- Add a note or section explicitly addressing cross-platform usage, highlighting any differences or considerations for Linux/macOS users.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-connect-to-sql-database.md
...dinsight/spark/apache-spark-connect-to-sql-database.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias toward Windows by exclusively referencing SQL Server Management Studio (SSMS) for database verification and management tasks, which is a Windows-only tool. There are no examples or mentions of Linux-compatible alternatives (such as Azure Data Studio, sqlcmd, or cross-platform tools), nor are there instructions for performing these tasks from Linux or macOS environments. The documentation assumes the user will use SSMS and does not provide parity for Linux users.
Recommendations
- Include instructions for connecting to Azure SQL Database using cross-platform tools such as Azure Data Studio, sqlcmd, or DBeaver.
- Provide command-line examples (e.g., using sqlcmd) for verifying table creation and querying data, which work on both Windows and Linux.
- Mention and demonstrate how to install and use these tools on Linux and macOS.
- Rephrase steps to avoid assuming the user is on Windows or has access to SSMS; offer alternatives equally or list cross-platform options first.
- Add screenshots or terminal output examples from Linux-based tools where appropriate.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/spark/apache-spark-overview.md
...main/articles/hdinsight/spark/apache-spark-overview.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 consistently mentioning Windows-centric tools and workflows (such as Azure PowerShell and .NET SDK) before or instead of Linux alternatives. There are no explicit Linux command-line examples or references to Bash/CLI workflows, and the only BI tool highlighted in detail is Microsoft Power BI. The documentation does not provide parity for Linux users in terms of setup, management, or integration examples.
Recommendations
- Include Linux/Bash command-line examples alongside or before PowerShell/.NET SDK instructions for cluster creation and management.
- Mention and provide examples for using the Azure CLI (az hdinsight ...) for cluster operations, which is cross-platform.
- Highlight BI tools that are popular on Linux (such as Tableau, Apache Superset, or open-source alternatives) with equal prominence as Power BI.
- Add explicit references to Linux-compatible workflows and tools in all relevant sections.
- Ensure that all code snippets and tutorials are available in both Windows (PowerShell/.NET) and Linux (Bash/CLI/Python) formats.
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 Linux-native alternatives or command-line methods. There are no explicit Linux or cross-platform examples for running Pig jobs, and the only integration example provided is Windows-specific. Additionally, the documentation references Windows tools before any cross-platform or Linux-native options.
Recommendations
- Add examples for running Pig jobs using SSH and the Linux command line (e.g., using PuTTY or native SSH clients) to ensure Linux parity.
- Include instructions for submitting Pig jobs via the Azure portal, Azure CLI, or REST API, which are cross-platform.
- Mention and provide walkthroughs for using Linux-native tools and scripting environments (e.g., Bash) alongside Windows tools.
- Balance the documentation by listing cross-platform or Linux methods before or alongside Windows-specific integrations like SSIS.
- Explicitly state that HDInsight clusters are typically Linux-based and provide guidance for both Windows and Linux users.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-manage-ambari-rest-api.md
...s/hdinsight/hdinsight-hadoop-manage-ambari-rest-api.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows and PowerShell are mentioned before Linux/Bash in several places, and Windows-specific tools and paths are referenced. Although Bash examples are provided throughout, the prerequisites and instructions often prioritize Windows environments (e.g., 'Bash on Ubuntu on Windows 10', PowerShell, Windows paths for jq). There are also notes about how to adapt Bash examples for Windows Command Prompt or PowerShell, but not vice versa. The use of Windows PowerShell and references to Windows Subsystem for Linux (WSL) further reinforce the Windows-centric approach.
Recommendations
- List Linux/Bash as the primary or first example in prerequisites and code blocks, especially since HDInsight clusters are Linux-based.
- Provide clear, standalone instructions for native Linux and macOS users, not just WSL or Bash on Windows.
- Avoid referencing Windows-specific paths (e.g., C:\HD\jq\jq-win64) in Bash/jq examples; instead, use generic or Linux-style paths.
- When mentioning PowerShell or Windows tools, ensure equivalent Linux-native alternatives are described with equal prominence.
- Clarify that all Bash examples work natively on Linux/macOS, not just in WSL.
- If referencing Azure PowerShell cmdlets, also mention equivalent Azure CLI commands for Linux users where possible.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-provision-linux-clusters.md
...hdinsight/hdinsight-hadoop-provision-linux-clusters.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits some Windows bias, primarily through the explicit mention of Azure PowerShell and Windows PowerShell cmdlets as setup and customization methods, and by referencing 'HDInsight Windows PowerShell cmdlets' before or instead of Linux equivalents. There is also a reference to working from a Windows PC in the related content, but no equivalent for Linux or macOS. While the main focus is on the Azure portal (which is cross-platform), command-line examples and tooling references tend to favor Windows or do not provide parity for Linux users.
Recommendations
- Ensure that all command-line examples and tooling references include both Windows (PowerShell) and Linux (Bash/Azure CLI) equivalents, presented side by side or with equal prominence.
- In sections mentioning 'HDInsight Windows PowerShell cmdlets', also mention and link to Azure CLI or Bash scripting options for Linux users.
- Add a 'Work in Apache Hadoop on HDInsight from a Linux PC' or 'macOS' equivalent to the related content, similar to the Windows PC link.
- Review all references to tools and setup methods to ensure Linux-first or at least equal treatment, especially in tables and lists.
- Where script actions or automation are discussed, provide examples for both PowerShell and Bash.
- Audit for any screenshots or instructions that are Windows-specific and provide Linux alternatives where applicable.