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 101-125 of 594 flagged pages
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 a Windows bias in several areas. In the section on uploading static files to a blob, it explicitly mentions 'Windows Command Prompt, PowerShell, or other command shell' before providing the Azure CLI command, implicitly prioritizing Windows environments. There are no explicit Linux or macOS shell examples, nor are Linux-specific tools or patterns mentioned. The documentation also references Windows-centric terminology (e.g., 'Command Prompt', 'PowerShell') and omits guidance for common Linux equivalents (e.g., bash, zsh).
Recommendations
- Explicitly mention Linux/macOS shells (e.g., bash, zsh, Terminal) alongside Windows shells when referring to command-line usage.
- Provide Linux/macOS-specific instructions or examples where relevant, such as file path formats, environment variable setting, and authentication flows.
- Avoid using Windows-centric terminology exclusively; use neutral terms like 'terminal' or 'command shell' and clarify cross-platform compatibility.
- If there are platform-specific caveats (e.g., differences in Azure CLI installation or authentication), document them for Linux/macOS users.
- Include troubleshooting tips or references for Linux/macOS users, especially for steps that may behave differently than on Windows.
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 First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias primarily through its references and linked examples. PowerShell is mentioned as the tool for connecting virtual networks, and there are no equivalent CLI or Linux-native examples provided. The documentation refers to Azure portal UI and PowerShell operations, but does not mention or link to Azure CLI, Bash, or Linux-oriented workflows. This may make the documentation less accessible or immediately actionable for Linux users.
Recommendations
- Provide parallel Azure CLI (az) examples alongside PowerShell for all network configuration and management tasks.
- Include references and links to Linux/Bash-based workflows where possible, especially for common operations like connecting virtual networks or applying network configurations.
- When mentioning PowerShell or Windows tools, ensure Linux equivalents are mentioned with equal prominence and, where possible, before or alongside Windows examples.
- Add explicit notes or sections for Linux users, clarifying any differences or additional steps required.
- Review related content and ensure that for every PowerShell or Windows-centric guide, a CLI or cross-platform alternative is linked.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/virtual-network-reference.md
...n/articles/api-management/virtual-network-reference.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page is generally platform-neutral but contains a few instances of Windows bias. It references Windows-specific tools and services (such as Windows Update, Windows Defender, and KMS activation for Windows VMs) without mentioning Linux equivalents or providing guidance for Linux-based deployments. Additionally, the only explicit mention of a management endpoint is for the Azure portal and PowerShell, with no mention of Azure CLI or other cross-platform tools. There are no Linux-specific examples or considerations, and Windows-related configurations are discussed without Linux parity.
Recommendations
- When referencing management endpoints, mention Azure CLI alongside PowerShell to provide cross-platform guidance.
- For sections discussing Windows-specific services (e.g., KMS, Windows Update, Windows Defender), add notes or links about Linux equivalents (such as Linux VM activation, update mechanisms, and security tools) or clarify if these steps are not required for Linux.
- Include examples or notes for Linux-based deployments where relevant, especially in sections about VM configuration and network requirements.
- Ensure that any scripts or command-line instructions are provided for both Windows (PowerShell) and Linux (Bash/Azure CLI) where applicable.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-integrate-internal-vnet-appgateway.md
...pi-management-howto-integrate-internal-vnet-appgateway.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page exclusively uses Azure PowerShell for all code examples and automation steps, with no mention or examples of equivalent Azure CLI, Bash, or cross-platform scripting. File paths and certificate handling assume Windows conventions (e.g., C:\ paths, .pfx files), and there is no guidance for Linux or macOS users. The prerequisites and instructions focus on Windows tooling and patterns, potentially excluding or confusing users on Linux or macOS.
Recommendations
- Provide equivalent Azure CLI (az) commands for all resource creation and configuration steps, alongside or instead of PowerShell.
- Use cross-platform file path examples (e.g., $HOME/certs/ or ~/certs/) or note the differences for Linux/macOS users.
- Include notes or sections on how to generate and use certificates on Linux/macOS, including OpenSSL commands for .pfx and .cer files.
- Mention that Azure PowerShell is available on Linux/macOS via PowerShell Core, but also recommend Azure CLI as a fully supported, cross-platform alternative.
- Where referencing tools or commands, avoid assuming a Windows environment; provide parity in instructions for Linux/macOS.
- Add troubleshooting and verification steps using Bash/curl that are platform-agnostic.
- Explicitly state in the prerequisites that all steps can be performed on Linux/macOS, and provide links to relevant setup guides.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-configuration-repository-git.md
...agement/api-management-configuration-repository-git.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by referencing Windows tools (Git Bash from Git for Windows, Visual Studio Immediate Window) as the primary or only examples for command-line and password encoding tasks. It also mentions Azure PowerShell before Azure CLI in several places, and provides detailed instructions for Visual Studio (a Windows-centric IDE) for URL encoding passwords, without offering equivalent Linux/macOS alternatives. There are no explicit Linux/macOS command-line examples or tool recommendations.
Recommendations
- Provide parallel Linux/macOS instructions and examples wherever Windows-specific tools or workflows are mentioned (e.g., suggest using the native terminal or Terminal.app, and provide equivalent shell commands).
- When referencing tools like Visual Studio for password encoding, include cross-platform alternatives (e.g., Python, Node.js, or command-line utilities for URL encoding).
- Avoid defaulting to Windows tools in examples; instead, use platform-agnostic tools or present both Windows and Linux/macOS options side by side.
- List Azure CLI before or alongside Azure PowerShell to avoid implying a Windows-first approach.
- Explicitly state that the instructions apply to all platforms and provide links to Git installation instructions for Linux/macOS as well as Windows.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-log-event-hubs.md
.../api-management/api-management-howto-log-event-hubs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing PowerShell examples for logger creation, referencing the Azure PowerShell module, and omitting equivalent CLI (az), Bash, or cross-platform scripting examples. The PowerShell example is the only imperative command-line example, and it appears before declarative options (Bicep, ARM). There are no Linux-native or cross-platform command-line instructions for users who do not use PowerShell.
Recommendations
- Add Azure CLI (az) command examples for logger creation and management, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash script examples or generic REST API curl examples to demonstrate how to perform tasks without relying on PowerShell.
- When listing tools or examples, present cross-platform options (e.g., Azure CLI) before or alongside Windows-specific tools (e.g., PowerShell), or clearly indicate that PowerShell is just one of several options.
- Explicitly mention that all steps can be performed from any OS using the Azure portal, REST API, or Azure CLI, not just PowerShell.
- Review and update the documentation to ensure Linux and macOS users are equally supported and not required to adapt Windows-centric instructions.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/automation-manage-api-management.md
...les/api-management/automation-manage-api-management.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively references Windows PowerShell cmdlets and scripts for managing Azure API Management via Azure Automation. There are no examples or mentions of Linux-compatible tools (such as Azure CLI, Bash, or Python), nor is there guidance for non-Windows environments. The focus on PowerShell and Windows tooling creates a bias towards Windows users and may exclude or hinder Linux users.
Recommendations
- Provide equivalent examples using Azure CLI, which is cross-platform and works natively on Linux.
- Include Bash or Python script samples for managing Azure API Management via Azure Automation.
- Mention and link to documentation for Linux/macOS users where appropriate.
- Structure sections to present cross-platform solutions first or in parallel with Windows/PowerShell examples.
- Clarify which tools and scripts are platform-agnostic and which are Windows-specific.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-versions.md
...ain/articles/api-management/api-management-versions.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell as a primary management tool alongside Azure CLI, and by referencing PowerShell before cross-platform or Linux-native options. There are no explicit Linux or bash examples, and the documentation does not mention Linux-specific tools or workflows. The order and emphasis favor Windows-centric tools and patterns.
Recommendations
- Provide explicit bash or shell command examples alongside PowerShell commands when referencing management tasks.
- List Azure CLI before Azure PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
- Mention that Azure CLI and Resource Manager templates are fully supported on Linux and macOS.
- Include links or references to Linux/macOS setup guides for Azure CLI and other tools.
- Avoid implying PowerShell is the default or preferred tool; clarify tool parity across platforms.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-revisions.md
...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 bias towards Windows by exclusively referencing 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). No Linux-native tools or cross-platform command-line instructions are mentioned, and the only automation examples are Windows-centric.
Recommendations
- Provide Azure CLI examples alongside PowerShell cmdlets for all command-line operations, as Azure CLI is cross-platform and widely used on Linux.
- Include REST API examples for users who prefer direct HTTP requests, which are platform-agnostic.
- Clearly indicate when a feature is only available via the Azure portal, and if so, ensure screenshots or instructions are not Windows-specific.
- Review all automation instructions to ensure Linux and macOS users are equally supported, not just Windows/PowerShell users.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/applications.md
...docs/blob/main/articles/api-management/applications.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell scripts for generating OAuth tokens and calling APIs, with no equivalent Linux/bash/cURL examples. The only command-line tooling referenced is PowerShell/Invoke-RestMethod, which is Windows-centric (though available cross-platform, it is not the default shell on Linux). The documentation also references the Azure Portal UI exclusively, which is more familiar to Windows users, and does not mention or prioritize Linux-native tools or workflows.
Recommendations
- Provide equivalent Linux/bash/cURL examples for generating tokens and calling APIs, alongside the PowerShell scripts.
- Explicitly mention that PowerShell Core is cross-platform, but also offer native bash/cURL commands for Linux/macOS users.
- Include CLI-based alternatives (e.g., Azure CLI commands) where possible, not just portal steps.
- Add a note or section on how to perform the same tasks on Linux/macOS, including any prerequisites or differences.
- Ensure that examples and instructions are presented in a platform-neutral order, or alternate which platform is shown first.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/breaking-changes/api-version-retirement-sep-2023.md
...nt/breaking-changes/api-version-retirement-sep-2023.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell is given equal prominence to Azure CLI, with explicit PowerShell commands and update instructions, while Linux-native tools or shell examples are not provided. The Azure CLI is mentioned, but no bash or Linux-specific guidance is included. The order of presentation often puts PowerShell before or alongside CLI, and Windows-centric tools (PowerShell, Azure portal) are emphasized. There are no explicit Linux shell or scripting examples, and the documentation assumes familiarity with Windows tools.
Recommendations
- Provide Linux shell (bash) equivalents for all PowerShell commands, especially for checking and updating Azure CLI.
- Explicitly mention that Azure CLI is cross-platform and provide Linux/macOS installation and update instructions.
- When listing tools, consider mentioning cross-platform tools (CLI, Terraform, Bicep) before Windows-centric ones (PowerShell).
- Add examples or links for managing API Management via bash scripts or Linux automation tools.
- Clarify that the Azure portal and REST API are platform-agnostic, and highlight this in relevant sections.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/developer-portal-alternative-processes-self-host.md
...nt/developer-portal-alternative-processes-self-host.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows/Azure-centric bias by exclusively referencing Azure tools and services, such as Azure CLI, Azure Function App, and Azure CDN, without mentioning or providing examples for Linux or cross-platform alternatives. There are no explicit Linux-specific instructions or examples, and the guidance assumes the use of Azure's ecosystem, which is more commonly associated with Windows environments.
Recommendations
- Include equivalent instructions and examples for Linux environments, such as using Bash scripts or Linux-native tools where applicable.
- Mention and provide examples for deploying to non-Azure hosting solutions (e.g., AWS S3, Google Cloud Storage, or generic Nginx/Apache static hosting) to ensure cross-platform applicability.
- Clarify that Azure CLI and Azure Functions Core Tools are cross-platform, and provide installation instructions for Linux and macOS, not just Windows.
- Offer alternative CDN recommendations beyond Azure CDN, such as Cloudflare or AWS CloudFront, to avoid exclusive Azure bias.
- Explicitly state that all npm and CLI commands are platform-agnostic, and note any platform-specific caveats if they exist.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/credentials-how-to-user-delegated.md
...es/api-management/credentials-how-to-user-delegated.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by providing only Azure PowerShell (Windows-centric) instructions for provisioning the service principal, referencing the AzureAD PowerShell module (which is primarily used on Windows), and omitting equivalent CLI or Bash examples. No Linux/macOS-specific instructions or cross-platform alternatives (such as Azure CLI or REST API) are provided for key setup steps. The documentation assumes the use of the Azure Portal and PowerShell, both of which are more familiar to Windows users.
Recommendations
- Add equivalent Azure CLI (az) commands for provisioning the service principal and other setup steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention that all PowerShell steps can be performed on Linux/macOS using Azure CLI or Bash, and provide those examples side-by-side.
- Where possible, provide REST API alternatives for automation scenarios.
- Clarify in prerequisites that PowerShell is not required and that users on Linux/macOS can follow along using CLI or portal.
- Review all code snippets and ensure parity between Windows (PowerShell) and Linux/macOS (CLI/Bash) instructions.
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
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias, most notably in Step 6 ('Upload static files to a blob'), where it explicitly instructs users to 'Open Windows Command Prompt, PowerShell, or other command shell' before running Azure CLI commands. No mention is made of Linux or macOS terminals, and no Linux-specific instructions or examples are provided. The general pattern is to assume a Windows environment, even though the rest of the steps are cross-platform and use generic shell commands.
Recommendations
- Update language in Step 6 to reference all major platforms, e.g., 'Open your terminal (Command Prompt, PowerShell, or terminal on Linux/macOS)'.
- Explicitly state that all commands are cross-platform unless otherwise noted.
- Wherever a shell or terminal is referenced, provide parity by mentioning Linux/macOS equivalents alongside Windows tools.
- If there are any platform-specific considerations (such as path separators or environment variable syntax), call them out with examples for both Windows and Linux/macOS.
- Consider adding a short section or note at the start of the document clarifying that the instructions are intended to be cross-platform, and that the Azure CLI and other tools work on Windows, Linux, and macOS.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/enable-cors-power-platform.md
.../articles/api-management/enable-cors-power-platform.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation assumes usage of the Azure Portal and Power Platform GUIs, which are most accessible and fully featured on Windows environments. There are no CLI, Bash, or cross-platform automation examples, nor is there mention of Linux-compatible tools or workflows. Troubleshooting guidance references Application Insights and browser developer tools, but does not mention cross-platform command-line tools or Linux-specific approaches. The documentation implicitly prioritizes Windows/GUI workflows and omits Linux or cross-platform alternatives.
Recommendations
- Include Azure CLI and/or Azure PowerShell command examples for configuring CORS policies, making sure to show both Windows (PowerShell) and Linux (Bash) syntax.
- Mention and provide examples for using cross-platform tools (e.g., az CLI, curl, jq) to automate or verify CORS policy configuration.
- Add troubleshooting steps that leverage cross-platform tools, such as curl for testing CORS headers from Linux/macOS terminals.
- Explicitly state that the Azure Portal and Power Platform GUIs are web-based and accessible from any OS, but provide parity for users who prefer or require command-line or scriptable solutions.
- Where screenshots or UI steps are provided, consider linking to equivalent documentation for CLI-based workflows.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/import-api-from-oas.md
...ob/main/articles/api-management/import-api-from-oas.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the explicit inclusion of Azure PowerShell (which is most commonly used on Windows and follows Windows scripting conventions) and the absence of any Linux- or bash-specific examples (such as using curl or jq, or mentioning Linux shell environments) demonstrates a Windows-centric bias. Additionally, PowerShell is given equal prominence to CLI, and there is no mention of Linux-native tools or workflows.
Recommendations
- Add explicit bash/shell examples for Linux users, such as using curl to download the OpenAPI spec and az CLI commands in a Linux shell context.
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary shell syntax differences.
- If PowerShell is included, consider also including bash or zsh examples to ensure parity for Linux/macOS users.
- Mention Linux and macOS compatibility in the prerequisites and tool installation sections.
- Where possible, avoid Windows-centric terminology (such as 'cmdlet') or explain it for non-Windows users.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/import-soap-api.md
...s/blob/main/articles/api-management/import-soap-api.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but gives equal prominence to PowerShell (a Windows-centric tool) and includes detailed PowerShell instructions and context setup. There is no mention of Bash, Linux shell, or cross-platform scripting alternatives, and PowerShell is referenced in both prerequisites and example sections. The structure and language (e.g., 'Azure PowerShell') reinforce a Windows-first perspective, even though Azure CLI is cross-platform.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash-specific notes or examples where relevant.
- Clarify that PowerShell Core is cross-platform, or provide Bash shell equivalents for context setup and scripting.
- Balance the order of examples: alternate between CLI and PowerShell, or lead with CLI (as the more cross-platform tool).
- In prerequisites, clarify that Azure CLI is available on all major platforms, and provide installation links for Linux/macOS.
- Consider adding a short section or callout for Linux/macOS users, highlighting any differences or tips.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-mutual-certificates.md
...management/api-management-howto-mutual-certificates.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides PowerShell-only examples for disabling certificate chain validation, with no equivalent CLI, Bash, or Linux-native instructions. The use of PowerShell cmdlets (New-AzApiManagementBackend, Set-AzApiManagementBackend) assumes a Windows environment or requires extra setup on Linux. There are no examples using Azure CLI, REST with curl, or other cross-platform tools.
Recommendations
- Add equivalent examples using Azure CLI (az apim), which is cross-platform and commonly used on Linux/macOS.
- Provide REST API examples using curl or httpie to demonstrate how to perform the same actions without PowerShell.
- Explicitly mention that PowerShell can be installed on Linux/macOS, or link to installation instructions if PowerShell is the only option.
- Ensure that all code snippets are accompanied by both Windows/PowerShell and Linux/Bash/Azure CLI alternatives where possible.
- Review the documentation for any other Windows-centric terminology or screenshots and provide Linux-agnostic alternatives.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-app-insights.md
...es/api-management/api-management-howto-app-insights.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing the Azure portal (a web GUI), REST API, Bicep, and ARM templates for configuration, without providing any command-line examples (such as Azure CLI, PowerShell, Bash, or scripting) that would be directly relevant to Linux users. There are no Linux-specific instructions or examples, and the documentation does not mention or demonstrate cross-platform command-line tools. The workflow assumes use of the Azure portal or ARM/Bicep templates, which are platform-agnostic in theory but are often associated with Windows-centric workflows. No PowerShell-specific bias is present, but the absence of Azure CLI or Bash examples is notable.
Recommendations
- Add Azure CLI examples for all configuration steps (e.g., creating loggers, enabling diagnostics), as Azure CLI is cross-platform and widely used on Linux.
- Include Bash script snippets for REST API calls, demonstrating how to perform the same operations from a Linux shell.
- Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and provide parity in instructions for each platform where relevant.
- If referencing the Azure portal, clarify that it is accessible from any OS, but supplement with command-line alternatives for automation and scripting.
- Where ARM/Bicep templates are shown, provide deployment instructions using Azure CLI (az deployment group create ...) rather than assuming portal usage.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-mutual-certificates.md
...management/api-management-howto-mutual-certificates.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias toward Windows by providing only Azure PowerShell examples for disabling certificate chain validation, with no equivalent CLI or Linux-native instructions. The use of PowerShell cmdlets is highlighted, and there are no Bash, Azure CLI, or cross-platform scripting examples. This may hinder users working on Linux or macOS environments.
Recommendations
- Provide equivalent Azure CLI (az) examples for all PowerShell cmdlets shown, especially for backend configuration tasks.
- Include Bash shell script examples or instructions for Linux/macOS users.
- Explicitly mention that PowerShell Core is cross-platform if PowerShell must be used, and provide installation guidance for non-Windows systems.
- Where possible, use REST API examples with curl or HTTPie to demonstrate platform-agnostic approaches.
- Review all sections to ensure that Linux and macOS users are equally supported in step-by-step instructions.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-role-based-access-control.md
...management/api-management-role-based-access-control.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for custom role creation and assignment, without offering equivalent Azure CLI (cross-platform) or Bash examples. References to tools and links mention PowerShell before Azure CLI, and the only code sample is in PowerShell, which is primarily a Windows-centric tool. There are no Linux/Bash or cross-platform CLI examples, which may disadvantage users on non-Windows systems.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell code samples, especially for custom role creation and assignment.
- When listing tools (Azure portal, PowerShell, Azure CLI, REST API), alternate the order or list Azure CLI before PowerShell to avoid 'windows_first' bias.
- Explicitly mention that all operations can be performed using Azure CLI and provide links to relevant CLI documentation.
- Include Bash or shell script examples where appropriate to ensure Linux parity.
- Add a note clarifying that PowerShell Core is cross-platform, but still provide CLI/Bash alternatives for users who prefer them.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-mutual-certificates.md
...management/api-management-howto-mutual-certificates.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides PowerShell-only examples for disabling certificate chain validation, with no equivalent examples for Linux-native tools (such as Azure CLI, Bash, or REST API via curl). The use of PowerShell cmdlets as the only code sample assumes a Windows environment or Windows PowerShell Core, and there is no mention of Linux command-line workflows or tools. This may hinder Linux users or those who prefer cross-platform tooling.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlets shown, especially for tasks like disabling certificate chain validation.
- Include REST API usage examples with curl or HTTPie to demonstrate cross-platform approaches.
- Explicitly mention that PowerShell Core is cross-platform if relevant, or clarify if the examples require Windows PowerShell.
- Where possible, provide Bash script snippets or references for Linux users.
- Ensure that any tool or workflow mentioned (such as certificate management) is accompanied by both Windows and Linux-compatible instructions.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-oauth2.md
...articles/api-management/api-management-howto-oauth2.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented towards the Azure portal UI and Microsoft Entra ID, with all examples and instructions assuming use of the Azure web portal. There are no command-line examples (neither PowerShell nor CLI), but all tool references are Microsoft/Azure-specific, with no mention of Linux, cross-platform, or open-source alternatives. The documentation does not provide parity for Linux users or those who prefer CLI-based workflows.
Recommendations
- Include Azure CLI examples for all steps that can be performed via command line, ensuring instructions are cross-platform.
- Where possible, provide REST API examples for automation and scripting, which are OS-agnostic.
- Mention and link to open-source OAuth 2.0 providers or tools (such as Keycloak, Auth0, or generic OAuth 2.0 servers) and show how to configure API Management with them.
- Explicitly state that the Azure portal is web-based and accessible from any OS, but also provide alternatives for users who prefer not to use a GUI.
- Add a section or callout for Linux/macOS users, clarifying that all steps can be performed from any OS, and providing any OS-specific considerations if necessary.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-ca-certificates.md
...api-management/api-management-howto-ca-certificates.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides a PowerShell command (`New-AzApiManagementSystemCertificate`) as the only CLI example for uploading a CA certificate, with no mention of equivalent Azure CLI, Bash, or Linux-native methods. The use of PowerShell and lack of Linux/Unix command-line alternatives indicate a Windows-centric bias.
Recommendations
- Add Azure CLI examples for uploading and managing CA certificates, as Azure CLI is cross-platform and widely used on Linux.
- Include Bash or Linux shell command examples where applicable, especially for certificate management tasks.
- Explicitly mention that PowerShell Core is cross-platform if recommending PowerShell, and provide installation guidance for non-Windows users.
- Ensure that any references to tools or commands are accompanied by their Linux/macOS equivalents or alternatives.
- Review the documentation for other areas where Windows-specific terminology or screenshots could be replaced or supplemented with cross-platform guidance.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-app-insights.md
...es/api-management/api-management-howto-app-insights.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a bias towards Windows environments by exclusively referencing the Azure portal (a web GUI), REST API, Bicep, and ARM templates for configuration, with no mention of Linux-native command-line tools or shell scripting. There are no CLI (az), PowerShell, Bash, or Linux-specific instructions or examples. The workflow assumes use of the Azure portal or infrastructure-as-code tools, which are platform-agnostic but often more familiar to Windows users. The absence of Azure CLI or Bash examples makes it less accessible for Linux users or those preferring command-line automation.
Recommendations
- Add Azure CLI (az) command examples for all major configuration steps, including creating loggers, assigning roles, and enabling diagnostics.
- Include Bash shell script snippets for automation scenarios, especially for Linux users.
- Explicitly mention that all steps can be performed from any OS using the Azure CLI or REST API, and provide cross-platform command-line alternatives.
- If PowerShell is referenced in other related docs, ensure Bash or Azure CLI equivalents are also provided.
- Clarify in the prerequisites and throughout the guide that the instructions are not limited to Windows and can be executed from Linux/macOS environments using CLI tools.