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 726-750 of 867 flagged pages
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/domain-joined/troubleshoot-domainnotfound.md
...hdinsight/domain-joined/troubleshoot-domainnotfound.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents Windows VM troubleshooting steps before Ubuntu/Linux equivalents and references Windows-specific tools (Control Panel UI) for domain joining, potentially leading to a perception that Windows is the primary or preferred platform for debugging. Linux instructions are present but less detailed and appear after the Windows example.
Recommendations
- Present Linux and Windows troubleshooting steps in parallel or start with Linux, given HDInsight clusters often run on Linux.
- Provide equally detailed instructions for Linux domain join (e.g., explicit Samba commands, configuration file examples) as for Windows.
- Avoid referencing Windows-specific tools (like Control Panel UI) without Linux equivalents.
- Clarify that both Windows and Linux VMs can be used for troubleshooting, and highlight any platform-specific caveats.
- Consider adding PowerShell and Bash script examples side-by-side for parity.
Create Pull Request
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-provision-vnet.md
...rticles/hdinsight/hbase/apache-hbase-provision-vnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation displays Windows bias in the 'Create a virtual machine' section, where instructions and links are provided specifically for creating a Windows Server VM, with no mention of Linux VM creation. This prioritizes Windows and omits Linux alternatives, despite the cluster itself being Linux-based. No PowerShell or Windows-specific tools are used elsewhere, but the lack of Linux VM guidance is notable.
Recommendations
- Add instructions and links for creating a Linux-based virtual machine in Azure, alongside or before the Windows VM example.
- Ensure examples and guidance for connecting, verifying, and managing the cluster are platform-neutral or include both Windows and Linux options where relevant.
- Review other sections for subtle Windows-first language or assumptions and revise to emphasize cross-platform parity.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-replication.md
...n/articles/hdinsight/hbase/apache-hbase-replication.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is largely Linux/Unix-focused, with all command-line examples using Bash and Linux tools, and the main workflow assumes Ubuntu VMs. However, there is a notable section that addresses Windows users, listing several ways to obtain the ssh utility on Windows before mentioning Linux/macOS (Azure Cloud Shell, Bash on Ubuntu on Windows, Git, OpenSSH for Windows). This places Windows-specific guidance before Linux equivalents in that context. No PowerShell examples or Windows command-line tools are provided, but the explicit mention of Windows tools and patterns (e.g., Bash on Ubuntu on Windows, OpenSSH for Windows) introduces a mild Windows-first/tool bias.
Recommendations
- When listing SSH options, mention native Linux/macOS SSH availability first, then provide Windows alternatives to avoid Windows-first ordering.
- If referencing Windows tools, ensure parity by also mentioning common Linux/macOS alternatives where relevant, and vice versa.
- Consider adding a short note for Windows users at the end of relevant sections, rather than interleaving Windows-specific instructions before Linux ones.
- Maintain a consistent order (Linux/macOS first, then Windows) throughout the documentation to match the primary platform focus.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/troubleshoot-rest-api.md
...main/articles/hdinsight/hbase/troubleshoot-rest-api.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references the IIS Gateway module, which is a Windows-specific technology, as the source of a security issue affecting REST API calls. No Linux equivalents or alternative gateway modules are mentioned, and there are no troubleshooting steps or examples for Linux-based deployments. The mitigation section does not clarify platform-specific steps, nor does it address Linux scenarios.
Recommendations
- Explicitly mention whether the IIS Gateway module issue affects only Windows-based HDInsight gateways or all deployments, including Linux.
- If Linux-based HDInsight clusters use a different gateway technology, provide details and troubleshooting steps relevant to Linux.
- Include examples or notes for Linux users, such as how to bypass the gateway or interact with HBase REST servers in Linux environments.
- Clarify whether the mitigation steps (deploying on a VM in the same VNet) differ for Windows and Linux users, and provide platform-specific guidance if necessary.
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 exhibits Windows bias by consistently using Windows-style paths (e.g., C:\HD\HDexample) in all examples and instructions, without providing equivalent Linux/macOS examples (e.g., /home/user/HDexample). The folder opening and file creation steps only reference Windows conventions, and there is no mention of Linux/macOS alternatives except for a brief note about Mono and xclip installation. This may confuse or alienate users on non-Windows platforms.
Recommendations
- Provide parallel examples for Linux/macOS, such as using /home/user/HDexample or ~/HDexample in folder paths.
- Explicitly mention how to perform key actions (e.g., opening folders, creating files) on Linux/macOS, including differences in keyboard shortcuts or UI.
- Where Windows-specific tools or conventions are referenced (such as C:\ paths), add a note or a table showing the equivalent for Linux/macOS.
- Ensure all screenshots and code snippets are platform-neutral or offer alternatives for Linux/macOS users.
- Expand the prerequisites section to clarify any platform-specific setup steps, such as directory conventions or required dependencies.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-customize-cluster-linux.md
.../hdinsight/hdinsight-hadoop-customize-cluster-linux.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page provides examples and guidance for using script actions in Azure HDInsight clusters. While the clusters themselves are Linux-based and script actions are Bash scripts, the documentation consistently lists Windows-centric tools (Azure PowerShell, .NET SDK) before Linux-friendly options (Azure CLI, REST API). Example code and command references are predominantly PowerShell-based, with more detailed PowerShell walkthroughs and output samples. The Azure CLI is mentioned, but with less prominence and fewer detailed examples. There are no Linux shell (bash) or direct SSH examples, and the .NET SDK (Windows-centric) is referenced before REST API or CLI in several sections.
Recommendations
- Present Azure CLI examples before or alongside Azure PowerShell examples, especially since HDInsight clusters are Linux-based.
- Provide more detailed Azure CLI walkthroughs, including output samples and step-by-step instructions, matching the depth of PowerShell examples.
- Include examples of using Bash scripts via SSH for advanced users who may want to interact directly with cluster nodes.
- Reference REST API and CLI options earlier in each section, not just as add-ons after PowerShell and .NET SDK.
- Clarify that PowerShell is cross-platform, but highlight CLI and Bash as native Linux options.
- Balance the documentation so that Linux-native workflows are as discoverable and detailed as Windows/PowerShell workflows.
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 examples for deploying and managing resources, but PowerShell is given equal prominence to CLI, and no explicit Linux shell examples (e.g., Bash) are provided. The use of PowerShell, which is traditionally Windows-centric, may imply a Windows bias, especially for users unfamiliar with PowerShell or working on Linux/macOS. There are no references to Linux-specific tools or shell patterns, and the documentation does not clarify cross-platform compatibility for the CLI or PowerShell commands.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and recommend CLI for cross-platform scenarios.
- Add Bash shell examples or clarify that CLI commands can be run in Bash or other Linux shells.
- De-emphasize PowerShell as the default or primary option, or provide guidance for Linux/macOS users who may not have PowerShell installed.
- Include a note about installing Azure CLI on Linux/macOS and link to relevant documentation.
- If PowerShell is mentioned, clarify that PowerShell Core is available cross-platform, but most Linux users will prefer CLI.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting environment variable setup and input file usage specifically for Windows (e.g., using 'set' and 'C:\Temp\input.txt') without providing equivalent Linux/macOS examples (e.g., 'export' and '/tmp/input.txt'). The main example workflow is explicitly described as 'based on a Windows environment,' and Linux alternatives are only mentioned in passing ('revise variables as needed for your environment') without concrete guidance or code snippets. All file paths and environment variable commands are Windows-centric.
Recommendations
- Provide parallel Linux/macOS examples for environment variable setup (e.g., 'export clustername=CLUSTERNAME').
- Include Linux-style file paths in input file examples (e.g., '@/tmp/input.txt').
- Explicitly show how to adapt commands for bash/zsh shells, not just Windows cmd.
- Add a note or section summarizing cross-platform differences and best practices.
- Ensure that all code snippets and instructions are presented for both Windows and Linux/macOS users, ideally side-by-side.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-replication.md
...n/articles/hdinsight/hbase/apache-hbase-replication.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is generally Linux-focused, with Ubuntu VMs and Bash/SSH commands used throughout. However, there is a notable Windows bias in the section describing how to obtain the SSH utility: Windows options are listed separately and before Linux/macOS, and several Windows-specific tools (Azure Cloud Shell, Bash on Ubuntu on Windows, Git for Windows, OpenSSH for Windows) are mentioned. This may suggest to readers that Windows is a primary platform, despite the actual setup being Linux-based.
Recommendations
- Present Linux/macOS instructions and tools before Windows-specific options when describing cross-platform utilities like SSH.
- Clarify that the main environment for HDInsight HBase replication is Linux, and that Windows instructions are supplementary for users who happen to be on Windows.
- For parity, provide explicit instructions for Linux and macOS users first, then add a separate note for Windows users.
- Avoid listing Windows tools in a way that implies they are required or preferred for the workflow, especially when the main environment is Linux.
- Where possible, link to cross-platform documentation or note that most commands are identical across Linux, macOS, and Windows (with WSL or similar).
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-provision-vnet.md
...rticles/hdinsight/hbase/apache-hbase-provision-vnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates Windows bias by exclusively referencing Windows in the virtual machine creation instructions ("Create a Virtual Machine Running Windows Server") and omitting equivalent Linux VM creation steps or links. The example for verifying communication uses generic commands (ping), but the VM creation section is Windows-centric and does not provide parity for Linux users.
Recommendations
- Add instructions and links for creating a Linux-based virtual machine in Azure, such as Ubuntu or CentOS, alongside the Windows VM example.
- Present both Windows and Linux VM creation options in parallel, or mention Linux first to avoid implicit prioritization of Windows.
- Ensure that subsequent steps (such as connecting, verifying communication, and using tools) include Linux-specific guidance where appropriate.
- Review all referenced links to ensure Linux equivalents are provided wherever Windows-specific documentation is cited.
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 a link to 'Work in Apache Hadoop on HDInsight from a Windows PC' is given before any mention of Linux or cross-platform tools. There is also a reference to Windows-specific tools, but no equivalent Linux-focused guidance or examples are provided. The main body of the documentation does not provide command-line or configuration examples, so bias in code samples is not present.
Recommendations
- Add parallel Linux-focused guidance and links in the 'Next steps' section, such as 'Work in Apache Hadoop on HDInsight from a Linux PC' or 'Using HDInsight from Linux/macOS'.
- Ensure that any references to platform-specific tools (e.g., Windows tools) are balanced with Linux/macOS equivalents.
- Where possible, provide cross-platform instructions or clearly indicate when steps are platform-specific.
- Review linked documentation to ensure Linux users have equivalent onboarding and troubleshooting resources.
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 generally maintains a neutral tone regarding platform bias, but in the 'Next steps' section, it lists 'Work in Apache Hadoop on HDInsight from a Windows PC' before any Linux-specific guidance. Additionally, it references a Windows-specific tooling page without mentioning Linux equivalents, which may suggest a subtle Windows bias.
Recommendations
- Add a parallel link or section for 'Work in Apache Hadoop on HDInsight from a Linux PC' or 'Linux tools for HDInsight' in the 'Next steps' section.
- Ensure that Linux-based workflows and tools are mentioned alongside Windows options, ideally in the same section or with equal prominence.
- Review referenced documentation (such as 'hdinsight-hadoop-windows-tools.md') to ensure Linux parity in examples and tooling guidance.
- Consider reordering or grouping platform-specific links together, or providing a platform-neutral introduction before listing OS-specific resources.
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
Windows First
Missing Linux Example
Summary
The documentation page focuses exclusively on .NET (C#) samples and references Visual Studio, which is traditionally a Windows-centric development environment. There are no examples or references for Linux-specific tools, environments, or workflows. The prerequisite and sample instructions assume a Windows/.NET context, with no mention of Linux or cross-platform alternatives.
Recommendations
- Include explicit instructions or notes on how to use the .NET SDK and samples on Linux (e.g., using .NET Core/SDK on Linux, VS Code, or JetBrains Rider).
- Mention and provide examples for running the samples on Linux, including any required dependencies or setup steps.
- Reference cross-platform development tools (such as VS Code) alongside Visual Studio.
- Clarify that the .NET SDK and samples are cross-platform if applicable, and provide troubleshooting or environment setup guidance for Linux users.
- Ensure parity in documentation structure and depth between Windows and Linux environments.
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 tooling by exclusively referencing Azure SQL Database as the external metastore solution, without mentioning or providing examples for commonly used open-source alternatives (such as MySQL or PostgreSQL) that are often preferred in Linux-based Hadoop deployments. There are no command-line examples (PowerShell or Bash), but the only database technology discussed is a Microsoft product, and all configuration steps assume use of Azure Portal or Ambari UI, with no Linux-native or cross-platform CLI guidance.
Recommendations
- Include guidance and examples for using open-source databases (e.g., MySQL, PostgreSQL) as external metastores, which are supported by Hive and Oozie and commonly used in Linux environments.
- Provide CLI-based instructions (using Bash/SSH) for configuring external metastores, in addition to portal and UI-based steps.
- Mention and link to documentation for setting up and connecting to non-Azure SQL databases, especially for users running HDInsight clusters in Linux environments or hybrid clouds.
- Clarify that while Azure SQL Database is recommended for Azure-native deployments, other RDBMS options are available and supported for Hive/Oozie/Ambari metastores.
- Add examples or references for managing firewall rules and connectivity for non-Azure SQL databases, which may be hosted on Linux servers.
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 most network management tasks, but PowerShell commands are consistently listed before CLI commands. This ordering, along with the use of PowerShell-specific scripting in some examples, subtly prioritizes Windows-centric tooling and patterns, even though Azure CLI is cross-platform and more native to Linux environments. There are no explicit Linux shell (bash) examples, and the documentation does not mention Linux-specific tools or workflows.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or list Azure CLI first to reflect its cross-platform nature and popularity among Linux users.
- Explicitly state that Azure CLI commands work natively on Linux, macOS, and Windows, and provide bash shell examples where appropriate.
- Where PowerShell scripting is used (e.g., looping over NICs), provide equivalent bash/CLI scripts for Linux users.
- Add a note clarifying that all management tasks can be performed from Linux environments using Azure CLI, and link to relevant Linux setup guides.
- Consider including screenshots or walkthroughs using Linux terminals to further demonstrate parity.
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 in the 'Next steps' section, which are primarily Windows-based. Additionally, the workflow for accessing and deleting clusters is described in terms of the Azure Portal UI, which is platform-agnostic but often more familiar to Windows users. There are no explicit Linux command-line examples or mentions of Linux-specific tools, and no PowerShell or CMD examples are present. However, the cluster creation link refers to 'linux-clusters', and the main Grafana access method is via web browser, which is cross-platform.
Recommendations
- Include references to cross-platform or Linux-native tools for managing HDInsight clusters, such as Azure CLI or Azure Cloud Shell, alongside or instead of Visual Studio tools.
- Provide command-line examples (using Bash/Azure CLI) for common tasks like accessing Grafana or deleting clusters, to ensure Linux users have parity.
- Balance 'Next steps' resources by including links to Linux-friendly development environments or tools, not just Visual Studio.
- Explicitly state that the Azure Portal and Grafana web UI are accessible from any OS, to reinforce cross-platform compatibility.
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 demonstrates a mild Windows bias by presenting Azure PowerShell examples before Azure CLI examples in key sections, and by providing detailed PowerShell scripts for network security group configuration. While Azure CLI (cross-platform) examples are included, there are no native Linux shell (bash) or scripting examples for Azure resource management. However, the DNS configuration sections do focus on Linux (Bind) and the network validator tool is recommended for use on Azure Linux VMs, which helps balance the overall bias.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid the perception of Windows-first bias.
- Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and are recommended for Linux users.
- Consider providing bash script examples for common tasks, especially for Linux-focused audiences.
- Where PowerShell is used, clarify that PowerShell Core is available on Linux and macOS, or provide equivalent bash/CLI commands.
- Add a brief section or note highlighting the parity between PowerShell and CLI, and guide users on choosing the best tool for their OS.
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
Missing Linux Example
Windows Tools
Summary
The documentation describes how to configure automatic topic creation in Apache Kafka on Azure HDInsight, mentioning PowerShell and Resource Manager templates for configuration during cluster creation. However, it does not provide any Linux/Unix CLI or Bash examples, nor does it mention Linux-native tools or workflows for cluster creation or configuration. The only automation tool mentioned is PowerShell, which is Windows-centric, and there is no parity for Linux users.
Recommendations
- Include equivalent Bash or Azure CLI examples for configuring Kafka during cluster creation, alongside or instead of PowerShell.
- Mention and provide examples for using Linux-native tools (such as Bash scripts or the Azure CLI) for cluster configuration.
- Ensure that automation instructions are cross-platform by referencing both Windows and Linux tools equally.
- Explicitly state that the steps can be performed from any OS, and clarify when a tool is Windows-specific.
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 examples for deployment, resource review, and cleanup. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some sections, PowerShell is mentioned before or alongside CLI without clarifying cross-platform usage. There are no Linux-specific shell examples (e.g., Bash), and no mention of Linux tools or environments, which may disadvantage Linux users or suggest a Windows-first approach.
Recommendations
- Clearly indicate that Azure CLI commands are cross-platform and can be run on Windows, Linux, and macOS.
- Consider providing Bash shell examples or explicitly referencing Bash for Linux/macOS users, especially in sections where command-line usage is demonstrated.
- If PowerShell is included, clarify that PowerShell Core is available cross-platform, or provide separate tabs for Windows PowerShell and Bash.
- Where possible, lead with Azure CLI/Bash examples, as these are more universally applicable, and mention PowerShell as an alternative.
- Add notes or links for Linux/macOS users about installing and using Azure CLI in their environments.
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 references the Windows-style environment variable (%HADOOP_HOME%) when describing the location of the core-site.xml file, and does not provide the Linux equivalent ($HADOOP_HOME). This suggests a subtle Windows-first bias. No explicit PowerShell or Windows command-line examples are present, but the use of Windows path notation and environment variable syntax may confuse Linux users. There are no Linux-specific examples or clarifications.
Recommendations
- When referencing environment variables or file paths, provide both Windows (%HADOOP_HOME%) and Linux ($HADOOP_HOME) syntax.
- Clarify that the location of configuration files applies to both Windows and Linux clusters, and show both path formats if they differ.
- Review for any other implicit Windows assumptions and ensure Linux parity in terminology and examples.
- If command-line examples are added in the future, ensure both Windows (cmd/PowerShell) and Linux (bash) examples are provided.
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 a link to 'Work in Apache Hadoop on HDInsight from a Windows PC' is given before any mention of Linux equivalents. Additionally, there is a reference to Windows-specific tooling, but no parallel guidance or examples for Linux users are provided. The main body of the documentation does not include command-line examples, but the resource links and structure suggest a Windows-centric approach.
Recommendations
- Add equivalent guidance and links for Linux users in the 'Next steps' section, such as 'Work in Apache Hadoop on HDInsight from a Linux PC' or similar documentation.
- Ensure that any references to Windows tools or workflows are paired with Linux alternatives, or provide cross-platform instructions where possible.
- Review linked pages (e.g., 'hdinsight-hadoop-windows-tools.md') to ensure Linux parity and consider linking to Linux-specific tools or instructions.
- Consider reordering links or examples so that Linux and Windows are presented with equal prominence, or in alphabetical order to avoid perceived prioritization.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides both Linux and Windows instructions for editing the hosts file, but the Linux example is more detailed and comes first. The Windows-specific instructions are brief and appear after the Linux steps. There is a screenshot for Windows, but no command-line example (e.g., using PowerShell or Notepad). The document mentions the Windows hosts file location but does not provide a step-by-step example for Windows users, nor does it mention Linux tools before Windows equivalents. Overall, there is a slight Windows bias in that Windows is treated as a secondary platform, with less detailed guidance.
Recommendations
- Provide step-by-step instructions for editing the hosts file on Windows, including example commands (e.g., using Notepad or PowerShell) similar to the Linux example.
- Include a command-line example for testing connectivity from Windows (e.g., using curl for Windows or PowerShell's Invoke-WebRequest), not just a screenshot.
- Ensure that both Linux and Windows examples are equally detailed and appear in parallel, rather than Linux first and Windows as an afterthought.
- Explicitly mention that the instructions apply to both Linux and Windows VMs, and provide parity in troubleshooting and verification steps for both platforms.
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
Medium Priority
View Details →
Detected Bias Types
Windows Tools
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 servers. The sample data, parser, and log schema are all tailored to Microsoft IIS, with no mention of Apache, Nginx, or other common Linux-based web servers. There are no examples or guidance for analyzing non-Windows log formats, nor suggestions for adapting the workflow to Linux environments.
Recommendations
- Include examples using log formats from popular Linux web servers such as Apache (access.log) or Nginx.
- Provide or reference a generic log parser or libraries for non-IIS logs, and demonstrate how to use them in Spark.
- Clarify that the sample data and parser are specific to IIS/Windows, and suggest equivalent workflows for Linux-based logs.
- Offer guidance on how to upload and analyze custom log files from Linux servers.
- Balance the documentation by mentioning both Windows and Linux scenarios, or provide links to Linux-focused log analysis tutorials.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hadoop/apache-hadoop-use-hive-curl.md
...ticles/hdinsight/hadoop/apache-hadoop-use-hive-curl.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash/cURL and PowerShell/Invoke-WebRequest examples for all major steps, but there is a subtle Windows bias: PowerShell is mentioned first in the prerequisites, and Windows/PowerShell is often referenced before Bash/Linux. The use of Windows-specific terminology (e.g., 'on Windows PowerShell') and the explicit mention of credential pop-ups (a Windows UX pattern) further reinforce this bias, even though Linux/Bash examples are present and complete.
Recommendations
- List Bash/cURL examples before PowerShell/Windows examples to avoid the perception of Windows-first bias.
- In the prerequisites, mention Bash/cURL before PowerShell/Invoke-WebRequest, or present them in parallel.
- Use neutral language such as 'On Bash' and 'On PowerShell' instead of 'on Windows PowerShell', to avoid platform-preference signaling.
- Where possible, provide parity in explanation detail for both Bash and PowerShell examples (e.g., credential handling).
- Consider a tabbed or side-by-side layout for Bash and PowerShell examples to emphasize equal support.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hbase/apache-hbase-tutorial-get-started-linux.md
...sight/hbase/apache-hbase-tutorial-get-started-linux.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally focuses on Linux/Bash workflows, but in the prerequisites section, it presents Windows (specifically Windows Subsystem for Linux and PowerShell) as the primary environment. Bash on Windows is mentioned before native Linux/Unix shells, and PowerShell alternatives are described in detail, suggesting a Windows-first approach. There are no explicit Linux-only gaps, but the ordering and emphasis may subtly favor Windows users.
Recommendations
- Present native Linux/Unix instructions first, followed by Windows-specific notes as alternatives.
- Avoid suggesting Windows Subsystem for Linux as the default Bash environment; instead, treat it as one of several options.
- When referencing PowerShell cmdlets, provide equivalent Linux/Unix commands side-by-side.
- Clarify that all examples work natively on Linux and macOS, and only require WSL or PowerShell on Windows.
- Ensure that all tooling and command-line examples are cross-platform or have clear, parallel instructions for each OS.