API Management
548
Total Pages
499
Linux-Friendly Pages
49
Pages with Bias
8.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
112 issues found
Showing 1-25 of 112 flagged pages
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
Windows First
Summary
The documentation page demonstrates Windows bias by providing a PowerShell command (`New-AzApiManagementSystemCertificate`) as the only CLI example for uploading a CA certificate, without mentioning or providing equivalent Azure CLI, Bash, or Linux-native instructions. The use of PowerShell and lack of Linux-specific or cross-platform examples may disadvantage users on non-Windows systems.
Recommendations
- Add equivalent Azure CLI commands for uploading CA certificates, with syntax examples for Bash and Linux environments.
- Explicitly mention cross-platform options and clarify that certificate upload can be performed from any OS using Azure CLI or REST API.
- Provide sample workflows for Linux and macOS users, including certificate file handling and upload steps.
- Reorder examples so that cross-platform or OS-neutral methods (e.g., Azure CLI, REST API) are presented before or alongside PowerShell.
- Include notes or links to documentation on installing and using Azure CLI on Linux/macOS.
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
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing PowerShell examples and instructions, referencing Azure PowerShell cmdlets and tools first, and providing more detailed PowerShell usage scenarios. While Azure CLI and REST API examples are included, PowerShell is consistently presented before CLI (which is more cross-platform and Linux-friendly), and there are no explicit Bash scripting or Linux shell examples beyond the CLI. There is also no mention of Linux-specific considerations or parity in the prerequisites or troubleshooting sections.
Recommendations
- Present Azure CLI (Bash) examples before or alongside PowerShell examples to ensure Linux users are equally supported.
- Expand Bash/Linux shell scripting examples, including variable handling and error checking, to match the detail level of PowerShell sections.
- Explicitly state that all CLI examples are cross-platform and tested on Linux, macOS, and Windows.
- Add troubleshooting tips or notes for Linux users, such as common issues with authentication or permissions.
- Where PowerShell-specific cmdlets are mentioned, provide equivalent Azure CLI commands and reference the official CLI documentation.
- Avoid using 'PowerShell' as the default or primary automation tool in introductory or summary sections; instead, refer to both PowerShell and CLI equally.
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, with no mention of Linux-friendly alternatives such as Azure CLI or REST API. No Linux-specific or cross-platform command-line examples are provided, and the only non-portal automation example is PowerShell, 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.
- Mention REST API methods for user management, providing sample requests and responses.
- Clarify that PowerShell is available cross-platform, but also provide parity with CLI and REST instructions.
- Ensure that automation and scripting examples are not limited to Windows-centric tools, and present Linux-friendly options alongside or before Windows-specific ones.
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
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 by referencing a Windows batch script (.bat) for cleanup operations. There are no equivalent examples or instructions for Linux users (e.g., Bash scripts, Azure CLI), nor are cross-platform alternatives mentioned. This may hinder Linux users or those working in non-Windows environments from following the guidance without additional research.
Recommendations
- Provide equivalent Azure CLI or Bash script examples alongside PowerShell scripts for role assignment and management tasks.
- Include instructions for running cleanup operations using shell scripts (.sh) or Azure CLI, not just Windows batch files.
- Explicitly state cross-platform compatibility for all scripts and tools, or provide guidance for Linux/macOS users where differences exist.
- Where possible, mention both Windows and Linux tools/patterns together, or in parallel sections, to ensure parity.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/import-soap-api.md
...s/blob/main/articles/api-management/import-soap-api.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but PowerShell is given equal prominence to CLI, and PowerShell is a Windows-centric tool. The prerequisites section lists Azure PowerShell immediately after Azure CLI, and the PowerShell example is detailed and uses Windows-specific cmdlets. There are no Linux shell (bash) or cross-platform scripting examples, nor is there mention of Linux-specific tools or patterns. The documentation assumes familiarity with PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Add bash/sh shell script examples using Azure CLI to demonstrate Linux-native workflows.
- Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
- Mention that PowerShell Core is available on Linux and macOS, but provide explicit bash examples for parity.
- Where possible, use generic CLI commands in examples before introducing platform-specific tools like PowerShell.
- Add notes or links for Linux users on installing and using Azure CLI and PowerShell Core on their systems.
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
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily by referencing PowerShell in the 'Related content' section for connecting virtual networks, without mentioning equivalent Linux/CLI/Bash examples. There are no explicit Linux or cross-platform command-line examples, and the only automation example provided is for PowerShell, which is Windows-centric. Additionally, where portal actions are described, there is no mention of Azure CLI or cross-platform alternatives.
Recommendations
- Add Azure CLI (cross-platform) examples alongside or before PowerShell references, especially in 'Related content' and any automation guidance.
- When referring to automation or scripting, provide both PowerShell and Bash/CLI equivalents to ensure Linux parity.
- Mention the Azure portal, Azure CLI, and PowerShell equally when describing configuration steps, or provide links to all relevant platform-specific guides.
- Review all linked articles (such as VPN and VNet connection guides) to ensure they include Linux/CLI options, and update this page to reference them.
- Explicitly state that all operations can be performed from Windows, Linux, or macOS using Azure CLI, and provide examples or links where appropriate.
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
Windows Tools
Missing Linux Example
Summary
The documentation page primarily demonstrates deployment using the Azure Portal, with only brief mentions of Azure PowerShell, Azure CLI, and REST API as alternatives. There are no explicit examples or step-by-step instructions for deploying via Azure CLI (which is cross-platform and preferred on Linux) or Bash scripting. The only command-line tool mentioned by name in the main flow is Azure PowerShell, a Windows-centric tool, and it is listed before Azure CLI. There are no Linux-specific instructions or screenshots.
Recommendations
- Add explicit, step-by-step examples for deploying the ARM template using Azure CLI (az deployment group create ...) and Bash, including command snippets.
- When listing alternative deployment methods, mention Azure CLI before Azure PowerShell to reflect cross-platform parity.
- Include screenshots or terminal output examples from Linux environments where appropriate.
- Clarify that all deployment methods (Azure Portal, Azure CLI, PowerShell, REST API) are supported on all platforms, and provide links to Linux-specific setup guides for Azure CLI.
- Consider adding a section or callout box specifically for Linux/macOS users, highlighting the recommended tools and any differences.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/self-hosted-gateway-enable-azure-ad.md
.../api-management/self-hosted-gateway-enable-azure-ad.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently referencing Azure Portal and PowerShell/CLI tools before or instead of Linux-native alternatives. Role assignment and app registration steps are linked primarily to Azure Portal (a web UI often associated with Windows workflows) and PowerShell/CLI, with no explicit Linux shell or cross-platform command-line examples. There are no Linux-specific instructions for tasks like role assignment or app registration, and the documentation does not mention or prioritize Linux-native tools or workflows.
Recommendations
- Provide explicit Linux shell (bash) examples for Azure CLI commands, especially for role assignments and app registration.
- When referencing Azure Portal, also link to or describe equivalent steps using Azure CLI in bash, making it clear these can be run on Linux/macOS.
- Where PowerShell is mentioned, ensure Azure CLI (bash) alternatives are presented first or equally.
- Clarify that all command-line steps can be performed on Linux, and provide sample commands where appropriate.
- Add a section or callout for Linux users, summarizing the parity of steps and tools available.
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
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but presents Azure CLI (cross-platform) first, followed by Azure PowerShell (Windows-centric). There are no explicit Linux shell examples (e.g., bash scripts), and the PowerShell section uses Windows-style variable assignment. The prerequisites mention both Azure CLI and PowerShell, but do not clarify platform parity or recommend cross-platform tools over Windows-specific ones.
Recommendations
- Add explicit bash/Linux shell examples where applicable, especially for variable assignment and command usage.
- Clarify in prerequisites that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows (unless using PowerShell Core).
- Consider adding a 'Bash' or 'Linux shell' tab alongside Azure CLI and PowerShell for command-line steps.
- When referencing tools, mention cross-platform options first and provide clear guidance for users on different operating systems.
- Review code snippets to ensure they are not using Windows-specific syntax unless necessary, and provide equivalent Linux/macOS alternatives.
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 equivalent example for Linux users (e.g., Azure CLI, Bash, or REST API). The only non-portal automation method mentioned is PowerShell, which is primarily a Windows tool. There is no mention of cross-platform alternatives or Linux-first approaches.
Recommendations
- Add Azure CLI examples for uploading and managing CA certificates, as Azure CLI is cross-platform and widely used on Linux.
- Include REST API examples for certificate management, which are platform-agnostic.
- When mentioning PowerShell, also provide equivalent commands for Azure CLI and/or Bash scripts.
- Explicitly state that PowerShell Core is cross-platform if recommending PowerShell, and clarify compatibility.
- Reorder or present all automation options together (PowerShell, Azure CLI, REST API) rather than only mentioning PowerShell.
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
Windows First
Summary
The documentation page demonstrates a Windows bias by providing example commands and tooling primarily for Azure PowerShell, which is most commonly used on Windows. The only CLI-based example for creating a logger with connection string credentials is given in PowerShell, with no equivalent shown for Bash, Azure CLI, or other Linux-native tools. References to tools (e.g., PowerShell cmdlets) are made before mentioning cross-platform alternatives, and there is no explicit guidance or examples for Linux users or those using Bash/Azure CLI.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, especially for creating loggers with connection string credentials.
- Include Bash shell snippets where appropriate, demonstrating how to use REST API calls via curl or az rest.
- Explicitly mention that Bicep and ARM templates are cross-platform and can be used on Linux, macOS, and Windows.
- Where PowerShell is referenced, clarify that it is available cross-platform, but also provide alternatives for users who prefer Bash or Azure CLI.
- Review all tool references and ensure Linux-native tools (Azure CLI, Bash, curl) are mentioned and demonstrated alongside Windows tools.
- Consider adding a 'Platform considerations' section to guide users on how to perform steps on both Windows and Linux.
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
Summary
The documentation page demonstrates a bias toward Windows environments by providing detailed Azure PowerShell examples for all identity management tasks, while omitting equivalent examples for Linux-friendly tools such as Azure CLI. PowerShell is a Windows-centric tool, and its usage is presented before or instead of alternatives. There are no Linux-specific instructions or examples, and no mention of cross-platform command-line options. The ARM template and portal instructions are platform-neutral, but all scripting guidance is PowerShell-only.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that Azure CLI can be used for these tasks, and link to relevant CLI documentation.
- Where scripting is shown, present both PowerShell and CLI examples side-by-side, or indicate which is recommended for each platform.
- Consider including Bash shell script snippets for automation scenarios.
- Review and update any referenced sample links to ensure Linux parity.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-role-based-access-control.md
...management/api-management-role-based-access-control.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 examples for custom role creation and assignment, referencing PowerShell before Azure CLI and REST API, and omitting equivalent Linux/bash examples. The use of PowerShell-centric instructions and lack of cross-platform scripting alternatives may disadvantage Linux users or those preferring bash/CLI workflows.
Recommendations
- Add equivalent Azure CLI and bash examples for custom role creation and assignment alongside PowerShell scripts.
- Present Azure CLI and REST API options before or alongside PowerShell to avoid Windows-first ordering.
- Explicitly mention cross-platform compatibility for all tools and scripts.
- Include notes or links to Linux-specific instructions or troubleshooting for common RBAC tasks.
- Ensure that all code samples are available in both PowerShell and bash/CLI formats to improve accessibility for non-Windows users.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-using-with-vnet.md
...icles/api-management/api-management-using-with-vnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing the Azure portal (a GUI tool most familiar to Windows users) as the primary configuration method and by linking to related content that specifically mentions PowerShell for VPN Gateway connections, without providing equivalent Linux/CLI/Bash examples. There are no explicit Linux or cross-platform command-line instructions, and no mention of Azure CLI or Bash scripting alternatives.
Recommendations
- Add Azure CLI (cross-platform) examples for configuring VNet connectivity and API Management deployment, alongside or before PowerShell/portal instructions.
- Where PowerShell scripts or references are provided (e.g., in related content), include equivalent Bash/Azure CLI commands.
- Explicitly mention that all steps can be performed from Linux/macOS using the Azure CLI or Cloud Shell, and provide links to relevant documentation.
- Balance the order of instructions so that cross-platform (CLI) methods are presented before or alongside Windows-specific tools.
- Review related content links to ensure Linux users are not directed only to PowerShell-based guides.
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 First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively references Azure PowerShell cmdlets and PowerShell workflow scripts for managing Azure API Management via Azure Automation. All examples and tutorials are PowerShell-based, with no mention of Linux-native tools, Bash, Azure CLI, or cross-platform scripting options. This creates a strong Windows and PowerShell bias, potentially excluding Linux users or those preferring platform-neutral automation approaches.
Recommendations
- Add equivalent examples using Azure CLI for API Management tasks within Azure Automation.
- Include Bash or Python script samples for managing API Management, demonstrating cross-platform automation.
- Mention that Azure Automation supports both PowerShell and Python runbooks, and provide links or examples for non-Windows environments.
- Reorder or balance references so that Windows and Linux tools are presented equally, or clarify cross-platform support up front.
- Highlight any limitations or considerations for Linux users, and provide guidance for setting up Azure Automation from Linux environments.
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
Azure Tools Heavy
Summary
The documentation page focuses exclusively on Azure-centric tools and workflows, with all examples using Azure CLI, Azure Functions, and Azure CDN. There are no Linux-specific instructions, nor are alternative non-Azure or Linux-native tools mentioned. The examples and recommendations assume the use of Azure services, which are most commonly used in Windows environments, and do not provide parity for Linux users or those using open-source alternatives.
Recommendations
- Provide explicit instructions and examples for Linux environments, such as using bash scripts, Linux-native CLI tools, or alternative hosting solutions (e.g., Apache, Nginx, or open-source CDNs).
- Include non-Azure options for hosting and CDN, such as Amazon S3, Google Cloud Storage, Cloudflare CDN, or self-hosted solutions.
- Clarify that all commands (npm, curl, az) are cross-platform, and specify any platform-specific considerations (e.g., installation steps for Azure CLI or Azure Functions Core Tools on Linux).
- Add troubleshooting notes for common Linux issues (e.g., permissions, environment variables, file system differences).
- Balance recommendations by mentioning both Windows and Linux approaches where relevant, and avoid assuming Azure as the default platform.
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
Missing Linux Example
Windows First
Summary
The documentation shows a bias towards Windows environments by providing only PowerShell scripts for role assignment and management, referencing .bat scripts for cleanup, and omitting equivalent Bash or CLI examples for Linux/macOS users. Windows tools and patterns are mentioned exclusively, with no Linux alternatives or parity guidance.
Recommendations
- Provide Azure CLI or Bash script equivalents for all PowerShell examples, especially for role creation and assignment.
- Include instructions for running cleanup scripts on Linux/macOS (e.g., provide a .sh script or explain how to adapt the .bat script).
- When referencing scripts or commands, mention both Windows and Linux options, or clarify cross-platform compatibility.
- Order examples so that cross-platform or Linux-native tools (e.g., Azure CLI) are presented before or alongside Windows/PowerShell tools.
- Explicitly state platform requirements or limitations when only Windows tools are available, and link to alternative guidance for Linux users.
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
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows and Azure-centric tools and workflows. It exclusively references Azure DevOps (Azure Repos, Azure Pipelines), GitHub Actions, and the Azure APIOps Toolkit, all of which are primarily oriented toward Windows or Azure environments. There are no explicit examples or mentions of Linux-native CI/CD tools (such as Jenkins, GitLab CI, or Travis CI), nor are there any command-line examples for Linux shells (bash, sh). The documentation also assumes the use of ARM templates and .NET-based tools, which are more common in Windows-centric workflows. While Terraform is mentioned, its usage is described only in the context of Azure Pipelines and GitHub Actions, not in a broader, platform-agnostic way.
Recommendations
- Include examples using popular Linux-native CI/CD tools such as Jenkins, GitLab CI, or Travis CI, and show how they can be used to publish APIs to Azure API Management.
- Provide command-line examples for both PowerShell (Windows) and Bash (Linux/macOS) where relevant, especially for tasks like deploying ARM templates or using the Azure CLI.
- Mention and link to Azure CLI documentation and examples, which are cross-platform, rather than focusing solely on Azure Pipelines or PowerShell-based workflows.
- Highlight that all tools and workflows described can be executed from Linux environments, and provide explicit instructions or notes where there are differences.
- Add a section or callout on best practices for Linux-based development environments, including containerized CI/CD runners and integration with open-source tools.
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 the Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the PowerShell section is Windows-centric, and there is no mention of Linux-specific tools or shell environments (e.g., Bash). The prerequisites list Azure PowerShell and Azure CLI, but the PowerShell section is given equal prominence to CLI, and there are no explicit Linux/Bash examples or troubleshooting notes for Linux users. The documentation also references the Azure Portal, which is web-based and platform-neutral, but command-line examples do not highlight Linux parity.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell commands using Bash syntax (e.g., export instead of set for environment variables).
- Add a note clarifying that PowerShell examples are primarily for Windows users, and suggest using Azure CLI for Linux/macOS users.
- Include troubleshooting tips or environment setup notes for Linux users, such as installing Azure CLI on Linux.
- Consider adding a Bash-specific example or a section showing how to perform the same tasks in a typical Linux shell environment.
- Where possible, avoid giving the impression that PowerShell is the default or preferred method for all users.
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
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on the Azure portal (a web-based, cross-platform tool, but often associated with Windows environments), and by only providing .NET/.NET Core examples for calling gRPC services, which are most commonly used on Windows. There are no examples or references for Linux-specific tools, workflows, or alternative client stacks (e.g., grpcurl, curl, or gRPC tools for Linux/macOS). No Linux command-line or shell examples are provided, and the documentation does not mention Linux-specific considerations or tools.
Recommendations
- Add examples for importing gRPC APIs using Linux-friendly tools such as Azure CLI or REST APIs, with bash shell commands.
- Include references to cross-platform or Linux-native gRPC client tools (e.g., grpcurl, grpc_cli) for testing and interacting with gRPC APIs.
- Provide parity in documentation by including .NET, Java, Python, and Go client examples, with explicit mention of Linux/macOS compatibility.
- Mention any Linux-specific prerequisites or troubleshooting steps, if applicable.
- Clarify that the Azure portal is web-based and accessible from any OS, to avoid the impression of Windows-centricity.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/import-api-from-oas.md
...ob/main/articles/api-management/import-api-from-oas.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 PowerShell (a Windows-centric tool) given equal prominence to the cross-platform Azure CLI. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tools or workflows. The PowerShell example uses Windows-style variable assignment and context setup, which may not be familiar or directly usable for Linux users. The documentation refers to Azure PowerShell requirements in the prerequisites, reinforcing the Windows bias.
Recommendations
- Add explicit bash examples for Azure CLI commands, showing usage in a Linux shell environment.
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- De-emphasize PowerShell as the default scripting environment, or provide parity by including bash/zsh examples.
- Mention installation and usage steps for Azure CLI and PowerShell on Linux and macOS, not just Windows.
- If PowerShell is included, note that PowerShell Core is available cross-platform, and provide examples compatible with Linux/macOS.
- Consider adding a table or section comparing workflows on Windows vs. Linux, highlighting any differences.
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
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation references enabling DDoS IP Protection via a link to a PowerShell-based guide, which is typically associated with Windows environments. There are no examples or instructions for Linux-native tools (such as Azure CLI or Bash), nor is there mention of cross-platform alternatives. The instructions and screenshots focus on the Azure Portal (web UI), which is platform-agnostic, but the only command-line reference is PowerShell, indicating a Windows bias.
Recommendations
- Add equivalent instructions and examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux and macOS.
- Explicitly mention that both PowerShell and Azure CLI can be used, and provide links or code snippets for both.
- Include Bash script examples where appropriate, especially for automation scenarios.
- Review linked pages (such as manage-ddos-protection-powershell-ip.md) to ensure Linux parity and add CLI/Bash alternatives if missing.
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
Windows Tools
Missing Linux Example
Summary
The documentation page primarily focuses on using the Azure Portal for deployment and only briefly mentions alternative methods (Azure PowerShell, Azure CLI, REST API) without providing any examples. The mention of Azure PowerShell and Azure CLI is secondary, and no Linux-specific instructions or screenshots are provided. The workflow and screenshots are tailored to the Azure Portal, which is more familiar to Windows users, and there are no command-line examples for Linux users.
Recommendations
- Add explicit, step-by-step examples for deploying the ARM template using Azure CLI, which is cross-platform and popular among Linux users.
- Provide both Azure PowerShell and Azure CLI command examples side-by-side, ensuring parity for Windows and Linux users.
- Include screenshots or terminal output examples from Linux environments (e.g., Bash shell) to balance the visual bias toward the Azure Portal.
- Mention that Azure CLI can be used on Windows, Linux, and macOS, and provide installation links for all platforms.
- Consider adding a section or callout specifically for Linux/macOS users, highlighting any differences or tips relevant to those platforms.
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 PowerShell is a Windows-centric tool and is presented as an equal alternative to Azure CLI. There are no explicit Linux shell examples (e.g., bash), and prerequisites mention Azure PowerShell without clarifying its cross-platform status or providing Linux-specific guidance. The documentation implicitly assumes familiarity with Windows tooling and does not offer parity for Linux users beyond Azure CLI.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, or provide explicit bash/Linux shell examples where appropriate.
- Add a dedicated Linux section or call out Linux-specific instructions, especially for environment setup and verification steps.
- Ensure that CLI examples use syntax and environment variables compatible with both Windows and Linux shells, or provide separate examples for each.
- Review prerequisites to include Linux-specific installation instructions for Terraform and Azure CLI/PowerShell.
- Consider mentioning or linking to WSL (Windows Subsystem for Linux) for Windows users who prefer a Linux environment.
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
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by explicitly mentioning PowerShell as a management tool for backend entities, without referencing Linux-native alternatives (such as Azure CLI or Bash scripting). No Linux-specific examples or tools are provided, and PowerShell is listed as a primary management method. There are no examples or instructions for managing backend entities from Linux environments.
Recommendations
- Add references and examples for managing backend entities using Azure CLI, which is cross-platform and widely used on Linux.
- Include Bash or shell scripting examples for common backend management tasks.
- Explicitly mention that management can be performed from Linux, macOS, and Windows, and provide parity in tooling instructions.
- List Azure CLI before or alongside PowerShell when enumerating management options.
- Ensure that all code and command examples are platform-neutral or provide both Windows and Linux alternatives.