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 126-150 of 594 flagged pages
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-mutual-certificates.md
...management/api-management-howto-mutual-certificates.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by providing only PowerShell examples for command-line operations, specifically for disabling certificate chain validation. There are no equivalent examples for Linux environments (e.g., Bash, Azure CLI), and the use of PowerShell cmdlets assumes a Windows-centric workflow. No Linux-native tools or cross-platform command-line instructions are mentioned.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell cmdlets shown, especially for tasks like disabling certificate chain validation.
- Include Bash shell examples where appropriate, or clarify if the steps are platform-agnostic.
- Explicitly mention cross-platform compatibility for all command-line instructions, and note any OS-specific requirements.
- Reference Linux tools or workflows (e.g., OpenSSL for certificate management) alongside Windows tools.
- Add a section or callout for Linux/macOS users, outlining any differences or additional steps required.
Create Pull Request
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
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Microsoft Entra ID (formerly Azure AD) and the Azure portal, which are Windows-centric tools. All configuration steps reference the Azure portal UI and Microsoft-specific workflows, with no mention of Linux command-line alternatives (such as Azure CLI, REST API, or Terraform). There are no examples or instructions for performing equivalent tasks on Linux or via cross-platform tools, and no mention of open-source OAuth providers or non-Microsoft environments.
Recommendations
- Include Azure CLI and REST API examples for all configuration steps, as these are cross-platform and commonly used on Linux.
- Reference open-source OAuth 2.0 providers (e.g., Keycloak, Auth0, Okta) and provide example configuration steps for at least one non-Microsoft provider.
- Add instructions for configuring OAuth 2.0 in API Management using infrastructure-as-code tools (e.g., Terraform, Bicep), which are platform-agnostic.
- Explicitly state that the Azure portal is web-based and accessible from any OS, but offer alternatives for users who prefer command-line or automated workflows.
- Provide troubleshooting steps or notes for Linux users, such as environment variable handling, file paths, or authentication methods that differ from Windows.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-use-managed-service-identity.md
...t/api-management-howto-use-managed-service-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell CLI examples for command-line operations, with no mention or examples of cross-platform tools such as Azure CLI (az), Bash, or scripting on Linux/macOS. The PowerShell approach is presented as the default and only command-line method, and installation instructions reference Windows-centric tools. There are no Linux or macOS-specific instructions or parity examples, and no mention of Bash, shell, or cross-platform scripting alternatives.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell snippets, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash/shell script examples where appropriate, especially for ARM template deployments.
- Explicitly mention that Azure CLI and PowerShell are both supported, and clarify when a step is platform-agnostic.
- Provide installation instructions or links for Azure CLI on Linux and macOS, not just PowerShell.
- Reorder sections or provide parallel examples so that Linux/macOS users do not feel secondary to Windows users.
- Where screenshots or UI steps are shown, note any platform differences or limitations.
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
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page generally maintains platform neutrality, but in the section on editing the hosts file for DNS testing, the Windows file path (%SystemDrive%\drivers\etc\hosts) is mentioned before the Linux/macOS equivalent (/etc/hosts). Additionally, the only external link for 'Creating a record in DNS' points to a legacy Windows Server article, with no Linux or cross-platform DNS guidance provided. There are no command-line examples (PowerShell, Bash, etc.), but the DNS and hosts file examples are Windows-centric.
Recommendations
- List Linux/macOS hosts file path before or alongside the Windows path, or present both together in a neutral way.
- Provide links to cross-platform or Linux DNS configuration documentation (e.g., BIND, dnsmasq, or Azure DNS CLI/Bash guides) in addition to or instead of Windows-only resources.
- Where external documentation is referenced, ensure parity by including Linux and macOS equivalents, not just Windows Server.
- If providing file paths or instructions, use a table or bullet points to show all major OSes equally.
- Consider adding CLI or script examples (e.g., Azure CLI, Bash) for common tasks to further improve cross-platform usability.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/developer-portal-basic-authentication.md
...pi-management/developer-portal-basic-authentication.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively mentioning the Azure PowerShell cmdlet (New-AzApiManagementUser) as the CLI tool for adding users, without referencing equivalent Azure CLI commands or REST API methods that are platform-agnostic. There are no Linux-specific examples or instructions, and the only automation example provided is PowerShell-based, which is most commonly used on Windows.
Recommendations
- Include Azure CLI examples for adding users to the developer portal, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Reference REST API methods for user management, providing curl or httpie examples that work on any OS.
- Clearly indicate that PowerShell is available on Linux and macOS, but provide parity by listing Azure CLI and REST API options first or alongside PowerShell.
- Add a note or section highlighting cross-platform tooling for managing API Management users, ensuring Linux users are not excluded.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/developer-portal-faq.md
...b/main/articles/api-management/developer-portal-faq.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through the exclusive use of PowerShell scripts for role assignment and management tasks, and references to Windows batch scripts (.bat) for cleanup operations. There are no equivalent examples or instructions for Linux/macOS users, such as Bash scripts or Azure CLI commands. Windows tools and patterns (PowerShell, .bat files) are mentioned exclusively and before any cross-platform alternatives, which may hinder Linux user experience.
Recommendations
- Provide equivalent Azure CLI or Bash script examples for role assignment and management tasks alongside PowerShell scripts.
- Include instructions for running cleanup operations using Bash (.sh) scripts for Linux/macOS environments.
- Clearly indicate cross-platform compatibility for all scripts and commands, and specify any OS-specific requirements.
- Where possible, use platform-agnostic tools (e.g., Azure CLI) in examples before or alongside Windows-specific tools.
- Add notes or sections specifically addressing Linux/macOS workflows for common administrative tasks.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/graphql-api.md
...-docs/blob/main/articles/api-management/graphql-api.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, with the PowerShell section being Windows-centric. The prerequisites mention Azure CLI and Azure PowerShell, but there is no explicit mention of Linux or Bash-specific guidance, nor are there examples tailored for Linux environments. The PowerShell example assumes a Windows environment, and no alternative is provided for Linux users who may not have access to PowerShell or prefer Bash scripting.
Recommendations
- Explicitly state that Azure CLI commands work cross-platform (Windows, Linux, macOS), and provide Bash-specific variable syntax if needed.
- Add a Bash shell example alongside the PowerShell example, or clarify that the Azure CLI example is intended for Bash/Unix shells.
- Mention installation and usage of Azure CLI and PowerShell on Linux, including links to relevant setup guides.
- Avoid assuming PowerShell is the default scripting environment; clarify when examples are Windows-specific.
- If PowerShell Core (cross-platform) is supported, note this and provide Linux/macOS usage notes.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/quickstart-terraform.md
...b/main/articles/api-management/quickstart-terraform.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but does not offer explicit Linux/macOS shell examples or mention Bash or other Linux-native tools. The PowerShell section uses Windows-style variable assignment, and the prerequisites list Azure PowerShell requirements alongside Azure CLI, which may not be as relevant for Linux users. There are no explicit Linux-specific instructions or parity in tool recommendations.
Recommendations
- Add explicit Bash/Linux shell examples for variable assignment and command usage, especially in the verification steps.
- Clarify that Azure CLI is cross-platform and can be used on Linux/macOS, and provide examples using Bash syntax.
- Reorder or balance the presentation of Azure CLI and PowerShell, or add a Bash tab to ensure Linux users see their platform represented.
- In the prerequisites, clarify that Azure PowerShell is optional and not required for Linux users if they use Azure CLI.
- Where file creation or directory navigation is mentioned, provide both Windows (cmd/PowerShell) and Linux (Bash) command examples.
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
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by only referencing Windows-centric tools and workflows (such as the Azure portal and Visual Studio Code), omitting Linux-specific instructions or alternatives. There are no command-line examples for Linux (e.g., Bash, curl), and the only development tool mentioned is Visual Studio Code, which, while cross-platform, is often associated with Windows in Microsoft documentation. No mention is made of Linux-native tools or how to perform tasks outside the Azure portal.
Recommendations
- Include command-line examples using Bash and curl for interacting with the MCP server endpoint, in addition to or instead of portal-only instructions.
- Explicitly mention that Visual Studio Code is available on Linux and provide setup instructions for Linux users.
- Provide alternative instructions for testing the MCP server using Linux-native tools (e.g., httpie, curl, or Postman on Linux).
- Add screenshots or walkthroughs using a Linux environment where relevant.
- Ensure parity in tool recommendations by listing both Windows and Linux options for each step, especially for testing and development.
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
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing Visual Studio Code (a Microsoft product, though cross-platform) and GitHub Copilot as the only suggested tools for testing the MCP server, without mentioning Linux-native alternatives or command-line approaches. All instructions are oriented around the Azure Portal GUI, which is platform-agnostic, but there is no mention of Linux-specific workflows, CLI tools, or examples. The documentation implicitly assumes a Windows-centric development environment by not providing parity for Linux users.
Recommendations
- Provide examples of testing the MCP server using cross-platform command-line tools such as curl or httpie, which are commonly used on Linux.
- Mention and demonstrate the use of Azure CLI or REST API calls for managing and testing MCP servers, ensuring instructions are not limited to GUI-based workflows.
- List alternative editors and tools for Linux users (e.g., Vim, Emacs, or JetBrains IDEs) when suggesting Visual Studio Code.
- Explicitly state that the instructions are platform-agnostic or provide separate sections for Windows and Linux where workflows differ.
- Include screenshots or terminal examples from Linux environments where relevant.
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
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio Code (a Microsoft product) and GitHub Copilot for testing, without mentioning Linux-native alternatives or command-line tools. All instructions assume use of the Azure portal, which is browser-based and cross-platform, but there are no examples or guidance for Linux users (e.g., using curl, httpie, or other CLI tools). The documentation does not provide parity for Linux environments or mention Linux-specific workflows.
Recommendations
- Include examples of testing the MCP server using Linux command-line tools such as curl or httpie.
- Mention that Visual Studio Code and GitHub Copilot are available on Linux, or suggest alternative editors and tools commonly used in Linux environments.
- Provide step-by-step instructions for testing the MCP server from a Linux shell, including sample requests.
- Ensure that any screenshots or instructions do not assume a Windows-only environment.
- Explicitly state cross-platform compatibility where relevant, and avoid implying Windows as the default platform.
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
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page primarily describes deploying an Azure API Management instance via the Azure portal and mentions Azure PowerShell, Azure CLI, and REST API as alternative deployment methods. However, the only explicit command-line tool mentioned first is Azure PowerShell, which is Windows-centric, and there are no concrete CLI or Linux-specific examples provided. The documentation does not provide parity in examples or instructions for Linux users, nor does it highlight cross-platform tools or workflows equally.
Recommendations
- Provide explicit Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
- When listing alternative deployment methods, mention Azure CLI before or alongside PowerShell to avoid a Windows-first impression.
- Include screenshots or terminal snippets from Linux environments where appropriate, not just the Azure portal UI.
- Clarify that all command-line instructions are cross-platform unless otherwise noted, and provide any OS-specific caveats.
- Consider a dedicated section or callout for Linux/macOS users to ensure their workflows are equally represented.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/virtual-network-injection-resources.md
.../api-management/virtual-network-injection-resources.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily through the exclusive mention of PowerShell in related content and the absence of Linux/CLI examples or references. The only explicit example of connecting virtual networks refers to PowerShell, with no equivalent Azure CLI or Linux-native tooling mentioned. There are no Bash, Linux, or cross-platform command-line instructions or references, and the documentation does not acknowledge Linux or cross-platform users in its guidance or examples.
Recommendations
- Add equivalent Azure CLI examples and references alongside or before PowerShell examples, especially in the 'Related content' section.
- Include links to documentation for connecting virtual networks using Azure CLI and/or ARM templates, not just PowerShell.
- Wherever PowerShell is mentioned, clarify that Azure CLI and ARM templates are also supported and provide links or examples.
- Review the documentation for other subtle Windows-centric terminology or assumptions, and ensure parity for Linux and cross-platform users.
- Consider adding a section or note explicitly stating that all operations can be performed from any OS using Azure CLI or the Azure Portal, not just from Windows/PowerShell.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/virtual-network-reference.md
...n/articles/api-management/virtual-network-reference.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page is largely platform-neutral, focusing on Azure networking concepts and requirements. However, there are several instances where Windows-specific tools, services, or endpoints are referenced without equivalent Linux mentions. Notably, the KMS endpoint section is exclusively about Windows VM activation, and the internal infrastructure section lists endpoints for Windows Update and Windows Defender without Linux equivalents or clarifications. Additionally, a referenced link for connecting VNets uses 'powershell' in its filename, suggesting a Windows-centric example. There are no explicit Linux or cross-platform command examples provided.
Recommendations
- When mentioning Windows-specific requirements (e.g., KMS, Windows Update, Windows Defender), clarify whether there are any equivalent requirements or considerations for Linux VMs, or explicitly state that these are not applicable to Linux.
- If providing links or examples for VNet connectivity or configuration, include both PowerShell (Windows) and Azure CLI/Bash (cross-platform/Linux) options, or link to documentation that covers both.
- Add a section or notes on Linux VM considerations for API Management in VNets, if any, to ensure parity and clarity for non-Windows users.
- Where possible, avoid implying that Windows is the default or only supported platform by using neutral language and providing cross-platform guidance.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-log-event-hubs.md
.../api-management/api-management-howto-log-event-hubs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page provides code examples for configuring loggers using Azure PowerShell, Bicep, ARM templates, and REST API, but only the PowerShell example is given for command-line/scripted creation of loggers. There are no CLI (az cli), Bash, or Linux-native examples. The only imperative scripting example is PowerShell, which is primarily a Windows tool, and there is no mention of cross-platform alternatives such as Azure CLI or Bash scripts. This may make it less accessible for Linux or macOS users.
Recommendations
- Add Azure CLI (az cli) examples for creating and managing loggers, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash script examples where appropriate, especially for tasks that can be automated via the command line.
- When referencing scripting tools, mention cross-platform options (e.g., 'You can use Azure PowerShell or Azure CLI...') and provide parity in examples.
- Explicitly state that PowerShell Core is available cross-platform if PowerShell examples are retained, or clarify which examples are Windows-only.
- Consider the order of examples: present cross-platform tools (like Azure CLI) before or alongside Windows-centric tools (like PowerShell).
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-ca-certificates.md
...api-management/api-management-howto-ca-certificates.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides a PowerShell command (`New-AzApiManagementSystemCertificate`) as the only CLI example for uploading a CA certificate, with no mention of equivalent Azure CLI, Bash, or Linux-native tooling. The only command-line example is Windows-centric, and there is no guidance for Linux or cross-platform users.
Recommendations
- Add Azure CLI examples for uploading and managing CA certificates, as Azure CLI is cross-platform and widely used on Linux.
- If PowerShell is mentioned, also provide Bash or shell script equivalents for Linux users.
- Explicitly state whether the process can be performed from Linux/macOS, and provide any relevant platform-specific notes.
- Reference or link to documentation on using REST APIs with curl or other Linux-native tools for certificate management.
- Ensure that screenshots and instructions do not assume a Windows environment unless unavoidable.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-configuration-repository-git.md
...agement/api-management-configuration-repository-git.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (Git Bash from Git for Windows, Visual Studio Immediate Window) and providing troubleshooting steps that assume access to Visual Studio, a Windows-centric IDE. There are no Linux or macOS-specific instructions or examples for cloning the repository, handling credentials, or URL encoding passwords. The order of tool mentions and examples also places Windows tools and workflows first, with no parity for Linux users.
Recommendations
- Provide explicit Linux and macOS examples for cloning the repository, including credential handling and URL encoding (e.g., using `python3 -c 'import urllib.parse; print(urllib.parse.quote("password"))'` or `printf %s "password" | jq -sRr @uri`).
- Mention cross-platform Git tools (e.g., native Git on Linux/macOS, or terminal usage) alongside or before Windows-specific ones.
- Replace or supplement Visual Studio Immediate Window instructions with cross-platform alternatives for URL encoding passwords.
- Add a note clarifying that all Git operations can be performed on Linux/macOS as well as Windows, and provide any OS-specific caveats if needed.
- Ensure that references to Azure CLI and PowerShell are balanced, and provide example commands for both where relevant.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/automation-manage-api-management.md
...les/api-management/automation-manage-api-management.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively references Windows PowerShell cmdlets and scripts for managing Azure API Management via Azure Automation. There are no examples or mentions of Linux-compatible tools (such as Azure CLI, Bash, or Python), nor are cross-platform scripting options discussed. The guidance assumes a Windows/PowerShell environment, which may exclude or disadvantage Linux users.
Recommendations
- Provide equivalent examples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
- Include Bash or Python script samples for common automation tasks.
- Mention that Azure Automation supports Python runbooks and provide links or examples.
- Rephrase sections to refer to 'PowerShell or other supported scripting languages' rather than only PowerShell.
- Ensure that links and samples are balanced, offering both Windows/PowerShell and Linux-friendly options.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-integrate-internal-vnet-appgateway.md
...pi-management-howto-integrate-internal-vnet-appgateway.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exclusively uses Azure PowerShell for all setup, configuration, and management steps, with all code samples and variable paths (e.g., certificate paths) reflecting Windows conventions. There are no examples or guidance for performing the same tasks using cross-platform tools such as Azure CLI, Bicep, or ARM templates, nor are there any Linux/macOS-specific instructions or file path conventions. This creates a strong Windows and PowerShell bias, making it less accessible for users on Linux or macOS systems.
Recommendations
- Provide equivalent Azure CLI examples for all major steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include notes or examples for Linux/macOS users, especially regarding file paths (e.g., use /home/contoso/ instead of C:\Users\Contoso\).
- Reference and link to ARM/Bicep template-based deployments for users who prefer declarative infrastructure-as-code approaches.
- Explicitly state that all steps can be performed on Linux/macOS with Azure CLI, and highlight any differences or prerequisites.
- Where PowerShell is required, clarify if Azure PowerShell Core (cross-platform) is supported, and provide installation instructions for non-Windows systems.
- Add a section or callout summarizing cross-platform options for managing Azure resources, with links to relevant documentation.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-mutual-certificates.md
...management/api-management-howto-mutual-certificates.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell cmdlet examples (e.g., New-AzApiManagementBackend), with no equivalent CLI or scripting examples for Linux environments. There is no mention of cross-platform tools such as Azure CLI or Bash scripts, and the only automation guidance is via PowerShell, which is primarily a Windows tool. This could hinder Linux or macOS users seeking parity.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlet instructions, especially for tasks like disabling certificate chain validation.
- Include Bash script snippets or REST API curl examples to demonstrate cross-platform automation.
- Explicitly mention that PowerShell Core is available cross-platform, or provide links to documentation for using PowerShell on Linux/macOS if PowerShell must be used.
- Ensure that references to automation tools (e.g., 'You can also disable certificate chain validation by using the Backend REST API') are accompanied by concrete, cross-platform code samples.
- Review all sections for implicit assumptions of a Windows environment and add clarifying notes or alternatives where needed.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-revisions.md
...in/articles/api-management/api-management-revisions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell cmdlets (e.g., New-AzApiManagementApiRelease, Update-AzApiManagementApiRelease) for command-line operations, without mentioning or providing examples for Linux-friendly alternatives such as Azure CLI or REST API. No Linux shell or cross-platform command-line examples are given, and the only automation tooling mentioned is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Add equivalent Azure CLI commands for all PowerShell cmdlet examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include REST API examples for operations such as setting a revision as current or updating the change log, to provide a platform-neutral automation option.
- When referencing command-line tools, mention Azure CLI before or alongside PowerShell to avoid implying Windows is the primary or only supported environment.
- Explicitly state that all operations can be performed from any OS using the Azure portal, Azure CLI, or REST API, and provide links or examples for each.
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
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell as a primary management tool alongside Azure CLI, and by not providing any Linux- or cross-platform-specific examples or guidance. The mention of Azure PowerShell before Azure CLI and the absence of explicit Linux command-line or automation examples suggest a preference for Windows-centric tools and workflows.
Recommendations
- Ensure that Azure CLI (which is cross-platform) is mentioned before or alongside Azure PowerShell in all tool lists and instructions.
- Provide explicit Linux shell (bash) examples for API management tasks, especially where PowerShell is referenced.
- Include notes or sections clarifying that all management operations can be performed from Linux, macOS, and Windows, and link to relevant cross-platform documentation.
- Where screenshots or UI elements are shown, ensure they are not Windows-specific, or provide Linux/macOS equivalents if relevant.
- Audit related documentation for similar patterns and update to maintain parity between Windows and Linux user experiences.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/applications.md
...docs/blob/main/articles/api-management/applications.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell scripts for generating OAuth tokens and calling APIs, with no equivalent examples for Linux or cross-platform tools such as curl or Bash. The only command-line automation shown is via PowerShell, and there are no references to Linux-native tools or instructions for non-Windows environments. The use of the Azure portal is platform-agnostic, but all scripting and automation guidance assumes a Windows/PowerShell context.
Recommendations
- Provide equivalent examples using curl and Bash for generating tokens and calling APIs, which are native to Linux and cross-platform environments.
- Explicitly mention that the API calls can be performed from any OS, and provide sample commands for both Windows (PowerShell) and Linux/macOS (Bash/curl).
- Add a note or section on how to install and use Azure CLI (which is cross-platform) for relevant operations, if applicable.
- Ensure troubleshooting and automation guidance includes steps or scripts that are not limited to Windows or PowerShell users.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/breaking-changes/api-version-retirement-sep-2023.md
...nt/breaking-changes/api-version-retirement-sep-2023.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation gives both Azure CLI and Azure PowerShell instructions for checking and updating tool versions, but the PowerShell example is presented alongside the CLI without explicit Linux/bash alternatives. PowerShell is a Windows-centric tool, and its mention without equivalent bash or shell commands may disadvantage Linux users. Additionally, the documentation references the Azure portal (a web UI) and REST API, but does not provide explicit Linux shell or bash script examples, nor does it clarify cross-platform usage for the CLI commands. The focus on PowerShell and lack of explicit Linux-native instructions indicate a mild Windows bias.
Recommendations
- For every PowerShell example, provide an equivalent bash or shell command for Linux/macOS users.
- Clarify that Azure CLI commands are cross-platform and can be run in bash, zsh, or other shells, not just Windows Command Prompt or PowerShell.
- Explicitly mention that Azure CLI is available on Linux, macOS, and Windows, and provide installation/update links for all platforms.
- Where possible, provide sample scripts or commands in both PowerShell and bash to ensure parity.
- Add a note or section addressing Linux/macOS users, highlighting any differences or considerations.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/developer-portal-alternative-processes-self-host.md
...nt/developer-portal-alternative-processes-self-host.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows/Azure-centric bias by exclusively referencing Azure tools and services (such as Azure CLI, Azure Function App, Azure CDN) without mentioning or providing examples for equivalent Linux or cross-platform alternatives. There are no Linux-specific instructions, and the use of Azure CLI and Azure Functions Core Tools assumes a Windows/Azure environment. No mention is made of non-Azure hosting, deployment, or CDN options, nor are there examples for Linux-native workflows.
Recommendations
- Include explicit instructions and examples for Linux environments, such as using bash scripts, Linux-native CLI tools, and deployment to non-Azure hosts.
- Mention and provide examples for alternative hosting and CDN solutions (e.g., AWS S3, Google Cloud Storage, Cloudflare CDN, Nginx, Apache) alongside Azure-specific options.
- Clarify that Azure CLI and Azure Functions Core Tools are cross-platform, and provide installation instructions for Linux and macOS.
- Add a section or notes highlighting how to adapt the workflow for Linux users, including common pitfalls and environment-specific considerations.
- Balance the order of presentation so that Azure/Windows tools are not always mentioned first, or group alternatives together to avoid implicit prioritization.