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 101-125 of 281 flagged pages
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples for creating and deleting ExpressRoute circuits. The main walkthrough uses PowerShell commands and instructions tailored to Windows users, such as right-clicking and pasting in the shell console. There are no equivalent Azure CLI or Bash examples for Linux/macOS users, and alternative deployment methods (CLI, REST, Portal) are only briefly mentioned at the end, without examples or guidance.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for all major operations (create, delete) to support Linux/macOS users.
  • Provide Bash script snippets or instructions for using Azure Cloud Shell in Bash mode.
  • Rephrase instructions that assume Windows-specific behaviors (e.g., right-click to paste) to be cross-platform or provide alternatives for Linux/macOS terminals.
  • Present PowerShell and CLI examples in parallel, or clearly indicate both options at the start of the tutorial.
  • Include notes about platform compatibility for each example, helping users choose the appropriate tool for their OS.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through the frequent mention of PowerShell as a management tool, often listed before or instead of cross-platform alternatives like Azure CLI or REST API. Several configuration and management instructions reference PowerShell cmdlets, and links to further configuration guidance use PowerShell in their titles or URLs. There are no explicit Linux-specific examples or references to Linux-native tools, and step-by-step instructions do not mention Linux shell commands or workflows. The Azure portal is referenced, which is cross-platform, but command-line examples and automation guidance are Windows-centric.
Recommendations
  • Add Linux-specific examples and workflows, such as Bash scripts or Azure CLI commands, alongside PowerShell instructions.
  • Ensure that Azure CLI and REST API methods are mentioned first or equally with PowerShell in all procedural steps.
  • Where PowerShell is referenced, include equivalent Azure CLI or Bash commands, and clarify platform compatibility.
  • Review linked articles (e.g., 'how-to-routefilter-powershell.md') to ensure Linux parity and provide alternative links or sections for non-Windows users.
  • Explicitly state that all management operations can be performed from Linux, macOS, and Windows, and provide guidance for each.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All example commands use PowerShell, and the Azure Connectivity Toolkit (AzureCT) is presented as a PowerShell module with installation and usage instructions exclusively for Windows. Supporting tools (iPerf, PSPing) are described in the context of Windows, with installation paths and firewall rules specific to Windows (e.g., C:\ACTTools, Windows Firewall). There are no Linux shell or CLI examples, nor instructions for installing or using these tools on Linux hosts. Even when mentioning that the remote host can be Linux, the steps and tooling remain Windows-centric.
Recommendations
  • Provide equivalent Linux instructions for installing and running iPerf and PSPing (or alternatives) using bash or other common Linux shells.
  • Include Linux command-line examples for running performance tests, such as using iPerf directly from the shell.
  • Document how to collect and interpret results on Linux, including file locations and output formats.
  • Mention Linux firewall configuration steps (e.g., using ufw or firewalld) for opening necessary ports.
  • Clarify which features of AzureCT (if any) are available or not available on Linux, and suggest open-source alternatives if AzureCT is Windows-only.
  • Reorder sections or provide parallel instructions so that Linux users do not have to adapt Windows-centric steps themselves.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell for configuration tasks (e.g., routing filters), linking to Windows-specific management APIs, and omitting Linux or cross-platform CLI examples. Windows tools and patterns are mentioned exclusively, and there are no instructions or examples for Linux users or administrators using cross-platform tools such as Azure CLI or REST APIs.
Recommendations
  • Provide equivalent Linux and cross-platform examples for all configuration steps, especially for tasks currently described only with PowerShell.
  • Include Azure CLI and REST API instructions alongside or before PowerShell examples to ensure parity for non-Windows users.
  • Link to cross-platform management documentation, not just Windows-specific APIs or tools.
  • Explicitly mention that all configuration steps can be performed from Linux/macOS environments using Azure CLI or REST, and provide sample commands.
  • Review all referenced articles and ensure they are not Windows-only or, if they are, provide alternative links for Linux users.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses Azure PowerShell for all configuration, verification, and management steps, with no mention of Azure CLI, Bash, or Linux-native tooling. All examples are PowerShell-centric, which is primarily a Windows tool, and there is no guidance for users on Linux or macOS platforms. The prerequisites and instructions assume PowerShell usage, reinforcing a Windows-first approach and omitting Linux parity.
