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 1-25 of 281 flagged pages
Expressroute Troubleshoot network link performance: Azure ExpressRoute ...te/expressroute-troubleshooting-network-performance.md
High Priority View Details →
Scanned: 2026-01-14 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 strong Windows bias: all step-by-step instructions, code samples, and toolkit usage are based on PowerShell and Windows-specific tools (AzureCT, PSPing). The installation paths, firewall instructions, and troubleshooting workflows are tailored for Windows environments, with only passing mention of Linux. No Linux-specific examples, commands, or tool usage are provided, making it difficult for Linux/macOS users to follow the documented process.
Recommendations
  • Provide equivalent Linux/macOS instructions for each step, including installation and usage of iPerf and other tools.
  • Offer Bash shell examples alongside PowerShell, especially for running performance tests.
  • Document Linux firewall configuration steps (e.g., using ufw, firewalld, or iptables) for opening necessary ports.
  • Clarify how to use iPerf and PSPing alternatives on Linux/macOS, and how to collect and interpret results.
  • If AzureCT is Windows-only, recommend cross-platform alternatives or document manual test procedures for Linux/macOS.
  • Include screenshots or output samples from Linux terminal sessions.
  • Reorder sections so that Windows and Linux instructions are presented with equal prominence.
GitHub Create Pull Request
Expressroute Troubleshoot network link performance: Azure ExpressRoute ...te/expressroute-troubleshooting-network-performance.md
High Priority View Details →
Scanned: 2026-01-13 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 is heavily biased toward Windows, with all core troubleshooting steps and examples using PowerShell, Windows-specific tools (PSPing, AzureCT PowerShell module), and Windows-centric installation paths and firewall instructions. Linux is mentioned only in passing, with no concrete Linux commands, examples, or parity guidance. Critical troubleshooting workflows (AzureCT usage, performance testing) are described exclusively for Windows, leaving Linux/macOS users without actionable steps.
Recommendations
  • Provide equivalent Linux/macOS instructions for installing and running iPerf and PSPing (or suitable alternatives) outside of PowerShell.
  • Document how to perform link performance tests using native Linux tools (e.g., bash scripts, iPerf commands, firewall configuration) and how to interpret results.
  • Offer a cross-platform version of the Azure Connectivity Toolkit, or clarify how Linux users can manually replicate its functionality.
  • Include Linux/macOS example commands and output formats alongside Windows/PowerShell examples.
  • Explicitly address Linux firewall configuration for iPerf and SSH, and provide troubleshooting steps for non-Windows hosts.
GitHub Create Pull Request
Expressroute Azure ExpressRoute: ARP tables - Troubleshooting ...e/expressroute-troubleshooting-arp-resource-manager.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively provides instructions and examples using PowerShell cmdlets, which are native to Windows environments. There are no equivalent examples or guidance for Linux users (e.g., using Azure CLI, Bash, or cross-platform tools). The prerequisites and troubleshooting steps assume the use of PowerShell, reinforcing a Windows-centric approach and omitting Linux parity.
Recommendations
  • Add equivalent instructions and examples using Azure CLI, which is cross-platform and commonly used on Linux and macOS.
  • Include guidance for viewing ARP tables using Bash scripts or other Linux-native tools where applicable.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, and provide installation steps if PowerShell usage is required.
  • Reorder or parallelize instructions so that Linux and Windows approaches are presented together, rather than Windows/PowerShell first.
  • Clarify tool compatibility and provide links to cross-platform documentation for ExpressRoute troubleshooting.
GitHub Create Pull Request
Expressroute Configure custom alerts to monitor advertised routes - Azure ExpressRoute ...ain/articles/expressroute/how-to-custom-route-alert.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on Azure PowerShell, with all automation and scripting examples provided exclusively in PowerShell. There is no mention of Bash, Azure CLI, or Linux-native scripting alternatives. The prerequisites and workflow steps assume familiarity with PowerShell, and there are no Linux or cross-platform examples or guidance. This creates a Windows-centric bias, potentially excluding users who prefer or require Linux-based automation.
Recommendations
  • Provide equivalent examples using Azure CLI and/or Bash scripts for runbook automation.
  • Explicitly mention that Azure Automation supports Python runbooks and link to relevant documentation.
  • Add a section comparing PowerShell and Azure CLI approaches, including pros/cons and platform compatibility.
  • Include Linux-specific setup notes, such as using Azure Cloud Shell (Bash) or running scripts from Linux VMs.
  • Clarify that the workflow can be adapted for non-Windows environments and provide sample scripts 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
