API Management
284
Total Pages
229
Linux-Friendly Pages
55
Pages with Bias
19.4%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
594 issues found
Showing 501-525 of 594 flagged pages
API Management
Deploy a Self-Hosted Gateway to Azure Kubernetes Service
...to-deploy-self-hosted-gateway-azure-kubernetes-service.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows tools (Azure PowerShell) alongside Azure CLI and Azure Portal for creating an AKS cluster, but does not provide any PowerShell-specific examples or commands. All deployment and verification steps use kubectl, which is cross-platform. The only minor bias is listing Azure PowerShell before Azure Portal, but Linux parity is otherwise maintained.
Recommendations
- Consider listing Azure CLI before Azure PowerShell in the prerequisites, as CLI is more commonly used across platforms.
- Explicitly mention that kubectl commands work on Windows, Linux, and macOS terminals.
- If possible, clarify that Azure PowerShell is optional and provide links to Linux/macOS installation instructions for Azure CLI and kubectl.
Create Pull Request
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is most commonly used on Windows) and its example may create a mild Windows bias. Additionally, PowerShell is listed alongside CLI in the prerequisites and workflow, and its example is presented immediately after the CLI example, rather than being clearly separated or marked as Windows-specific. No Linux/macOS-specific tools or workflows are mentioned, and there is no explicit guidance for Linux users regarding PowerShell usage.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, but is most commonly used on Windows.
- Add a note for Linux/macOS users about installing and using Azure PowerShell, or recommend using Azure CLI as the preferred cross-platform tool.
- Consider presenting Azure CLI examples first, as it is the most universally accessible for all platforms.
- Explicitly state that all CLI commands work on Linux/macOS, and provide troubleshooting tips for non-Windows environments if needed.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but PowerShell is presented as a first-class option alongside CLI. The prerequisites list Azure CLI and Azure PowerShell equally, and the PowerShell example is given its own section. There are no Linux-specific examples or explicit mention of Linux/macOS compatibility for PowerShell, which may cause confusion for non-Windows users. However, the Azure CLI example is present and fully functional for Linux/macOS users.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows, and recommend Azure CLI for Linux/macOS users.
- Add a note in the prerequisites section indicating that Azure PowerShell is best supported on Windows, while Azure CLI is cross-platform.
- Consider providing Bash shell examples or highlighting CLI usage for Linux/macOS users.
- Explicitly state that all Azure CLI commands are supported on Linux/macOS.
API Management
Azure API Management virtual network injection - network resources
.../api-management/virtual-network-injection-resources.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is largely platform-neutral, focusing on Azure networking concepts and requirements for API Management virtual network injection. However, there is a minor instance of Windows bias in the 'Related content' section, where a PowerShell-based guide is referenced for connecting virtual networks, without mention of Linux/macOS CLI alternatives. No PowerShell commands or Windows-specific tools are used in the main content, and all guidance is applicable to any OS.
Recommendations
- In the 'Related content' section, add links to equivalent Azure CLI or Bash-based guides for connecting virtual networks, ensuring Linux/macOS users are equally supported.
- Where PowerShell is referenced, clarify that Azure CLI or portal-based approaches are also available and provide links.
- Review cross-referenced articles to ensure parity in example scripts and tooling for Linux/macOS users.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page primarily uses Azure Portal and Azure CLI examples, but when mentioning scripting or automation, it references Azure PowerShell cmdlets before or alongside Azure CLI, and does not provide Linux/macOS-specific guidance or examples. The PowerShell cmdlet is mentioned as an option for disabling a regional gateway, but no Bash or Linux shell equivalent is given. The ordering of tools (PowerShell before CLI) and lack of explicit Linux/macOS parity is a minor Windows bias.
Recommendations
- When referencing scripting tools, mention Azure CLI first, as it is cross-platform, and PowerShell second.
- Provide explicit Bash or shell script examples for Linux/macOS users where automation is discussed.
- Clarify that Azure CLI commands work on Windows, Linux, and macOS.
- Where PowerShell is referenced, add a note that Azure CLI is recommended for cross-platform use.
- Add links to Azure CLI installation and usage guides for Linux/macOS.
API Management
Backup and restore your Azure API Management instance for disaster recovery
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides detailed PowerShell examples for backup and restore operations, with PowerShell presented before Azure CLI and REST API options. While Azure CLI and REST API examples are included, the PowerShell section is more extensive and appears first, which may create friction for Linux/macOS users who prefer Bash or CLI workflows. No Windows-specific tools or patterns are mentioned beyond PowerShell, and Linux parity is generally maintained via CLI and REST examples.
Recommendations
- Present Azure CLI examples before PowerShell, or at least in parallel, to avoid implying PowerShell is the preferred or default method.
- Expand Azure CLI examples to cover managed identity scenarios, matching the detail provided in PowerShell sections.
- Explicitly note that PowerShell can be run cross-platform, but highlight CLI as the native option for Linux/macOS users.
- Add a short section clarifying that all operations can be performed on Linux/macOS using Azure CLI and REST API, and link to relevant CLI installation guides.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but PowerShell is presented as a first-class option alongside CLI, and the PowerShell example is given equal prominence. There is minor Windows bias in that PowerShell is a Windows-centric tool (though now cross-platform), and the documentation does not mention Linux-specific shell options or tools. However, the Azure CLI example is fully functional and shown before PowerShell, and all steps can be completed on Linux/macOS using the CLI or portal.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, but is most commonly used on Windows.
- Explicitly note that Azure CLI is fully supported on Linux/macOS and is the recommended tool for non-Windows environments.
- Consider adding a brief note for Linux/macOS users about installing and using Azure CLI, or linking to relevant installation guides.
- If possible, provide bash/zsh shell script examples for Azure CLI usage to reinforce Linux parity.
API Management
Azure API Management virtual network injection - network resources
.../api-management/virtual-network-injection-resources.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is generally platform-neutral, focusing on Azure concepts and resources. However, in the 'Related content' section, a link is provided to 'Connect virtual networks from different deployment models using PowerShell', which highlights a Windows-centric tool without mentioning cross-platform alternatives (such as Azure CLI or ARM templates). Additionally, PowerShell is referenced before any Linux-friendly options, which may subtly reinforce Windows-first patterns.
Recommendations
- Add links or examples for connecting virtual networks using Azure CLI, which is cross-platform, alongside the PowerShell example.
- Mention ARM template or Bicep-based approaches for resource deployment and configuration, which are platform-agnostic.
- Ensure that any scripting or tooling references include both Windows and Linux/macOS-friendly options, or clarify when a tool is Windows-only.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but PowerShell is featured equally alongside CLI, and is presented after CLI. PowerShell is a Windows-centric tool, but Azure CLI is cross-platform. There are no Linux-specific examples or notes, but the CLI example is sufficient for Linux/macOS users. The prerequisites list both Azure CLI and PowerShell, but do not clarify platform differences or recommend CLI for Linux/macOS users.
Recommendations
- Add a note in the prerequisites section clarifying that Azure CLI is cross-platform and recommended for Linux/macOS users, while PowerShell is primarily for Windows.
- Consider providing a Bash shell example (even if identical to CLI) to reinforce Linux parity.
- Explicitly state that all CLI commands work on Linux/macOS, and PowerShell is optional for those platforms.
- If possible, link to guidance for installing Azure CLI on Linux/macOS.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides instructions and examples primarily using the Azure portal and Azure CLI, with a brief mention of Azure PowerShell. The PowerShell cmdlet is referenced after the CLI example, and no Windows-specific tools or patterns are prioritized. All provided command-line examples use Azure CLI, which is cross-platform. There are no PowerShell-heavy sections, nor are Windows tools or patterns mentioned exclusively or before their Linux equivalents. The documentation is largely neutral, but the PowerShell reference could be seen as a minor 'windows_first' bias.
Recommendations
- Ensure that Azure CLI examples are presented before or alongside PowerShell examples.
- Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
- If referencing PowerShell, consider also referencing Bash or other Linux-native shells where appropriate.
- Add explicit notes or links for Linux/macOS users if there are platform-specific considerations.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows, and its inclusion as a main example may indicate a mild Windows bias. Additionally, PowerShell examples are given equal prominence to CLI, which may not be necessary for Linux/macOS users. However, the CLI example is present and shown before PowerShell, mitigating the bias.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider adding a note that Azure PowerShell is available on Linux/macOS, but CLI is generally recommended for non-Windows environments.
- If possible, provide bash shell scripting examples alongside PowerShell for parity.
- Explicitly mention that all CLI commands work on Linux/macOS, and link to relevant platform-specific installation guides.
API Management
Azure API Management virtual network injection - network resources
.../api-management/virtual-network-injection-resources.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is largely platform-neutral, focusing on Azure networking concepts and requirements for API Management virtual network injection. However, in the 'Related content' section, a PowerShell-based guide is referenced before any mention of Linux/CLI alternatives, which may subtly prioritize Windows users. No explicit Windows-only tools, commands, or examples are present in the main content.
Recommendations
- In the 'Related content' section, add links to equivalent Azure CLI or Bash guides for connecting virtual networks, ensuring Linux/macOS users see parity.
- Where PowerShell is referenced, clarify that Azure CLI and portal options are available and provide links to those alternatives.
- Review other cross-referenced documentation to ensure Linux/macOS examples are given equal prominence.
API Management
Azure API Management virtual network injection - network resources
.../api-management/virtual-network-injection-resources.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is generally platform-neutral, focusing on Azure networking concepts. However, there is a minor bias in the 'Related content' section, where a PowerShell-based guide is referenced for connecting virtual networks, and no equivalent Linux/CLI example is provided or mentioned. Additionally, PowerShell is mentioned before any Linux alternatives, which may create friction for Linux/macOS users.
Recommendations
- Add links or references to Azure CLI or Bash-based guides for connecting virtual networks, alongside the PowerShell example.
- Ensure that Linux/macOS-friendly tools and examples are mentioned wherever PowerShell is referenced.
- Consider listing cross-platform solutions (Azure CLI, REST API, Portal) before or alongside Windows-specific tools in related content sections.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation primarily uses Azure Portal and Azure CLI examples, which are cross-platform. However, in the section about disabling routing to a regional gateway, Azure PowerShell is mentioned alongside Azure CLI and REST API, but no Linux-specific tools or shell scripts are referenced. Azure PowerShell is a Windows-centric tool, and its mention before Linux-native alternatives (like Bash scripts or REST API via curl) may create minor friction for Linux/macOS users. The overall guidance and examples are not Windows-exclusive, but there is a slight tendency to mention Windows tools (PowerShell) without Linux equivalents.
Recommendations
- When referencing Azure PowerShell, also mention Bash or shell scripting alternatives for Linux/macOS users, such as using curl with the REST API.
- Provide explicit examples using Azure CLI (already present) and REST API via curl for disabling gateways, to ensure parity.
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Avoid listing PowerShell before CLI or REST API unless the feature is truly Windows-only.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation primarily uses Azure portal and Azure CLI examples for deployment and configuration tasks, but when mentioning programmatic options for disabling regional gateways, it lists Azure PowerShell before Azure CLI and REST API. The PowerShell cmdlet is referenced by name, but no Linux-specific shell or tool is highlighted. However, the Azure CLI is used for all command-line examples, which is cross-platform. There are no Windows-only tools or patterns, and no missing Linux examples for critical tasks.
Recommendations
- When listing programmatic options, mention Azure CLI before PowerShell, as CLI is cross-platform and preferred for Linux/macOS users.
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS.
- If referencing PowerShell, clarify that Azure PowerShell is available on Linux/macOS, or provide Bash equivalents where relevant.
- Avoid listing PowerShell as the first option unless the task is Windows-specific.
API Management
Azure API Management virtual network injection - network resources
.../api-management/virtual-network-injection-resources.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation includes a related link to connecting virtual networks using PowerShell, which is a Windows-centric tool, and lists this before mentioning Linux-equivalent approaches. However, the main content is otherwise platform-neutral, focusing on Azure resource configuration rather than OS-specific commands or tools.
Recommendations
- Add equivalent Azure CLI or Azure Cloud Shell examples or links for connecting virtual networks, as these are cross-platform and widely used by Linux/macOS users.
- When referencing PowerShell-based guides, also reference or link to documentation for performing the same tasks with Azure CLI or ARM templates.
- Consider reordering related content so that cross-platform tools (Azure CLI, ARM templates) are mentioned before or alongside PowerShell.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the PowerShell section is Windows-centric and is given equal prominence to CLI. There is no explicit Linux/macOS bias, but PowerShell is primarily used on Windows, and its inclusion may suggest a Windows preference. Additionally, PowerShell is mentioned before Linux-native shell examples (e.g., Bash), and there are no Bash or Linux-specific examples provided.
Recommendations
- Add explicit Bash shell examples for Azure CLI usage, demonstrating cross-platform compatibility.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and highlight this in the CLI section.
- Consider mentioning PowerShell Core (pwsh) for Linux/macOS users if PowerShell examples are retained.
- If possible, reorder examples to show Azure CLI (cross-platform) before PowerShell (Windows-centric) or clarify their parity.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation primarily uses Azure Portal and Azure CLI for instructions, which are cross-platform. However, in the section about disabling routing to a regional gateway, Azure PowerShell is mentioned as an option alongside REST API and Azure CLI, but no Linux-specific tools or shell examples (such as Bash scripts) are provided. Azure CLI is shown first and is cross-platform, but PowerShell is referenced without explicit parity for Linux/macOS users. There are no Windows-only tools or patterns, and no evidence of missing Linux examples for critical tasks.
Recommendations
- Clarify that Azure PowerShell can be used on Linux/macOS, or provide Bash shell script examples where appropriate.
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS.
- If referencing PowerShell, consider linking to documentation about using PowerShell Core on Linux/macOS.
- Ensure that any command-line instructions are clearly marked as cross-platform, and avoid implying PowerShell is Windows-only.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows, and its inclusion as a main example may create friction for Linux/macOS users. Additionally, PowerShell examples are given equal prominence to CLI, which can be seen as a mild Windows bias. However, there are no Windows-only tools or patterns, and the CLI example is present and functional for Linux/macOS users.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider mentioning that Azure PowerShell can be installed on Linux/macOS, but CLI is generally more common for non-Windows environments.
- If possible, provide Bash shell scripting examples alongside PowerShell, or highlight CLI usage for Linux/macOS users.
- Ensure that any references to PowerShell do not imply it is required for Linux/macOS users.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation primarily uses Azure Portal and Azure CLI examples, but when mentioning programmatic options for disabling routing to a regional gateway, it lists Azure PowerShell cmdlets alongside REST API and Azure CLI, with PowerShell mentioned before Linux-native tools. There are no explicit Linux/macOS examples or references to Bash scripting, and PowerShell is referenced without Linux parity guidance. However, the main workflow is portal- and CLI-based, which are cross-platform.
Recommendations
- When listing programmatic options, mention Azure CLI first, as it is cross-platform, and clarify that PowerShell is available on Linux/macOS as well.
- Add explicit Bash or shell scripting examples where relevant, or clarify that Azure CLI commands work equally on Linux/macOS.
- Avoid listing PowerShell before CLI unless the task is Windows-specific.
- Add a note that Azure PowerShell is available cross-platform, or link to Linux/macOS installation guides.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but PowerShell is featured equally alongside CLI and is presented as a primary workflow. PowerShell is a Windows-centric tool, and its inclusion as a main example may create friction for Linux/macOS users. However, Azure CLI examples are present and fully functional for cross-platform users. The order of examples (Portal, CLI, then PowerShell) does not prioritize Windows, but the presence of PowerShell as a main tab could be seen as minor Windows bias.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
- Consider adding Bash or shell script examples for Linux users, or explicitly state that Azure CLI is cross-platform.
- Add a note indicating that PowerShell Core is available on Linux/macOS, if relevant.
- Ensure all CLI instructions are verified to work on Linux/macOS.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but the PowerShell example is given equal prominence to the CLI example. The prerequisites list Azure CLI before Azure PowerShell, but both are included. There are no Linux-specific examples or explicit mention of Linux/macOS compatibility for CLI commands. The PowerShell example is Windows-centric, but Azure CLI is cross-platform. The portal instructions are platform-agnostic. The bias is minor, mainly due to the inclusion of PowerShell as a primary example and lack of explicit Linux guidance.
Recommendations
- Explicitly state that Azure CLI is cross-platform and works on Linux/macOS.
- Add a note clarifying that PowerShell is available on Linux/macOS, or indicate that the PowerShell example is primarily for Windows users.
- Consider including a Bash shell example for Azure CLI usage to reinforce Linux parity.
- Mention any OS-specific considerations for file paths or authentication if relevant.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides step-by-step instructions primarily using the Azure Portal and Azure CLI, with a brief mention of Azure PowerShell as an alternative tool for disabling routing to a regional gateway. The PowerShell cmdlet is referenced after the Azure CLI example, and no Windows-specific tools or patterns are prioritized. All examples and instructions are cross-platform (Azure Portal and Azure CLI), and the PowerShell mention is not exclusive or prioritized. There are no Windows-only examples, tools, or patterns, and Linux parity is maintained throughout.
Recommendations
- Ensure that all CLI examples are explicitly noted as cross-platform.
- If referencing PowerShell, clarify its platform compatibility (PowerShell Core runs on Linux/macOS).
- Consider adding a note that Azure CLI is available on Windows, Linux, and macOS for clarity.
- If possible, provide Bash shell script examples for Linux users in addition to Azure CLI commands.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows and its example is given equal prominence. There is no explicit mention of Linux/macOS-specific tools or workflows, and PowerShell is presented as a standard option, which may create friction for Linux users who typically use Bash or other shells.
Recommendations
- Clarify that Azure CLI is fully supported on Linux/macOS and provide explicit instructions for installing and using it on those platforms.
- Mention that Azure PowerShell can be installed and used on Linux/macOS, or note its Windows-centric nature.
- Consider providing Bash shell examples alongside PowerShell where scripting is involved.
- Add a brief note about cross-platform compatibility for each tool, especially for CLI and PowerShell sections.
- If possible, include troubleshooting tips for Linux/macOS users (e.g., file path differences, authentication nuances).
API Management
Azure API Management virtual network injection - network resources
.../api-management/virtual-network-injection-resources.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform and does not focus on Windows-specific tools, commands, or patterns. However, in the 'Related content' section, the example for connecting virtual networks refers specifically to a PowerShell-based guide before any CLI or Linux-native alternatives, which is a minor instance of Windows-first ordering.
Recommendations
- In the 'Related content' section, add or reference equivalent guides for connecting virtual networks using Azure CLI or ARM templates, and consider listing these before or alongside the PowerShell example.
- Wherever PowerShell is referenced, ensure that Azure CLI or cross-platform alternatives are also mentioned, especially in introductory or example lists.