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 51-75 of 281 flagged pages
Expressroute Troubleshoot network link performance: Azure ExpressRoute ...te/expressroute-troubleshooting-network-performance.md
High Priority View Details →
Scanned: 2026-01-10 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 page exhibits a strong Windows bias. All example commands and tooling are centered around PowerShell and Windows-specific utilities (AzureCT, PSPing, Windows Firewall, Set-NetTCPSetting). Installation and usage instructions are exclusively for Windows, with no Linux command-line or tool usage shown. While Linux is mentioned as a possible remote host, no Linux-specific guidance, examples, or troubleshooting steps are provided. The documentation assumes Windows as the default environment for both on-premises and Azure VMs, and all performance tuning advice is Windows-centric.
Recommendations
  • Provide equivalent Linux command-line examples for installing and running iPerf and PSPing (or alternatives like hping, nping, or native ping/traceroute).
  • Include instructions for running performance tests from Linux hosts, including firewall configuration (e.g., using iptables or ufw) and network tuning (e.g., sysctl settings for TCP window size).
  • Document how to use AzureCT or similar toolkits on Linux, or recommend cross-platform alternatives.
  • Add troubleshooting steps and output examples for Linux environments, including sample test results and file locations.
  • Ensure parity in guidance for both Windows and Linux, including VM setup, tool installation, and performance tuning.
  • Mention Linux tools and patterns before or alongside Windows equivalents, rather than only as an afterthought.
GitHub Create Pull Request
Expressroute Azure ExpressRoute gateway migration - Troubleshooting errors and best practices ...cles/expressroute/gateway-migration-error-messaging.md
High Priority View Details →
Scanned: 2026-01-10 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 migration using the Azure portal and PowerShell, but does not mention or provide examples for Linux-native tools (such as Azure CLI or Bash scripting). PowerShell is a Windows-centric tool, and its mention before any Linux alternatives suggests a Windows-first bias. There are no troubleshooting or migration examples using Linux command-line tools, nor are Linux-specific patterns or considerations discussed.
Recommendations
  • Add migration instructions and troubleshooting examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux.
  • Include Bash scripting examples for common migration and troubleshooting tasks.
  • Mention Linux support explicitly in the 'Next steps' section, e.g., 'Learn how to migrate using Azure CLI (Linux, macOS, Windows)'.
  • Ensure that all PowerShell examples are paired with equivalent Azure CLI examples for parity.
  • Discuss any Linux-specific considerations or limitations in ExpressRoute gateway migration, if applicable.
GitHub Create Pull Request
Expressroute About migrating to an availability zone-enabled ExpressRoute virtual network gateway ...s/blob/main/articles/expressroute/gateway-migration.md
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias by providing migration instructions and examples exclusively for PowerShell, with no mention of Linux CLI tools (such as Azure CLI or Bash). PowerShell is referenced as the only scripting method for advanced operations (e.g., adding GatewaySubnet prefixes), and migration steps are described with PowerShell before any Linux alternatives. There are no Linux/Bash-specific examples or parity guidance for non-Windows users.
Recommendations
  • Add Azure CLI (az) examples for all migration steps, including subnet prefix management and gateway operations.
  • Explicitly mention Linux and macOS support for migration tasks, clarifying which tools and commands are available cross-platform.
  • Provide Bash script equivalents for PowerShell instructions, especially for preview features and advanced configuration.
  • Reorder documentation sections so that Azure CLI and portal instructions are presented before or alongside PowerShell, ensuring equal visibility.
  • Include troubleshooting and validation steps using Azure CLI and Bash, not just PowerShell.
  • Add a table or note summarizing tool parity (PowerShell, Azure CLI, portal) for each major migration step.