Recommendations
  • Add equivalent Azure CLI examples for all configuration steps, as Azure CLI is cross-platform and commonly used on Linux and macOS.
  • Include a section on how to perform these tasks in Bash or via the Azure Portal, where applicable.
  • Update prerequisites to mention both Azure PowerShell and Azure CLI, with installation instructions for each on Windows, Linux, and macOS.
  • Clarify that Azure Cloud Shell supports both PowerShell and Bash, and provide examples for both environments.
  • Ensure troubleshooting and verification steps include CLI commands, not just PowerShell.
  • Review all notes and guidance to ensure they are not Windows-specific and provide Linux/macOS alternatives where needed.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
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 Linux-native tools, Azure CLI, or REST API alternatives. All code examples are PowerShell-based, which is primarily a Windows-centric tool, and there are no instructions or examples for users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for each PowerShell command, as Azure CLI is cross-platform and widely used on Linux.
  • Include notes or sections explaining how to perform these tasks using REST API or ARM templates for automation and platform neutrality.
  • Clarify that Azure PowerShell can be used in Azure Cloud Shell, which is available on all platforms, but still provide CLI alternatives for users who prefer native Linux tools.
  • Ensure that prerequisites and instructions do not assume a Windows environment; mention any platform-specific requirements or differences.
  • Consider reordering examples so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell instructions and examples, while omitting equivalent Linux/CLI examples. The only command-line method described uses Azure PowerShell, which is most commonly used on Windows, and there is no mention of Azure CLI or Bash alternatives. The structure and examples prioritize Windows-centric tools and workflows.
Recommendations
  • Add Azure CLI (az) examples for all PowerShell commands, showing how to perform the same maintenance configuration tasks on Linux/macOS.
  • Explicitly mention cross-platform compatibility for command-line steps, clarifying which tools work on Windows, Linux, and macOS.
  • Include Bash script examples or guidance for users who prefer Linux environments.
  • Reorder or parallelize documentation sections so that Linux/CLI options are presented alongside or before Windows/PowerShell instructions.
  • Add a note about installing and using Azure PowerShell on Linux/macOS if PowerShell must be used.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell migration instructions before any mention of Linux or cross-platform CLI alternatives. There are no explicit Linux or Azure CLI examples or references, and troubleshooting steps do not mention platform-agnostic tools. The 'Next steps' section highlights PowerShell as the only command-line migration method, omitting Azure CLI or Bash scripts, which are preferred by Linux users.
Recommendations
  • Add Azure CLI migration instructions and link them alongside PowerShell in the 'Next steps' section.
  • Provide troubleshooting examples using both PowerShell and Azure CLI, ensuring parity for Linux users.
  • Explicitly mention that migration and troubleshooting can be performed from Linux, macOS, and Windows platforms.
  • Include Bash script examples or references for common tasks, such as resource validation and subnet management.
  • Review all referenced articles to ensure Linux-friendly tooling is documented and accessible.
