Expressroute

194
Total Pages
161
Linux-Friendly Pages
33
Pages with Bias
17.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

78 issues found
Showing 26-50 of 78 flagged pages
Expressroute Configure a virtual network gateway for ExpressRoute using the Azure portal ...expressroute-howto-add-gateway-portal-resource-manager.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page prioritizes Windows-centric workflows by referencing PowerShell instructions and examples, and by listing PowerShell-based guides alongside the portal guide. There are no explicit Linux/macOS CLI (e.g., Azure CLI, Bash) examples or links, and Windows/PowerShell tools are mentioned as the alternative to the portal, with no Linux equivalents provided.
Recommendations
  • Add Azure CLI (cross-platform) instructions and examples for all major tasks (gateway creation, configuration, SKU upgrade, deletion).
  • Include links to Azure CLI documentation or create parallel guides for Linux/macOS users.
  • When referencing command-line alternatives, mention Azure CLI before or alongside PowerShell, and clarify cross-platform compatibility.
  • Ensure screenshots and step-by-step instructions are not Windows-specific (e.g., avoid PowerShell-only screenshots).
GitHub Create Pull Request
Expressroute Azure ExpressRoute: Add IPv6 support for private peering ...n/articles/expressroute/expressroute-howto-add-ipv6.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides instructions for Azure Portal, Azure CLI, and Azure PowerShell. However, PowerShell is featured heavily, with multiple steps and examples, and is required for certain tasks (e.g., enabling IPv6 on zone-redundant gateways in the portal). PowerShell is a Windows-centric tool, and its usage is emphasized over cross-platform alternatives. Additionally, in some sections, PowerShell instructions are referenced as the preferred or only method, and PowerShell examples are shown before CLI equivalents in some places.
Recommendations
  • Ensure all tasks that currently require PowerShell have equivalent Azure CLI instructions, especially for enabling IPv6 on zone-redundant gateways.
  • Where PowerShell is referenced as the only method (e.g., in portal steps), clarify if Azure CLI can be used and provide those instructions.
  • Present CLI and PowerShell examples in parallel, or list CLI first to avoid implicit Windows prioritization.
  • Explicitly note that Azure CLI is cross-platform and recommend it for Linux/macOS users.
  • Audit for any PowerShell-specific terminology or steps and provide CLI alternatives.
GitHub Create Pull Request
Expressroute Azure ExpressRoute Template: Create an ExpressRoute circuit ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-howto-circuit-resource-manager-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page is heavily biased towards Windows and PowerShell usage. All code examples use Azure PowerShell, with no equivalent Azure CLI, Bash, or Linux/macOS shell examples provided. The workflow assumes familiarity with PowerShell and Windows conventions, and PowerShell is presented as the primary method for template deployment, with alternatives (CLI, portal, REST) only briefly mentioned and not exemplified. This creates friction for Linux/macOS users who typically use Azure CLI or Bash.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell commands, especially for template deployment and resource deletion.
  • Include explicit instructions and code blocks for Bash/Linux/macOS users, showing how to perform the same tasks.
  • Reorder sections or present CLI and PowerShell examples side-by-side to avoid Windows-first bias.
  • Clarify that Azure Cloud Shell supports both PowerShell and Bash, and show how to select the preferred shell.
GitHub Create Pull Request
Expressroute Azure ExpressRoute: Configure Global Reach ...es/expressroute/expressroute-howto-set-global-reach.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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 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 Linux/macOS users who may prefer Bash or Azure CLI. The prerequisites and tooling sections reinforce this bias by referencing Azure PowerShell and omitting any Linux-native or CLI-based workflows.
Recommendations
  • Provide equivalent Azure CLI examples for all configuration steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that Azure PowerShell can be installed and used on Linux/macOS, or link to installation guides for non-Windows platforms.
  • Add Bash script examples where appropriate, or clarify how commands can be run in Azure Cloud Shell (which supports both Bash and PowerShell).
  • Reorder or balance examples so that Linux/macOS-friendly options are presented alongside or before Windows/PowerShell options.
  • Include a section on tool choice, helping users select between PowerShell and CLI based on their OS.
