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 301-325 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
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased toward Windows and PowerShell usage. All code examples use Azure PowerShell cmdlets, and file paths are shown in Windows format (e.g., C:\Users\Contoso\). There are no CLI (az), Bash, or Linux/macOS shell examples, nor any mention of cross-platform alternatives. This creates friction for Linux/macOS users, who must translate all steps to their environment.
Recommendations
- Provide equivalent Azure CLI (az) commands for all PowerShell examples.
- Show file path examples in both Windows and Linux/macOS formats, or use environment-agnostic variables.
- Explicitly mention that all steps can be performed on Linux/macOS and provide guidance for certificate handling and file locations on those platforms.
- Add Bash shell examples for connectivity verification (e.g., curl commands) and hosts file editing instructions for Linux/macOS.
- Include a note at the start clarifying platform support and linking to cross-platform setup guides.
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
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page shows a notable Windows bias in the tooling and examples provided. The only CLI example for creating a logger with a connection string uses Azure PowerShell, with no equivalent Azure CLI, Bash, or Linux-native example. PowerShell is a Windows-centric tool, and its mention is prioritized over cross-platform alternatives. While Bicep and ARM templates are cross-platform, the lack of Azure CLI or Bash scripting examples creates friction for Linux/macOS users. The REST API examples are labeled as 'PowerShell' tabs, further reinforcing the Windows-first approach.
Recommendations
- Add Azure CLI examples for creating and managing loggers, especially for connection string scenarios.
- Provide Bash or shell script snippets where appropriate.
- Clarify that Bicep and ARM templates are cross-platform and can be used from any OS.
- Avoid labeling REST API tabs as 'PowerShell' when the example is generic and not PowerShell-specific.
- Explicitly mention Linux/macOS compatibility for all tools and steps.
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 PowerShell-only examples for critical tasks (such as disabling certificate chain validation), referencing Windows-centric tools (PowerShell cmdlets), and omitting equivalent Linux/macOS command-line instructions (such as Azure CLI or REST API curl examples). The PowerShell approach is presented first and in detail, while the REST API alternative is mentioned only briefly, with no example. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer platform-agnostic tools.
Recommendations
- Add Azure CLI examples for all PowerShell cmdlet instructions, especially for disabling certificate chain validation.
- Provide REST API usage examples (e.g., curl commands) for tasks currently shown only with PowerShell.
- Explicitly mention cross-platform alternatives before or alongside Windows/PowerShell instructions.
- Clarify that PowerShell instructions are Windows-centric and offer guidance for Linux/macOS users.
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
Missing Linux Example
Windows Tools
Summary
The documentation page references PowerShell cmdlets (e.g., New-AzApiManagementApiRelease, Update-AzApiManagementApiRelease) as the only command-line automation examples for managing API revisions. There are no equivalent examples or mentions of Azure CLI, REST API, or other cross-platform tools, which creates friction for Linux/macOS users who may not use PowerShell.
Recommendations
- Add Azure CLI examples for revision management tasks alongside PowerShell examples.
- Reference REST API endpoints for revision operations to provide platform-neutral automation options.
- Explicitly mention that PowerShell is available cross-platform, but provide guidance for users who prefer native Linux/macOS tools.
- Ensure that all command-line instructions have Linux/macOS equivalents or alternatives.
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 command-line examples (e.g., Bash/cURL). Windows tools and patterns (PowerShell, Invoke-RestMethod) are used exclusively in code samples, and no Linux or cross-platform alternatives are mentioned. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native tools.
Recommendations
- Add equivalent Bash/cURL examples for generating tokens and calling APIs, showing how to use curl or httpie.
- Explicitly mention that the process can be performed on any OS and provide platform-agnostic instructions.
- Include notes or links to PowerShell Core (pwsh) for Linux/macOS users if PowerShell is required.
- Consider showing Linux/macOS examples before or alongside Windows/PowerShell examples to avoid implicit prioritization.
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 First
Missing Linux Example
Summary
The documentation page exclusively references Azure PowerShell cmdlets and PowerShell workflow scripts for managing Azure API Management via Azure Automation. There are no mentions of Bash, Azure CLI, or Linux/macOS-compatible automation approaches. All examples and tutorials are PowerShell-centric, which may create friction for Linux/macOS users who prefer or require non-PowerShell solutions.
Recommendations
- Add examples using Azure CLI and Bash scripts for managing Azure API Management in Azure Automation.
- Explicitly mention that Azure Automation supports Python and other runbook types, and provide links or examples.
- Clarify cross-platform compatibility of Azure Automation and its scripting options.
- Ensure tutorials and sample links include Linux/macOS-friendly options, not just PowerShell.
API Management
Subscriptions in Azure API Management | Microsoft Docs
...rticles/api-management/api-management-subscriptions.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation mentions Azure PowerShell as a tool for automating subscription key management workflows, but does not mention Linux/macOS equivalents (such as Azure CLI or REST API usage) or provide cross-platform examples. This creates a subtle bias toward Windows environments and tools, potentially leaving Linux/macOS users unclear about their options for automation.
Recommendations
- Mention Azure CLI and REST API as cross-platform alternatives to Azure PowerShell for automating subscription key management.
- Provide example commands for Azure CLI and/or REST API usage alongside PowerShell examples.
- Clarify that Azure PowerShell is available on Linux/macOS, but highlight CLI and REST API as fully cross-platform solutions.
- Ensure any automation or scripting recommendations include at least one example that works natively on Linux/macOS.
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-based alternative to the Azure portal for adding users, without mentioning or providing examples for Azure CLI or REST API methods, which are cross-platform and preferred by Linux/macOS users. This creates a subtle bias towards Windows environments and tools.
Recommendations
- Include equivalent Azure CLI commands for user management tasks, such as adding users to the developer portal.
- Reference REST API methods for user management, with example requests.
- Explicitly state that PowerShell is available cross-platform, but also provide non-PowerShell alternatives.
- Order examples so that cross-platform tools (Azure CLI, REST API) are mentioned before or alongside PowerShell.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Medium 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. While Azure CLI is cross-platform, PowerShell is primarily a Windows tool (though available on Linux/macOS), and its inclusion as a main method reflects a Windows-centric approach. The PowerShell example is given equal prominence to CLI, and no Linux/macOS-specific shell examples (e.g., bash, curl, etc.) are provided. Additionally, the documentation refers to Azure PowerShell requirements in the prerequisites, which may be less relevant for Linux/macOS users.
Recommendations
- Add explicit Linux/macOS shell examples (e.g., using curl or bash with Azure CLI) to demonstrate parity.
- Clarify that Azure CLI is fully cross-platform and highlight its usage for Linux/macOS users.
- Consider moving PowerShell examples to a separate section or after CLI examples to reduce perceived Windows-first bias.
- Include notes or links for installing and using Azure PowerShell on Linux/macOS, if its usage is required.
- Mention alternative tools or workflows that are common in Linux/macOS environments.
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 Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a notable Windows bias, especially in the initial provisioning steps. Azure PowerShell and the AzureAD module are used exclusively for service principal provisioning, with no mention of Linux/macOS alternatives (such as Azure CLI or cross-platform scripting). The only command-line examples are PowerShell-based, and the prerequisite section references Azure PowerShell requirements. No Linux or macOS-specific instructions or parity examples are provided, and Windows-centric tooling is presented first and exclusively.
Recommendations
- Provide equivalent Azure CLI commands for service principal provisioning, which work on Linux/macOS as well as Windows.
- Add notes or sections indicating how to complete each step on Linux/macOS, including installation and authentication instructions for Azure CLI.
- Where PowerShell is referenced, offer alternative cross-platform scripting options or clarify that Azure CLI is recommended for non-Windows users.
- Review all command-line examples and ensure Linux/macOS users are not blocked or forced to use Windows tools.
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 provides critical role assignment and permission management examples exclusively using PowerShell scripts and references to .bat scripts, which are Windows-centric. There are no equivalent CLI (az), Bash, or Linux/macOS instructions for these operations. This creates friction for Linux/macOS users who may not have access to PowerShell or .bat scripting environments.
Recommendations
- Provide Azure CLI (az) equivalents for role creation and assignment, as Azure CLI is cross-platform.
- Include Bash script examples alongside .bat scripts for cleanup operations.
- Explicitly mention that PowerShell Core is available on Linux/macOS, or link to relevant installation guides.
- Where possible, use REST API examples (with curl) for operations like role assignment and token generation.
- Order examples so that cross-platform solutions (CLI, REST) are presented before or alongside Windows-specific tools.
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 explicitly mentions PowerShell, which is primarily a Windows tool. There are no examples or instructions for Linux/macOS users (such as Azure CLI or Bash), nor is there mention of cross-platform alternatives. The main instructions focus on the Azure portal, which is platform-agnostic, but the only programmatic example is Windows-centric.
Recommendations
- Add Azure CLI and/or Bash examples for enabling DDoS IP Protection, alongside PowerShell.
- Explicitly mention cross-platform tools where possible, and provide parity in instructions.
- Clarify which steps are platform-agnostic (e.g., Azure portal) and which require OS-specific tools.
- Link to documentation pages that include Linux/macOS instructions, or update the referenced page to do so.
API Management
Azure API Management policy reference - set-backend-service | Microsoft Docs
.../articles/api-management/set-backend-service-policy.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page references Windows-centric tools (PowerShell) for backend entity management and lists PowerShell before any Linux/macOS alternatives. No Linux-specific tools or CLI examples are provided, and the only explicit tooling guidance is for PowerShell, which is primarily a Windows technology (despite recent cross-platform support). This may create friction for Linux/macOS users seeking parity in backend management workflows.
Recommendations
- Include Azure CLI examples for backend entity management, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Mention REST API usage with curl or similar Linux-native tools for backend management.
- Clarify that PowerShell is available cross-platform, but provide explicit Linux/macOS instructions or alternatives.
- List cross-platform tools (Azure CLI, REST API) before or alongside PowerShell to avoid Windows-first perception.
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 and is listed as a required prerequisite alongside CLI. PowerShell is a Windows-centric tool, and its inclusion as a primary method can signal a Windows bias. There are no Linux/macOS-specific instructions or notes, and PowerShell is mentioned before any Linux shell alternatives. The CLI example is cross-platform, but the documentation does not clarify this or offer parity notes for Linux/macOS users.
Recommendations
- Clarify that Azure CLI is fully cross-platform and can be used on Linux/macOS.
- De-emphasize PowerShell as a required prerequisite, or note that it is optional for non-Windows users.
- Add explicit instructions or notes for Linux/macOS users, e.g., how to install and use Azure CLI.
- Consider listing CLI examples before PowerShell examples to reduce perceived Windows-first bias.
- If PowerShell is mentioned, clarify that it is available on Linux/macOS, or provide Bash examples for parity.
API Management
Quickstart - Create Azure API Management Instance - ARM Template
...ain/articles/api-management/quickstart-arm-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation primarily demonstrates deployment using the Azure portal and mentions Azure PowerShell and Azure CLI as alternative methods, but does not provide any CLI or PowerShell examples. There is no explicit bias toward Windows tools, but the lack of command-line examples (especially for Azure CLI, which is cross-platform) means Linux/macOS users do not see parity in instructions. The portal-based workflow is platform-neutral, but CLI/automation users (often on Linux) are underserved.
Recommendations
- Add explicit Azure CLI deployment instructions and examples, as CLI is cross-platform and preferred by many Linux/macOS users.
- If mentioning Azure PowerShell, also provide equivalent Azure CLI commands, and present CLI examples before or alongside PowerShell.
- Include screenshots or terminal output for CLI usage on Linux/macOS.
- Clarify that all deployment methods (portal, CLI, PowerShell, REST) are supported on all major 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 and referenced. While Azure CLI is cross-platform, PowerShell is primarily a Windows tool (though available on Linux, it's less common in Linux workflows). There are no explicit Linux/macOS shell examples (e.g., bash scripts), and the order of presentation sometimes puts Windows-centric tools (PowerShell) on equal footing with CLI, potentially confusing Linux users. No Linux-specific troubleshooting or tool recommendations are provided.
Recommendations
- Add explicit bash/sh examples for verification and resource cleanup steps, demonstrating Linux-native workflows.
- Clarify that Azure CLI commands work on Linux/macOS and Windows, while PowerShell is optional and primarily for Windows users.
- Provide troubleshooting tips or links specific to Linux/macOS environments.
- Consider listing Azure CLI (cross-platform) examples before PowerShell (Windows-centric) in all sections.
- Mention that PowerShell Core is available on Linux/macOS, but is not required for most users.
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 notable 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/macOS-friendly CLI or scripting examples. This may create friction for users on non-Windows platforms who prefer or require bash, Azure CLI, or REST-based workflows.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell code snippets, especially for custom role creation and assignment.
- Present Azure CLI and REST API options alongside PowerShell, not after or as secondary references.
- Explicitly mention platform compatibility for each tool and example.
- Consider including bash scripts or REST API payloads for tasks currently only shown in PowerShell.
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 command-line tool for adding users, without mentioning cross-platform alternatives such as Azure CLI or REST API. This creates a bias toward Windows and PowerShell users, as Linux/macOS users may not use PowerShell by default and are not provided with equivalent examples.
Recommendations
- Include Azure CLI commands for user management alongside PowerShell examples.
- Reference REST API methods for adding users, which are platform-agnostic.
- Explicitly state that PowerShell is available cross-platform, or link to installation instructions for non-Windows users.
- Present command-line examples for both Windows (PowerShell) and Linux/macOS (Azure CLI or Bash).
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 First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased toward Windows and PowerShell. All code examples use Azure PowerShell cmdlets, and file paths are shown in Windows format (e.g., C:\Users\Contoso\). There are no CLI (az), Bash, or Linux/macOS-specific instructions or examples. The prerequisites explicitly require Azure PowerShell, and there is no mention of cross-platform alternatives. This creates friction for Linux and macOS users, who must translate all steps to az CLI or adapt PowerShell usage, and may be unfamiliar with Windows-centric file path conventions.
Recommendations
- Provide equivalent examples using Azure CLI (az) commands, which are cross-platform.
- Show file paths in both Windows and Linux/macOS formats, or use environment variables for portability.
- Explicitly mention that Azure PowerShell is available cross-platform, but recommend CLI for Linux/macOS users.
- Add Bash script examples for key steps, especially resource creation and DNS configuration.
- Include troubleshooting notes for Linux/macOS users regarding certificate handling and file paths.
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, without mentioning or providing equivalent instructions for Linux/macOS users (e.g., Azure CLI or REST API). This creates friction for non-Windows users who may not have access to PowerShell or prefer platform-native tools.
Recommendations
- Add Azure CLI examples for uploading CA certificates, as Azure CLI is cross-platform.
- Include REST API instructions for certificate management, which work on all platforms.
- Explicitly mention Linux/macOS compatibility and provide sample commands for those environments.
- Reorder examples so that platform-neutral methods (Azure portal, REST API, Azure CLI) 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 moderate Windows bias. PowerShell examples are presented first and in greater detail, with explicit variable setup and multiple scenarios (system/user-assigned managed identity). The CLI (Bash) and REST examples are present and reasonably complete, but PowerShell is prioritized and referenced throughout, including in prerequisites and links. There is no mention of Linux-specific shell environments or alternative scripting tools, and the documentation assumes familiarity with PowerShell and Windows-centric patterns.
Recommendations
- Present CLI (Bash) examples before PowerShell, or alternate their order to avoid implicit prioritization.
- Expand Bash/CLI sections to match the detail and scenarios provided in PowerShell (e.g., managed identity variations).
- Explicitly mention that Azure CLI and REST examples are cross-platform and suitable for Linux/macOS users.
- Add notes or links for Linux/macOS users on installing and using Azure CLI, and clarify that PowerShell Core is available cross-platform if users prefer it.
- Where possible, provide equivalent examples in native Linux shell scripting (e.g., Bash), especially for variable setup and automation.
- Avoid language in prerequisites that implies PowerShell is required; clarify that users can choose between PowerShell, CLI, or REST.
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 as the only explicit CLI example for creating loggers with connection string credentials. The PowerShell example is presented before alternatives, and no equivalent Azure CLI, Bash, or Linux-native scripting examples are provided. The documentation references tools (PowerShell) that are most commonly used on Windows, and does not mention or show how to perform the same tasks using cross-platform tools. However, the use of REST API, ARM, and Bicep templates provides platform-neutral options, mitigating the severity of the bias.
Recommendations
- Add Azure CLI examples for creating and managing loggers, especially for connection string scenarios.
- Explicitly mention that REST API, ARM, and Bicep methods are cross-platform and suitable for Linux/macOS users.
- Where PowerShell is referenced, provide equivalent Bash or shell script examples using Azure CLI.
- Consider reordering examples so that platform-neutral methods (REST API, ARM, Bicep, Azure CLI) appear before PowerShell.
- Add a note clarifying that PowerShell is available cross-platform, but Azure CLI is often preferred on Linux/macOS.
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 demonstrates a bias towards Windows by providing only PowerShell examples for disabling certificate chain validation, referencing Windows-centric tools (PowerShell cmdlets), and omitting equivalent Linux/macOS command-line instructions (such as Azure CLI or REST API examples). The PowerShell approach is presented first and in detail, while the REST API alternative is mentioned only briefly, without example code.
Recommendations
- Add Azure CLI examples for all tasks currently shown only with PowerShell, especially for disabling certificate chain validation.
- Provide REST API example payloads and usage for disabling certificate chain validation.
- Explicitly mention cross-platform alternatives and clarify which tools are available on Linux/macOS.
- Where PowerShell is referenced, also link to documentation for Azure CLI and REST API usage.
- Ensure example code is provided for both Windows and Linux/macOS users in all critical sections.
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
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a notable Windows bias, especially in the 'Create token and use with API call' section, where only Azure PowerShell scripts are provided for generating OAuth tokens and calling APIs. There are no equivalent examples for Linux/macOS users (e.g., Bash/cURL), and PowerShell is a Windows-centric tool, despite its cross-platform availability. The use of Azure portal instructions also assumes familiarity with Windows-style GUI navigation, and Windows tools/patterns are mentioned exclusively and first.
Recommendations
- Provide Bash/cURL examples for generating tokens and calling APIs, alongside PowerShell scripts.
- Explicitly mention that PowerShell Core is available cross-platform, and clarify any Windows-specific requirements.
- Add CLI-based instructions (e.g., Azure CLI, Bash) for steps currently described only via the Azure portal.
- Ensure that Linux/macOS users have clear, step-by-step guidance for all critical operations.
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
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias by providing detailed instructions and version checks for Azure PowerShell (a Windows-centric tool), listing Azure PowerShell before cross-platform tools in several places, and referencing Windows-specific command patterns. While Azure CLI and Terraform (cross-platform) are also mentioned, there are no Linux/macOS-specific instructions or examples, and PowerShell is given equal or greater prominence to CLI tools.
Recommendations
- Provide explicit Linux/macOS instructions or command examples where relevant (e.g., how to check and update Azure CLI on Linux/macOS).
- List cross-platform tools (Azure CLI, Terraform) before Windows-centric tools (Azure PowerShell) in all lists and instructions.
- Clarify that Azure PowerShell is available cross-platform, but highlight Azure CLI as the primary cross-platform tool.
- Include links to Linux/macOS installation/update guides for all tools mentioned.
- Where PowerShell commands are shown, provide equivalent Bash or shell commands where possible.