High Priority View Details →
Scanned: 2026-01-11 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 providing migration instructions and examples exclusively for PowerShell, with no mention of Linux-native tools (such as Azure CLI or Bash scripting). The FAQ and procedural steps reference PowerShell as the only supported automation method for certain features (e.g., adding prefixes), and migration guidance is split between the Azure portal and PowerShell, with PowerShell listed before any Linux-compatible alternatives. There are no examples or explicit instructions for Linux users, nor is Azure CLI mentioned as an option.
Recommendations
  • Add equivalent migration instructions and examples using Azure CLI, which is cross-platform and widely used on Linux.
  • Where PowerShell is referenced as the only supported method (e.g., adding prefixes), clarify if Azure CLI or REST API support is planned or available.
  • Provide Bash script examples for common migration tasks to improve accessibility for Linux users.
  • Explicitly mention platform compatibility for each tool (e.g., 'PowerShell (Windows, Linux, macOS)' and 'Azure CLI (Windows, Linux, macOS)').
  • Ensure that documentation sections referencing automation or scripting do not default to PowerShell unless it is truly the only supported method, and provide parity for Linux users where possible.
GitHub Create Pull Request
Expressroute About Scalable Gateway ...cs/blob/main/articles/expressroute/scalable-gateway.md
High Priority View Details →
Scanned: 2026-01-11 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 a method for upgrading the gateway, mentioning it explicitly alongside the Azure portal. There is no mention of Azure CLI, Bash, or Linux-native tooling for configuration or upgrades. This suggests a Windows-first and PowerShell-heavy bias, with missing Linux examples for command-line operations.
Recommendations
  • Include Azure CLI examples for gateway upgrade and configuration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that configuration can be performed from Linux or macOS environments using Azure CLI or REST API, not just PowerShell.
  • Provide side-by-side examples for both PowerShell and Azure CLI where command-line instructions are given.
  • Review related content and ensure Linux parity in all referenced how-to guides.
GitHub Create Pull Request
Expressroute Azure ExpressRoute FastPath: Features, availability, and limitations ...docs/blob/main/articles/expressroute/about-fastpath.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for Azure ExpressRoute FastPath shows evidence of Windows bias. Configuration instructions are only linked for the Azure portal and Azure PowerShell, with no mention of Azure CLI or Linux-based configuration methods. PowerShell, a Windows-centric tool, is presented as the sole command-line example, and there are no Linux-specific or cross-platform instructions. This prioritizes Windows tooling and may hinder Linux users from easily following configuration steps.
Recommendations
  • Add configuration instructions using Azure CLI, which is cross-platform and widely used on Linux.
  • Explicitly mention that FastPath can be configured from Linux environments using Azure CLI or REST API.
  • Ensure all command-line examples are provided for both PowerShell and Azure CLI, with equal prominence.
  • Include links to Linux-specific setup guides or troubleshooting steps where relevant.
  • Review future documentation updates to avoid presenting Windows tools before or instead of Linux equivalents.
GitHub Create Pull Request
Expressroute About ExpressRoute virtual network gateways ...ssroute/expressroute-about-virtual-network-gateways.md
High Priority View Details →
Scanned: 2026-01-11 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 page demonstrates a Windows bias by providing only Azure PowerShell examples for gateway subnet creation, referencing PowerShell and REST API resources exclusively (with no mention of Azure CLI or Linux shell equivalents), and listing PowerShell before REST API in resource tables. There are no Linux or cross-platform command examples, and no mention of Linux-specific tools or patterns. This may hinder accessibility for users who primarily use Linux or prefer Azure CLI/bash.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all configuration steps, especially for gateway subnet creation.
  • Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.
  • Include bash shell script examples where appropriate to demonstrate cross-platform usage.
  • Reference Azure CLI documentation and commands in resource tables, giving equal prominence to PowerShell and CLI.
  • Review terminology to ensure that instructions and recommendations are not Windows-centric, and clarify cross-platform compatibility.
