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 226-250 of 594 flagged pages
API Management https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/graphql-api.md ...-docs/blob/main/articles/api-management/graphql-api.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a GraphQL API, but it gives equal prominence to PowerShell (a Windows-centric tool) and does not mention or provide native Linux shell (bash) or scripting examples. The prerequisites list Azure PowerShell as a required tool, which is primarily associated with Windows environments, and the PowerShell example is given its own dedicated section. There is no explicit Linux or bash example, nor is there mention of Linux-specific tooling or considerations.
Recommendations
  • Add explicit bash or shell script examples for Linux users alongside PowerShell examples.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • In the prerequisites, note that Azure PowerShell is optional and primarily for users who prefer PowerShell, and highlight that Azure CLI is fully supported on Linux.
  • Ensure that any references to tools or commands are balanced between Windows and Linux environments, and avoid implying that PowerShell is required.
  • Consider adding a section or note for Linux/macOS users to ensure parity and inclusivity.
API Management https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/import-app-service-as-api.md ...n/articles/api-management/import-app-service-as-api.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and workflows (such as Visual Studio Code and ASP.NET Core tutorials, which are traditionally associated with Windows development), and by omitting explicit Linux or cross-platform examples for creating and deploying web apps. There are no command-line examples (such as Bash, Azure CLI, or PowerShell), but the only development and deployment guidance references Windows-preferred technologies and patterns, with no mention of Linux alternatives or parity.
Recommendations
  • Add explicit Linux-based examples for creating and deploying web APIs, such as using the Azure CLI and Bash.
  • Include references to Linux-friendly frameworks and editors (e.g., Python Flask, Node.js, or Java Spring Boot) alongside ASP.NET Core.
  • Provide deployment instructions using cross-platform tools (e.g., Azure CLI, GitHub Actions) rather than only referencing Visual Studio Code.
  • Clarify that the steps are platform-agnostic where possible, and call out any platform-specific differences.
  • Ensure that screenshots and UI references do not assume a Windows environment.
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 →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
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 inclusion of Azure PowerShell (which is traditionally associated with Windows environments) and its parity with CLI in the documentation can be seen as a Windows bias. There are no explicit Linux-specific examples, nor is there mention of Linux-native tools or shell environments. The order of presentation (Portal, CLI, then PowerShell) is neutral, but the presence of PowerShell-specific instructions and requirements, without any Linux shell or scripting examples, may disadvantage Linux users.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell commands (e.g., bash) where appropriate.
  • Include a note or section for Linux users, clarifying that PowerShell is optional and not required on Linux.
  • Provide sample scripts using bash or other common Linux shells for tasks such as environment variable setup and command execution.
  • If referencing PowerShell, consider also referencing bash or zsh for parity, or clarify that PowerShell Core is cross-platform.
  • Add troubleshooting or environment setup notes specific to Linux (e.g., file path differences, installation steps for CLI tools on Linux).
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 →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides examples for both Azure CLI and Azure PowerShell, but there is a notable emphasis on PowerShell, which is traditionally associated with Windows environments. PowerShell is given equal prominence to Azure CLI, despite CLI being more cross-platform. There are no explicit Linux shell (bash) examples, and PowerShell is presented as a primary automation tool, which may not be as familiar or available to Linux users. Additionally, the prerequisites and instructions do not mention Linux-specific considerations or tools.
Recommendations
  • Add explicit bash (Linux shell) examples alongside PowerShell, or clarify that Azure CLI commands are cross-platform and show them in a Linux context (e.g., using bash variables and syntax).
  • In the prerequisites, mention that Azure CLI works natively on Linux/macOS and provide installation links or notes for those platforms.
  • De-emphasize PowerShell as a primary automation tool for cross-platform scenarios, or at least note that it is available on Linux/macOS but may require separate installation.
  • Ensure that screenshots and UI instructions do not assume a Windows environment (e.g., file paths, dialogs).
  • Consider including a section or callout for Linux/macOS users with tips or troubleshooting relevant to those platforms.