GitHub Create Pull Request
Expressroute https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-howto-add-ipv6.md ...n/articles/expressroute/expressroute-howto-add-ipv6.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides parity between Azure Portal, Azure CLI, and Azure PowerShell instructions, but there is a noticeable Windows bias. PowerShell examples and references are frequent and sometimes prioritized, with explicit instructions to use PowerShell for steps where the portal experience is incomplete. The CLI (Linux-friendly) instructions are present, but PowerShell is often mentioned first or as the fallback, and there are no references to Bash scripting or Linux-specific tools. The documentation assumes familiarity with PowerShell and Windows-centric workflows.
Recommendations
  • Ensure CLI instructions are always presented with equal prominence and detail as PowerShell, especially where the portal experience is incomplete.
  • Add explicit Bash scripting examples for common tasks, especially for advanced configuration and troubleshooting.
  • Where PowerShell is recommended due to portal limitations, clarify that Azure CLI can be used equivalently and provide CLI commands.
  • Avoid phrases like 'use the PowerShell instructions' and instead say 'use CLI or PowerShell instructions' with both options shown.
  • Reference Linux and macOS environments in prerequisites and installation guidance, not just Windows/PowerShell.
  • Include troubleshooting and advanced configuration examples using CLI/Bash, not only PowerShell.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page exclusively uses Azure PowerShell cmdlets for all configuration steps, with no mention of Linux, Bash, Azure CLI, or cross-platform alternatives. All command-line examples and tool references are PowerShell-specific, and file paths use Windows conventions. There are no examples or guidance for users on Linux or macOS platforms, nor any mention of how to accomplish these tasks outside of PowerShell.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell cmdlets, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash shell examples and use platform-agnostic file paths (e.g., ~/NetworkConfig.xml) where possible.
  • Add a section or callouts for Linux/macOS users, describing any differences or prerequisites.
  • Reference documentation or guides for configuring these connections using the Azure Portal (if/when available) or REST API for maximum platform neutrality.
  • Ensure that any required tools or scripts are available and supported on Linux/macOS, and provide installation instructions for those platforms.
GitHub Create Pull Request
Expressroute https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/how-to-expressroute-direct-portal.md ...cles/expressroute/how-to-expressroute-direct-portal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is presented as the primary scripting example alongside the Azure Portal, with Azure CLI included but often after PowerShell. File path examples (e.g., C:\Users\SampleUser\Downloads) are Windows-centric, and PowerShell commands are used for both Windows and Cloud Shell scenarios. There is little mention of Linux-specific patterns, and CLI examples do not clarify Linux usage or provide Linux file path conventions.
Recommendations
  • Provide explicit Linux file path examples (e.g., /home/user/Downloads/LOA.pdf) alongside Windows paths in CLI and PowerShell sections.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and mention any OS-specific considerations.
  • Add bash shell script examples where appropriate, especially for tasks like file downloads, environment variable usage, and automation.
  • Ensure that CLI examples use environment variables and paths that are OS-agnostic or show both Windows and Linux variants.
  • When referencing Cloud Shell, specify that it is Linux-based and show Linux path conventions.
  • Review and balance the order of examples so that PowerShell and CLI are presented with equal prominence, or alternate which comes first.
  • Avoid using Windows-only tools or terminology (e.g., C:\ paths) without also providing Linux/macOS equivalents.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for Azure-side operations, referencing the Azure portal (which is most commonly used on Windows), and omitting equivalent Azure CLI (cross-platform) commands. There are no Linux-specific instructions or examples for validating or configuring the Azure VPN gateway, nor are there examples for Linux-based on-premises VPN devices (such as strongSwan or libreswan). All on-premises device examples are for Cisco CSR1000, which is often run on Hyper-V (a Windows hypervisor), and no Linux-native device configuration is shown.
