Internet Peering

23
Total Pages
15
Linux-Friendly Pages
8
Pages with Bias
34.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (18)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/prerequisites.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools
Summary:
The documentation page references associating Peer ASN to an Azure Subscription with a link to a PowerShell-specific guide (howto-subscription-association-powershell.md), but does not mention or provide equivalent instructions for Linux users (e.g., using Azure CLI or Bash). There is an implicit bias towards Windows/PowerShell tooling, and Linux-native methods are omitted.
Recommendations:
  • Add explicit instructions or links for associating Peer ASN using Azure CLI, which is cross-platform and commonly used on Linux.
  • Wherever PowerShell is referenced, ensure that equivalent steps for Bash/Azure CLI are provided and linked.
  • In the 'Related content' section, include links to guides that use Azure CLI or REST API, not just Azure Portal or PowerShell.
  • Review all prerequisite steps to ensure that no step assumes a Windows environment or tool by default.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/walkthrough-exchange-all.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example
Summary:
The documentation references the use of a PowerShell cmdlet for deleting exchange peering, but does not provide equivalent instructions or examples for Linux users (e.g., using Azure CLI or REST API). No Linux-specific tools or cross-platform command-line examples are mentioned, and the only command-line reference is Windows-centric.
Recommendations:
  • Provide equivalent Azure CLI commands for managing exchange peering, including deletion, alongside PowerShell instructions.
  • Explicitly mention cross-platform tools (such as Azure CLI and REST API) in all procedural steps where PowerShell is referenced.
  • Add examples or notes for Linux/macOS users to ensure parity and inclusivity.
  • Where possible, present cross-platform (CLI/REST) examples before or alongside Windows/PowerShell examples to avoid Windows-first bias.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/walkthrough-direct-all.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by referencing only PowerShell-based instructions for creating or modifying a direct peering, without providing equivalent CLI or Linux-native examples. The guidance assumes the use of PowerShell cmdlets and does not mention or link to Azure CLI or REST API alternatives, which are more platform-agnostic and commonly used on Linux/macOS. There is no mention of Linux tools or workflows, and the only command-line reference is to PowerShell.
Recommendations:
  • Provide parallel instructions using Azure CLI (az peering ...) for all PowerShell-based steps.
  • Explicitly mention that both PowerShell and Azure CLI/REST API can be used, and link to relevant documentation for each.
  • Include example commands for Linux/macOS users, ensuring parity in guidance and screenshots where applicable.
  • Avoid language that assumes the use of Windows or PowerShell as the default environment.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/prerequisites.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools
Summary:
The documentation page references associating Peer ASN to an Azure subscription and links only to a PowerShell-based guide (howto-subscription-association-powershell.md), with no mention of Linux or cross-platform alternatives such as Azure CLI or REST API. This suggests a bias towards Windows tooling and omits guidance for Linux users.
Recommendations:
  • Provide equivalent instructions for associating Peer ASN using Azure CLI, which is cross-platform and widely used on Linux.
  • Include references or links to REST API or ARM template methods for associating Peer ASN, if available.
  • Explicitly mention that PowerShell instructions are for Windows and provide alternative steps for Linux/macOS users.
  • Ensure that all procedural documentation includes both Windows (PowerShell) and Linux (CLI/REST) examples where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/howto-subscription-association-portal.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation exclusively describes how to associate an ASN with an Azure subscription using the Azure portal, which is a web-based GUI. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), nor are there any references to Linux or cross-platform tools. The portal-centric approach implicitly favors Windows users, as historically the Azure portal and related documentation have been more closely aligned with Windows workflows. There is no mention of Linux, macOS, or cross-platform command-line alternatives.
