Expressroute
113
Total Pages
61
Linux-Friendly Pages
52
Pages with Bias
46.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
281 issues found
Showing 126-150 of 281 flagged pages
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/circuit-placement-api.md
...ob/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, without offering equivalent Azure CLI (cross-platform) or Bash examples. The initial steps for provider registration use PowerShell cmdlets exclusively, which may disadvantage Linux or macOS users. The remainder of the documentation uses REST API examples, which are platform-neutral.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell commands, especially for subscription registration and provider feature registration steps.
- Explicitly mention that both Azure PowerShell and Azure CLI can be used, and provide guidance for users on Linux/macOS.
- Where possible, provide Bash shell examples for REST API calls (e.g., using curl) to demonstrate cross-platform usage.
- Review introductory sections to ensure that Windows tools or patterns are not presented as the default or only option.
Create Pull Request
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/how-to-custom-route-alert.md
...ain/articles/expressroute/how-to-custom-route-alert.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation exclusively uses PowerShell scripts and cmdlets for automation, with no mention of Bash, Azure CLI, or cross-platform scripting alternatives. All automation examples and instructions are based on PowerShell, which is more commonly associated with Windows environments, and there is no guidance for users who may be working from Linux or macOS systems. The documentation also references Windows-centric tools and patterns (e.g., PowerShell runbooks) without acknowledging or providing parity for Linux-native approaches.
Recommendations
- Provide equivalent examples using Azure CLI (az) commands and Bash scripts for automation tasks, alongside PowerShell.
- Explicitly state that Azure Automation supports Python runbooks and provide a sample Python script for the same monitoring workflow.
- Clarify whether the PowerShell scripts and modules used are compatible with PowerShell Core on Linux/macOS, and if so, provide installation and usage guidance for those platforms.
- Include a section or note for Linux/macOS users, outlining any differences or additional steps required to achieve the same result.
- Where possible, use cross-platform tools and language in instructions (e.g., refer to 'terminal' instead of 'PowerShell console', and avoid assuming a Windows environment).
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-howto-set-global-reach.md
...es/expressroute/expressroute-howto-set-global-reach.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation exclusively uses Azure PowerShell cmdlets for all configuration, verification, and management steps, with no mention of Azure CLI, Bash, or cross-platform alternatives. All code examples and instructions assume the use of PowerShell, which is traditionally associated with Windows environments, and there is no guidance for users on Linux or macOS platforms.
Recommendations
- Provide equivalent Azure CLI (az) command examples for each PowerShell example, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Add a section or notes explaining how to perform these tasks in Bash or from the Azure Cloud Shell using Bash.
- Clarify that Azure PowerShell can be used on Linux/macOS, but still offer CLI alternatives for users who prefer native tools.
- Ensure that prerequisites and setup instructions include both Azure PowerShell and Azure CLI installation and authentication steps.
- Review all references to PowerShell to ensure they are balanced with cross-platform alternatives, and update headings/sections to reflect multi-platform support.
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-erdirect-about.md
...n/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 commands for onboarding to ExpressRoute Direct, with no equivalent Azure CLI (cross-platform) or Bash examples. This assumes a Windows or PowerShell-centric workflow, potentially excluding Linux and macOS users. No mention is made of Linux-native tools or alternative onboarding methods.
Recommendations
- Add equivalent Azure CLI (az) command examples alongside PowerShell for all onboarding and management steps.
- Explicitly state that both Windows and Linux/macOS users can manage ExpressRoute Direct, and provide guidance for each platform.
- Where possible, include Bash shell examples for common tasks.
- Avoid referencing only Windows-specific tools or workflows; ensure parity in instructions and tooling.
- Consider a 'Choose your platform' section at the start of procedural steps, linking to both PowerShell and CLI/Bash instructions.
Expressroute
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 demonstrates a Windows bias by referencing Windows-specific management APIs (with a link to a Windows documentation page), mentioning PowerShell as the only example for ExpressRoute routing configuration, and omitting any Linux or cross-platform command-line examples or tools. There are no references to Linux-native tools or Azure CLI, and no examples are provided for Linux users.
Recommendations
- Include Azure CLI examples alongside or instead of PowerShell for configuration tasks, such as creating and modifying ExpressRoute circuits and routing filters.
- Reference cross-platform management APIs and documentation, not just Windows-specific endpoints.
- Explicitly mention that management and configuration can be performed from Linux, macOS, and Windows, and provide relevant examples.
- Add links to Linux and cross-platform tooling documentation (e.g., Azure CLI, REST API usage) for ExpressRoute.
- Ensure that all procedural steps and code snippets are platform-agnostic or have both Windows and Linux variants.
Expressroute
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
Summary
The documentation exhibits a Windows bias primarily in the 'Before you begin' section, where only Azure PowerShell commands are provided for the required subscription enrollment step, with no equivalent Azure CLI or cross-platform instructions. Additionally, file path examples (e.g., C:\Users\SampleUser\Downloads\LOA.pdf) use Windows conventions without mentioning Linux alternatives. The initial enrollment step is Windows-first and lacks Linux parity, potentially blocking Linux/macOS users from following the guide end-to-end.
Recommendations
- Provide Azure CLI equivalents for all PowerShell commands, especially for the subscription enrollment step, or clarify if the step is only possible in PowerShell.
- Include Linux/macOS file path examples (e.g., ~/Downloads/LOA.pdf) alongside Windows paths when specifying output destinations.
- Add notes or links for cross-platform users on how to accomplish prerequisite steps using CLI or REST if PowerShell is unavoidable.
- Review all examples and ensure that none assume a Windows environment by default; offer parity for Linux/macOS users throughout.
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/about-upgrade-circuit-bandwidth.md
...ticles/expressroute/about-upgrade-circuit-bandwidth.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as a primary method for upgrading circuit bandwidth, and mentioning it before Azure CLI. There are no explicit Linux or cross-platform command-line examples, and the documentation does not clarify that Azure CLI is cross-platform or provide Bash/Linux shell examples.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Provide example commands for both PowerShell and Bash (using Azure CLI) to ensure Linux users are equally supported.
- List Azure CLI before PowerShell to avoid the impression that Windows tools are preferred.
- Add a note or section highlighting Linux/macOS compatibility and any OS-specific considerations.
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-about-virtual-network-gateways.md
...ssroute/expressroute-about-virtual-network-gateways.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 gateway subnet creation, referencing PowerShell and REST API resources exclusively, and omitting any Azure CLI (cross-platform) or Linux-native command examples. The focus on PowerShell cmdlets and lack of parity with CLI or Bash scripting may disadvantage Linux and macOS users.
Recommendations
- Add Azure CLI examples alongside PowerShell for all command-line operations, especially for gateway subnet creation.
- Include references and links to Azure CLI documentation and syntax in the 'REST APIs and PowerShell cmdlets' section.
- Explicitly mention that all operations can be performed from Linux, macOS, or Windows using Azure CLI.
- Where possible, provide Bash script equivalents for common tasks.
- Reorder examples or provide both PowerShell and CLI examples together, rather than PowerShell only or first.
Expressroute
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 is heavily biased towards Windows and PowerShell usage. All step-by-step examples and code blocks use Azure PowerShell exclusively, with no equivalent Azure CLI (cross-platform) or Bash examples provided inline. The instructions and workflow assume the use of PowerShell, which is traditionally associated with Windows, and there is no mention of Linux or macOS-specific guidance. While links to Azure CLI and REST API deployment methods are provided, they are secondary and not integrated into the main instructional flow.
Recommendations
- Provide parallel Azure CLI (az) examples alongside PowerShell scripts for all deployment and deletion steps.
- Include explicit instructions or code blocks for Bash/shell environments to ensure Linux and macOS users are equally supported.
- Reorganize the documentation to present both PowerShell and CLI methods equally, or allow users to select their preferred environment at the top of the page.
- Clarify that Azure Cloud Shell supports both PowerShell and Bash, and show how to choose between them.
- Avoid language that assumes the user is on Windows or using PowerShell by default; instead, use neutral, cross-platform phrasing.
Expressroute
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, referencing Windows-specific tools (such as Control Panel and Windows Firewall), and presenting Windows procedures and scripts before or more prominently than Linux equivalents. Linux instructions are present but are less automated, require manual steps, and are less detailed. There are also references to Windows-specific verification steps without Linux parity.
Recommendations
- Provide equivalent automated scripts for Linux (e.g., a bash script to open firewall ports and configure the agent, similar to the provided PowerShell script for Windows).
- Include Linux verification steps (such as commands to check agent status and connectivity) alongside the Windows Control Panel instructions.
- Present Windows and Linux instructions in parallel or in clearly separated, equally detailed sections to avoid the perception of Windows-first bias.
- Reference Linux tools and configuration files with the same level of detail as Windows tools (e.g., mention systemd, firewalld/iptables, and log file locations for Linux).
- Where possible, provide cross-platform CLI examples (such as using Azure CLI) instead of only PowerShell.
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/gateway-migration.md
...s/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 Windows bias by exclusively referencing PowerShell for command-line migration and subnet management tasks, with no mention of Azure CLI or Bash/Linux alternatives. All automation and scripting guidance is provided only via PowerShell, which is traditionally associated with Windows environments. There are no examples or instructions for Linux users or those preferring cross-platform tools.
Recommendations
- Provide Azure CLI (az) command examples alongside PowerShell for all migration and subnet management tasks.
- Explicitly mention that PowerShell can be used on Linux/macOS, or clarify if any steps are Windows-only.
- Include Bash or shell script equivalents where appropriate, or link to cross-platform documentation.
- Reorder guidance so that cross-platform tools (Azure CLI) are mentioned before or alongside PowerShell.
- Add a section or note for Linux/macOS users, outlining supported tools and any differences in procedure.
Expressroute
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
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased toward Windows and PowerShell usage. All configuration steps and code samples are provided exclusively using Azure PowerShell cmdlets, with explicit references to installing PowerShell modules and using Windows-style file paths (e.g., 'C:\NetworkConfig.xml'). There are no examples or instructions for performing these tasks using Azure CLI, Bash, or other cross-platform tools. The documentation does not mention or provide parity for Linux or macOS users, nor does it reference alternative tooling or scripting environments.
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.
- Include notes or sections for Linux/macOS users, such as how to install and use Azure CLI and where to store configuration files (e.g., using '/home/user/NetworkConfig.xml' paths).
- Where file paths are referenced, show both Windows and Linux/macOS path formats.
- Add a table or selector at the top of the article allowing users to choose between PowerShell and Azure CLI (or Bash) instructions.
- Explicitly state that the instructions are applicable on Windows, and provide links or guidance for users on other platforms.
- Review all referenced scripts and tools to ensure they are available and supported on non-Windows platforms.
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-troubleshooting-expressroute-overview.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-troubleshooting-expressroute-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by providing only Azure PowerShell command examples for all CLI-based verification and troubleshooting steps. There are no equivalent examples using Azure CLI (cross-platform) or Bash scripting. Additionally, the recommended network testing tool is PsPing, which is a Windows-only Sysinternals utility, with no mention of Linux alternatives. No Linux-native commands or tools are referenced, and the documentation does not address how Linux users can perform the same tasks.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside all PowerShell examples to ensure cross-platform usability.
- Include Linux-native network testing tools (such as hping3, nping, or standard ping/traceroute) as alternatives to PsPing for connectivity testing.
- Explicitly mention that all PowerShell commands can be run in Azure Cloud Shell, which is available on all platforms, but also show Bash/Azure CLI syntax.
- Where possible, add troubleshooting steps or command examples that use common Linux networking tools (e.g., ip, ifconfig, arp, route, netstat) for validating ARP, BGP, and routing.
- Structure sections so that cross-platform or platform-neutral tools are presented first, or at least in parallel with Windows-specific tools.
Expressroute
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 is heavily biased towards Windows by exclusively using PowerShell cmdlets for all configuration, management, and viewing tasks. There are no examples or instructions for Linux users, such as Azure CLI or Bash equivalents. The only tooling mentioned is PowerShell, which is traditionally a Windows-centric tool, though it is now cross-platform. No Linux-native patterns or commands are provided.
Recommendations
- Add equivalent Azure CLI (az) command examples for each PowerShell cmdlet shown, as Azure CLI is cross-platform and commonly used on Linux.
- Include a section or callout for Linux/macOS users, clarifying how to perform these tasks without PowerShell.
- Where possible, provide Bash script examples or references to REST API usage for advanced users.
- Reorganize the documentation to present both PowerShell and Azure CLI options side-by-side, or allow users to select their preferred platform at the top of the article.
- Explicitly state that PowerShell Core is available on Linux/macOS, if PowerShell must be used, and provide installation instructions for those platforms.
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/site-to-site-vpn-over-microsoft-peering.md
...xpressroute/site-to-site-vpn-over-microsoft-peering.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for Azure-side configuration and validation, referencing the Azure portal (which is platform-agnostic but often used in Windows contexts), and omitting Azure CLI (cross-platform) or Bash examples. All device configuration examples are for Cisco IOS/CSR, with no Linux-based VPN device (e.g., strongSwan, libreswan) configuration or validation commands. The workflow and validation steps consistently present PowerShell commands first or exclusively, with no parity for Linux administrators.
Recommendations
- Add Azure CLI (az) command examples alongside all Azure PowerShell commands for resource creation, configuration, and validation.
- Include Linux-based VPN device configuration examples (e.g., strongSwan, libreswan) in addition to Cisco IOS/CSR examples, especially for on-premises device setup and tunnel validation.
- When referencing the Azure portal, clarify its cross-platform nature and provide CLI alternatives where possible.
- Present both PowerShell and CLI/Bash commands in parallel, or at least link to equivalent Linux/CLI documentation.
- Explicitly mention that all steps can be performed from Linux/macOS environments using Azure CLI, and provide references or links to those instructions.
- Add validation and troubleshooting steps using Linux-native tools (e.g., ipsec status, journalctl, tcpdump) for tunnel and BGP session checks.
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/use-s2s-vpn-as-backup-for-expressroute-privatepeering.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/use-s2s-vpn-as-backup-for-expressroute-privatepeering.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing all Azure-side command-line examples exclusively in PowerShell, with no Bash, Azure CLI, or Linux-native equivalents. Additionally, network validation and failover testing examples use Windows tools (tracert) and Windows-style command prompts, with no mention of Linux alternatives (e.g., traceroute). This prioritizes Windows environments and omits guidance for users on Linux or cross-platform systems.
Recommendations
- Provide Azure CLI (az) command equivalents for all PowerShell examples, especially for route validation and ExpressRoute circuit management.
- Include Linux-native command examples (e.g., traceroute instead of tracert) alongside Windows examples when demonstrating network validation from on-premises servers.
- Explicitly mention that the procedures can be performed from both Windows and Linux environments, and provide guidance or links for Linux users.
- Where screenshots or sample outputs are shown from Windows terminals, consider adding corresponding Linux/Bash terminal examples.
- Review the documentation for any other Windows-centric terminology or assumptions, and ensure Linux parity throughout.
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/about-upgrade-circuit-bandwidth.md
...ticles/expressroute/about-upgrade-circuit-bandwidth.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation lists PowerShell as a primary method for upgrading circuit bandwidth, and mentions it before Azure CLI, which is more cross-platform and Linux-friendly. There are no explicit Linux or Bash examples, and the focus on PowerShell may suggest a Windows-centric approach.
Recommendations
- Present Azure CLI examples before or alongside PowerShell, as Azure CLI is cross-platform and widely used on Linux.
- Include explicit Bash/Linux shell command examples where relevant, especially for common administrative tasks.
- Clarify that all operations can be performed from Linux, macOS, or Windows, and provide parity in step-by-step instructions for each platform.
- Avoid implying PowerShell is the default or preferred method unless there is a technical reason.
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/about-fastpath.md
...docs/blob/main/articles/expressroute/about-fastpath.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page references Azure PowerShell specifically as a configuration method for ExpressRoute FastPath, without mentioning or providing parity for Linux/CLI-based alternatives. The 'Next steps' section lists PowerShell before any cross-platform tools, and there are no explicit examples or guidance for Linux users (e.g., Azure CLI or Bash scripting). This creates a Windows-first impression and lacks Linux parity.
Recommendations
- Add explicit instructions and examples for configuring ExpressRoute FastPath using Azure CLI, which is cross-platform and commonly used on Linux.
- In the 'Next steps' section, list Azure CLI and PowerShell options together, or list CLI first to avoid Windows-first bias.
- Wherever PowerShell is mentioned, provide equivalent Bash or Azure CLI commands.
- Include notes or links for Linux/macOS users to ensure they can follow along without needing Windows-specific tools.
- Review all configuration steps and ensure that none are exclusive to Windows or PowerShell, and that Linux users are not left out.
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/circuit-placement-api.md
...ob/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, without offering equivalent Azure CLI or REST-based examples that are cross-platform. The initial setup steps assume the use of PowerShell, which is most commonly used on Windows, and there is no mention of Linux or macOS workflows. All other API interactions are shown as REST calls, which are platform-neutral, but the critical first step (provider registration) lacks Linux parity.
Recommendations
- Add Azure CLI examples for subscription registration and provider feature registration, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that the REST API and Azure CLI can be used from any OS, and provide equivalent commands for each step where possible.
- Consider reordering or presenting Azure CLI and REST examples before or alongside PowerShell to avoid the impression of Windows-first workflows.
- Include a note or section addressing cross-platform usage, clarifying that all API operations can be performed from Linux, macOS, or Windows.
Expressroute
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 towards Windows and PowerShell. All examples and instructions use Windows PowerShell cmdlets, and there is no mention of Linux or cross-platform alternatives. The prerequisites specifically require the Windows PowerShell module, and there are no Bash, Azure CLI, or Linux-native instructions or examples. This makes the documentation less accessible to users on Linux or macOS platforms.
Recommendations
- Provide equivalent instructions and examples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
- Include Bash shell examples for retrieving ARP tables or interacting with Azure resources.
- Mention and link to Linux/macOS installation guides for Azure CLI or other relevant tools.
- Clearly indicate which steps are Windows-specific and provide parity for non-Windows users.
- Review prerequisites to ensure they are not Windows-exclusive unless absolutely necessary, and offer alternatives where possible.
Expressroute
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 demonstrates a Windows bias by providing only Azure PowerShell examples for command-line configuration, with no mention of Azure CLI or Bash equivalents that are commonly used on Linux and macOS. The PowerShell steps are presented as the sole scripting option, and the documentation references Windows-centric tools and patterns without offering Linux alternatives or parity.
Recommendations
- Add equivalent Azure CLI (az) command examples alongside PowerShell for all configuration steps.
- Explicitly mention that the steps can be performed from any OS using Azure CLI or Cloud Shell, not just from Windows/PowerShell.
- Include Bash script examples or note cross-platform compatibility where possible.
- Reorder or present PowerShell and CLI steps in parallel, or provide a clear choice for users based on their platform.
- Review included content (INCLUDE files) to ensure Linux and cross-platform instructions are present.
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/cross-connections-api-development.md
...cles/expressroute/cross-connections-api-development.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively showing command-line examples using Windows file paths (e.g., C:\Users\...), and referencing the ARMClient tool as if it is being run from a Windows environment. There are no Linux or cross-platform shell examples, and no mention of Linux-compatible tools or usage patterns. The documentation assumes a Windows user context throughout, which may hinder Linux users.
Recommendations
- Provide equivalent Linux/macOS shell examples (e.g., using bash/zsh) alongside Windows command-line examples.
- Clarify whether ARMClient is available and supported on Linux/macOS, and provide installation and usage instructions for those platforms if so.
- Use platform-neutral file paths in documentation, or show both Windows and Linux path examples where relevant.
- Explicitly mention that the API can be accessed from any OS, and provide curl or HTTPie examples for REST API calls, which are available on all platforms.
- Avoid assuming a Windows user context in narrative or examples; strive for parity in tool recommendations and usage instructions.
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-about-virtual-network-gateways.md
...ssroute/expressroute-about-virtual-network-gateways.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 gateway subnet creation, referencing PowerShell cmdlets and REST APIs as primary configuration tools, and omitting equivalent Azure CLI (cross-platform) or ARM template examples. There are no Linux-native or cross-platform command examples, and PowerShell is presented as the default automation method.
Recommendations
- Add Azure CLI examples alongside PowerShell for all configuration steps, especially for gateway subnet creation.
- Include ARM template snippets or Bicep examples for users who prefer declarative infrastructure-as-code approaches.
- Explicitly mention that all operations can be performed from any OS using Azure CLI, not just Windows/PowerShell.
- Reorganize technical resources to list Azure CLI and REST API before or alongside PowerShell, emphasizing cross-platform options.
- Where PowerShell is referenced, provide a parallel Azure CLI command block to ensure parity for Linux and macOS users.
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-erdirect-about.md
...n/articles/expressroute/expressroute-erdirect-about.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 commands for onboarding to ExpressRoute Direct, with no equivalent Azure CLI (cross-platform) or Bash examples. The instructions and code snippets assume the use of PowerShell, which is traditionally associated with Windows environments, and there is no mention of how to perform these steps on Linux or macOS. This can make the onboarding process less accessible to users on non-Windows platforms.
Recommendations
- Add equivalent Azure CLI (az) command examples alongside PowerShell commands for all onboarding and configuration steps.
- Clearly indicate that both PowerShell and CLI can be used, and provide guidance for users on Linux/macOS.
- Where possible, provide Bash script examples or note any platform-specific differences.
- Reorganize sections so that cross-platform tools (like Azure CLI) are mentioned before or alongside Windows-specific tools.
- Include a note or table summarizing which tools/commands are available on which platforms (Windows, Linux, macOS).
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-faqs.md
...s/blob/main/articles/expressroute/expressroute-faqs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. PowerShell is repeatedly mentioned as a primary or sole automation tool for managing ExpressRoute (e.g., 'PowerShell cmdlet', 'how-to-routefilter-powershell.md'), and REST API/CLI are mentioned but often after PowerShell. There are no explicit Linux or cross-platform command-line examples, and no mention of Linux-native tools or shell environments. Where automation or scripting is referenced, Windows/PowerShell is prioritized or assumed. This may make it less accessible or less clear for Linux users.
Recommendations
- Provide Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
- When referencing automation or scripting, mention both PowerShell and Bash/CLI options, and link to relevant documentation for both.
- Avoid using 'PowerShell' as the default or only example in links and code samples (e.g., 'how-to-routefilter-powershell.md'); provide or link to equivalent Azure CLI or Bash guides.
- Explicitly state that all management operations can be performed from Linux, macOS, and Windows, and provide guidance for each.
- Where screenshots or UI instructions are shown, ensure they are not Windows-specific unless necessary, or provide Linux/macOS equivalents if applicable.