Recommendations
  • Add Azure CLI examples alongside or before PowerShell examples for all Azure-side operations, including BGP route verification, tunnel status checks, and VPN gateway configuration.
  • Include configuration and validation examples for popular Linux-based VPN devices (e.g., strongSwan, libreswan), showing how to set up IPsec/IKE and BGP on those platforms.
  • Reference Linux tools and commands (such as ipsec status, swanctl, or vtysh for FRRouting) for tunnel and BGP verification.
  • Explicitly mention that the Azure portal and PowerShell are available on non-Windows platforms, or provide links to cross-platform usage guides.
  • Ensure that instructions for finding public IP addresses, configuring firewalls, and other operational steps include Linux-native approaches (e.g., using nmcli, iptables, etc.).
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates bias towards Windows by exclusively referencing PowerShell commands (e.g., Get-AzExpressRouteCircuitStats) for monitoring and validation tasks, without providing equivalent Linux/CLI examples. The guidance assumes the use of Windows-based tools and omits instructions for Linux users, such as Azure CLI or REST API alternatives. No Linux-specific commands, patterns, or troubleshooting steps are mentioned.
Recommendations
  • Include Azure CLI examples (e.g., az network express-route) alongside PowerShell commands for monitoring and validation tasks.
  • Provide REST API references for ExpressRoute circuit statistics and failover validation.
  • Add troubleshooting and monitoring instructions for Linux environments, including sample shell scripts or command-line patterns.
  • Explicitly mention cross-platform support and clarify that all steps can be performed on both Windows and Linux systems.
  • Where PowerShell is referenced, add equivalent Bash or CLI commands in parallel for parity.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing command-line examples and operational instructions primarily using Windows tools (tracert) and PowerShell cmdlets (Get-AzVirtualNetworkGatewayLearnedRoute, Set-AzExpressRouteCircuit) for Azure resource validation and failover. There are no equivalent Linux or cross-platform CLI examples (such as bash, Azure CLI, or Linux traceroute), and Windows tools are mentioned first and exclusively in all relevant sections.
Recommendations
  • Add equivalent Linux examples for all command-line operations, such as using Azure CLI (az network vnet-gateway list-learned-routes, az network vnet-gateway list-advertised-routes) for route validation and failover.
  • Include Linux traceroute examples alongside Windows tracert, and clarify OS-specific differences.
  • Present cross-platform instructions in parallel (e.g., 'On Windows, use PowerShell... On Linux/macOS, use Azure CLI...'), rather than Windows-first or Windows-only.
  • Reference platform-agnostic tools and scripts where possible, and avoid assuming the user is on Windows.
  • Explicitly mention that all steps can be performed from Linux/macOS environments and provide sample commands.
GitHub Create Pull Request
Expressroute https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-howto-add-ipv6.md ...n/articles/expressroute/expressroute-howto-add-ipv6.md
High Priority View Details →
Scanned: 2025-08-25 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides instructions for the Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, there is a notable emphasis on PowerShell (a Windows-centric tool) throughout the guide. In several places, PowerShell examples and instructions are given prominence, sometimes being referenced as the preferred or only method for certain steps (e.g., creating the virtual network gateway in the portal section refers users to PowerShell). There are no explicit Linux-specific shell examples (e.g., Bash), and PowerShell is treated as a primary automation tool, which may disadvantage Linux users unfamiliar with it.
Recommendations
  • Wherever PowerShell is referenced as the only or preferred automation method, ensure equivalent Azure CLI (Bash-friendly) instructions are provided and clearly marked as cross-platform.
  • Avoid language such as 'use the PowerShell instructions' in portal sections; instead, offer both CLI and PowerShell alternatives, or clarify that CLI is cross-platform.
  • Add explicit Bash shell examples where possible, especially for scripting scenarios, to improve accessibility for Linux users.
  • In summary tables or step lists, avoid listing PowerShell before CLI, or alternate the order to avoid implicit prioritization.
  • Clarify in the prerequisites and tool installation sections that Azure CLI is fully supported on Linux and macOS, and provide links or notes for Linux users.
GitHub Create Pull Request
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 →
Scanned: 2025-08-25 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page shows a moderate Windows bias. PowerShell is mentioned as a primary automation/configuration tool, and some configuration guides and links reference PowerShell cmdlets or scripts before (or instead of) equivalent Azure CLI or Linux-native instructions. There are no explicit Linux or cross-platform command examples, and the documentation assumes familiarity with Windows-centric tools and patterns.
Recommendations
  • Provide Azure CLI examples alongside or before PowerShell examples for all configuration and management tasks.
  • Explicitly mention Linux/macOS compatibility for all command-line instructions and tools.
  • Link to both PowerShell and Azure CLI documentation where relevant, ensuring parity in guidance.
  • Include examples or references for Linux-based automation (e.g., Bash scripts) where appropriate.
  • Avoid assuming the use of Windows-only tools or environments; clarify when steps are cross-platform.
