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

50 issues found
Showing 26-50 of 50 flagged pages
Internet Peering Set up peering with Microsoft ...e-docs/blob/main/articles/internet-peering/overview.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 references Azure PowerShell and the Azure portal as the primary methods for setting up peering, without mentioning CLI or Linux-native tools. There are no examples or guidance for Linux/macOS users, and the only automation tool named is PowerShell, which is Windows-centric.
Recommendations
  • Explicitly mention Azure CLI as an alternative to PowerShell for cross-platform support.
  • Provide examples and instructions for setting up peering using Azure CLI, which works on Linux/macOS.
  • Clarify that the Azure portal is web-based and accessible from any OS.
  • Avoid language that implies PowerShell is the only automation option.
GitHub Create Pull Request
Internet Peering Set up peering with Microsoft ...e-docs/blob/main/articles/internet-peering/overview.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 page references Azure PowerShell and the Azure portal as the only methods for setting up peering with Microsoft, without mentioning cross-platform tools (such as Azure CLI) or providing Linux/macOS-specific guidance. This creates a bias toward Windows users and may cause friction for those on Linux or macOS.
Recommendations
  • Explicitly mention Azure CLI as a supported, cross-platform tool for setting up peering, alongside Azure PowerShell and the portal.
  • Provide example commands for Azure CLI in addition to (or instead of) PowerShell.
  • Clarify that both Azure PowerShell and Azure CLI are available on Windows, Linux, and macOS, and link to installation guides for each platform.
  • Ensure walkthroughs linked in 'Related content' also include Linux/macOS-friendly instructions and examples.
GitHub Create Pull Request
Internet Peering Prerequisites to set up peering with Microsoft ...s/blob/main/articles/internet-peering/prerequisites.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 references associating Peer ASN to an Azure subscription and links to a PowerShell-specific guide ('howto-subscription-association-powershell.md'), with no mention of Linux/macOS CLI alternatives or cross-platform instructions. There are no Linux or Azure CLI examples, and the only workflow referenced is PowerShell-based, which is primarily a Windows tool. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native CLI tools.
Recommendations
  • Add instructions and examples for associating Peer ASN using Azure CLI, which is cross-platform.
  • Explicitly mention platform support for each method (e.g., PowerShell for Windows, Azure CLI for Linux/macOS/Windows).
  • Provide links to both PowerShell and Azure CLI documentation for all tasks.
  • Consider including screenshots or step-by-step guides for the Azure portal, which is platform-agnostic.
GitHub Create Pull Request
Internet Peering Set up and manage an exchange peering .../articles/internet-peering/walkthrough-exchange-all.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 references PowerShell cmdlets for deleting exchange peerings, but does not mention equivalent Linux/macOS tools or Azure CLI commands. No Linux/macOS-specific instructions or examples are provided, and the only tooling referenced is Windows-centric.
Recommendations
  • Include Azure CLI examples for managing exchange peerings, especially for deletion and other key operations.
  • Explicitly mention cross-platform alternatives to PowerShell, such as Bash scripts or REST API usage.
  • Add notes or sections clarifying how Linux/macOS users can perform the same tasks, with step-by-step instructions.
GitHub Create Pull Request
Internet Peering Set up and monitor a direct peering ...in/articles/internet-peering/walkthrough-direct-all.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 demonstrates a Windows bias by referencing PowerShell cmdlets for key operations, such as creating or deleting a direct peering, without mentioning equivalent Linux/macOS tools or Azure CLI commands. There are no examples or guidance for users on non-Windows platforms, and the workflow assumes familiarity with Windows-centric tooling.
Recommendations
  • Add Azure CLI examples for all major operations (create, delete, convert peering) alongside PowerShell instructions.
  • Explicitly mention cross-platform options and provide links to Linux/macOS setup guides.
  • Clarify whether all steps can be completed using the Azure Portal, and provide portal-based instructions where possible.
  • Include troubleshooting notes for non-Windows environments, especially for BGP configuration and link testing.