GitHub Create Pull Request
Expressroute Configure custom BGP communities for Azure ExpressRoute private peering ...xpressroute/how-to-configure-custom-bgp-communities.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 Azure CLI, Bash, or Linux-native tooling. All code examples are PowerShell scripts, which are most familiar to Windows users. There is no guidance for users on Linux or macOS platforms, nor are alternative command-line tools or workflows presented.
Recommendations
  • Add equivalent Azure CLI examples for all configuration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that Azure CLI can be used from Bash, Cloud Shell, or other shells, and provide links to relevant CLI documentation.
  • Include notes or sections for Linux/macOS users, clarifying any differences in workflow or prerequisites.
  • Where PowerShell is referenced, clarify that Azure CLI is an alternative and provide side-by-side examples where possible.
  • Review and update the 'Working with Azure PowerShell' section to also reference Azure CLI and Bash usage.
GitHub Create Pull Request
Expressroute Configure Azure ExpressRoute Direct ...cles/expressroute/how-to-expressroute-direct-portal.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits several forms of Windows bias. PowerShell is presented as a primary automation method alongside the Azure Portal, with examples and file paths that are Windows-centric (e.g., C:\Users\SampleUser\Downloads). In some sections, PowerShell instructions are given before Azure CLI, and CLI examples sometimes reuse PowerShell commands or syntax. There is no explicit mention of Linux shell environments (bash, zsh), nor are Linux-specific file paths or usage patterns shown. The documentation does not clarify cross-platform differences, such as how file paths or environment variables should be handled on Linux/macOS. There are no bash or shell script examples, and the documentation assumes familiarity with Windows conventions.
Recommendations
  • Add explicit Linux/macOS examples for file paths (e.g., /home/sampleuser/Downloads/LOA.pdf) and clarify cross-platform differences in file handling.
  • Include bash or shell script equivalents for PowerShell commands, especially for Azure CLI usage.
  • Ensure Azure CLI instructions are fully platform-neutral, avoiding Windows-centric syntax or assumptions.
  • Present Azure CLI and PowerShell examples in parallel, and avoid giving PowerShell precedence over CLI, especially since CLI is cross-platform.
  • Add notes or tips for Linux/macOS users where behavior or syntax differs (e.g., path separators, environment variables).
  • Review screenshots and UI references to ensure they are not exclusively Windows-oriented if possible.
GitHub Create Pull Request
Expressroute Configure Connection Monitor for Azure ExpressRoute ...es/expressroute/how-to-configure-connection-monitor.md
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias in several ways: PowerShell scripts are provided for key configuration steps (e.g., deploying the monitoring solution, opening firewall ports), with no equivalent Bash or Linux shell examples. Windows tools and patterns (such as Control Panel and registry keys) are referenced explicitly, while Linux instructions are less detailed and require manual file edits. Windows steps and scripts are often mentioned before Linux alternatives, and troubleshooting links are Windows-centric. Linux users must perform more manual configuration, and guidance is less comprehensive.
Recommendations
  • Provide equivalent Bash or shell scripts for Linux users for steps currently covered only by PowerShell (e.g., deploying the monitoring solution, opening firewall ports).
  • Include Linux-first or at least parallel instructions, ensuring Linux examples are as detailed and automated as Windows ones.
  • Reference Linux troubleshooting resources alongside Windows ones.
  • Avoid assuming Windows as the default platform; present OS options side-by-side.
  • Automate Linux agent configuration (e.g., port changes and firewall rules) with sample scripts, reducing manual file editing.
  • Ensure parity in screenshots and UI walkthroughs for both Windows and Linux environments.
GitHub Create Pull Request
Expressroute Planned maintenance guidance for ExpressRoute ...blob/main/articles/expressroute/planned-maintenance.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the PowerShell command Get-AzExpressRouteCircuitStats for monitoring traffic statistics, without providing equivalent CLI or Linux-native examples. The guidance assumes the use of Windows-centric tools and does not mention Linux alternatives or provide cross-platform instructions for key operational steps.
Recommendations
  • Include Azure CLI examples (e.g., az network express-route) alongside PowerShell commands for monitoring and troubleshooting ExpressRoute circuits.
  • Explicitly mention that monitoring and failover validation can be performed from Linux or macOS environments, and provide sample commands for those platforms.
  • Reference cross-platform tools (such as curl, netcat, or standard BGP monitoring utilities) where applicable, and clarify any platform-specific requirements.
  • Ensure all operational steps (e.g., failover validation, monitoring) have both Windows and Linux instructions, or note any limitations.
  • Add a section or note on best practices for Linux-based network edge devices, including relevant configuration and troubleshooting tips.