GitHub Create Pull Request
Expressroute Azure ExpressRoute: Configure MACsec ...ain/articles/expressroute/expressroute-howto-macsec.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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 cmdlets for all configuration steps, with no mention of Linux/macOS alternatives such as Azure CLI, Bash, or cross-platform scripting. Prerequisites and troubleshooting are described in terms of PowerShell, and there is no guidance for users who may be on Linux or macOS. The use of PowerShell is assumed throughout, and Windows-centric tools and modules are referenced without parity for other platforms.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all steps, as Azure CLI is cross-platform and works on Linux/macOS.
  • Explicitly state that all commands can be run in Azure Cloud Shell, which supports Bash and PowerShell, and clarify platform requirements.
  • Add a section or notes for Linux/macOS users, including installation instructions for Azure CLI and how to perform the same tasks.
  • Reorder examples so that cross-platform tools (Azure CLI) are shown first or side-by-side with PowerShell.
  • Avoid assuming local PowerShell installation; highlight Cloud Shell as a platform-neutral option.
GitHub Create Pull Request
Expressroute Verify Azure ExpressRoute connectivity - troubleshooting guide ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-troubleshooting-expressroute-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides extensive PowerShell-based troubleshooting and verification steps for Azure ExpressRoute, with no equivalent CLI or Bash examples for Linux/macOS users. The only explicit tool recommendation for connectivity testing is PsPing, a Windows-only Sysinternals utility, with no mention of cross-platform alternatives. This creates friction for users on Linux or macOS, who must adapt instructions or seek their own tools.
Recommendations
  • Provide Azure CLI (az) command equivalents alongside PowerShell examples for all verification and troubleshooting steps.
  • Include Bash or shell script examples where appropriate.
  • Recommend cross-platform connectivity testing tools (e.g., hping, nping, or standard ping/traceroute) in addition to PsPing.
  • Explicitly note platform differences and offer guidance for Linux/macOS users in relevant sections.
  • Add troubleshooting steps using Linux-native commands (e.g., ip, arp, netstat) for ARP and routing validation.
GitHub Create Pull Request
Expressroute Configure Connection Monitor for Azure ExpressRoute ...es/expressroute/how-to-configure-connection-monitor.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell scripts are provided for critical configuration steps (e.g., configuring the monitoring solution and opening firewall ports), with no equivalent Bash or Linux shell examples. Windows tools and patterns (e.g., Control Panel, registry keys, Windows Firewall) are described in detail, while Linux instructions are brief, manual, and lack automation. Windows examples and steps are consistently presented before Linux ones.
Recommendations
  • Provide Bash or Linux shell script equivalents for all PowerShell scripts, especially for configuring the monitoring solution and firewall rules.
  • Include automated Linux instructions for opening firewall ports, such as sample iptables or firewalld commands.
  • Present Windows and Linux steps in parallel, or alternate which platform is described first to avoid implicit prioritization.
  • Expand Linux troubleshooting and verification guidance to match the detail provided for Windows.
  • Reference Linux-specific agent management tools and UI locations, not just Windows Control Panel.
GitHub Create Pull Request
Expressroute Azure ExpressRoute gateway migration - Troubleshooting errors and best practices ...cles/expressroute/gateway-migration-error-messaging.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page references PowerShell as the only command-line migration method and lists it before any Linux/macOS alternatives. There are no examples or instructions for using Azure CLI, Bash, or other cross-platform tools, and no mention of Linux/macOS-specific guidance. This creates friction for users on non-Windows platforms who may not use PowerShell.
Recommendations
  • Include Azure CLI examples for migration steps alongside PowerShell instructions.
  • Explicitly mention that Azure CLI is supported on Linux/macOS and provide links to relevant CLI documentation.
  • Present cross-platform tools (Azure CLI, REST API) before or alongside Windows-specific tools like PowerShell.
  • Add troubleshooting steps and resource management examples using Bash or CLI commands.
  • Clarify any platform-specific limitations or requirements for migration tasks.