GitHub Create Pull Request
Expressroute About Azure ExpressRoute Direct ...n/articles/expressroute/expressroute-erdirect-about.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by exclusively providing Azure PowerShell commands for onboarding, with no equivalent examples for Linux users (such as Azure CLI or Bash). The onboarding instructions assume the use of PowerShell, which is native to Windows, and do not mention or prioritize cross-platform tools. There is no guidance for Linux or macOS users, nor are alternative command-line interfaces suggested.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all onboarding steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that onboarding can be performed from any OS, and provide instructions for both PowerShell and CLI.
  • Where possible, provide Bash script examples or note differences in command syntax for Linux/macOS environments.
  • Review other sections to ensure that tool recommendations and workflows do not assume a Windows environment by default.
GitHub Create Pull Request
Expressroute Configure customer-controlled maintenance for your virtual network gateway ...xpressroute/customer-controlled-gateway-maintenance.md
High Priority View Details →
Scanned: 2026-01-11 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 only Azure PowerShell examples for command-line configuration, with no mention of Azure CLI or Bash alternatives commonly used on Linux and macOS. The PowerShell steps are presented as the sole scripting option, and there is no guidance for Linux users or parity in tooling. The portal instructions are platform-neutral, but all automation and scripting guidance is Windows-centric.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, showing how to perform the same maintenance configuration steps using az commands.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Provide Bash script snippets or guidance for Linux automation where appropriate.
  • Ensure that references to command-line tools do not default to Windows/PowerShell unless there is a technical limitation.
  • Include a section or note on platform compatibility, clarifying which steps/tools work on Windows, Linux, and macOS.
GitHub Create Pull Request
Expressroute FAQ - Azure ExpressRoute | Microsoft Docs ...s/blob/main/articles/expressroute/expressroute-faqs.md
High Priority View Details →
Scanned: 2026-01-11 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 primarily through the frequent mention of PowerShell as a management tool, with instructions and links referencing PowerShell cmdlets and workflows. In sections describing how to change bandwidth, enable/disable features, or configure route filters, PowerShell is mentioned before or instead of Azure CLI or REST API. There are no explicit Linux or cross-platform command examples, and Linux-native tools or workflows are not referenced. This can make the documentation less accessible for users who prefer or require Linux-based management.
Recommendations
  • Add Azure CLI examples alongside PowerShell in all procedural sections, especially where PowerShell is currently referenced.
  • Explicitly mention REST API and Azure portal as cross-platform alternatives where applicable.
  • Where PowerShell cmdlets are referenced, provide equivalent Azure CLI commands or scripts.
  • Include notes or examples for Linux users, such as Bash scripts or CLI usage, to ensure parity.
  • Review linked articles (e.g., how-to-routefilter-powershell.md) and ensure they have Linux/Azure CLI coverage.
  • Avoid listing PowerShell before CLI unless there is a technical reason; consider presenting both together or in parallel.
GitHub Create Pull Request
Expressroute Azure ExpressRoute: Add IPv6 support for private peering ...n/articles/expressroute/expressroute-howto-add-ipv6.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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, but PowerShell (a Windows-centric tool) is given equal or greater prominence than CLI, and is referenced for steps where the portal is incomplete. Several instructions and notes specifically direct users to use PowerShell, and there are no Linux-specific shell examples (e.g., Bash). The use of PowerShell cmdlets and references to PowerShell Cloud Shell reinforce a Windows bias, as PowerShell is most commonly used on Windows, despite its cross-platform availability. There are no references to Linux-native tools, nor are Bash or other Linux shell examples provided.
Recommendations
  • Add Bash shell examples alongside Azure CLI commands to demonstrate Linux parity.
  • When referencing command-line instructions, clarify that Azure CLI can be used from Bash/Linux environments and provide explicit Bash syntax where appropriate.
  • Avoid recommending PowerShell as the fallback when portal functionality is incomplete; instead, suggest Azure CLI (which is cross-platform) as the default automation tool.
  • Include notes or sections highlighting Linux compatibility and usage patterns, such as using Azure CLI in Bash or Zsh.
  • If PowerShell is referenced, clarify its cross-platform availability and provide installation instructions for Linux and macOS, not just Windows.
  • Review and balance the order of examples so that CLI/Bash instructions are presented before or alongside PowerShell, rather than after.