API Management https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/quickstart-arm-template.md ...ain/articles/api-management/quickstart-arm-template.md
High Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing the Azure portal (a web UI, but often associated with Windows workflows), mentioning Azure PowerShell before Azure CLI, and not providing explicit Linux/Unix shell examples. While Azure CLI is mentioned, there are no concrete CLI or shell command examples, and no Linux-specific guidance or screenshots are provided. The documentation implicitly assumes a Windows-centric workflow.
Recommendations
  • Provide explicit Azure CLI command-line examples for deploying and managing resources, with syntax suitable for Bash/Linux shells.
  • List Azure CLI before Azure PowerShell when mentioning alternative deployment methods, or present both equally.
  • Include screenshots or instructions that are platform-agnostic or show both Windows and Linux terminals where relevant.
  • Add a section or callout for Linux/macOS users, clarifying that all steps can be performed from any OS using Azure CLI.
  • Where possible, avoid language that implies the Azure portal is a Windows-only tool, and clarify its cross-platform nature.
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 →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page is generally platform-neutral but contains several instances of Windows bias. It references Windows-specific infrastructure and tools (such as KMS activation, Windows Update, and Windows Defender) without mentioning Linux equivalents or clarifying their relevance for non-Windows environments. Additionally, the only explicit example of a deployment model connection uses PowerShell (a Windows-centric tool) in the related content, and there are no Linux or cross-platform command examples provided.
Recommendations
  • Where Windows-specific infrastructure (e.g., KMS, Windows Update, Windows Defender) is mentioned, clarify that these steps are only required for Windows VMs and provide equivalent guidance or a statement for Linux VMs (e.g., how to handle OS updates or security for Linux).
  • In related content and examples, provide parity by including links or instructions for Linux-based management (e.g., using Azure CLI, Bash scripts, or Linux tools) alongside PowerShell/Windows examples.
  • Explicitly state when a configuration step is only relevant for Windows workloads to avoid confusion for Linux users.
  • Add a section or note summarizing any differences or additional considerations for Linux-based deployments, especially regarding network access for updates, diagnostics, and security.
  • Review all tool and endpoint references to ensure Linux users are not left without guidance for their platform.
API Management Defend API Management Against DDoS Attacks ...rticles/api-management/protect-with-ddos-protection.md
Medium Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation references enabling DDoS IP Protection for a public IP address via a linked page that uses PowerShell, but does not mention or provide examples for Linux/macOS users (such as Azure CLI or Bash). The main instructions focus on the Azure Portal, which is platform-agnostic, but the PowerShell reference creates friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for enabling DDoS IP Protection, alongside PowerShell instructions.
  • Explicitly mention that Azure CLI and Bash can be used on Linux/macOS for equivalent tasks.
  • Provide links to cross-platform command-line documentation where relevant.
API Management Add a Custom CA Certificate - API Management | Microsoft Docs ...api-management/api-management-howto-ca-certificates.md
Medium Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a PowerShell command (`New-AzApiManagementSystemCertificate`) as the only CLI example for uploading a CA certificate, without mentioning or providing equivalent Azure CLI or REST API examples. This creates friction for Linux/macOS users, as PowerShell is primarily a Windows tool and not universally available or preferred on other platforms.
Recommendations
  • Add Azure CLI example(s) for uploading a CA certificate, as Azure CLI is cross-platform.
  • Mention REST API options for certificate upload, with example requests.
  • Clarify that PowerShell is one option, and provide parity for Linux/macOS users.
  • Consider linking to documentation on using PowerShell Core on Linux/macOS if PowerShell must be used.
API Management Use Managed Identities in Azure API Management | Microsoft Docs ...t/api-management-howto-use-managed-service-identity.md
Medium Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides step-by-step instructions for creating and managing managed identities in Azure API Management using the Azure portal, Azure PowerShell, and ARM templates. However, all CLI examples are exclusively in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bash examples. The PowerShell instructions are presented before ARM template examples, and there is no mention of Linux/macOS-specific workflows or tools. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer Azure CLI.
Recommendations
  • Add Azure CLI examples for all PowerShell workflows, especially for creating and updating API Management instances with managed identities.
  • Explicitly mention that Azure CLI is cross-platform and provide links to relevant Azure CLI documentation.
  • Where possible, show both PowerShell and Azure CLI code blocks side-by-side or in tabs.
  • Clarify any limitations or differences between PowerShell and Azure CLI for these operations.
  • Consider referencing Bash scripting for ARM template deployment, which is common on Linux/macOS.
