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 26-50 of 594 flagged pages
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 equivalents. Windows/PowerShell instructions are given before any cross-platform alternatives, and there is no guidance for Linux or macOS users. The use of PowerShell and references to Windows-centric tools and patterns are prevalent throughout the page.
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.
- Explicitly mention that both PowerShell and Azure CLI can be used, and provide links to installation guides for each.
- Include Bash script samples where appropriate, especially for ARM template deployments and resource management.
- Reorder sections so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell, to avoid Windows-first bias.
- Add notes or tables comparing PowerShell and CLI usage for common tasks, helping users choose the best tool for their environment.
- Ensure screenshots and UI references are not Windows-specific, or clarify when steps are identical across platforms.
Create Pull Request
API Management
How to use role-based access control in Azure API Management | Microsoft Docs
...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 role creation and assignment, referencing PowerShell before Azure CLI and REST API, and omitting equivalent Linux/bash or cross-platform CLI examples. The use of PowerShell-centric tooling and lack of explicit Linux instructions may hinder Linux users or those preferring non-Windows environments.
Recommendations
- Add Azure CLI examples for all PowerShell code snippets, especially for custom role creation and assignment.
- Present Azure CLI and REST API options alongside PowerShell, or even before PowerShell, to emphasize cross-platform support.
- Explicitly mention that Azure CLI and REST API are cross-platform and suitable for Linux/macOS users.
- Include bash script examples where appropriate.
- Review and update references to tools and workflows to ensure parity between Windows and Linux environments.
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 demonstrates a strong Windows bias. All code examples use Azure PowerShell, with no mention of Azure CLI, Bash, or Linux-native tools. File paths and certificate handling are shown in Windows format (e.g., C:\Users\Contoso\), and there are no Linux or cross-platform alternatives for variable setup, resource creation, or certificate management. The prerequisites explicitly require Azure PowerShell, and the workflow assumes a Windows environment throughout. There are no Linux-specific instructions, nor is there guidance for users on macOS or Linux.
Recommendations
- Provide equivalent Azure CLI (az) examples alongside PowerShell for all resource creation and configuration steps.
- Include Linux/macOS file path examples and guidance for certificate management (e.g., using OpenSSL, Linux file paths).
- Add a prerequisites section for Linux/macOS users, including installation of Azure CLI and relevant tools.
- Where PowerShell is used for variable assignment or scripting, show Bash alternatives.
- Explicitly state that the process is cross-platform and highlight any differences or considerations for Linux/macOS users.
- Reference documentation for both Azure PowerShell and Azure CLI, and link to platform-specific quickstarts.
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 by providing only Azure PowerShell examples for command-line logger creation, without any equivalent examples for Linux-native tools such as Azure CLI, Bash, or cross-platform scripting. The PowerShell example is the only command-line method shown, and it is presented before infrastructure-as-code options (Bicep, ARM). There is no mention of Linux shell usage, nor are Linux-specific instructions or examples provided. The documentation also references Windows-centric tools (PowerShell) exclusively for scripting, which may alienate Linux users or those working in cross-platform environments.
Recommendations
- Add Azure CLI examples for logger creation and management, demonstrating equivalent functionality to the PowerShell cmdlets.
- Include Bash script snippets for common tasks, such as creating loggers or configuring connections, to support Linux users.
- Explicitly mention that all REST API and infrastructure-as-code examples (Bicep, ARM) are cross-platform and can be used from Linux, macOS, or Windows.
- Reorder examples so that cross-platform methods (REST API, Azure CLI) are presented before or alongside PowerShell, rather than PowerShell-first.
- Add a note clarifying that PowerShell is available on Linux and macOS, but provide CLI alternatives for users who prefer native Linux tools.
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
Windows First
Summary
The documentation page demonstrates a bias towards Windows by providing only PowerShell examples for backend configuration and certificate management, referencing Windows-centric tools (PowerShell cmdlets), and omitting equivalent Linux/Unix shell or CLI examples. There is no mention of Linux-specific workflows, such as using Azure CLI or Bash scripts, and Windows tools are introduced before any cross-platform alternatives.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlet instructions, especially for disabling certificate chain validation and managing backends.
- Include Bash or shell script snippets for certificate management tasks, demonstrating how Linux users can interact with Azure API Management.
- Reference cross-platform tools (such as Azure CLI) before or alongside Windows-specific tools like PowerShell.
- Explicitly state that all operations can be performed on Linux/macOS as well as Windows, and provide links to platform-agnostic documentation.
- Where screenshots or UI instructions are given, clarify any platform-specific differences or limitations.
API Management
Revisions in Azure API Management | Microsoft Docs
...in/articles/api-management/api-management-revisions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell cmdlets (e.g., New-AzApiManagementApiRelease, Update-AzApiManagementApiRelease) as the only CLI automation examples, with no mention of equivalent Azure CLI or REST API commands that are cross-platform. There are no Linux-specific or cross-platform command-line examples, and the only automation tooling mentioned is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlets mentioned, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include REST API examples for managing revisions, which are platform-agnostic.
- When referencing automation, mention both PowerShell and Azure CLI options, and present them in parallel or with equal prominence.
- Explicitly state that PowerShell Core is available cross-platform if PowerShell examples are retained, but still provide CLI/REST alternatives.
- Consider a 'Platform parity' note or table summarizing how to perform each action in Azure Portal, PowerShell, Azure CLI, and REST API.
API Management
Subscriptions in Azure API Management | Microsoft Docs
...rticles/api-management/api-management-subscriptions.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation references Azure PowerShell as a tool for automating subscription key lifecycle management, but does not mention or provide parity for Linux-native tools or CLI alternatives. There are no examples or instructions for managing subscriptions using cross-platform tools like Azure CLI, Bash scripts, or REST API calls from Linux environments. This creates a subtle bias toward Windows and PowerShell-centric workflows.
Recommendations
- Explicitly mention Azure CLI as an alternative to Azure PowerShell for automating subscription key management and provide example commands.
- Include REST API examples using curl or httpie, which are common on Linux and macOS, for subscription creation and key management.
- Avoid referencing only Windows-specific tools (such as PowerShell) when describing automation options; always provide cross-platform alternatives.
- Add a section or note clarifying that all management operations can be performed from Linux, macOS, and Windows using Azure CLI, REST API, or SDKs.
- Where possible, present examples in a platform-neutral order (e.g., Azure CLI before PowerShell, or both together) to avoid implicit prioritization.
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 examples for token generation and API calls, without offering equivalent Linux-friendly alternatives (such as Bash/cURL). The troubleshooting and configuration steps are centered around the Azure Portal, which is most commonly accessed on Windows, and there is no mention of Linux command-line tools or workflows. The inclusion of PowerShell scripts as the only code samples further reinforces the Windows-centric approach.
Recommendations
- Add Linux-friendly examples using Bash and cURL for token generation and API calls, alongside the PowerShell scripts.
- Explicitly mention that the Azure Portal is accessible from any OS/browser, and provide CLI alternatives (e.g., Azure CLI commands) for key configuration steps.
- Include notes or sections for developers using macOS or Linux, highlighting any differences or additional steps required.
- Ensure troubleshooting and related content reference cross-platform tools and workflows, not just those familiar to Windows users.
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
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell before Linux-friendly alternatives, providing only PowerShell commands for version checks and upgrades, and referencing Windows-centric tools (PowerShell, Azure portal) without offering equivalent Linux shell examples (e.g., Bash). There are no explicit Linux command-line examples for checking/updating Azure CLI or SDKs, and the guidance for programmatic changes focuses on PowerShell and the Azure portal, both of which are more familiar to Windows users.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell commands, especially for checking/updating Azure CLI and SDKs.
- Mention cross-platform tools (e.g., Azure CLI) before Windows-specific ones (e.g., PowerShell) when listing options.
- Include instructions for updating modules/packages using Linux package managers (apt, yum, Homebrew) where relevant.
- Clarify that Azure CLI and Terraform are cross-platform and provide examples for both Windows and Linux environments.
- Add explicit Linux/macOS instructions for setting the Minimum API version programmatically (e.g., using curl with REST API, az CLI in Bash).
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 bias towards Windows by exclusively mentioning the Azure PowerShell cmdlet (New-AzApiManagementUser) as the CLI tool for adding users, without reference to cross-platform alternatives such as Azure CLI or REST API. No Linux-specific or platform-neutral examples are provided for user management, and the only automation example is Windows-centric.
Recommendations
- Include Azure CLI examples for adding users, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Mention REST API methods for user management, providing platform-neutral automation options.
- Clarify that PowerShell is available on Linux and macOS, but also provide instructions for installing and using it on those platforms, or suggest alternatives.
- Ensure that automation and scripting examples are presented in a platform-neutral order, or provide both Windows and Linux/macOS alternatives side by side.
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
Summary
The documentation page exclusively references Azure PowerShell cmdlets and workflow scripts for managing Azure API Management via Azure Automation. All examples and tutorials are PowerShell-based, with no mention of Bash, Azure CLI, or Linux-native automation approaches. This creates a Windows-centric bias and may exclude or discourage Linux users.
Recommendations
- Add examples using Azure CLI for API Management tasks within Azure Automation.
- Include Bash script samples and guidance for Linux-based automation scenarios.
- Mention cross-platform compatibility of Azure Automation and clarify that runbooks can be authored in Python or Bash, not just PowerShell.
- Provide links to Linux-focused tutorials or documentation for Azure Automation.
- Ensure that references to PowerShell are balanced with equivalent Linux tooling and scripting options.
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 exclusively providing Azure PowerShell commands for service principal provisioning, without mentioning or providing equivalent Linux/macOS-friendly alternatives (such as Azure CLI or Bash scripts). The only command-line tooling referenced is PowerShell, and installation instructions assume a Windows environment. No Linux-specific instructions or examples are given, and the use of PowerShell is presented as the default and only option for automation.
Recommendations
- Add equivalent Azure CLI commands for service principal provisioning, which work cross-platform (Linux, macOS, Windows).
- Include Bash script examples for steps that require scripting, or clarify that the steps can be performed in Bash/Terminal environments.
- Explicitly mention that all steps can be performed on Linux/macOS, and provide links or instructions for non-Windows environments.
- When listing prerequisites, clarify that PowerShell is not required and offer alternatives for Linux users.
- Where PowerShell modules are referenced, note that Azure CLI is available and provide installation instructions for Linux/macOS.
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
Windows First
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 Windows batch scripts (.bat) for cleanup operations. No equivalent Linux/bash examples are provided, and Windows-centric tools and patterns (PowerShell, .bat files) are mentioned without alternatives or parity for Linux users. This may hinder accessibility for developers working on Linux or macOS platforms.
Recommendations
- Provide bash or Azure CLI equivalents for all PowerShell scripts, especially for role assignment and management tasks.
- Include instructions for running cleanup operations using shell scripts (.sh) for Linux/macOS environments, or document how to use the .bat script via cross-platform tools.
- When referencing scripts or tools, mention both Windows and Linux options, or clarify platform requirements and alternatives.
- Consider reordering examples so that cross-platform or Linux options are presented alongside or before Windows-specific instructions.
- Add notes or links to platform-specific documentation where appropriate.
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 page demonstrates a Windows bias in several areas. In Step 6, users are instructed to 'Open Windows Command Prompt, PowerShell, or other command shell,' listing Windows shells first and not providing explicit Linux/macOS terminal instructions or examples. There are no Linux-specific examples or guidance for uploading files, and the use of Azure CLI is described generically without clarifying cross-platform usage. The documentation does not provide parity for Linux users in terms of shell commands, environment setup, or troubleshooting.
Recommendations
- Explicitly mention Linux/macOS terminals (e.g., Bash, zsh) alongside Windows shells when instructing users to open a command shell.
- Provide Linux/macOS-specific examples for Azure CLI commands, including any differences in quoting, environment variables, or file paths.
- Add troubleshooting notes or tips for common issues encountered on Linux/macOS (e.g., file permissions, npm/node compatibility).
- Ensure that all steps referencing command shells or tools are platform-neutral or include both Windows and Linux/macOS instructions.
- Where GUI instructions are given for Azure Portal, clarify that the steps are the same regardless of OS, and provide CLI alternatives where possible.
API Management
Add a GraphQL API to Azure API Management | Microsoft Docs
...-docs/blob/main/articles/api-management/graphql-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 GraphQL API, but PowerShell is given equal prominence as CLI, and PowerShell is a Windows-centric tool. The prerequisites section lists Azure PowerShell immediately after Azure CLI, and the PowerShell example is presented in full detail. There is no explicit mention of Linux-specific tools or shell environments (e.g., Bash), nor are there examples tailored for Linux users. The documentation assumes familiarity with PowerShell, which is traditionally a Windows-first technology, and does not clarify cross-platform usage or provide parity for Linux-native workflows.
Recommendations
- Explicitly state that Azure CLI works natively on Linux, macOS, and Windows, and provide Bash-specific examples where appropriate.
- Clarify that PowerShell Core is cross-platform, but note that most Linux users will prefer Bash/CLI workflows.
- Add a section or note for Linux users, highlighting any differences in environment setup or command usage.
- Consider providing examples using Bash scripts or referencing Linux package managers for installing Azure CLI.
- Ensure that CLI examples are presented first, as CLI is the most cross-platform tool, and clarify that PowerShell is optional and primarily for users who prefer it.
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 CLI and Azure PowerShell, with PowerShell (a Windows-centric tool) given equal prominence to the CLI. There are no Linux-specific shell examples (e.g., Bash), nor are Linux-native tools or workflows mentioned. The prerequisites and examples focus on Azure PowerShell, which is most commonly used on Windows, and do not discuss Linux environments or alternatives. The ordering of examples (Portal, CLI, PowerShell) does not explicitly favor Windows, but the inclusion and detail of PowerShell content reflects a Windows bias.
Recommendations
- Add explicit Bash shell examples for Azure CLI usage, demonstrating commands in a Linux terminal.
- Clarify that Azure CLI works cross-platform and provide instructions for installing and running it on Linux and macOS.
- Mention that Azure PowerShell is available on Linux and macOS, or provide parity examples using Bash or other Linux-native tools.
- Include troubleshooting or environment setup notes for Linux users, such as file path conventions and authentication differences.
- Consider reordering examples or providing tabs for 'Windows', 'Linux', and 'macOS' to emphasize cross-platform support.
API Management
Defend API Management Against DDoS Attacks
...rticles/api-management/protect-with-ddos-protection.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, typically accessed from Windows environments) as the primary method for enabling DDoS protection. Additionally, the only command-line example provided for enabling DDoS IP Protection refers to a PowerShell-based guide, with no mention of Azure CLI or Bash alternatives. There are no Linux-specific instructions or examples, and Windows-centric tools and patterns are mentioned exclusively or first.
Recommendations
- Include Azure CLI and Bash examples alongside PowerShell instructions for enabling DDoS protection on public IP addresses.
- Explicitly mention that the Azure portal can be accessed from any OS and provide parity in instructions for Linux/macOS users.
- Add a section or links for Linux users detailing how to perform the same operations using cross-platform tools.
- Ensure that all command-line references are available in both PowerShell and Azure CLI formats, with equal prominence.
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
Windows First
Powershell Heavy
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 is included as a primary method. PowerShell is a Windows-centric tool, and its inclusion alongside CLI (which is cross-platform) can signal a Windows bias. There are no explicit Linux-specific instructions, nor is there mention of Linux shell alternatives (e.g., Bash scripts). The prerequisites section lists both Azure CLI and Azure PowerShell, but does not clarify platform differences or recommend CLI for Linux users. The documentation does not provide any Linux-specific troubleshooting, nor does it mention running PowerShell Core on Linux.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows (or PowerShell Core for Linux/macOS).
- Add explicit instructions or notes for Linux users, such as using Bash or running CLI commands in a Linux shell.
- If PowerShell examples are included, mention that PowerShell Core is available for Linux/macOS and provide installation links.
- Consider providing Bash script equivalents for common tasks, or at least mention that Azure CLI commands can be run in Bash.
- In the prerequisites, specify platform recommendations (e.g., 'Use Azure CLI on Linux/macOS, PowerShell on Windows').
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 both Azure CLI and Azure PowerShell instructions for verifying results, but PowerShell is a Windows-centric tool and is presented as a primary option alongside Azure CLI. There are no explicit Linux shell examples (e.g., bash), and prerequisites mention Azure PowerShell requirements before any Linux-specific alternatives. The examples for setting variables use syntax that is compatible with bash (CLI) and PowerShell, but no explicit Linux shell or cross-platform notes are given. There is a slight Windows bias in tool selection and ordering.
Recommendations
- Add explicit bash/Linux shell examples for all CLI commands, including variable assignment and command execution.
- Clarify that Azure CLI works cross-platform and provide notes or examples for Linux/macOS users.
- Reorder instructions to present Azure CLI (cross-platform) before Azure PowerShell (Windows-centric), or clearly label PowerShell as Windows-specific.
- Include troubleshooting or setup notes for Linux environments, such as package installation or environment configuration.
- Review included prerequisite content to ensure Linux and macOS users are equally supported and addressed.
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
Windows Defender Endpoints
Kms Windows Vm
Windows First
Summary
The documentation page displays a moderate Windows bias. Several sections and examples reference Windows-specific infrastructure, endpoints, and tools (such as KMS activation, Windows Update, and Windows Defender), without mentioning Linux equivalents or requirements. The only explicit mention of operating system-specific configuration is for Windows VMs (KMS endpoint), and diagnostic endpoints are Windows-centric. No Linux-specific endpoints, tools, or troubleshooting patterns are discussed, and Windows endpoints are listed first and exclusively in relevant sections.
Recommendations
- Add guidance for Linux VM activation and licensing if applicable, or clarify that no equivalent is needed.
- Include information about Linux-specific update mechanisms (e.g., outbound connectivity for apt/yum repositories) if API Management instances or supporting infrastructure may run on Linux.
- Mention Linux security and diagnostic endpoints or clarify that only Windows endpoints are required.
- Where Windows-specific endpoints (e.g., Windows Update, Defender) are listed, explicitly state whether these are only needed for Windows-based infrastructure, and provide parity notes for Linux.
- Review related content and examples to ensure Linux administration tools and patterns (such as Bash, CLI, or Linux firewall configuration) are referenced alongside PowerShell or Windows-centric documentation.
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 and does not mention or provide examples for Linux-native tools (such as Azure CLI or Bash). There are no Linux-specific management instructions or parity in example tooling, and PowerShell is mentioned before any cross-platform alternatives.
Recommendations
- Include Azure CLI commands and examples for managing backend entities alongside PowerShell references.
- Explicitly mention that backend management can be performed from Linux/macOS using Azure CLI or REST API, not just PowerShell.
- Provide example scripts or command lines for Linux environments (e.g., Bash, Azure CLI) in addition to or before PowerShell.
- Clarify that PowerShell is available cross-platform, but highlight native Linux approaches to avoid Windows-centric perception.
API Management
Add a Custom CA Certificate - API Management | Microsoft Docs
...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 page demonstrates Windows bias by exclusively mentioning the PowerShell command (`New-AzApiManagementSystemCertificate`) as the CLI method 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 shown is PowerShell, a Windows-centric tool, and there is no mention of Linux-native tools or cross-platform alternatives in the main workflow.
Recommendations
- Add Azure CLI examples for uploading and managing CA certificates, which are cross-platform and widely used on Linux.
- Include REST API examples for certificate management, as these are platform-agnostic.
- Explicitly mention Linux workflows and tools where applicable, such as using Bash scripts or OpenSSL for certificate handling.
- Ensure that automation examples are provided for both Windows (PowerShell) and Linux (Azure CLI/Bash), and present them side-by-side or in parallel sections.
- Review other documentation pages for similar bias and update them to improve parity.
API Management
How to use role-based access control in Azure API Management | Microsoft Docs
...management/api-management-role-based-access-control.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing only PowerShell examples for custom role creation and assignment, referencing Azure PowerShell before Azure CLI and REST API, and omitting equivalent Linux/bash or cross-platform CLI examples. The use of PowerShell as the sole code sample assumes a Windows environment and may exclude Linux/macOS users or those who prefer bash scripting.
Recommendations
- Add Azure CLI examples for all PowerShell code snippets, especially for custom role creation and assignment.
- Explicitly mention that both PowerShell and Azure CLI are supported on Windows, Linux, and macOS, and provide links to cross-platform installation guides.
- Present Azure CLI and REST API options alongside PowerShell, not after or as secondary tools.
- Include bash script examples where appropriate, or clarify how Linux/macOS users can perform the same tasks.
- Review documentation for other places where Windows-centric tools or terminology are used and ensure Linux parity.
API Management
Revisions in Azure API Management | Microsoft Docs
...in/articles/api-management/api-management-revisions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively mentioning PowerShell cmdlets (e.g., New-AzApiManagementApiRelease, Update-AzApiManagementApiRelease) for command-line operations, without providing equivalent examples for Linux users (such as Azure CLI or REST API). The only tooling referenced for automation is PowerShell, which is primarily associated with Windows environments.
Recommendations
- Add Azure CLI examples for all operations currently described with PowerShell cmdlets.
- Reference REST API endpoints for revision management, enabling cross-platform automation.
- Explicitly mention that PowerShell is available on Linux and macOS, but provide parity with CLI and REST for users who prefer those tools.
- Ensure that examples and instructions are not Windows-centric and provide equal visibility to Linux-compatible tools.
API Management
Backup and restore your Azure API Management instance for disaster recovery
...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 moderate Windows bias. PowerShell examples are presented first and in greater detail, with explicit variable setup and multiple authentication scenarios. The use of Azure PowerShell cmdlets is emphasized throughout, and the prerequisites section specifically calls out installing Azure PowerShell. While Azure CLI (Bash) and REST API examples are provided, they are generally listed after PowerShell, and there is no mention of Linux-specific tools or shell environments beyond Bash. There are no examples using native Linux utilities or scripting languages (e.g., Python, curl), and the documentation does not address platform-specific nuances or troubleshooting for Linux users.
Recommendations
- Present CLI (Bash) examples before or alongside PowerShell to avoid Windows-first ordering.
- Expand Bash/CLI sections to include more detailed variable setup and authentication scenarios, matching the depth of PowerShell examples.
- Include examples using native Linux tools (e.g., curl for REST API calls, Python scripts) to demonstrate parity for Linux users.
- Add troubleshooting notes or tips specific to Linux environments (e.g., permissions, environment variables, shell differences).
- Clarify that Azure PowerShell is cross-platform and provide installation instructions for Linux/macOS alongside Windows.
- Consider referencing or linking to Linux-specific documentation or community resources for Azure API Management backup/restore.