GitHub Create Pull Request
Expressroute ExpressRoute for Cloud Solution Providers - Azure | Microsoft Docs ...ressroute/expressroute-for-cloud-solution-providers.md
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates Windows bias in several ways: it references PowerShell as the primary method for managing and modifying ExpressRoute routing, links to Windows-specific management APIs, and omits Linux CLI or cross-platform examples for ExpressRoute configuration and management. Windows tools and terminology are mentioned exclusively or before any Linux equivalents, and there is a lack of parity in guidance for Linux-based environments.
Recommendations
  • Add Azure CLI and/or REST API examples for ExpressRoute configuration and management, alongside PowerShell examples.
  • Include explicit instructions and code samples for Linux and macOS users, such as using Bash scripts or Azure CLI.
  • Reference cross-platform management tools and avoid linking only to Windows-specific documentation.
  • Ensure that any mention of PowerShell is balanced with equivalent Azure CLI or other cross-platform tool guidance.
  • Review linked resources to confirm they are not Windows-only and provide Linux parity where possible.
GitHub Create Pull Request
Expressroute Configure a virtual network gateway for ExpressRoute using the Azure portal ...expressroute-howto-add-gateway-portal-resource-manager.md
High Priority View Details →
Scanned: 2026-01-11 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 prioritizing Azure portal and PowerShell instructions, with explicit references to PowerShell for advanced configuration (e.g., IPv6-based private peering). There are no examples or guidance for Linux users (such as Azure CLI or Bash), and the only command-line instructions referenced are for PowerShell, which is traditionally associated with Windows environments. The navigation selector and important notes exclusively mention PowerShell, omitting Linux-native tooling.
Recommendations
  • Add equivalent Azure CLI (az) instructions for all PowerShell examples, especially for advanced scenarios like IPv6-based private peering.
  • Update navigation selectors to include 'Resource Manager - Azure CLI' and 'Classic - Azure CLI' where applicable.
  • Ensure screenshots and step-by-step instructions are platform-neutral or provide parallel examples for Linux/macOS users.
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide links to relevant CLI documentation.
  • Review all 'Important' and 'Note' callouts to ensure Linux users are not excluded from advanced configuration guidance.
GitHub Create Pull Request
Expressroute Configure ExpressRoute and S2S VPN coexisting connections: classic ...les/expressroute/expressroute-howto-coexist-classic.md
High Priority View Details →
Scanned: 2026-01-11 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 and code samples use Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native tools. There are no examples or instructions for performing these tasks on Linux or macOS platforms, nor is there guidance for users who prefer cross-platform or non-Windows environments. The installation instructions and workflow assume a Windows environment, referencing file paths like 'C:\NetworkConfig.xml' and omitting alternatives for Linux or macOS.
Recommendations
  • Add equivalent Azure CLI examples for each PowerShell command, with clear instructions for Linux/macOS users.
  • Include notes or sections on how to perform the same configuration using Bash or shell scripts.
  • Reference cross-platform tools and workflows, such as using Azure CLI or REST API, and provide sample commands.
  • Mention file path conventions for Linux/macOS (e.g., '/home/user/NetworkConfig.xml') alongside Windows paths.
  • Clarify that PowerShell Core is available on Linux/macOS, and provide guidance for its use if PowerShell is required.
  • Ensure installation instructions cover both Windows and Linux/macOS environments, including package managers and prerequisites.
GitHub Create Pull Request
Expressroute Link a virtual network to ExpressRoute circuits - Azure portal ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/expressroute/expressroute-howto-linkvnet-portal-resource-manager.md
High Priority View Details →
Scanned: 2026-01-11 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 the Azure portal and PowerShell instructions before Azure CLI, and by providing detailed steps only for the Azure portal (a GUI-centric, Windows-preferred tool). While the top selector mentions Azure CLI, the main content does not provide any CLI examples or Linux-specific guidance. There is no mention of Linux tools, shell commands, or parity for non-Windows users, and PowerShell (a Windows-native tool) is given prominence both in the selector and in linked articles.
Recommendations
  • Add explicit Azure CLI step-by-step instructions alongside portal and PowerShell examples, ensuring parity for Linux and macOS users.
  • Include bash shell examples for common operations, such as creating connections and managing authorizations.
  • Reference Linux-friendly tools and workflows (e.g., az CLI, bash scripting) in the prerequisites and throughout the guide.
  • Ensure that all screenshots and walkthroughs are not exclusively tied to Windows environments or the Azure portal, and clarify cross-platform compatibility.
  • Reorder example selectors to present Azure CLI before PowerShell, or present both equally, to avoid Windows-first perception.
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
High Priority View Details →
Scanned: 2026-01-11 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 strong Windows bias by exclusively providing Azure PowerShell examples for both provisioning and deleting ExpressRoute circuits. There are no examples using Azure CLI, Bash, or other Linux-friendly tools. The workflow instructions and code blocks assume the user is operating in a PowerShell environment, which is native to Windows and less common on Linux. While alternative deployment methods (Azure CLI, REST API, Portal) are mentioned, no examples or guidance are provided for these methods.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands shown, including circuit creation and deletion.
  • Include Bash shell instructions for Linux users, especially for steps involving Cloud Shell.
  • Present CLI and PowerShell examples side-by-side or in parallel sections to ensure parity.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for selecting the preferred shell.
  • Review and update workflow steps to avoid assumptions about the user's operating system or shell environment.