GitHub Create Pull Request
Expressroute About migrating to an availability zone-enabled ExpressRoute virtual network gateway ...s/blob/main/articles/expressroute/gateway-migration.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias toward Windows by exclusively referencing PowerShell for command-line migration steps and subnet management, with no mention of Azure CLI or Bash/Linux/macOS-compatible instructions. The FAQ and migration steps direct users to PowerShell-based workflows, and PowerShell is the only automation tool mentioned for preview features. There is no guidance for Linux/macOS users who may prefer Azure CLI or Bash scripts, and PowerShell is presented as the default/only option for scripting and automation.
Recommendations
  • Add equivalent Azure CLI examples and links for all migration and subnet management tasks currently described as PowerShell-only.
  • Explicitly state platform compatibility for each tool (e.g., PowerShell, Azure CLI) and provide guidance for Linux/macOS users.
  • Reorder documentation to present Azure CLI and portal instructions before or alongside PowerShell, ensuring parity.
  • Include troubleshooting and FAQ entries for common Linux/macOS scenarios and issues.
GitHub Create Pull Request
Expressroute Configure custom BGP communities for Azure ExpressRoute private peering ...xpressroute/how-to-configure-custom-bgp-communities.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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 steps, with no mention of Azure CLI, Bash, or Linux/macOS workflows. All code examples are PowerShell-based, and the page references Windows-centric tools and patterns, making it difficult for Linux/macOS users to follow or replicate the instructions directly.
Recommendations
  • Add equivalent Azure CLI examples for all configuration steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that Azure PowerShell can be used in Azure Cloud Shell, which is available in-browser and supports Bash and PowerShell, to reduce perceived Windows exclusivity.
  • Include a section or note on how Linux/macOS users can perform these tasks, including installation instructions for Azure CLI and/or PowerShell Core on non-Windows platforms.
  • Order examples so that CLI and PowerShell are presented together, or alternate which comes first, to avoid Windows-first bias.
GitHub Create Pull Request
Expressroute Configure Azure ExpressRoute Direct ...cles/expressroute/how-to-expressroute-direct-portal.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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 examples are provided in detail and often precede Azure CLI examples. File paths in examples (e.g., C:\Users\SampleUser\Downloads) are Windows-centric, and instructions for saving files default to Windows locations. While Azure CLI is included for cross-platform parity, PowerShell is given prominence and some CLI sections contain copy-paste errors referencing PowerShell. There are no Linux/macOS-specific notes, and the documentation does not mention platform-specific considerations for CLI usage or file paths.
Recommendations
  • Ensure Azure CLI examples are presented before or alongside PowerShell, especially for cross-platform tasks.
  • Provide Linux/macOS file path examples (e.g., /home/sampleuser/Downloads/LOA.pdf) in CLI and PowerShell sections.
  • Add notes clarifying that Azure CLI works on Windows, Linux, and macOS, and provide platform-specific instructions where relevant.
  • Review and correct copy-paste errors in CLI sections that reference PowerShell commands.
  • Explicitly mention that all tasks can be completed on Linux/macOS using Azure CLI and Cloud Shell, and link to installation guides for non-Windows platforms.
GitHub Create Pull Request
Expressroute Planned maintenance guidance for ExpressRoute ...blob/main/articles/expressroute/planned-maintenance.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a moderate Windows bias by referencing the 'Get-AzExpressRouteCircuitStats' PowerShell command as the primary method for monitoring ExpressRoute traffic statistics during failover validation. No Linux or cross-platform CLI alternatives (such as Azure CLI or REST API) are provided, and the Windows/PowerShell tool is mentioned first and exclusively in the example. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer platform-agnostic tools.
Recommendations
  • Include equivalent Azure CLI commands (e.g., 'az network express-route ...') for monitoring ExpressRoute circuit statistics.
  • Reference REST API endpoints for ExpressRoute monitoring to provide a platform-neutral option.
  • Explicitly state that PowerShell is one option and provide parity for Linux/macOS users.
  • Reorder examples or provide both Windows and Linux/macOS instructions side by side.
