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 201-225 of 281 flagged pages
Expressroute Azure ExpressRoute: Router configuration samples ...es/expressroute/expressroute-config-samples-routing.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation is primarily focused on router configuration for Cisco IOS-XE and Juniper MX series, which are platform-agnostic. However, the MACSec section references PowerShell commands for configuring CAK/CKN values, implicitly assuming users are on Windows or using Windows tools. No Linux or cross-platform alternatives are mentioned for this step.
Recommendations
  • Provide Linux/macOS equivalents for the PowerShell commands referenced in the MACSec configuration section, such as Azure CLI or REST API examples.
  • Clarify whether the PowerShell step is required only for Azure-side configuration, and if so, link to cross-platform methods for setting these values.
  • Explicitly state platform requirements for any steps that use Windows-specific tools, and offer alternatives where possible.
GitHub Create Pull Request
Expressroute Azure ExpressRoute: Configure MACsec ...ain/articles/expressroute/expressroute-howto-macsec.md
Medium Priority View Details →
Scanned: 2026-01-14 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 is heavily biased towards Windows and PowerShell usage. All configuration steps, examples, and command references are provided exclusively using Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux/macOS alternatives. The prerequisites and troubleshooting sections also assume PowerShell usage, and there is no guidance for users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all steps, as Azure CLI is cross-platform and works natively on Linux/macOS.
  • Explicitly mention that Azure PowerShell can be installed and used on Linux/macOS, or provide links to installation guides for those platforms.
  • Include Bash script examples where possible, especially for secret management and resource creation.
  • Reorder sections or add notes to clarify that the process can be completed on any OS, not just Windows.
  • Reference Azure Cloud Shell as a cross-platform solution, and provide instructions for using it from Linux/macOS terminals.
GitHub Create Pull Request
Expressroute Get operation correlation ID from Activity Log .../blob/main/articles/expressroute/get-correlation-id.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes how to obtain the correlation ID using the Azure Portal web interface, with screenshots and instructions that implicitly assume a graphical desktop environment. There are no examples or instructions for obtaining the correlation ID using command-line tools such as Azure CLI, PowerShell, or REST API, which are commonly used on Linux/macOS. The absence of CLI or API instructions creates friction for users on non-Windows platforms, especially those who prefer or require automation.
Recommendations
  • Add instructions and examples for obtaining the correlation ID using Azure CLI (az monitor activity-log list) and/or REST API.
  • Include PowerShell examples for parity, but ensure CLI/API examples are presented first or alongside.
  • Clarify that the portal method works on any OS with a supported browser, but highlight automation-friendly alternatives.
  • Provide sample commands and expected output for Linux/macOS users.