GitHub Create Pull Request
Expressroute Azure ExpressRoute: Configure MACsec ...ain/articles/expressroute/expressroute-howto-macsec.md
High Priority View Details →
Scanned: 2026-01-11 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, code samples, and tool references are exclusively provided using Azure PowerShell cmdlets, with no mention of Linux equivalents (such as Azure CLI or Bash scripting). There is no guidance for users working on Linux or macOS platforms, nor any cross-platform alternatives for the described procedures.
Recommendations
  • Add equivalent Azure CLI (az) commands for all PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that the configuration steps can be performed on Linux/macOS using Azure CLI or Bash, and provide links to relevant setup guides.
  • Include a section on prerequisites for Linux/macOS users, such as installing Azure CLI and authenticating via az login.
  • Where PowerShell modules are referenced, provide alternative instructions for Azure CLI or REST API usage.
  • Ensure that troubleshooting and connectivity verification steps include Linux-friendly tools and commands (e.g., using tcpdump, iproute2, or curl).
GitHub Create Pull Request
Expressroute Azure ExpressRoute: Configure Global Reach ...es/expressroute/expressroute-howto-set-global-reach.md
High Priority View Details →
Scanned: 2026-01-11 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, Bash, or cross-platform scripting tools. The only tooling mentioned is Azure PowerShell, which is traditionally associated with Windows environments, though it is now cross-platform. There is no mention of Linux-specific workflows or parity in command-line tooling.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all PowerShell cmdlets, as Azure CLI is widely used on Linux and macOS.
  • Explicitly mention that Azure PowerShell is cross-platform, and provide installation instructions for Linux/macOS if PowerShell is required.
  • Include Bash script examples or guidance for users who prefer shell scripting on Linux.
  • Where possible, provide a table or section comparing PowerShell and Azure CLI commands for each operation.
  • Clarify any limitations or differences in functionality between PowerShell and CLI for ExpressRoute Global Reach.
GitHub Create Pull Request
Expressroute Azure ExpressRoute: Circuit configuration workflow ...b/main/articles/expressroute/expressroute-workflows.md
High Priority View Details →
Scanned: 2026-01-11 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 a verification method and does not mention Linux-specific tools or provide CLI examples alongside PowerShell. The order of tool mentions (PowerShell, Azure portal, CLI) puts Windows-centric tooling first, and there are no explicit Linux or cross-platform command examples. This may make the workflow less accessible to Linux users and reinforce a Windows-centric approach.
Recommendations
  • Include Azure CLI examples for all steps where PowerShell is referenced, and present CLI before or alongside PowerShell to emphasize cross-platform support.
  • Explicitly mention Linux and macOS compatibility in verification and configuration steps.
  • Add references to Linux-native tools (such as bash, curl, etc.) where appropriate for connectivity and provisioning checks.
  • Review all workflow steps to ensure parity in instructions for both Windows and Linux users, avoiding implicit prioritization of Windows tools.
