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 526-550 of 594 flagged pages
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 cross-platform and does not focus on Windows-specific features. However, there is a minor bias in the 'Related content' section, where a PowerShell-based guide is linked for connecting virtual networks, and no equivalent CLI/Bash or Linux-native example is provided. Additionally, PowerShell is mentioned before any cross-platform alternatives.
Recommendations
- In the 'Related content' section, add links to equivalent guides using Azure CLI (az) or Bash scripts for connecting virtual networks, ensuring Linux/macOS users have clear, native instructions.
- When referencing PowerShell-based operations, also mention or link to cross-platform alternatives (e.g., Azure CLI, REST API, or ARM templates) where available.
- Review other linked articles to ensure that Linux/macOS users are not forced to use Windows tools for critical operations.
Create Pull Request
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 brief mention of Azure PowerShell as an alternative tool for disabling regional gateways. The PowerShell cmdlet is referenced after the CLI example and is not the sole method shown. No Windows-specific tools or patterns are prioritized, and Linux parity is generally maintained. However, the PowerShell reference appears before any mention of Linux shell scripting, and there are no explicit Bash or Linux shell examples, which could be improved for parity.
Recommendations
- When referencing Azure PowerShell, also mention Bash or Linux shell alternatives explicitly, such as Azure CLI usage in Bash.
- Provide example CLI commands in both Windows (PowerShell) and Linux (Bash) syntax where relevant.
- Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- If scripting is discussed, include sample Bash scripts alongside PowerShell scripts.
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 CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. Both tools are cross-platform, but PowerShell is still more commonly used on Windows. The CLI example is given before PowerShell, but there is no explicit Linux/macOS example or mention of Linux-specific workflows. The documentation does not reference Windows-only tools, but the inclusion of PowerShell may create friction for Linux/macOS users who are less likely to use it.
Recommendations
- Explicitly mention that Azure CLI and PowerShell are both cross-platform, and provide links or notes about installing and using PowerShell on Linux/macOS.
- Add a note clarifying that the Azure CLI commands work identically on Linux, macOS, and Windows.
- Consider adding a Bash shell example for Azure CLI to reinforce Linux parity.
- If PowerShell is included, provide installation instructions or links for Linux/macOS users.
- Ensure that screenshots and portal instructions are not Windows-specific (they currently are not).
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 CLI. The PowerShell section is detailed and included alongside CLI, but there are no Linux/macOS-specific examples or notes. The order of examples (portal, CLI, PowerShell) is neutral, but the presence of PowerShell as a main workflow may create friction for Linux/macOS users if they are unfamiliar with PowerShell.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, but may be more familiar to Windows users.
- Add explicit notes or examples for Linux/macOS users, such as using Bash or zsh with Azure CLI.
- Consider including sample CLI commands that demonstrate Linux/macOS shell usage (e.g., environment variable syntax differences).
- Mention that Azure CLI is fully cross-platform and preferred for Linux/macOS environments.
- If PowerShell is not required for Linux/macOS, indicate that CLI covers all functionality.
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 tools for managing API Management instances, it lists Azure PowerShell cmdlets alongside Azure CLI and REST API, with PowerShell mentioned before Linux-native equivalents. There are no explicit Linux/macOS examples or references to Bash scripting, and PowerShell is referenced as a primary automation tool. However, all core tasks can be completed via the Azure CLI or REST API, which are cross-platform.
Recommendations
- Add explicit Bash/Linux/macOS examples where scripting is discussed, especially for automation tasks.
- When listing automation tools, mention Azure CLI (cross-platform) before Azure PowerShell, or at least equally.
- Clarify that Azure CLI and REST API are fully supported on Linux/macOS, and provide links to their documentation.
- Consider including sample Bash scripts for common operations, such as disabling a regional gateway.
- Ensure screenshots and UI instructions are not Windows-specific (e.g., avoid referencing Windows-only portal features).
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 cross-platform, but there is a subtle Windows bias in the 'Related content' section, where a PowerShell-based guide is referenced for connecting virtual networks, and no equivalent CLI/Bash/Linux example is provided or referenced. No explicit Linux examples are missing from the main content, but the PowerShell-first reference may create friction for non-Windows users.
Recommendations
- Add references to Azure CLI or Bash-based guides for connecting virtual networks, alongside or in place of the PowerShell-specific link.
- Where possible, provide cross-platform command examples (Azure CLI, ARM templates) in addition to or instead of PowerShell.
- Review other related content links to ensure parity 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 provides Azure CLI and Azure PowerShell examples for disabling routing to a regional gateway, but only mentions PowerShell as an alternative to Azure CLI. There are no Linux/macOS-specific examples or explicit parity guidance. Azure portal instructions are platform-neutral, but command-line guidance could imply Windows bias by referencing PowerShell before other options.
Recommendations
- Explicitly state that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for automation regardless of OS.
- Add Bash shell examples or clarify that Azure CLI commands are identical on Linux/macOS.
- Mention that PowerShell Core is available cross-platform, or provide links to Linux/macOS installation guides for PowerShell if referenced.
- Where PowerShell is referenced, also reference Bash or other common shells to reinforce parity.
- Consider listing Azure CLI examples before PowerShell, as CLI is more universally accessible.
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 examples appearing before CLI and REST examples. While Azure CLI and REST API options are also documented, PowerShell is given prominence and more detailed scripting, which may create friction for Linux/macOS users who do not have access to PowerShell or prefer Bash scripting. However, all critical operations are also covered via Azure CLI and REST, ensuring Linux parity.
Recommendations
- Present Azure CLI examples before PowerShell or in parallel, to avoid Windows-first ordering.
- Expand Azure CLI sections to include managed identity scenarios, matching the detail provided in PowerShell examples.
- Explicitly note that Azure CLI and REST API are fully cross-platform and recommended for Linux/macOS users.
- Consider adding Bash scripting examples for common automation scenarios.
- Clarify that PowerShell is not required for Linux/macOS users and highlight CLI/REST parity.
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 CLI and Azure PowerShell, with PowerShell being Windows-centric. Both tools are cross-platform, but PowerShell is more commonly associated with Windows, and its inclusion may signal a Windows bias. The structure presents Azure CLI and PowerShell examples separately, but PowerShell is given equal prominence, which may create friction for Linux/macOS users. No Linux-specific shell or tool examples (e.g., Bash scripting) are provided, and PowerShell requirements are listed alongside CLI prerequisites.
Recommendations
- Clarify that Azure PowerShell is available cross-platform and provide guidance for Linux/macOS users if needed.
- Consider adding Bash or shell script examples for Linux/macOS users, or explicitly state that Azure CLI commands are suitable for all platforms.
- Reorder examples to show Azure CLI first, as it is more universally available across platforms.
- Add a note explaining the parity between Azure CLI and PowerShell for Linux/macOS users.
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. While Azure CLI and REST API examples are also included, the PowerShell examples are more extensive and appear before CLI and REST, which may create friction for Linux/macOS users who typically use Bash and CLI tools. No Windows-only tools or patterns are mentioned, and Linux parity is generally maintained, but the ordering and detail favor Windows/PowerShell users.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid Windows-first bias.
- Ensure CLI examples are as detailed as PowerShell examples, including managed identity scenarios.
- Explicitly mention that Azure CLI and REST API methods are fully cross-platform and suitable for Linux/macOS users.
- Consider adding a note at the top clarifying that all operations can be performed from Linux/macOS using CLI or REST.
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 historically Windows-centric, though now available cross-platform) and the explicit PowerShell example may create a perception of Windows bias. Additionally, the PowerShell example is given equal prominence to the CLI example, and PowerShell requirements are listed alongside CLI prerequisites. However, no critical steps are Windows-only, and Linux/macOS users can use the Azure CLI or portal to complete all tasks.
Recommendations
- Clarify that Azure PowerShell is available cross-platform and provide installation instructions for Linux/macOS if not already included.
- Consider mentioning Bash or shell scripting alternatives for Azure CLI usage, especially for users on Linux/macOS.
- If possible, indicate that all CLI commands are fully supported on Linux/macOS and provide links to relevant platform-specific documentation.
- Ensure that the order of examples does not imply Windows preference (e.g., list CLI first, then PowerShell).
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 on disabling routing to a regional gateway, Azure PowerShell is mentioned alongside Azure CLI and REST API, but no Linux-specific tools or shell examples (such as Bash scripting or references to Linux-native automation) are provided. Azure CLI is shown first, but PowerShell is referenced in the same sentence, which may create a slight impression of Windows-first bias. There are no explicit Windows-only tools or patterns, and no critical steps are Windows-only.
Recommendations
- Add explicit Bash shell examples for Azure CLI commands to reinforce Linux parity.
- Clarify that Azure CLI is fully cross-platform and can be used on Linux/macOS as well as Windows.
- If referencing PowerShell, also mention that Azure CLI is preferred for Linux/macOS users.
- Consider including links or notes about using Azure CLI in Bash or Zsh shells 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 in the section about disabling routing to a regional gateway, it references Azure PowerShell cmdlets alongside Azure CLI and REST API. The PowerShell example is mentioned after CLI, but no Linux/macOS-specific tools or shell examples are provided. However, Azure CLI is cross-platform and the portal instructions are OS-agnostic. There are no Windows-only tools or patterns, and no exclusive PowerShell or Windows tool usage, but PowerShell is referenced without explicit Linux parity.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS.
- Add explicit Bash or shell script examples if relevant.
- When referencing PowerShell, note that Azure PowerShell is available cross-platform, or provide equivalent CLI commands for all tasks.
- Consider mentioning that all portal steps are OS-independent.
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, ensuring Linux/macOS users are supported. However, PowerShell is emphasized and presented before cross-platform alternatives, which may create a perception of Windows preference.
Recommendations
- Present Azure CLI examples before PowerShell, or alternate the order to avoid Windows-first bias.
- Explicitly note that Azure CLI and REST API methods are fully supported on Linux/macOS and are recommended for cross-platform environments.
- Add clarifying statements that PowerShell examples are for users who prefer or require PowerShell, while CLI and REST are suitable for all platforms.
- Consider including Bash scripting examples for common automation scenarios, further demonstrating Linux parity.
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 and detail. The PowerShell section is not marked as Windows-specific, and there is no mention of Linux/macOS compatibility or alternatives for PowerShell. The order of examples is CLI first, then PowerShell, which is not Windows-first, but the PowerShell example is detailed and assumes cross-platform availability without clarification. No Windows-only tools or patterns are mentioned, and the Azure CLI example is fully cross-platform.
Recommendations
- Clarify that Azure PowerShell is available on Linux/macOS, or explicitly note any limitations.
- Provide Bash or shell script examples for Linux users if relevant.
- Add a note about cross-platform compatibility for both Azure CLI and PowerShell.
- Consider mentioning that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
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 both Azure PowerShell and Azure CLI examples for backup and restore operations, but PowerShell examples are presented first and in greater detail. PowerShell is primarily a Windows-centric tool, and its prominence may create friction for Linux/macOS users. However, full Azure CLI (bash) and REST API examples are also included, ensuring Linux parity for all critical operations.
Recommendations
- Present Azure CLI examples before PowerShell, or at least in parallel, to avoid Windows-first bias.
- Expand CLI sections to match the detail and coverage of PowerShell examples, including managed identity scenarios if possible.
- Explicitly mention that Azure CLI and REST API methods are fully cross-platform and suitable for Linux/macOS users.
- Add a brief note clarifying that PowerShell is available on Linux/macOS, but CLI is often preferred for those platforms.
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 the Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is most commonly used on Windows) as a primary example, and the explicit mention of PowerShell requirements in the prerequisites, introduces a mild Windows bias. Additionally, PowerShell examples are given equal prominence to CLI examples, and the PowerShell section appears after the CLI section, which is positive, but the overall structure still emphasizes Windows tooling.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Add a note in the PowerShell section indicating that Azure PowerShell is available on Linux/macOS, but CLI is generally more common for non-Windows environments.
- Consider adding Bash shell scripting examples for CLI usage, highlighting Linux/macOS workflows.
- Explicitly mention that all tasks can be completed on Linux/macOS using Azure CLI, and link to any relevant Linux/macOS setup guides.
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 scripting tools for managing API Management instances, Azure PowerShell is referenced alongside Azure CLI. The PowerShell cmdlet is mentioned before other tools, and no Linux-specific shell or scripting examples (e.g., Bash) are provided. However, the Azure CLI is cross-platform and is used for the main command-line examples. There are no exclusive Windows tools or patterns, and the overall workflow is accessible to Linux/macOS users.
Recommendations
- When listing scripting tools, mention Azure CLI first, as it is cross-platform, and clarify that Azure PowerShell is available on Linux/macOS as well.
- Add Bash shell script examples for disabling/enabling regional gateways using Azure CLI.
- Explicitly state that all Azure CLI commands can be run on Linux/macOS terminals.
- Consider linking to Azure CLI installation guides 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, the inclusion of Azure PowerShell (which is more commonly used on Windows) as a primary example, and the explicit mention of PowerShell requirements in prerequisites, may signal a Windows bias. Additionally, PowerShell examples are given equal prominence to CLI, which could be confusing for Linux/macOS users, as PowerShell is less common on those platforms. However, the CLI example is present and fully functional for Linux/macOS users, and no critical steps are Windows-only.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Mention that Azure PowerShell is available cross-platform, but is more commonly used on Windows.
- Consider providing Bash shell scripting examples alongside PowerShell, or explicitly state that Bash users should use Azure CLI.
- Reorder examples to show Azure CLI before PowerShell, or indicate platform recommendations for each tool.
- In prerequisites, clarify that Azure PowerShell is optional and not 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 Tools
Powershell Heavy
Windows First
Summary
The documentation references Azure PowerShell cmdlets (set-azapimanagement) alongside Azure CLI and REST API for managing regional gateways, and lists PowerShell before CLI in the tools section. However, the only explicit command-line examples provided are for Azure CLI, which is cross-platform. No Linux-specific examples or tools are mentioned, and there is no indication of Linux/macOS incompatibility for the described tasks.
Recommendations
- Ensure that all command-line examples are provided for both Azure CLI and PowerShell, with clear notes on cross-platform compatibility.
- When listing management tools, mention Azure CLI before PowerShell to avoid Windows-first bias, or clarify that both are supported across platforms.
- Explicitly state that all tasks can be performed from Linux/macOS using Azure CLI and REST API, and provide links to installation guides for these platforms.
- If PowerShell is referenced, clarify that Azure PowerShell is available on Linux/macOS and provide installation instructions.
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 Tools
Powershell Heavy
Windows First
Summary
The documentation page provides Azure CLI and Azure PowerShell examples for managing multi-region deployments of Azure API Management, but it mentions the PowerShell cmdlet ('set-azapimanagement') before the Azure CLI command ('az apim update') when describing how to disable routing to a regional gateway. Additionally, the reference to 'other Azure tools' is vague and does not specify Linux/macOS-compatible alternatives. There are no explicit Linux/macOS examples or notes about cross-platform usage, and screenshots and instructions are focused on the Azure Portal UI, which is cross-platform but does not address CLI parity.
Recommendations
- List Azure CLI commands before PowerShell commands, as Azure CLI is cross-platform and preferred for Linux/macOS users.
- Explicitly mention that Azure CLI is available on Linux/macOS and provide installation links or references.
- Provide Bash shell script examples where appropriate, especially for automation tasks.
- Clarify 'other Azure tools' to include REST API usage and cross-platform SDKs.
- Add a note that all Azure CLI commands work on Linux, macOS, and Windows.
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 Tools
Powershell Heavy
Windows First
Summary
The documentation page provides command-line examples for managing multi-region Azure API Management instances, but only includes Azure PowerShell and Azure CLI examples. The PowerShell cmdlet (set-azapimanagement) is mentioned alongside the CLI, and Windows-centric terminology (context menu, UI navigation) is used. There are no Linux/macOS-specific instructions or examples, and Windows tools are referenced before their cross-platform equivalents.
Recommendations
- Add explicit Linux/macOS parity notes for Azure CLI usage, clarifying that all CLI commands work cross-platform.
- Include bash shell examples for CLI commands, and clarify any OS-specific differences (such as line continuations, quoting).
- When referencing PowerShell, note that Azure PowerShell is available on Linux/macOS, or provide equivalent CLI commands where possible.
- Avoid Windows-centric UI terminology (e.g., 'context menu', '... button') or clarify how these actions are performed on other platforms.
- Consider adding screenshots or instructions for Azure Portal navigation on non-Windows platforms if UI differs.
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 Tools
Powershell Heavy
Windows First
Summary
The documentation page provides command-line examples for managing Azure API Management multi-region deployments using Azure CLI and PowerShell. While Azure CLI is cross-platform, the explicit mention and linking of Azure PowerShell cmdlets (set-azapimanagement) and the ordering of PowerShell before other tools in the disable routing section indicate a mild Windows bias. There are no Linux/macOS-specific examples or explicit parity notes, and the documentation does not mention Bash scripting or Linux shell usage. However, the core instructions are portal-based or use Azure CLI, which is available on all platforms.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS.
- When listing command-line tools, mention Azure CLI first as it is cross-platform, and provide parity examples for Bash or shell scripting if relevant.
- Add a note that PowerShell cmdlets are available on Linux/macOS via PowerShell Core, or provide equivalent Bash/CLI examples where possible.
- Avoid listing Windows-specific tools (PowerShell) before cross-platform tools unless there is a technical reason.
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 Tools
Powershell Heavy
Windows First
Summary
The documentation references Azure PowerShell cmdlets (set-azapimanagement) alongside Azure CLI and REST API for managing regional gateways, and lists PowerShell before CLI in the list of tools. However, all command-line examples provided are Azure CLI, which is cross-platform. No explicit Linux/macOS examples or tools are given, and there is no mention of Linux-specific considerations or parity in the walkthroughs. The documentation assumes use of the Azure portal and CLI, which are available on all platforms, but the presence and ordering of PowerShell references may create minor friction for Linux/macOS users.
Recommendations
- Ensure that all command-line examples are provided for both Azure CLI and Azure PowerShell, or clarify platform compatibility for each tool.
- Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is available on all platforms but may require additional installation steps.
- If PowerShell is mentioned, provide equivalent Bash or shell script examples for Linux/macOS users.
- Review ordering of tool references to list Azure CLI before PowerShell, or group them neutrally.
- Add a short note in the prerequisites or tool usage sections about platform compatibility and installation instructions for CLI and PowerShell 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 Tools
Powershell Heavy
Windows First
Summary
The documentation provides command-line examples for managing multi-region API Management deployments using Azure CLI and PowerShell. While Azure CLI is cross-platform, the documentation explicitly mentions the Azure PowerShell cmdlet (set-azapimanagement) alongside CLI and REST API, and lists PowerShell before mentioning 'other Azure tools'. No Linux/macOS-specific tools or shell examples are provided, and PowerShell is referenced as a primary method for some operations. The general workflow and UI instructions are platform-agnostic, but command-line automation examples show a mild Windows/PowerShell bias.
Recommendations
- Ensure all command-line examples use Azure CLI as the default, since it is cross-platform.
- If PowerShell is mentioned, clarify that Azure CLI works on Linux/macOS and provide Bash shell examples where appropriate.
- Add explicit notes or examples for Linux/macOS users, such as shell scripting or automation approaches.
- Reorder references so that Azure CLI is listed before PowerShell, emphasizing cross-platform parity.