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 176-200 of 594 flagged pages
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 First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for command-line operations, with no mention of Azure CLI or Bash scripting alternatives that are cross-platform and commonly used on Linux and macOS. Windows tools and patterns (such as PowerShell and its cmdlets) are mentioned exclusively and before any cross-platform alternatives. There are no Linux-specific or cross-platform command-line instructions, and the documentation does not acknowledge or guide users on how to perform these tasks outside of the Windows/PowerShell ecosystem.
Recommendations
- Add equivalent Azure CLI examples (az apim ...) alongside or before PowerShell examples for all operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that both Azure PowerShell and Azure CLI can be used, and provide guidance for users on different operating systems.
- Include Bash scripting examples where appropriate, especially for automation scenarios.
- Where PowerShell is referenced, clarify its availability on Linux and macOS, or provide links to installation instructions for non-Windows platforms.
- Review and update the documentation structure to avoid always presenting Windows/PowerShell first; consider leading with cross-platform tools or presenting them in parallel.
- Ensure that all screenshots and UI references are not specific to Windows-only environments.
Create Pull Request
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 First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, a tool most commonly associated with Windows environments. There are no examples using Azure CLI (which is cross-platform and preferred by many Linux users), nor are there any Bash or Linux shell script examples. The PowerShell approach is presented before ARM templates, and there is no mention of Linux-specific workflows or tools. Installation instructions and references are all for Azure PowerShell, with no equivalent guidance for Linux users.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell command sequences, as Azure CLI is cross-platform and widely used on Linux.
- Include Bash shell script examples where appropriate, especially for automation scenarios.
- When listing command-line options, present Azure CLI and PowerShell in parallel, or at least mention both, rather than only PowerShell.
- Provide installation and setup instructions for Azure CLI alongside PowerShell, with links to Linux-specific documentation.
- Review references and links to ensure Linux users are not excluded (e.g., avoid only linking to PowerShell samples).
- Consider adding a section or note explicitly stating that all operations can be performed from Linux environments using Azure CLI or ARM templates.
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 command-line examples exclusively in Azure PowerShell, which is primarily a Windows-centric tool, and by referencing PowerShell installation and usage instructions without mentioning cross-platform alternatives like Azure CLI or Bash. There are no Linux- or macOS-specific instructions or examples, and the PowerShell approach is presented before any mention of ARM templates, with no Azure CLI parity. This may hinder Linux or macOS users who prefer or require non-Windows tooling.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell command snippets, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that Azure PowerShell is available cross-platform, but also provide Bash or shell script examples where appropriate.
- In sections where PowerShell is referenced, add a parallel section or tab for Azure CLI, and consider presenting both options side-by-side.
- Include installation and usage instructions for Azure CLI alongside PowerShell, and link to relevant documentation for both.
- Review all references to Windows-specific tools or patterns and ensure Linux/macOS users are equally supported in instructions and troubleshooting.
- Consider adding a note at the top of the page clarifying that all examples are available in both PowerShell and Azure CLI, with links to both.
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 command-line examples exclusively in Azure PowerShell, referencing PowerShell installation instructions, and omitting equivalent Azure CLI (cross-platform) or Bash examples. The 'devx-track-azurepowershell' tag and repeated references to PowerShell samples reinforce this bias. No Linux- or macOS-specific instructions or examples are present, and the PowerShell approach is presented before or instead of any cross-platform alternatives.
Recommendations
- Add Azure CLI examples alongside all Azure PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash shell scripts or command snippets where appropriate, especially for ARM template deployments.
- Reference Azure CLI installation and usage guides in addition to PowerShell guides.
- Where possible, use neutral language (e.g., 'command-line' or 'terminal') instead of 'PowerShell' when introducing sections, unless the content is truly PowerShell-specific.
- Consider adding a table or section comparing PowerShell and Azure CLI commands for common tasks.
- Ensure screenshots and UI walkthroughs do not assume a Windows environment unless unavoidable.
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 exhibits a Windows bias by providing command-line examples exclusively in Azure PowerShell, referencing installation of Azure PowerShell (which is most commonly associated with Windows environments), and omitting any examples using Azure CLI (which is cross-platform and more common on Linux/macOS). There are no Bash or Linux-native shell examples, and PowerShell is always presented as the primary or only scripting interface. No mention is made of Linux-specific tooling or workflows.
Recommendations
- Add equivalent Azure CLI (az) command examples alongside all Azure PowerShell examples, especially for resource creation and identity assignment.
- Explicitly mention that Azure CLI is cross-platform and can be used from Linux, macOS, and Windows.
- Where PowerShell installation is referenced, provide a parallel reference for installing Azure CLI.
- Consider including Bash script examples or at least showing CLI commands in a Bash context.
- Review and update language to avoid implying PowerShell is the only or default automation tool.
- Add a section or note clarifying that all operations can be performed from Linux environments using Azure CLI and ARM templates.
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 command-line examples for scripting and automation, with no mention of Azure CLI (which is cross-platform and more commonly used on Linux/macOS). The PowerShell approach is presented as the default scripting method, and there are no Bash or Linux-native instructions. The documentation also references installation of Azure PowerShell, a tool most closely associated with Windows environments, and does not provide parity for Linux users.
Recommendations
- Add equivalent Azure CLI (az) command examples alongside all PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
- In sections where PowerShell is referenced, explicitly mention that Azure CLI can be used as an alternative, and provide links to relevant Azure CLI documentation.
- Ensure that installation instructions for Azure CLI are included, or at least referenced, for users on Linux and macOS.
- Where scripting examples are given, consider providing both PowerShell and Bash/Azure CLI versions, or use tabs to allow users to select their preferred environment.
- Avoid presenting PowerShell as the only or primary automation tool; instead, introduce both PowerShell and CLI approaches together.
- Review all references to Windows-specific tools or patterns and ensure Linux equivalents are mentioned with equal prominence.
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 the installation of Azure PowerShell (which is most commonly used on Windows), and omitting equivalent Azure CLI (cross-platform) or Bash examples. There are no Linux- or macOS-specific instructions, and PowerShell is presented as the default scripting tool for automation, with no mention of alternatives. This may disadvantage users on Linux or macOS, or those who prefer Azure CLI.
Recommendations
- Add Azure CLI examples alongside all PowerShell examples for creating and managing managed identities, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that Azure PowerShell can be used cross-platform, but also provide Bash or shell script equivalents where appropriate.
- When listing automation options, present Azure CLI and PowerShell together, or list Azure CLI first to avoid the impression of Windows-first bias.
- Include notes or links for Linux/macOS users on how to install and use the Azure CLI and/or PowerShell Core on their platforms.
- Where possible, provide sample ARM/Bicep templates with deployment instructions using both Azure CLI and PowerShell.
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 First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell command-line examples for scripting and automation, with no equivalent examples for Azure CLI (which is cross-platform and more commonly used on Linux/macOS). The PowerShell approach is introduced before any mention of ARM templates, and there are no Linux-native or bash shell examples. The installation instructions and sample code reference Windows-centric tools and patterns, omitting Linux-friendly alternatives.
Recommendations
- Add Azure CLI examples alongside all Azure PowerShell examples, especially for creating and managing managed identities and API Management instances.
- When introducing command-line automation, present Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
- Explicitly mention that both Azure CLI and PowerShell are supported, and link to cross-platform installation guides.
- Include bash shell scripting examples where appropriate, or at least note that all CLI commands work in Linux/macOS terminals.
- Where possible, provide parity in screenshots and UI instructions for Linux/macOS users (for example, referencing Azure Cloud Shell, which is cross-platform).
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
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation demonstrates a Windows bias by providing only Azure PowerShell examples for command-line operations, with no mention or examples of Azure CLI (which is cross-platform and commonly used on Linux/macOS). Instructions for installing and using PowerShell are included, but there are no equivalent steps or code snippets for Linux users. The documentation refers to 'PowerShell samples' and does not mention Bash, shell scripting, or Linux-specific tools. This may make it less accessible or intuitive for Linux users.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell code snippets, including resource creation, identity assignment, and updates.
- Include installation and usage instructions for Azure CLI, especially for Linux/macOS environments.
- Where referencing 'PowerShell samples', also link to or mention Azure CLI samples if available.
- In step-by-step instructions, present both PowerShell and CLI options, or indicate which are cross-platform.
- Review terminology to ensure it is inclusive of non-Windows environments (e.g., avoid assuming PowerShell is the default shell).
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 command-line examples exclusively in Azure PowerShell, referencing PowerShell installation, and omitting equivalent Azure CLI (cross-platform) or Bash examples. The PowerShell sections are prominent and detailed, while Linux-native or cross-platform command-line options are not mentioned. This may hinder accessibility for Linux and macOS users who prefer or require Azure CLI or Bash scripting.
Recommendations
- Add Azure CLI examples alongside all PowerShell examples for creating and managing managed identities, including resource creation, updates, and assignments.
- Explicitly mention that Azure CLI is cross-platform and provide installation links for Linux/macOS users.
- Where PowerShell is referenced, add a parallel section for Azure CLI (or Bash) and ensure both are kept up-to-date.
- In introductory sections and step-by-step guides, avoid assuming PowerShell as the default tool; instead, present both PowerShell and CLI options or let users choose.
- Review all references to Windows-specific tools or patterns and provide Linux/macOS equivalents where applicable.
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 command-line examples for scripting and automation, with no mention or examples of Azure CLI (cross-platform) or Bash scripting. The installation and usage instructions reference only PowerShell, which is traditionally associated with Windows, and there is no guidance for Linux or macOS users. The structure also presents PowerShell before ARM templates, and there are no Linux-native tools or shell examples provided.
Recommendations
- Add equivalent Azure CLI (az) command examples alongside PowerShell for all scripting/automation tasks.
- Include Bash shell script examples where appropriate, especially for resource creation and management.
- Explicitly mention that Azure CLI and ARM templates are cross-platform and can be used on Linux, macOS, and Windows.
- Reorder sections or provide parallel examples so that Windows and Linux users see their options equally (e.g., 'Azure CLI', 'Azure PowerShell', 'ARM template').
- Reference installation guides for Azure CLI on Linux and macOS, not just PowerShell.
- Where screenshots or UI steps are shown, clarify if there are any platform-specific differences.
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 examples for Linux or cross-platform tools (e.g., curl, bash). The use of PowerShell-specific cmdlets (Invoke-RestMethod, ConvertTo-Json, Write-Host) assumes a Windows environment. There are no CLI or bash/curl examples, and the only automation guidance is Windows-centric. Additionally, the inclusion of Azure PowerShell requirements in prerequisites and the absence of Linux or cross-platform tooling references further reinforce this bias.
Recommendations
- Add equivalent Linux/cross-platform examples using curl and bash for generating tokens and calling APIs.
- Include Azure CLI examples where possible, as it is cross-platform.
- Explicitly mention that the PowerShell examples are for Windows and provide alternative instructions for Linux/macOS users.
- Remove or supplement the Azure PowerShell requirements note with information about using other tools on non-Windows platforms.
- Ensure that all automation and scripting examples are provided in both PowerShell and bash/curl formats to support parity.
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 providing PowerShell cmdlet examples (e.g., New-AzApiManagementApiRelease, Update-AzApiManagementApiRelease) for managing API revisions, without mentioning or providing equivalent examples for Linux/macOS users (such as Azure CLI or REST API). The only automation tool referenced is PowerShell, which is traditionally associated with Windows environments, and there are no cross-platform command examples.
Recommendations
- Add 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 for revision management tasks, which are platform-agnostic.
- When mentioning automation tools, list Azure CLI and REST API before or alongside PowerShell to avoid implying Windows-first workflows.
- Explicitly state that all operations can be performed from any OS using Azure CLI or REST API, and provide links to relevant documentation.
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. It references PowerShell cmdlets (New-AzApiManagementBackend, Set-AzApiManagementBackend) as the primary automation method, which are Windows-centric tools. There is no mention of Azure CLI, Bash, or Linux scripting alternatives, and no explicit Linux or cross-platform guidance for these tasks.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell cmdlets, especially for disabling certificate chain validation.
- Include Bash or shell script snippets where appropriate, or clarify if tasks can be performed cross-platform.
- Explicitly state that PowerShell Core is cross-platform if that is intended, or provide instructions for Linux users.
- Mention and demonstrate how to perform certificate management tasks using REST API with curl or similar Linux tools.
- Ensure that all automation and scripting guidance is presented in a platform-neutral way, or provide parallel examples for both Windows and Linux environments.
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
Windows First
Summary
The documentation page demonstrates a Windows bias by providing PowerShell examples for logger creation, referencing Azure PowerShell cmdlets, and omitting equivalent CLI or scripting examples for Linux/macOS users. The PowerShell example is the only imperative command-line example given, with no Azure CLI, Bash, or cross-platform scripting alternatives. This may disadvantage users on non-Windows platforms or those who prefer cross-platform tools.
Recommendations
- Add Azure CLI examples for logger creation and management, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash shell script examples where appropriate, especially for tasks like constructing REST API requests.
- When referencing tools, mention Azure CLI and PowerShell together, or list Azure CLI first to avoid the impression of Windows-first bias.
- Explicitly state that all configuration steps can be performed from any OS using REST API, Azure CLI, or ARM/Bicep templates, and provide links or examples.
- Where PowerShell is used, provide a side-by-side Azure CLI or Bash equivalent to ensure parity for Linux/macOS users.
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 a bias toward Windows by referencing the Azure PowerShell cmdlet (New-AzApiManagementUser) as the only CLI-based method for adding users, without mentioning or providing examples for cross-platform tools such as Azure CLI. There are no Linux-specific or cross-platform command-line examples, and the only automation tool mentioned is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Include equivalent Azure CLI commands for adding users to Azure API Management, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell is available cross-platform, but also provide Bash or shell script examples where appropriate.
- Add a section or note highlighting cross-platform tooling options for managing users, such as REST API calls or Azure CLI, to ensure parity for Linux and macOS users.
- Where possible, avoid referencing only Windows-centric tools or provide them alongside Linux-friendly alternatives.
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 command-line examples exclusively in Azure PowerShell, referencing PowerShell installation, and omitting equivalent Azure CLI (cross-platform) or Bash examples. The instructions for scripting and automation are tailored to Windows users, with no mention of Linux or macOS workflows. Windows tooling and terminology are prioritized, and Linux users are not given parity in guidance.
Recommendations
- Add Azure CLI examples alongside all PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that both Azure PowerShell and Azure CLI can be used, and provide links to both sets of documentation.
- Where possible, provide Bash shell script snippets for automation tasks, or clarify that the steps are not OS-specific.
- In sections that reference installing PowerShell, also reference installing Azure CLI and provide platform-agnostic instructions.
- Review and update terminology to avoid implying that PowerShell is the default or only scripting environment.
- Ensure screenshots and UI instructions are not specific to Windows unless unavoidable, and clarify when steps are identical across platforms.
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 Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows and Azure-specific tools and workflows. It exclusively references Azure CLI, Azure Functions Core Tools, and Azure CDN, with no mention of Linux-specific workflows, alternative open-source tools, or cross-platform deployment patterns. All command-line examples assume a Windows/Azure-centric environment and do not address Linux-specific nuances or alternatives.
Recommendations
- Include explicit notes confirming that all CLI tools and commands work equally on Linux, macOS, and Windows, or provide platform-specific instructions where differences exist.
- Mention and provide examples for deploying to non-Azure static hosts (e.g., AWS S3, Google Cloud Storage, or generic Nginx/Apache setups) to illustrate cross-platform parity.
- List open-source or cross-platform alternatives to Azure CDN, such as Cloudflare or Fastly, and provide example configurations.
- Clarify that Azure Functions Core Tools and Azure CLI are cross-platform, and provide installation instructions for Linux and macOS.
- Where possible, use generic shell commands (e.g., bash) and avoid Windows-specific command syntax or tools.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting PowerShell examples and instructions before CLI (Bash) or REST alternatives. The PowerShell section is more detailed, and the use of PowerShell-specific cmdlets and variable syntax is emphasized. There is no mention of Linux-specific shell environments or tools, and the CLI examples, while present, are secondary. The documentation assumes familiarity with PowerShell and Windows-centric tools, which may disadvantage Linux users.
Recommendations
- Present CLI (Bash) examples before or alongside PowerShell examples, or alternate their order to avoid always prioritizing Windows tools.
- Expand CLI (Bash) sections to match the level of detail and explanation given in PowerShell sections.
- Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide guidance for Linux users where appropriate.
- Include notes or links for installing and using Azure CLI and PowerShell on Linux, highlighting cross-platform compatibility.
- Where possible, provide examples using native Linux tools or scripting (e.g., Bash scripts) for automation scenarios.
- Avoid assuming PowerShell as the default automation tool; clarify that both PowerShell and CLI are equally supported.
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 a Windows bias primarily through its references and examples. It mentions connecting virtual networks using PowerShell (a Windows-centric tool) in the 'Related content' section, and does not provide equivalent guidance or examples for Linux users (e.g., Azure CLI, Bash). There are no Linux or cross-platform command-line examples, and the only automation tool referenced is PowerShell. This may make the documentation less accessible or actionable for users on Linux or macOS platforms.
Recommendations
- Include Azure CLI (az) command examples alongside or instead of PowerShell for all relevant operations, especially in 'Related content' and any procedural sections.
- When referencing automation or scripting, mention both PowerShell and Bash/CLI options, or provide links to both.
- Avoid listing Windows/PowerShell tools first or exclusively; ensure parity by presenting cross-platform tools and workflows.
- Add explicit notes or links for Linux/macOS users where procedures may differ, especially for network configuration and DNS setup.
- Audit related documentation links to ensure they do not disproportionately point to Windows/Powershell-specific guidance.
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 primarily through the exclusive use of Azure PowerShell examples for command-line logger creation, with no equivalent Azure CLI, Bash, or Linux-native scripting examples. The PowerShell example is presented as the only imperative command-line method, and there is no mention of cross-platform tools or guidance for Linux/macOS users. This may hinder accessibility for users on non-Windows platforms.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell command-line snippets, especially for logger creation and management.
- Explicitly mention that Azure CLI and PowerShell are both supported, and clarify cross-platform compatibility.
- Where PowerShell is used, provide Bash or shell script alternatives for Linux/macOS users.
- Review the order of example presentation to avoid always listing Windows/PowerShell first; consider parallel tabbed examples for PowerShell and CLI.
- Include a note in the prerequisites or relevant sections about cross-platform tooling and links to Azure CLI documentation.
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 is heavily oriented toward the Azure Portal and Power Platform GUIs, which are web-based and cross-platform, but it implicitly assumes a Windows-centric workflow by referencing Power Platform and Power Apps/Automate (which are most commonly used in Windows environments). There are no CLI, PowerShell, or Linux shell examples, nor is there mention of using Azure CLI or other cross-platform tools. Troubleshooting recommendations mention 'developer tools in your browser' and 'Application Insights', but do not provide parity for Linux command-line users or scripting approaches.
Recommendations
- Add Azure CLI and/or Azure PowerShell examples for configuring CORS policies, with explicit mention of cross-platform compatibility.
- Include Linux shell (bash) command examples for relevant API calls or configuration steps.
- Mention and provide examples for using cross-platform tools (e.g., Azure CLI) before or alongside GUI instructions.
- Clarify that the steps can be performed from any OS, and provide links to documentation for Linux and macOS users.
- If possible, provide automation scripts (e.g., bash, PowerShell Core) for bulk or repeatable CORS policy configuration.
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 strong Windows bias, particularly in its use of Azure PowerShell for all command-line examples and the exclusive reference to the Azure Portal (a web UI that is most familiar to Windows users). There are no equivalent examples using cross-platform tools such as Bash, curl, or Azure CLI, which are more common in Linux and macOS environments. The documentation does not mention or provide Linux-native workflows, and the only scripting examples are in PowerShell, a Windows-centric shell (despite its cross-platform availability, it is still less common on Linux).
Recommendations
- Provide equivalent examples using Bash and curl for token generation and API calls.
- Include Azure CLI commands for relevant operations, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that PowerShell examples can be run on Linux/macOS, or provide installation instructions for PowerShell Core if required.
- Where possible, use generic HTTP tools (e.g., curl, httpie) for API calls to demonstrate platform-agnostic workflows.
- Balance the order of examples: present Linux/cross-platform examples before or alongside Windows/PowerShell examples.
- Reference Linux/macOS environments in prerequisites and instructions, not just Windows/Portal-centric workflows.
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 page 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, Bash, Azure CLI, or cross-platform scripting options. The focus on PowerShell and absence of Linux or cross-platform alternatives indicates a strong Windows bias.
Recommendations
- Include equivalent examples using Azure CLI, which is cross-platform and widely used on Linux.
- Provide Bash script samples for managing Azure API Management via Azure Automation.
- Mention and link to documentation for using Azure Automation with Python or other cross-platform scripting languages.
- Clearly state that Azure Automation supports non-Windows runbooks and provide guidance for Linux users.
- Ensure that references to PowerShell are balanced with references to other tools and languages where possible.
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 creating custom roles, referencing Azure PowerShell before Azure CLI in tool lists, and omitting equivalent Azure CLI or Bash examples that would be more familiar to Linux/macOS users. This may make it less accessible for users on non-Windows platforms.
Recommendations
- Add equivalent Azure CLI examples alongside PowerShell code blocks for all role management tasks.
- When listing tools (Azure PowerShell, Azure CLI, REST API), alternate the order or mention Azure CLI first in some instances to avoid a 'Windows-first' impression.
- Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI or REST API, and provide links or examples.
- Consider including Bash script examples or cross-platform instructions where possible.
- Review and update the 'ms.custom' metadata to reflect cross-platform parity, not just Azure PowerShell.