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 151-175 of 281 flagged pages
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 page demonstrates a Windows bias by referencing Windows-centric management APIs, linking to Windows documentation, and providing PowerShell as the only example for ExpressRoute routing configuration. There are no Linux or cross-platform CLI examples, and Windows tools and patterns are mentioned exclusively or before any Linux alternatives.
Recommendations
- Include Azure CLI and/or Bash examples alongside or instead of PowerShell for ExpressRoute configuration tasks.
- Reference cross-platform management APIs and documentation, not just Windows-specific ones.
- Provide links and examples for Linux-based management and automation tools (e.g., Azure CLI, REST API usage from Bash).
- Ensure that documentation for ExpressRoute routing and circuit management covers both Windows and Linux environments equally.
- Avoid linking only to Windows documentation (such as previous-versions/windows/mt844538) and instead use platform-neutral or cross-platform Azure docs.
Create Pull Request
Expressroute
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 PowerShell-based instructions and references, with no mention of Linux, Bash, or cross-platform CLI alternatives. The only non-portal automation example referenced is PowerShell, and the structure and links present PowerShell before any Linux-friendly options. There are no Linux or Azure CLI examples or references, and no mention of Bash or cross-platform scripting.
Recommendations
- Add Azure CLI (az) instructions and links alongside or before PowerShell examples, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Ensure that all automation or scripting references include both PowerShell and Azure CLI options.
- Rephrase references such as '[PowerShell instructions]' to '[PowerShell or Azure CLI instructions]' and provide corresponding links.
- Consider including a section or selector for Linux/macOS users, or clarify that the portal and Azure CLI are fully supported on all platforms.
- Audit all referenced articles to ensure Linux parity in examples and instructions.
Expressroute
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 and explicitly instructing users to use PowerShell for certain steps. There are no CLI or Linux-native command examples, and no mention of cross-platform tools like Azure CLI. This may hinder Linux or macOS users who do not have access to PowerShell or prefer other tooling.
Recommendations
- Provide equivalent Azure CLI (az) commands for all PowerShell examples, especially for gateway configuration and management steps.
- Mention that PowerShell is available cross-platform, but clarify that Azure CLI is often preferred on Linux/macOS.
- Wherever a command-line example is given, present both PowerShell and Azure CLI versions, or link to cross-platform documentation.
- Review the documentation for other implicit Windows-first assumptions, such as screenshots or terminology, and ensure parity for Linux/macOS users.
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 demonstrates a strong Windows/Powershell bias. The primary example for deploying an ExpressRoute circuit using an ARM template is provided only in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash example. Instructions and workflow steps are written specifically for PowerShell users, and the guidance assumes use of the Azure Cloud Shell in PowerShell mode. While there is a brief mention of Azure CLI and REST API as alternative deployment methods, no concrete CLI or Bash examples are provided. This prioritization of PowerShell and lack of Linux-native or cross-platform command examples may hinder accessibility for Linux and macOS users.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell scripts, especially for deploying and deleting ExpressRoute circuits.
- Include Bash shell instructions and examples where appropriate, or clarify that Azure Cloud Shell supports both Bash and PowerShell.
- Present CLI and PowerShell examples side-by-side or in tabs, ensuring neither platform is prioritized over the other.
- Explicitly state that all operations can be performed from Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.
- Review and update workflow steps to be platform-neutral, avoiding assumptions about the user's operating system or shell.
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
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation is heavily biased towards Windows environments, specifically PowerShell. All configuration steps and code samples use Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native tools. File paths and command syntax are Windows-centric (e.g., C:\NetworkConfig.xml). There are no examples or guidance for users on Linux or macOS platforms, and the installation instructions focus solely on PowerShell modules.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Linux/macOS file path examples (e.g., /home/user/NetworkConfig.xml) alongside Windows paths.
- Add a section or callouts for users on Linux/macOS, including installation instructions for Azure CLI and/or PowerShell Core on those platforms.
- Where possible, use platform-agnostic language and tools, or clearly indicate when a step is Windows-specific.
- Consider reordering or parallelizing instructions so that Linux/macOS methods are presented alongside Windows methods, rather than Windows-first.
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-howto-erdirect.md
...n/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 toward Windows and PowerShell usage. All command-line examples use Azure PowerShell cmdlets, and file paths are Windows-centric (e.g., C:\Users\SampleUser\Downloads). There is only a brief mention of Cloud Shell with a Linux-style path, but no Bash, Azure CLI, or Linux-native examples are provided. Windows tools and conventions are assumed throughout, and Linux alternatives are not discussed.
Recommendations
- Provide equivalent Azure CLI (az) command examples for all operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Linux/macOS file path examples alongside Windows paths, especially when referencing file downloads or script outputs.
- Explicitly mention that Azure PowerShell can be used on Linux/macOS, or provide installation instructions for non-Windows users.
- Structure sections so that cross-platform or Linux-native approaches (e.g., Azure CLI, Bash) are presented alongside or before Windows/PowerShell examples.
- Add notes or links to documentation for using Cloud Shell, Bash, or other cross-platform tools to perform the same tasks.
- Where possible, avoid Windows-specific terminology or clarify when a step is platform-agnostic.
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
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a Windows bias primarily in the 'Before you begin' section, where Azure PowerShell is required for subscription enrollment and registration, with no equivalent Azure CLI or Linux-native instructions provided. Additionally, file path examples (e.g., for LOA document download) use Windows-style paths without Linux alternatives. The rest of the guide uses Azure CLI, which is cross-platform, but the initial steps and some examples assume a Windows environment.
Recommendations
- Provide Azure CLI commands for subscription enrollment and provider feature registration, or explicitly state if these steps can only be performed via PowerShell.
- Include Linux/macOS file path examples (e.g., '~/Downloads/LOA.pdf') alongside Windows paths when specifying output destinations.
- If PowerShell is required for certain steps, clarify this limitation and offer guidance for Linux users (e.g., using Azure Cloud Shell or installing PowerShell Core on Linux).
- Review all command and output examples to ensure they are platform-agnostic or provide platform-specific variants where necessary.
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-howto-macsec.md
...ain/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 page exclusively uses Azure PowerShell cmdlets and assumes the reader is using PowerShell, which is traditionally a Windows-centric tool. There are no examples or guidance for users on Linux or macOS, such as using Azure CLI, Bash, or cross-platform scripting. All setup and configuration steps are shown with PowerShell, and there is no mention of Linux-native tools or alternative workflows.
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 installing and using these tools on non-Windows systems.
- Include Bash script examples or references for common tasks, especially for secret management and resource creation.
- Add a section or callouts for Linux users, highlighting any differences or additional considerations (e.g., authentication, environment setup).
- Avoid assuming the use of Windows or PowerShell as the default; present cross-platform options side-by-side or in parallel sections.
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
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 instructions assume the use of PowerShell, which is traditionally associated with Windows environments, and there is no guidance for users on Linux or macOS. The prerequisites and setup sections also reference Azure PowerShell specifically, reinforcing a Windows-centric approach.
Recommendations
- Provide equivalent Azure CLI (az) command examples for all configuration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include a section or notes on how to perform these tasks using Bash or in a Linux/macOS environment, clarifying any differences or prerequisites.
- Mention that Azure PowerShell can be used on Linux and macOS, but also highlight the availability and parity of Azure CLI.
- Reorganize the documentation so that cross-platform tools (like Azure CLI) are presented before or alongside PowerShell, rather than only after or not at all.
- Add links to official Azure CLI documentation for ExpressRoute where appropriate.
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-prerequisites.md
...in/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 Bash alternatives. There are no Linux-specific instructions or parity in tooling examples, and the only command-line tooling mentioned is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Wherever Azure PowerShell is mentioned, also provide equivalent Azure CLI (az) commands and Bash examples, or at least reference that these alternatives exist.
- Explicitly state that both Windows and Linux users can manage ExpressRoute resources, and link to cross-platform tooling documentation.
- Add a section or note clarifying that all required steps can be performed from Linux/macOS via Azure CLI, and provide links to relevant guides.
- Review all command references and ensure that Linux and cross-platform options are presented equally and not as an afterthought.
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 page exclusively uses PowerShell cmdlets for all configuration, management, and status-checking examples, with no mention or examples of Azure CLI, Bash, or cross-platform tools. There are explicit instructions to download PowerShell cmdlets, and no Linux-native or cross-platform alternatives are provided. This creates a strong Windows/PowerShell bias and limits accessibility for Linux or macOS users.
Recommendations
- Provide equivalent Azure CLI examples for all configuration, management, and status-checking tasks, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include a section or callout at the beginning of the article explaining that all tasks can be performed using Azure CLI, with a link to the relevant CLI documentation.
- Where PowerShell-specific instructions are given (such as installing cmdlets), provide parallel instructions for installing and using Azure CLI.
- Consider restructuring the article or adding tabs/switchers to allow users to select their preferred tool (PowerShell or Azure CLI), ensuring parity in instructions and examples.
- Explicitly mention that PowerShell Core is available cross-platform, if relevant, and provide installation guidance for non-Windows users if PowerShell must be used.
Expressroute
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 page demonstrates a strong Windows bias by exclusively referencing Azure PowerShell modules and providing only PowerShell command examples for migration tasks. There is no mention of Azure CLI or Bash equivalents, which are commonly used on Linux and macOS platforms. The guidance assumes the use of Windows tools and patterns, and does not address cross-platform scenarios or provide parity for Linux users.
Recommendations
- Include Azure CLI (az) command examples alongside PowerShell for all migration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that the migration can be performed from any OS using Azure CLI, not just from Windows with PowerShell.
- Provide links to Azure CLI installation and usage documentation, similar to the PowerShell references.
- Where PowerShell modules are referenced, also reference Azure CLI equivalents and their documentation.
- Review all code snippets and ensure that for every PowerShell example, a CLI/Bash example is also provided.
- Avoid language that assumes the user is on Windows or using Windows-specific tools.
Expressroute
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 Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively provides instructions and examples using PowerShell cmdlets for retrieving ARP tables on Azure ExpressRoute circuits. There are no examples or guidance for performing equivalent operations using Azure CLI, Bash, or other cross-platform tools. The prerequisites specifically require the Azure PowerShell module, and all code samples are in PowerShell. There is no mention of Linux or macOS workflows, nor are alternative tools or commands referenced.
Recommendations
- Provide equivalent instructions and examples using Azure CLI (az) commands, which are cross-platform and work on Linux, macOS, and Windows.
- Explicitly mention that the steps can be performed from any OS using Azure CLI, and provide installation links for both PowerShell and CLI.
- Include Bash or shell script examples where appropriate, especially for common troubleshooting or data retrieval tasks.
- Clarify any limitations or differences in output or capabilities between PowerShell and CLI, if applicable.
- Add a section or note for Linux/macOS users, outlining the recommended approach for retrieving ARP tables and interacting with ExpressRoute resources.
Expressroute
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
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias throughout. All code examples are in PowerShell, and the workflow is centered around the AzureCT PowerShell module, which is only available for Windows. The instructions for installing and running tools (iPerf, PSPing) are Windows-centric, including references to Windows Firewall and installation paths (e.g., C:\ACTTools). There is no step-by-step guidance or command-line examples for Linux users, and Linux is only mentioned passively as a possible remote host. Even in the test setup and results, only Windows Server is used. The documentation does not provide Linux equivalents for the PowerShell-based workflow, nor does it mention or demonstrate how to perform equivalent tests on Linux systems.
Recommendations
- Provide parallel Linux instructions and examples for each step, including how to install and use iPerf and PSPing (or Linux alternatives) on Linux hosts.
- Include bash or shell command examples for Linux users, alongside PowerShell examples.
- Document how to perform link performance tests between two Linux hosts, or between Windows and Linux, without requiring the AzureCT PowerShell module.
- Clarify which parts of the workflow are Windows-only and offer alternative workflows for Linux environments.
- Include sample output from Linux command-line tools to help Linux users interpret their results.
- Mention Linux firewall configuration (e.g., ufw, firewalld, iptables) where Windows Firewall is discussed.
- In test setup and results, include scenarios using Linux VMs and servers, not just Windows Server.
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-workflows.md
...b/main/articles/expressroute/expressroute-workflows.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation references PowerShell and the Azure portal as primary verification and configuration methods, with CLI mentioned only as an afterthought. There are no explicit Linux or cross-platform command-line examples, and the workflow implicitly assumes familiarity with Windows-centric tools and patterns.
Recommendations
- Include explicit Azure CLI examples for all verification and configuration steps, especially for circuit and peering state checks.
- When listing tools or methods (e.g., 'Verify provisioning using PowerShell, the Azure portal, or CLI'), mention CLI first or equally, and clarify that Azure CLI is cross-platform.
- Add Linux shell (bash) command examples where appropriate, especially for common tasks such as querying circuit status.
- Provide links to both PowerShell and Azure CLI documentation for each relevant step.
- Review for any other Windows-centric terminology or assumptions and ensure parity for Linux and macOS users.
Expressroute
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 example in the 'Next steps' section, without mentioning Azure CLI or Bash alternatives. There are no Linux-specific tools, patterns, or examples provided, and PowerShell is referenced before any cross-platform options. This may make the documentation less accessible for Linux or cross-platform users.
Recommendations
- Add Azure CLI (az) examples and links alongside PowerShell instructions for all migration and troubleshooting tasks.
- In the 'Next steps' section, include a link to a Linux/Bash/Azure CLI migration guide, or combine PowerShell and Azure CLI instructions in a unified guide.
- Ensure that all command-line instructions are presented in both PowerShell and Azure CLI formats, with equal prominence.
- Explicitly mention that migration can be performed from Linux, macOS, or Windows environments using Azure CLI.
- Review the documentation for any implicit assumptions about the user's operating system and clarify cross-platform compatibility where relevant.
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 steps and subnet management, with no mention of Azure CLI or Bash/Linux alternatives. This focus on PowerShell and omission of cross-platform tools may hinder Linux or macOS users seeking parity in migration guidance.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside PowerShell instructions for all migration and subnet management tasks.
- Explicitly mention that PowerShell examples are also available on Linux and macOS, or clarify when features are Windows-only.
- Include Bash or shell script snippets where appropriate, especially for validation and monitoring steps.
- Ensure that all references to tooling (e.g., 'supported only via PowerShell') are accompanied by notes on CLI support status and roadmap, or links to relevant GitHub issues/feature requests.
- Add a section or callout for Linux/macOS users, summarizing supported cross-platform tools and any known limitations.
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 users, while Linux instructions are manual and less automated. Windows tools and workflows (such as PowerShell scripts for firewall configuration) are mentioned first and in more detail, with Linux alternatives being less prominent or requiring manual intervention. There is also a lack of parity in verification steps and troubleshooting guidance for Linux compared to Windows.
Recommendations
- Provide equivalent automation for Linux users, such as shell scripts to open firewall ports and configure agents, similar to the provided PowerShell script for Windows.
- Present Linux and Windows instructions in parallel, giving equal prominence and detail to both platforms.
- Include verification and troubleshooting steps for Linux agents, not just for Windows (e.g., how to verify agent connectivity on Linux).
- Avoid referencing Windows tools (like Control Panel) without Linux equivalents; provide Linux-specific guidance where appropriate.
- Where possible, use cross-platform tools or commands, or clearly indicate when a step is platform-specific.
- Consider including screenshots or examples for Linux agent installation and configuration, matching the level of detail given for Windows.
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
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell command examples for all CLI-based troubleshooting steps, without offering Azure CLI (cross-platform) or Bash equivalents. Additionally, the only explicit connectivity test tool recommended is PsPing, which is a Windows-only utility. There are no Linux-native or cross-platform alternatives mentioned for command-line operations or connectivity testing.
Recommendations
- Provide Azure CLI (az) command examples alongside PowerShell for all resource and peering validation steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash or shell script examples for relevant troubleshooting steps, especially for Linux users.
- Recommend cross-platform connectivity testing tools (such as hping3, nping, or standard ping/traceroute) in addition to or instead of PsPing, and provide example usage for both Windows and Linux environments.
- Explicitly mention that the PowerShell examples are for Windows and provide equivalent instructions for Linux/macOS users.
- Where screenshots or portal instructions are given, clarify that the steps are platform-agnostic or note any differences for non-Windows users.
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/how-to-configure-custom-bgp-communities.md
...xpressroute/how-to-configure-custom-bgp-communities.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation exclusively uses Azure PowerShell for all configuration steps, with no mention of Azure CLI, Bash, or Linux-native tools. All code samples are PowerShell scripts, and the workflow assumes familiarity with PowerShell, which is more common on Windows systems. There are no examples or guidance for users on Linux or macOS platforms.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and commonly used on Linux and macOS.
- Explicitly mention that the configuration can be performed from any OS using Azure CLI or Cloud Shell, not just PowerShell.
- Add a section or callout for Linux/macOS users, guiding them to use Azure CLI or Bash scripts.
- Where possible, use neutral terminology (e.g., 'command line' instead of 'PowerShell') and avoid assuming a Windows environment.
- Ensure that all prerequisite and sign-in steps include both PowerShell and CLI alternatives.
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
Windows First
Summary
The documentation is heavily focused on PowerShell and Azure Automation runbooks using PowerShell scripts, with no mention of Linux alternatives or Bash/Azure CLI examples. All scripting and automation steps are described using PowerShell, and there is no guidance for users who may prefer or require Linux-based tooling or scripting environments. The documentation assumes familiarity with Azure PowerShell and does not provide parity for Linux users.
Recommendations
- Provide equivalent examples using Azure CLI (az) commands and Bash scripts for automation, especially for collecting ExpressRoute gateway route information.
- Mention that Azure Automation supports Python runbooks and provide a sample Python script for the same monitoring task.
- Clarify whether the described workflow is possible using Linux-based automation (e.g., using Azure CLI in Automation Accounts or Logic Apps) and provide instructions if so.
- Add a section or note for Linux/macOS users, outlining how to perform the same steps without relying on PowerShell.
- Where PowerShell modules are referenced, also reference Azure CLI equivalents and provide installation instructions for Linux environments.
- Ensure that any prerequisites or 'before you begin' sections mention both PowerShell and CLI options, not just PowerShell.
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/planned-maintenance.md
...blob/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 exclusively referencing the PowerShell command `Get-AzExpressRouteCircuitStats` for traffic monitoring during failover validation, without providing equivalent CLI or Linux-native commands. No Linux or cross-platform command-line examples (such as Azure CLI or REST API) are given for monitoring or validation tasks, and the only tool mentioned for direct interaction is a Windows-centric one.
Recommendations
- Provide Azure CLI examples (e.g., `az network express-route`) alongside or instead of PowerShell commands for monitoring and validation tasks.
- Include REST API or cross-platform scripting options for users on Linux or macOS.
- Explicitly mention that monitoring and management can be performed from any OS, and provide sample commands for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI).
- Where possible, link to documentation or guides for Linux-based network monitoring and ExpressRoute management.
- Avoid assuming the use of Windows tools by default; present cross-platform options first or in parallel.
Expressroute
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, referencing PowerShell-specific cmdlets and output, and omitting equivalent Azure CLI (cross-platform) or Bash examples. The instructions and screenshots are tailored to PowerShell users, with no mention or guidance for Linux or macOS users who may prefer or require CLI/Bash. While the text briefly mentions that Azure CLI and REST API are also supported, no examples or step-by-step instructions are given for those methods.
Recommendations
- Provide Azure CLI (az) command examples alongside PowerShell for all deployment and cleanup steps.
- Include Bash shell instructions or note that Azure CLI commands work cross-platform (Windows, Linux, macOS).
- Add screenshots or output examples from Azure CLI to ensure parity.
- Reorder or parallelize instructions so that CLI and PowerShell are presented equally, rather than PowerShell first or exclusively.
- Explicitly mention that Cloud Shell supports both Bash and PowerShell, and guide users to choose their preferred shell.
Expressroute
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/reset-circuit.md
...-docs/blob/main/articles/expressroute/reset-circuit.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides detailed instructions exclusively for Azure PowerShell, which is primarily a Windows-centric tool, and does not offer equivalent CLI or Bash examples for Linux users. There is no mention of Azure CLI or cross-platform scripting, and the only command-line instructions are for PowerShell.
Recommendations
- Add equivalent Azure CLI (az) command examples for resetting an ExpressRoute circuit, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash shell examples where appropriate, or clarify that the steps can be performed on any OS using Azure CLI.
- Explicitly mention that PowerShell Core is available cross-platform if PowerShell must be used, and provide installation instructions for Linux/macOS.
- Ensure that future documentation sections provide parity between Windows (PowerShell) and Linux (CLI/Bash) tooling.
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 demonstrates a Windows bias by providing only Azure PowerShell examples for Azure-side configuration and validation, referencing the Azure portal (which is cross-platform but often Windows-centric in documentation), and omitting Azure CLI (cross-platform) or Linux-native command examples. All device-side configuration examples are for Cisco IOS-XE, with no mention of Linux-based VPN solutions (e.g., strongSwan, libreswan). There are no Linux/Unix command-line examples for validation or configuration, and PowerShell is consistently used for Azure operations.
Recommendations
- Add Azure CLI examples alongside or in place of PowerShell for all Azure-side configuration and validation steps, as Azure CLI is fully cross-platform and widely used on Linux.
- Include Linux-based VPN device configuration examples (e.g., strongSwan, libreswan) in addition to Cisco IOS-XE, to support organizations using Linux appliances.
- When referencing how to obtain information (such as public IPs or connection status), provide both PowerShell and Azure CLI commands.
- Ensure that validation and troubleshooting steps include Linux-native tools (e.g., ipsec status, journalctl, ip route) for parity with Cisco and Windows/PowerShell examples.
- Where possible, avoid presenting PowerShell as the default or only automation/scripting option for Azure, and highlight the cross-platform nature of Azure CLI.