GitHub Create Pull Request
Expressroute Configure custom alerts to monitor advertised routes - Azure ExpressRoute ...ain/articles/expressroute/how-to-custom-route-alert.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Azure PowerShell for automation, with all scripting and automation examples provided exclusively in PowerShell. There are no examples or guidance for using alternative scripting environments such as Azure CLI, Bash, or Python, which are more common on Linux/macOS. The reliance on PowerShell and the absence of cross-platform scripting options create friction for Linux/macOS users.
Recommendations
  • Provide equivalent examples using Azure CLI and/or Python for automation runbooks, as both are supported in Azure Automation and are cross-platform.
  • Explicitly mention that Azure Automation supports Python and Azure CLI runbooks, and link to relevant documentation.
  • Offer guidance or links for users who prefer Bash or other Linux-native scripting tools.
  • Reorder introductory sections to clarify that PowerShell is one option, not the only method.
  • Include a note or table comparing PowerShell, Python, and Azure CLI support in Azure Automation for route monitoring 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-14 00:00
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 towards Windows by exclusively referencing PowerShell for command-line migration steps and subnet management, with no mention of Azure CLI or Bash/Linux-native tools. All automation and scripting guidance is PowerShell-centric, which may create friction for Linux and macOS users who do not use PowerShell as their primary shell.
Recommendations
  • Provide equivalent Azure CLI (az) examples alongside PowerShell instructions for all migration and subnet management tasks.
  • Explicitly mention that PowerShell can be used cross-platform, or clarify if any steps require Windows-only features.
  • Add Bash or shell script snippets where appropriate, especially for common validation or monitoring tasks.
  • Ensure that all links to migration guides (e.g., 'migrate using PowerShell') have corresponding Azure CLI or cross-platform alternatives.
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-13 00:00
Reviewed by: LLM Analysis
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, with command-line examples exclusively in PowerShell. There are no CLI, Bash, or Linux-native instructions or examples, which may hinder Linux/macOS users who do not use PowerShell.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands.
  • Explicitly mention cross-platform options, such as using Azure CLI or REST API.
  • Clarify whether PowerShell steps can be run on Linux/macOS (with PowerShell Core), or provide alternatives.
  • Reorder or parallelize examples so that Linux/macOS-friendly options are presented alongside Windows/PowerShell instructions.
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-13 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 by listing PowerShell-based instructions and links prominently, with no mention of Linux/macOS CLI equivalents. The main guide focuses exclusively on the Azure portal UI, but when command-line instructions are referenced (e.g., for advanced IPv6 configuration), only PowerShell is mentioned. There are no Bash, Azure CLI, or Linux/macOS-specific examples or guidance.
Recommendations
  • Add equivalent Azure CLI (az) instructions for all PowerShell-based steps, especially for advanced scenarios like IPv6 configuration.
  • Include explicit references and links to Linux/macOS-compatible tooling and documentation.
  • When listing command-line options, present Azure CLI (cross-platform) before or alongside PowerShell, not after.
  • Clarify that PowerShell instructions can be run on Linux/macOS, or provide Bash/CLI alternatives where possible.
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-13 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 focused on Azure PowerShell for both creating and deleting ExpressRoute circuits, with all code examples and step-by-step instructions using PowerShell syntax. There are no CLI (bash) or Linux/macOS-specific examples, and PowerShell is presented as the primary method for template deployment, with alternatives (CLI, portal, REST) only mentioned in a brief note after the main walkthrough.
Recommendations
  • Add equivalent Azure CLI (bash) examples for creating and deleting ExpressRoute circuits, with step-by-step instructions.
  • Present both PowerShell and CLI examples side-by-side, or clearly indicate which instructions apply to which platforms.
  • Explicitly mention that Azure Cloud Shell supports both PowerShell and Bash, and provide guidance for Linux/macOS users.
  • Reorder or balance the documentation so that non-Windows methods are not relegated to a footnote.
GitHub Create Pull Request
Expressroute Configure custom alerts to monitor advertised routes - Azure ExpressRoute ...ain/articles/expressroute/how-to-custom-route-alert.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Azure PowerShell and assumes the use of PowerShell scripts and cmdlets throughout the automation process. There are no examples or guidance for using alternative scripting environments such as Azure CLI, Bash, or Python, which are more common on Linux/macOS platforms. The instructions and sample scripts are PowerShell-specific, and there is no mention of how Linux/macOS users might adapt or run these automations.
Recommendations
  • Provide equivalent Azure CLI or REST API examples for collecting ExpressRoute gateway route information, as Azure CLI is cross-platform and natively supported on Linux/macOS.
  • Include a note or section on how to author and run runbooks using Python (supported in Azure Automation) or Bash, with example scripts for the same monitoring logic.
  • Clarify whether the PowerShell runbooks can be authored and executed from non-Windows environments (e.g., using PowerShell Core on Linux/macOS), and provide setup instructions if so.
  • Where possible, use neutral language (e.g., 'automation script' instead of 'PowerShell script') and link to cross-platform tooling documentation.
  • Explicitly state any limitations or requirements for Linux/macOS users, and offer workarounds or alternatives.
GitHub Create Pull Request
Expressroute Planned maintenance guidance for ExpressRoute ...blob/main/articles/expressroute/planned-maintenance.md
Medium Priority View Details →
Scanned: 2026-01-13 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 Windows bias by exclusively referencing the Get-AzExpressRouteCircuitStats PowerShell command for traffic monitoring during failover validation, without providing equivalent Linux/macOS CLI examples. No cross-platform alternatives (such as Azure CLI or REST API) are mentioned, and the Windows-specific tool is introduced first and solely. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Include Azure CLI equivalents (e.g., az network express-route) for all PowerShell commands.
  • Reference REST API methods for ExpressRoute circuit statistics retrieval.
  • Explicitly mention cross-platform options and provide examples for Linux/macOS users.
  • Present Windows and Linux/macOS instructions side-by-side or in parallel sections.
  • Avoid assuming PowerShell is available on all platforms; clarify prerequisites for each tool.