GitHub Create Pull Request
Expressroute Azure ExpressRoute: Configure S2S VPN over Microsoft peering ...xpressroute/site-to-site-vpn-over-microsoft-peering.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 Windows bias by providing Azure PowerShell commands as the primary method for Azure-side configuration and validation, referencing the Azure portal (which is most commonly used on Windows), and omitting equivalent Azure CLI (cross-platform) or Linux-native examples. All device-side configuration examples are for Cisco IOS-XE (which is OS-neutral), but all Azure-side scripting and verification is shown only with PowerShell, with no Bash, Azure CLI, or Linux-native alternatives. There are no examples or guidance for Linux-based VPN devices or for using Linux tools to validate or troubleshoot the VPN connection.
Recommendations
  • Add Azure CLI (az) command examples alongside or in place of PowerShell for all Azure-side configuration and validation steps.
  • Include instructions for finding public IP addresses and verifying tunnel status using Azure CLI and Bash scripts.
  • Provide configuration and troubleshooting examples for a Linux-based VPN device (e.g., strongSwan, libreswan, or OpenVPN) in addition to Cisco IOS-XE.
  • Reference Linux tools (e.g., ipsec status, tcpdump, iproute2) for tunnel validation and troubleshooting.
  • Ensure that all code snippets and workflow steps are presented in a cross-platform manner, or at least offer parity between Windows and Linux approaches.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
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 in several ways: all Azure-side command examples use PowerShell, with no Bash/CLI or Linux-native equivalents; network validation steps (such as traceroute) use Windows syntax and prompt; and there are no Linux or cross-platform alternatives provided for key operational steps. This may hinder Linux users or those using non-Windows environments from following the guidance seamlessly.
Recommendations
  • Provide Azure CLI (az) command examples alongside PowerShell for all Azure resource operations (e.g., route validation, ExpressRoute circuit management).
  • Include Linux traceroute examples (e.g., using 'traceroute' or 'mtr' commands) in addition to Windows 'tracert'.
  • Explicitly mention that the steps can be performed from Linux or macOS environments, and provide syntax for those platforms where applicable.
  • Where scripts or commands are shown, offer both Windows and Linux versions, or note any platform-specific differences.
  • Add a section or note on cross-platform tooling and considerations for users managing Azure networking from non-Windows systems.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
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 only Azure PowerShell examples for gateway subnet creation, omitting equivalent Azure CLI (cross-platform) or ARM template examples. References to PowerShell and REST APIs are present, but Linux-specific tools or workflows are not mentioned. The documentation assumes familiarity with PowerShell, which is primarily a Windows tool, and does not provide parity for users on Linux or macOS platforms.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all configuration tasks, especially for gateway subnet creation.
  • Include ARM template snippets for resource creation to support infrastructure-as-code scenarios on any platform.
  • Explicitly mention that Azure CLI is cross-platform and provide links to relevant CLI documentation.
  • Ensure REST API references are accompanied by sample requests using curl or other platform-neutral tools.
  • Review all technical walkthroughs to provide both PowerShell and CLI instructions, giving equal prominence to each.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references PowerShell as a verification method before mentioning alternatives (Azure portal, CLI), and does not provide explicit Linux or cross-platform command examples. There is a lack of parity in showing how Linux users would perform key steps, such as verifying provisioning or configuring routing, with only PowerShell or generic references given.
Recommendations
  • Explicitly provide Azure CLI examples alongside PowerShell for all command-line steps, as Azure CLI is cross-platform and preferred by Linux users.
  • When listing verification methods, mention Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
  • Add notes or sections for Linux/macOS users, clarifying any platform-specific considerations or differences.
  • Ensure that all workflow steps that reference PowerShell also include equivalent Azure CLI commands, and link to cross-platform documentation where available.
