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 201-225 of 594 flagged pages
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-based alternative to the Azure Portal for uploading a CA certificate. There are no examples or mentions of equivalent Linux-friendly tools (such as Azure CLI or REST API usage) for this operation. The documentation implicitly assumes a Windows environment by referencing PowerShell exclusively, and does not provide parity for Linux or cross-platform users.
Recommendations
- Add Azure CLI examples for uploading and managing CA certificates, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include REST API examples (with curl or similar tools) for certificate management tasks, allowing users on any OS to automate these operations.
- When mentioning PowerShell, also mention and provide examples for other platforms/tools in parallel, rather than exclusively or first.
- Explicitly state that the PowerShell command is one option, and link to documentation for other methods (CLI, REST API) where available.
- Review all command-line instructions to ensure Linux users are not excluded or required to use Windows-specific tools.
Create Pull Request
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 Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows and Microsoft-centric tools and workflows. All examples and instructions are given exclusively through the Azure portal UI, which is typically accessed via a web browser but is deeply integrated with Microsoft Entra ID (formerly Azure AD) and does not mention or provide alternatives for Linux-based workflows, CLI tools, or non-Microsoft OAuth providers. There are no references to Linux command-line tools, cross-platform scripting, or open-source alternatives. The documentation assumes the use of Microsoft Entra ID and the Azure portal, both of which are most familiar to Windows users.
Recommendations
- Provide equivalent instructions using Azure CLI and/or PowerShell, and ensure Azure CLI examples are included (as it is cross-platform and widely used on Linux).
- Include examples or references for configuring OAuth 2.0 with non-Microsoft providers (such as Okta, Auth0, or open-source solutions like Keycloak), and show how to obtain endpoints and credentials from those systems.
- Add a section or callouts for Linux/macOS users, clarifying that all steps can be performed from any OS via the Azure portal, and explicitly mention any OS-specific prerequisites or differences.
- Where possible, include curl or httpie command-line examples for API calls, token requests, or validation steps, to demonstrate parity for developers working in Linux environments.
- Reference and link to documentation for cross-platform tools (e.g., Azure CLI, REST API) wherever the Azure portal is mentioned, to ensure users on all platforms have clear guidance.
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 it demonstrates a Windows bias by giving equal prominence to PowerShell (a Windows-centric tool), listing it immediately after CLI, and including detailed PowerShell setup instructions. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is presented as a primary automation method alongside CLI, despite CLI being more cross-platform. The prerequisites and examples do not mention or demonstrate Linux-native tools or workflows.
Recommendations
- Add explicit Bash or shell script examples for Linux users, especially for common automation scenarios.
- Clarify that Azure CLI commands are fully cross-platform and can be run on Linux, macOS, and Windows.
- De-emphasize PowerShell as a primary automation tool by listing Azure CLI first and PowerShell second, or by grouping PowerShell as an alternative for Windows users.
- Include notes or sections on how to install and use Azure CLI on Linux, and link to Linux-specific setup guides.
- If PowerShell is included, mention that PowerShell Core is available cross-platform, but provide native Bash alternatives where possible.
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 a Windows bias 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 or cross-platform command-line tools are mentioned, and the only automation examples are Windows-specific.
Recommendations
- Provide equivalent Azure CLI commands for all PowerShell cmdlet examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include REST API examples where appropriate, since these are platform-agnostic.
- When mentioning command-line tools, list Azure CLI and REST API before or alongside PowerShell to avoid implying Windows is the primary or only supported environment.
- Add a note clarifying that all operations can be performed using Azure CLI or REST API, not just PowerShell.
- Consider including bash shell script snippets for common tasks, to further support Linux users.
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
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell as a primary management tool alongside Azure CLI, mentioning PowerShell before CLI, and omitting explicit Linux or cross-platform command-line examples. There is no mention of Linux-specific tools or guidance, and the examples and instructions assume a Windows-centric workflow.
Recommendations
- Ensure that Azure CLI examples are provided before or alongside Azure PowerShell examples, as CLI is cross-platform.
- Explicitly mention that Azure CLI and Resource Manager templates are fully supported on Linux, macOS, and Windows.
- Add Linux/macOS-specific notes or examples where relevant, especially for command-line operations.
- Avoid listing PowerShell before CLI unless there is a technical reason; consider alternating order or grouping by platform.
- Include screenshots or instructions from non-Windows environments (e.g., Azure CLI in a Linux terminal) to reinforce cross-platform parity.
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
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (Git Bash from Git for Windows), providing troubleshooting steps that rely on Visual Studio (a Windows-centric IDE), and omitting explicit Linux/macOS examples or alternatives. The only command-line examples are generic git commands, but the only tool mentioned by name is Git for Windows, and the only workaround for password encoding uses Visual Studio's Immediate Window, which is not available on Linux/macOS. No Linux or cross-platform alternatives are suggested for these steps.
Recommendations
- Explicitly mention and provide examples for Linux and macOS users, such as using the built-in terminal or common shells (bash, zsh) for git commands.
- Replace or supplement the Visual Studio Immediate Window password encoding step with a cross-platform alternative, such as using Python, Node.js, or command-line tools (e.g., `python3 -c 'import urllib.parse; print(urllib.parse.quote("password"))'`).
- List cross-platform Git tools (e.g., native git, GitHub CLI, etc.) and avoid suggesting only Windows-specific downloads.
- Where screenshots or UI steps are shown, clarify that the process is the same across platforms or note any differences.
- Add a section or callout for Linux/macOS users to ensure parity and inclusivity.
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 importing OpenAPI specifications using the Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is traditionally Windows-centric, though now cross-platform) and the explicit PowerShell example may indicate a Windows bias. The order of presentation (Portal, CLI, then PowerShell) is acceptable, but the documentation does not provide any Linux- or bash-specific guidance, troubleshooting, or examples beyond the CLI, nor does it mention Linux-specific considerations or tools. There are no missing Linux examples per se, but the presence of PowerShell-specific instructions and the lack of any Linux shell or scripting context may make the documentation feel more Windows-oriented.
Recommendations
- Explicitly state that Azure CLI commands are cross-platform and provide any Linux/macOS-specific notes if relevant (e.g., environment variable syntax differences).
- Consider adding bash or shell script examples for Linux users, especially for scripting scenarios.
- If PowerShell is included, clarify that PowerShell Core is available cross-platform, or provide equivalent bash examples where possible.
- Mention any Linux-specific prerequisites or troubleshooting steps, if applicable.
- Ensure parity in troubleshooting and advanced usage sections for both Windows and Linux users.
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 exhibits a mild Windows bias. It references Windows-specific tools and scenarios (such as KMS activation and Windows Update/Defender endpoints) without mentioning Linux equivalents or clarifying their relevance for non-Windows environments. Additionally, some linked content (e.g., VPN Gateway connections via PowerShell) suggests a Windows-first approach. There are no Linux-specific examples or guidance, and the documentation does not address how requirements differ for Linux-based deployments.
Recommendations
- Where Windows-specific endpoints or ports are mentioned (e.g., KMS activation, Windows Update, Windows Defender), clarify that these are only required for Windows VMs and note that Linux VMs do not require these settings.
- Add a section or notes on Linux VM requirements, explicitly stating if any ports or endpoints are needed for Linux (e.g., for package updates or diagnostics), or confirm that no special configuration is needed.
- When referencing tools or scripts (such as PowerShell), provide equivalent instructions or links for Linux environments (e.g., Azure CLI, Bash scripts).
- Review related links and ensure parity by including Linux-focused or cross-platform documentation where available.
- Consider adding a table or callout summarizing differences in network requirements between Windows and Linux VM scenarios.
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
Missing Linux Example
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 cloning and URL encoding passwords. There are no Linux or macOS-specific instructions or examples, and the only tool-specific guidance is for Windows environments. This may hinder Linux or cross-platform users who are unfamiliar with these Windows-centric tools.
Recommendations
- Provide explicit Linux and macOS instructions for cloning the repository, such as using the default terminal or common Linux tools.
- Replace or supplement the Visual Studio Immediate Window example for URL encoding with a cross-platform method, such as using Python, Node.js, or command-line utilities available on Linux/macOS.
- When referencing tools, mention cross-platform options first (e.g., 'any Git client or terminal'), and only mention Windows-specific tools as one possible option.
- Add a note or section clarifying that all Git operations can be performed from any OS, and provide example commands for Linux/macOS shells.
- Ensure parity in troubleshooting steps and credential handling for non-Windows environments.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-ca-certificates.md
...api-management/api-management-howto-ca-certificates.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates Windows bias by providing a PowerShell command (`New-AzApiManagementSystemCertificate`) as the only CLI example for uploading a CA certificate, without mentioning or providing equivalent instructions for Linux users (e.g., Azure CLI, Bash, or REST API). The use of PowerShell and the lack of Linux-native tooling or examples suggest a preference for Windows environments.
Recommendations
- Add Azure CLI examples for uploading and managing CA certificates, as Azure CLI is cross-platform and widely used on Linux.
- Include REST API examples for certificate management to provide a platform-agnostic approach.
- Present PowerShell and CLI/REST examples side-by-side, or at least mention Linux-compatible alternatives before or alongside Windows-specific tools.
- Clarify that the PowerShell command is optional and provide guidance for users on non-Windows platforms.
- Review and update screenshots or UI instructions to ensure terminology and steps are not Windows-centric.
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 is heavily biased toward Windows and PowerShell usage. All command-line examples are provided exclusively in Azure PowerShell, with no mention of Azure CLI, Bash, or cross-platform scripting. File paths use Windows-style conventions (e.g., C:\Users\Contoso\), and there is no guidance for Linux or macOS users regarding certificate storage or command adaptation. The documentation assumes the use of Windows tools and patterns throughout, making it less accessible for users on Linux or macOS.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside PowerShell for all resource creation and configuration steps.
- Include Bash shell script examples and use cross-platform file path conventions (e.g., $HOME/certs/ or ~/certs/) in variable definitions.
- Add notes or sections specifically addressing Linux/macOS users, especially for certificate handling, file paths, and environment setup.
- Reference cross-platform tools (such as OpenSSL for certificate generation) and avoid assuming the use of Windows-only utilities.
- Where PowerShell is required, clarify that Azure PowerShell is available on Linux/macOS and provide installation instructions for those platforms.
- Reorder or parallelize instructions so that Linux/macOS approaches are presented equally, not as an afterthought.
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 PowerShell examples for command-line operations (such as disabling certificate chain validation), without offering equivalent instructions for Linux or cross-platform tools like Azure CLI. The use of PowerShell cmdlets and the absence of bash or Azure CLI examples may disadvantage Linux users or those working in non-Windows environments.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell cmdlets, especially for tasks like disabling certificate chain validation.
- Include bash shell examples where appropriate, particularly for uploading certificates or managing API Management resources.
- Explicitly mention that PowerShell examples can be run on Linux/macOS using PowerShell Core, or provide alternative commands for native Linux environments.
- Review the documentation for other areas where Windows-centric tools or workflows are assumed, and ensure Linux parity throughout.
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 Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by providing only Azure PowerShell examples for command-line logger creation, without offering equivalent Azure CLI or Bash examples. The use of PowerShell is highlighted as the sole scripting interface, and there is no mention of Linux-native tools or cross-platform command-line alternatives. This may hinder Linux or macOS users who prefer or require non-PowerShell workflows.
Recommendations
- Add Azure CLI examples alongside PowerShell for logger creation and management, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that all configuration steps can be performed from any OS using the Azure portal or REST API, not just via PowerShell.
- Where PowerShell is used, provide equivalent Bash or shell script snippets where possible, or link to documentation showing how to perform the same steps using Azure CLI.
- Clarify that Bicep and ARM templates are OS-agnostic, and provide guidance on deploying them from Linux/macOS environments.
- Review all sections for references to Windows-specific tools or workflows and ensure Linux parity is maintained throughout.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-use-managed-service-identity.md
...t/api-management-howto-use-managed-service-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for command-line operations, referencing installation of Azure PowerShell (a Windows-centric tool), and omitting equivalent Azure CLI (cross-platform) or Bash examples. The PowerShell approach is presented before ARM templates, and there is no mention of Linux or macOS workflows. This may disadvantage users on Linux or macOS who prefer Azure CLI or Bash scripting.
Recommendations
- Add Azure CLI examples for all operations currently demonstrated with Azure PowerShell, including creating and updating API Management instances with managed identities.
- Include Bash script examples where appropriate, especially for ARM template deployments.
- Explicitly mention that Azure CLI is cross-platform and provide installation links for Linux/macOS users.
- Present Azure CLI and PowerShell examples side-by-side or in parallel tabs, rather than PowerShell-first.
- Review references to 'install Azure PowerShell' and add corresponding instructions for Azure CLI.
- Ensure screenshots and UI instructions are not Windows-specific, or clarify if they are universal.
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 a Windows bias by referencing PowerShell cmdlets (e.g., New-AzApiManagementApiRelease, Update-AzApiManagementApiRelease) as the only CLI automation examples, without mentioning or providing equivalent Azure CLI or REST API commands that are cross-platform. There are no Linux/macOS-specific instructions or examples, and the use of PowerShell is presented as the default scripting/automation method.
Recommendations
- Provide equivalent Azure CLI commands for all PowerShell cmdlet examples, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include REST API examples for automation tasks, which are platform-agnostic.
- When mentioning PowerShell, also mention Azure CLI and REST API options, and present them in parallel or in a neutral order (not Windows/PowerShell first).
- Add explicit notes or sections for Linux/macOS users to ensure parity and inclusivity.
- Review the documentation for other areas where Windows-specific tools or patterns are assumed, and update to include cross-platform alternatives.
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
Missing Linux Example
Windows Tools
Summary
The documentation provides a detailed PowerShell example for creating and assigning custom roles but does not offer equivalent examples using cross-platform tools such as Azure CLI. PowerShell is a Windows-centric tool (though available on Linux, it is less commonly used there), and the lack of Azure CLI or bash examples may hinder Linux users. Additionally, the page references Azure PowerShell before Azure CLI in the list of tools, and the only code sample is in PowerShell.
Recommendations
- Add equivalent Azure CLI (az role definition/az role assignment) examples alongside PowerShell code samples for custom role creation and assignment.
- When listing tools for role assignment, mention Azure CLI before or alongside Azure PowerShell to avoid implying a Windows-first workflow.
- Include bash or shell script examples where appropriate to demonstrate cross-platform compatibility.
- Explicitly state that all operations can be performed using Azure CLI and provide links to relevant CLI documentation.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-subscriptions.md
...rticles/api-management/api-management-subscriptions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page references Azure PowerShell and Azure SDKs as tools for automating subscription key management, but does not mention Linux-native tools, CLI examples, or provide cross-platform command-line instructions. There are no Linux-specific or cross-platform automation examples, and the only tooling mentioned is PowerShell, which is traditionally Windows-centric (despite now being cross-platform).
Recommendations
- Include Azure CLI examples alongside or instead of Azure PowerShell for automation tasks, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that Azure PowerShell is available on Linux and macOS, or provide Bash shell script examples where appropriate.
- When referencing SDKs, clarify which languages and platforms are supported, and provide at least one example using a Linux-friendly language (e.g., Python).
- Avoid implying that PowerShell is the primary or only automation tool; present CLI and SDK options in a platform-neutral order.
- Add a section or callout for Linux/macOS users, highlighting equivalent tools and workflows.
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 references Azure PowerShell before Azure CLI and does not provide Linux-specific examples or mention Linux tooling. The order of tools (Azure CLI, Azure PowerShell, Resource Manager templates, API) places PowerShell prominently, and there are no bash or Linux command-line examples. The documentation assumes familiarity with Windows-centric tools and patterns, which may disadvantage Linux users.
Recommendations
- Provide explicit Linux/bash examples alongside or before PowerShell examples.
- When listing management tools, mention Azure CLI before Azure PowerShell, as CLI is cross-platform and more familiar to Linux users.
- Include sample commands for both Azure CLI and Azure PowerShell where relevant.
- Reference Linux-native tools or workflows where possible, and clarify that all management operations can be performed from Linux environments.
- Avoid assuming the user is using Windows or PowerShell; use neutral language and tool ordering.
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
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples for generating tokens and calling APIs are provided exclusively in PowerShell, a Windows-centric shell. There are no equivalent examples using cross-platform or Linux-native tools (such as curl or bash scripts). The only CLI scripting guidance is for Azure PowerShell, and there is no mention of Linux or macOS workflows. The documentation assumes use of the Azure Portal (web UI), which is cross-platform, but all automation and scripting is presented in a Windows-first manner.
Recommendations
- Provide equivalent examples using curl and bash for Linux/macOS users, especially for OAuth token generation and API calls.
- Explicitly mention that the API calls and token generation can be performed from any OS, not just Windows.
- Where Azure PowerShell is referenced, also provide Azure CLI (az) equivalents, which are cross-platform.
- Add a note or section highlighting Linux/macOS compatibility and any OS-specific considerations.
- Ensure screenshots and UI instructions do not assume a Windows environment unless absolutely necessary.
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 provides only PowerShell-based examples for managing Azure API Management via Azure Automation. There is no mention of Linux-compatible tools (such as Azure CLI, Bash scripts, or Python), nor are any cross-platform or Linux-specific examples provided. The focus on PowerShell and Windows tools creates a Windows-centric bias.
Recommendations
- Include equivalent examples using Azure CLI, which is cross-platform and widely used on Linux.
- Provide Bash or Python script samples for managing Azure API Management in Azure Automation.
- Explicitly mention that Azure Automation supports multiple runbook types (PowerShell, Python, Graphical, etc.) and provide links or examples for each.
- Reorder content or add parallel sections so that Linux-compatible tools and workflows are presented alongside Windows/PowerShell options.
- Clarify in the introduction that the guide currently focuses on PowerShell, and point to resources for other platforms.
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 First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell (and specifically the AzureAD module) instructions for provisioning the service principal, with no equivalent Bash/CLI or Linux-native example. The prerequisite section includes a PowerShell requirements include, and all command-line steps are shown using PowerShell syntax. There is no mention of cross-platform Azure CLI alternatives, and the documentation assumes use of the Azure Portal (web UI), which is platform-neutral but does not compensate for the lack of Linux/CLI parity in scripting steps.
Recommendations
- Provide equivalent Azure CLI (az) commands for all PowerShell steps, especially for provisioning the service principal. Azure CLI is cross-platform and works natively on Linux and macOS.
- Add a section or callout indicating that all steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant Azure CLI documentation.
- Where PowerShell modules are referenced (e.g., AzureAD), mention their platform limitations and suggest alternatives for non-Windows users.
- Ensure that all code snippets and automation steps are available in both PowerShell and Bash/Azure CLI formats, ideally side-by-side.
- Review the 'azure-powershell-requirements-no-header' include to ensure it does not exclude or discourage Linux users.
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 bias towards Windows/Azure tools and workflows. All examples and instructions use Azure CLI, Azure Functions, and related Microsoft tooling, with no mention of Linux-specific workflows or alternatives. There are no explicit Linux or cross-platform deployment examples, and the recommended tools and services are all Microsoft-centric.
Recommendations
- Include explicit Linux/macOS command-line examples where applicable (e.g., bash, zsh).
- Mention and provide examples for deploying to non-Azure static hosts (e.g., AWS S3, Google Cloud Storage, Apache/Nginx on Linux).
- Reference cross-platform tools (such as Docker) for local development and deployment.
- Clarify that Azure CLI and Azure Functions Core Tools are cross-platform, and provide installation instructions for Linux/macOS.
- List alternative CDN and hosting providers, not just Azure CDN.
- Add a section or callout noting that all steps can be performed on Linux/macOS, and highlight any differences if they exist.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/developer-portal-basic-authentication.md
...pi-management/developer-portal-basic-authentication.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates bias towards Windows by referencing the Azure PowerShell cmdlet (New-AzApiManagementUser) as the only CLI-based method for adding users, without mentioning or providing examples for equivalent operations using cross-platform tools like Azure CLI, REST API, or scripting on Linux/macOS. No Linux or cross-platform command-line examples are given.
Recommendations
- Add equivalent Azure CLI commands for user management (e.g., az apim user create) alongside PowerShell examples.
- Mention and link to REST API documentation for user management, which is platform-agnostic.
- Explicitly state that Azure PowerShell is available cross-platform, but also provide bash/Linux/macOS-friendly examples.
- Ensure that any scripting or automation guidance is provided for both Windows (PowerShell) and Linux/macOS (bash, Azure CLI).
- Consider reordering examples so that cross-platform or Linux-friendly tools are mentioned first or alongside Windows-specific tools.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/developer-portal-faq.md
...b/main/articles/api-management/developer-portal-faq.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias, particularly in the permissions section, where only PowerShell scripts and Windows batch (.bat) scripts are provided for role creation and cleanup tasks. There are no equivalent examples or guidance for Linux or cross-platform environments (e.g., Bash, Azure CLI). Windows tools and patterns (PowerShell, .bat scripts) are mentioned exclusively and before any Linux alternatives, which are absent.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell scripts, especially for role creation and assignment.
- Include Bash shell script examples alongside .bat scripts for cleanup and automation tasks.
- Explicitly mention cross-platform compatibility and provide instructions for both Windows and Linux/macOS users.
- Where possible, use platform-agnostic tools (e.g., Azure CLI, REST API) in examples and documentation.
- Add notes or links to official documentation for performing the same tasks on Linux/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 page focuses exclusively on using the Azure portal and Power Platform web interfaces, which are typically accessed via Windows environments. There are no command-line examples (such as Azure CLI, Bash, or PowerShell), but the workflow and screenshots implicitly assume a Windows-centric user base. There is no mention of Linux or cross-platform tooling, nor are there instructions for performing these tasks via non-Windows environments or automation scripts.
Recommendations
- Include Azure CLI or REST API examples for configuring CORS policies, which can be run on any platform (Windows, Linux, macOS).
- Explicitly mention that the Azure portal and Power Platform interfaces are web-based and accessible from any OS, not just Windows.
- Add notes or examples for users who may wish to automate these tasks from Linux or macOS environments.
- If screenshots are used, consider including ones taken from browsers on Linux or macOS to reinforce cross-platform compatibility.
- Reference cross-platform developer tools (e.g., VS Code, Azure CLI) where appropriate.