GitHub Create Pull Request
Expressroute Reset a failed circuit - ExpressRoute | Microsoft Docs ...-docs/blob/main/articles/expressroute/reset-circuit.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides detailed instructions for resetting an ExpressRoute circuit using the Azure portal and Azure PowerShell. All command-line examples use PowerShell, which is primarily a Windows tool, and there are no equivalent instructions or examples for Linux/macOS users (e.g., using Azure CLI or Bash). The PowerShell section is prominent and assumes the user is familiar with Windows tooling, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI examples for Linux/macOS users.
  • Explicitly mention that Azure CLI can be used on all platforms and provide step-by-step instructions.
  • Reorder or parallelize sections so that Windows and Linux/macOS options are presented equally.
  • Clarify any platform-specific requirements for each method.
GitHub Create Pull Request
Expressroute Using S2S VPN as a backup for Azure ExpressRoute Private Peering | Microsoft Docs ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/use-s2s-vpn-as-backup-for-expressroute-privatepeering.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. All Azure-side command-line examples use PowerShell, with no Bash, Azure CLI, or Linux/macOS equivalents. The traceroute example uses Windows syntax (tracert), and Windows paths (C:\Users\...) are shown. There are no Linux/macOS-specific instructions or examples for key validation and failover steps, potentially creating friction for non-Windows users.
Recommendations
  • Provide Azure CLI (az) command equivalents for all PowerShell examples, with sample Bash syntax.
  • Include Linux/macOS traceroute examples (e.g., traceroute 10.17.11.132) alongside Windows tracert.
  • Use generic file paths or clarify that commands work on multiple platforms.
  • Explicitly mention that all steps can be performed from Linux/macOS, and link to relevant cross-platform tooling.
  • Add notes or sections for Linux/macOS users, especially for network validation and failover testing.
GitHub Create Pull Request
Expressroute Azure ExpressRoute: Configure S2S VPN over Microsoft peering ...xpressroute/site-to-site-vpn-over-microsoft-peering.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. Azure PowerShell is used exclusively for all Azure-side command examples, with no Azure CLI (cross-platform) equivalents provided. Instructions for viewing gateway IP addresses and tunnel status reference the Azure portal and PowerShell, omitting CLI or REST API options. The only on-premises device configuration example is for Cisco CSR1000 running on Hyper-V (a Windows virtualization platform), with no Linux-based VPN device or configuration shown. All command-line examples for Azure management are PowerShell, which is primarily used on Windows, and are presented before any mention of alternative tooling.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all Azure-side commands (e.g., Get-AzBgpServiceCommunity, Get-AzVirtualNetworkGatewayConnection, etc.), ensuring parity for Linux/macOS users.
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide links to CLI documentation.
  • Include configuration examples for a Linux-based VPN device (e.g., StrongSwan, Libreswan, or Openswan) in addition to Cisco CSR1000.
  • When referencing the Azure portal, clarify that it is web-based and platform-agnostic.
  • For on-premises device configuration, provide at least one example using a Linux VM or appliance.
  • Where possible, use generic terminology (e.g., 'virtual machine') instead of 'Hyper-V VM' unless the distinction is necessary.
GitHub Create Pull Request
Expressroute About migrating to an availability zone-enabled ExpressRoute virtual network gateway ...s/blob/main/articles/expressroute/gateway-migration.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell for command-line migration and subnet management tasks, with no mention of Linux/macOS equivalents (such as Azure CLI or Bash). All automation and scripting examples are PowerShell-based, and there is no guidance for users on non-Windows platforms. The migration steps and FAQ repeatedly direct users to PowerShell, and do not provide parity for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for all PowerShell-based instructions, especially for migration and subnet management.
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide links to relevant CLI documentation.
  • Where possible, provide Bash script equivalents or note cross-platform alternatives.
  • Reorder example links so that Azure CLI and portal instructions are presented before or alongside PowerShell.
  • Clarify platform requirements for each tool, and recommend cross-platform tools for automation.
