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 26-50 of 112 flagged pages
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/secure-mcp-servers.md
...lob/main/articles/api-management/secure-mcp-servers.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Visual Studio Code (a Microsoft tool popular on Windows) as the primary example for client configuration and secure key management. No Linux-specific tools, shells, or configuration examples are provided, and there is no mention of Linux command-line usage or alternative editors. The only client-side tool mentioned is Visual Studio Code, and the documentation does not address Linux-first or cross-platform workflows.
Recommendations
- Include Linux-native examples, such as using curl or httpie for API requests with authentication headers.
- Mention and provide examples for configuring MCP server access using common Linux editors (e.g., Vim, nano) or configuration files.
- Add guidance for managing secrets and environment variables securely on Linux (e.g., using .env files, gnome-keyring, or pass).
- Clarify that Visual Studio Code is cross-platform, or provide alternative instructions for Linux users.
- Where possible, provide shell script or command-line examples (bash/zsh) for Linux users alongside any Windows/PowerShell or Visual Studio Code instructions.
Create Pull Request
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 Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily through its references to Windows-centric tools and patterns. For example, the 'Related content' section links to a guide specifically about connecting virtual networks using PowerShell, a tool most commonly associated with Windows. There are no equivalent references to Linux-native tools (such as Azure CLI or Bash scripting), nor are there examples or guidance for Linux users. The documentation does not provide parity for Linux environments, and Windows/PowerShell tools are mentioned exclusively.
Recommendations
- Add equivalent Linux-focused examples and links, such as how to connect virtual networks using Azure CLI or Bash.
- Ensure that for every PowerShell or Windows tool reference, there is a corresponding Azure CLI or Linux-native command example.
- Update the 'Related content' section to include links to Linux/CLI-based guides, not just PowerShell.
- Explicitly mention that all operations can be performed from Linux environments using Azure CLI or REST APIs, and provide sample commands.
- Review the documentation for other implicit Windows-first assumptions and revise language to be platform-neutral where possible.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/virtual-network-workspaces-resources.md
...api-management/virtual-network-workspaces-resources.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates Windows bias primarily by referencing Windows paths before Linux equivalents (e.g., hosts file location), and by using screenshots and instructions that appear to be Azure Portal-centric (which often aligns with Windows workflows). There are no explicit Linux or cross-platform CLI examples (such as Azure CLI or Bash), and the only mention of Linux is secondary, in parentheses after the Windows path. There are no Linux-specific tools or commands provided.
Recommendations
- Provide explicit Linux and macOS examples alongside Windows, especially for common tasks like editing the hosts file.
- Include Azure CLI and Bash command examples for network configuration and resource management, not just portal-based instructions.
- When referencing file paths, list Linux/macOS paths first or equally, not only as a parenthetical after Windows.
- Add screenshots or instructions for cross-platform tools (e.g., Azure CLI, Bash) in addition to or instead of portal screenshots.
- Ensure that any PowerShell or Windows-specific instructions are matched with equivalent Linux/macOS command-line examples.
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 demonstrates a bias towards Windows and Azure-centric tools and workflows. It exclusively references Azure DevOps, Azure Pipelines, and Visual Studio Code, with no mention of Linux-specific tools, shell examples, or alternative CI/CD platforms commonly used in Linux environments (e.g., Jenkins, GitLab CI, or native bash scripting). The documentation assumes the use of Azure and Windows-oriented tools, and does not provide parity for Linux users in terms of examples or tool recommendations.
Recommendations
- Include examples and references for Linux-native tools and workflows, such as bash scripts for deployment, or using Jenkins/GitLab CI for CI/CD pipelines.
- Mention and provide examples for cross-platform CLI tools (e.g., Azure CLI) with explicit Linux usage instructions.
- Add alternative editor suggestions (e.g., Vim, Emacs, JetBrains IDEs) alongside Visual Studio Code.
- Provide explicit Linux shell command examples for common tasks (e.g., deploying ARM templates or using Terraform from bash).
- Reference and link to documentation for running Azure DevOps pipelines or GitHub Actions runners on Linux hosts.
- Balance the order of tool presentation, ensuring Linux-friendly options are mentioned alongside or before Windows-centric ones.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/developer-portal-self-host.md
.../articles/api-management/developer-portal-self-host.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits Windows bias in several ways: Windows tools and terminology (Command Prompt, PowerShell) are mentioned first and explicitly, while Linux equivalents are not described or are only implied. There are no explicit Linux shell examples or instructions for Linux-specific environments. The Azure CLI example is presented generically, but the context and instructions assume a Windows environment. The documentation lacks parity in step-by-step guidance for Linux users, such as using Bash or Linux-specific file paths and shell commands.
Recommendations
- Explicitly mention Linux and macOS as supported environments in prerequisites and steps.
- Provide Linux/Bash shell examples alongside Windows Command Prompt/PowerShell instructions.
- Use neutral terminology such as 'terminal' or 'command shell' instead of 'Windows Command Prompt, PowerShell'.
- Include notes or examples for Linux-specific Azure CLI installation and usage.
- Add troubleshooting tips for common Linux/macOS issues (e.g., permissions, path separators).
- Ensure all file paths and commands are cross-platform or provide platform-specific variants.
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides command-line examples for managing API Management multi-region deployments using Azure CLI and Azure PowerShell, but does not mention or provide examples for Linux/macOS shell environments or tools. PowerShell is referenced explicitly, and the Azure CLI examples use the 'azurecli' code block, but there is no discussion of shell differences or Linux-specific considerations. The order of tool mention often puts PowerShell before CLI, and no Bash or Linux-specific guidance is given.
Recommendations
- Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide Bash shell examples where appropriate.
- When referencing PowerShell, explicitly state that it is available on Linux/macOS, or provide equivalent Bash or shell commands for common tasks.
- Avoid listing PowerShell before CLI unless there is a technical reason; consider listing CLI first as it is more universally available.
- Add notes or links for Linux/macOS users regarding installation and usage of Azure CLI and PowerShell Core.
- Where screenshots or UI instructions are given, clarify if any steps differ for Linux/macOS users.
API Management
Use Managed Identities in Azure API Management | Microsoft Docs
...t/api-management-howto-use-managed-service-identity.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed examples for Azure PowerShell and the Azure Portal, both of which are most commonly used on Windows. There are no CLI (az) or Bash examples, nor any mention of Linux/macOS-specific workflows. PowerShell is featured as the only command-line automation method, and its installation instructions are referenced, which may be confusing or less accessible for Linux/macOS users. The ARM template examples are cross-platform, but the lack of Azure CLI or Bash scripting creates friction for non-Windows users.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell workflows, including creating and updating managed identities.
- Explicitly mention that Azure CLI and Bash can be used on Linux/macOS and provide links to relevant guides.
- Reorder sections so that cross-platform methods (ARM templates, Azure CLI) are presented before or alongside PowerShell.
- Clarify that PowerShell is available on Linux/macOS, but provide CLI alternatives for users who prefer native tools.
- Include notes or links for Linux/macOS users regarding prerequisites and environment setup.
API Management
Use Managed Identities in Azure API Management | Microsoft Docs
...t/api-management-howto-use-managed-service-identity.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed instructions and code samples for Azure PowerShell, which is primarily a Windows-centric tool, and does not offer equivalent examples for Azure CLI or bash scripts that are more commonly used on Linux/macOS. PowerShell instructions are presented before ARM template examples, and there are no Linux/macOS-specific guidance or parity for command-line operations.
Recommendations
- Add Azure CLI examples alongside or before PowerShell examples for all operations (creating, updating, and removing managed identities).
- Explicitly mention cross-platform tools and provide bash script samples where appropriate.
- Clarify that Azure PowerShell is available on Linux/macOS, but highlight Azure CLI as the preferred cross-platform option.
- Ensure that all step-by-step instructions are available for both PowerShell and CLI users.
- Consider reordering examples so that cross-platform solutions (CLI, ARM templates) appear before Windows-specific tools.
API Management
Secure API Management Backend Using Client Certificate Authentication
...management/api-management-howto-mutual-certificates.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for disabling certificate chain validation, referencing Windows-centric tools (PowerShell cmdlets), and omitting equivalent Linux/macOS CLI or scripting examples. The PowerShell approach is presented first and in detail, while alternatives for Linux users (such as Azure CLI or REST API usage) are not described or exemplified.
Recommendations
- Add Azure CLI examples for all tasks currently shown only with PowerShell, especially for disabling certificate chain validation.
- Explicitly mention and demonstrate how Linux/macOS users can perform the same operations, e.g., using Bash scripts or REST API calls.
- Where PowerShell is referenced, provide parity by showing equivalent commands for Azure CLI or other cross-platform tools.
- Avoid language that assumes PowerShell is the default or only method; clarify that multiple platforms are supported.
API Management
Set up basic authentication to developer portal
...pi-management/developer-portal-basic-authentication.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation references the Azure PowerShell cmdlet (New-AzApiManagementUser) as the only CLI tool for programmatically adding users, with no mention of Azure CLI, REST API, or cross-platform alternatives. This creates a bias toward Windows and PowerShell users, leaving Linux/macOS users without clear guidance for command-line automation.
Recommendations
- Add equivalent instructions and examples using Azure CLI (az apim user create) if available.
- Reference REST API methods for user management in Azure API Management.
- Clarify which tools are cross-platform and provide links to their documentation.
- Present cross-platform or Linux/macOS options before or alongside PowerShell examples.
API Management
Defend API Management Against DDoS Attacks
...rticles/api-management/protect-with-ddos-protection.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation references enabling DDoS IP Protection via a linked page that specifically mentions PowerShell, which is primarily a Windows tool. There are no explicit Linux or cross-platform CLI examples provided in the main content, and the only automation example is PowerShell-focused. This creates friction for Linux/macOS users who may prefer or require Azure CLI or other cross-platform tools.
Recommendations
- Add Azure CLI examples for enabling DDoS IP Protection on public IP addresses.
- Explicitly mention that PowerShell Core is available cross-platform, if PowerShell must be used.
- Provide parity in instructions for Linux/macOS users, including screenshots or terminal commands where appropriate.
- Link to documentation sections that use Bash or Azure CLI for equivalent tasks.
API Management
Add a Custom CA Certificate - API Management | Microsoft Docs
...api-management/api-management-howto-ca-certificates.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides a PowerShell command (New-AzApiManagementSystemCertificate) as the only CLI example for uploading a CA certificate, with no mention of Linux/macOS equivalents (such as Azure CLI or REST API usage). This creates a bias toward Windows users and may hinder Linux/macOS users who do not use PowerShell.
Recommendations
- Add Azure CLI examples for uploading CA certificates, which are cross-platform.
- Include REST API example calls for certificate upload, with sample curl commands.
- Explicitly mention that PowerShell is available on Linux/macOS, or provide installation guidance.
- Order examples so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell.
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
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a notable Windows bias, primarily by presenting PowerShell examples first and in greater detail, referencing Azure PowerShell cmdlets, and requiring users to install Azure PowerShell. While Azure CLI and REST examples are provided, PowerShell is emphasized and appears before cross-platform alternatives, which may create friction for Linux/macOS users who typically use Bash and Azure CLI.
Recommendations
- Present Azure CLI (Bash) examples before or alongside PowerShell examples to promote cross-platform parity.
- Expand CLI sections to match the detail and coverage of PowerShell sections, including managed identity scenarios.
- Explicitly state that Azure CLI and REST methods are fully supported on Linux/macOS, and provide troubleshooting tips for non-Windows environments.
- Add notes or links for installing and using Azure CLI on Linux/macOS.
- Where possible, avoid language that implies PowerShell is the default or preferred method.
API Management
Use API Management in a virtual network with Azure Application Gateway
...pi-management-howto-integrate-internal-vnet-appgateway.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell. All code examples use Azure PowerShell cmdlets, and file path examples use Windows-style paths (e.g., C:\Users\Contoso\). There are no CLI, Bash, or Linux/macOS-specific instructions or examples. The prerequisites explicitly require Azure PowerShell, with no mention of Azure CLI or cross-platform alternatives. This creates friction for Linux/macOS users who may prefer Bash, Azure CLI, or other tooling.
Recommendations
- Provide equivalent Azure CLI (az) examples for all resource creation and configuration steps.
- Use platform-neutral file path examples, or show both Windows and Linux/macOS variants.
- Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI or PowerShell Core, and link to relevant installation guides.
- Add notes or sections for Linux/macOS users, highlighting any differences (e.g., certificate handling, file paths).
- Reorder examples so that platform-neutral or cross-platform instructions appear before Windows-specific ones.
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
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias, primarily through the use of Azure PowerShell examples and references to PowerShell cmdlets as the only CLI-based example for creating loggers with connection strings. The PowerShell example is presented before any cross-platform alternatives, and no Bash, Azure CLI, or Linux/macOS-specific instructions are provided for these tasks. The rest of the documentation focuses on REST API, Bicep, and ARM templates, which are cross-platform, but the only imperative scripting example is Windows-centric.
Recommendations
- Add Azure CLI examples for creating loggers, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash or shell script snippets where appropriate, especially for tasks that can be automated outside PowerShell.
- Explicitly state that Bicep, ARM, and REST API methods are platform-agnostic and can be used on any OS.
- If PowerShell is mentioned, clarify that PowerShell Core is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
- Consider presenting Azure CLI or REST API examples before PowerShell to avoid implicit Windows-first ordering.
API Management
Use Managed Identities in Azure API Management | Microsoft Docs
...t/api-management-howto-use-managed-service-identity.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed instructions and code samples for Azure PowerShell, which is primarily a Windows-centric tool, and references installation steps for Azure PowerShell. There are no equivalent examples or instructions for Azure CLI, which is cross-platform and preferred by many Linux/macOS users. PowerShell examples are presented before ARM template examples, and no bash or Linux-native workflow is described.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, including resource group creation, managed identity assignment, and updates.
- Explicitly mention that Azure CLI is supported and provide installation links for Linux/macOS users.
- Where possible, show both PowerShell and CLI examples side-by-side, or use tabs to allow users to select their preferred environment.
- Clarify that ARM templates and portal instructions are platform-agnostic, but highlight CLI as a first-class option for automation on Linux/macOS.
API Management
Revisions in Azure API Management | Microsoft Docs
...in/articles/api-management/api-management-revisions.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation references PowerShell cmdlets (New-AzApiManagementApiRelease, Update-AzApiManagementApiRelease) for managing revisions, without mentioning equivalent CLI commands or REST API options. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer cross-platform tools. No Linux/macOS-specific examples or alternatives are provided.
Recommendations
- Include Azure CLI examples for revision management tasks alongside PowerShell examples.
- Reference REST API methods for revision operations to ensure platform neutrality.
- Explicitly note that PowerShell is available cross-platform, but provide instructions for installation on Linux/macOS if PowerShell usage is required.
- Present examples for both Windows (PowerShell) and Linux/macOS (CLI/REST) in parallel, or default to platform-neutral tools.
API Management
How to use role-based access control in Azure API Management | Microsoft Docs
...management/api-management-role-based-access-control.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for custom role creation and assignment, referencing Azure PowerShell in metadata and links, and not including equivalent Azure CLI or REST API examples. While Azure CLI and REST API are mentioned as alternative tools, practical guidance and code samples are exclusively PowerShell-based, which is most commonly used on Windows.
Recommendations
- Add Azure CLI examples for custom role creation and assignment, ensuring Linux/macOS users have direct guidance.
- Include REST API sample requests for role management tasks.
- Present CLI and REST API examples alongside PowerShell, or even before PowerShell, to demonstrate cross-platform parity.
- Review metadata and internal links to ensure they do not prioritize PowerShell over other cross-platform tools.
API Management
Securely Access Products and APIs - Microsoft Entra Applications - Azure API Management
...docs/blob/main/articles/api-management/applications.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides only Azure PowerShell examples for generating OAuth tokens and calling APIs, with no equivalent Linux/macOS shell (e.g., Bash/cURL) examples. The use of PowerShell is presented as the default and only method for scripting these tasks, which may create friction for Linux/macOS users who do not use PowerShell. Additionally, the documentation references the Azure portal UI, which is cross-platform, but the scripting and automation sections are Windows-centric.
Recommendations
- Add equivalent Bash/cURL examples for generating tokens and calling APIs, demonstrating how to perform these steps on Linux/macOS.
- Explicitly state that the PowerShell examples are for Windows and provide alternative instructions for Linux/macOS users.
- Where possible, use cross-platform tools (e.g., cURL, HTTPie) in examples, or provide both PowerShell and Bash/cURL versions side-by-side.
- Review the 'azure-powershell-requirements-no-header' include to ensure it does not imply PowerShell is required for all users.
API Management
Manage Azure API Management using Azure Automation
...les/api-management/automation-manage-api-management.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exclusively references Azure PowerShell cmdlets and PowerShell workflow scripts for managing Azure API Management with Azure Automation. No mention is made of Bash, Azure CLI, or Linux/macOS-compatible scripting approaches. All examples and tutorials linked are PowerShell-centric, which is most commonly associated with Windows environments.
Recommendations
- Include examples using Azure CLI for API Management tasks within Azure Automation.
- Provide Bash script samples for Linux/macOS users.
- Explicitly mention cross-platform compatibility of Azure Automation and PowerShell Core, if applicable.
- Add links to documentation or tutorials for managing Azure API Management using non-Windows tools.
- Present examples for both Windows and Linux/macOS environments, or clarify platform requirements.
API Management
Manage Connections for End Users - Azure API Management | Microsoft Docs
...es/api-management/credentials-how-to-user-delegated.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, especially in the initial provisioning steps. All command-line instructions for provisioning the Azure API Management Data Plane service principal are provided exclusively using Azure PowerShell and the AzureAD PowerShell module, which are Windows-centric tools. No equivalent Bash, Azure CLI, or cross-platform instructions are given. The documentation also introduces these Windows tools before any mention of alternatives, and does not acknowledge Linux/macOS workflows for these critical steps.
Recommendations
- Provide equivalent Azure CLI commands for service principal provisioning, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash shell examples alongside PowerShell, or at least reference that the steps can be performed on Linux/macOS using Azure CLI.
- Explicitly state platform requirements for PowerShell steps and offer alternatives for non-Windows users.
- Add a table or section comparing PowerShell and Azure CLI workflows for key steps.
API Management
Developer portal - Frequently asked questions
...b/main/articles/api-management/developer-portal-faq.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page contains a notable Windows bias in the permissions section, where only PowerShell scripts are provided for role creation and assignment, with no equivalent Bash, Azure CLI, or Linux/macOS instructions. Additionally, the cleanup script example references a Windows batch file (.bat) and uses Windows-style commands, without mentioning Linux alternatives. These omissions may create friction for Linux/macOS users attempting administrative tasks.
Recommendations
- Provide Azure CLI or Bash script equivalents for role creation and assignment, alongside PowerShell examples.
- Include instructions for running the cleanup script on Linux/macOS, such as a shell script (.sh) alternative or guidance on using the batch script with Wine or similar tools.
- Wherever scripts or commands are shown, present cross-platform options or clarify platform requirements.
- Explicitly mention platform compatibility for provided scripts and tools.
API Management
Azure API Management - API version retirements (June 2024) | Microsoft Docs
...nt/breaking-changes/api-version-retirement-sep-2023.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page shows moderate Windows bias. Azure PowerShell is mentioned and given explicit update instructions, while Linux/macOS equivalents (such as Bash scripting or platform-specific package managers) are not discussed. Azure CLI is covered, but PowerShell instructions appear before CLI instructions in some places, and no Linux-specific CLI installation or update guidance is provided. The use of Windows-centric tools and terminology (PowerShell, PSGallery) is present, and examples for updating tools are Windows-oriented.
Recommendations
- Include explicit instructions for updating Azure CLI and PowerShell modules on Linux/macOS, such as using apt, yum, or Homebrew.
- Provide Bash or shell script examples alongside PowerShell commands for checking/updating modules.
- Mention cross-platform compatibility for tools like Azure CLI and Terraform, and clarify any platform-specific steps.
- List CLI instructions before PowerShell, or present both together to avoid Windows-first ordering.
- Reference Linux/macOS package managers and installation methods in the 'More information' section.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Medium 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 PowerShell is given equal prominence to CLI and is listed as a prerequisite. PowerShell is a Windows-centric tool, and its inclusion as a primary method introduces Windows bias. There are no Linux-specific shell examples (e.g., bash), and PowerShell is mentioned before any Linux-native alternatives. The CLI example is cross-platform, but the presence and emphasis on PowerShell may create friction for Linux/macOS users.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommend it as the primary automation method for Linux/macOS users.
- Add explicit bash or shell script examples where appropriate, especially for tasks that could be performed outside of Azure CLI.
- Move PowerShell examples to a dedicated Windows section or clearly label them as Windows-specific.
- In the prerequisites, note that PowerShell is optional and primarily for Windows users, while Azure CLI is recommended for all platforms.
API Management
Quickstart - Create Azure API Management instance - Terraform
...b/main/articles/api-management/quickstart-terraform.md
Medium 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 examples included. While Azure CLI is cross-platform, PowerShell is primarily associated with Windows, and no explicit Linux/macOS shell examples (e.g., Bash) are provided. The order of presentation sometimes places Windows-centric tools (PowerShell) alongside or after CLI, but no Linux-specific instructions or troubleshooting are given.
Recommendations
- Add explicit Bash/Linux/macOS shell examples for verification and resource cleanup steps.
- Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide any OS-specific notes if needed.
- If PowerShell is shown, also show Bash equivalents for all commands.
- Include troubleshooting notes relevant to Linux/macOS environments.