GitHub Create Pull Request
Expressroute Azure ExpressRoute: Prerequisites ...in/articles/expressroute/expressroute-prerequisites.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias primarily by referencing Azure PowerShell commands as the prerequisite method for ExpressRoute Direct enrollment, without mentioning or providing equivalent Azure CLI or Linux-native instructions. No Linux-specific tools or examples are given, and the only command-line tooling referenced is PowerShell, which is traditionally associated with Windows environments. This may make the documentation less accessible or immediately useful for users on Linux or macOS platforms.
Recommendations
  • Add Azure CLI instructions alongside PowerShell for all command-line steps, especially for ExpressRoute Direct enrollment.
  • Explicitly mention cross-platform support for Azure management tools, including links to Linux/macOS installation guides for Azure CLI and PowerShell.
  • Where PowerShell is referenced, clarify that it is available on Linux and macOS, or provide alternative examples using Bash/Azure CLI.
  • Review all procedural steps to ensure parity between Windows and Linux environments, and add troubleshooting notes for common Linux-specific issues if relevant.
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
High Priority View Details →
Scanned: 2026-01-11 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. All command-line examples for ExpressRoute verification, configuration, and troubleshooting use Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native tools. The only traffic test tool referenced is PsPing, a Windows-only utility. There are no Linux equivalents or cross-platform alternatives provided, and Windows-centric tools and patterns are presented exclusively and before any Linux options (which are absent).
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line tasks, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Linux-native tools for network testing, such as 'ping', 'traceroute', 'nc', or 'iperf', and show how to use them for ExpressRoute troubleshooting.
  • Reference cross-platform alternatives to PsPing, such as 'hping3', 'iperf', or 'nmap', and provide example usage.
  • Explicitly state that the troubleshooting steps can be performed from Linux and macOS environments, not just Windows.
  • Where screenshots or instructions reference Windows-only tools, add equivalent steps for Linux (e.g., using Bash, terminal commands, or Linux desktop environments).
  • Review and update any portal instructions to clarify that the Azure portal is accessible from any OS/browser.
GitHub Create Pull Request
Expressroute Troubleshoot network link performance: Azure ExpressRoute ...te/expressroute-troubleshooting-network-performance.md
High Priority View Details →
Scanned: 2026-01-11 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 strong Windows bias. All example commands use PowerShell, and the Azure Connectivity Toolkit (AzureCT) is presented as a PowerShell module with installation and usage instructions only for Windows. The supporting tools (iPerf, PSPing) are described in the context of Windows, with installation paths and firewall instructions specific to Windows (e.g., C:\ACTTools, Windows Firewall). There are no Linux shell or CLI examples, and Linux usage is only mentioned in passing (e.g., 'the other host can be Linux'), without any concrete guidance or parity in troubleshooting steps or tool usage.
Recommendations
  • Provide equivalent Linux instructions for installing and running iPerf and PSPing, including example shell commands and typical installation paths.
  • Include Linux-specific troubleshooting steps, such as opening ports with iptables/firewalld and running iPerf in server/client mode on Linux.
  • Document how to use AzureCT or alternative tools on Linux, or clarify cross-platform alternatives if AzureCT is Windows-only.
  • Offer example output from Linux command-line tools to match the PowerShell output shown.
  • Ensure that both Windows and Linux are treated as first-class platforms in all sections, especially in step-by-step guides and tool recommendations.
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-11 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 migration instructions before any mention of Linux or cross-platform alternatives. There are no explicit CLI (az) or Bash examples, and troubleshooting steps do not reference Linux tools or workflows. The 'Next steps' section prioritizes PowerShell, which is traditionally a Windows-centric tool, and omits Azure CLI or Bash guidance, leaving Linux users without parity in migration instructions.
Recommendations
  • Add Azure CLI (az) and Bash examples for migration and troubleshooting steps alongside PowerShell instructions.
  • In the 'Next steps' section, include links to migration guides using Azure CLI and Bash, not just PowerShell.
  • Ensure troubleshooting steps reference cross-platform tools and workflows, not just Windows-centric ones.
  • Where PowerShell is mentioned, clarify that it is available cross-platform, or provide equivalent Linux-native instructions.
  • Review and update all code samples and operational guidance to ensure Linux users have clear, supported paths for all documented procedures.
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-11 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 and management steps, with no mention of Azure CLI, Bash, or Linux-native tools. All code samples are PowerShell-based, and the workflow assumes a Windows or PowerShell environment, which may disadvantage 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 and macOS.
  • Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI or Bash, and link to relevant CLI documentation.
  • Add a section comparing PowerShell and CLI workflows, helping users choose the best tool for their environment.
  • Avoid language that implies PowerShell is the only or preferred method; present CLI and PowerShell options side-by-side where possible.
GitHub Create Pull Request
← Previous Page 1 of 12 Next →