API Management

548
Total Pages
499
Linux-Friendly Pages
49
Pages with Bias
8.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

112 issues found
Showing 51-75 of 112 flagged pages
API Management Quickstart - Create Azure API Management Instance - ARM Template ...ain/articles/api-management/quickstart-arm-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily describes deploying an Azure API Management instance using the Azure portal, with only brief mentions of Azure PowerShell and Azure CLI as alternative methods. There are no explicit examples or instructions for using Azure CLI (which is cross-platform and preferred on Linux/macOS), nor are Linux-specific patterns or screenshots shown. The mention of PowerShell and CLI is generic and comes after the portal workflow, with no parity in step-by-step guidance for non-Windows users.
Recommendations
  • Add explicit, step-by-step instructions for deploying the ARM template using Azure CLI, including example commands.
  • Provide Linux/macOS screenshots or clarify that the CLI instructions work on all platforms.
  • List CLI and PowerShell deployment methods before or alongside the portal method, not only as an afterthought.
  • Ensure all resource management (review, cleanup) steps include CLI examples, not just portal navigation.
GitHub Create Pull Request
API Management Azure API Management policy reference - set-backend-service | Microsoft Docs .../articles/api-management/set-backend-service-policy.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions PowerShell as a management tool for backend entities, but does not mention or provide examples for Linux/macOS equivalents such as Azure CLI or Bash scripting. No Linux-specific tools or examples are provided, and the management options are listed with PowerShell as the only command-line tool. All code examples are platform-neutral XML, but the management tooling reference is Windows-centric.
Recommendations
  • Add references and examples for Azure CLI commands for managing backend entities, which are cross-platform.
  • Mention Bash scripting or other Linux/macOS-compatible tools alongside PowerShell.
  • Explicitly state that management can be performed from Linux/macOS using Azure CLI or REST API.
  • Provide example commands for both PowerShell and Azure CLI where relevant.
GitHub Create Pull Request
API Management Subscriptions in Azure API Management | Microsoft Docs ...rticles/api-management/api-management-subscriptions.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions Azure PowerShell as a tool for automating subscription key management workflows, but does not mention Linux/macOS equivalents such as Azure CLI or REST API usage. No platform-specific examples are provided, but the only automation tool referenced is Windows-centric, and Linux alternatives are omitted.
Recommendations
  • Explicitly mention Azure CLI and REST API as cross-platform alternatives to Azure PowerShell for automating subscription key management.
  • Provide example commands for Azure CLI and REST API usage alongside PowerShell references.
  • Clarify that Azure PowerShell is available on Linux/macOS, or link to installation instructions for non-Windows platforms.
  • Ensure that all tooling recommendations are platform-neutral or that Linux/macOS equivalents are given equal prominence.
GitHub Create Pull Request
API Management Backup and restore your Azure API Management instance for disaster recovery ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are presented first and in greater detail, with explicit variable setup and multiple scenarios (system-assigned/user-assigned managed identity). The prerequisites section highlights Azure PowerShell installation before mentioning CLI or REST. The use of PowerShell-specific cmdlets (Backup-AzApiManagement, Restore-AzApiManagement) and references to Windows-centric tooling (PowerShell) are prominent. Although Azure CLI and REST examples are provided, they are less detailed and appear after PowerShell, suggesting a Windows-first approach.
Recommendations
  • Present CLI (Bash) examples before or alongside PowerShell examples to avoid Windows-first ordering.
  • Expand CLI examples to match the detail and scenario coverage of PowerShell (e.g., managed identity variants).
  • Add explicit notes or sections for Linux/macOS users, including installation and usage tips for Azure CLI.
  • Balance the documentation by referencing cross-platform tools (CLI, REST) equally with PowerShell.
  • Consider adding troubleshooting or environment-specific guidance for Linux/macOS users.