Recommendations:
  • Add step-by-step instructions for associating an ASN using the Azure CLI, which is cross-platform and works on Windows, Linux, and macOS.
  • If PowerShell examples are added, ensure equivalent Azure CLI (bash-friendly) examples are provided and presented first or side-by-side.
  • Explicitly mention that the Azure portal is accessible from any modern browser on any OS, to avoid the impression of Windows exclusivity.
  • Include troubleshooting or scripting guidance for Linux users, such as using curl or az commands for automation.
  • Consider adding a section on how to perform the same tasks using ARM templates or REST API calls, which are OS-agnostic.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/overview.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a bias towards Windows by referencing Azure PowerShell as the primary automation tool for setting up peering, with no mention of Linux-native tools, Azure CLI, or cross-platform alternatives. There are no examples or instructions for Linux users, and the only automation method mentioned is PowerShell, which is traditionally associated with Windows environments.
Recommendations:
  • Include Azure CLI instructions and examples alongside or before PowerShell, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that PowerShell Core is available on Linux if PowerShell examples are retained, and provide installation guidance.
  • Add Linux-specific or cross-platform setup steps and tooling references to ensure parity for non-Windows users.
  • Review all walkthroughs and related content to ensure that Linux and macOS users are equally supported in setup and management tasks.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/walkthrough-exchange-all.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example
Summary:
The documentation references running a PowerShell cmdlet to delete the exchange peering, but does not provide equivalent instructions or examples for Linux users (e.g., using Azure CLI or Bash). No Linux tools or cross-platform command examples are mentioned, and the only command-line reference is Windows-specific.
Recommendations:
  • Provide equivalent Azure CLI or Bash command examples for managing exchange peerings, including deletion, alongside or instead of PowerShell instructions.
  • Explicitly mention cross-platform tools (such as Azure CLI) that can be used from Linux, macOS, or Windows.
  • Avoid referencing only PowerShell cmdlets in important notes; instead, generalize the warning or provide parallel guidance for other platforms.
  • Include a section or table comparing management options (PowerShell, Azure CLI, Portal) for different operating systems.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/walkthrough-communications-services-partner.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation is heavily Azure portal-centric and does not provide any command-line examples or automation options for either Windows (e.g., PowerShell) or Linux (e.g., Azure CLI, Bash). However, the absence of Linux-specific instructions or examples (such as Azure CLI commands) means Linux users are underserved, especially since the FAQ explicitly states that only the Azure portal is supported and no API or CLI options are available.
Recommendations:
  • Add equivalent Azure CLI (cross-platform) instructions for all portal-based steps, enabling Linux and macOS users to automate or script the process.
  • If certain features are only available via the portal, clearly state this limitation and provide a roadmap or guidance for when CLI/API support will be available.
  • Include references to automation options (such as ARM templates, Bicep, or Terraform) where possible, to support infrastructure-as-code workflows common on Linux.
  • Ensure that any screenshots or UI instructions are supplemented with text-based alternatives for accessibility and cross-platform parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/walkthrough-exchange-route-server-partner.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools
Summary:
The documentation exclusively describes configuration steps using the Azure portal UI, with no command-line examples or automation options provided. There are no references to PowerShell, Windows, or Linux tools, but the lack of CLI or API guidance means Linux users (who may prefer Azure CLI or REST API) are underserved. The only tool mentioned for configuration is the Azure portal, which is a web-based GUI and not platform-specific, but the absence of CLI/API parity is a subtle bias toward GUI-centric (often Windows-first) workflows.
Recommendations:
  • Add equivalent Azure CLI commands for all major configuration steps (e.g., associating ASN, creating peering, registering ASN).
  • Provide REST API examples for automation and cross-platform parity.
  • Explicitly mention that the Azure portal is web-based and platform-agnostic, but offer links or examples for users who prefer command-line or scripted workflows.
  • Include a note about PowerShell and Azure CLI support, and provide links to relevant documentation for both.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/walkthrough-peering-service-all.md [View Details]
