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 401-425 of 594 flagged pages
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/amazon-bedrock-passthrough-llm-api.md
...s/api-management/amazon-bedrock-passthrough-llm-api.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page provides instructions and code samples that are platform-neutral in most areas, but all interactive steps reference the Azure portal (web-based) and .NET/C# SDKs for API calls, which are most commonly used on Windows. There are no Linux-specific command-line examples (e.g., Bash, curl, or Python), and no mention of Linux tools or shell environments. The only SDK example is in C#, with no parity for Linux-preferred languages or tools. This may make the documentation less accessible for Linux users.
Recommendations
- Add equivalent examples using Linux-friendly tools such as curl or httpie for making API calls.
- Provide code samples in cross-platform languages commonly used on Linux, such as Python (using boto3 or requests), in addition to .NET/C#.
- Explicitly mention that the Azure portal is web-based and accessible from any OS, to clarify platform neutrality.
- If referencing SDKs, include installation and usage instructions for both Windows and Linux environments.
- Where possible, provide shell command examples (e.g., Bash scripts) for steps like storing secrets or calling APIs.
Create Pull Request
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-subscriptions.md
...rticles/api-management/api-management-subscriptions.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references Azure PowerShell and Azure SDKs as tools for automating subscription key management, but does not mention Linux-native tools or provide CLI (az CLI) examples. There are no code or command-line examples at all, but the only automation tool specifically named is Azure PowerShell, which is Windows-centric. This may give the impression that Windows tools are preferred or required, and Linux users are not directly supported.
Recommendations
- When mentioning automation tools, explicitly include cross-platform options such as Azure CLI (az), which runs natively on Linux, macOS, and Windows.
- Provide example commands for both Azure PowerShell and Azure CLI when discussing automation or scripting tasks.
- Avoid mentioning only Windows-centric tools (like PowerShell) without also referencing their Linux-friendly equivalents.
- Consider adding bash or shell script examples for common automation scenarios, or link to documentation that demonstrates Linux-compatible workflows.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-oauth2.md
...articles/api-management/api-management-howto-oauth2.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation exclusively references the Azure portal (a web-based GUI) and Microsoft Entra ID for OAuth 2.0 provider configuration, without mentioning or providing examples for command-line or cross-platform tools (such as Azure CLI, Bash scripts, or Linux-based workflows). There are no references to Linux-specific tools or environments, and all step-by-step instructions assume use of the Azure portal, which is most commonly accessed from Windows environments. No PowerShell or Windows command-line examples are present, but the lack of Linux/CLI parity is notable.
Recommendations
- Provide equivalent instructions using Azure CLI commands, which are cross-platform and can be run on Linux, macOS, and Windows.
- Include examples of registering applications and configuring OAuth 2.0 using Bash scripts or REST API calls, not just through the Azure portal.
- Mention that the Azure portal is web-based and accessible from any OS, but explicitly state that all steps can be performed from Linux or macOS as well.
- Reference or link to documentation for Linux users on installing and using Azure CLI and other relevant tools.
- If possible, add a section or callout for Linux/macOS users to clarify any OS-specific considerations or alternative workflows.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are given first and in greatest detail, with variable setup and multiple authentication scenarios. While Azure CLI (Bash) and REST examples are provided, the PowerShell (Windows) approach is consistently presented before cross-platform alternatives, and the CLI examples are less detailed. There are no explicit Linux-only or platform-specific tools, but the prominence and ordering of PowerShell content may signal a preference for Windows environments.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI (Bash) examples first to balance platform representation.
- Expand CLI (Bash) examples to include all authentication scenarios shown in PowerShell (e.g., managed identities).
- Explicitly state that both PowerShell and CLI examples are cross-platform, and clarify that Azure CLI works natively on Linux and macOS.
- Where possible, provide example scripts for both Windows (PowerShell) and Linux/macOS (Bash) in parallel, especially for variable setup and automation.
- Add a note or section highlighting platform neutrality and cross-platform support for all tools used.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/azure-openai-api-from-specification.md
.../api-management/azure-openai-api-from-specification.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes procedures using the Azure portal GUI, with no mention of command-line tools or scripts. Where command-line or automation might be relevant (e.g., downloading and editing OpenAPI specs, importing APIs), no examples are provided for either Windows (PowerShell) or Linux (bash/CLI). However, the only implicit platform-specific references are to the Azure portal, which is platform-agnostic but often more familiar to Windows users. There is no mention of Linux tools, CLI commands, or cross-platform automation, and no guidance for users who prefer or require non-GUI workflows.
Recommendations
- Add Azure CLI and/or Azure PowerShell examples for importing APIs, downloading OpenAPI specs, and configuring authentication, ensuring both Windows and Linux command-line users are supported.
- Provide bash shell script examples for Linux users where relevant (e.g., using curl or wget to download OpenAPI specs, jq for editing JSON).
- Explicitly mention that all steps can be performed on any OS via the Azure portal, but offer parity by including at least one example for both CLI and GUI workflows.
- Where screenshots or instructions reference file paths or editors, include both Windows and Linux conventions.
- Consider a section on automation or scripting for advanced users, with cross-platform examples.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/enable-cors-power-platform.md
.../articles/api-management/enable-cors-power-platform.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page focuses exclusively on using the Azure portal and Power Platform web interfaces, which are platform-agnostic, but it implicitly assumes a Windows-centric workflow by only referencing Power Platform and Azure tools, which are most commonly used in Windows environments. There are no command-line examples (such as Azure CLI or PowerShell), but also no mention of Linux-specific tools or workflows. There is a lack of parity for Linux users who may prefer or require CLI-based instructions.
Recommendations
- Add examples using Azure CLI for configuring CORS policies, which is cross-platform and widely used on Linux.
- Explicitly mention that all steps can be performed from any OS with a supported web browser, to reassure non-Windows users.
- If PowerShell or Windows-specific tools are referenced in other related articles, ensure equivalent Bash or Azure CLI examples are provided.
- Include a note or section for users who prefer automation or scripting, with links to relevant cross-platform tools.
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 page focuses on using the Azure portal and .NET for gRPC API import and consumption, with no mention of Linux-specific tools, command-line instructions, or cross-platform alternatives. The only client example references .NET, which is typically associated with Windows, and there are no examples for Linux environments or other languages. There is also an absence of CLI, PowerShell, or Bash examples, but the lack of any Linux or cross-platform guidance results in a Windows-first impression.
Recommendations
- Include examples for importing gRPC APIs using Azure CLI or Bash scripts to provide parity for Linux users.
- Add references or links to gRPC client usage in other languages (e.g., Python, Go, Java) and on Linux systems.
- Explicitly mention that the steps are platform-agnostic if that is the case, or provide separate instructions for Windows and Linux where differences exist.
- Provide guidance for managing and deploying .proto files and gRPC services from Linux environments.
- If .NET is used as an example, balance it with examples for other popular cross-platform frameworks.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/export-rest-mcp-server.md
...main/articles/api-management/export-rest-mcp-server.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently references Visual Studio Code and GitHub Copilot for testing and using MCP servers, but does not provide any examples or guidance for Linux or cross-platform command-line tools. All instructions and screenshots are based on the Azure Portal (web-based, but often associated with Windows-centric workflows) and Visual Studio Code, with no mention of Linux-native tools, shell commands, or alternative editors. There are no PowerShell-specific commands, but the absence of Linux/CLI parity and the exclusive focus on tools commonly used on Windows (and Mac, but not Linux CLI) indicate a 'windows_first' and 'missing_linux_example' bias.
Recommendations
- Provide equivalent instructions and examples for Linux users, such as using curl or httpie to test the MCP server endpoints.
- Include CLI-based examples (e.g., Azure CLI, Bash scripts) for configuring and testing MCP servers, not just portal and VS Code workflows.
- Mention and demonstrate how to use open source or cross-platform tools (e.g., Postman, curl) to interact with the MCP server.
- Clarify that Visual Studio Code is available on Linux, but also offer alternatives for users who prefer not to use VS Code.
- Add a section or callout specifically for Linux users, highlighting any differences or additional steps required.
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 or cross-platform CLI examples or tooling are provided, and the only explicit tooling example is PowerShell.
Recommendations
- Include Azure CLI examples for backend entity management, as Azure CLI is cross-platform and widely used on Linux.
- Mention and link to Azure CLI documentation alongside PowerShell and REST API references.
- If scripts or automation are discussed, provide both PowerShell and Bash (or generic shell) script examples.
- Review all tooling mentions to ensure Linux users are not excluded or required to use Windows-specific tools.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-deploy-multi-region.md
...management/api-management-howto-deploy-multi-region.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page primarily describes procedures using the Azure Portal UI and Azure CLI, with a single mention of Azure PowerShell. While the CLI examples are cross-platform, there is a subtle Windows bias in the order of tool presentation: Azure PowerShell is mentioned alongside the CLI and REST API, but no explicit Linux shell or scripting examples (e.g., Bash) are provided. There are no references to Windows-specific tools or commands, but the lack of Linux/Bash-specific guidance or parity in scripting examples may disadvantage Linux users.
Recommendations
- Provide explicit Bash shell examples for common operations, especially where Azure CLI is used, to demonstrate parity and clarify cross-platform usage.
- When listing tools for performing tasks (e.g., disabling a regional gateway), alternate the order or explicitly state that both Azure CLI and PowerShell are supported on all platforms.
- Include notes or links to documentation for running Azure CLI and PowerShell on Linux, to reinforce cross-platform support.
- If referencing PowerShell, consider also referencing Bash or other popular Linux shells to avoid the perception of Windows-first bias.
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 page focuses on using the Azure portal and .NET for gRPC API import and consumption, with no mention of Linux-specific tools, CLI commands, or cross-platform examples. The only client example references .NET, which is more commonly associated with Windows environments, and there are no Linux or open-source alternatives provided.
Recommendations
- Include examples using Azure CLI or Azure PowerShell for importing gRPC APIs, with explicit instructions for both Windows and Linux shells.
- Provide gRPC client usage examples in other languages commonly used on Linux, such as Python, Go, or Node.js.
- Mention and demonstrate the use of cross-platform tools (e.g., curl, grpcurl) for testing gRPC endpoints.
- Clarify that the steps are platform-agnostic where possible, or provide platform-specific notes if there are differences.
- Add a section or links for Linux users on how to prepare and upload .proto files, and how to interact with Azure API Management from Linux environments.
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 or instructions using cross-platform tools such as Azure CLI or Bash scripts, and no mention of Linux-specific workflows.
Recommendations
- Add step-by-step instructions for enabling DDoS Protection using Azure CLI, which is cross-platform and widely used on Linux.
- Where PowerShell-based guides are referenced, also provide links to equivalent Azure CLI documentation.
- Include Bash script examples for automation scenarios, ensuring Linux users have parity.
- Explicitly mention that all steps can be performed from any OS using the Azure CLI or REST API, and provide relevant command examples.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/quickstart-arm-template.md
...ain/articles/api-management/quickstart-arm-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page primarily demonstrates deploying an Azure API Management instance using the Azure portal, with only passing mentions of Azure PowerShell and Azure CLI as alternative methods. There are no concrete examples or instructions for using the CLI or PowerShell, and no Linux-specific guidance or screenshots. The documentation implicitly assumes use of the Azure portal (which is platform-agnostic but often associated with Windows environments) and does not provide parity for Linux users who may prefer command-line deployment.
Recommendations
- Add explicit step-by-step examples for deploying the ARM template using Azure CLI, including the exact command(s) to run. Ensure these examples are platform-neutral or specify Linux/macOS compatibility.
- Provide PowerShell deployment instructions as a separate section, clearly indicating that PowerShell is available on multiple platforms but is often used in Windows environments.
- Include sample commands for verifying and cleaning up resources using the Azure CLI, not just the portal.
- Add screenshots or terminal output examples for both CLI and PowerShell where appropriate.
- Clearly state that all deployment methods (portal, CLI, PowerShell, REST API) are supported and provide equal detail for each, or link directly to detailed guides for each method.
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, without mentioning Linux or cross-platform alternatives. There are no Linux-specific examples or CLI instructions, and the only tool explicitly named is PowerShell.
Recommendations
- Include Azure CLI examples for managing backend entities, as Azure CLI is cross-platform and widely used on Linux.
- Mention that backend management can also be performed using Azure CLI or REST API, not just PowerShell.
- If scripting examples are provided, offer both PowerShell and Bash/Azure CLI equivalents.
- Review all tool references to ensure Linux users are not excluded or made to feel like a secondary audience.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-using-with-internal-vnet.md
...-management/api-management-using-with-internal-vnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation demonstrates mild Windows bias, most notably in the DNS configuration section where the hosts file path for Windows is listed first and the reference to the hosts file uses a Windows-style environment variable (%SystemDrive%). Additionally, the only external link for creating a DNS record points to a legacy Windows Server documentation page, with no equivalent Linux guidance or links. However, Linux and macOS hosts file paths are mentioned, and no PowerShell-specific or Windows-only command-line examples are present.
Recommendations
- When referencing file paths (such as the hosts file), alternate the order or list Linux/macOS first in some instances to avoid always privileging Windows.
- Provide external documentation links for both Windows and Linux (e.g., link to official Linux documentation for editing /etc/hosts, not just Windows Server).
- Where environment variables are used (e.g., %SystemDrive%), also show the Linux equivalent or use neutral language.
- If referencing tools or procedures that are OS-specific, ensure parity by including Linux/macOS equivalents or noting differences.
- Consider adding CLI-based configuration examples (e.g., using Azure CLI or ARM templates) that are cross-platform, and avoid assuming the reader is using the Azure Portal on Windows.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are presented first and in greater detail, with variable setup and multiple authentication scenarios. Azure CLI (Bash) examples are provided, but only after PowerShell, and the documentation's structure and depth favor Windows/PowerShell workflows. There are no Linux-specific tools or patterns, but parity is mostly maintained through Azure CLI and REST examples.
Recommendations
- Present CLI (Bash) examples before or alongside PowerShell examples to avoid the impression of Windows-first workflows.
- Ensure that all authentication and configuration scenarios shown in PowerShell are equally covered in CLI/Bash examples.
- Explicitly mention Linux/macOS compatibility for CLI/Bash examples to reassure non-Windows users.
- Where possible, provide cross-platform scripting tips or highlight any differences in behavior between platforms.
- Consider including a short section on using these tools from Linux/macOS environments, especially for variable setup and authentication.
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
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a subtle Windows bias by referencing only ASP.NET Core and Visual Studio Code for creating and publishing example web APIs, both of which are traditionally associated with Windows development environments. There are no explicit Linux or cross-platform examples or mentions of Linux-specific tools or workflows. The documentation does not provide command-line or shell examples (e.g., Bash, CLI), nor does it mention Linux distributions or tools, focusing instead on GUI-based workflows that are more familiar to Windows users.
Recommendations
- Add explicit examples and links for creating and publishing web APIs using Linux-based tools and environments, such as using the Azure CLI or deploying from a Linux terminal.
- Include references to cross-platform frameworks and editors (e.g., Node.js, Python Flask, Java Spring Boot) and show how to publish these to Azure App Service from Linux.
- Provide step-by-step instructions or links for deploying APIs from Linux and macOS, not just Windows-centric tools like Visual Studio Code.
- Mention that Visual Studio Code is cross-platform, and provide Linux/macOS installation instructions or alternatives.
- Where possible, include screenshots or terminal commands from Linux environments to demonstrate parity.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/quickstart-arm-template.md
...ain/articles/api-management/quickstart-arm-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page primarily describes using the Azure Portal for deployment, but when mentioning command-line alternatives, it lists Azure PowerShell before Azure CLI and does not provide any explicit Linux or cross-platform command-line examples. There are no bash or Linux-specific instructions, and the only command-line tools mentioned are Azure PowerShell and Azure CLI, with PowerShell listed first. No Linux tools or screenshots are provided.
Recommendations
- When listing command-line deployment options, mention Azure CLI before or alongside Azure PowerShell, as Azure CLI is cross-platform and widely used on Linux.
- Provide explicit examples for deploying the ARM template using Azure CLI (bash) and, if possible, PowerShell, to ensure parity.
- Include screenshots or terminal snippets that demonstrate Linux or cross-platform usage, not just Azure Portal UI.
- Add a section or callout highlighting that Azure CLI works on Linux, macOS, and Windows, and provide installation links for each.
- Ensure that any referenced documentation (such as 'Deploy templates') includes Linux/bash examples, or link directly to sections that do.
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 providing a link to a PowerShell-based guide for enabling DDoS IP Protection. There are no CLI or Linux-native command examples (such as Azure CLI or Bash scripts), and the only automation example referenced is PowerShell, which is primarily associated with Windows environments.
Recommendations
- Provide equivalent 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.
- Include Bash script examples where automation is discussed, to ensure Linux users have parity.
- When linking to automation guides, offer both PowerShell and Azure CLI documentation links.
- Explicitly mention that the Azure Portal is accessible from any OS, but supplement with command-line instructions for users who prefer or require non-GUI workflows.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation demonstrates a moderate Windows bias by prioritizing PowerShell examples and instructions before CLI (Bash) and REST alternatives. PowerShell is a Windows-centric tool, and its prominence may disadvantage Linux or cross-platform users. However, the inclusion of Azure CLI (Bash) and REST API examples does provide Linux parity, though these are consistently presented after PowerShell, reinforcing a 'Windows-first' pattern.
Recommendations
- Present Azure CLI (Bash) examples before or alongside PowerShell examples to better serve Linux and cross-platform users.
- Explicitly state that Azure CLI commands are cross-platform and can be used on Windows, Linux, and macOS.
- Where possible, provide examples in a neutral scripting language (such as Bash or Python) or clarify that PowerShell Core is available cross-platform.
- Review and balance the order of example tabs so that no single OS is consistently prioritized.
- Add a brief section or note highlighting tool availability and parity across platforms.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-deploy-multi-region.md
...management/api-management-howto-deploy-multi-region.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by exclusively providing Azure CLI and Azure PowerShell examples for managing API Management regional gateways, with explicit mention of the Azure PowerShell cmdlet (set-azapimanagement) and no mention of Linux-specific tools or shell environments. While the Azure CLI is cross-platform, the absence of any Linux shell (bash) or scripting examples, and the ordering of PowerShell before CLI in the list of tools, subtly prioritizes Windows-centric tooling and usage patterns.
Recommendations
- Include explicit bash/Linux shell examples alongside Azure CLI commands, demonstrating usage in a Linux environment.
- When listing management tools, mention cross-platform tools (Azure CLI, REST API) before Windows-specific tools (Azure PowerShell).
- If referencing PowerShell, clarify that Azure CLI is fully supported on Linux/macOS and provide equivalent bash scripting examples where appropriate.
- Add a note or section highlighting that all Azure CLI commands work identically on Linux, macOS, and Windows, and provide example shell commands for common Linux environments.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-using-with-internal-vnet.md
...-management/api-management-using-with-internal-vnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally maintains cross-platform neutrality, but in the section on editing the hosts file for DNS testing, the Windows path (%SystemDrive%\drivers\etc\hosts) is listed before the Linux/macOS path (/etc/hosts). Additionally, a related content link points to a Windows 2000 Server DNS article, which is outdated and Windows-specific. No PowerShell-heavy or Windows-only command examples are present, but subtle prioritization of Windows paths and tools is evident.
Recommendations
- List Linux/macOS and Windows hosts file paths in parallel or in alphabetical order, or provide separate instructions for each platform to avoid implicit prioritization.
- Replace or supplement the 'Creating a record in DNS' related link with a modern, cross-platform or Azure-native DNS documentation link.
- Where platform-specific paths or tools are mentioned, ensure equal prominence and detail for Linux/macOS equivalents.
- Consider including example commands or screenshots for both Windows and Linux environments where relevant (e.g., editing hosts file, DNS setup).
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/developer-portal-self-host.md
.../articles/api-management/developer-portal-self-host.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally uses cross-platform tools (Git, Node.js, Azure CLI) and avoids OS-specific commands. However, in Step 6, it explicitly instructs users to 'Open Windows Command Prompt, PowerShell, or other command shell,' listing Windows shells first and not mentioning Linux or macOS shells by name. No Linux- or macOS-specific examples or shell references are provided, which may give the impression of a Windows-first or Windows-preferred workflow.
Recommendations
- In Step 6, explicitly mention Linux and macOS terminals alongside Windows Command Prompt and PowerShell (e.g., 'Open your terminal (Windows Command Prompt, PowerShell, Linux shell, or macOS Terminal)').
- Wherever shell commands are shown, clarify that they work on all platforms unless otherwise noted.
- If any step has platform-specific nuances (such as path separators or environment variable syntax), provide examples for both Windows and Linux/macOS.
- Consider adding a short note in the prerequisites or introduction stating that the instructions are cross-platform and tested on Windows, Linux, and macOS.
- If screenshots or UI instructions are given for Azure CLI or other tools, include Linux/macOS terminal screenshots where appropriate.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/devops-api-development-templates.md
...les/api-management/devops-api-development-templates.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation focuses exclusively on Azure-native and cross-platform tools but does not provide any OS-specific examples. However, it implicitly exhibits a 'windows_first' bias by only mentioning Microsoft-centric tools (Azure Pipelines, Visual Studio Code, dotnet-apim) and omits explicit Linux or non-Microsoft CI/CD tools and workflows. There are no CLI or shell command examples, but the absence of Linux-specific tools, editors, or pipelines (e.g., GitLab CI, Jenkins, or Linux shell usage) and the exclusive mention of Visual Studio Code and .NET tools suggest a lack of Linux parity.
Recommendations
- Include examples of using popular Linux-based CI/CD tools such as Jenkins, GitLab CI, or Travis CI for API deployment.
- Mention and provide examples of using Linux-native editors (e.g., Vim, Emacs, or JetBrains IDEs) for API definition editing.
- Provide CLI examples using bash or shell scripts for deploying APIs, in addition to or instead of Azure Pipelines or GitHub Actions.
- Reference cross-platform or Linux-preferred tools for API linting, testing, and deployment where possible.
- Explicitly state the cross-platform compatibility of the mentioned tools, and provide guidance for Linux users where workflows may differ.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/export-rest-mcp-server.md
...main/articles/api-management/export-rest-mcp-server.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently references Visual Studio Code and GitHub Copilot for testing and using the MCP server, but does not provide any Linux-specific instructions, CLI examples, or mention of alternative editors or tools commonly used on Linux. All configuration and usage steps are described in the context of the Azure Portal (web-based) and Visual Studio Code, which, while cross-platform, is often associated with Windows workflows. There are no explicit Linux shell, terminal, or non-GUI instructions, nor any mention of Linux-specific considerations.
Recommendations
- Add explicit instructions or notes confirming that all steps (including Visual Studio Code and GitHub Copilot usage) are fully supported on Linux, and mention any Linux-specific prerequisites if applicable.
- Provide alternative examples using command-line tools (such as curl, httpie, or az CLI) for testing the MCP server, which are commonly used on Linux.
- Include a section or callout for Linux users, highlighting any differences or confirming parity in experience.
- Mention and, if possible, provide examples for other editors or tools popular on Linux (such as Vim, Emacs, or JetBrains IDEs) for interacting with the MCP server.
- Ensure that screenshots and file path examples are not Windows-specific (e.g., avoid backslashes or Windows-style paths).