API Management Use Managed Identities in Azure API Management | Microsoft Docs ...t/api-management-howto-use-managed-service-identity.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions for creating and managing managed identities in Azure API Management using the Azure portal, Azure PowerShell, and ARM templates. However, all CLI-based examples are exclusively in Azure PowerShell, with no mention of Azure CLI or Bash equivalents. PowerShell is presented as the only scripting option, and instructions for installing Azure PowerShell reference Windows-centric guidance. There are no Linux/macOS-specific examples or notes, and PowerShell is shown before ARM templates, reinforcing Windows-first patterns.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash shell scripting examples where appropriate, or clarify that PowerShell commands can be run on Linux/macOS with PowerShell Core.
  • Mention that Azure PowerShell is available on Linux/macOS, and provide links to installation instructions for those platforms.
  • Consider presenting Azure CLI examples before or alongside PowerShell to avoid Windows-first ordering.
  • Explicitly state platform compatibility for each tool and example.
API Management Defend API Management Against DDoS Attacks ...rticles/api-management/protect-with-ddos-protection.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references enabling DDoS IP Protection via a linked page that uses PowerShell for configuration, which is traditionally Windows-centric. There are no explicit Linux/macOS CLI or Azure CLI examples on this page. The Azure portal steps are platform-neutral, but the only programmatic example referenced is PowerShell.
Recommendations
  • Add Azure CLI examples for enabling DDoS IP Protection, as Azure CLI is cross-platform and works on Linux/macOS.
  • Explicitly mention that PowerShell can be used on Linux/macOS, or provide Bash equivalents.
  • Ensure that referenced pages (such as manage-ddos-protection-powershell-ip.md) include Azure CLI and REST API instructions alongside PowerShell.
API Management Add a Custom CA Certificate - API Management | Microsoft Docs ...api-management/api-management-howto-ca-certificates.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation primarily describes uploading CA certificates via the Azure portal, which is platform-neutral. However, the only command-line example provided is the Windows PowerShell command (`New-AzApiManagementSystemCertificate`). There is no mention of Linux/macOS equivalents (such as Azure CLI or REST API usage), nor are Linux tools or workflows referenced. This creates friction for non-Windows users who prefer or require command-line automation.
Recommendations
  • Add Azure CLI examples for uploading CA certificates, as Azure CLI is cross-platform.
  • Mention REST API options for certificate management, with example requests.
  • Clarify that PowerShell is Windows-centric and provide alternatives for Linux/macOS users.
  • Consider linking to documentation on using certificates with Linux tools (e.g., OpenSSL) for certificate preparation.
API Management Use Managed Identities in Azure API Management | Microsoft Docs ...t/api-management-howto-use-managed-service-identity.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed instructions and code samples for Azure portal, Azure PowerShell, and ARM templates, but omits equivalent examples for Azure CLI (which is cross-platform and commonly used on Linux/macOS). PowerShell is featured heavily for scripting and automation, with explicit installation instructions and sample code, while no mention is made of Azure CLI or Bash scripting. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer CLI tools native to their platforms.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all tasks (creating, updating, and removing managed identities).
  • Mention Azure CLI as a supported tool for managing API Management instances and managed identities.
  • Provide Bash scripting examples where appropriate, or clarify that PowerShell scripts can be run cross-platform if true.
  • Reorder sections so that cross-platform tools (Azure CLI, ARM templates) are presented before or alongside PowerShell.
  • Explicitly state that all operations can be performed via Azure CLI, not just PowerShell.
API Management Add a Custom CA Certificate - API Management | Microsoft Docs ...api-management/api-management-howto-ca-certificates.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a PowerShell command (`New-AzApiManagementSystemCertificate`) as the only CLI example for uploading a CA certificate, without mentioning or providing equivalent Azure CLI or Bash examples. This creates friction for Linux/macOS users, as PowerShell is primarily a Windows tool and not the default shell on Linux/macOS. The rest of the instructions are portal-based and platform-agnostic.
Recommendations
  • Add Azure CLI example(s) for uploading a CA certificate, or clarify if this operation is not supported via Azure CLI.
  • If PowerShell is the only supported CLI, explicitly state this and provide guidance for Linux/macOS users on installing and using PowerShell Core.
  • Consider including Bash or REST API examples for certificate upload to improve parity.
  • Mention cross-platform alternatives before or alongside Windows/PowerShell commands.