GitHub Create Pull Request
Expressroute About ExpressRoute virtual network gateways ...ssroute/expressroute-about-virtual-network-gateways.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides only Azure PowerShell examples for gateway subnet creation, omitting equivalent Azure CLI or ARM template examples that would be more familiar to Linux/macOS users. References to PowerShell and REST APIs are present, but Linux-friendly tools and workflows are not demonstrated or mentioned. This creates friction for non-Windows users who may prefer Azure CLI or other cross-platform automation methods.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all resource creation and configuration steps.
  • Include ARM template snippets for infrastructure-as-code scenarios.
  • Explicitly mention that Azure CLI is cross-platform and provide links to relevant CLI documentation.
  • Ensure REST API references include examples of usage from Linux/macOS environments (e.g., curl, bash).
  • Review all code blocks and ensure parity between PowerShell and CLI examples.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page references Azure PowerShell as the only command-line configuration example, with no mention of Azure CLI or Linux/macOS-specific instructions. The 'Next steps' section lists Azure PowerShell before any cross-platform alternatives, and there are no Linux/macOS-specific tools or examples provided. This creates friction for users on non-Windows platforms who may prefer or require Azure CLI or Bash-based workflows.
Recommendations
  • Add Azure CLI examples alongside or before Azure PowerShell instructions, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that FastPath can be configured using Azure CLI, and provide a link to relevant documentation.
  • Ensure that all configuration steps are available for both Windows and Linux/macOS users, including screenshots or terminal examples where appropriate.
  • In the 'Next steps' section, list Azure CLI and portal options before or alongside PowerShell to avoid implying a Windows-first workflow.
GitHub Create Pull Request
Expressroute Azure ExpressRoute: Router configuration samples ...es/expressroute/expressroute-config-samples-routing.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Powershell Heavy
Summary
The documentation is focused on router configuration for Cisco IOS-XE and Juniper MX series, which are platform-agnostic. However, the only explicit reference to 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 provisioning. No Linux/macOS alternatives or parity guidance are provided.
Recommendations
  • Add instructions or references for configuring CAK/CKN values using Linux/macOS tools (e.g., Azure CLI, REST API, or other cross-platform methods).
  • Clarify whether PowerShell is required or if other platforms are supported for MACSec key provisioning.
  • Provide links or examples for Linux/macOS users to achieve the same 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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Azure ExpressRoute Direct exhibits a notable Windows bias in the onboarding section, where only Azure PowerShell commands are provided for subscription enrollment and resource provider registration. There are no equivalent Azure CLI (cross-platform) or Bash examples, nor is there guidance for Linux/macOS users. The rest of the page is platform-neutral, but the initial setup instructions create friction for non-Windows users.
Recommendations
  • Add Azure CLI examples alongside PowerShell for subscription enrollment and resource provider registration.
  • Explicitly mention that Azure CLI is supported and provide Bash/Linux/macOS command syntax.
  • Include links to cross-platform tooling documentation (e.g., Azure CLI installation and usage).
  • Consider presenting CLI examples first or side-by-side with PowerShell to signal equal support.
GitHub Create Pull Request
Expressroute Azure ExpressRoute: ARP tables - Troubleshooting ...e/expressroute-troubleshooting-arp-resource-manager.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively provides PowerShell cmdlets and instructions for viewing ARP tables on Azure ExpressRoute circuits. There are no examples or guidance for Linux/macOS users (e.g., using Azure CLI, Bash, or cross-platform tools), and the prerequisites specifically require the Azure PowerShell module. This creates a notable bias toward Windows environments.
Recommendations
  • Add equivalent instructions and examples using Azure CLI, which is cross-platform and works on Linux/macOS.
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide sample commands for ARP table retrieval.
  • If PowerShell is required for certain operations, clarify whether PowerShell Core (pwsh) is supported on Linux/macOS and provide installation guidance.
  • Reorder or supplement examples so that Linux/macOS users are not excluded or forced to use Windows tools.