GitHub Create Pull Request
Expressroute Azure ExpressRoute: ARP tables - Troubleshooting ...e/expressroute-troubleshooting-arp-resource-manager.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides instructions and examples using PowerShell cmdlets, which are native to Windows and require either Windows or PowerShell Core on Linux/macOS. There are no CLI, Bash, or Azure CLI examples, nor any mention of Linux/macOS workflows. The prerequisites and all troubleshooting steps assume the use of PowerShell, creating friction for users on Linux or macOS platforms.
Recommendations
  • Add equivalent instructions using Azure CLI (az expressroute ...), which is cross-platform and works natively on Linux/macOS.
  • Include Bash shell examples for querying ARP tables where applicable.
  • Explicitly mention support for Linux/macOS and provide guidance for installing and using PowerShell Core if PowerShell is required.
  • Present Azure CLI and Bash examples before or alongside PowerShell examples to avoid Windows-first bias.
GitHub Create Pull Request
Expressroute Azure ExpressRoute FastPath: Features, availability, and limitations ...docs/blob/main/articles/expressroute/about-fastpath.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides configuration guidance for Azure ExpressRoute FastPath, but only references Azure PowerShell and the Azure portal for setup, with no mention of Azure CLI or Linux/macOS-specific instructions. The 'Next steps' section lists PowerShell before any cross-platform tools, and does not provide parity for Linux users who may prefer CLI or Bash-based workflows.
Recommendations
  • Add configuration instructions using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Ensure that CLI examples are presented alongside PowerShell and portal instructions, or consider listing CLI first to emphasize platform neutrality.
  • Explicitly state that all configuration steps can be performed on Linux/macOS using Azure CLI.
  • Where scripts or commands are shown, provide both PowerShell and Bash/CLI equivalents.
GitHub Create Pull Request
Expressroute Managing complex network architectures with BGP communities - Azure ExpressRoute ...ocs/blob/main/articles/expressroute/bgp-communities.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses on conceptual guidance for managing BGP communities in Azure ExpressRoute, but when referring to configuration steps, it only mentions the Azure portal and does not provide any CLI, PowerShell, or automation examples. There is no explicit Windows bias in terms of examples or tools, but the absence of Linux/macOS-friendly command-line instructions (such as Azure CLI or REST API) means Linux users may lack parity in automation or scripting scenarios.
Recommendations
  • Add configuration instructions using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include REST API examples for programmatic configuration, benefiting all platforms.
  • If PowerShell examples are added, ensure Azure CLI equivalents are provided and shown alongside or before PowerShell.
  • Explicitly mention that the Azure portal is accessible from any OS, but highlight automation options for non-Windows environments.
GitHub Create Pull Request
Expressroute Configure customer-controlled maintenance for your virtual network gateway ...xpressroute/customer-controlled-gateway-maintenance.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides configuration steps using the Azure portal and PowerShell, with all CLI examples and tooling focused exclusively on PowerShell. There are no Bash, Azure CLI, or Linux/macOS-specific instructions or examples. PowerShell is a Windows-centric tool, and its use is presented as the only scripting option, creating friction for Linux/macOS users who may prefer or require Bash or Azure CLI.
Recommendations
  • Add equivalent Azure CLI (az maintenance ...) examples for all PowerShell commands.
  • Explicitly mention cross-platform options, such as using Azure CLI or Bash, and provide links to relevant documentation.
  • Clarify that PowerShell Core is available on Linux/macOS, but also provide native Bash/Azure CLI instructions for parity.
  • Reorder or parallelize examples so that Linux/macOS options are presented alongside Windows/PowerShell options.
GitHub Create Pull Request
Expressroute About ExpressRoute virtual network gateways ...ssroute/expressroute-about-virtual-network-gateways.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides configuration examples and references primarily using Azure PowerShell cmdlets, which are most commonly used on Windows. There are no CLI (az) or Linux/macOS shell examples for key tasks such as creating the gateway subnet. The technical resources section lists only PowerShell and REST API links, omitting Azure CLI documentation. This creates friction for Linux/macOS users who typically use the Azure CLI or Bash.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for all configuration tasks, especially for gateway subnet creation.
  • Include links to Azure CLI documentation in the technical resources section.
  • Where screenshots or instructions reference PowerShell, provide equivalent CLI/Bash instructions and screenshots.
  • Explicitly state that all operations can be performed using Azure CLI on Linux/macOS, and provide guidance for cross-platform users.