GitHub Create Pull Request
Expressroute https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/scalable-gateway.md ...cs/blob/main/articles/expressroute/scalable-gateway.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 a method for performing upgrades, but does not mention CLI or Linux-based alternatives. Windows tooling (PowerShell) is mentioned before any cross-platform or Linux-native options, and there are no examples or instructions for Linux users. This creates a bias toward Windows environments and may hinder Linux users from following the guidance.
Recommendations
  • Include Azure CLI examples alongside PowerShell instructions for upgrade and configuration tasks.
  • Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and provide links to relevant CLI documentation.
  • When referencing upgrade or migration processes, list both PowerShell and CLI options, and avoid implying that PowerShell is the only or primary method.
  • Add a section or note clarifying cross-platform support for all management tasks described.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively provides PowerShell-based instructions and examples for viewing ARP tables on Azure ExpressRoute circuits. There are no references to Linux tools, Bash, Azure CLI, or cross-platform alternatives. The prerequisites and all troubleshooting steps assume the use of PowerShell, which is traditionally associated with Windows environments, and do not mention how to perform these tasks on Linux or macOS.
Recommendations
  • Add equivalent instructions and examples using Azure CLI, which is cross-platform and commonly used on Linux and macOS.
  • Include Bash script examples for retrieving ARP tables, where possible.
  • Explicitly mention Linux/macOS compatibility for the documented procedures, or provide links to platform-specific guides.
  • Clarify whether the PowerShell module can be used on Linux/macOS (with PowerShell Core), and provide installation steps for those platforms.
  • Consider adding troubleshooting steps and tool references that are relevant to Linux environments (e.g., using 'arp', 'ip neigh', or other network utilities).
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by only providing configuration instructions for the Azure portal and Azure PowerShell, with no mention of Linux-friendly tools such as Azure CLI or ARM templates. PowerShell is a Windows-centric tool, and its configuration steps are listed before any Linux-equivalent methods. There are no examples or guidance for Linux users, nor are cross-platform alternatives referenced.
Recommendations
  • Add configuration instructions using Azure CLI, which is cross-platform and widely used on Linux.
  • Include ARM template examples for automation, which are platform-agnostic.
  • Explicitly mention that Azure PowerShell is available on Linux and macOS, or clarify its cross-platform support.
  • Present configuration options in a neutral order (e.g., CLI, PowerShell, Portal) to avoid Windows-first bias.
  • Provide troubleshooting and operational examples using Linux tools and shell commands where appropriate.
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-09 00:34
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 providing configuration instructions only via the Azure portal and PowerShell, both of which are most commonly used on Windows. There are no examples or guidance for Linux users, such as using Azure CLI or Bash scripts. PowerShell is highlighted as the sole command-line method, and no Linux-native tools or workflows are mentioned.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that the steps can be performed on Linux and macOS using Azure CLI, and provide sample commands.
  • Include Bash script examples where appropriate, or reference automation options available on Linux.
  • Ensure that documentation sections do not prioritize Windows tools (PowerShell) over cross-platform alternatives (Azure CLI).
  • Add a note clarifying platform compatibility for each method (portal, PowerShell, CLI).
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page for Azure ExpressRoute FAQ demonstrates a Windows bias in several areas. Instructions for managing ExpressRoute circuits often mention PowerShell and REST API, with PowerShell listed before Azure CLI. Some configuration guides and links (e.g., route filters, circuit provisioning) reference PowerShell-specific documentation or workflows, but do not provide explicit Linux/Azure CLI examples or parity. There is a lack of Linux-specific command-line instructions, and Windows tools/patterns (PowerShell) are mentioned more frequently and earlier than their cross-platform equivalents.
Recommendations
  • Provide Azure CLI examples alongside PowerShell for all configuration and management tasks, ensuring parity for Linux and macOS users.
  • Where PowerShell is referenced, explicitly mention that Azure CLI is available and provide links to CLI documentation.
  • Review all linked 'how-to' guides and ensure Linux/Azure CLI instructions are present and easily discoverable.
  • Avoid listing Windows/PowerShell tools before cross-platform alternatives unless there is a technical reason.
  • Add notes or sections for Linux users, clarifying any differences or additional steps required for common ExpressRoute operations.