GitHub Create Pull Request
Expressroute ExpressRoute for Cloud Solution Providers - Azure | Microsoft Docs ...ressroute/expressroute-for-cloud-solution-providers.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through the exclusive mention of PowerShell for ExpressRoute circuit routing configuration, and by referencing Windows-centric management APIs and documentation. There are no Linux or cross-platform CLI examples provided, nor are Linux-native tools or workflows mentioned. This may create friction for users on Linux or macOS who need to perform ExpressRoute management tasks.
Recommendations
  • Include Azure CLI examples alongside PowerShell for all configuration and management tasks, as Azure CLI is cross-platform.
  • Reference Linux/macOS-compatible tools and workflows where applicable, such as Bash scripts or REST API usage.
  • Ensure external links and API documentation do not exclusively target Windows or PowerShell, but also mention alternatives for other platforms.
  • Add explicit notes or sections for Linux/macOS users, outlining any differences or additional steps required.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides parity between Azure Portal, Azure CLI, and Azure PowerShell for most tasks. However, there is a notable bias toward PowerShell, especially in critical steps such as enabling IPv6 on zone-redundant gateways, where only PowerShell commands are provided and users are explicitly told to use PowerShell due to portal limitations. This assumes access to PowerShell, which is a Windows-centric tool, although it is available on Linux/macOS. Additionally, PowerShell examples and references are frequent, and in some sections, PowerShell is mentioned before CLI. There are no Linux/macOS-specific instructions or troubleshooting notes, and the documentation does not acknowledge differences in PowerShell usage across platforms.
Recommendations
  • Provide explicit Azure CLI alternatives for all PowerShell-only steps, especially where users are told to use PowerShell due to portal limitations.
  • Clarify that PowerShell Core is available cross-platform and provide installation guidance for Linux/macOS users.
  • Ensure that CLI examples are given equal prominence and are not secondary to PowerShell, especially in critical workflow steps.
  • Add troubleshooting notes or links for Linux/macOS users who may encounter issues running PowerShell scripts.
  • Consider adding bash or shell script examples for common tasks, or at least acknowledge their use.
GitHub Create Pull Request
Expressroute Configure ExpressRoute and S2S VPN coexisting connections: classic ...les/expressroute/expressroute-howto-coexist-classic.md
Medium Priority View Details →
Scanned: 2026-01-13 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 is heavily biased towards Windows and PowerShell. All configuration steps rely exclusively on Azure PowerShell cmdlets, with no mention of Linux/macOS alternatives such as Azure CLI, Bash, or cross-platform scripting. File paths use Windows conventions (e.g., C:\NetworkConfig.xml), and there are no examples or guidance for users on Linux or macOS. The installation instructions and workflow assume a Windows environment, creating friction for non-Windows users.
Recommendations
  • Provide equivalent instructions using Azure CLI, which is cross-platform and works on Linux/macOS.
  • Include Bash or shell script examples for key steps, especially for uploading configuration files and managing gateways.
  • Use generic or platform-neutral file path examples (e.g., /home/user/NetworkConfig.xml) alongside Windows paths.
  • Explicitly mention that the steps can be performed on Linux/macOS, and link to relevant installation guides for Azure CLI and PowerShell Core.
  • Add a section or callouts for Linux/macOS users, noting any differences or additional requirements.
GitHub Create Pull Request
Expressroute Azure ExpressRoute: Configure MACsec ...ain/articles/expressroute/expressroute-howto-macsec.md
Medium Priority View Details →
Scanned: 2026-01-13 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 or CLI equivalents. All examples, prerequisites, and troubleshooting steps assume use of PowerShell, which is natively a Windows tool. There is no guidance for users who prefer Bash, Azure CLI, or other cross-platform tools, nor any indication of how to perform these tasks on Linux or macOS.
Recommendations
  • Provide Azure CLI (az) examples alongside PowerShell for all configuration steps.
  • Explicitly mention that Azure PowerShell can be installed and used on Linux/macOS, or provide installation instructions for those platforms.
  • Add Bash script equivalents for secret creation, identity assignment, and ExpressRoute port configuration.
  • Clarify which steps are platform-agnostic and which require specific OS tools.
  • Reorder examples to present cross-platform (CLI) options first, or at least in parallel with PowerShell.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., permissions, module installation).
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-13 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 cmdlets for all configuration, verification, and management steps. There are no examples or instructions for using Azure CLI, REST API, or ARM templates, which are cross-platform and commonly used on Linux/macOS. The only tool referenced is PowerShell, which, while available on Linux, is not the default or preferred shell for many Linux/macOS users. There is no mention of Bash, Azure CLI, or other Linux-native workflows.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly state that PowerShell Core is available on Linux/macOS and provide installation instructions or a link.
  • Reference REST API or ARM template options for automation, which are platform-agnostic.
  • Where possible, provide Bash script examples or note any differences in command usage on Linux/macOS.
  • Reorganize sections to present cross-platform tools (like Azure CLI) before or alongside PowerShell.
