Route Server

20
Total Pages
15
Linux-Friendly Pages
5
Pages with Bias
25.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (8)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/route-server/tutorial-protect-route-server-ddos.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples. There are no references to Windows-specific tools or PowerShell, but there are also no CLI examples (such as Azure CLI or Bash scripts) that would support Linux or cross-platform users. This omission can be considered a bias of omission, as Linux users often prefer or require CLI-based instructions.
Recommendations:
  • Add equivalent Azure CLI (az) command examples for each major step, alongside or after the portal instructions.
  • Explicitly mention that all steps can be performed using the Azure CLI or PowerShell, and provide links to relevant documentation.
  • Ensure that any scripts or automation examples are provided in both PowerShell and Bash where appropriate.
  • Include a section or callout for 'Command-line alternative' for users who prefer not to use the portal.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/route-server/route-server-faq.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy
Summary:
The documentation page for Azure Route Server FAQ demonstrates subtle Windows bias. The 'Next steps' section links only to a PowerShell-based quickstart, which is Windows-centric, and there are no Linux or cross-platform CLI examples or references. The documentation does not mention or provide parity for Linux tools or workflows, nor does it reference the Azure CLI, which is cross-platform. This may make it less accessible or welcoming for Linux users.
Recommendations:
  • Add links to cross-platform Azure CLI (az) quickstart and configuration guides alongside or before PowerShell guides.
  • Ensure that all example commands and scripts are provided in both PowerShell and Azure CLI/bash formats.
  • Explicitly mention that Azure Route Server can be managed from Linux/macOS using the Azure CLI, and provide relevant documentation links.
  • Review all 'Next steps' and instructional links to ensure Linux users are not excluded or made to feel secondary.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/route-server/quickstart-create-route-server-template.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for deploying and cleaning up resources, referencing PowerShell cmdlets and output screenshots, and not including equivalent Azure CLI (cross-platform) or Bash examples. The instructions and screenshots are tailored to a Windows/PowerShell workflow, with no Linux-specific or cross-platform guidance.
Recommendations:
  • Add Azure CLI examples (using Bash or Cloud Shell) alongside PowerShell for all deployment and cleanup steps.
  • Include screenshots and instructions that are not specific to PowerShell or Windows environments.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide guidance for both.
  • Ensure that references to tools and commands are balanced between Windows and Linux/cross-platform options.
  • Where possible, provide a tabbed interface or clear separation for PowerShell and CLI/Bash instructions, so users can follow the workflow appropriate for their environment.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/route-server/tutorial-protect-route-server-ddos.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples. There is no explicit Windows bias (e.g., PowerShell or Windows tools), but there is a lack of parity for users who prefer or require CLI-based workflows, such as those on Linux or macOS. No Azure CLI, Bash, or cross-platform scripting examples are provided.
Recommendations:
  • Add equivalent Azure CLI examples for each major step (creating DDoS protection plan, Route Server, enabling DDoS, peering, cleanup).
  • Ensure CLI examples are cross-platform (work on Linux, macOS, and Windows).
  • Where appropriate, provide Bash scripts or command snippets alongside portal instructions.
  • Explicitly mention that all steps can be performed via CLI and link to relevant CLI documentation.
  • Consider including PowerShell examples only if Azure CLI and Bash are also provided, and present them in parallel.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/route-server/overview.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy
Summary:
The documentation page for Azure Route Server exhibits subtle Windows bias. In the 'Related content' section, the only quickstart linked is for creating an Azure Route Server using PowerShell, which is primarily a Windows tool. There are no equivalent Linux or cross-platform CLI examples or quickstarts referenced. The documentation does not mention or provide examples using Azure CLI, Bash, or Linux-native tools, nor does it clarify that PowerShell Core is cross-platform. This may give the impression that Windows or PowerShell is the preferred or only supported environment.
Recommendations:
  • Add links to quickstarts and tutorials that use Azure CLI and/or Bash, which are cross-platform and commonly used on Linux.
  • If PowerShell is referenced, clarify whether PowerShell Core (cross-platform) is supported, and consider providing both Windows PowerShell and Bash/Azure CLI examples side by side.
  • Ensure that all example commands and deployment instructions are available for both Windows and Linux users.
  • Review related content and ensure parity in guidance for both Windows and Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/route-server/quickstart-create-route-server-template.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for deploying and cleaning up resources, referencing PowerShell-specific cmdlets, and omitting equivalent Azure CLI (cross-platform) or Bash examples. The workflow and screenshots are tailored to PowerShell users, with no Linux or Bash alternatives presented or mentioned first.
Recommendations:
  • Add Azure CLI (az) examples alongside PowerShell for all deployment and cleanup steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention both PowerShell and CLI options in the deployment instructions, ideally presenting them in parallel sections or tabs.
  • Include Bash shell usage instructions for Linux/macOS users, especially for Cloud Shell.
  • Balance screenshots and output examples to include both PowerShell and CLI outputs.
  • In the 'Deploy the template' and 'Clean up resources' sections, provide both PowerShell and CLI code blocks, and clarify that users can choose either based on their environment.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/route-server/peer-route-server-with-virtual-appliance.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation is heavily biased towards Windows. It exclusively demonstrates deploying a Windows Server VM as the NVA, uses only Windows Server tools (e.g., RRAS, PowerShell cmdlets), and provides no guidance or examples for Linux-based NVAs or BGP configuration using Linux tools. All command-line examples are in PowerShell, and there is no mention of Linux alternatives or parity.
Recommendations:
  • Add a parallel section for deploying a Linux-based NVA (e.g., Ubuntu or CentOS) and configuring BGP using common Linux routing daemons such as FRRouting (FRR), Quagga, or Bird.
  • Provide Linux command-line examples (e.g., using apt/yum to install routing software, editing configuration files, and using vtysh or birdc to configure BGP peers).
  • Include screenshots or instructions for connecting to a Linux VM (e.g., SSH) and configuring the firewall appropriately.
  • Explicitly mention that both Windows and Linux NVAs are supported, and link to relevant Linux documentation.
  • Where PowerShell/Azure CLI is used, provide equivalent Bash/Azure CLI commands for Linux users.
  • Clarify that RRAS is not supported in production and recommend production-grade NVA solutions for both Windows and Linux.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/route-server/route-server-faq.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy
Summary:
The documentation page demonstrates a Windows bias primarily through its 'Next steps' section, which links exclusively to a PowerShell-based quickstart, without mentioning or linking to equivalent Linux/CLI/Bash examples. There are no command-line examples in the FAQ itself, but the only configuration guidance provided is Windows-centric. No Linux tools, patterns, or examples are referenced, and the documentation does not mention Azure CLI or Bash scripting, which are common on Linux.
Recommendations:
  • Provide links to both PowerShell and Azure CLI (cross-platform) quickstart/configuration guides in the 'Next steps' section.
  • Ensure that all example commands and scripts throughout the documentation are available in both PowerShell and Azure CLI/Bash formats.
  • Explicitly mention that Azure Route Server can be managed from Linux/macOS using Azure CLI, and provide relevant documentation links.
  • Review related documentation to ensure Linux users are equally supported and not required to use Windows-specific tools.