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 1301-1325 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/troubleshooting-guide.md
...lob/main//articles/event-hubs/troubleshooting-guide.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. The primary troubleshooting command for checking dropped packets uses the Windows-only 'psping.exe' tool and provides a PowerShell/Windows command-line example, with only a vague mention of 'equivalent commands' for other tools. There are no concrete Linux or cross-platform command examples (e.g., using 'nc', 'telnet', or 'curl'), and the download link for 'psping' points to a Microsoft Sysinternals page, which is Windows-specific. The structure and order of examples and tool recommendations prioritize Windows users and tools.
Recommendations
- Provide explicit Linux/macOS equivalents for all troubleshooting commands, such as using 'nc', 'telnet', or 'curl' to test TCP connectivity.
- Include both Windows and Linux command examples side by side, or use cross-platform tools where possible.
- Avoid referencing Windows-only tools (like 'psping.exe') as the primary or only example; if mentioned, always pair with a Linux alternative.
- Clarify instructions for obtaining and running tools on non-Windows platforms.
- Consider using more platform-neutral language and tool recommendations throughout the documentation.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-hubs/schema-registry-dotnet-send-receive-quickstart.md
...hubs/schema-registry-dotnet-send-receive-quickstart.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a clear Windows bias by exclusively referencing Microsoft Visual Studio as the development environment, using only Windows-specific tooling (such as the Visual Studio UI and Package Manager Console), and omitting any instructions or examples for Linux or cross-platform development. There are no command-line instructions for .NET CLI or guidance for using editors like VS Code, nor are there any Linux-specific setup or authentication steps. All package installation and project creation steps are described in terms of Visual Studio's GUI and Windows-centric workflows.
Recommendations
- Add parallel instructions for Linux and macOS users, including how to use the .NET CLI (e.g., `dotnet new console`, `dotnet add package ...`) for project creation and package management.
- Include examples for using cross-platform editors such as Visual Studio Code, and provide guidance for authentication methods that work outside Visual Studio (e.g., Azure CLI, environment variables).
- Explicitly state that the quickstart works on Windows, Linux, and macOS, and provide any platform-specific prerequisites or troubleshooting steps.
- Replace or supplement screenshots and step-by-step instructions that are Visual Studio-specific with equivalent command-line or VS Code workflows.
- Ensure that all code generation and build steps are described in a way that is not dependent on Windows-only tools or interfaces.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-for-cloud-solution-providers.md
...ressroute/expressroute-for-cloud-solution-providers.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias by referencing Windows-centric tools and documentation (such as linking to a 'previous-versions/windows' API page), mentioning PowerShell for configuration tasks without providing Linux/CLI equivalents, and omitting Linux-specific guidance or examples for ExpressRoute management and configuration. There are no explicit Linux or cross-platform command-line examples, and the only scripting/configuration reference is to PowerShell.
Recommendations
- Provide Azure CLI and/or REST API examples alongside or instead of PowerShell for all configuration and management tasks, ensuring parity for Linux and macOS users.
- Replace or supplement Windows-specific documentation links (such as those under 'previous-versions/windows') with platform-neutral or cross-platform Azure documentation.
- Explicitly mention that all configuration steps can be performed from Linux, macOS, or Windows, and provide sample commands or scripts for each where appropriate.
- Where PowerShell is referenced, add equivalent Azure CLI or Bash script examples to ensure Linux users are not excluded.
- Audit all referenced tools and workflows to ensure they are accessible and documented for non-Windows environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-howto-add-ipv6-portal.md
...les/expressroute/expressroute-howto-add-ipv6-portal.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 commands for gateway configuration, explicitly instructing users to use PowerShell for certain steps, and omitting equivalent instructions for Linux users (such as Azure CLI or Bash). There are no Linux or cross-platform command-line examples, and the PowerShell approach is presented as the default or only supported method for some tasks.
Recommendations
- Provide Azure CLI (az) command examples alongside PowerShell for all configuration steps, especially for gateway management.
- Clearly indicate when a step can be performed using the Azure CLI or Bash on Linux/macOS, and provide those instructions.
- If certain features are only available via PowerShell, explicitly state this limitation and provide guidance for Linux users (e.g., using Azure Cloud Shell, which supports both PowerShell and Bash).
- Review the documentation to ensure that tool-agnostic or cross-platform approaches are presented first, or at least in parallel with Windows-specific instructions.
- Add a section or note summarizing cross-platform support and linking to relevant Azure CLI documentation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-erdirect-about.md
...//articles/expressroute/expressroute-erdirect-about.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by providing only Azure PowerShell command examples for onboarding, with no equivalent Azure CLI (cross-platform) or Bash examples. This implicitly prioritizes Windows tooling and patterns, potentially excluding Linux/macOS users or those who prefer CLI-based workflows.
Recommendations
- Provide Azure CLI (az) command examples alongside PowerShell for all onboarding and management steps.
- Explicitly mention that both PowerShell and CLI can be used, and link to relevant cross-platform setup guides.
- Where possible, include Bash shell examples for common tasks to ensure Linux parity.
- Review other sections for subtle Windows-centric language or assumptions, and ensure documentation is inclusive of all platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-howto-coexist-classic.md
...les/expressroute/expressroute-howto-coexist-classic.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation exclusively uses Azure PowerShell cmdlets for all configuration steps, with no mention of Linux, Bash, or cross-platform alternatives such as Azure CLI. All example commands use Windows-style file paths (e.g., C:\NetworkConfig.xml), and there are no instructions or examples for users on Linux or macOS. The installation instructions and tooling references are Windows-centric, and there is no parity in guidance for non-Windows environments.
Recommendations
- Provide equivalent Azure CLI examples for all configuration steps, as Azure CLI is cross-platform and works on Windows, Linux, and macOS.
- Include Linux/macOS file path examples alongside Windows paths (e.g., /home/user/NetworkConfig.xml).
- Add a section or callouts for users on Linux/macOS, including any prerequisites or differences in workflow.
- Where PowerShell is required due to classic model limitations, explicitly state this and suggest using PowerShell Core (pwsh), which is available cross-platform, with installation guidance for Linux/macOS.
- Review and update all tooling references to clarify platform compatibility and provide links to cross-platform installation guides.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-faqs.md
.../blob/main//articles/expressroute/expressroute-faqs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is mentioned as a primary automation/configuration tool (e.g., for changing bandwidth, enabling/disabling premium features, configuring route filters), and there are no explicit Linux or cross-platform CLI examples. When automation or scripting is referenced, PowerShell is listed before or instead of Azure CLI, and Linux-native tools or workflows are not mentioned. There are no Linux-specific instructions or examples, and the documentation assumes familiarity with Windows-centric tools.
Recommendations
- For every PowerShell example or mention, provide an equivalent Azure CLI example, as Azure CLI is cross-platform and widely used on Linux.
- When listing automation options (e.g., 'You can update the bandwidth using the Azure portal, REST API, PowerShell, or Azure CLI'), ensure Azure CLI is listed before or alongside PowerShell.
- Add explicit Linux-focused guidance or notes where relevant, such as how to perform tasks from a Linux shell or using Linux-native tools.
- Where screenshots or UI walkthroughs are provided, ensure they are not Windows-specific or supplement with Linux/macOS equivalents if relevant.
- Review and update links or references to ensure they do not assume a Windows environment (e.g., avoid only linking to PowerShell-specific guides).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/gateway-migration-error-messaging.md
...cles/expressroute/gateway-migration-error-messaging.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell migration instructions as the only command-line automation option in the 'Next steps' section, without mentioning Azure CLI or Bash/Linux alternatives. There are no Linux-specific examples, and the PowerShell path is presented before any cross-platform or Linux-native tooling, which may exclude or inconvenience Linux users.
Recommendations
- Add explicit Azure CLI (az) migration instructions and links alongside PowerShell instructions in the 'Next steps' section.
- Include Linux/Bash command examples where resource operations (GET/SET, etc.) are discussed, not just PowerShell.
- Ensure that all automation and scripting guidance is presented in a cross-platform manner, or at least gives equal prominence to Linux and Windows options.
- Where possible, clarify that Azure CLI and PowerShell are both supported, and link to both sets of documentation.
- Consider including a table or section comparing PowerShell and Azure CLI commands for common migration tasks.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/firewall/explicit-proxy.md
...re-docs/blob/main//articles/firewall/explicit-proxy.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page references Azure PowerShell for deployment instructions in the 'Next steps' section, without mentioning or linking to equivalent Linux-friendly tools such as Azure CLI or ARM templates. There are no examples or instructions tailored for Linux users, and the only deployment guidance provided is Windows-centric.
Recommendations
- Include links and examples for deploying and configuring Azure Firewall using Azure CLI, which is cross-platform and widely used on Linux.
- Mention ARM/Bicep template deployment options for platform-neutral automation.
- When referencing PowerShell, clarify that Azure CLI and other tools are also supported, and provide parallel instructions or links.
- Ensure that screenshots and UI instructions are not specific to Windows environments unless unavoidable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-howto-add-gateway-portal-resource-manager.md
...expressroute-howto-add-gateway-portal-resource-manager.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows and PowerShell-based workflows. The navigation selector at the top offers 'Azure portal', 'PowerShell', and 'Classic PowerShell' options, with no mention of Azure CLI or Bash/Linux equivalents. Instructions and important notes reference PowerShell for advanced configuration (e.g., IPv6 setup), and there are no examples or guidance for users on Linux or macOS platforms. The absence of Azure CLI commands or cross-platform scripting options limits accessibility for non-Windows users.
Recommendations
- Add Azure CLI examples and instructions alongside or before PowerShell examples, especially for advanced tasks such as IPv6 configuration.
- Update the navigation selector to include 'Resource Manager - Azure CLI' and link to a corresponding guide.
- Ensure all command-line instructions are provided in both PowerShell and Azure CLI formats, with clear indications of platform compatibility.
- Where screenshots or UI steps are provided, include notes or links for users who prefer or require command-line interfaces on Linux/macOS.
- Review and update any references to Windows-specific tools or terminology to use cross-platform language where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-howto-expressroute-direct-cli.md
...essroute/expressroute-howto-expressroute-direct-cli.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exhibits Windows bias primarily in the 'Before you begin' section, where only Azure PowerShell commands are provided for subscription enrollment and provider registration, with no equivalent Azure CLI or Linux/macOS instructions. Additionally, file path examples (e.g., for LOA download) use Windows-style paths (C:\Users\...), and there is no mention of Linux or cross-platform alternatives for these operations. The documentation assumes a Windows environment for initial setup and file management, which may hinder Linux or macOS users.
Recommendations
- Provide Azure CLI equivalents for all PowerShell commands, especially for subscription enrollment and provider registration, and clarify that these can be run on any platform.
- When showing file paths (e.g., for LOA download), include both Windows (C:\Users\...) and Linux/macOS (~/Downloads/...) examples, or use a platform-agnostic placeholder.
- Explicitly state that all Azure CLI commands are cross-platform and can be run on Windows, Linux, or macOS.
- If certain steps must be performed in PowerShell, explain why and offer guidance for non-Windows users (e.g., using Azure Cloud Shell or installing PowerShell Core on Linux/macOS).
- Review all examples and notes to ensure Linux parity and avoid assuming a Windows environment by default.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-howto-circuit-resource-manager-template.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-howto-circuit-resource-manager-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows/Powershell bias. The primary example for deploying an ExpressRoute circuit via an ARM template is provided exclusively in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash example. Instructions and workflow steps are written for PowerShell users, and the 'Try it' and copy-paste instructions are tailored to the PowerShell experience. While there is a brief mention of Azure CLI and REST API as alternative deployment methods, no concrete CLI or Bash examples are given, and the PowerShell approach is presented first and in detail.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell scripts, including parameter prompts and deployment commands.
- Include Bash shell instructions for Linux/macOS users, especially for steps like copying and pasting commands.
- Present CLI and PowerShell examples side-by-side or in tabs, so users can easily select their preferred environment.
- Avoid language that assumes the user is on Windows or using PowerShell (e.g., 'Right-click the shell console').
- Ensure that all steps (creation, deletion, etc.) have both PowerShell and CLI/Bash code blocks.
- Explicitly state that Azure CLI is cross-platform and supported on Windows, Linux, and macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-troubleshooting-arp-resource-manager.md
...e/expressroute-troubleshooting-arp-resource-manager.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively provides PowerShell-based instructions and cmdlets for retrieving ARP tables, with no mention of Linux, Bash, Azure CLI, or cross-platform alternatives. All examples and prerequisites assume the use of PowerShell, which is traditionally associated with Windows environments, and there is no guidance for users on Linux or macOS systems.
Recommendations
- Add equivalent Azure CLI (az) commands for retrieving ARP tables, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash script examples or instructions for users working in Linux environments.
- Explicitly mention that PowerShell Core is available cross-platform, and provide installation guidance for non-Windows users if PowerShell must be used.
- Reorganize the page or selector to offer both PowerShell and Azure CLI/Bash options, ensuring Linux users are not excluded.
- Update prerequisites to mention both PowerShell and Azure CLI as supported tools for this operation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-migration-classic-resource-manager.md
...ute/expressroute-migration-classic-resource-manager.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples and instructions, with no mention of Azure CLI or Bash alternatives. All code snippets and migration steps are shown using PowerShell cmdlets, which are most familiar to Windows users. There is no guidance for users on Linux or macOS, nor are cross-platform tools or commands referenced. The prerequisite steps also focus on installing and configuring Azure PowerShell, reinforcing the Windows-centric approach.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell snippets, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include a section or note clarifying that all steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.
- Where possible, use neutral, cross-platform language (e.g., 'Azure CLI or PowerShell') in instructions and prerequisites.
- Mention how to install and use Azure CLI alongside or instead of Azure PowerShell.
- Review all referenced links and ensure they do not default to Windows-specific content or tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-howto-macsec.md
...in//articles/expressroute/expressroute-howto-macsec.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses Azure PowerShell cmdlets for all configuration steps, with no mention of Azure CLI, Bash, or cross-platform alternatives. All examples and prerequisites assume the use of PowerShell, which is traditionally associated with Windows environments, and there is no guidance for Linux or macOS users. The document also references installing PowerShell modules and does not provide parity for users who might prefer or require Linux-native tools.
Recommendations
- Provide equivalent Azure CLI (az) command examples for all PowerShell cmdlets, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI or PowerShell Core, and provide instructions for those environments.
- Include a section or notes for Linux users, such as how to install and use Azure CLI or PowerShell Core on Linux.
- Avoid assuming PowerShell as the default tool; present both PowerShell and CLI examples side by side or allow users to select their preferred environment.
- Clarify any platform-specific limitations or differences, if any, for Linux/macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-prerequisites.md
...n//articles/expressroute/expressroute-prerequisites.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 Azure PowerShell commands as a prerequisite for ExpressRoute Direct enrollment, without mentioning Azure CLI or providing Linux/macOS alternatives. There are no examples or instructions for Linux users, and the only command-line tooling referenced is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Include Azure CLI commands alongside or before Azure PowerShell commands, especially for enrollment and configuration steps.
- Explicitly mention that Azure CLI is cross-platform and provide Linux/macOS instructions where relevant.
- Add examples or links to documentation for performing ExpressRoute-related tasks using Azure CLI or REST API.
- Review all procedural steps to ensure parity between Windows and Linux/macOS users, avoiding assumptions that users are on Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-troubleshooting-arp-classic.md
...pressroute/expressroute-troubleshooting-arp-classic.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased toward Windows environments, exclusively providing PowerShell cmdlets and referencing the Windows PowerShell module for Azure. There are no instructions or examples for Linux or cross-platform CLI tools (such as Azure CLI), nor are any Linux-native commands or workflows mentioned. The prerequisites and all troubleshooting steps assume the use of Windows and PowerShell, with no mention of alternatives for Linux users.
Recommendations
- Add equivalent instructions and examples using Azure CLI (az), which is cross-platform and works on both Linux and Windows.
- Include sample commands for retrieving ARP tables or relevant ExpressRoute information from Linux environments.
- Mention the availability of Azure CLI and how to install it on Linux, as an alternative to the Windows PowerShell module.
- Rephrase prerequisites and steps to be platform-neutral, or provide parallel sections for Windows/PowerShell and Linux/Azure CLI.
- If certain functionality is only available via PowerShell, explicitly state this limitation and provide any possible workarounds for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-troubleshooting-network-performance.md
...te/expressroute-troubleshooting-network-performance.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 throughout. All example commands, including installation and usage of the Azure Connectivity Toolkit (AzureCT), are provided exclusively in PowerShell, with no Linux shell or cross-platform alternatives. The toolkit itself is a PowerShell module, and instructions for installing supporting tools (iPerf, PSPing) and configuring firewall rules are Windows-centric. The test environment and reference results are based on Windows Server, and there is no guidance for running equivalent tests or setup on Linux hosts. Linux is only mentioned in passing (e.g., 'the other can be either Windows or Linux'), but no practical Linux instructions or examples are provided.
Recommendations
- Provide equivalent Linux shell (bash) examples for all PowerShell commands, including installing and running iPerf and collecting results.
- Document how to perform link performance tests using native Linux tools (e.g., iPerf, netcat, traceroute) without requiring AzureCT or PowerShell.
- Include instructions for configuring Linux firewalls (e.g., ufw, firewalld, iptables) to allow necessary test traffic.
- Offer sample test scenarios where both endpoints are Linux, or where the local or remote host is Linux.
- Clarify any limitations or differences in test methodology or results when using Linux versus Windows.
- If AzureCT is not available for Linux, recommend open-source or cross-platform alternatives and provide usage guidance.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-howto-erdirect.md
...//articles/expressroute/expressroute-howto-erdirect.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All command-line examples use Azure PowerShell cmdlets, and file paths are shown in Windows format (e.g., C:\Users\SampleUser\Downloads) before mentioning Linux/Cloud Shell equivalents. There are no examples using Azure CLI, Bash, or native Linux tools, and the workflow assumes familiarity with Windows conventions and PowerShell scripting.
Recommendations
- Provide equivalent Azure CLI (az) command examples for each PowerShell command, as Azure CLI is cross-platform and commonly used on Linux and macOS.
- Include Bash shell script examples and Linux file path conventions (e.g., /home/user/Downloads) alongside or before Windows paths.
- Clearly indicate when a command or feature is only available in PowerShell, and suggest alternatives for Linux users where possible.
- Add a section or callout at the beginning clarifying that all steps can be performed from Azure Cloud Shell (which supports both Bash and PowerShell), and provide explicit instructions for both environments.
- Where file downloads or manipulations are discussed, show both Windows and Linux/MacOS methods for accessing or handling those files.
- Avoid using Windows-specific terminology or tools (such as referencing only PowerShell or C:\ paths) without also providing Linux/MacOS equivalents.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/gateway-migration.md
.../blob/main//articles/expressroute/gateway-migration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by providing migration instructions and advanced configuration steps (such as adding multiple prefixes to the GatewaySubnet) exclusively via PowerShell, with no mention of Azure CLI, Bash, or Linux-native tooling. There are no Linux/Unix command examples or guidance, and PowerShell is presented as the only scripting interface for key operations.
Recommendations
- Provide equivalent Azure CLI (az) command examples and migration guides alongside PowerShell instructions, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention support for Linux/macOS environments where applicable, and clarify if any features are PowerShell-only.
- For steps currently only available in PowerShell (such as adding multiple prefixes), note the limitation and provide a timeline or workaround for Linux users.
- Ensure that documentation navigation and 'Next Steps' sections offer both PowerShell and Azure CLI (or REST API) options equally, not just PowerShell.
- Include Bash script examples or references for common administrative tasks where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/how-to-configure-connection-monitor.md
...es/expressroute/how-to-configure-connection-monitor.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell scripts and automation for Windows users, while Linux instructions are manual and less automated. Windows tools and patterns (such as PowerShell scripts and Control Panel references) are mentioned first and in more detail, with Linux steps often relegated to manual file edits. There is a lack of parity in automation and troubleshooting guidance for Linux users.
Recommendations
- Provide equivalent Bash or shell scripts for Linux users to automate tasks such as opening firewall ports, similar to the provided PowerShell script for Windows.
- Present Windows and Linux instructions in parallel, rather than listing Windows steps first and Linux as an afterthought.
- Include Linux-specific troubleshooting steps and verification commands, not just references to Windows Control Panel.
- Where possible, use cross-platform tools or Azure CLI examples instead of (or in addition to) PowerShell.
- Ensure all automation and configuration steps are equally covered for both platforms, including registry or configuration file changes.
- Add screenshots or command outputs for Linux steps, similar to those shown for Windows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/how-to-custom-route-alert.md
...in//articles/expressroute/how-to-custom-route-alert.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell environments. All automation and scripting examples are provided exclusively in PowerShell, with no mention of Bash, Azure CLI, or cross-platform alternatives. The workflow assumes familiarity with Azure PowerShell and does not acknowledge or provide guidance for users on Linux or macOS. The use of PowerShell-specific modules and cmdlets, as well as references to 'runbooks with PowerShell scripts,' further reinforces a Windows-centric approach. There are no examples or instructions for achieving the same functionality using Linux-native tools or scripting languages.
Recommendations
- Provide equivalent examples using Azure CLI (az) commands and Bash scripts, which are cross-platform and widely used on Linux and macOS.
- Explicitly mention that Azure Automation supports Python runbooks and provide a sample Python script for the same monitoring task.
- Add a section or callout for Linux/macOS users, outlining how to set up and run the monitoring workflow using non-Windows tools.
- Where PowerShell is required, clarify that PowerShell Core (pwsh) is available cross-platform, and provide installation instructions for Linux/macOS.
- Ensure that any references to tools or modules (e.g., Az PowerShell modules) are accompanied by their Azure CLI or REST API equivalents.
- Consider reordering sections or providing parallel instructions so that Linux and cross-platform options are not treated as an afterthought.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/expressroute-howto-routing-classic.md
...les/expressroute/expressroute-howto-routing-classic.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively uses PowerShell cmdlets for all configuration, management, and viewing tasks related to ExpressRoute peering. There are no examples or instructions for Linux users, such as Azure CLI or Bash scripts, nor is there mention of cross-platform tools. The prerequisite section also refers only to installing PowerShell modules, reinforcing a Windows-centric approach.
Recommendations
- Add equivalent Azure CLI examples for each PowerShell cmdlet shown, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include a section or callout at the start clarifying which tools are supported on which platforms, and link to installation instructions for Azure CLI on Linux.
- Where possible, provide Bash script examples alongside PowerShell, or at least reference how Linux/macOS users can accomplish the same tasks.
- Review and update the 'Download the latest PowerShell cmdlets' section to also mention Azure CLI installation and usage.
- Ensure that future documentation for Azure networking features provides parity between Windows/PowerShell and Linux/Azure CLI workflows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/planned-maintenance.md
...lob/main//articles/expressroute/planned-maintenance.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell (Get-AzExpressRouteCircuitStats) examples for monitoring traffic statistics during failover validation, without mentioning or providing equivalent Linux/CLI commands. There is no guidance for Linux users or those using cross-platform tools, and the only tool-specific example is Windows-centric.
Recommendations
- Include equivalent Azure CLI commands (e.g., 'az network express-route ...') alongside PowerShell examples for all monitoring and validation steps.
- Explicitly mention that monitoring and failover validation can be performed from Linux/macOS environments using Azure CLI or REST API.
- Provide sample scripts or command lines for both Windows (PowerShell) and Linux (Bash/Azure CLI) users.
- Add a table or section comparing available tools for ExpressRoute management across platforms (PowerShell, Azure CLI, REST API), with links to relevant documentation.
- Avoid referencing only Windows-specific tools when cross-platform alternatives exist.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/expressroute/quickstart-create-expressroute-vnet-template.md
...sroute/quickstart-create-expressroute-vnet-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a strong Windows bias by providing only Azure PowerShell examples for deploying the ARM template, with no equivalent Azure CLI (cross-platform) or Bash examples. The instructions and screenshots focus on PowerShell usage, which is more familiar to Windows users. While the Azure Cloud Shell is mentioned (which can run on any OS), the provided script is PowerShell-specific, and there is no mention of Bash or CLI alternatives. The 'Remove-AzResourceGroup' cmdlet is also used for cleanup, again with no CLI or Bash equivalent. Although the page briefly mentions that Azure CLI and REST API can be used, it does not provide any examples or guidance for those methods.
Recommendations
- Add equivalent Azure CLI (az) examples for all deployment and cleanup steps, ideally in Bash syntax.
- Present both PowerShell and CLI examples side-by-side or allow the user to select their preferred shell.
- Ensure screenshots and instructions are not PowerShell-specific, or provide alternatives for Linux/macOS users.
- Explicitly mention that Cloud Shell supports both Bash and PowerShell, and show how to select the shell.
- Where possible, avoid using Windows-specific terminology or tools as the default or only option.