API Management
548
Total Pages
499
Linux-Friendly Pages
49
Pages with Bias
8.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
112 issues found
Showing 76-100 of 112 flagged pages
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/import-app-service-as-api.md
...n/articles/api-management/import-app-service-as-api.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric development patterns (ASP.NET Core, Visual Studio Code) and omitting Linux-specific examples or tooling. All examples and tutorials assume a Windows-based workflow, with no mention of Linux alternatives for creating, publishing, or managing Azure web apps and APIs.
Recommendations
- Add Linux-specific examples for creating and publishing web APIs, such as using Python (Flask, FastAPI), Node.js, or Java.
- Include instructions for deploying web apps to Azure App Service from Linux environments, e.g., using Azure CLI, GitHub Actions, or Docker.
- Reference Linux-friendly editors and tools (e.g., VS Code on Linux, JetBrains IDEs, command-line workflows) alongside Visual Studio Code.
- Explicitly mention cross-platform compatibility and provide parity in screenshots and step-by-step guides for both Windows and Linux users.
- Highlight any differences or considerations when using Azure portal and API Management from Linux systems.
Create Pull Request
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/import-container-app-with-oas.md
...ticles/api-management/import-container-app-with-oas.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing the Azure portal UI and not providing any command-line examples. There are no CLI (az), PowerShell, or Bash examples, nor is there mention of Linux-specific workflows. All instructions are centered around the Azure portal, which is platform-agnostic but often associated with Windows-first workflows. There are no explicit Linux or cross-platform command-line instructions, nor are alternative tools (such as cURL, Bash scripts, or az CLI) mentioned.
Recommendations
- Add examples using the Azure CLI (az) for importing and testing APIs, which are cross-platform and widely used on Linux.
- Include Bash/cURL command examples for testing the imported API, in addition to the Azure portal UI.
- Explicitly mention that all steps can be performed from any OS via the Azure portal, and highlight any platform-specific considerations if they exist.
- Provide PowerShell and Bash script equivalents for common tasks, ensuring parity between Windows and Linux users.
- Where screenshots are used, ensure they do not show Windows-specific UI elements (such as Windows file paths or PowerShell prompts).
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
Windows Tools
Missing Linux Example
Summary
The documentation references enabling DDoS IP Protection via a link to a Powershell-based guide, but does not mention or provide equivalent Linux/CLI examples. The instructions for enabling DDoS Protection focus on the Azure Portal UI, which is platform-agnostic, but the only programmatic example referenced is Windows/Powershell-specific. No Bash, Azure CLI, or Linux-native instructions are provided.
Recommendations
- Add Azure CLI examples for enabling DDoS Protection on a public IP address and virtual network, ensuring Linux users have parity.
- Explicitly mention that both Powershell and Azure CLI can be used, and provide links to both sets of instructions.
- Where possible, include Bash script snippets or instructions for Linux environments alongside Powershell examples.
- Review related linked documentation to ensure Linux/CLI instructions are present and referenced equally.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-protect-backend-with-aad.md
...ement/api-management-howto-protect-backend-with-aad.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows by exclusively referencing the Azure portal (a web-based, Microsoft-centric tool) for all configuration steps, without mentioning or providing alternatives using cross-platform or Linux-friendly tools such as Azure CLI, Azure PowerShell (on Linux), or REST APIs. No command-line or automation examples are provided, which are often preferred in Linux environments.
Recommendations
- Add equivalent instructions using Azure CLI commands for all major steps, such as app registration and scope creation.
- Provide REST API examples for automation and cross-platform compatibility.
- Mention and link to Azure PowerShell (which is cross-platform) as an alternative to the Azure portal.
- Explicitly state that all steps can be performed from Linux, macOS, or Windows using CLI or REST, and provide sample commands.
- Consider including a table or section comparing different methods (Portal, CLI, REST) for each configuration step.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/azure-ai-foundry-api.md
...b/main/articles/api-management/azure-ai-foundry-api.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (a web-based GUI commonly accessed from Windows environments) for all instructions, with no mention of command-line alternatives such as Azure CLI, Bash, or PowerShell. There are no Linux-specific examples or guidance for users who may prefer or require non-GUI, cross-platform workflows. The absence of CLI or automation options limits parity for Linux users and those working in headless or automated environments.
Recommendations
- Add equivalent instructions for importing Microsoft Foundry APIs using Azure CLI, Bash, or PowerShell, ensuring examples are cross-platform.
- Include sample commands and scripts for Linux environments, such as using az apim commands to create and configure APIs.
- Reference automation and infrastructure-as-code options (e.g., ARM templates, Bicep, Terraform) for users who do not use the portal.
- Explicitly state that the portal is accessible from any OS, but provide parity for users who prefer or require CLI-based workflows.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-versions.md
...ain/articles/api-management/api-management-versions.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page references Azure PowerShell as a management tool alongside Azure CLI, Resource Manager templates, and REST API, but does not mention Linux-specific equivalents or clarify cross-platform compatibility. Azure PowerShell is a Windows-centric tool, and its mention before clarifying CLI parity may suggest a Windows-first approach. No explicit Linux command-line examples or Linux-specific instructions are provided.
Recommendations
- Clarify that Azure CLI and Azure PowerShell are both cross-platform, and provide explicit instructions or examples for Linux users where relevant.
- Include Linux shell (bash) examples for API management tasks, especially where PowerShell is referenced.
- Mention that Azure CLI is available on Linux and macOS, and highlight any differences in usage or installation between platforms.
- If screenshots or UI instructions are provided, note any platform-specific differences in appearance or behavior.
- Consider listing Azure CLI before Azure PowerShell to avoid implicit Windows-first ordering.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/credentials-how-to-azure-ad.md
...articles/api-management/credentials-how-to-azure-ad.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively uses the Azure Portal (web UI) for all configuration steps, which is a cross-platform tool, but it does not provide any command-line examples. There are no references to Linux-native tools (such as Azure CLI or Bash scripting), nor are there any PowerShell or Windows-specific commands. However, the absence of CLI examples (like Azure CLI or Bash) means Linux users do not have parity with those who might prefer or require command-line automation.
Recommendations
- Add equivalent Azure CLI commands for each portal-based step, especially for app registration, permission granting, and credential provider setup.
- Include Bash script examples for automating the process on Linux systems.
- Explicitly mention that all steps can be performed using Azure CLI or REST API, and link to relevant documentation.
- Provide a section or appendix with end-to-end CLI-based workflow for Linux users.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/expose-existing-mcp-server.md
.../articles/api-management/expose-existing-mcp-server.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates mild Windows bias by recommending Visual Studio Code (VS Code) for testing the MCP server and referencing GitHub Copilot integration, both of which are commonly associated with Windows environments. There are no explicit examples or instructions for Linux users, nor are alternative Linux-native tools suggested. The documentation does not provide command-line or shell examples, nor does it mention Powershell, but it does omit Linux-specific testing workflows and tools.
Recommendations
- Include Linux-native alternatives for testing MCP servers, such as curl, httpie, or Postman (which is cross-platform).
- Explicitly mention that VS Code and GitHub Copilot are available on Linux and macOS, or suggest equivalent editors and tools for those platforms.
- Provide example commands for both Windows (Powershell, CMD) and Linux (bash, zsh) when relevant.
- Add a section or note on how to test MCP servers from a Linux shell environment.
- Ensure screenshots and instructions are not exclusively tailored to Windows UI conventions.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/import-app-service-as-api.md
...n/articles/api-management/import-app-service-as-api.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric development tools (such as Visual Studio Code and ASP.NET Core tutorials) and omitting Linux-specific instructions or examples. There are no examples of using Linux command-line tools, deployment patterns, or alternative Linux-based workflows. The documentation assumes usage of the Azure portal and Visual Studio Code, which, while cross-platform, are more commonly associated with Windows environments. No Linux shell commands, package managers, or deployment instructions are provided.
Recommendations
- Add explicit instructions and examples for deploying web APIs from Linux environments, such as using the Azure CLI, Bash scripts, or Linux-based CI/CD pipelines.
- Include references to Linux development tools (e.g., VS Code on Linux, JetBrains Rider, or command-line editors) and how to publish to Azure App Service from those environments.
- Provide sample commands for creating and deploying web apps using Linux shell (e.g., Bash) and the Azure CLI.
- Mention cross-platform compatibility for all tools and clarify when steps are identical or different on Linux vs. Windows.
- Add links to documentation or tutorials specifically targeting Linux users, such as 'Deploy a Python/Node.js web app to Azure App Service from Ubuntu'.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/protect-with-defender-for-apis.md
...icles/api-management/protect-with-defender-for-apis.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes using the Azure portal (a web-based GUI) for all operations, with no mention of command-line alternatives such as Azure CLI, PowerShell, or REST API. While this avoids explicit Windows tool bias, it implicitly favors Windows/GUI workflows, which are more familiar to Windows users. There are no examples or guidance for Linux users or those who prefer automation via CLI or scripts.
Recommendations
- Add Azure CLI examples for enabling Defender for APIs, onboarding/offboarding APIs, and viewing security insights, as Azure CLI is cross-platform and widely used on Linux.
- If relevant, provide REST API examples for all major operations, allowing users on any platform to automate tasks.
- If PowerShell examples are included in the future, ensure Azure CLI or Bash equivalents are always provided alongside.
- Explicitly mention that all operations can be performed via the portal, CLI, or REST API, and link to relevant automation documentation.
- Consider a section summarizing cross-platform options for managing Defender for APIs, highlighting parity between Windows and Linux workflows.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/self-hosted-gateway-enable-azure-ad.md
.../api-management/self-hosted-gateway-enable-azure-ad.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by referencing Azure portal and PowerShell/CLI tools before or alongside Linux-friendly options, and by linking to portal-based (GUI) instructions, which are more familiar to Windows users. However, the actual deployment and configuration steps are Kubernetes/YAML-centric, which are cross-platform and Linux-native. There are no explicit PowerShell-only examples, but the instructions for creating roles and app registrations reference the Azure portal and PowerShell/CLI documentation before mentioning Linux-specific alternatives.
Recommendations
- Provide explicit Azure CLI examples for all steps (role creation, assignment, app registration) directly in the documentation, not just as links.
- When referencing Azure portal or PowerShell, always mention Azure CLI and/or ARM templates as first-class alternatives, and consider listing CLI examples before portal/PowerShell.
- Add a section or callout clarifying that all steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.
- Where possible, include bash scripts or command-line snippets for Linux users, especially for role assignments and app registration.
- Review all links to ensure parity between Windows (PowerShell/portal) and Linux (CLI/script) guidance.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/how-to-deploy-self-hosted-gateway-kubernetes-opentelemetry.md
...to-deploy-self-hosted-gateway-kubernetes-opentelemetry.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation displays mild Windows bias by referencing Windows-specific tools (PowerShell, Azure portal) before Linux alternatives and using Windows-style path separators (e.g., .\opentelemetry-collector-config.yml) in command examples. However, most technical steps use cross-platform tools (Helm, kubectl, curl), and Linux users can follow along with minimal adaptation.
Recommendations
- Present Linux and Windows options equally when listing tools (e.g., mention Azure CLI before PowerShell or in parallel).
- Use platform-neutral path separators in command examples (e.g., './opentelemetry-collector-config.yml' instead of '.\opentelemetry-collector-config.yml').
- Explicitly note that all commands work on Linux, macOS, and Windows, and provide any necessary adaptations for each platform.
- Where PowerShell or Azure portal is mentioned, also provide direct Linux CLI equivalents or links.
- Add a note in prerequisites clarifying that Helm, kubectl, and curl are available on all major platforms.
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 mentions Azure PowerShell cmdlets alongside Azure CLI and REST API. The PowerShell tool is referenced before Linux-native equivalents, and no explicit Linux/macOS-specific guidance or examples are provided. However, the CLI and REST API examples are cross-platform, and the overall workflow is not Windows-specific.
Recommendations
- Ensure that Azure CLI examples are presented before PowerShell examples, as CLI is cross-platform.
- Explicitly mention that Azure CLI and REST API commands work on Linux/macOS, and provide any relevant shell syntax tips if needed.
- If PowerShell is referenced, clarify that Azure PowerShell is available on Linux/macOS, or provide Bash alternatives where appropriate.
- Add a note that all steps can be completed on Linux/macOS unless there is a Windows-only requirement.
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 disabling routing to a regional gateway using Azure CLI and references Azure PowerShell cmdlets (set-azapimanagement) alongside REST API and Azure CLI. The Azure CLI is cross-platform, but the explicit mention of Azure PowerShell (which is most commonly used on Windows) and the order in which tools are listed (PowerShell before REST API and CLI) may suggest a slight Windows bias. No Linux/macOS-specific instructions or examples are provided, but all tasks can be completed using cross-platform tools.
Recommendations
- When listing command-line tools, mention Azure CLI first as it is cross-platform, followed by REST API, then Azure PowerShell.
- Clarify that Azure PowerShell is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
- Add explicit Linux/macOS shell examples where relevant, or note that Azure CLI commands work on all platforms.
- Avoid implying PowerShell is the primary or preferred method unless required by the task.
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 examples for managing API Management multi-region deployments using Azure CLI and Azure PowerShell, but does not mention or provide examples for Linux/macOS-specific tools or workflows. Azure PowerShell is referenced alongside Azure CLI, and the PowerShell cmdlet is mentioned before other tools in the section about disabling routing to a regional gateway. No Linux/macOS-specific shell examples (e.g., Bash) or platform notes are included, and the documentation assumes familiarity with Azure portal and CLI, which are cross-platform, but PowerShell is traditionally Windows-centric.
Recommendations
- Add explicit notes clarifying that Azure CLI commands work on Linux/macOS as well as Windows.
- Provide Bash shell examples for equivalent operations, especially for tasks currently shown only with Azure PowerShell.
- Reorder tool mentions so that cross-platform tools (Azure CLI) are listed before Windows-centric tools (PowerShell).
- Include a brief section or note on platform compatibility for all tools referenced.
- Where possible, link to documentation on installing and using Azure CLI and PowerShell on Linux/macOS.
API Management
VNet configuration settings | Azure API Management
...n/articles/api-management/virtual-network-reference.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows Specific Section
Summary
The documentation is generally platform-neutral, focusing on Azure networking concepts and configuration. However, there are several references to Windows-specific infrastructure (e.g., Windows Update, Windows Defender, KMS endpoint for Windows activation), and a section on port requirements for Windows VMs. There are no explicit Linux/macOS examples or equivalent sections, which may give the impression of a Windows-centric bias in infrastructure requirements.
Recommendations
- Add clarifications or equivalent guidance for Linux-based VMs, such as required ports for Linux package updates (e.g., apt, yum, or security updates) if relevant.
- Where Windows-specific endpoints (e.g., Windows Update, Defender, KMS) are mentioned, explicitly state that these are only required if Windows VMs are present, and clarify that Linux VMs may have different or no such requirements.
- Consider adding a section or note about Linux/macOS infrastructure needs, even if only to state that no additional endpoints are required for common distributions.
- Review related content links to ensure Linux users are equally supported (e.g., avoid only linking to PowerShell-based guides).
API Management
VNet configuration settings | Azure API Management
...n/articles/api-management/virtual-network-reference.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows Specific Section
Summary
The documentation is largely platform-neutral, focusing on Azure networking concepts and requirements. However, there are a few sections that reference Windows-specific infrastructure and tools, such as KMS activation for Windows VMs and Windows Update/Defender endpoints. There is also a mention of PowerShell in the context of management endpoints, but no explicit Linux/macOS alternatives or command-line examples are provided. These references are mostly in the context of supporting Windows VMs within the VNet, not for API Management itself.
Recommendations
- Clarify that Windows-specific sections (KMS, Windows Update/Defender) are only relevant if Windows VMs are present, and provide equivalent guidance for Linux VMs if applicable (e.g., mention Linux activation or update endpoints if needed).
- Where PowerShell is mentioned (e.g., 'Management endpoint for Azure portal and PowerShell'), add a note about cross-platform alternatives such as Azure CLI or REST API, or link to relevant documentation.
- Ensure that any command-line or tool references include Linux/macOS equivalents or explicitly state if only Windows is supported.
- If there are no Linux-specific requirements, explicitly state that the rest of the configuration is platform-agnostic.
API Management
Azure API Management - Overview and Key Concepts
...articles/api-management/api-management-key-concepts.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page references Azure PowerShell and Azure CLI as management tools, listing PowerShell first and mentioning Visual Studio Code extension (a Microsoft-centric tool). There are no explicit Linux/macOS examples, but the management plane is described in terms of Azure portal, PowerShell, CLI, and REST API. The self-hosted gateway is noted as Linux-based, which is positive for Linux parity. However, the overall framing of management tools leans toward Windows/Microsoft-centric options, with PowerShell mentioned before CLI and no explicit mention of Bash or Linux-native workflows.
Recommendations
- List Azure CLI before PowerShell when describing cross-platform management options, as CLI is natively supported on Linux/macOS.
- Explicitly mention that Azure CLI and REST API are fully supported on Linux/macOS.
- Provide links or examples for Linux/macOS users, such as Bash scripts or terminal usage.
- Clarify that Visual Studio Code is cross-platform, and suggest other editors or tools popular on Linux/macOS.
- Add a note that all management operations can be performed from Linux/macOS environments.
API Management
Subscriptions in Azure API Management | Microsoft Docs
...rticles/api-management/api-management-subscriptions.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation mentions Azure PowerShell as a tool for automating subscription key management workflows, but does not mention or provide equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API usage). No explicit Windows/Powershell examples are given, but the reference to PowerShell as the automation tool implies a Windows-centric approach. There are no command-line examples at all, but the only tool named is PowerShell.
Recommendations
- Mention Azure CLI as an alternative to Azure PowerShell for automating subscription key management, and provide example commands for both.
- Clarify that REST API operations can be performed using tools available on all platforms (e.g., curl, HTTPie, Postman), and provide sample requests.
- Where automation is discussed, explicitly state that workflows can be implemented using Bash scripts, Python, or other cross-platform tools.
- Ensure that any references to PowerShell are accompanied by Linux/macOS equivalents, or note that PowerShell Core is cross-platform.
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
Powershell Heavy
Summary
The documentation lists Windows-centric tools (Azure PowerShell) before Linux alternatives (Azure CLI) when describing how to create an AKS cluster. The mention of Azure PowerShell is explicit, and no Linux-specific shell or workflow is highlighted. However, the main deployment steps use kubectl, which is cross-platform, and no commands are exclusive to Windows or PowerShell. There are no Windows-only examples, but the ordering and tool references show a mild Windows-first bias.
Recommendations
- List Azure CLI before Azure PowerShell when describing AKS cluster creation, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly mention that kubectl commands work on Linux, macOS, and Windows.
- Provide links or notes for Linux/macOS users on installing Azure CLI and kubectl.
- Avoid implying PowerShell is a primary or preferred method unless necessary for a Windows-specific scenario.
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
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the PowerShell example is given equal prominence and detail, and prerequisites explicitly mention Azure PowerShell alongside Azure CLI. There is no explicit mention of Linux/macOS-specific considerations, nor are alternative Linux-native tools or shell examples provided. The ordering of examples (Portal, CLI, PowerShell) is neutral, but the inclusion and detail of PowerShell may signal a Windows-centric approach.
Recommendations
- Clarify that Azure CLI works on Linux/macOS and provide explicit shell (bash) examples where appropriate.
- Add a note or section for Linux/macOS users, confirming parity and any differences in experience or setup.
- Consider including troubleshooting or environment setup tips for Linux/macOS users (e.g., file paths, authentication).
- If PowerShell is mentioned, clarify that PowerShell Core is cross-platform, or provide bash alternatives for scripting tasks.
API Management
Self-Host the API Management Developer Portal
.../articles/api-management/developer-portal-self-host.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias in the section describing how to upload static files to Azure Blob Storage. It explicitly mentions 'Windows Command Prompt, PowerShell, or other command shell' and does not provide Linux/macOS-specific terminal instructions or examples. The rest of the documentation uses generic commands (git, npm, Azure CLI) that are cross-platform, and the GitHub Actions example uses Ubuntu, but the explicit mention of Windows shells and lack of Linux/macOS parity in the upload step creates minor friction for non-Windows users.
Recommendations
- Replace 'Open Windows Command Prompt, PowerShell, or other command shell.' with 'Open your terminal (Command Prompt, PowerShell, or a Linux/macOS shell)'.
- Explicitly state that the Azure CLI command works on Linux/macOS terminals as well.
- Optionally, provide example commands for Linux/macOS users, such as using bash/zsh.
- Add a note clarifying that all CLI commands are cross-platform unless otherwise specified.
API Management
Add a GraphQL API to Azure API Management | Microsoft Docs
...-docs/blob/main/articles/api-management/graphql-api.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a GraphQL API, but PowerShell is given equal prominence as CLI, and prerequisites explicitly list Azure PowerShell as a tool. PowerShell is a Windows-centric tool, and its inclusion alongside CLI (which is cross-platform) can signal a Windows bias. Additionally, the order of tabs is Portal, CLI, then PowerShell, which is a minor instance of 'windows_first' since PowerShell is featured before other Linux-native tools (e.g., Bash scripts). No Linux/macOS-specific instructions or troubleshooting are provided.
Recommendations
- Clarify that Azure CLI works on Windows, Linux, and macOS, and is recommended for cross-platform use.
- Add explicit Bash or shell script examples for Linux/macOS users, especially for common tasks like environment variable setting.
- Consider moving PowerShell examples after CLI examples, or grouping them under a 'Windows' heading.
- Add troubleshooting notes for Linux/macOS users, such as file path differences or shell environment setup.
- Explicitly mention that PowerShell Core is available on Linux/macOS if relevant, or clarify when Windows-only PowerShell applies.
API Management
Deploy a Self-Hosted Gateway to Azure Container Apps - Azure API Management
...nt/how-to-deploy-self-hosted-gateway-container-apps.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, but PowerShell is consistently presented as the second tab, and there are no Linux-specific troubleshooting steps or references to Linux tools. The examples and instructions are written generically for Azure CLI, which is cross-platform, but the inclusion of PowerShell syntax and tabs may subtly signal a Windows-first approach. There are no explicit Linux/macOS limitations, but the documentation does not mention Linux-specific considerations or alternative workflows.
Recommendations
- Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows.
- Add a short note or section on Linux/macOS prerequisites (e.g., installation of Azure CLI, shell compatibility).
- Consider listing Bash examples first, or randomize tab order to avoid implicit prioritization.
- Include troubleshooting tips for common Linux/macOS issues (e.g., permissions, environment variables).
- Reference Linux-native tools or workflows where relevant.
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 exhibits mild Windows bias by referencing PowerShell in the 'Related content' section and linking to a guide for connecting virtual networks using PowerShell, a Windows-centric tool. No Linux or cross-platform CLI alternatives (such as Azure CLI or Bash) are mentioned alongside or before the PowerShell reference. However, the main body of the documentation is platform-neutral and does not provide command-line examples or instructions that would exclude Linux/macOS users.
Recommendations
- Include equivalent Azure CLI or Bash instructions and links alongside PowerShell references, especially in the 'Related content' section.
- When mentioning tools or scripts, provide both Windows (PowerShell) and cross-platform (Azure CLI, Bash) options.
- Consider listing cross-platform tools before or alongside Windows-specific ones to avoid implicit prioritization.