Scanned: 2025-07-12 23:44 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation exclusively references the Azure portal UI for all configuration steps and does not provide any command-line examples, such as PowerShell, Azure CLI, or Bash. While this avoids explicit Windows/Powershell bias, it still presents a bias by omitting Linux-friendly workflows (e.g., Azure CLI/Bash) and focusing solely on the graphical portal, which is more commonly associated with Windows environments. There is also no mention of Linux tools or command-line automation, and the FAQ confirms that only the portal is supported, with no API or CLI options.
Recommendations:
  • Add equivalent Azure CLI examples for all portal-based steps, ensuring commands are shown in Bash syntax for Linux users.
  • Explicitly mention platform-agnostic tools (e.g., Azure CLI) where possible, and clarify any limitations.
  • If certain actions are only available in the portal, state this clearly and provide a roadmap or alternatives for Linux/CLI users.
  • Include screenshots or instructions for using the Azure CLI in both Windows (PowerShell) and Linux (Bash) environments, if/when CLI support becomes available.
  • Monitor for future API/CLI support and update documentation promptly to ensure Linux parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/walkthrough-peering-service-all.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a bias toward Windows by exclusively referencing the Azure portal (a web-based GUI) for all configuration steps, with no mention of command-line alternatives such as Azure CLI, PowerShell, or REST API. There are no Linux-specific instructions or examples, and the only configuration method mentioned is the Azure portal, which is commonly associated with Windows-centric workflows. Additionally, the FAQ explicitly states that there is currently no API support and that configuration can only be performed via the Azure portal, further limiting options for Linux or automation-focused users.
Recommendations:
  • Add step-by-step instructions for performing all configuration tasks using Azure CLI, which is cross-platform and widely used on Linux.
  • If possible, provide REST API examples for automation and parity with non-GUI workflows.
  • Include PowerShell examples only if they are complemented by equivalent Azure CLI or REST API instructions.
  • Clarify any platform dependencies for the Azure portal, and ensure that Linux users are not disadvantaged.
  • Update the FAQ and main content when API or CLI support becomes available, to encourage automation and cross-platform parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/walkthrough-exchange-route-server-partner.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools
Summary:
The documentation exclusively describes configuration steps using the Azure portal (a web GUI), without providing any command-line examples or automation options. There are no references to CLI tools (such as Azure CLI or PowerShell), but also no Linux-specific guidance or parity. The FAQ explicitly states that there is no API support and that configuration can only be done via the Azure portal, which may disadvantage users who prefer or require CLI/automation, especially on Linux systems. There are no PowerShell-specific examples, but the lack of Linux/CLI parity is a notable bias.
Recommendations:
  • Add equivalent instructions for performing these tasks using the Azure CLI (az), which is cross-platform and widely used on Linux.
  • Where possible, provide REST API examples or scripts (even if limited), or clarify roadmap for API/CLI support.
  • Explicitly mention that the Azure portal is web-based and accessible from any OS, but highlight any limitations for Linux users if present.
  • If PowerShell or Windows tools are not required, clarify this to reassure Linux users.
  • Monitor for future CLI/API support and update documentation to include Linux-friendly automation options as soon as available.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/walkthrough-exchange-all.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation references PowerShell cmdlets for deleting exchange peering, but does not mention equivalent Linux/CLI tools or provide cross-platform examples. There is an implicit assumption that users are operating in a Windows/PowerShell environment, with no guidance for Linux or macOS users.
Recommendations:
  • Include Azure CLI examples alongside PowerShell cmdlets for all operations, especially for deleting exchange peering.
  • Explicitly mention cross-platform tools and provide command-line instructions that work on Linux and macOS.
  • Add a section or note clarifying that all tasks can be performed using Azure CLI or REST API, and link to relevant documentation.
  • Avoid assuming PowerShell is the default or only supported tool; present both Windows and Linux options equally.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/howto-subscription-association-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation exclusively describes how to associate an ASN with an Azure subscription using the Azure portal, with all instructions and screenshots based on the web interface. There are no command-line examples provided for any platform (Windows, Linux, or macOS), but there is an implicit Windows bias as Azure documentation often defaults to Windows-centric tools or workflows. The absence of any mention of cross-platform command-line tools (such as Azure CLI or Azure PowerShell) or Linux-specific guidance means Linux users are not directly supported in this workflow.
