Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 1276-1300 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-troubleshoot-azure-resource-manager.md
...ure-stack-edge-gpu-troubleshoot-azure-resource-manager.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples and troubleshooting steps reference PowerShell cmdlets and modules, with no equivalent instructions for Linux or macOS users. The setup and validation steps focus on PowerShell installation and usage, and there is only a brief mention of a Linux/Mac-specific error without providing any Linux-native troubleshooting steps or examples. Windows tools and patterns are presented exclusively and before any cross-platform considerations.
Recommendations
- Provide equivalent CLI examples using Azure CLI (az) for Linux/macOS users alongside PowerShell commands.
- Include instructions for installing and configuring required tools (e.g., Azure CLI, OpenSSL, certificate management) on Linux and macOS.
- Add troubleshooting steps and examples for common Linux/macOS environments, such as handling certificates and environment variables.
- Reorganize sections to present cross-platform guidance together, rather than focusing on Windows/PowerShell first.
- Explicitly state which steps are platform-specific and provide alternatives where needed.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-troubleshoot-virtual-machine-image-upload.md
...ack-edge-gpu-troubleshoot-virtual-machine-image-upload.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing troubleshooting steps and tooling references that are specific to Windows environments. PowerShell and Hyper-V cmdlets (Convert-VHD, Get-VHD) are mentioned exclusively for VHD conversion and inspection, with no mention of Linux or cross-platform alternatives. The 'Prepare generalized image' link explicitly references Windows VHD preparation, and there are no examples or guidance for Linux users or Linux-based tools. The 'Next steps' section also prioritizes Azure PowerShell deployment, again omitting Linux CLI or cross-platform instructions.
Recommendations
- Include equivalent Linux-based instructions for preparing and converting VHDs, such as using qemu-img or other open-source tools.
- Provide examples using Azure CLI (az) for deployment and management, not just Azure PowerShell.
- Add links or references to documentation for preparing Linux-based VM images, not just Windows VHDs.
- When mentioning tools or commands, present both Windows and Linux options, or clarify if a step is platform-specific.
- Ensure that troubleshooting steps are inclusive of both Windows and Linux environments, or explicitly state any platform limitations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-troubleshoot-virtual-machine-provisioning.md
...ack-edge-gpu-troubleshoot-virtual-machine-provisioning.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: PowerShell commands and scripts are used exclusively for troubleshooting tasks such as listing and deleting ingestion jobs, with no equivalent Bash or Linux CLI examples. In sections where both Windows and Linux are relevant (e.g., VM image preparation), Windows workflows and links are listed before Linux ones, and some troubleshooting steps (e.g., checking for duplicate IPs) use Windows-specific tools like Test-NetConnection (tnc) without providing Linux alternatives. Linux-specific troubleshooting is present but less detailed and often segregated into separate sections, rather than being presented in parallel with Windows guidance.
Recommendations
- Provide equivalent Linux/Bash command examples for all troubleshooting steps that currently use PowerShell or Windows tools (e.g., use curl or wget for REST calls, and use ping/nc for network checks).
- When listing workflows or links for both Windows and Linux, alternate the order or present them side-by-side to avoid always listing Windows first.
- For network troubleshooting, include Linux-native commands (e.g., ping, nc, ss, ip) alongside Windows commands like Test-NetConnection.
- For REST API interactions, show both PowerShell and Bash/curl examples.
- Ensure that Linux troubleshooting guidance is as detailed and prominent as Windows guidance, and integrate Linux steps into the main troubleshooting flow rather than as afterthoughts or separate sections.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/scripts/powershell-webhook-secure-delivery-microsoft-entra-user.md
...owershell-webhook-secure-delivery-microsoft-entra-user.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page is heavily biased towards Windows environments by providing only PowerShell script examples, referencing Azure PowerShell modules, and omitting any equivalent Bash, CLI, or Linux-native instructions. The script assumes the use of PowerShell and Windows-centric tooling, with no mention of cross-platform alternatives or guidance for Linux/macOS users.
Recommendations
- Provide equivalent examples using Azure CLI (az) and Bash scripts for each step, ensuring Linux/macOS users can follow along without PowerShell.
- Explicitly mention that the PowerShell script can be run cross-platform using PowerShell Core, or provide installation instructions for PowerShell on Linux/macOS.
- Include notes or links to documentation for performing the same tasks using REST API calls or SDKs, which are platform-agnostic.
- Reorder or supplement instructions so that cross-platform or Linux-native approaches are presented alongside or before Windows/PowerShell-specific methods.
- Add a section summarizing the requirements and options for users on different operating systems, clarifying how to adapt the instructions for their environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/send-events-webhooks-private-destinations.md
...vent-grid/send-events-webhooks-private-destinations.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 using Windows-style syntax (e.g., .\azbridge.exe), referencing .NET/C# code exclusively, and omitting explicit Linux or cross-platform command examples. While Azure Relay Bridge is described as cross-platform, no Linux-specific instructions or shell examples are given, and the only code sample is in C#.
Recommendations
- Add equivalent Linux/bash command-line examples (e.g., ./azbridge instead of .\azbridge.exe) alongside Windows examples.
- Provide code samples in additional languages (such as Python, Node.js, or bash) to illustrate cross-platform usage.
- Explicitly mention how to run Azure Relay Bridge on Linux (e.g., using chmod +x, running as ./azbridge, or using Docker).
- Clarify that the C# sample is for illustration and link to language-agnostic or multi-language handshake validation examples.
- Ensure that references to tools and SDKs highlight their cross-platform capabilities and provide parity in instructions for both Windows and Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/secure-webhook-delivery.md
...b/main//articles/event-grid/secure-webhook-delivery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias by exclusively using PowerShell scripts and the Azure Cloud Shell's PowerShell environment for setup steps, with no mention or examples for Bash or Linux-native workflows. All scripting and automation steps are shown in PowerShell, and the Azure Shell is always referenced in the context of PowerShell, not Bash. There are no Linux or cross-platform shell examples, and the documentation assumes familiarity with Windows-centric tools and patterns.
Recommendations
- Provide equivalent Bash shell scripts for all PowerShell examples, especially for steps involving Microsoft Graph and Azure CLI.
- Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to perform steps in both environments.
- Where possible, use Azure CLI for scripting and automation, as it is cross-platform, and only use PowerShell-specific commands when necessary.
- Add notes or sections for Linux/macOS users, including any differences in authentication or environment setup.
- Ensure that all referenced scripts (such as those linked in the documentation) have Bash equivalents or are written in a cross-platform way.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-workflows.md
.../main//articles/expressroute/expressroute-workflows.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation references PowerShell as a method for verifying provisioning, and lists it before the Azure portal and CLI. There are no explicit Linux or cross-platform command examples, and no mention of Bash, Cloud Shell, or Linux-native tools. This creates a subtle bias toward Windows-centric workflows and tools.
Recommendations
- When mentioning verification methods, list Azure CLI and Azure portal before PowerShell, or present all three together to avoid implying a preference.
- Provide explicit Azure CLI (cross-platform) command examples alongside or instead of PowerShell examples.
- Reference Azure Cloud Shell as a cross-platform, browser-based option for command-line tasks.
- If scripting is discussed, include both PowerShell and Bash/CLI examples to ensure Linux parity.
- Review for any other implicit assumptions of a Windows environment and clarify that all steps can be performed from Linux/macOS as well.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/subscribe-to-resource-notifications-containerservice-events.md
...ribe-to-resource-notifications-containerservice-events.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides parallel instructions for Azure CLI, Azure PowerShell, and Azure Portal, but consistently includes Azure PowerShell examples and commands, which are primarily used on Windows. The PowerShell sections are always present and often listed before or alongside CLI, and there is no mention of Bash, shell scripting, or Linux-specific considerations. There are no Linux-specific examples or notes about cross-platform differences, and PowerShell is presented as a first-class option, which may bias the documentation toward Windows users.
Recommendations
- Explicitly state that Azure CLI commands work cross-platform (Windows, Linux, macOS) and highlight this in the introduction.
- Add Bash or shell script examples where scripting is relevant, especially for automation scenarios.
- Clarify that Azure PowerShell is available on Linux and macOS via PowerShell Core, or provide guidance for Linux users if there are differences.
- Consider listing Azure CLI before PowerShell in all sections, as CLI is more universally cross-platform.
- Add a note or section on using these commands in Linux environments, including any prerequisites or differences (e.g., shell quoting, authentication).
- Avoid implying that PowerShell is the default or primary automation tool for all users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/authorize-access-shared-access-signature.md
...event-hubs/authorize-access-shared-access-signature.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 PowerShell and Azure CLI together when discussing how to create policy rules, but does not provide explicit Linux or cross-platform command examples. The mention of PowerShell before Azure CLI and the lack of Linux-specific guidance or examples (such as Bash commands or Linux shell usage) reinforces a subtle preference for Windows environments.
Recommendations
- Provide explicit Linux/Bash command examples alongside or before PowerShell examples.
- When mentioning tools, use cross-platform terminology (e.g., 'Azure CLI' before 'PowerShell') and clarify that Azure CLI is available on Windows, Linux, and macOS.
- Include screenshots or instructions from the Azure portal that are platform-agnostic.
- Add a section or note highlighting how to perform the same operations on Linux/macOS, especially for command-line tasks.
- Ensure that all code snippets and instructions are tested and presented for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/authenticate-shared-access-signature.md
...les/event-hubs/authenticate-shared-access-signature.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides code examples for multiple languages and platforms, including Bash for Linux/macOS. However, it includes a dedicated PowerShell section (which is Windows-centric), and the Bash example is listed after PowerShell. There is also a lack of explicit mention of Linux command-line tools or patterns outside the Bash example, and the 'Samples' section only references .NET (which is often associated with Windows, though now cross-platform). The instructions for disabling local/SAS key authentication focus on the Azure Portal and ARM templates, which are cross-platform, but no mention is made of CLI tools like Azure CLI or Azure PowerShell for Linux users.
Recommendations
- List Bash/Linux examples before or alongside PowerShell to avoid implying Windows-first workflows.
- Add explicit references to Linux/Mac tools (e.g., Azure CLI commands for disabling local/SAS key authentication) where only portal or ARM template instructions are given.
- Include sample links for Java, Node.js, or Bash/Linux-based workflows in the 'Samples' section, not just .NET.
- Where PowerShell is used, clarify its availability on Linux and macOS, or provide equivalent Bash commands.
- Ensure that any references to tools or workflows (such as Azure PowerShell) are accompanied by cross-platform alternatives (e.g., Azure CLI).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/event-hubs-dotnet-standard-getstarted-send.md
...ent-hubs/event-hubs-dotnet-standard-getstarted-send.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias by exclusively referencing Visual Studio 2022 (a Windows-centric IDE), using Windows UI navigation (e.g., menu paths), and providing only PowerShell-based NuGet installation commands via the Package Manager Console. There are no instructions or examples for Linux or cross-platform development environments (such as VS Code, JetBrains Rider, or command-line .NET tools), nor are there alternative shell commands (e.g., Bash) for package installation. The documentation assumes a Windows GUI workflow throughout, omitting Linux or macOS equivalents.
Recommendations
- Provide parallel instructions for Linux and macOS users, including using VS Code or JetBrains Rider, and .NET CLI commands (e.g., 'dotnet new console', 'dotnet add package ...') for project creation and package installation.
- Include Bash/zsh shell commands for installing NuGet packages, not just PowerShell/Package Manager Console examples.
- Mention and demonstrate cross-platform development tools and editors, not just Visual Studio 2022.
- Clarify that the .NET SDK and Azure SDK libraries are cross-platform and can be used on Windows, Linux, and macOS.
- Where UI navigation is described (e.g., menu paths), provide equivalent command-line alternatives.
- Add a note or section specifically addressing Linux/macOS setup and usage, including any OS-specific prerequisites or troubleshooting tips.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/dynamically-add-partitions.md
...ain//articles/event-hubs/dynamically-add-partitions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell as the first example for updating partition count, referencing the Windows-specific .NET SDK (WindowsAzure.ServiceBus), and using PowerShell cmdlets. Although a cross-platform Azure CLI example is provided, the ordering and prominence of PowerShell and Windows tools suggest a preference for Windows environments. There are no explicit Linux shell or scripting examples, and Linux-native tooling is not highlighted.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and widely used on Linux.
- Include Linux shell (bash) examples for relevant operations, such as using Azure CLI in bash scripts.
- Reference cross-platform SDKs and avoid highlighting Windows-specific SDKs unless necessary.
- Where PowerShell is used, clarify that it is available on Linux and macOS as well, or provide equivalent bash commands.
- Ensure that any references to tools or patterns are balanced with Linux equivalents, and avoid Windows-first ordering.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/event-hubs-node-get-started-send.md
...rticles/event-hubs/event-hubs-node-get-started-send.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. It instructs users to 'open a Command Prompt window' to install npm packages, and the sample output for running the receiver code uses a Windows-style command prompt path (e.g., 'C:\Self Study\Event Hubs\JavaScript>node receive.js'). There are no explicit Linux or macOS terminal instructions or examples, nor is there mention of cross-platform shell usage. The documentation does not provide parity for Linux users in terms of setup or command-line instructions.
Recommendations
- Replace 'open a Command Prompt window' with 'open a terminal window' or specify both Command Prompt (Windows) and terminal (Linux/macOS) options.
- Provide example commands and sample outputs using both Windows (cmd.exe or PowerShell) and Linux/macOS (bash/zsh) environments.
- Avoid using Windows-specific file paths in example outputs; use generic or cross-platform paths, or provide both Windows and Linux/macOS examples.
- Explicitly state that the instructions work on Windows, Linux, and macOS, and mention any OS-specific prerequisites or differences if applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/event-hubs-capture-python.md
...main//articles/event-hubs/event-hubs-capture-python.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and patterns, such as using backslashes in file paths (e.g., '\' in os.getcwd()), instructing users to open a 'command prompt', and omitting any mention of Linux or cross-platform alternatives. There are no Linux-specific instructions or examples, and the guidance assumes a Windows environment throughout.
Recommendations
- Provide equivalent Linux/macOS instructions alongside Windows instructions, such as using 'terminal' instead of only 'command prompt'.
- Use os.path.join for file paths in Python code to ensure cross-platform compatibility, and avoid hardcoded backslashes.
- Show example commands for both Windows (cmd) and Linux/macOS (bash) when installing packages and running scripts.
- Mention that the scripts and instructions are cross-platform, and explicitly state any platform-specific considerations.
- Include screenshots or references to Azure Portal that are not OS-specific, or provide both Windows and Linux perspectives where relevant.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/transport-layer-security-configure-minimum-version.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/transport-layer-security-configure-minimum-version.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing command-line examples using PowerShell syntax (e.g., .\ARMClient.exe), referencing a Windows-specific tool (ARMClient.exe), and omitting equivalent instructions or examples for Linux or macOS users. There are no bash, curl, or cross-platform CLI examples for obtaining a bearer token or querying the API, and no mention of how to perform these steps outside of a Windows environment.
Recommendations
- Provide equivalent instructions and examples for Linux/macOS users, such as using Azure CLI (az account get-access-token) or curl for API calls.
- Include bash or shell script examples alongside PowerShell commands.
- Mention cross-platform tools (e.g., Azure CLI, REST tools available on Linux/macOS) before or alongside Windows-specific tools.
- Clarify that ARMClient.exe is a Windows tool and suggest alternatives for other platforms.
- Ensure all code snippets and instructions are accessible and relevant to users on all major operating systems.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/event-hubs-geo-dr.md
...cs/blob/main//articles/event-hubs/event-hubs-geo-dr.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in the 'Manual failover' section by listing Azure Portal, Azure CLI, PowerShell, and C# methods, with PowerShell (a Windows-centric tool) given its own tab and no explicit mention of Linux shell scripting or examples. While Azure CLI is cross-platform, there are no Bash or Linux-specific command examples, nor is there mention of Linux automation patterns. The sample code and references are also .NET/C# heavy, with only a single Java sample linked at the end, and no Python or other common cross-platform languages highlighted.
Recommendations
- Add explicit Bash/Linux shell examples for CLI commands, including sample scripts for automation.
- Include Python sample code for failover automation, as Python is widely used on Linux and cross-platform.
- Clarify in the CLI section that Azure CLI commands work on Windows, Linux, and macOS, and provide example terminal prompts for Linux/macOS.
- Balance code samples and references by including links to samples in other languages (e.g., Python, Node.js) and not just .NET/C# and Java.
- Consider adding a section or callout for Linux administrators, highlighting any OS-specific considerations or best practices.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/circuit-placement-api.md
...b/main//articles/expressroute/circuit-placement-api.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 Azure PowerShell (Windows-centric) command-line examples for subscription registration, with no equivalent examples for Linux users (e.g., Azure CLI or Bash). The initial setup steps assume the use of PowerShell, which is most common on Windows, and do not mention or provide alternatives for Linux or cross-platform environments. All subsequent API usage is shown as REST calls, which are platform-neutral, but the initial onboarding is Windows-first.
Recommendations
- Provide Azure CLI (az) command examples alongside or before PowerShell examples for subscription registration and resource provider registration.
- Explicitly mention that both PowerShell and CLI can be used, and link to cross-platform installation guides.
- Add Bash shell examples for Linux users where appropriate.
- Consider reordering examples to present cross-platform (CLI/REST) options first, or at least in parallel with PowerShell.
- Clarify in the text that the API and all management operations are platform-agnostic, and that users can choose their preferred tooling.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/event-hubs-exchange-events-different-protocols.md
...hubs/event-hubs-exchange-events-different-protocols.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows/.NET bias. While it covers both Java and .NET (C#) code samples, .NET examples are consistently present and sometimes precede or are more detailed than their Java counterparts. The .NET examples assume knowledge of Windows-specific behaviors (such as endianness on x86/x64), and the documentation references Microsoft-specific clients and types. There are no explicit Linux or cross-platform command-line examples, and no mention of Linux-specific considerations or tools.
Recommendations
- Ensure that Java examples are always presented alongside .NET examples, and alternate their order to avoid always listing .NET first.
- Add explicit notes about cross-platform compatibility, especially regarding endianness and byte order, clarifying that Java code is portable and .NET code may require special handling on Windows.
- Include Linux-specific or cross-platform command-line examples (e.g., using curl for HTTPS, or CLI tools for Kafka/AMQP) where appropriate.
- Reference open-source, cross-platform AMQP and Kafka clients, not just Microsoft-specific ones.
- Avoid assuming the reader is on Windows/x86/x64; clarify when platform-specific behavior is discussed.
- Where .NET code is shown, mention Mono or .NET Core/5+/6+ for Linux compatibility, or provide equivalent code for Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/customer-controlled-gateway-maintenance.md
...xpressroute/customer-controlled-gateway-maintenance.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for command-line configuration, with no mention of Azure CLI or Bash alternatives that are commonly used on Linux and macOS. The PowerShell section is presented as the sole scripting option, and there is no guidance for Linux users. The use of PowerShell cmdlets and the absence of cross-platform command-line instructions indicate a lack of Linux parity.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell instructions, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that both PowerShell and Azure CLI can be used, and provide guidance for both environments.
- Include Bash script examples or notes for Linux/macOS users where relevant.
- Reorganize the documentation to present Azure CLI and PowerShell options side-by-side, or allow users to select their preferred environment.
- Avoid language that implies PowerShell is the only or primary method for automation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/event-hubs-kafka-stream-analytics.md
...ticles/event-hubs/event-hubs-kafka-stream-analytics.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. It specifically references running commands on a Windows machine using a Node.js command prompt, without mentioning Linux or macOS equivalents. There are no explicit Linux or cross-platform instructions or clarifications, and the only shell environment mentioned is Windows-specific. No Linux-specific tools or terminal instructions are provided.
Recommendations
- Explicitly mention that the command-line steps (e.g., using Maven) work on Linux, macOS, and Windows, and provide example commands for Linux/macOS terminals if there are any differences.
- Replace or supplement the reference to 'Node.js command prompt' with a more generic term such as 'terminal' or 'command prompt', and clarify that any terminal (e.g., Bash, PowerShell, CMD) can be used.
- Add a note or section for Linux/macOS users, especially if there are any environment-specific considerations (e.g., path separators, permissions, or prerequisites).
- Ensure screenshots and instructions are not Windows-centric, or provide alternatives for other platforms if UI or CLI differences exist.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/event-hubs-resource-manager-namespace-event-hub.md
...ubs/event-hubs-resource-manager-namespace-event-hub.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively providing Azure PowerShell examples for deploying and managing Event Hubs resources. There are no Azure CLI (cross-platform) or Bash examples, which are more common for Linux and macOS users. The instructions for command-line deployment, validation, and cleanup are all PowerShell-based, and there is no mention of Linux-specific workflows or tools.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell scripts, including deployment, validation, and cleanup steps.
- Include Bash shell instructions where appropriate, especially for users on Linux and macOS.
- Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide users with a choice of which environment to use.
- Ensure that references to command-line tools and scripts are not Windows-centric and clarify cross-platform compatibility.
- Consider reordering or presenting PowerShell and CLI examples side-by-side to avoid implying a Windows-first approach.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/event-hubs-service-endpoints.md
...n//articles/event-hubs/event-hubs-service-endpoints.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While it covers Azure Portal and Resource Manager templates (which are cross-platform), the command-line automation sections mention Azure CLI and Azure PowerShell, but only the PowerShell section provides explicit command examples. There are no Linux-specific or Bash examples, and PowerShell is traditionally associated with Windows. The Azure CLI section is brief and lacks parity in example depth. No Linux tools or patterns are mentioned, and PowerShell is presented after CLI but with more detail.
Recommendations
- Provide explicit Azure CLI command examples for all operations described in the PowerShell section, ensuring parity in detail and clarity.
- Include Bash shell script examples for common tasks, or at least show how Azure CLI can be used in a Linux/macOS environment.
- Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, to avoid the impression that PowerShell is the primary or preferred automation tool.
- Where possible, add notes or links to Linux-specific guidance or troubleshooting for networking and firewall configuration.
- Ensure that screenshots and UI instructions do not assume a Windows environment (e.g., avoid showing Windows-specific UI elements if not necessary).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/private-link-service.md
...blob/main//articles/event-hubs/private-link-service.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for CLI-based configuration, omitting equivalent Azure CLI (cross-platform) or Bash scripts. The validation steps explicitly instruct users to create a Windows VM and connect via Windows command line, with no mention of Linux VMs or shell usage. All automation and scripting guidance is Windows-centric, and Windows tools (PowerShell, Windows VM) are mentioned exclusively or before any Linux alternatives.
Recommendations
- Provide equivalent Azure CLI (az) and/or Bash script examples alongside PowerShell for all resource creation and configuration steps.
- Include instructions for creating and validating with a Linux virtual machine, or at least mention that the steps are applicable to both Windows and Linux VMs.
- When demonstrating command-line validation (e.g., nslookup), show the command and expected output for both Windows Command Prompt/PowerShell and Linux shell environments.
- Avoid assuming the user is on Windows; use neutral language such as 'create a virtual machine' and specify both Windows and Linux options.
- Reference cross-platform tools and patterns (e.g., Azure CLI, Bash, SSH) before or alongside Windows-specific tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/test-locally-with-event-hub-emulator.md
...les/event-hubs/test-locally-with-event-hub-emulator.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by presenting Windows and PowerShell instructions before Linux/macOS equivalents, referencing Windows-specific tools (WSL, PowerShell), and providing more detailed step-by-step instructions for Windows users. Linux and macOS instructions are less detailed and sometimes only mentioned after the Windows steps. There are also notes and path conventions specific to Windows, with less emphasis on Linux-native workflows.
Recommendations
- Present Linux/macOS instructions alongside or before Windows instructions, or use parallel tabbed sections for each OS.
- Provide equally detailed, step-by-step instructions for Linux and macOS users, including terminal commands for navigation and script execution.
- Avoid assuming PowerShell or WSL as the default shell; provide native Linux/macOS shell examples.
- When referencing Docker Desktop, link to both Windows and Linux/macOS installation guides.
- Clarify file path conventions for all platforms, not just Windows.
- Include troubleshooting or environment setup notes relevant to Linux/macOS users (e.g., permissions, Docker group membership).
- Where scripts or tools are cross-platform, highlight this explicitly and show usage in both environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/transport-layer-security-configure-client-version.md
...s/transport-layer-security-configure-client-version.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides only a .NET example, which is most commonly used on Windows, and recommends Fiddlerβa Windows-centric toolβfor verifying TLS versions. There are no examples for Linux-based client environments or alternative verification tools, and Windows tools are mentioned before any cross-platform or Linux equivalents.
Recommendations
- Include examples for configuring TLS in common Linux environments, such as using Python, Java, or Node.js clients.
- Suggest cross-platform or Linux-native tools for verifying TLS versions, such as Wireshark, tcpdump, or OpenSSL s_client.
- Present verification tools in a platform-neutral way, mentioning both Windows and Linux options.
- Clarify that .NET Core and .NET 5+ are cross-platform and provide guidance for Linux users if .NET is to be used.
- Add explicit instructions or references for Linux users to ensure parity and inclusivity.