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 51-75 of 594 flagged pages
API Management
Use API Management in a virtual network with Azure Application Gateway
...pi-management-howto-integrate-internal-vnet-appgateway.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits strong Windows bias by exclusively using Azure PowerShell for all configuration steps, providing only PowerShell code samples, and referencing Windows file paths (e.g., C:\Users\Contoso\). There are no CLI (az), Bash, or Linux-oriented examples, nor is there guidance for users on Linux or macOS platforms. The prerequisites and variable setup assume a Windows environment, further reinforcing the bias.
Recommendations
- Add equivalent Azure CLI (az) examples for all major steps, including resource creation, networking, certificates, and DNS configuration.
- Provide Bash shell script samples and Linux/macOS file path conventions alongside PowerShell examples.
- Include a section in prerequisites noting cross-platform options and how to install/configure Azure CLI and PowerShell on Linux/macOS.
- Reference Linux certificate generation and storage practices (e.g., using OpenSSL, storing certs in /home/user/ or /etc/ssl/).
- Explicitly state that all steps can be performed on Linux/macOS and provide troubleshooting tips for non-Windows environments.
- Where file paths are shown, provide both Windows and Linux/macOS formats.
Create Pull Request
API Management
How to Log Events to Azure Event Hubs in Azure API Management | Microsoft Docs
.../api-management/api-management-howto-log-event-hubs.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 in several ways. PowerShell is the only command-line example provided for creating loggers with connection string credentials, with no equivalent Bash, Azure CLI, or Linux shell example. The use of PowerShell is presented as the primary or sole scripting tool, and there is no mention of Linux-specific workflows or cross-platform alternatives. The documentation references Windows-centric tools (PowerShell) before mentioning cross-platform options (Bicep, ARM templates, REST API), and does not provide parity for Linux users in terms of command-line instructions or tooling.
Recommendations
- Add Azure CLI examples for all logger creation scenarios, especially for connection string credential setup.
- Include Bash or shell script snippets where PowerShell is used, or clarify that the steps are cross-platform.
- Explicitly mention that Bicep, ARM templates, and REST API methods are platform-agnostic and suitable for Linux/macOS users.
- Where PowerShell is referenced, provide a note or link to equivalent Linux/macOS instructions.
- Review and update documentation to ensure Linux and macOS users are equally supported in all procedural steps.
API Management
Secure API Management Backend Using Client Certificate Authentication
...management/api-management-howto-mutual-certificates.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates bias towards Windows by providing PowerShell-only examples for disabling certificate chain validation and referencing Windows-centric tools (PowerShell cmdlets) without offering equivalent Linux or cross-platform CLI instructions. There are no bash, Azure CLI, or Linux-specific examples for certificate management tasks, which may hinder Linux users' experience.
Recommendations
- Provide equivalent examples using Azure CLI (az apim) for all PowerShell cmdlets shown.
- Include bash shell examples for certificate management tasks, especially for disabling certificate chain validation.
- Explicitly mention cross-platform alternatives and clarify that management tasks can be performed on Linux/macOS as well as Windows.
- Add notes or links to documentation for Linux users on how to install and use Azure CLI for API Management operations.
- Ensure that REST API examples include curl or httpie commands to demonstrate platform-neutral usage.
API Management
Deploy Azure API Management Instance to External Virtual Network
...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 (which is most commonly used on Windows), and by linking to related content that specifically mentions PowerShell for VPN Gateway connections. There are no explicit Linux CLI or Bash examples, nor are Linux-specific tools or patterns discussed. The documentation does not provide parity for Linux users in terms of command-line instructions or alternative tooling.
Recommendations
- Include Azure CLI (cross-platform) examples alongside or before PowerShell examples for all configuration steps.
- Reference Bash or Linux shell commands for template deployment and network configuration where applicable.
- Add explicit instructions for accessing and configuring the Azure portal from Linux environments (e.g., browser compatibility, az login).
- Ensure that related content links include Linux-focused guides, such as VPN Gateway configuration using Azure CLI or REST API, not just PowerShell.
- When mentioning tools or scripts, clarify their cross-platform compatibility or provide alternatives for Linux users.
API Management
Use Managed Identities in Azure API Management | Microsoft Docs
...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 examples for command-line operations, with no mention of Azure CLI or Bash/Linux equivalents. PowerShell is referenced before any cross-platform tools, and installation instructions are tailored to Windows users. There is no guidance or code samples for Linux/macOS users, nor any mention of platform-agnostic alternatives. The documentation also references Windows-centric tools and patterns, such as PowerShell modules, without balancing with Linux-friendly approaches.
Recommendations
- Add Azure CLI examples alongside PowerShell for all command-line operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash script samples for resource creation and management, especially for steps currently shown only in PowerShell.
- Explicitly mention that Azure CLI and PowerShell are both supported, and provide links to installation guides for both on all major operating systems.
- Reorder sections so that cross-platform tools (Azure CLI, ARM templates) are presented before or alongside Windows-specific tools.
- Add notes or callouts for Linux/macOS users, clarifying any differences or additional steps required.
- Review and update references to 'PowerShell samples' to also include 'CLI samples' where available.
API Management
Versions in Azure API Management | Microsoft Docs
...ain/articles/api-management/api-management-versions.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page references Azure PowerShell and the Azure portal as primary management tools, listing Azure PowerShell before Azure CLI and omitting explicit Linux-oriented examples or tools. There are no command-line examples for Linux users, and the documentation does not mention cross-platform usage patterns or alternatives to Windows-centric tools. The focus on Azure PowerShell and the portal (which are more commonly used on Windows) suggests a Windows-first bias.
Recommendations
- Provide explicit Azure CLI examples alongside or before Azure PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
- Include command-line walkthroughs for managing API versions using Azure CLI, with sample commands.
- Mention that the Azure portal and Azure CLI are both accessible from Linux, macOS, and Windows, and clarify any platform-specific limitations.
- Add references to scripting and automation using Bash or other Linux-native tools where relevant.
- Ensure that documentation screenshots and instructions do not assume a Windows environment.
API Management
Securely Access Products and APIs - Microsoft Entra Applications - Azure API Management
...docs/blob/main/articles/api-management/applications.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell scripts for token generation and API calls, without offering equivalent examples for Linux or cross-platform tools such as curl or Bash. The use of PowerShell and references to the Azure portal (which is most commonly accessed from Windows environments) further reinforce the Windows-centric approach. No Linux-specific instructions or alternative command-line examples are provided, making it less accessible for Linux or macOS users.
Recommendations
- Provide equivalent examples using curl and Bash for token generation and API calls, suitable for Linux and macOS environments.
- Explicitly mention that the instructions are cross-platform where applicable, and clarify any platform-specific requirements.
- Include troubleshooting steps or notes relevant to Linux environments, such as handling environment variables or storing secrets securely.
- Reference cross-platform tools (e.g., Azure CLI) alongside PowerShell, and offer side-by-side examples for both.
- Review the documentation for other implicit Windows-first patterns, such as screenshots or terminology, and ensure parity for Linux users.
API Management
Manage Azure API Management using Azure Automation
...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 demonstrates a strong Windows bias by exclusively referencing Azure PowerShell cmdlets and PowerShell workflow scripts for managing Azure API Management via Azure Automation. No mention is made of Linux-friendly alternatives such as Azure CLI, Bash scripting, or cross-platform automation patterns. All examples and tutorials are PowerShell-centric, which may alienate users on Linux or those preferring non-Windows tooling.
Recommendations
- Include Azure CLI examples for managing API Management within Azure Automation.
- Provide Bash or Python script samples for automation tasks, highlighting cross-platform compatibility.
- Mention and link to documentation for running non-PowerShell runbooks in Azure Automation (e.g., Python, Bash).
- Ensure that tutorials and samples are available for both Windows and Linux users, with clear instructions for each environment.
- Explicitly state the cross-platform capabilities of Azure Automation and how users on Linux can leverage them.
API Management
Azure API Management - API version retirements (June 2024) | Microsoft Docs
...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 page demonstrates a Windows bias by listing Azure PowerShell (a Windows-centric tool) alongside Azure CLI, and providing PowerShell-specific commands and update instructions before mentioning cross-platform alternatives. The 'Update your tools' section gives detailed PowerShell instructions but does not offer equivalent Linux shell (bash/zsh) examples, nor does it mention Linux package managers for CLI updates. The Azure portal instructions assume a GUI workflow, which is more common on Windows. No explicit Linux-specific guidance or examples are provided.
Recommendations
- Provide Linux shell (bash/zsh) equivalents for all PowerShell commands, especially for checking and updating Azure CLI and SDKs.
- Mention Linux package managers (e.g., apt, yum, snap) for updating Azure CLI, in addition to the 'az upgrade' command.
- Clarify that Azure CLI is cross-platform and provide platform-specific instructions for both Windows and Linux.
- Include examples of using REST API calls with curl or httpie, which are common on Linux, for programmatic updates.
- Add notes or sections addressing common Linux workflows and tools, ensuring parity with Windows instructions.
API Management
Manage Connections for End Users - Azure API Management | Microsoft Docs
...es/api-management/credentials-how-to-user-delegated.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell instructions for provisioning the service principal, without mentioning or providing equivalent steps for Linux or cross-platform environments (e.g., Azure CLI, Bash). The use of PowerShell-specific modules and commands assumes a Windows environment and omits guidance for users on Linux or macOS. Additionally, the prerequisites and step-by-step instructions prioritize Windows tools and do not offer parity for Linux users.
Recommendations
- Add equivalent instructions using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
- Explicitly mention that Azure PowerShell commands can be run on Linux/macOS if PowerShell Core is installed, or provide installation guidance.
- Provide Bash or shell script examples for common tasks, such as service principal creation and authentication.
- Include notes or links to documentation for Linux/macOS users, ensuring all steps can be completed regardless of OS.
- Review and update screenshots and UI references to clarify any OS-specific differences.
API Management
Developer portal - Frequently asked questions
...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 bias toward Windows environments, primarily through the exclusive use of PowerShell scripts for permission management and the use of a .bat script for cleanup operations. There are no equivalent examples or instructions for Linux or cross-platform environments (e.g., Bash, Azure CLI), and Windows tools/scripts are mentioned without alternatives.
Recommendations
- Provide equivalent Bash/Azure CLI scripts for role creation and assignment, alongside PowerShell examples.
- Include instructions for running cleanup scripts on Linux/macOS (e.g., provide a .sh script or explain how to use the .bat file with Wine or convert it to Bash).
- Explicitly mention cross-platform compatibility for all scripts and tools, or provide links to platform-specific instructions.
- When referencing scripts or command-line tools, list Linux/macOS options before or alongside Windows/PowerShell options to avoid Windows-first bias.
API Management
Set up basic authentication to developer portal
...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 command-line tool for adding users, without providing equivalent Azure CLI or REST API examples that are platform-agnostic and commonly used on Linux/macOS. No Linux-specific instructions or parity examples are given for command-line operations.
Recommendations
- Include Azure CLI examples for adding users, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Mention REST API methods for user management, providing curl or HTTP request examples.
- Avoid referencing only PowerShell cmdlets when describing automation or scripting options; present alternatives first or alongside PowerShell.
- Explicitly state that all steps can be performed from any OS using Azure CLI or REST API, not just Windows/PowerShell.
- Add a section or note highlighting cross-platform tooling for managing API Management users.
API Management
Self-Host the API Management Developer Portal
.../articles/api-management/developer-portal-self-host.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: it references Windows Command Prompt and PowerShell first when discussing command shells, does not provide explicit Linux/macOS terminal examples or instructions, and omits Linux-specific guidance for Azure CLI authentication and file uploads. All command-line examples are generic but the narrative and instructions assume a Windows environment, potentially leaving Linux users without clear, platform-specific steps.
Recommendations
- Explicitly mention Linux and macOS terminal usage alongside Windows Command Prompt and PowerShell in all relevant steps.
- Provide Linux/macOS-specific instructions for Azure CLI authentication, file uploads, and any platform-dependent configuration steps.
- Include example commands for Linux/macOS shells (e.g., bash, zsh) where file paths or environment variables may differ.
- Clarify any differences in behavior or prerequisites for Linux users, such as package installation methods for Node.js, npm, and Azure CLI.
- Add troubleshooting tips for common Linux-specific issues (e.g., file permissions, CLI authentication).
API Management
Deploy a Self-Hosted Gateway to Azure Container Apps - Azure API Management
...nt/how-to-deploy-self-hosted-gateway-container-apps.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation consistently provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell (Windows) examples are always present and given equal prominence to Bash. There are no Linux-specific instructions or troubleshooting notes, and the use of PowerShell syntax may be confusing for Linux users. The documentation does not mention Linux tools or patterns, nor does it address platform-specific differences (e.g., file permissions, environment variable handling, shell differences).
Recommendations
- Add explicit Linux instructions or troubleshooting notes, especially for common issues (e.g., file permissions, shell differences, environment variable syntax).
- Provide examples using native Linux tools and patterns where relevant (e.g., systemd, networking commands, file operations).
- Clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows, and consider making Bash (Linux/macOS) examples the default or primary example, with PowerShell as an alternative.
- Include a section on platform-specific considerations, such as differences in CLI installation, environment variable syntax, and file system paths.
- Ensure parity in guidance for both Windows and Linux users, including troubleshooting, prerequisites, and verification steps.
API Management
Defend API Management Against DDoS Attacks
...rticles/api-management/protect-with-ddos-protection.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Azure portal (a GUI tool most commonly used on Windows), and linking to instructions for enabling DDoS IP Protection via PowerShell, without providing equivalent CLI or Linux-native examples. There are no Bash/Azure CLI instructions, and the workflow assumes use of Windows-centric tools and patterns.
Recommendations
- Add step-by-step instructions for enabling DDoS Protection using Azure CLI (az network vnet update, az network public-ip update) alongside PowerShell examples.
- Explicitly mention that the Azure portal is accessible from any OS, and provide links to CLI documentation for Linux/macOS users.
- Where PowerShell is referenced, also provide Bash/Azure CLI commands for parity.
- Review related links and ensure simulation/testing and telemetry guides include cross-platform tooling and examples.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...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 Portal, Azure CLI, and Azure PowerShell, with PowerShell (a Windows-centric tool) given equal prominence to Azure CLI. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is mentioned in prerequisites and example sections, despite being less commonly used on Linux. The CLI examples are generic and could apply to Linux, but the explicit inclusion and parity of PowerShell examples suggest a Windows bias. No Linux-specific tools, patterns, or troubleshooting are mentioned.
Recommendations
- Add explicit Bash shell examples for Azure CLI commands, showing usage in a typical Linux environment.
- Clarify that Azure CLI commands work cross-platform and provide notes or troubleshooting for Linux users (e.g., authentication, environment setup).
- De-emphasize PowerShell as a primary automation tool unless Linux PowerShell usage is specifically addressed.
- Include references to Linux-native tools or workflows where relevant (e.g., curl, jq for API manipulation).
- Ensure that prerequisites and setup instructions include Linux-specific guidance alongside Windows/PowerShell.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but the PowerShell example is given equal prominence and detail as the CLI example. PowerShell is a Windows-centric tool, and its inclusion alongside CLI (which is cross-platform) can signal a Windows bias, especially since there are no Linux-specific shell examples (e.g., Bash) or explicit mention of Linux environments. The prerequisites section lists both Azure CLI and Azure PowerShell, but does not clarify that CLI is cross-platform while PowerShell is traditionally Windows-first (though now available on Linux). There is no mention of Linux-specific considerations, nor are there examples using native Linux tools or shell environments.
Recommendations
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Add explicit Bash or shell examples for Linux users, demonstrating the same import process.
- Note that PowerShell is available on Linux, but is more commonly used on Windows; provide guidance for Linux users who may prefer Bash.
- Include a section or callout for Linux-specific setup or troubleshooting tips.
- Ensure that examples and instructions do not assume a Windows environment (e.g., file paths, tool availability).
API Management
Quickstart - Create Azure API Management instance - Terraform
...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 verification steps using Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. There are no explicit Linux shell examples (e.g., bash), and PowerShell is presented as an equal alternative to Azure CLI, despite CLI being cross-platform and PowerShell being primarily associated with Windows. The prerequisites mention Azure PowerShell requirements but do not clarify cross-platform usage or provide Linux-specific guidance. No Linux-specific tools or shell commands (such as bash, sh, or zsh) are mentioned, and the examples use variable assignment syntax that is ambiguous for Linux users.
Recommendations
- Add explicit bash/Linux shell examples for verification steps, using standard bash syntax.
- Clarify that Azure CLI is cross-platform and provide Linux/macOS installation instructions.
- If mentioning PowerShell, specify that it is available cross-platform, or provide guidance for Linux/macOS users.
- Include Linux-specific troubleshooting or environment preparation steps in the prerequisites.
- Ensure variable assignment examples use syntax compatible with both Windows (PowerShell) and Linux (bash), or provide both versions side-by-side.
API Management
Azure API Management policy reference - set-backend-service | Microsoft Docs
.../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 references PowerShell as a primary tool for managing backend entities, without mentioning Linux-native alternatives (such as Azure CLI or REST API usage from Bash). No Linux-specific examples or parity guidance are provided, and Windows/PowerShell tooling is mentioned before cross-platform options.
Recommendations
- Add explicit examples for managing backend entities using Azure CLI and REST API from Bash, highlighting cross-platform compatibility.
- Mention Azure CLI and REST API as first-class management options alongside PowerShell, not after or as secondary.
- Clarify that PowerShell is available on Linux, but also provide command-line examples using Bash and CLI for Linux users.
- Ensure all tooling references are balanced between Windows and Linux, and avoid implying PowerShell is the default or only supported method.
API Management
VNet configuration settings | Azure API Management
...n/articles/api-management/virtual-network-reference.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows Update Endpoints
Kms Windows Activation
Windows Defender Endpoints
Windows First
Summary
The documentation page exhibits a moderate Windows bias. Several sections specifically mention Windows-centric infrastructure and endpoints, such as Windows Update, Windows Defender, and KMS activation for Windows VMs. These requirements are detailed without equivalent mentions of Linux-specific needs (e.g., Linux update repositories, Linux security tools). Additionally, the KMS endpoint section is solely relevant to Windows, and Windows-related endpoints are listed before any Linux alternatives (which are absent). There are no Linux/Powershell command examples, but the overall focus on Windows infrastructure is evident.
Recommendations
- Add guidance for Linux VM scenarios, such as required outbound connectivity for popular Linux distributions' update repositories (e.g., Ubuntu, Red Hat, CentOS).
- Include information about security update endpoints for Linux (e.g., mirrors for apt, yum, zypper).
- Mention Linux-specific diagnostic and monitoring requirements if applicable.
- Clarify which sections are Windows-only and provide parity for Linux where possible.
- Review related content and links to ensure Linux administration and troubleshooting are covered alongside Windows.
API Management
Azure API Management virtual network injection - network resources
.../api-management/virtual-network-injection-resources.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page exhibits Windows bias primarily through its references to PowerShell for connecting virtual networks and the absence of Linux or cross-platform CLI examples. The related content section specifically highlights PowerShell-based guidance for VPN connectivity, and there are no equivalent instructions for Azure CLI, Bash, or Linux-native tools. This prioritizes Windows tooling and patterns, potentially making it less accessible for Linux users.
Recommendations
- Add equivalent Azure CLI and Bash examples alongside PowerShell instructions for all network configuration and connectivity scenarios.
- In related content, link to documentation that demonstrates how to connect virtual networks using Azure CLI and/or Linux tools, not just PowerShell.
- Where possible, use cross-platform language and avoid implying PowerShell is the default or only option.
- Explicitly mention that all operations can be performed from Linux, macOS, and Windows, and provide guidance for each.
- Review all referenced links and ensure Linux parity in example scripts and walkthroughs.
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 demonstrates a strong Windows bias by exclusively referencing Azure PowerShell cmdlets and PowerShell workflow scripts for managing Azure API Management with Azure Automation. There are no examples or mentions of Linux-friendly alternatives such as Azure CLI, Bash scripts, or cross-platform automation tools. The related content and samples further reinforce PowerShell as the primary method, omitting Linux or non-Windows approaches.
Recommendations
- Include examples using Azure CLI for API Management tasks within Azure Automation.
- Provide sample Bash or Python scripts that can be used in Azure Automation runbooks.
- Explicitly mention that Azure Automation supports multiple runbook types, including Python and graphical workflows, not just PowerShell.
- Add links to documentation or tutorials for managing Azure API Management with non-Windows tools.
- Present Windows and Linux automation options side-by-side to ensure parity and help users choose the best fit for their environment.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/how-to-deploy-self-hosted-gateway-azure-kubernetes-service.md
...to-deploy-self-hosted-gateway-azure-kubernetes-service.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates Windows bias by listing Azure PowerShell as a primary method for creating an AKS cluster alongside Azure CLI and Azure portal, with PowerShell mentioned before Linux-native alternatives. There are no explicit Linux shell examples or references to Linux-specific tools or workflows. The deployment instructions assume a generic terminal but do not clarify cross-platform differences, and the prerequisites section emphasizes Windows-centric tooling.
Recommendations
- List Linux-native tools (e.g., Bash, Linux terminal) explicitly alongside PowerShell and Azure CLI in the prerequisites.
- Provide example commands for both Windows (PowerShell) and Linux (Bash) environments where relevant.
- Clarify that Azure CLI works cross-platform and provide links or notes for Linux installation and usage.
- Ensure that instructions and screenshots (if any) do not assume Windows-only environments.
- Add notes or sections for Linux users, including troubleshooting tips and environment setup guidance.
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 exclusively mentioning the PowerShell command (`New-AzApiManagementSystemCertificate`) for uploading CA certificates, without providing equivalent CLI or Linux-native examples. Windows tools and patterns are referenced, and no Linux or cross-platform alternatives (such as Azure CLI, Bash, or REST API examples) are provided. The PowerShell method is called out in a note, reinforcing Windows-first guidance.
Recommendations
- Add Azure CLI examples for uploading and managing CA certificates, ensuring parity with PowerShell instructions.
- Include REST API sample calls for certificate management, which are platform-agnostic.
- Provide Bash or shell script snippets for Linux users where appropriate.
- Explicitly mention cross-platform options and clarify that PowerShell Core is available on Linux, if relevant.
- Reorder or balance examples so that Windows and Linux methods are presented equally, avoiding Windows-first ordering.
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 page demonstrates a Windows bias by presenting PowerShell examples first in each backup/restore section, providing detailed variable setup and usage for PowerShell, and referencing Azure PowerShell as a primary tool. While Azure CLI (Bash) and REST API examples are included, PowerShell is consistently prioritized and described in greater detail, reflecting a preference for Windows-centric tooling and workflows. There are no Linux-specific shell or scripting examples beyond generic Azure CLI usage, and no mention of Linux-native tools or patterns.
Recommendations
- Alternate the order of examples so that Azure CLI (Bash) is presented before PowerShell in some sections, or present both side-by-side.
- Provide equal detail and variable setup for Azure CLI/Bash examples as is given for PowerShell.
- Explicitly mention that Azure CLI and REST API workflows are cross-platform and suitable for Linux and macOS users.
- Include troubleshooting notes or tips for Linux environments, such as permissions, shell differences, or storage access patterns.
- Reference Linux-native scripting (e.g., Bash scripts) for automation, and provide sample scripts for backup/restore operations.
- Avoid language that implies PowerShell is the default or preferred method unless justified by feature parity.