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 451-475 of 867 flagged pages
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-create-non-interactive-authentication-dotnet-applications.md
...ate-non-interactive-authentication-dotnet-applications.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only C#/.NET examples, referencing NuGet and PowerShell commands, and omitting any Linux-specific instructions or cross-platform considerations. The instructions assume a Windows development environment, with no mention of how to perform equivalent tasks on Linux or using cross-platform tools.
Recommendations
- Include equivalent instructions for developing and running the .NET application on Linux (e.g., using .NET Core/SDK on Linux).
- Provide examples for installing NuGet packages using the dotnet CLI (dotnet add package ...) instead of or in addition to Install-Package, which is PowerShell-specific.
- Mention any prerequisites or differences when running the sample code on Linux, such as environment variable handling or secure string usage.
- Link to documentation for setting up a .NET development environment on Linux.
- Add notes or sections highlighting cross-platform compatibility and any platform-specific caveats.
- If referencing PowerShell, also provide Bash/Azure CLI equivalents for authentication and resource management steps.
Create Pull Request
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-add-hive-libraries.md
...icles/hdinsight/hdinsight-hadoop-add-hive-libraries.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. The primary script referenced is a PowerShell (.ps1) script, and the script location section lists the PowerShell script before the Bash script. Additionally, the instructions for uploading files to Azure Storage recommend Azure Storage Explorer, a tool with a strong Windows association, and mention the Azure portal (also Windows-centric) before any CLI or Linux-native options. While Linux is referenced (and a Bash script is provided), the ordering and tooling recommendations favor Windows users.
Recommendations
- List both PowerShell and Bash script locations together, or list the Bash script first if the cluster is Linux-based.
- Provide explicit Linux-native instructions and tools for uploading files to Azure Storage (e.g., Azure CLI, azcopy, or blobfuse), not just Azure Storage Explorer.
- Where possible, use cross-platform terminology and avoid assuming the user is on Windows.
- Clarify which script (PowerShell or Bash) should be used depending on the user's environment, and provide parity in examples and instructions.
- Include Linux CLI examples for all steps, especially for storage account and blob container creation and file upload.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-custom-ambari-db.md
.../main/articles/hdinsight/hdinsight-custom-ambari-db.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively referencing Azure SQL Database (a Microsoft/Windows-centric technology) as the only supported external database for Ambari. There are no examples or mentions of using Linux-native or open-source database systems (such as PostgreSQL or MySQL) as alternatives. All command-line examples use Azure CLI, which is cross-platform, but the overall workflow and requirements are tightly coupled to Microsoft technologies, with no guidance for Linux-preferred database setups.
Recommendations
- Document support (or lack thereof) for Linux-native/open-source databases (e.g., PostgreSQL, MySQL) as external Ambari DB options, and provide setup instructions if supported.
- If only Azure SQL Database is supported, explicitly state this limitation and provide rationale.
- Include examples or notes for Linux users, such as using Azure CLI from a Linux shell, and clarify that no PowerShell-specific steps are required.
- If possible, provide parity in tooling and workflows for both Windows and Linux environments, or clearly indicate any platform-specific requirements.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-create-linux-clusters-arm-templates.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-create-linux-clusters-arm-templates.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page shows a mild Windows bias by referencing PowerShell and Visual Studio (both Windows-centric tools) before or more prominently than cross-platform or Linux-native alternatives. PowerShell deployment is described before Azure CLI, and Visual Studio is highlighted for template deployment, with no mention of Linux-native IDEs or editors beyond a brief note about Visual Studio Code. There are no explicit Linux command-line examples or references to Linux-specific tooling.
Recommendations
- Present Azure CLI deployment instructions before or alongside PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
- Expand on the use of Visual Studio Code (which is cross-platform) for template deployment, and provide step-by-step examples for Linux environments.
- Include Linux shell (bash) examples for deploying templates, not just PowerShell.
- Mention Linux-native editors (e.g., vim, nano) as alternatives for editing templates.
- Ensure that references to Windows-centric tools (like Visual Studio and PowerShell) are balanced with Linux-friendly options, and clarify cross-platform compatibility where applicable.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-create-linux-clusters-adf.md
...dinsight/hdinsight-hadoop-create-linux-clusters-adf.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation demonstrates a strong Windows/PowerShell bias. All command-line examples for resource creation and file management are provided exclusively in PowerShell, with no equivalent Bash, Azure CLI, or Linux shell examples. The prerequisites and workflow assume the user is using PowerShell, and references to tools or scripting are Windows-centric. There is no mention of how to perform these steps on Linux or macOS, nor are cross-platform alternatives (such as Azure CLI) presented. This may hinder Linux users or those preferring non-Windows environments.
Recommendations
- Provide equivalent Azure CLI (az) commands for all PowerShell scripts and steps, as Azure CLI is cross-platform and works natively on Linux and macOS.
- Explicitly mention that the tutorial can be followed from Linux/macOS and provide Bash shell examples where appropriate.
- In the prerequisites, offer both PowerShell and Azure CLI as options, with links to installation guides for each.
- Where file operations are performed (such as copying blobs), show both PowerShell and Azure CLI (or even Python SDK) alternatives.
- Review all step-by-step instructions to ensure parity for Linux users, including screenshots or notes where the Azure Portal UI may differ.
- Consider adding a section or callout for Linux/macOS users, summarizing the main differences or additional steps required.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-linux-information.md
...ticles/hdinsight/hdinsight-hadoop-linux-information.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation is generally Linux-focused, as expected for HDInsight on Linux, but there are some subtle Windows biases. PowerShell is listed as a primary method for accessing Azure Data Lake Storage Gen1, and Windows-specific tools (like Data Lake Tools for Visual Studio) are mentioned. In some lists, Windows/PowerShell tools are mentioned before Linux/CLI equivalents, which may suggest a Windows-first approach. However, most command-line examples use Bash/cURL/jq, and Linux tools are well represented.
Recommendations
- Ensure that for every PowerShell or Windows tool mentioned, an equivalent Linux/CLI method is provided and listed with equal prominence.
- When listing tools or methods, alternate the order or group by platform (e.g., 'Windows tools', 'Linux tools') to avoid implicit prioritization.
- Provide explicit Linux/Bash examples for all operations, especially where PowerShell or Visual Studio tools are mentioned.
- Consider adding a table or section summarizing cross-platform access methods, clearly indicating which are available on Linux, macOS, and Windows.
- Where possible, avoid listing Windows-specific tools (like Visual Studio extensions) without also mentioning cross-platform alternatives.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-oms-log-analytics-tutorial.md
...insight/hdinsight-hadoop-oms-log-analytics-tutorial.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are consistently provided before Azure CLI (Linux-friendly) examples, and the PowerShell Az module is referenced as a primary automation tool. The structure and ordering of sections (PowerShell before CLI) reinforce a Windows-first approach. While Linux is referenced (e.g., performance counters, SSH logs, and a Linux tutorial link), there are no explicit Linux shell or scripting examples beyond Azure CLI, and Windows-centric tools (PowerShell) are emphasized.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present them side-by-side, to avoid a Windows-first impression.
- Explicitly mention that Azure CLI commands are cross-platform and runnable on Linux, macOS, and Windows.
- Where PowerShell is referenced, consider also providing Bash or shell script equivalents for common administrative tasks.
- Expand on Linux-specific monitoring or troubleshooting steps, especially for agent management and log collection.
- Clarify in prerequisites that both Windows and Linux users are supported equally, and link to Linux-specific setup guides where appropriate.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-migrate-dotnet-to-linux.md
.../hdinsight/hdinsight-hadoop-migrate-dotnet-to-linux.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows-first bias by focusing on migration from Windows-based HDInsight and providing instructions that rely heavily on Windows-specific tools (Visual Studio, .NET Portability Analyzer for Visual Studio). There are no examples or guidance for performing equivalent steps (such as portability analysis, building, or deploying) using Linux-native tools or workflows. The documentation assumes the user is developing on Windows and does not address Linux development environments.
Recommendations
- Provide instructions for running the .NET Portability Analyzer or similar tools on Linux (e.g., via command-line or cross-platform alternatives).
- Include examples of building .NET projects for Mono/HDInsight using cross-platform tools such as the dotnet CLI or Mono's xbuild/msbuild on Linux.
- Offer guidance for users developing on Linux, not just those migrating from Windows.
- Mention Linux file path conventions and provide code examples that are platform-agnostic or demonstrate both Windows and Linux paths.
- Reference Linux-native editors or IDEs (such as VS Code, JetBrains Rider, or MonoDevelop) as alternatives to Visual Studio.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-customize-cluster-bootstrap.md
...nsight/hdinsight-hadoop-customize-cluster-bootstrap.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by providing detailed PowerShell examples and a complete PowerShell script, while omitting equivalent Linux CLI or Bash examples. The primary programmatic approaches highlighted are PowerShell, .NET SDK, and ARM templates, with no mention of Azure CLI or Bash scripting for Linux users. The prerequisites and verification steps also assume a Windows-centric workflow, and there is no guidance for Linux-native tooling or scripting.
Recommendations
- Add equivalent Azure CLI and Bash script examples for customizing HDInsight clusters, especially for configuration tasks currently shown only in PowerShell.
- Include Linux prerequisites, such as Azure CLI installation and usage instructions.
- Present cross-platform approaches (e.g., Azure CLI, REST API) before or alongside Windows-specific tools like PowerShell.
- Ensure that all sample scripts and configuration steps are available for both Windows and Linux environments.
- Update verification steps to include methods accessible from Linux (e.g., using curl, jq, or browser-agnostic instructions).
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-hadoop-optimize-hive-query.md
...cles/hdinsight/hdinsight-hadoop-optimize-hive-query.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by mentioning Azure PowerShell and the Azure portal as primary tools for cluster management, with no explicit mention or examples of Linux-native tools or workflows (such as Azure CLI on Linux, SSH, or Bash scripting). The order of tool presentation (portal, PowerShell, CLI) also subtly prioritizes Windows-centric approaches. No Linux-specific examples or screenshots are provided, and the documentation does not address Linux user workflows directly.
Recommendations
- Include explicit examples and instructions using Azure CLI commands on Linux for cluster management tasks, such as scaling worker nodes.
- Provide screenshots or terminal output from Linux environments (e.g., Bash shell) alongside or instead of Azure portal/PowerShell images.
- Mention and demonstrate how to use SSH or Bash scripts for interacting with HDInsight clusters, especially for Linux users.
- Ensure that references to tools and workflows are platform-neutral or, where possible, present Linux-native options first or equally.
- Add a section or callout for Linux users, clarifying that all features are available and supported on Linux-based HDInsight clusters, and link to relevant Linux documentation.
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 First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While the content is generally cross-platform and HDInsight clusters are Linux-based, the documentation repeatedly references Windows-specific tools (such as Azure PowerShell and Windows PowerShell cmdlets) and lists them alongside or before Linux/CLI alternatives. There is a lack of explicit Linux shell or Bash examples, and the 'Related content' section highlights working from a Windows PC. Script actions are described as being available from the Azure portal, HDInsight Windows PowerShell cmdlets, or the .NET SDK, with no mention of Bash or Linux-native scripting. The Azure CLI is mentioned, but not emphasized equally. There are no explicit Linux/Bash command examples, and Windows tools are sometimes mentioned first or exclusively.
Recommendations
- Ensure that Linux/Bash/CLI examples are provided wherever PowerShell or Windows tools are mentioned, especially for script actions and cluster management.
- When listing setup methods or tools, alternate the order or explicitly state parity between Windows and Linux tools (e.g., 'Azure CLI (Linux/macOS/Windows)' and 'Azure PowerShell (Windows/macOS/Linux)').
- Add explicit Bash or shell script examples for common tasks, especially in sections discussing script actions or automation.
- In the 'Related content' section, include links to guides for working from Linux/macOS as well as Windows.
- Avoid referring to 'Windows PowerShell cmdlets' exclusively; use 'PowerShell' and clarify cross-platform support where applicable.
- Highlight that the Azure CLI is cross-platform and can be used from Linux, macOS, and Windows equally.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-linux-ambari-ssh-tunnel.md
...rticles/hdinsight/hdinsight-linux-ambari-ssh-tunnel.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation provides both cross-platform (ssh command) and Windows-specific (PuTTY) instructions for creating SSH tunnels. However, it gives significant prominence to Windows tools and patterns: PuTTY, a Windows SSH client, is given a dedicated section with detailed, step-by-step instructions and screenshots, while no equivalent graphical Linux SSH client (such as GNOME Terminal, Konsole, or tools like Remmina) is mentioned. The browser compatibility notes focus on Windows proxy settings and limitations, and troubleshooting is framed around Windows-centric browsers (Edge, Internet Explorer, Chrome on Windows). There are no Linux-specific troubleshooting tips, nor are Linux GUI SSH tools or their workflows covered.
Recommendations
- Add a section for creating SSH tunnels using popular Linux graphical SSH clients (e.g., GNOME Terminal, Remmina, or KDE Konsole), including screenshots and step-by-step instructions.
- Balance the browser troubleshooting and proxy configuration advice by including Linux-specific browser settings and potential issues (e.g., how to set up SOCKS5 in Firefox or Chrome on Linux, or mention Linux proxy tools like ProxyChains).
- If mentioning Windows-specific tools like PuTTY, provide parity by referencing or linking to equivalent Linux tools and workflows.
- Include troubleshooting tips relevant to Linux users, such as handling SSH agent forwarding, permissions, or common Linux SSH client errors.
- Consider reordering sections so that cross-platform or Linux-native methods are presented before or alongside Windows-specific tools, to avoid a 'windows_first' impression.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-operationalize-data-pipeline.md
...es/hdinsight/hdinsight-operationalize-data-pipeline.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While the core pipeline and cluster operations are Linux/Unix-centric (using SSH, SCP, bash, and Hadoop/HDFS commands), the documentation repeatedly presents Windows-specific instructions, tools, and terminology first or exclusively. Windows tools and environments (such as the Azure portal, Query Editor, and references to Windows Subsystem for Linux) are mentioned before or instead of native Linux equivalents. There is a lack of explicit Linux desktop guidance for some steps, and some command examples use Windows command prompt syntax (e.g., 'cmd' code blocks) even when the context is cross-platform.
Recommendations
- Provide parallel instructions and examples for both Windows and Linux/macOS environments, especially for file transfers (SCP), SSH, and database access.
- When referencing tools like Azure Query Editor or the Azure portal, clarify that these are web-based and platform-agnostic, or provide CLI alternatives (e.g., Azure CLI, sqlcmd) with Linux/macOS usage examples.
- Avoid using Windows Subsystem for Linux (WSL) as the default or only Linux environment for Windows users; instead, offer native Linux/macOS instructions and note WSL as an option for Windows.
- For all command-line examples, specify the shell/environment (e.g., bash, cmd, PowerShell) and provide both Windows and Linux/macOS syntax where they differ.
- Ensure that any references to browser extensions or tools (like Foxy Proxy) include Linux/macOS installation and usage notes.
- Review the order of instructions to avoid always presenting Windows-first; alternate or present Linux/macOS and Windows instructions in parallel sections.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-migrate-granular-access-cluster-configurations.md
...insight-migrate-granular-access-cluster-configurations.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation demonstrates a moderate Windows bias. It references and provides migration guidance for several Windows-centric tools (Visual Studio, Visual Studio Code, Azure Data Lake and Stream Analytics Tools for Visual Studio, Az.HDInsight PowerShell) and describes PowerShell cmdlets in detail. While cross-platform SDKs and tools (Azure CLI, IntelliJ, Eclipse, Python, Java, Go) are also mentioned, Windows tools and patterns are often listed first or described in greater detail. There are no Linux-specific examples or explicit parity guidance for Linux users.
Recommendations
- Add explicit Linux-focused examples, such as using Azure CLI from a Linux shell, or scripting with Bash.
- Include migration steps or troubleshooting for Linux-native environments (e.g., how to update or use the SDKs/tools on Linux).
- Balance the order of tool presentation: alternate or group by platform, or explicitly note cross-platform compatibility.
- For PowerShell cmdlets, provide equivalent Azure CLI or REST API commands where possible.
- Clarify which tools are cross-platform (e.g., VS Code, Azure CLI) and which are Windows-only, to help Linux users navigate the options.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/kafka/apache-kafka-producer-consumer-api.md
.../hdinsight/kafka/apache-kafka-producer-consumer-api.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation shows a moderate Windows bias: Windows tools and patterns (such as Putty and .cmd code blocks) are mentioned first or exclusively in some sections, and Linux-native alternatives are not always presented with equal prominence. Some commands are shown in Windows command prompt style, and the SSH client recommendation is Windows-centric.
Recommendations
- When listing prerequisites, mention both Windows and Linux SSH clients equally (e.g., 'An SSH client such as OpenSSH (Linux/macOS) or Putty (Windows)').
- For command-line examples, provide both Windows and Linux/macOS command syntax where they differ, or clarify which OS the example is for.
- Use neutral or dual code block formatting (e.g., both 'cmd' and 'bash') for commands like 'scp', 'ssh', and 'mvn', and clarify any OS-specific differences.
- Where Windows tools (like Putty) are mentioned, also mention Linux/macOS equivalents (like the built-in 'ssh' command).
- Review all code snippets and instructions to ensure Linux users are not required to adapt Windows-specific instructions on their own.
- Consider adding a short section or callout for cross-platform usage tips, especially for common developer environments.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-log-management.md
...ob/main/articles/hdinsight/hdinsight-log-management.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell and Windows-centric tools (e.g., Visual Studio, Power Query for Excel, System Center) are mentioned frequently, often before or instead of Linux alternatives. While some Linux-native tools and workflows (SSH, logrotate, Ambari UI) are included, scripting and automation examples are predominantly PowerShell-focused, and Linux command-line examples are sparse or missing in several sections. There is a lack of parity in scripting guidance and tool recommendations for Linux users.
Recommendations
- Provide Bash or shell script equivalents alongside all PowerShell examples, especially for log collection, archiving, and Azure Storage access.
- Mention Linux-native tools (e.g., Azure CLI, AzCopy, rsync, cron jobs) before or alongside Windows tools like PowerShell and Visual Studio.
- Include explicit Linux command-line examples for common tasks such as downloading logs, automating retention, and interacting with Azure Storage.
- Highlight cross-platform tools and SDKs, and clarify which tools are available on both Windows and Linux.
- Balance references to Windows-specific monitoring solutions (e.g., System Center) with Linux-compatible alternatives or open-source monitoring stacks.
- Ensure that all scripting and automation guidance is available for both Windows and Linux environments, not just PowerShell.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-plan-virtual-network-deployment.md
...hdinsight/hdinsight-plan-virtual-network-deployment.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for network configuration tasks, but PowerShell commands are consistently listed before Azure CLI commands. There are no Linux shell or Bash-specific examples, and the documentation does not mention Linux-native tools or patterns (such as Bash scripting or Linux command-line utilities) for network management. The focus on PowerShell and the ordering of examples may give the impression of a Windows-centric approach, despite HDInsight clusters themselves being Linux-based.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI (which is cross-platform) first, especially since HDInsight clusters are Linux-based.
- Explicitly mention that Azure CLI commands can be run natively on Linux, macOS, and Windows, and provide Bash script snippets where appropriate.
- Include references or examples using Linux-native tools (e.g., curl, dig, nslookup) for network diagnostics alongside Azure CLI/PowerShell.
- Clarify that PowerShell is available cross-platform, but highlight Azure CLI as the primary tool for Linux users.
- Where possible, provide context or links for Linux users on installing and using Azure CLI and other relevant tools.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-overview.md
...ocs/blob/main/articles/hdinsight/hdinsight-overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page for Azure HDInsight shows a bias toward Windows by emphasizing Windows-only BI tools (Power Query, Microsoft Hive ODBC Driver, Excel integration) and not providing Linux or cross-platform alternatives. Several BI integration examples explicitly require Windows, and there is no mention of Linux-compatible tools or workflows for these scenarios. The development tools section lists both cross-platform and Windows-only IDEs, but the BI tooling is Windows-centric. There are no PowerShell examples or explicit command-line instructions, but the lack of Linux parity in BI tooling and examples is notable.
Recommendations
- Include examples and documentation for Linux-compatible BI tools (e.g., Tableau, Apache Superset, Qlik, or open-source ODBC/JDBC drivers) for connecting to HDInsight.
- Explicitly mention and provide instructions for using cross-platform tools (such as VS Code, IntelliJ, Eclipse) for all relevant workflows, not just development.
- Where Excel or Power Query is mentioned as Windows-only, suggest alternative workflows for Linux users (e.g., using Python libraries like pandas, or open-source spreadsheet tools).
- Add a section or callout highlighting cross-platform and Linux-friendly options for data visualization and BI integration.
- Ensure that all 'Get Started' and 'Next Steps' links and examples are not limited to Windows environments, or provide Linux equivalents where necessary.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-private-link.md
...blob/main/articles/hdinsight/hdinsight-private-link.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways. In the connectivity testing step, the only example VM image is Windows 10 Pro, and RDP is the only remote access port mentioned. The instructions for accessing the cluster suggest using a Windows command prompt, and there is no mention of Linux VMs or SSH from a Linux terminal. Additionally, PowerShell is mentioned before Azure CLI in the cluster creation step, and there are no explicit Linux shell or Bash examples. The overall pattern assumes a Windows environment for management and testing, with little to no guidance for Linux users.
Recommendations
- Include Linux VM deployment instructions and examples (e.g., Ubuntu or CentOS) alongside Windows VM examples in the connectivity testing section.
- Mention SSH as the primary remote access method for Linux VMs, and provide instructions for connecting via SSH from a Linux terminal.
- When referencing command-line tools, present Azure CLI and PowerShell examples in parallel, and avoid listing PowerShell first by default.
- Provide explicit Bash or Linux shell command examples where relevant, especially for connectivity and DNS testing.
- Clarify that the steps are applicable to both Windows and Linux environments, and highlight any OS-specific considerations.
- When listing inbound ports for VM access, include SSH (22) for Linux VMs in addition to RDP (3389) for Windows VMs.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-restrict-outbound-traffic.md
...icles/hdinsight/hdinsight-restrict-outbound-traffic.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-related FQDNs (e.g., login.windows.net, login.microsoftonline.com), referencing WindowsUpdate and Windows login activity, and omitting explicit Linux or cross-platform command-line examples. While there is a mention of Ubuntu security updates, the overall focus is on Windows-centric services and patterns, with no PowerShell or CLI scripts provided for either platform.
Recommendations
- Provide explicit examples for both Windows and Linux environments, such as Azure CLI and Bash commands for configuring firewall rules and route tables.
- Balance FQDN examples by including Linux-specific dependencies (e.g., package repositories, Linux authentication endpoints) alongside Windows equivalents.
- Clarify that the steps apply equally to clusters running on Linux-based HDInsight nodes, and highlight any OS-specific considerations.
- Include screenshots or instructions from both the Azure portal and command-line tools (Azure CLI, PowerShell, Bash) to ensure parity.
- Review and update terminology to avoid Windows-centric language (e.g., 'Windows login activity') when the process is generic or applies to both platforms.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-sales-insights-etl.md
...ain/articles/hdinsight/hdinsight-sales-insights-etl.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides a PowerShell example as the primary or only command-line method for triggering the Azure Data Factory pipeline, with no equivalent Bash or Linux-native example. PowerShell and Windows tools (e.g., Power BI Desktop) are mentioned explicitly and in detail, while Linux alternatives or parity are not addressed. The ordering and phrasing suggest a Windows-first approach, and Linux users are left to infer or adapt steps themselves.
Recommendations
- Provide a Bash/Azure CLI example for triggering the Data Factory pipeline, not just PowerShell.
- Explicitly mention that PowerShell commands can be run cross-platform (if true), or provide guidance for Linux/Mac users.
- List both PowerShell and Bash/Azure CLI options side-by-side or in parallel sections to ensure parity.
- Mention or link to Power BI alternatives for Linux users, or clarify that Power BI Desktop is Windows-only and suggest Power BI web as an option.
- Avoid language that implies PowerShell/Windows is the default or only supported environment.
- Ensure that all steps (especially automation and scripting) have clear, tested instructions for both Windows and Linux users.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-restrict-public-connectivity.md
...es/hdinsight/hdinsight-restrict-public-connectivity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell automation examples for DNS setup and referencing PowerShell first when describing how to create a cluster. There are no equivalent Bash or Azure CLI script examples for Linux users, and the PowerShell approach is presented as the primary method for automation.
Recommendations
- Provide equivalent Bash/Azure CLI script examples for DNS automation tasks, ensuring Linux users can follow along without needing PowerShell.
- When referencing how to create a cluster, mention Azure CLI and ARM templates before or alongside PowerShell, not after.
- Add explicit Linux/macOS guidance or notes where automation or scripting is discussed, clarifying that all steps can be performed cross-platform.
- Where possible, use cross-platform tools (e.g., Azure CLI, ARM templates) in code examples, or provide parallel examples for both Windows (PowerShell) and Linux (Bash/CLI).
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-scaling-best-practices.md
...articles/hdinsight/hdinsight-scaling-best-practices.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is listed first among the scaling utilities, and the PowerShell Az module is highlighted, with detailed command examples. The Azure CLI is included, but PowerShell is consistently mentioned before it. There is no explicit mention of Linux-specific command-line environments or tools (e.g., Bash, native Linux scripting), and the documentation assumes familiarity with Windows-centric tools and patterns. However, SSH and Bash commands are provided for cluster management tasks, which helps mitigate bias, but the initial focus and ordering favor Windows users.
Recommendations
- List Azure CLI before PowerShell in the utilities table, as CLI is cross-platform and more commonly used on Linux.
- Provide explicit Bash/Linux shell examples for scaling operations, especially for users who may not use PowerShell.
- Clarify that all command-line utilities (PowerShell, Azure CLI) are available on both Windows and Linux, and provide installation links for both platforms.
- Include a section or note for Linux/macOS users, outlining the recommended tools and any differences in usage.
- Where possible, use neutral language and ordering (e.g., 'Azure CLI or PowerShell') to avoid implying a Windows-first workflow.
Hdinsight
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/hdinsight/hdinsight-supported-node-configuration.md
...es/hdinsight/hdinsight-supported-node-configuration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell scripts as a primary method for deploying HDInsight clusters, mentioning PowerShell before Azure CLI, and providing SKU identifier instructions specifically for PowerShell and 'other scripts' without clarifying or providing Linux/bash examples. There are no explicit Linux or bash command examples or references, and Windows-centric scripting is implied as the default.
Recommendations
- Explicitly mention both PowerShell and bash/Azure CLI scripting throughout, ensuring Linux parity in all instructions.
- Provide example commands for both PowerShell and bash/Azure CLI when discussing VM SKU identifiers and deployment scripts.
- Clarify that the instructions apply equally to Linux environments and provide links to Linux-specific documentation where appropriate.
- Avoid phrasing that prioritizes PowerShell or Windows scripting; instead, use neutral language such as 'in your deployment scripts (PowerShell, bash, Azure CLI, etc.)'.
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 provides both Bash and PowerShell examples throughout, but there is a consistent pattern of mentioning Windows-specific tools and environments (such as Bash on Ubuntu on Windows 10, Windows PowerShell, and explicit references to Windows paths for jq) before or alongside Linux-native alternatives. The prerequisites and setup sections prioritize Windows environments, and some instructions (e.g., jq path in PowerShell) are tailored for Windows users. There are no missing Linux examples, but the overall framing and tool recommendations are Windows-centric.
Recommendations
- In the prerequisites, mention native Linux environments (e.g., Ubuntu, CentOS) before or alongside Windows Subsystem for Linux, and clarify that all Bash examples work natively on Linux.
- When referencing tools like jq, provide installation instructions or links for both Linux and Windows, not just Windows.
- Avoid Windows-specific paths (e.g., C:\HD\jq\jq-win64) in PowerShell examples, or provide equivalent Linux paths for parity.
- When listing shell options, avoid phrasing that implies Windows is the primary or default environment (e.g., 'Bash on Ubuntu on Windows 10' as the main example).
- Consider providing a dedicated section or callout for Linux users, especially in setup and prerequisites.
- Where possible, clarify that all examples are cross-platform unless otherwise noted, and ensure Linux is not presented as an afterthought.