GitHub Create Pull Request
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 →
Scanned: 2025-08-25 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page references Azure PowerShell as a configuration method and does not mention or provide examples for Linux-native tools (such as Azure CLI or Bash scripting). The 'Next steps' section lists Azure PowerShell before any other automation or scripting options, and there are no Linux-specific instructions or parity in examples. This may create the impression that Windows or PowerShell is the primary or preferred environment for managing ExpressRoute FastPath, potentially disadvantaging Linux users.
Recommendations
  • Add explicit instructions and examples for configuring ExpressRoute FastPath using Azure CLI (az), which is cross-platform and commonly used on Linux.
  • Ensure that both Azure PowerShell and Azure CLI guides are referenced equally in the 'Next steps' section, ideally listing CLI first or side-by-side.
  • Wherever PowerShell commands are mentioned, provide equivalent Bash/Azure CLI commands.
  • Include notes clarifying that all features are accessible from both Windows and Linux environments.
  • Review linked configuration guides to ensure Linux parity and update them if necessary.
GitHub Create Pull Request
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 →
Scanned: 2025-08-25 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for gateway subnet creation, with no equivalent Azure CLI (cross-platform) or ARM template examples. The technical resources section lists only PowerShell and REST API links, omitting Azure CLI references. This focus on PowerShell and lack of Linux/cross-platform examples may hinder users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all code snippets, especially for gateway subnet creation.
  • Include references and links to Azure CLI documentation in the technical resources section.
  • Where possible, provide ARM/Bicep template examples for infrastructure-as-code parity.
  • Review the documentation for other areas where only PowerShell is mentioned and ensure CLI parity.
  • Explicitly state that both PowerShell and CLI are supported, and clarify any platform-specific requirements.
GitHub Create Pull Request
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 →
Scanned: 2025-07-14 17:05
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows by providing migration instructions and advanced configuration steps (such as adding multiple prefixes to GatewaySubnet) exclusively via PowerShell, with no mention of Azure CLI, Bash, or other cross-platform/Linux-friendly tools. There are no Linux-specific or cross-platform command examples, and PowerShell is presented as the only scripting interface for automation, which may disadvantage Linux users.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell instructions, especially for migration and subnet configuration tasks.
  • Explicitly mention cross-platform options (e.g., Azure CLI, Bash scripts) alongside PowerShell in all relevant sections and next steps.
  • Where PowerShell is required due to feature gaps, clearly state this and provide a roadmap or workaround for Linux users.
  • Add a section or callout for Linux/macOS administrators, summarizing which steps can be performed using cross-platform tools and which currently require PowerShell.
  • Ensure that links to migration guides and troubleshooting include both PowerShell and Azure CLI/Bash options where possible.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides configuration steps using the Azure portal and Azure PowerShell, but does not mention or provide examples for Linux-native tools such as Azure CLI, nor does it reference Bash or shell scripting. The PowerShell example assumes the use of Windows or PowerShell Core, and there is no guidance for users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all PowerShell steps, ensuring Linux and macOS users have clear guidance.
  • Explicitly mention that PowerShell Core is cross-platform if relevant, or clarify any Windows-specific requirements.
  • Include Bash or shell scripting examples where appropriate.
  • Structure the documentation so that Azure CLI and PowerShell examples are presented together or allow the user to select their preferred platform.
  • Review included content (INCLUDE files) to ensure Linux parity is maintained throughout.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses PowerShell cmdlets and assumes the use of the Azure PowerShell module, with no mention of equivalent commands or tooling for Linux or cross-platform environments (such as Azure CLI, Bash, or REST API). All examples and prerequisites are Windows/PowerShell-centric, and there is no guidance for users on Linux or macOS systems.
