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 451-475 of 594 flagged pages
API Management
Quickstart: Create Azure API Management instance by using Bicep
.../blob/main/articles/api-management/quickstart-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all key steps, but PowerShell is featured equally alongside CLI, and PowerShell is a Windows-centric tool. There is no explicit mention of Linux/macOS-specific instructions or considerations, and PowerShell examples are given in every section, which may create friction for Linux/macOS users who typically use Azure CLI. However, Azure CLI examples are present and shown first in each case.
Recommendations
- Add a brief note clarifying that Azure CLI is cross-platform and recommended for Linux/macOS users, while PowerShell is primarily for Windows.
- Consider including a section or callout for Linux/macOS users, highlighting that all CLI commands work natively on those platforms.
- If possible, add links or references to installing Azure CLI on Linux/macOS.
- Mention that PowerShell Core is available cross-platform, but Azure PowerShell is most commonly used on Windows.
Create Pull Request
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 and does not provide command-line examples or tooling instructions specific to any OS. However, in the 'Related content' section, a link to 'Connect virtual networks from different deployment models using PowerShell' is given, and no equivalent Linux/CLI/Bash example is referenced or prioritized. This subtly prioritizes Windows/PowerShell as the default automation approach.
Recommendations
- In the 'Related content' section, add or prioritize links to equivalent Azure CLI or Bash-based guidance for connecting virtual networks, ensuring Linux/macOS users see their options equally.
- Where PowerShell is referenced, clarify that equivalent steps can be performed using Azure CLI, and provide links or notes to such documentation.
- Review related guidance to ensure Linux/macOS users are not implicitly directed to use Windows/PowerShell tooling for common network tasks.
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 platform-neutral, focusing on Azure networking concepts. However, in the 'Related content' section, a link to a PowerShell-based guide for connecting virtual networks is provided without mention of CLI or Linux-native alternatives. This subtly prioritizes Windows/PowerShell as the default automation tool, which may create friction for Linux/macOS users.
Recommendations
- In the 'Related content' section, add links to equivalent Azure CLI or ARM template guides for connecting virtual networks, ensuring Linux/macOS users have clear, first-class options.
- Where PowerShell is referenced, clarify that equivalent steps can be performed using Azure CLI or provide links to those instructions.
- Review other cross-references to ensure that automation and scripting examples are not Windows/PowerShell-centric unless the feature is Windows-only.
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 comprehensive coverage for PowerShell (Windows-centric) usage, with detailed variable setup and command examples. While Azure CLI (cross-platform) and REST API examples are also included, PowerShell is consistently presented first and in greater detail, which may subtly prioritize Windows users. There are no Linux/macOS-specific issues, but the ordering and depth of PowerShell content reflect a mild Windows bias.
Recommendations
- Present Azure CLI (Bash) examples before or alongside PowerShell examples to emphasize cross-platform parity.
- Ensure that CLI examples are as detailed as PowerShell ones, including variable setup and context.
- Explicitly state that Azure CLI and REST API methods are fully supported on Linux/macOS.
- Consider adding a note that PowerShell Core is available cross-platform, if relevant, to clarify for non-Windows users.
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 briefly mentions Azure PowerShell as an option for creating an AKS cluster before mentioning the Azure CLI and portal. However, all deployment and verification steps use kubectl commands, which are cross-platform and standard for Kubernetes. No PowerShell-specific commands or Windows-only tools are used in the main workflow.
Recommendations
- Consider listing Azure CLI before Azure PowerShell in the prerequisites, as CLI is more universally used across platforms.
- Explicitly note that all kubectl commands work equally on Windows, Linux, and macOS.
- If possible, provide links to Linux/macOS-specific installation guides for Azure CLI and kubectl.
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 page provides instructions for deploying Azure API Management to multiple regions, primarily using the Azure portal and Azure CLI. The only explicit mention of a Windows-specific tool is the Azure PowerShell cmdlet (set-azapimanagement), which is listed after the Azure CLI and REST API options. No PowerShell-only examples are given, and the CLI is presented first. There are no Windows-only tools or patterns, and Linux parity is maintained throughout. The only minor bias is listing PowerShell as an option, but this does not impact Linux/macOS users, as CLI and REST API alternatives are provided.
Recommendations
- Ensure that Azure CLI examples are always provided and shown before PowerShell examples.
- Clarify that Azure CLI and REST API are cross-platform and preferred for Linux/macOS users.
- If possible, provide Bash shell scripting examples for automation alongside CLI commands.
- Explicitly state that PowerShell is optional and not required for Linux/macOS users.
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 top-level example may create a Windows bias. The PowerShell example is given equal prominence to the CLI example, and there are no explicit Linux/macOS-specific instructions or troubleshooting tips. The CLI example is cross-platform, but PowerShell is presented as a standard workflow, which may confuse Linux/macOS users who typically use Bash or Zsh.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
- Consider adding Bash or shell script examples for Linux/macOS users, or explicitly state that Azure CLI is the preferred cross-platform tool.
- Add a note indicating that PowerShell can be used on Linux/macOS, but CLI is more common for those platforms.
- Ensure that CLI examples are shown first, or highlight their cross-platform nature.
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 parity between Azure CLI and Azure PowerShell examples for importing a SOAP API, but PowerShell is presented as a primary workflow alongside CLI. The prerequisites list both Azure CLI and Azure PowerShell, but does not mention Bash or shell scripting alternatives. The PowerShell example is given equal prominence to CLI, but PowerShell is a Windows-centric tool, potentially creating friction for Linux/macOS users. However, the Azure CLI example is fully cross-platform and appears before PowerShell, mitigating the bias.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommend it for Linux/macOS users.
- Add a note that Azure PowerShell is available on Linux/macOS, but CLI is generally preferred for non-Windows environments.
- Consider including Bash or shell scripting examples for common operations, or link to CLI scripting guides.
- Explicitly state that all tasks can be completed using Azure CLI on Linux/macOS.
API Management
Quickstart: Create Azure API Management instance by using Bicep
.../blob/main/articles/api-management/quickstart-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all tasks. Azure CLI is cross-platform, while PowerShell is more commonly associated with Windows, though it is available on Linux/macOS. The CLI examples are consistently presented before PowerShell, and no Windows-specific tools or patterns are mentioned. No Linux/macOS-specific examples or shell scripts are provided, but the CLI coverage ensures Linux parity.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS as well as Windows.
- Consider adding brief notes or examples for Bash scripting or integrating Bicep deployments in Linux environments.
- Mention that PowerShell Core is available cross-platform, but CLI is generally preferred for Linux/macOS users.
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 largely platform-neutral, focusing on Azure networking concepts. However, there is a minor bias in the 'Related content' section, which links to a PowerShell-based guide for connecting virtual networks. This may imply Windows-first tooling, as PowerShell is traditionally associated with Windows, even though it is now cross-platform. No Linux-specific CLI examples or references are provided, and the PowerShell guide is mentioned before any Azure CLI or ARM template alternatives.
Recommendations
- Add links to equivalent Azure CLI documentation for connecting virtual networks, ensuring Linux/macOS users have clear guidance.
- Where PowerShell is referenced, clarify that Azure CLI or ARM templates can also be used, and provide links or examples.
- In the 'Related content' section, balance PowerShell links with Azure CLI alternatives, or note that PowerShell is available cross-platform.
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 examples, but briefly mentions Azure PowerShell (set-azapimanagement) as a tool for disabling regional gateways. The PowerShell reference appears alongside CLI and REST API options, but no Linux-specific or macOS-specific guidance or examples are provided. The ordering sometimes places PowerShell before CLI, and there are no explicit Linux/macOS parity notes. However, the CLI examples are platform-agnostic and are shown in full, so Linux/macOS users can complete all tasks.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS as well as Windows.
- When mentioning Azure PowerShell, note its Windows-centric nature and suggest Azure CLI as the preferred cross-platform tool.
- Consider providing example scripts or command-line snippets for Linux/macOS environments where relevant, such as bash or zsh.
- Explicitly state that all portal and CLI steps are platform-independent unless otherwise noted.
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 shown first in each example section. Azure CLI and REST API examples are also included, supporting cross-platform usage. However, the prominence and detail of PowerShell examples, as well as their placement before CLI/Bash examples, indicate a mild Windows bias. All CLI examples use Bash syntax, ensuring Linux/macOS parity, and REST API instructions are platform-neutral.
Recommendations
- Consider presenting Azure CLI (Bash) examples before PowerShell, or side-by-side, to avoid implying Windows as the default platform.
- Expand Azure CLI examples to include managed identity scenarios, matching the detail provided for PowerShell.
- Explicitly note that Azure CLI and REST API methods are fully supported on Linux/macOS, and highlight their parity.
- Where possible, provide links to additional Linux/macOS-specific guidance or troubleshooting.
API Management
Quickstart: Create Azure API Management instance by using Bicep
.../blob/main/articles/api-management/quickstart-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all steps, but PowerShell is featured equally alongside CLI, which is primarily used on Windows. There is no explicit mention of Linux/macOS-specific tools or patterns, and the CLI examples are cross-platform. However, PowerShell is presented as a first-class option, which may create minor friction for Linux/macOS users, as PowerShell is less commonly used on those platforms.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users.
- Add brief notes indicating that PowerShell examples are primarily for Windows users, while CLI is suitable for all platforms.
- Consider including Bash shell examples or highlighting CLI usage in Bash for Linux/macOS users.
- If possible, reorder examples to show Azure CLI first, or explicitly state platform applicability for each tool.
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 provides links for creating an AKS cluster using Azure CLI, Azure PowerShell, and Azure Portal, with PowerShell (a Windows-centric tool) listed before the Azure Portal. However, all deployment and operational examples use cross-platform tools (kubectl, YAML), and no Windows-specific commands or tools are prioritized or exclusively used. There are no missing Linux/macOS examples, and no Windows-only tools are referenced in the main deployment flow.
Recommendations
- List Azure CLI (cross-platform) before Azure PowerShell in the prerequisites to emphasize Linux/macOS parity.
- Explicitly mention that all kubectl commands and YAML deployments are cross-platform and can be run from Linux, macOS, or Windows terminals.
- Consider adding a note clarifying that Azure PowerShell is primarily for Windows users, while Azure CLI is recommended for 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. However, in the 'Related content' section, the link 'Connect virtual networks from different deployment models using PowerShell' references PowerShell specifically, which is a Windows-centric tool. No Linux/bash equivalents are mentioned alongside this link, and PowerShell is listed before other general resources.
Recommendations
- Add links or references to equivalent Linux/bash CLI documentation for connecting virtual networks (e.g., Azure CLI examples).
- When mentioning PowerShell-specific guidance, also mention or link to Linux/macOS-compatible tools and instructions (such as Azure CLI or ARM templates).
- Ensure parity in example scripts and tooling references throughout the documentation, especially 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 is generally cross-platform, focusing on Azure portal and Azure CLI, which are available on Windows, Linux, and macOS. However, there is mild Windows bias in the 'Disable routing to a regional gateway' section, where the Azure PowerShell cmdlet (set-azapimanagement) is mentioned alongside Azure CLI and REST API, but no equivalent Linux/macOS-specific tooling is highlighted. Additionally, PowerShell is mentioned before REST API and Azure CLI in the tools list, which may subtly prioritize Windows patterns.
Recommendations
- Explicitly state that Azure CLI and REST API are fully supported on Linux/macOS.
- When listing tools, mention cross-platform options (Azure CLI, REST API) before Windows-specific ones (PowerShell).
- If PowerShell is referenced, clarify its cross-platform availability or provide Bash/shell script equivalents where relevant.
- Add a note that all Azure CLI examples work on Linux/macOS terminals.
- Consider including sample Bash scripts for common operations, if relevant.
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 provides links for creating an Azure Kubernetes cluster using Azure CLI, Azure PowerShell, and Azure Portal. The PowerShell (Windows-centric) option is mentioned second, after Azure CLI, and before Azure Portal. All command examples use kubectl, which is cross-platform, and no Windows-specific tools or patterns are prioritized or exclusively mentioned. There are no missing Linux/macOS examples, and no Windows-only tools are used.
Recommendations
- Consider listing Azure CLI and Azure Portal options before Azure PowerShell, as CLI is more cross-platform and PowerShell is Windows-centric.
- Explicitly note that all kubectl commands work on Linux, macOS, and Windows.
- If possible, provide brief guidance for Linux/macOS users on installing kubectl and Azure CLI, or link to relevant documentation.
API Management
Quickstart: Create Azure API Management instance by using Bicep
.../blob/main/articles/api-management/quickstart-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all operations, but PowerShell is presented as an equal option throughout, which can create friction for Linux/macOS users since PowerShell is less commonly used outside Windows. In some sections, PowerShell is mentioned alongside CLI, but not after CLI, and the prerequisites list PowerShell requirements separately. However, Azure CLI examples are always present, and there are no Windows-specific tools or patterns.
Recommendations
- Clarify that Azure CLI is cross-platform and generally preferred for Linux/macOS users.
- Consider listing Azure CLI examples before PowerShell in all sections to reinforce CLI as the default for non-Windows users.
- Add a brief note in the prerequisites indicating that PowerShell is optional and primarily for users who prefer it, especially on Windows.
- Ensure that any references to PowerShell do not imply it is required for Linux/macOS users.
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 concepts and requirements. However, in the 'Related content' section, a PowerShell-based example for connecting virtual networks is listed before any Linux or CLI equivalent, which may subtly prioritize Windows tools. No explicit PowerShell commands or Windows-specific tooling are used in the main guidance, and Linux/macOS users can complete all tasks described.
Recommendations
- In the 'Related content' section, add or prioritize links to Azure CLI or ARM template-based guides for connecting virtual networks, ensuring Linux/macOS parity.
- Where PowerShell is referenced, clarify that Azure CLI and portal options are available and provide links to those alternatives.
- Review other cross-links to ensure Linux/macOS users are equally supported in all referenced guides.
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/PowerShell as an option for creating an AKS cluster before Linux alternatives, but all deployment and operational examples use cross-platform tools (kubectl, YAML). No Windows-specific tools or patterns are prioritized in the main workflow, and Linux users can follow all steps without friction.
Recommendations
- List Linux (Azure CLI) and Windows (PowerShell) options together or with Azure CLI first, as it is cross-platform.
- Clarify that all kubectl commands and YAML files are platform-agnostic and can be run from any OS.
- Add a brief note that the workflow is fully compatible with Linux/macOS terminals.
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 to the CLI. The inclusion of PowerShell as a main workflow, and its detailed example, may create friction for Linux/macOS users, especially since native shell (bash/zsh) examples are not provided. The order of examples (portal, CLI, PowerShell) does not overtly prioritize Windows, but the presence of PowerShell as a core example is a mild bias.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider adding a bash/zsh shell example for invoking Azure CLI commands, demonstrating Linux/macOS usage.
- Explicitly note PowerShell's platform support, and suggest alternatives for Linux/macOS users if relevant.
- Ensure that CLI instructions are comprehensive and do not assume Windows-specific shell environments.
API Management
Quickstart: Create Azure API Management instance by using Bicep
.../blob/main/articles/api-management/quickstart-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all tasks, but PowerShell is featured equally alongside CLI, and PowerShell is a Windows-centric tool. The structure presents CLI and PowerShell examples in tabbed format, but PowerShell is included throughout, which may imply Windows as a primary platform. No Linux-specific tools or shell examples (e.g., Bash) are given, and there is no explicit mention of Linux/macOS compatibility or differences.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and are platform-agnostic.
- Consider mentioning Bash or shell environments for Linux/macOS users, or explicitly state that Azure CLI commands can be run in Bash, Zsh, or other shells.
- Add a note about Azure PowerShell being primarily for Windows, and recommend Azure CLI for cross-platform usage.
- If possible, provide example screenshots or terminal prompts from Linux/macOS environments to reinforce parity.
- Ensure that prerequisites for Azure CLI include instructions for Linux/macOS installation, not just Windows.
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 networking concepts. However, there is a minor Windows bias in the 'Related content' section, where a link is provided to a guide on connecting virtual networks using PowerShell, a Windows-centric tool, without mentioning or linking to equivalent CLI or Bash guidance. Additionally, PowerShell is referenced before any cross-platform alternatives, which may create the impression that Windows tools are preferred or required.
Recommendations
- In the 'Related content' section, add links to equivalent Azure CLI and/or Bash-based guides for connecting virtual networks, if available.
- Where PowerShell is mentioned, clarify that Azure CLI and other cross-platform tools can also be used, and provide links or references to those alternatives.
- Ensure that examples and guidance throughout the documentation include both PowerShell and Azure CLI (or Bash) options when 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 instructions primarily through the Azure Portal and Azure CLI, with a single mention of Azure PowerShell as an alternative tool for disabling routing to a regional gateway. The PowerShell cmdlet is referenced after the Azure CLI and REST API, and no Windows-specific tools or patterns are prioritized. All code examples and instructions are platform-neutral or CLI-based, and there are no PowerShell-heavy sections or Windows-only tools. However, the PowerShell cmdlet is mentioned before explicitly referencing 'other Azure tools', which could be seen as a minor Windows-first ordering.
Recommendations
- Explicitly mention that all Azure CLI commands are cross-platform and suitable for Linux/macOS users.
- When listing Azure tools, consider listing Azure CLI before PowerShell, or clarify parity between them.
- Add a note for Linux/macOS users about Azure CLI installation and usage if relevant.
- If referencing PowerShell, provide equivalent Bash or shell script examples when appropriate.
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/PowerShell (Azure PowerShell) as an option for creating an AKS cluster before Linux alternatives (Azure CLI), but provides parity by also referencing the Azure CLI and Azure portal. All command examples use kubectl, which is cross-platform. No Windows-specific tools or patterns are used in the main deployment steps.
Recommendations
- List Azure CLI before Azure PowerShell in the prerequisites, as CLI is more widely used and cross-platform.
- Explicitly note that kubectl commands work on Windows, Linux, and macOS terminals.
- Consider providing links to Linux/macOS-specific installation guides for prerequisites (kubectl, Azure CLI).