API Management Import SOAP API to Azure API Management | Microsoft Docs ...s/blob/main/articles/api-management/import-soap-api.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides three main workflows: Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, PowerShell is presented as a first-class option, and its example is given equal prominence to CLI. There is no explicit mention of Linux/macOS compatibility for PowerShell, nor are there any Linux/macOS-specific instructions or troubleshooting tips. The CLI example is generic and cross-platform, but the PowerShell section may confuse Linux/macOS users, as Azure PowerShell is less commonly used outside Windows. No Linux-specific tools or shell examples (e.g., Bash) are provided.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform, but may require additional setup on Linux/macOS.
  • Add a Bash shell example for Azure CLI to demonstrate Linux/macOS usage.
  • Explicitly mention that the Azure CLI example works on Linux/macOS and Windows.
  • Consider adding troubleshooting notes for Linux/macOS users, such as file path conventions or authentication differences.
  • If PowerShell is not recommended for Linux/macOS, state this clearly.
API Management Defend API Management Against DDoS Attacks ...rticles/api-management/protect-with-ddos-protection.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references enabling DDoS IP Protection via a linked PowerShell-based guide, which is typically Windows-centric. There are no explicit Linux/macOS CLI examples or mentions of Azure CLI or other cross-platform tools. The guidance for enabling DDoS Protection on a public IP address points users to a PowerShell-focused workflow, potentially creating friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for enabling DDoS IP Protection, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell commands can be run on Linux/macOS using PowerShell Core, or provide Bash equivalents.
  • Where possible, provide step-by-step instructions for both Azure Portal and Azure CLI workflows.
  • Clarify tool requirements and alternatives for non-Windows users.
API Management Add a Custom CA Certificate - API Management | Microsoft Docs ...api-management/api-management-howto-ca-certificates.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a PowerShell command (`New-AzApiManagementSystemCertificate`) as the only CLI example for uploading a CA certificate, without mentioning or providing equivalent Azure CLI, Bash, or Linux/macOS-compatible methods. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples for uploading CA certificates, as Azure CLI is cross-platform and widely used.
  • Mention Bash or shell scripting alternatives where applicable.
  • Clarify if PowerShell Core (pwsh) is supported on Linux/macOS, and provide instructions if so.
  • Ensure REST API usage is documented for certificate upload, as REST APIs are platform-agnostic.
API Management Defend API Management Against DDoS Attacks ...rticles/api-management/protect-with-ddos-protection.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation references enabling DDoS IP Protection via a linked page that is PowerShell-focused, which is typically Windows-centric. There is no mention of Linux/macOS CLI alternatives or parity in the main instructions, and the PowerShell method is referenced before any CLI or portal-based options. However, the primary instructions use the Azure portal, which is cross-platform.
Recommendations
  • Add Azure CLI examples for enabling DDoS IP Protection, alongside PowerShell instructions, to ensure Linux/macOS users have clear guidance.
  • Explicitly mention that PowerShell commands can be run on Linux/macOS (via PowerShell Core), or provide equivalent Azure CLI commands.
  • Where possible, link to documentation that covers both PowerShell and Azure CLI methods, or update the referenced page to include CLI instructions.
API Management Use Managed Identities in Azure API Management | Microsoft Docs ...t/api-management-howto-use-managed-service-identity.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides step-by-step instructions for creating and managing managed identities in Azure API Management using the Azure portal, Azure PowerShell, and ARM templates. However, it exclusively features PowerShell examples for CLI-based operations, with no equivalent instructions for Azure CLI (cross-platform) or Bash scripting. PowerShell is presented as the primary scripting tool, and there are no Linux/macOS-specific examples or guidance. This creates friction for users on Linux/macOS who may prefer or require Azure CLI or Bash.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all CLI-based operations, such as creating resource groups, managed identities, and API Management instances.
  • Explicitly mention that Azure CLI is supported and provide links to relevant Azure CLI documentation.
  • Ensure that scripting instructions are not Windows-centric and clarify cross-platform compatibility.
  • Consider including Bash script snippets or references for ARM template deployments.
API Management Add a Custom CA Certificate - API Management | Microsoft Docs ...api-management/api-management-howto-ca-certificates.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a PowerShell example (`New-AzApiManagementSystemCertificate`) for uploading a CA certificate but does not mention or provide equivalent CLI, Bash, or Linux/macOS tooling. The only command-line option is Windows-centric, and no Linux/macOS alternatives or parity are discussed.
Recommendations
  • Add Azure CLI examples for uploading CA certificates, as Azure CLI is cross-platform.
  • Mention Bash or shell scripting alternatives if available.
  • Clarify if the PowerShell command can be run on PowerShell Core (cross-platform) or if it is Windows-only.
  • Provide guidance for Linux/macOS users, including any REST API or portal-based alternatives.