Recommendations
  • Add equivalent instructions and examples using Azure CLI (az), which is cross-platform and commonly used on Linux and macOS.
  • Include Bash shell examples for retrieving ARP tables or interacting with Azure resources.
  • Mention REST API options for users who may want to automate or script the retrieval of ARP tables without PowerShell.
  • Clearly indicate which instructions are Windows/PowerShell-specific, and provide parallel sections for Linux/macOS users.
  • Update the prerequisites to mention both PowerShell and Azure CLI as supported tools for this operation.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
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 equivalent Azure CLI (cross-platform) or Bash examples. Additionally, network validation steps from the client side use Windows tools (tracert) and Windows-style paths (C:\Users\...), with no mention of Linux alternatives (e.g., traceroute). This may disadvantage users operating from Linux or macOS environments.
Recommendations
  • For every PowerShell example, provide an equivalent Azure CLI (az) command example, which is cross-platform and widely used on Linux/macOS.
  • When demonstrating network validation from the client side, include both Windows (tracert) and Linux (traceroute) command examples.
  • Use generic file paths or clarify that steps apply to both Windows and Linux environments where possible.
  • Explicitly mention that the procedures are applicable regardless of the on-premises OS, and provide guidance or links for users on non-Windows systems.
  • Consider including Bash script snippets or references to Linux-native tools for parity.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page references Azure PowerShell as a configuration method for ExpressRoute FastPath, but does not mention or provide examples for Azure CLI, which is cross-platform and commonly used on Linux and macOS. The 'Next steps' section lists Azure PowerShell after the portal, but omits Azure CLI entirely. There are no command-line examples or instructions tailored for Linux users, and the only automation example is Windows-centric (PowerShell).
Recommendations
  • Add Azure CLI instructions and examples alongside or before Azure PowerShell in the 'Next steps' section and throughout the documentation.
  • Explicitly mention that both Azure PowerShell and Azure CLI can be used for configuration, and provide parity in example commands.
  • Where scripts or automation are referenced, provide both PowerShell and Bash (or CLI) equivalents to ensure Linux users are supported.
  • Review the documentation for other Windows-centric terminology or tools, and ensure Linux alternatives are equally represented.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through the frequent mention of PowerShell and the Azure portal as configuration tools, with no equivalent Linux or cross-platform CLI examples provided. References to REST API and Azure CLI are present but are less emphasized and often listed after PowerShell. There are no Linux-specific instructions, nor are there examples using bash or Linux-native tools. This can make the documentation less accessible or intuitive for Linux users or those preferring cross-platform command-line tools.
Recommendations
  • Provide Azure CLI (az) examples alongside or before PowerShell examples for all configuration and management tasks.
  • Include bash shell snippets and Linux-native command-line instructions where relevant.
  • Ensure that references to management tools (Azure portal, PowerShell, REST API, Azure CLI) are presented in a neutral or parallel order, not prioritizing Windows tools.
  • Add explicit notes or sections for Linux users, clarifying any platform-specific considerations or differences.
  • Where screenshots or images of tools are shown, include both Windows and Linux variants if applicable.
  • Review all procedural steps to ensure parity between Windows and Linux environments, especially for automation and scripting.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
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 Linux/Cloud Shell equivalents. There are no CLI (az) or Bash examples, and Linux-specific guidance is minimal or secondary. The documentation assumes the use of Windows tools and environments, with only a brief mention of Cloud Shell for Linux-like environments.
Recommendations
  • Provide Azure CLI (az) command examples alongside or instead of PowerShell, as Azure CLI is cross-platform and widely used on Linux.
  • For each step, include both Windows (PowerShell) and Linux (Bash/CLI) command examples, clearly labeled.
  • When referencing file paths, show both Windows (C:\...) and Linux (/home/...) formats together.
  • Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI or Cloud Shell, and provide links to relevant setup guides.
  • Avoid assuming the user is on Windows or using PowerShell by default; use neutral language and tool-agnostic instructions where possible.
  • Add a section at the beginning explaining tool options (PowerShell, Azure CLI, Cloud Shell) and their cross-platform availability.
GitHub Create Pull Request
← Previous Page 5 of 12 Next →