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 376-400 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 provides only .NET (C#) code samples and references the Azure portal GUI, both of which are more commonly associated with Windows environments. There are no Linux-specific or cross-platform CLI examples (such as Bash, curl, or Python), nor is there mention of Linux tools or workflows. The documentation implicitly assumes a Windows/.NET development environment, which may disadvantage Linux users.
Recommendations
- Add equivalent code samples using cross-platform languages such as Python (e.g., using boto3 and requests) to demonstrate calling the Bedrock API through API Management from Linux or macOS.
- Include command-line examples using curl or HTTPie for invoking the API endpoint, which are standard on Linux systems.
- Mention and provide examples for using the Azure CLI (az) for relevant configuration steps, as it is cross-platform.
- Clarify that the .NET example is cross-platform, but explicitly state and show how to run it on Linux (e.g., using .NET Core on Ubuntu).
- Where possible, avoid implying that the Azure portal is the only way to perform configuration; provide CLI or ARM template alternatives.
Create Pull Request
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 provided first and in greater detail, with variable setup and multiple access scenarios. Azure CLI (Bash) and REST examples are present, but PowerShell is prioritized and more thoroughly explained. There are no explicit Linux-specific tools or shell examples beyond Azure CLI, and no mention of Linux-native scripting or automation approaches. The documentation assumes familiarity with PowerShell, which is traditionally a Windows-centric tool, despite its cross-platform availability.
Recommendations
- Present Azure CLI (Bash) examples before or alongside PowerShell examples to avoid implying PowerShell is the primary or preferred approach.
- Expand Azure CLI sections to match the detail and coverage of PowerShell sections, including variable setup and all access scenarios.
- Explicitly mention that PowerShell and Azure CLI are both cross-platform, and clarify that all examples work on Linux, macOS, and Windows.
- Where possible, add Linux-native automation examples (e.g., Bash scripts, cron usage) or reference Linux shell scripting in the context of automation.
- Review language to ensure it does not assume a Windows environment or familiarity with Windows-specific tools.
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 page references Azure PowerShell and Azure SDKs as tools for automating subscription key management, but does not mention Linux-native tools, Bash, or CLI alternatives. No command-line examples are provided, but the only automation tool specifically named is Azure PowerShell, which is primarily associated with Windows environments. There are no Linux-specific or cross-platform examples or tool mentions.
Recommendations
- When suggesting automation tools, mention cross-platform options such as Azure CLI (az), Bash scripts, or REST API calls alongside Azure PowerShell.
- Provide example commands for both Azure PowerShell and Azure CLI to demonstrate parity.
- Explicitly state that Azure CLI and REST API approaches are fully supported on Linux, macOS, and Windows.
- Avoid implying that PowerShell is the default or only automation tool; present it as one of several options.
- Consider including a table or section comparing how to perform key management tasks using PowerShell, Azure CLI, and REST API.
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 demonstrates a bias towards Windows by only referencing the Azure portal (which is web-based and cross-platform, but often associated with Windows workflows) and .NET for gRPC client/server examples, without providing equivalent Linux or cross-platform command-line examples (e.g., using grpcurl, curl, or other open-source tools). There are no Linux-specific instructions or examples, and the only programming language ecosystem referenced is .NET, which is historically Windows-centric.
Recommendations
- Add examples for calling gRPC services using cross-platform tools such as grpcurl or Postman, including command-line instructions that work on Linux.
- Include references or links to gRPC client/server tutorials in other languages (e.g., Python, Go, Java) that are commonly used on Linux.
- Explicitly mention that the Azure portal is accessible from any OS, and consider providing Azure CLI or ARM/Bicep deployment examples from a Linux shell.
- Balance .NET examples with equivalent Linux-friendly or open-source alternatives to ensure parity for non-Windows users.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/private-endpoint.md
.../blob/main/articles/api-management/private-endpoint.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation primarily uses Azure Portal and Azure CLI examples, which are cross-platform, but there is a subtle Windows bias in the 'Test in virtual network' section where only nslookup is shown as the DNS utility example (nslookup is more commonly associated with Windows, though available on Linux). There are no PowerShell-specific or Windows-only tool examples, but Linux/Unix alternatives (like dig) are only mentioned in passing and not shown in example commands. The documentation does not provide explicit Linux shell or scripting examples, nor does it mention Linux-specific tools or workflows.
Recommendations
- When suggesting DNS utilities, provide both Windows (nslookup) and Linux (dig) command examples side by side.
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS, and provide example shell prompts for both (e.g., Bash and PowerShell).
- Where possible, include Linux/Unix command-line examples (e.g., curl, dig) alongside any Windows-centric examples.
- If referencing the Azure Portal, clarify that it is web-based and platform-agnostic.
- Add a note or section for common troubleshooting or validation steps using Linux tools and shell environments.
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 deploying an Azure API Management instance using the Azure portal, with only brief mentions of Azure PowerShell and Azure CLI as alternative methods. There are no explicit examples or instructions for using Azure CLI (which is cross-platform and commonly used on Linux/macOS), nor are there any Linux-specific tools or terminal instructions. The mention of Azure PowerShell (traditionally Windows-centric) appears before Azure CLI, and no Linux shell or bash examples are provided.
Recommendations
- Add explicit, step-by-step instructions and code examples for deploying the ARM template using Azure CLI (az deployment), including sample commands.
- Ensure that Azure CLI instructions are presented before or alongside Azure PowerShell, as CLI is cross-platform and widely used on Linux.
- Include bash shell examples for common tasks such as resource cleanup, in addition to portal-based instructions.
- Clarify that all command-line methods work on Linux, macOS, and Windows, and provide links to relevant CLI documentation.
- Consider adding a table or section summarizing all deployment options (Portal, CLI, PowerShell, REST API) with links or code snippets for each.
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 Windows bias by only referencing ASP.NET Core and Visual Studio Code for creating and publishing web APIs, which are traditionally associated with Windows development environments. There are no examples or references for Linux-based frameworks, tools, or deployment workflows. The documentation does not mention or provide parity for Linux users or alternative stacks.
Recommendations
- Include examples for creating and publishing web APIs using popular Linux-based frameworks (e.g., Node.js/Express, Python/Flask, Java/Spring Boot) and show how to deploy them to Azure App Service.
- Add instructions or links for deploying web apps to Azure from Linux environments using the Azure CLI, GitHub Actions, or other cross-platform tools.
- Ensure that references to development tools (such as Visual Studio Code) clarify their cross-platform nature, and provide Linux-specific setup guidance where appropriate.
- Provide sample commands or scripts for Linux shells (bash/zsh) alongside any PowerShell or Windows command examples, if relevant.
- Explicitly state that Azure App Service and API Management support web apps developed and deployed from both Windows and Linux environments.
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
Windows First
Missing Linux Example
Summary
The documentation exclusively references the Azure portal (a web-based GUI) and Microsoft Entra ID for OAuth 2.0 configuration, with all step-by-step instructions and screenshots based on the Azure portal interface. There are no command-line examples (such as Azure CLI, PowerShell, Bash, or REST API), nor are there references to Linux-native tools or workflows. The documentation assumes use of the Azure portal, which is platform-agnostic but is often associated with Windows-centric workflows. No Linux-specific or cross-platform command-line instructions are provided.
Recommendations
- Add equivalent instructions using Azure CLI (az) commands for all steps involving app registration, permission assignment, and OAuth configuration. Azure CLI is cross-platform and works natively on Linux.
- Provide REST API examples for automation scenarios, which are platform-neutral.
- Include references or links to documentation for configuring OAuth 2.0 with non-Microsoft providers, or at least mention that the steps may differ for other providers.
- Explicitly state that all steps can be performed from any OS via the Azure portal, and highlight any platform-specific considerations if they exist.
- Where screenshots or UI navigation are shown, consider supplementing with command-line equivalents for users who prefer or require non-GUI workflows.
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 mentioned before the Linux/macOS path (/etc/hosts). Additionally, a related link points to a Windows 2000 Server DNS article, further emphasizing Windows-centric resources.
Recommendations
- When referencing file paths or system locations (such as the hosts file), list Linux/macOS and Windows paths together or alternate their order to avoid 'Windows first' bias.
- Provide links to cross-platform or Linux/macOS-specific DNS configuration documentation, not just Windows resources.
- Where possible, include examples or references for both Windows and Linux tools/utilities when discussing system configuration steps.
- Audit related content and external links to ensure they are not disproportionately focused on Windows, especially when the topic is broadly applicable.
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
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on the Azure portal and Microsoft Entra ID (formerly Azure AD), which are Microsoft-centric tools and services. All step-by-step instructions and screenshots are based on the Azure portal UI, with no mention of command-line alternatives (such as Azure CLI, PowerShell, or REST API), nor any examples for Linux-based workflows or non-Microsoft OAuth 2.0 providers. There are no references to Linux tools, shell commands, or cross-platform approaches for registering applications or configuring OAuth 2.0, making the documentation less accessible to Linux users or those preferring automation and scripting.
Recommendations
- Provide equivalent instructions using Azure CLI and/or REST API, which are cross-platform and can be run on Linux, macOS, and Windows.
- Include examples for registering applications and configuring OAuth 2.0 using command-line tools (e.g., az ad app create, az ad app permission, etc.), not just the Azure portal.
- Mention and, where possible, demonstrate how to use non-Microsoft OAuth 2.0 providers (such as Google, Okta, Auth0) to illustrate broader applicability.
- Add a section or callout for Linux users, highlighting any differences or additional steps required when working outside the Windows ecosystem.
- Ensure that any screenshots or UI references are supplemented with text-based, scriptable alternatives for automation and CI/CD scenarios.
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
Missing Linux Example
Windows First
Summary
The documentation provides instructions exclusively through the Azure Portal UI and does not include any command-line examples. There is no mention of PowerShell or Windows-specific tools, but there is also a complete absence of Linux or cross-platform CLI (e.g., Azure CLI, Bash) examples. All example paths and screenshots are based on the Azure Portal, which is platform-agnostic but may be more familiar to Windows users. The lack of CLI or script-based instructions can disadvantage Linux users or those who prefer automation.
Recommendations
- Add Azure CLI examples for importing and configuring Azure OpenAI APIs in API Management, as the Azure CLI is cross-platform and widely used on Linux.
- Include Bash script snippets for downloading and editing the OpenAPI specification, in addition to the manual text editor instructions.
- Explicitly mention that all steps can be performed on any OS via the Azure Portal, but provide parity with CLI-based workflows for users on Linux or those preferring automation.
- If PowerShell examples are ever added, ensure equivalent Bash/Azure CLI examples are provided alongside.
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 First
Missing Linux Example
Summary
The documentation exclusively uses the Azure portal (web UI) for all steps and does not provide any command-line examples. There are no references to Windows-specific tools like PowerShell, but the lack of CLI instructions (such as Azure CLI or Bash) means Linux users do not see parity. The workflow implicitly assumes a GUI-first (and thus, often Windows-first) approach, which can disadvantage users on Linux or those who prefer automation.
Recommendations
- Add equivalent Azure CLI commands for all steps, especially for creating app registrations, configuring credential providers, and setting API Management policies.
- Provide Bash shell examples for relevant steps, such as using curl or az commands.
- Explicitly mention that all steps can be performed on any OS via the Azure portal, but highlight CLI alternatives for Linux/macOS users.
- Include a section or callout for automation and scripting, referencing cross-platform tools.
- Ensure screenshots and instructions do not assume a Windows environment (e.g., avoid showing Windows-only UI elements if possible).
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 primarily demonstrates deployment using the Azure Portal UI and briefly mentions Azure PowerShell, Azure CLI, and REST API as alternatives, but does not provide any concrete command-line examples for any platform. There is a subtle Windows-first bias in the order of tool mentions (PowerShell before CLI), and the absence of explicit Linux/macOS command-line examples or screenshots. The documentation does not show any PowerShell or Windows-specific commands, but also does not provide parity for Linux users.
Recommendations
- Add explicit Azure CLI examples for deploying the ARM template, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
- When listing alternative deployment methods, mention Azure CLI before PowerShell to avoid implying a Windows-first workflow.
- Include at least one example of deploying the template using the Azure CLI, with sample commands and expected output.
- If referencing PowerShell, also provide Bash/Linux shell equivalents for all command-line operations.
- Add screenshots or terminal snippets from both Windows and Linux environments if possible, or use neutral/abstracted terminal screenshots.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/private-endpoint.md
.../blob/main/articles/api-management/private-endpoint.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by exclusively referencing the Azure portal (a web UI), Azure CLI, and REST API for configuration, but does not provide any OS-specific command-line examples. However, in the 'Test in virtual network' section, only the nslookup utility is mentioned for DNS validation, which is available on both Windows and Linux, but no explicit Linux or cross-platform shell examples are provided. There are no PowerShell-specific commands or Windows-only tools, but the absence of Linux-specific or cross-platform shell examples (e.g., bash, curl, dig) and the lack of explicit mention of Linux environments or tools indicate a subtle Windows-first and missing Linux example bias.
Recommendations
- Include explicit Linux and cross-platform command-line examples (e.g., using dig, curl, or bash scripts) alongside nslookup.
- When referencing Azure CLI, clarify that it is cross-platform and provide sample commands in both Windows (cmd/PowerShell) and Linux (bash) syntax where relevant.
- Add troubleshooting and validation steps using common Linux tools (e.g., dig, host, curl) to ensure parity.
- Explicitly mention that all steps can be performed from Linux environments, and provide any OS-specific notes if differences exist.
- Where screenshots or UI steps are shown, consider adding CLI/automation alternatives that are equally accessible from Linux.
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 exhibits subtle Windows bias in the DNS configuration section. The hosts file path is listed as '%SystemDrive%\drivers\etc\hosts' (Windows) before '/etc/hosts' (Linux, macOS), and a related link in 'Related content' points to a Windows 2000 Server DNS article. No Linux-specific tools or commands are mentioned, and no Linux-first or Linux-only examples are provided.
Recommendations
- List Linux and Windows hosts file paths in parallel or alternate the order to avoid 'windows_first' bias.
- Provide links to cross-platform or Linux/macOS-specific DNS configuration documentation, not just Windows resources.
- Include example commands for editing the hosts file on both Windows (e.g., using Notepad with admin rights) and Linux/macOS (e.g., using sudo nano or vi).
- Where possible, reference cross-platform tools or provide equivalent instructions for both operating systems.
- Review 'Related content' to ensure Linux and macOS users are equally supported with relevant links.
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
Missing Linux Example
Windows First
Summary
The documentation exclusively uses the Azure portal (web UI) for all instructions and does not provide any command-line examples. There are no references to Windows-specific tools like PowerShell, but there is also a complete absence of Linux (or cross-platform) CLI examples (such as Azure CLI or Bash). This omission can be considered a subtle form of Windows bias, as the Azure portal is often associated with Windows-centric workflows and many users on Linux or macOS prefer CLI-based instructions. Additionally, the lack of CLI parity may hinder automation and scripting, which are common in Linux environments.
Recommendations
- Add Azure CLI examples for all major steps, such as importing an API, configuring authentication, and testing endpoints.
- Provide Bash script snippets for downloading and editing the OpenAPI specification.
- Explicitly mention that all steps can be performed on Linux, macOS, and Windows, and provide cross-platform instructions where possible.
- Include references to relevant Azure CLI documentation and ensure that screenshots or UI instructions are supplemented with equivalent CLI commands.
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 references the Azure portal (web UI) for all steps and does not provide any command-line examples. There is no mention of platform-specific tools, but where command-line or scripting could be relevant (e.g., downloading and editing OpenAPI specs, importing APIs), no examples are given for PowerShell, Windows CMD, Bash, or Linux CLI tools. The lack of CLI instructions or examples means that users on Linux or macOS are not provided parity with Windows users, who might expect PowerShell or CMD instructions. The documentation implicitly assumes a GUI-first, Windows-centric workflow by referencing the Azure portal and omitting cross-platform CLI alternatives.
Recommendations
- Add CLI examples for importing APIs using Azure CLI and/or PowerShell, and ensure both Windows and Linux/macOS commands are shown.
- Include instructions for downloading and editing OpenAPI specifications using cross-platform tools (e.g., curl, wget, nano, vi, notepad).
- Explicitly mention that all steps can be performed on any OS via the Azure portal, but provide parity by showing how to accomplish tasks using CLI tools available on Linux/macOS.
- Where screenshots are shown, clarify that the portal is accessible from any OS and consider including CLI output or code snippets for automation scenarios.
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 First
Missing Linux Example
Summary
The documentation exclusively uses the Azure Portal (web UI) for all steps and does not provide any command-line examples. While this avoids explicit Windows-only tools like PowerShell, it implicitly favors Windows users by not mentioning or demonstrating CLI-based workflows (such as Azure CLI or Bash scripting), which are commonly used on Linux and macOS. There are no Linux-specific instructions, nor are cross-platform command-line alternatives provided.
Recommendations
- Add Azure CLI examples for each major step (e.g., app registration, credential provider creation, API configuration), ensuring commands work on Linux, macOS, and Windows.
- Explicitly mention that all portal steps can be performed from any OS, but provide CLI alternatives for automation and parity.
- Include sample scripts in Bash (and optionally PowerShell) for common tasks, such as registering an app or configuring API Management.
- Reference Azure CLI documentation and provide links for users who prefer command-line or automated workflows.
- Review all screenshots and instructions to ensure they do not assume a Windows environment (e.g., avoid showing Windows-specific UI elements or file paths).
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
Missing Linux Example
Windows First
Summary
The documentation exclusively describes using the Azure Portal (a web interface) for all operations and does not provide any command-line examples. There are no references to Windows-specific tools or PowerShell, but also no mention of Linux, CLI, or cross-platform automation. The lack of Azure CLI, Bash, or REST API examples means Linux and automation-focused users are underserved. The instructions implicitly assume a GUI-first (and thus often Windows-first) workflow, which can be a subtle form of bias.
Recommendations
- Add equivalent instructions for enabling and managing Defender for APIs using the Azure CLI (az), which is cross-platform and widely used on Linux.
- Include REST API examples for onboarding/offboarding APIs to Defender for APIs, allowing for automation and platform independence.
- If PowerShell examples are ever added, ensure Bash or CLI equivalents are provided alongside.
- Explicitly mention that all steps can be performed from any OS via the Azure Portal, but highlight and document command-line and automation options for Linux users.
- Consider a 'Choose your platform' section at the start, linking to instructions for Portal, CLI, PowerShell, and REST API.
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 bias by only providing instructions for enabling DDoS protection using the Azure Portal (a GUI tool most accessible from Windows) and referencing a PowerShell-based guide for enabling DDoS IP Protection. There are no CLI (az cli), Bash, or Linux-native instructions or examples, and the only automation example points to PowerShell, which is primarily a Windows tool.
Recommendations
- Add equivalent instructions for enabling DDoS protection using Azure CLI (az cli) commands, which are cross-platform and commonly used on Linux and macOS.
- Provide Bash script examples where automation is discussed, or at least reference Bash/CLI alternatives alongside PowerShell.
- When linking to automation guides (such as enabling DDoS IP Protection), include links to both PowerShell and Azure CLI documentation, ensuring Linux users have clear, first-class guidance.
- Explicitly mention that the Azure Portal is web-based and cross-platform, but also provide command-line alternatives for users who prefer or require non-GUI workflows.
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 primarily describes deploying an ARM template using the Azure Portal, and only briefly mentions alternative methods (Azure PowerShell, Azure CLI, REST API) without providing any examples or commands. There are no explicit examples for Linux users (e.g., Bash or CLI commands), and the mention of PowerShell precedes Azure CLI, which is more cross-platform. No Linux-specific tools or terminal instructions are provided.
Recommendations
- Provide explicit Azure CLI (bash) command examples for deploying the ARM template, alongside or before PowerShell examples.
- Include step-by-step instructions for deploying the template using the Azure CLI, suitable for Linux/macOS users.
- When listing alternative deployment methods, mention Azure CLI before PowerShell to emphasize cross-platform support.
- Add examples for reviewing and cleaning up resources using Azure CLI commands, not just via the Azure Portal.
- Consider a table or section comparing deployment methods (Portal, CLI, PowerShell, REST) with links or inline examples for each.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/private-endpoint.md
.../blob/main/articles/api-management/private-endpoint.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a mild Windows bias by omitting explicit Linux-specific instructions or examples. All command-line examples use the Azure CLI, which is cross-platform, but there are no references to Linux-specific tools, shell environments, or differences in experience. The only DNS test example uses nslookup, which is available on both platforms, but no mention is made of dig (commonly used on Linux). All portal navigation and screenshots are platform-agnostic, but the absence of Linux- or macOS-specific notes or examples may leave Linux users without tailored guidance.
Recommendations
- Include explicit Linux and macOS command-line examples where relevant, especially for DNS validation (e.g., show both nslookup and dig).
- Add notes about cross-platform compatibility for Azure CLI commands, including any differences in installation or usage between Windows, Linux, and macOS.
- Where testing connectivity or DNS, provide example commands for both Windows (nslookup, PowerShell) and Linux/macOS (dig, host, nslookup).
- If referencing tools or utilities, clarify their availability and installation on different operating systems.
- Consider adding a section or callout for Linux/macOS users, highlighting any unique steps or considerations.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/how-to-deploy-self-hosted-gateway-container-apps.md
...nt/how-to-deploy-self-hosted-gateway-container-apps.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, but consistently lists Bash first. There is no exclusive use of Windows tools, but the presence of PowerShell tabs and syntax throughout the article indicates a Windows-centric approach. No Linux-specific tools or patterns are mentioned, but Bash examples are present and complete. There are no missing Linux examples, but the dual tab format may suggest a slight bias towards Windows users by always including PowerShell and referencing 'PowerShell syntax.'
Recommendations
- Consider explicitly stating that Bash examples are suitable for Linux/macOS and that PowerShell is for Windows, to clarify parity.
- Add a note confirming that all Azure CLI commands work identically on Linux, macOS, and Windows (with Bash or PowerShell).
- If possible, provide a single, unified CLI example when the syntax is identical, reducing the perception of platform bias.
- Include troubleshooting or environment preparation notes for both Linux and Windows users, not just generic Azure CLI setup.
- Ensure that any references to the Azure portal or tools are not Windows-specific (which is currently the case, but should be monitored in future updates).
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 (az CLI), Bash, or Linux-native instructions. There are no Linux or cross-platform command-line examples, and the only automation example is PowerShell-focused.
Recommendations
- Add Azure CLI (az) command examples for enabling DDoS Protection on both VNets and public IP addresses, alongside or instead of PowerShell instructions.
- Include Bash shell examples for relevant operations, ensuring parity for Linux and macOS users.
- When linking to further instructions (such as enabling DDoS IP Protection), provide links to both PowerShell and Azure CLI documentation.
- Explicitly mention that all operations can be performed from any OS using Azure CLI, not just via PowerShell or the Azure Portal.
- Consider including a table or section comparing methods (Portal, PowerShell, Azure CLI) for each task to highlight cross-platform options.
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 page references Windows-specific tools (PowerShell) for backend management and omits mention of Linux-native or cross-platform alternatives. No Linux-specific examples or CLI instructions are provided, and PowerShell is the only command-line tool explicitly mentioned.
Recommendations
- Add equivalent Azure CLI examples for backend management tasks, as Azure CLI is cross-platform and widely used on Linux.
- Mention that backend entities can also be managed via Azure CLI, and provide a link to relevant documentation.
- Ensure that any references to PowerShell are accompanied by Azure CLI or REST API examples to provide parity for Linux and macOS users.
- Consider including a note that PowerShell Core is cross-platform, but clarify usage instructions for Linux environments if PowerShell is to be retained.