GitHub Create Pull Request
Expressroute https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-erdirect-about.md ...n/articles/expressroute/expressroute-erdirect-about.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively providing Azure PowerShell commands for onboarding, without offering equivalent Azure CLI or Bash examples. This approach assumes users are on Windows or familiar with PowerShell, and omits guidance for Linux or cross-platform users. No Linux-specific tools or workflows are mentioned, and PowerShell is presented as the default method for interacting with Azure.
Recommendations
  • Add equivalent Azure CLI commands for all onboarding and management steps, alongside PowerShell examples.
  • Explicitly mention that both PowerShell and Azure CLI can be used, and provide links to installation guides for both on Windows, Linux, and macOS.
  • Include Bash script examples where appropriate, especially for automation scenarios.
  • Review technical requirements and workflows for any implicit Windows-centric assumptions, and clarify cross-platform compatibility.
  • Ensure diagrams and workflow images do not imply a Windows-only environment.
GitHub 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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page displays a Windows bias by prioritizing Azure portal and PowerShell instructions, with explicit links to PowerShell-based guides for both Resource Manager and Classic deployment models. There are no references to Linux CLI tools (such as Azure CLI) or Bash examples, and the only command-line instructions referenced are for PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Add equivalent Azure CLI (az) instructions for all major tasks, including gateway creation, configuration, and SKU upgrades.
  • Provide Bash shell examples alongside PowerShell, especially for users on Linux and macOS.
  • Update cross-links and selector menus to include 'Resource Manager - Azure CLI' and/or 'Classic - Azure CLI' options.
  • Ensure screenshots and step-by-step guides are not exclusively tailored to Windows/PowerShell users.
  • Explicitly mention platform-agnostic tools and approaches where possible, and clarify that PowerShell can be used cross-platform if relevant.
GitHub Create Pull Request
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-09 00:34
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 and instructions, with no equivalent Azure CLI, Bash, or Linux-native examples for creating or deleting an ExpressRoute circuit. The workflow assumes use of PowerShell and Windows patterns (e.g., right-click to paste), and only references other deployment methods in a brief list at the end, rather than providing parity in step-by-step guidance.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, including circuit creation and deletion.
  • Include Bash script examples and instructions for Linux/macOS users.
  • Adjust instructions to use cross-platform terminology (e.g., 'paste into the shell' rather than 'right-click and paste').
  • Present CLI and PowerShell examples side-by-side, or provide clear navigation to Linux/macOS-specific instructions.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS, or clarify platform requirements for each method.
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-09 00:34
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 and Windows-centric tools for configuration and management tasks, without providing equivalent Linux or cross-platform examples. The only explicit example for managing ExpressRoute routing is via PowerShell, and links to management APIs reference Windows documentation. There are no CLI, Bash, or Linux-native instructions or examples, and Windows tools and patterns are mentioned exclusively or before any cross-platform alternatives.
Recommendations
  • Include Azure CLI (az) examples alongside or instead of PowerShell for all configuration and management tasks, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Provide Bash or shell script examples for common ExpressRoute tasks, especially for routing and circuit management.
  • Reference cross-platform documentation and tools (e.g., Azure CLI, REST API) before or alongside Windows/Powershell-specific resources.
  • Ensure that all links to management APIs and guides include Linux and macOS compatibility notes or alternatives, not just Windows.
  • Explicitly state when a procedure is platform-agnostic, and avoid assuming the user is on Windows.
  • Add a section or callout for Linux administrators, highlighting any differences or additional steps required for Linux environments.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell. However, PowerShell (a Windows-centric tool) is given equal prominence to CLI, and in several places, PowerShell commands are referenced directly within portal instructions (e.g., for enabling IPv6 on zone-redundant gateways). There are explicit instructions to use PowerShell when the portal experience is incomplete, but no equivalent Bash or Linux shell alternatives are mentioned. The documentation assumes PowerShell is available and does not address Linux-native scripting or tools outside Azure CLI.