API Management Defend API Management Against DDoS Attacks ...rticles/api-management/protect-with-ddos-protection.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation references enabling DDoS IP Protection via a linked PowerShell guide, without mentioning or linking to equivalent Azure CLI or Bash examples. The only explicit command-line example is PowerShell, and there is no mention of Linux/macOS-friendly tooling or instructions. The Azure portal steps are platform-neutral, but the command-line guidance is Windows-centric.
Recommendations
  • Add Azure CLI examples for enabling DDoS IP Protection on public IP addresses, alongside PowerShell instructions.
  • Explicitly mention that Azure CLI and Bash can be used on Linux/macOS for relevant operations.
  • Link to cross-platform command-line documentation where possible, not only PowerShell guides.
  • Ensure parity in example ordering (e.g., show Azure CLI first or alongside PowerShell).
API Management Use Managed Identities in Azure API Management | Microsoft Docs ...t/api-management-howto-use-managed-service-identity.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides detailed instructions and code samples for Azure portal, Azure PowerShell, and ARM templates, but omits equivalent examples for Linux/macOS users, such as Azure CLI. PowerShell is emphasized for scripting, and there are no references to cross-platform tools or shell environments. This creates friction for users on Linux or macOS, as they must adapt PowerShell commands or seek external resources.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all tasks, including creating and updating managed identities.
  • Explicitly mention that Azure CLI is cross-platform and provide links to relevant CLI documentation.
  • Ensure that scripting instructions are not PowerShell-exclusive, and clarify which tools are supported on Linux/macOS.
  • Consider showing Azure CLI examples before or alongside PowerShell to emphasize platform neutrality.
API Management Use Managed Identities in Azure API Management | Microsoft Docs ...t/api-management-howto-use-managed-service-identity.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides detailed instructions for creating and managing managed identities in Azure API Management using the Azure portal, Azure PowerShell, and ARM templates. However, it exclusively offers PowerShell-based CLI examples for scripting, with no equivalent Azure CLI (az) or Bash examples. PowerShell is primarily associated with Windows, although it is cross-platform, but Azure CLI is more commonly used on Linux/macOS. The PowerShell instructions are presented before any mention of ARM templates, and there is no guidance for Linux/macOS users or explicit mention of cross-platform alternatives.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for all scripting tasks, including creating resource groups, managed identities, and API Management instances.
  • Explicitly mention that PowerShell is available cross-platform, but Azure CLI is often preferred on Linux/macOS.
  • Consider presenting Azure CLI and PowerShell examples side-by-side or in tabs, rather than PowerShell-only.
  • Include notes or links for Linux/macOS users about installing and using Azure CLI.
  • Review and update any references to Windows-centric tools or patterns to ensure Linux/macOS parity.
API Management Add a Custom CA Certificate - API Management | Microsoft Docs ...api-management/api-management-howto-ca-certificates.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a PowerShell command (`New-AzApiManagementSystemCertificate`) as the only CLI example for uploading a CA certificate, without mentioning or providing equivalent Azure CLI or Bash/Linux commands. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples for uploading CA certificates, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention if PowerShell is required and provide guidance for Linux/macOS users on how to install/use PowerShell if no alternative exists.
  • Consider including Bash or REST API examples for certificate management to ensure parity for non-Windows users.
API Management Import an OpenAPI specification to Azure API Management | Microsoft Docs ...ob/main/articles/api-management/import-api-from-oas.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, the PowerShell section is Windows-centric and lacks mention of cross-platform PowerShell Core usage on Linux/macOS. The PowerShell example is given equal prominence to CLI, but there are no explicit Linux/macOS shell examples (e.g., Bash). Additionally, there is no guidance for Linux users regarding PowerShell installation or usage, and the portal instructions do not mention platform differences.
Recommendations
  • Clarify that Azure CLI is cross-platform and works on Linux/macOS.
  • Explicitly state that Azure PowerShell can be used on Linux/macOS via PowerShell Core, and provide installation links or notes.
  • Consider adding Bash shell examples for Azure CLI usage to reinforce Linux parity.
  • Mention any platform-specific differences in the Azure portal experience, if applicable.
  • Add a short section or note for Linux/macOS users outlining recommended tools and any prerequisites.