GitHub Create Pull Request
Expressroute Azure ExpressRoute: Prerequisites ...in/articles/expressroute/expressroute-prerequisites.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page exhibits mild Windows bias by referencing Azure PowerShell commands as a prerequisite for ExpressRoute Direct enrollment, without mentioning cross-platform alternatives (such as Azure CLI or portal). PowerShell is most commonly associated with Windows, and its mention as the only method may create friction for Linux/macOS users. No explicit Windows-only tools or examples are present, but the lack of Linux/macOS parity in tooling references is notable.
Recommendations
  • Add instructions or references for using Azure CLI (which is cross-platform) to enroll subscriptions for ExpressRoute Direct.
  • Clarify whether the Azure Portal can be used for the same tasks, and provide links or steps.
  • Explicitly state that PowerShell is available on Linux/macOS, or link to installation guides for non-Windows platforms.
  • When mentioning command-line tools, present both PowerShell and CLI options side-by-side, or indicate which are cross-platform.
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-13 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 page demonstrates a strong Windows bias by exclusively providing Azure PowerShell command examples for all verification and troubleshooting steps. There are no CLI (az), Bash, or Linux/macOS-specific instructions or examples. The only explicit tool recommendation for connectivity testing is PsPing, a Windows-only Sysinternals utility, with no mention of Linux alternatives. All command-line guidance assumes a Windows environment, and Windows-centric tools and patterns are referenced before any cross-platform options.
Recommendations
  • Add equivalent Azure CLI (az) commands for all PowerShell examples, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash shell examples where appropriate, especially for basic network troubleshooting (e.g., using ping, traceroute, or tcpdump).
  • Suggest cross-platform connectivity testing tools such as hping, nping (from nmap), or standard ping/traceroute for Linux/macOS users, alongside PsPing.
  • Clearly indicate which commands/tools are Windows-only and provide Linux/macOS alternatives in parallel.
  • Consider reordering examples so that cross-platform solutions appear first or side-by-side with Windows-specific instructions.
GitHub Create Pull Request
Expressroute Azure ExpressRoute: Circuit configuration workflow ...b/main/articles/expressroute/expressroute-workflows.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references PowerShell as a method for verifying provisioning, but does not mention or provide examples for equivalent Linux/macOS tools (such as Azure CLI or Bash). No explicit Linux/macOS commands or workflow examples are provided, and Windows tooling is mentioned first and exclusively in the relevant step.
Recommendations
  • Explicitly mention Azure CLI and Bash as alternatives to PowerShell for provisioning verification.
  • Provide example commands for both PowerShell (Windows) and Azure CLI/Bash (Linux/macOS) wherever command-line interaction is referenced.
  • Ensure that all steps referencing tooling or commands include cross-platform instructions or links.
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-13 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 moderate Windows bias by providing migration instructions specifically for the Azure portal and PowerShell, with no mention of Linux-native tools (such as Azure CLI or Bash scripting). The FAQ and guidance for advanced subnet configuration explicitly state that certain features are only available via PowerShell, with no Linux or cross-platform alternatives provided. PowerShell is referenced before any cross-platform tooling, and Linux/macOS users are not given parity in migration instructions.
Recommendations
  • Add equivalent Azure CLI (az) examples and migration steps alongside PowerShell instructions, ensuring Linux/macOS users have clear guidance.
  • Where features are currently PowerShell-only, explicitly note this limitation and, if possible, provide workarounds or timelines for Azure CLI support.
  • In FAQs and step-by-step guides, present cross-platform options (Azure CLI, REST API, or ARM templates) before or alongside PowerShell.
  • Clarify whether PowerShell Core (pwsh) is supported on Linux/macOS for these tasks, and provide installation guidance if so.
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-13 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-specific workflows. All code examples are PowerShell-based, and the page references Windows-centric tools and patterns, creating friction for users on Linux or macOS platforms.
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 used in Azure Cloud Shell, which is available on all platforms, but clarify local installation requirements for Linux/macOS.
  • Add a section or notes for Linux/macOS users, including any platform-specific considerations or troubleshooting tips.
  • Ensure that documentation does not assume Windows as the default environment; present CLI/Bash examples before or alongside PowerShell.
GitHub Create Pull Request
← Previous Page 9 of 12 Next →