GitHub Create Pull Request
Expressroute Azure ExpressRoute: Router configuration samples ...es/expressroute/expressroute-config-samples-routing.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation is focused on router configuration for Cisco IOS-XE and Juniper MX series, which are platform-agnostic. However, the only mention of an OS-specific tool is in the MACSec section, where it states that CAK and CKN values must match those configured via PowerShell commands, implying a Windows-centric approach for key management. No Linux or cross-platform alternatives are mentioned for this step.
Recommendations
  • Provide equivalent Linux/macOS command-line instructions for configuring MACSec CAK/CKN values, such as using Azure CLI or REST API.
  • Clarify whether PowerShell is required only for Azure-side configuration, and if so, link to cross-platform tools (Azure CLI, portal, etc.).
  • Add notes or examples for Linux/macOS users to ensure parity in key management and configuration steps.
GitHub Create Pull Request
Expressroute About Azure ExpressRoute Direct ...n/articles/expressroute/expressroute-erdirect-about.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides onboarding instructions for ExpressRoute Direct exclusively using Azure PowerShell commands, with no mention of Azure CLI or Bash equivalents. This creates friction for Linux/macOS users who may not use PowerShell or prefer command-line tools native to their platforms. The rest of the document is platform-neutral, but the critical onboarding steps are Windows/PowerShell-centric.
Recommendations
  • Add Azure CLI examples for all onboarding steps (e.g., az account set, az feature register, az provider register).
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide links to installation guides.
  • Where possible, provide Bash script equivalents alongside PowerShell examples.
  • Clarify any platform-specific requirements or limitations for onboarding.
GitHub Create Pull Request
Expressroute Configure a virtual network gateway for ExpressRoute using the Azure portal ...expressroute-howto-add-gateway-portal-resource-manager.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page prioritizes Windows-centric tools and workflows, notably by referencing PowerShell instructions and providing links to PowerShell-based guides (both Resource Manager and Classic) without mentioning Linux/macOS equivalents (such as Azure CLI or Bash). Windows/PowerShell examples are referenced before any cross-platform alternatives, and there are no explicit Linux/macOS instructions or parity notes.
Recommendations
  • Add Azure CLI examples and links alongside PowerShell instructions for all tasks, especially for gateway creation and configuration.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Where PowerShell is referenced (e.g., for IPv6-based private peering), provide equivalent CLI commands and documentation links.
  • Ensure that screenshots and step-by-step instructions do not assume a Windows environment.
  • Add a note at the beginning clarifying that all steps can be performed from Linux/macOS using the Azure portal and CLI.
GitHub Create Pull Request
Expressroute Configure peering for ExpressRoute circuit - Azure portal ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-howto-routing-portal-resource-manager.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 primarily in the following ways: (1) The cross-platform selector lists PowerShell before Azure CLI, and the main page links to PowerShell guides twice (including classic), while only one Azure CLI link is provided. (2) The only command-line example given for certificate generation uses Windows-style 'openssl.exe' syntax, which is not standard on Linux/macOS, and does not provide a Linux/macOS equivalent. (3) There are no explicit Linux/macOS examples or references, and the documentation does not mention platform-specific considerations for non-Windows users.
Recommendations
  • Provide Linux/macOS command-line examples alongside Windows examples, especially for OpenSSL usage (e.g., use 'openssl' instead of 'openssl.exe').
  • In cross-platform selectors, list Azure CLI and PowerShell equally, or alternate their order to avoid implicit prioritization.
  • Explicitly mention platform differences or considerations where relevant (e.g., file paths, command syntax).
  • Add notes or links for Linux/macOS users to ensure parity in instructions and troubleshooting.
GitHub Create Pull Request
← Previous Page 2 of 4 Next →