GitHub Create Pull Request
API Management Securely Access Products and APIs - Microsoft Entra Applications - Azure API Management ...docs/blob/main/articles/api-management/applications.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only Azure PowerShell examples for generating OAuth tokens and calling APIs, with no equivalent Linux/macOS shell (e.g., Bash/cURL) examples. The use of PowerShell and Invoke-RestMethod is Windows-centric, and Windows tools are mentioned exclusively for scripting tasks. This creates friction for Linux and macOS users who may not have PowerShell installed or prefer native tools.
Recommendations
  • Add equivalent Bash/cURL examples for generating tokens and calling APIs, alongside PowerShell scripts.
  • Explicitly mention that the PowerShell scripts can be run cross-platform (if true), or provide guidance for Linux/macOS users.
  • Where possible, use generic REST API calls with cURL or HTTPie in addition to PowerShell.
  • Clarify prerequisites for scripting, including installation instructions for PowerShell on Linux/macOS if it is required.
GitHub Create Pull Request
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-01-11 06:20
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, which is Windows-centric. There is no mention of Linux/macOS equivalents (such as Azure CLI or REST API usage) for this operation, nor are Linux tools or workflows referenced. This creates friction for non-Windows users who may not have access to PowerShell.
Recommendations
  • Add Azure CLI examples for uploading CA certificates, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API example for certificate upload, with sample curl commands.
  • Explicitly mention platform compatibility for each method (PowerShell, CLI, REST API) and recommend cross-platform options.
  • Consider listing Linux/macOS methods before or alongside Windows/PowerShell methods to avoid implicit prioritization.
GitHub Create Pull Request
API Management Revisions in Azure API Management | Microsoft Docs ...in/articles/api-management/api-management-revisions.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation references PowerShell cmdlets (New-AzApiManagementApiRelease, Update-AzApiManagementApiRelease) as the only CLI examples for managing API revisions, without mentioning or providing equivalent Azure CLI, Bash, or Linux/macOS instructions. This creates friction for non-Windows users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples for all revision management tasks alongside PowerShell examples.
  • Explicitly mention cross-platform alternatives to PowerShell, such as Bash scripts or REST API calls.
  • Ensure that instructions for taking revisions offline, setting current revisions, and updating change logs are available for Linux/macOS users.
  • Where PowerShell is referenced, clarify its availability on Linux/macOS or provide links to installation guides.
GitHub Create Pull Request
API Management How to Log Events to Azure Event Hubs in Azure API Management | Microsoft Docs .../api-management/api-management-howto-log-event-hubs.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is the only CLI tool shown for imperative logger creation, with no equivalent Azure CLI, Bash, or Linux/macOS shell examples. The PowerShell example is presented before declarative options (Bicep/ARM), and no cross-platform command-line alternatives are mentioned. This may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Add Azure CLI examples for logger creation, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell is available cross-platform, or provide Bash/shell script alternatives.
  • Present cross-platform tools (Azure CLI, REST API) before or alongside PowerShell to avoid Windows-first ordering.
  • Include notes or links for Linux/macOS users on how to perform equivalent tasks without PowerShell.
GitHub Create Pull Request
API Management How to use role-based access control in Azure API Management | Microsoft Docs ...management/api-management-role-based-access-control.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing only PowerShell examples for custom role creation and assignment, referencing Azure PowerShell in metadata and examples, and omitting equivalent Azure CLI or REST API examples. While Azure CLI and REST API are mentioned as alternative tools for role assignment, no concrete examples or code snippets are provided for Linux/macOS users, making the guidance less accessible for those platforms.
Recommendations
  • Add Azure CLI examples for custom role creation and assignment alongside PowerShell examples.
  • Provide REST API sample requests for key operations, especially those currently shown only in PowerShell.
  • Ensure that examples for Linux/macOS-friendly tools (CLI, REST) are presented before or alongside Windows/PowerShell examples.
  • Review metadata and custom tags to avoid reinforcing PowerShell as the default or only approach.
