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 426-450 of 594 flagged pages
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/grpc-api.md
...ure-docs/blob/main/articles/api-management/grpc-api.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation does not provide any OS-specific command-line examples, but it does reference .NET (which is cross-platform but often associated with Windows) for calling gRPC services. There are no explicit Linux or macOS instructions, nor are there examples using Linux-native tools or patterns. The documentation also does not mention Powershell or Windows-specific tools directly, but the absence of Linux examples and the presence of .NET references may create a subtle Windows-first impression.
Recommendations
- Include examples or references for calling gRPC services using popular Linux tools (e.g., grpcurl, grpc_cli) or languages commonly used on Linux (such as Python, Go, or Java).
- Explicitly mention that .NET is cross-platform and provide instructions for Linux and macOS users where relevant.
- Add a section or links for testing or interacting with gRPC APIs from Linux/macOS environments.
- Ensure parity in documentation by including both Windows and Linux/macOS command-line examples where applicable.
Create Pull Request
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/how-to-deploy-self-hosted-gateway-container-apps.md
...nt/how-to-deploy-self-hosted-gateway-container-apps.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, but consistently lists Bash first, followed by PowerShell. There are no exclusive Windows tools or patterns, and no steps are limited to Windows. However, the presence of PowerShell examples throughout, and the explicit '[PowerShell](#tab/psh)' tabs, indicate a bias toward Windows users, as there are no explicit Linux-specific shell examples (e.g., zsh, fish) or notes about Linux environments. All CLI examples are cross-platform, but the dual Bash/PowerShell split may suggest a Windows-centric approach.
Recommendations
- Clarify that Bash examples are suitable for Linux, macOS, and Windows (with WSL or Git Bash), and that PowerShell is available cross-platform.
- Add a brief note in the prerequisites or introduction explicitly stating that all CLI commands work on Linux, macOS, and Windows.
- Consider including a generic 'Shell' tab for commands that are identical across Bash and other POSIX shells, to avoid over-emphasizing PowerShell.
- If relevant, mention any Linux-specific considerations (such as file permissions, environment variable syntax differences, or package dependencies) to improve Linux parity.
- Ensure that any troubleshooting or advanced sections include Linux-specific guidance if Windows-specific guidance is present.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/protect-with-ddos-protection.md
...rticles/api-management/protect-with-ddos-protection.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by referencing only the Azure portal (a web GUI) and linking to a PowerShell-based guide for enabling DDoS IP Protection, without providing equivalent CLI or Linux-native instructions. There are no examples using Azure CLI, Bash, or other cross-platform tools, and the only automation example is PowerShell-centric.
Recommendations
- Add Azure CLI (az) command examples for enabling DDoS Protection on both VNets and public IP addresses, as Azure CLI is cross-platform and widely used on Linux.
- Where PowerShell scripts or references are provided, include equivalent Bash or Azure CLI commands.
- Explicitly mention that the Azure portal is accessible from any OS, but provide automation examples for both Windows (PowerShell) and Linux/macOS (CLI/Bash).
- Review all linked guides (such as the one for enabling DDoS IP Protection) to ensure they include cross-platform instructions, not just PowerShell.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/set-backend-service-policy.md
.../articles/api-management/set-backend-service-policy.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references Windows-specific tools (PowerShell) for backend management and omits mention of Linux-native or cross-platform alternatives. No Linux command-line or scripting examples are provided, and the only CLI tool referenced is PowerShell, which is traditionally associated with Windows.
Recommendations
- Include Azure CLI examples for managing backend entities, as Azure CLI is cross-platform and widely used on Linux.
- Mention and link to Azure CLI documentation alongside PowerShell in the note about backend management.
- If possible, provide Bash or shell script examples for relevant tasks to ensure parity for Linux users.
- Clarify that PowerShell Core is available cross-platform, if referencing PowerShell, and provide installation guidance for Linux if appropriate.
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 via 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. No PowerShell-heavy or Windows-only examples are present, and Linux parity is generally maintained. However, Azure PowerShell is mentioned before 'other Azure tools,' which could be considered a minor 'windows_first' bias.
Recommendations
- When listing tools for managing API Management instances, mention Azure CLI and PowerShell together, clarifying that both are cross-platform.
- Provide explicit examples for both Azure CLI and Azure PowerShell where relevant, and note that Azure CLI is available on Linux/macOS.
- If referencing 'other Azure tools,' consider linking to cross-platform options or clarifying their OS compatibility.
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 section. While Azure CLI and REST API examples are also included, the PowerShell examples are more prominent and detailed, which may create friction for Linux/macOS users who do not use PowerShell. There is no evidence of missing Linux examples, as Azure CLI (bash) and REST API methods are documented, but the ordering and depth of PowerShell coverage suggest a Windows bias.
Recommendations
- Present Azure CLI (bash) examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Ensure that Azure CLI examples are as detailed and comprehensive as PowerShell examples, including managed identity scenarios.
- Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI and REST API, and clarify any limitations.
- Consider adding a summary table comparing PowerShell, Azure CLI, and REST API approaches for quick reference.
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 PowerShell examples are given their own section. There are no Linux-specific examples or explicit mention of Linux/macOS compatibility for CLI commands, but the CLI example is cross-platform. The documentation does not use Windows-only tools or patterns, but PowerShell is a Windows-centric shell, and its inclusion without Bash or Linux shell alternatives may create friction for Linux/macOS users.
Recommendations
- Explicitly state that Azure CLI is cross-platform and works on Linux/macOS.
- Consider adding Bash or shell script examples for Linux users, or clarify that Azure CLI commands are suitable for Linux/macOS.
- Mention PowerShell Core compatibility if relevant, since PowerShell Core runs on Linux/macOS.
- List Azure CLI as the preferred cross-platform tool in prerequisites and examples, with PowerShell as an optional Windows-centric alternative.
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
Missing Linux Example
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, but the PowerShell example is given equal prominence to the CLI example, despite PowerShell being primarily a Windows tool. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is presented as a standard workflow alongside CLI, which may create friction for Linux/macOS users. The CLI example is cross-platform, but the lack of explicit Linux/macOS context or examples (such as Bash or zsh) and the inclusion of PowerShell as a main tab suggest a mild Windows bias.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS as well as Windows.
- Consider adding Bash/zsh shell examples for Linux/macOS users, or explicitly note that PowerShell is optional and CLI is cross-platform.
- Reorder examples to show Azure CLI first, and PowerShell as an alternative for Windows users.
- Add a note about how to install and use Azure CLI on Linux/macOS.
- Mention that PowerShell Core is available cross-platform, but most Linux/macOS users prefer Bash/zsh.
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 deployment and resource management steps. Azure CLI is cross-platform, while PowerShell is primarily associated with Windows, though it is available on Linux/macOS. The CLI examples are always presented before PowerShell, and there are no Windows-specific tools or patterns prioritized. No Linux/macOS-specific examples or shell scripts are provided, but the CLI coverage ensures parity.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Consider adding Bash shell script examples for Linux/macOS users, especially for automation.
- Clarify that PowerShell examples are for users who prefer PowerShell, which is now cross-platform.
- Add a note about Azure CLI installation on Linux/macOS for completeness.
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 bias in the 'Related content' section, where a PowerShell-based guide is referenced for connecting virtual networks from different deployment models, without mentioning equivalent CLI or Linux-friendly options. No Windows-specific tools, patterns, or examples are present in the main guidance.
Recommendations
- In the 'Related content' section, add links to equivalent guides using Azure CLI or ARM templates for connecting virtual networks, ensuring Linux/macOS users have clear, first-class options.
- Where PowerShell is referenced, clarify that Azure CLI and Portal options exist and provide links to those alternatives.
- Review other cross-referenced documentation to ensure Linux/macOS parity in examples and tooling.
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 dedicated example introduces a mild Windows bias. Additionally, PowerShell is listed alongside CLI in the prerequisites and workflow steps, and the PowerShell example is given equal prominence to CLI, which may subtly prioritize Windows tools. However, all critical tasks can be completed using Azure CLI, which works on Linux and macOS, and no steps are Windows-only.
Recommendations
- Clarify that Azure PowerShell is available cross-platform (if true), or note any Windows-specific limitations.
- Consider adding Bash or shell script examples for Azure CLI to reinforce Linux parity.
- Explicitly mention that Azure CLI is fully supported on Linux/macOS and is the recommended cross-platform tool.
- If PowerShell is not required for Linux/macOS users, note that CLI is sufficient for all 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 Tools
Windows First
Summary
The documentation is generally platform-neutral, but there is minor evidence of Windows bias. Specifically, the 'Related content' section references 'Connect virtual networks from different deployment models using PowerShell', which is a Windows-centric tool, and it appears before any mention of Linux or cross-platform alternatives. No Linux-specific examples or CLI guidance are provided, and PowerShell is mentioned without reference to Azure CLI or Bash equivalents.
Recommendations
- Add links to equivalent Azure CLI documentation for connecting virtual networks, ensuring Linux/macOS users have clear guidance.
- When referencing PowerShell, also mention Azure CLI or Bash alternatives, or clarify if PowerShell Core (cross-platform) is supported.
- Review related content and examples to ensure Linux/macOS parity, such as including links to Bash or CLI-based tutorials.
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 regional gateways, Azure PowerShell is referenced alongside REST API and Azure CLI. Azure PowerShell is mentioned before Linux-native tools, and no Bash or Linux-specific scripting examples are provided. However, the Azure CLI is used for the main command-line examples, which is cross-platform.
Recommendations
- When listing programmatic options, mention Azure CLI before Azure PowerShell, as CLI is cross-platform.
- Provide Bash shell script examples for disabling/enabling regional gateways, especially 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 equivalent Bash examples.
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 extensive PowerShell examples for backup and restore operations, with PowerShell shown first in each section. While Azure CLI and REST API examples are also provided, there is a notable emphasis on PowerShell usage, which is most commonly associated with Windows environments. The PowerShell examples use Windows-style variable assignment and scripting, and the prerequisites highlight Azure PowerShell installation before mentioning CLI or REST alternatives. However, Linux/macOS users can use Azure CLI and REST API methods, which are documented in parity.
Recommendations
- Consider presenting Azure CLI examples before PowerShell, or at least alternating their order to avoid implicit Windows-first bias.
- Explicitly mention that Azure CLI and REST API methods are fully cross-platform and suitable for Linux/macOS users.
- Add a note clarifying that PowerShell Core is available on Linux/macOS, and provide any relevant installation guidance if PowerShell usage is intended for those platforms.
- Ensure that all critical operations have CLI and REST API examples, and highlight their parity with PowerShell.
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 prerequisites list both Azure CLI and Azure PowerShell, but does not mention Bash or other Linux-native tools. The PowerShell example is presented after the CLI example, but the overall structure and content are neutral. There are no Windows-only tools or patterns mentioned, and the Azure CLI example is cross-platform. However, there is a mild bias in listing PowerShell as a primary tool alongside CLI, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider adding Bash shell script examples for Azure CLI usage.
- Explicitly state that PowerShell is optional and primarily for Windows users.
- Mention that Azure CLI can be used on all platforms, while PowerShell is most common on Windows.
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. PowerShell is a Windows-centric tool, and its inclusion may create friction for Linux/macOS users. However, Azure CLI examples are present and shown first in each section, ensuring Linux parity. No Windows-only tools or patterns are mentioned, and all instructions are cross-platform except for PowerShell.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
- Consider adding a note for Linux/macOS users recommending Azure CLI as the preferred tool.
- Optionally, include Bash shell script examples for common tasks to further support Linux users.
- Ensure that all prerequisites and instructions for Azure CLI are clear and accessible for Linux/macOS environments.
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 it mentions the PowerShell cmdlet before the CLI command and does not provide Linux/macOS-specific guidance or examples. The overall workflow is portal-centric and cross-platform, but command-line instructions slightly favor Windows/PowerShell users.
Recommendations
- List Azure CLI commands before PowerShell cmdlets, as Azure CLI is cross-platform and preferred for Linux/macOS users.
- Explicitly state that Azure CLI works on Linux/macOS and provide any relevant shell usage tips.
- Add bash/zsh shell example snippets where appropriate, especially for scripting or automation.
- Clarify that all portal instructions are platform-agnostic.
- Consider mentioning that PowerShell Core is available on Linux/macOS if referencing 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, Azure PowerShell is primarily used on Windows and its example is given equal prominence. The PowerShell example is detailed and included alongside CLI, but there are no Linux/macOS-specific shell examples (e.g., Bash) or notes about cross-platform usage. Additionally, the PowerShell section appears after the CLI, but both are presented as primary options.
Recommendations
- Clarify that Azure CLI is fully cross-platform and suitable for Linux/macOS users.
- Add explicit notes or examples for Bash or other Linux-native shells if relevant.
- Mention that Azure PowerShell can be used on Linux/macOS, but CLI is generally preferred for cross-platform scenarios.
- Consider including a brief comparison table or guidance for users on different platforms to help them choose the best tool.
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 deployment, resource review, and cleanup steps. Azure CLI is cross-platform and appears first in each example section, while PowerShell (which is Windows-centric, though available on Linux/macOS) is provided as an alternative. No Windows-only tools or patterns are mentioned, and Linux users can complete all tasks using Azure CLI. There is a minor bias in that PowerShell is included throughout, but CLI is always shown first, minimizing friction.
Recommendations
- Consider clarifying that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Optionally, add a note that PowerShell examples are provided for users who prefer PowerShell, but Azure CLI is the default for cross-platform scenarios.
- Ensure that any referenced prerequisites for PowerShell mention its availability on Linux/macOS, if relevant.
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 presented before Azure CLI and REST API examples. While Azure CLI (bash) and REST API instructions are included, the prominence and order of PowerShell content may create friction for Linux/macOS users, especially since PowerShell is traditionally associated with Windows environments.
Recommendations
- Present Azure CLI (bash) examples before or alongside PowerShell examples to signal equal support for Linux/macOS users.
- Explicitly mention that Azure PowerShell is cross-platform and provide guidance for installing and using PowerShell on Linux/macOS.
- Expand CLI examples to cover managed identity scenarios, matching the detail provided in PowerShell sections.
- Add a note clarifying that all operations can be performed from Linux/macOS using Azure CLI or PowerShell Core.
- Ensure parity in variable setup and context for CLI and REST examples, matching the completeness of PowerShell instructions.
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 mentioned before Portal. However, all deployment and verification steps use kubectl commands, which are cross-platform and standard for Kubernetes. No Windows-specific tools or patterns are prioritized, and Linux/macOS users can follow all steps without friction.
Recommendations
- Consider listing Azure CLI before PowerShell in the prerequisites, as Azure CLI is more commonly used on Linux/macOS.
- Explicitly mention that kubectl commands work on Windows, Linux, and macOS to reassure non-Windows users.
- If possible, provide brief notes or links about installing kubectl on different platforms.
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 link to 'Connect virtual networks from different deployment models using PowerShell' is included, which presents Windows/PowerShell tooling before any Linux or cross-platform alternatives. No Linux-specific examples or CLI equivalents are mentioned alongside this reference.
Recommendations
- Add links or references to Azure CLI or Bash-based guides for connecting virtual networks, ensuring Linux/macOS users have parity.
- When referencing PowerShell-based documentation, also mention cross-platform alternatives (e.g., Azure CLI) where available.
- Review related content sections to ensure Windows tools are not presented as the default or only option.
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 focus and ordering may create friction for Linux/macOS users, as PowerShell is primarily associated with Windows environments. However, Azure CLI and REST API examples ensure Linux parity for all critical operations.
Recommendations
- Consider presenting Azure CLI examples before PowerShell, or at least alternating the order, to avoid implicit Windows-first bias.
- Explicitly note that Azure CLI and REST API methods are fully supported on Linux/macOS, and clarify PowerShell's cross-platform availability if relevant.
- Add a brief section explaining that all operations can be performed on Linux/macOS using Azure CLI or REST, and that PowerShell Core is available cross-platform if users prefer.
- Ensure that any references to installing PowerShell mention PowerShell Core for Linux/macOS, not just Windows 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
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 routing to a regional gateway. The PowerShell cmdlet is referenced after the Azure CLI example, and no explicit Windows-only tools or patterns are prioritized. All command-line examples use Azure CLI, which is cross-platform. There are no PowerShell-heavy sections, and Linux parity is generally maintained. However, Azure PowerShell is mentioned before 'other Azure tools', which could be seen as a minor 'windows_first' bias.
Recommendations
- When mentioning Azure PowerShell, clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Provide explicit examples for both Azure CLI and Azure PowerShell only if there are significant differences or if PowerShell is required for certain operations.
- Consider listing Azure CLI as the primary tool for scripting and automation, with PowerShell as an alternative for Windows users.
- Add a note that all Azure CLI commands work on Linux, macOS, and Windows.
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, with PowerShell (a Windows-centric tool) mentioned before the portal. However, all deployment and operational examples use cross-platform tools (kubectl), and no Windows-specific commands or tools are prioritized or exclusively used. There are no missing Linux/macOS examples, and the workflow is platform-neutral after cluster creation.
Recommendations
- List Azure CLI (cross-platform) before Azure PowerShell in the prerequisites to avoid subtle Windows-first ordering.
- Explicitly note that all kubectl commands work on Linux, macOS, and Windows.
- If possible, provide links to Linux/macOS-specific guidance for AKS cluster creation, or clarify that Azure CLI is recommended for cross-platform use.