Recommendations
  • Where PowerShell is recommended due to portal limitations, provide equivalent Azure CLI commands and explicitly mention that CLI is cross-platform (Linux, macOS, Windows).
  • Avoid referencing PowerShell as the only alternative when the portal is incomplete; always provide CLI alternatives.
  • Clarify that PowerShell is primarily a Windows tool and recommend Azure CLI for Linux/macOS users.
  • Add notes or links for installing and using Azure CLI on Linux/macOS, especially in sections where PowerShell is referenced.
  • Review all examples to ensure CLI commands are present and complete for every scenario covered by PowerShell.
  • Consider adding Bash script examples for automation tasks, or at least mention that Azure CLI can be used in Bash scripts.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
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. Installation instructions and command references assume a Windows/PowerShell context, and there are no parallel examples for Linux users. The structure and language also prioritize Windows tooling and patterns, making it less accessible for users on Linux or macOS.
Recommendations
  • Provide equivalent Azure CLI examples for each PowerShell command, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include installation instructions for Azure CLI and reference Bash or shell scripting where appropriate.
  • Explicitly state that the procedures can be performed from Linux/macOS using Azure CLI, and provide links to relevant documentation.
  • Where XML configuration files are referenced, clarify that editing and uploading can be done from any OS, and provide cross-platform guidance.
  • Reorganize sections so that cross-platform (CLI) instructions are presented alongside or before Windows/PowerShell-specific instructions.
  • Add a note at the beginning clarifying OS/tooling requirements and offering parity for Linux/macOS users.
GitHub Create Pull Request
Expressroute https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-howto-linkvnet-portal-resource-manager.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-howto-linkvnet-portal-resource-manager.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 prioritizing Windows-centric tools and workflows. The navigation selector lists 'PowerShell' before 'Azure CLI', and includes both 'PowerShell' and 'PowerShell (classic)' as primary alternatives to the Azure portal, which are Windows-native tools. There are no direct Linux-specific examples, nor are Linux command-line tools (such as Bash or native Linux networking utilities) mentioned. The main walkthrough is focused on the Azure portal UI, which is cross-platform, but the only code-based alternatives referenced are PowerShell and Azure CLI, with PowerShell given precedence. There are no explicit Linux instructions, nor any mention of Linux-specific considerations or troubleshooting.
Recommendations
  • Provide Linux-specific examples and workflows, such as using Bash scripts or Linux-native tools for ExpressRoute configuration.
  • Ensure Azure CLI examples are given equal or greater prominence than PowerShell, as Azure CLI is cross-platform.
  • Include troubleshooting steps or notes relevant to Linux environments (e.g., SSH, Linux networking commands).
  • Clarify that all steps can be performed on Linux, macOS, and Windows, and highlight any platform-specific differences.
  • Consider adding a section or links for Linux users, especially for command-line operations and automation.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
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 code examples and instructions assume the use of PowerShell, which is traditionally associated with Windows environments. There is no guidance for users on Linux or macOS, nor are alternative command-line tools presented.
Recommendations
  • Add equivalent Azure CLI examples for all configuration, verification, and management steps.
  • Include instructions for running Azure CLI/Bash commands on Linux and macOS, and clarify cross-platform support.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS, but provide parity with CLI and Bash examples.
  • Reorganize sections so that both PowerShell and CLI/Bash instructions are presented side-by-side, or provide a selector for platform-specific guidance.
  • Reference Azure Cloud Shell as a cross-platform option, and clarify how both PowerShell and Bash shells can be used.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively uses Azure PowerShell cmdlets for all configuration steps, with no mention of Linux-native tools, Bash, Azure CLI, or cross-platform alternatives. All examples and instructions assume the use of PowerShell, which is most commonly associated with Windows environments. There is no guidance for users on Linux or macOS, nor any reference to how these steps could be performed outside of PowerShell.
Recommendations
  • Add equivalent Azure CLI examples for all configuration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that Azure PowerShell can be installed and used on Linux and macOS, and provide installation instructions or links.
  • Provide Bash script examples or instructions for users who prefer shell scripting on Linux.
  • Include a section or notes on configuring MACsec from Linux-based edge routers, including references to relevant Linux tools (e.g., iproute2, strongSwan, etc.) for MACsec configuration.
  • Reorder or balance examples so that Linux and Windows approaches are presented equally, or at least clarify that the PowerShell approach is not Windows-exclusive.
GitHub Create Pull Request
← Previous Page 3 of 12 Next →