GitHub Create Pull Request
API Management Secure API Management Backend Using Client Certificate Authentication ...management/api-management-howto-mutual-certificates.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias towards Windows by providing PowerShell-only examples for disabling certificate chain validation, referencing Windows-centric Azure PowerShell cmdlets, and omitting equivalent Linux/macOS command-line instructions (such as Azure CLI or bash). Windows tools and patterns are mentioned exclusively, and no Linux/macOS alternatives are provided or referenced. The PowerShell example appears before the REST API alternative, reinforcing the Windows-first approach.
Recommendations
  • Add Azure CLI examples for all PowerShell cmdlets shown, especially for disabling certificate chain validation.
  • Include bash or shell script snippets for certificate management tasks where applicable.
  • Explicitly mention cross-platform tools and workflows, clarifying which steps are OS-agnostic.
  • Reorder examples to present REST API or CLI options before or alongside PowerShell.
  • Provide guidance for Linux/macOS users on prerequisites and environment setup.
GitHub Create Pull Request
API Management Use API Management in a virtual network with Azure Application Gateway ...pi-management-howto-integrate-internal-vnet-appgateway.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses Azure PowerShell for all setup and configuration steps, with no mention or examples of Azure CLI, Bash, or cross-platform alternatives. File paths and certificate management are shown in Windows format (e.g., C:\Users\Contoso\), and there is no guidance for Linux/macOS users regarding equivalent commands or file system conventions. This creates friction for non-Windows users and may hinder their ability to follow the guide without significant adaptation.
Recommendations
  • Provide equivalent Azure CLI examples for all major steps, alongside PowerShell.
  • Use cross-platform file path examples or note Linux/macOS equivalents (e.g., /home/contoso/).
  • Add notes or sections for certificate management on Linux/macOS (e.g., using OpenSSL).
  • Explicitly state that the steps can be performed on Linux/macOS and provide troubleshooting tips for common platform differences.
  • Reference Bash or shell scripting alternatives where appropriate.
GitHub Create Pull Request
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-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions and code samples for Azure PowerShell, but does not mention or provide equivalent examples for Azure CLI or other cross-platform tools. PowerShell is featured as the only command-line automation method, and its installation instructions are referenced, which can create friction for Linux/macOS users who may prefer or already use Azure CLI. Portal and ARM template instructions are platform-neutral, but command-line automation is Windows-centric.
Recommendations
  • Add equivalent Azure CLI examples alongside PowerShell for all command-line operations, including creating and updating managed identities.
  • Explicitly mention that Azure CLI is supported and provide links to Azure CLI documentation.
  • Where PowerShell installation is referenced, also reference Azure CLI installation for Linux/macOS users.
  • Ensure that cross-platform command-line instructions are presented in parallel, or at least alternate which is shown first.
GitHub Create Pull Request
API Management Manage Azure API Management using Azure Automation ...les/api-management/automation-manage-api-management.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively references Azure PowerShell cmdlets and PowerShell workflow scripts for managing Azure API Management via Azure Automation. It does not mention or provide examples for Bash, Azure CLI, or other Linux/macOS-friendly tools. All sample links and tutorials are PowerShell-centric, implying a Windows-first approach and omitting Linux/macOS equivalents.
Recommendations
  • Add examples using Azure CLI for API Management tasks within Azure Automation.
  • Include Bash or Python script samples for automation scenarios.
  • Explicitly mention cross-platform compatibility of Azure Automation and clarify how Linux/macOS users can author and run automation scripts.
  • Provide links to documentation or tutorials for non-PowerShell automation in Azure Automation.