GitHub Create Pull Request
Internet Peering Associate your ASN to Azure subscription - Azure portal ...ernet-peering/howto-subscription-association-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 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 associate an ASN to an Azure subscription using the Azure portal, a web-based GUI. There are no examples or references to command-line tools, scripts, or automation methods such as Azure CLI, PowerShell, or REST API. While the portal is cross-platform, the lack of Linux-specific or CLI-based instructions may disadvantage Linux users and those seeking automation or non-GUI workflows. The documentation implicitly favors Windows-centric patterns by focusing solely on the Azure portal, which is more commonly associated with Windows environments.
Recommendations
  • Add instructions for associating ASN using Azure CLI, which is cross-platform and widely used on Linux.
  • Include PowerShell examples for Windows users, but ensure Azure CLI or REST API methods are presented first or alongside.
  • Provide automation-friendly examples (e.g., bash scripts, REST API calls) to support Linux and DevOps workflows.
  • Explicitly mention that the Azure portal is accessible from any OS, but highlight alternative methods for users who prefer command-line or automated approaches.
GitHub Create Pull Request
Internet Peering Associate your ASN to Azure subscription - Azure portal ...ernet-peering/howto-subscription-association-portal.md
Medium Priority View Details →
Scanned: 2026-01-10 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 associate an ASN to an Azure subscription using the Azure portal, a web-based GUI. There are no command-line examples, nor any mention of cross-platform tools such as Azure CLI, PowerShell, or REST API. While the portal is accessible from any OS, the lack of CLI/API instructions means users on Linux (who often prefer or require automation and command-line workflows) are underserved. The documentation implicitly favors GUI workflows, which are more commonly associated with Windows environments.
Recommendations
  • Add equivalent instructions for associating ASN using Azure CLI, which is cross-platform and widely used on Linux.
  • Include PowerShell examples for Windows users, but ensure CLI examples are listed first or alongside for parity.
  • Provide REST API sample requests for advanced/automated scenarios, useful for both Linux and Windows users.
  • Explicitly state that the Azure portal is accessible from any OS, but highlight automation options for Linux users.
GitHub Create Pull Request
Internet Peering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/howto-subscription-association-portal.md ...ernet-peering/howto-subscription-association-portal.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes how to associate an ASN to an Azure subscription using the Azure portal, a web-based GUI. There are no examples or references to command-line tools, scripts, or automation methods such as Azure CLI, PowerShell, or REST API. While no explicit Windows tools are mentioned, the focus on the Azure portal inherently favors users on Windows, as it is often the default platform for Azure documentation and administration. There is no mention of Linux-specific workflows or parity for users who prefer command-line or automated approaches, which are common in Linux environments.
Recommendations
  • Add equivalent instructions for performing ASN association using Azure CLI, which is cross-platform and widely used on Linux.
  • Provide PowerShell examples if relevant, but ensure Azure CLI or REST API methods are presented first or alongside them to avoid Windows-first bias.
  • Include notes or links to automation options (e.g., ARM templates, Terraform) that can be used from Linux systems.
  • Explicitly state that all steps can be performed from any OS with a supported browser, but highlight CLI and API alternatives for Linux users.
  • Ensure screenshots and examples do not assume a Windows environment (e.g., avoid showing Windows-specific UI elements unless necessary).
GitHub Create Pull Request
Internet Peering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/howto-subscription-association-portal.md ...ernet-peering/howto-subscription-association-portal.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes how to associate an ASN to an Azure subscription using the Azure portal, which is a graphical interface primarily accessed via web browsers on Windows. There are no examples or instructions for performing these tasks using command-line tools such as Azure CLI, PowerShell, or REST API, nor are there any Linux-specific guidance or parity. This implicitly favors Windows users and those comfortable with GUI workflows, while omitting guidance for Linux users who may prefer CLI or automation.
Recommendations
  • Add instructions for associating ASN using Azure CLI, which is cross-platform and widely used on Linux.
  • Include examples for using Azure PowerShell and REST API, with explicit notes on platform compatibility.
  • Provide links to CLI and API documentation for users who prefer automation or non-GUI workflows.
  • Ensure screenshots and step-by-step guides are supplemented with equivalent command-line instructions.
  • Explicitly mention that the Azure portal is accessible from any OS, but offer alternatives for Linux users.
GitHub Create Pull Request
Internet Peering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/prerequisites.md ...s/blob/main/articles/internet-peering/prerequisites.md
Medium Priority View Details →
Scanned: 2025-08-17 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation references associating Peer ASN using a guide that is specifically for PowerShell (howto-subscription-association-powershell.md), which is a Windows-centric tool. There are no examples or instructions for Linux users or for using cross-platform tools like Azure CLI. The absence of Linux or cross-platform examples and the exclusive mention of PowerShell indicate a bias toward Windows environments.
Recommendations
  • Provide equivalent instructions for associating Peer ASN using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Include explicit Linux/macOS command-line examples where relevant.
  • Reference both PowerShell and Azure CLI documentation links, and clarify which tools are supported on which platforms.
  • Consider including a table or section summarizing available tools (PowerShell, Azure CLI, Portal) and their platform compatibility.