Recommendations:
  • Add step-by-step instructions for associating an ASN using the Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Include example commands for both Azure CLI and Azure PowerShell (if relevant), and present Azure CLI examples first or alongside PowerShell to ensure Linux parity.
  • Explicitly mention that the Azure portal is web-based and platform-agnostic, but also provide links or references to command-line alternatives for users who prefer or require automation or non-GUI workflows.
  • Where screenshots are used, clarify that the portal experience is the same across operating systems, and consider including terminal screenshots for CLI workflows.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation page exhibits a Windows bias by exclusively mentioning Azure PowerShell and the Azure portal as the means to set up peering, without referencing equivalent Linux-native tools or CLI options. There are no examples or instructions for Linux users, such as using Azure CLI (az), and the only automation example is PowerShell, which is primarily associated with Windows environments.
Recommendations:
  • Include instructions and examples for setting up peering using Azure CLI (az), which is cross-platform and widely used on Linux.
  • Mention both Azure PowerShell and Azure CLI as supported automation tools, listing them together or in a neutral order.
  • Provide explicit guidance or links for Linux and macOS users, ensuring parity in setup steps and tooling.
  • Avoid implying that PowerShell is the only or primary automation method, and clarify that all major platforms are supported.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/prerequisites.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools
Summary:
The documentation refers to associating Peer ASN using a guide specifically named 'howto-subscription-association-powershell.md', indicating reliance on PowerShell (a Windows-centric tool) for this operation. There are no equivalent instructions or references for Linux or cross-platform tools (such as Azure CLI or REST API), nor are Linux-specific examples provided.
Recommendations:
  • Provide equivalent instructions for associating Peer ASN using Azure CLI, which is cross-platform and widely used on Linux.
  • Include references or links to documentation for performing the same tasks via REST API or Azure Portal, both of which are platform-agnostic.
  • Ensure that all step-by-step guides and code examples are available for both Windows (PowerShell) and Linux (Azure CLI, Bash) users.
  • Explicitly mention the availability of cross-platform tools and recommend them where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/walkthrough-communications-services-partner.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation is heavily focused on the Azure portal GUI and does not provide any command-line examples or automation options for either Windows (PowerShell) or Linux (CLI, Bash). However, it does not show explicit Windows bias such as PowerShell commands or Windows-only tools. The main bias is the lack of parity for users who prefer or require command-line or automated setup, which is common in Linux environments.
Recommendations:
  • Provide equivalent Azure CLI (cross-platform) commands for all portal-based steps, enabling Linux and automation-friendly workflows.
  • If PowerShell examples are ever added, ensure Azure CLI and/or REST API examples are included alongside them.
  • Document any prerequisites or differences for Linux-based network appliances or tools, if relevant.
  • Mention and link to API or CLI documentation for users who want to script or automate the process, and update the FAQ if/when API support becomes available.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/walkthrough-direct-all.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates Windows bias by directing users to a PowerShell-based guide for creating or modifying a direct peering, without mentioning or linking to equivalent Linux/CLI instructions. The only explicit tooling reference is to PowerShell cmdlets, and there are no Bash, Azure CLI, or Linux-native examples provided.
Recommendations:
  • Add parallel instructions or links for performing direct peering setup and management using Azure CLI (az) or REST API, which are cross-platform and commonly used on Linux.
  • Explicitly mention that PowerShell cmdlets can be run on Linux (if applicable), or clarify platform requirements.
  • Provide example commands for both Windows (PowerShell) and Linux (Bash/Azure CLI) users in all procedural sections.
  • Ensure that references to tooling and scripts are balanced and not Windows-centric, to improve accessibility for Linux administrators.