GitHub Create Pull Request
API Management Azure API Management - API version retirements (June 2024) | Microsoft Docs ...nt/breaking-changes/api-version-retirement-sep-2023.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias by listing Azure PowerShell (a Windows-centric tool) alongside Azure CLI, and providing PowerShell-specific commands and update instructions. PowerShell examples are given equal prominence to CLI, and Windows tools are referenced before Linux equivalents in some cases. There are no explicit Linux/macOS examples or instructions, and no mention of platform-specific considerations for updating tools or running scripts.
Recommendations
  • Explicitly mention that Azure CLI and Terraform are cross-platform and provide Linux/macOS-specific instructions or notes where relevant.
  • Include examples for checking/updating Azure CLI and Terraform on Linux/macOS (e.g., using apt, yum, or Homebrew).
  • Clarify that PowerShell Core is available on Linux/macOS, and provide installation/update instructions for those platforms.
  • Avoid listing Windows-centric tools (PowerShell) before cross-platform tools (CLI, Terraform) unless contextually justified.
  • Add a note or section addressing platform differences in tool usage and updates.
GitHub Create Pull Request
API Management Developer portal - Frequently asked questions ...b/main/articles/api-management/developer-portal-faq.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias, particularly in sections related to permissions and role assignment. All scripting examples use PowerShell, with no Bash, Azure CLI, or Linux/macOS alternatives. The only explicit script for portal cleanup is a Windows batch file (.bat), and there are no instructions for running these tasks on Linux or macOS. Windows tools and patterns (PowerShell, .bat scripts) are referenced exclusively and appear before any mention of cross-platform or Linux-native approaches.
Recommendations
  • Provide Azure CLI or Bash script equivalents for all PowerShell examples, especially for role creation and assignment.
  • Offer instructions or scripts for portal cleanup using Bash (.sh) or cross-platform tools.
  • Explicitly mention that tasks can be performed on Linux/macOS and link to relevant cross-platform documentation.
  • When listing scripts or commands, present cross-platform (CLI/Bash) options before or alongside Windows-specific examples.
  • Clarify any platform-specific limitations or requirements for the provided scripts.
GitHub Create Pull Request
API Management Manage Connections for End Users - Azure API Management | Microsoft Docs ...es/api-management/credentials-how-to-user-delegated.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, especially in the initial provisioning steps. Step 1 exclusively uses Azure PowerShell and the AzureAD module, with no mention of Linux/macOS alternatives (such as Azure CLI or cross-platform scripting). The PowerShell example is presented first and solely, and there are no equivalent Linux/macOS instructions for service principal provisioning. The rest of the guide relies on the Azure portal (web-based), which is cross-platform, but the critical initial step creates friction for non-Windows users.
Recommendations
  • Provide equivalent Azure CLI commands for service principal provisioning, which work on Linux/macOS.
  • Explicitly mention cross-platform alternatives to PowerShell (e.g., Bash, Azure CLI) in the prerequisites and steps.
  • Add notes or links for Linux/macOS users on how to install and use Azure CLI.
  • Reorder examples to present cross-platform options first or side-by-side with Windows-specific instructions.
GitHub Create Pull Request
API Management Set up basic authentication to developer portal ...pi-management/developer-portal-basic-authentication.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias by referencing the Azure PowerShell cmdlet (New-AzApiManagementUser) as the only command-line tool for adding users, without mentioning Linux/macOS equivalents such as Azure CLI or REST API. This may create friction for non-Windows users who do not use PowerShell.
Recommendations
  • Include Azure CLI examples for adding users, which are cross-platform and widely used on Linux/macOS.
  • Mention REST API methods for user management, providing platform-neutral options.
  • Clarify that PowerShell is available on Linux/macOS, but also provide instructions for installing and using it on those platforms.
  • Present command-line examples for both PowerShell and Azure CLI, ideally side-by-side.