GitHub Create Pull Request
Internet Peering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/walkthrough-peering-service-all.md ...es/internet-peering/walkthrough-peering-service-all.md
Medium Priority View Details →
Scanned: 2025-08-17 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively describes configuration and management using the Azure portal UI, with no mention of command-line tools, scripts, or automation options for either Windows (e.g., PowerShell) or Linux (e.g., Azure CLI, Bash). However, the only tool mentioned is the Azure portal, which is a web-based interface and not OS-specific, but the absence of any Linux-friendly automation or CLI examples (such as Azure CLI commands) indicates a bias towards GUI-based workflows, which are more commonly associated with Windows environments. There is also an explicit statement that APIs are not supported and configuration can only be done via the Azure portal, further limiting Linux parity and automation options.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all portal-based steps, enabling Linux and cross-platform users to automate or script the process.
  • Document any REST API endpoints or planned API support, even if currently unavailable, to inform users about future automation possibilities.
  • If PowerShell or Windows-specific tools are not required, explicitly state that the process is OS-agnostic, but still provide CLI examples for parity.
  • Include troubleshooting and validation steps that can be performed from Linux environments (e.g., using curl, dig, or traceroute) where relevant.
  • Solicit feedback from Linux users to identify additional parity gaps in the onboarding and management process.
GitHub Create Pull Request
Internet Peering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/howto-subscription-association-portal.md ...ernet-peering/howto-subscription-association-portal.md
Medium Priority View Details →
Scanned: 2025-08-17 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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 provided for any platform (Windows, Linux, or macOS), but the reliance on the Azure portal and absence of CLI/automation options can be considered a form of Windows-first bias, as enterprise Windows users are more likely to use GUI workflows. There is no mention of Linux tools, shell commands, or cross-platform automation methods (such as Azure CLI or PowerShell Core), and no guidance for users who may prefer or require non-GUI, scriptable approaches.
Recommendations
  • Add step-by-step instructions for associating an ASN using the Azure CLI (az peering commands), which is cross-platform and works on Linux, macOS, and Windows.
  • Provide PowerShell Core examples for users who prefer scripting, making sure to specify that these work on all major platforms.
  • Include a section comparing portal, CLI, and PowerShell approaches, highlighting their cross-platform compatibility.
  • Explicitly mention that the Azure portal is web-based and accessible from any OS, but also provide automation-friendly alternatives for Linux and macOS users.
  • Ensure screenshots and terminology are not Windows-specific (e.g., avoid referencing Windows-only tools or UI conventions).
GitHub Create Pull Request
Internet Peering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/prerequisites.md ...s/blob/main/articles/internet-peering/prerequisites.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Internet Peering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/walkthrough-exchange-all.md .../articles/internet-peering/walkthrough-exchange-all.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Internet Peering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/prerequisites.md ...s/blob/main/articles/internet-peering/prerequisites.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Internet Peering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/howto-subscription-association-portal.md ...ernet-peering/howto-subscription-association-portal.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Internet Peering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/walkthrough-exchange-all.md .../articles/internet-peering/walkthrough-exchange-all.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Internet Peering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/walkthrough-exchange-route-server-partner.md ...t-peering/walkthrough-exchange-route-server-partner.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Internet Peering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/walkthrough-peering-service-all.md ...es/internet-peering/walkthrough-peering-service-all.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Internet Peering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/howto-subscription-association-portal.md ...ernet-peering/howto-subscription-association-portal.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Internet Peering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/prerequisites.md ...s/blob/main/articles/internet-peering/prerequisites.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Internet Peering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/walkthrough-exchange-route-server-partner.md ...t-peering/walkthrough-exchange-route-server-partner.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Internet Peering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/walkthrough-peering-service-all.md ...es/internet-peering/walkthrough-peering-service-all.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Internet Peering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/walkthrough-communications-services-partner.md ...peering/walkthrough-communications-services-partner.md
Low Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
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.
GitHub Create Pull Request
Internet Peering https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/internet-peering/walkthrough-communications-services-partner.md ...peering/walkthrough-communications-services-partner.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
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.
GitHub Create Pull Request
← Previous Page 2 of 2 Next →