GitHub Create Pull Request
API Management Add a GraphQL API to Azure API Management | Microsoft Docs ...-docs/blob/main/articles/api-management/graphql-api.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a GraphQL API, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is included as a main method. The prerequisites section lists Azure PowerShell alongside Azure CLI, and the PowerShell example is detailed and uses Windows-specific patterns. There are no Linux/macOS-specific instructions or notes, and PowerShell is not natively available on most Linux/macOS systems. The order of examples is Portal, CLI, then PowerShell, which is not overtly Windows-first, but the inclusion of PowerShell as a primary method signals a Windows bias.
Recommendations
  • Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add explicit notes for Linux/macOS users, such as installation instructions for Azure CLI and mention that PowerShell is optional and not required.
  • Consider providing bash or shell script examples for Linux users, or at least note that Azure CLI commands work natively in bash/zsh.
  • If PowerShell is included, add a note about PowerShell Core availability on Linux/macOS, or link to installation instructions.
  • Reorder examples to show Azure CLI before PowerShell, and clarify platform compatibility in each section.
GitHub Create Pull Request
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-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing a SOAP API, but PowerShell is given equal prominence and is referenced as a prerequisite tool. PowerShell is a Windows-centric tool, and its inclusion alongside CLI may suggest a Windows bias, especially since no Linux/macOS-specific shell examples (e.g., Bash, zsh) or notes about cross-platform usage are provided. Additionally, PowerShell is mentioned in the prerequisites before the actual import instructions, reinforcing its importance. There are no explicit Linux/macOS examples or troubleshooting notes.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and highlight its usage for Linux/macOS users.
  • Add notes or examples for Linux/macOS users, such as Bash or zsh shell usage, especially for environment variable syntax.
  • Indicate that PowerShell Core is available cross-platform, or provide links to installation instructions for non-Windows systems.
  • Consider listing Azure CLI examples before PowerShell, or mark PowerShell as optional for Windows users.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., file path differences, authentication).
GitHub Create Pull Request
API Management Defend API Management Against DDoS Attacks ...rticles/api-management/protect-with-ddos-protection.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation references enabling DDoS protection via the Azure portal and links to a PowerShell-based guide for managing DDoS IP Protection, but does not provide equivalent CLI (az), Bash, or Linux/macOS-specific instructions. This creates a bias toward Windows users, especially in automation or scripting contexts.
Recommendations
  • Add Azure CLI (az) command examples for enabling DDoS protection on VNets and public IPs.
  • Include Bash script snippets for Linux/macOS users where PowerShell is referenced.
  • Explicitly mention that all steps can be performed cross-platform using Azure CLI, and provide links or examples.
  • Reorder or balance references so that PowerShell and CLI examples are presented together, or CLI first.
GitHub Create Pull Request
API Management VNet configuration settings | Azure API Management ...n/articles/api-management/virtual-network-reference.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows Specific Section
Summary
The documentation is largely platform-neutral, focusing on Azure networking concepts and service tags. However, there is a dedicated section ('KMS endpoint') describing configuration steps specifically for Windows VMs, including Windows activation via KMS. Additionally, endpoints for Windows Update and Windows Defender are listed under 'Internal infrastructure and diagnostics', which are only relevant for Windows-based infrastructure. There are no equivalent Linux/macOS-specific instructions or mentions (e.g., for Linux activation, package updates, or security tools).
Recommendations
  • Add guidance for Linux VMs in the VNet, such as required outbound ports for common Linux update mechanisms (e.g., apt, yum, zypper) or security services.
  • Clarify that Windows-specific sections (KMS, Windows Update, Windows Defender) are only relevant for Windows VMs, and provide parity for Linux/macOS where applicable.
  • If there are platform-specific networking requirements for Linux/macOS, include them alongside Windows instructions.
  • Consider adding a table or section summarizing platform-specific requirements for both Windows and Linux/macOS VMs in the VNet.
GitHub Create Pull Request
API Management Quickstart - Create Azure API Management instance - Terraform ...b/main/articles/api-management/quickstart-terraform.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides verification steps using Azure CLI and Azure PowerShell, with PowerShell examples included. While Azure CLI is cross-platform, PowerShell is primarily associated with Windows. There are no explicit Linux/macOS shell examples (e.g., Bash), nor is there mention of Linux-specific tools or patterns. The order of presentation puts Azure CLI first, which is positive, but the inclusion of PowerShell without equivalent Bash examples may create friction for Linux/macOS users.
Recommendations
  • Add Bash shell examples for verification steps, showing how to run equivalent commands on Linux/macOS.
  • Clarify that Azure CLI commands work on all platforms and highlight any platform-specific considerations.
  • If PowerShell is included, consider mentioning cross-platform PowerShell Core, or provide equivalent Bash commands.
  • Explicitly state that all steps can be performed on Linux/macOS and Windows, and note any differences.
GitHub Create Pull Request
API Management https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/how-to-deploy-self-hosted-gateway-container-apps.md ...nt/how-to-deploy-self-hosted-gateway-container-apps.md
Medium Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, but PowerShell (Windows) examples are always presented immediately after Bash, and sometimes the syntax comments and code are more detailed for PowerShell. There are no Linux-specific tools or patterns mentioned, and the Azure portal (web UI) is referenced throughout, which is platform-agnostic. However, the documentation does not provide any Linux-specific troubleshooting, nor does it mention Linux-native shells beyond Bash, and the structure implicitly prioritizes Windows parity by always including PowerShell examples.
Recommendations
  • Ensure that Bash examples are always presented first, as is currently done, but consider including a note that Bash examples are suitable for Linux and macOS users.
  • Add explicit statements clarifying that all Azure CLI commands work identically on Linux, macOS, and Windows (with Bash or PowerShell).
  • Where PowerShell-specific syntax is explained, provide equivalent explanations for Bash (e.g., variable assignment, line continuation).
  • Consider including troubleshooting tips or common issues for Linux environments, such as permissions or shell differences.
  • If possible, add examples or notes for other popular Linux shells (e.g., zsh, fish) or clarify that Bash examples are compatible with these.
  • Review for any subtle language that assumes a Windows-first audience and adjust to be more platform-neutral.
GitHub Create Pull Request
API Management https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/import-function-app-as-api.md .../articles/api-management/import-function-app-as-api.md
Medium Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes using the Azure Portal GUI for all operations and does not provide any command-line examples. While it does not explicitly mention Windows tools like PowerShell or CMD, the only alternative tool referenced is Visual Studio Code (which is cross-platform but often associated with Windows). There are no examples using Azure CLI, Bash, or other Linux-native tools, nor is there any mention of Linux-specific workflows. The documentation assumes use of the Azure Portal, which is platform-agnostic but often perceived as Windows-centric due to its integration with other Microsoft tools.
Recommendations
  • Add Azure CLI examples for importing a Function App as an API, including relevant commands for Linux/macOS users.
  • Include Bash shell command examples where applicable, especially for tasks like retrieving keys or configuring API Management.
  • Explicitly mention that all steps can be performed from any OS via the Azure Portal, and highlight any cross-platform tools.
  • If Visual Studio Code is referenced, clarify its cross-platform nature and provide instructions for Linux/macOS installation and usage.
  • Consider adding a section or callout for Linux users, summarizing parity and any differences in workflow.
GitHub Create Pull Request
API Management https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/set-backend-service-policy.md .../articles/api-management/set-backend-service-policy.md
Medium Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references PowerShell as a management tool for backend entities but does not mention Linux-native tools (such as Azure CLI or Bash scripting) or provide Linux-specific examples. All management tooling references are either Windows-centric or generic, with no explicit Linux parity. No Linux-specific examples or command-line instructions are provided.
Recommendations
  • Add references and links to Azure CLI documentation and examples for managing backend entities, alongside or before PowerShell.
  • Explicitly mention that backend entities can be managed using cross-platform tools such as Azure CLI and REST API, not just PowerShell.
  • Provide example commands for both PowerShell and Azure CLI (or Bash) when describing management operations.
  • Ensure that any scripts or automation examples are available in both PowerShell and Bash/Azure CLI formats.
  • Review and update the documentation to avoid implying that PowerShell is the primary or only supported tool for management tasks.
GitHub Create Pull Request
← Previous Page 3 of 5 Next →