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 351-375 of 594 flagged pages
API Management Deploy a Self-Hosted Gateway to Azure Container Apps - Azure API Management ...nt/how-to-deploy-self-hosted-gateway-container-apps.md
Medium Priority View Details →
Scanned: 2026-01-11 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 Azure CLI commands, but consistently lists PowerShell examples immediately after Bash, and uses Windows/PowerShell-specific syntax and variable assignment patterns. There is no explicit Linux-only example, and the structure may subtly prioritize Windows users by always including PowerShell, even when Bash is sufficient for cross-platform use.
Recommendations
  • Ensure Bash examples are clearly marked as suitable for both Linux and macOS, not just 'Bash'.
  • Consider including a note that Bash commands work on Linux/macOS and Windows (via WSL or Git Bash), while PowerShell is primarily for Windows.
  • Add explicit Linux/macOS environment setup instructions or troubleshooting tips if there are platform-specific differences.
  • If PowerShell is not strictly necessary, consider making Bash the default and listing PowerShell as an alternative, or provide a single cross-platform CLI example where possible.
  • Review variable assignment and command syntax to ensure parity and clarity for Linux users.
  • Avoid using Windows-centric terminology or patterns unless there is a clear platform-specific requirement.
GitHub Create Pull Request
API Management Import an Azure web app to Azure API Management | Microsoft Docs ...n/articles/api-management/import-app-service-as-api.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric technologies and workflows, such as ASP.NET Core and Visual Studio Code, for creating and publishing web APIs. There are no examples or guidance for Linux-based development stacks, tools, or deployment patterns. The documentation assumes the user is working in a Windows environment and does not provide parity for Linux users.
Recommendations
  • Include examples for creating and publishing web APIs using popular Linux stacks (e.g., Node.js/Express, Python/Flask, Java/Spring Boot).
  • Provide instructions for deploying web apps to Azure App Service from Linux environments, including CLI-based workflows (Azure CLI, Bash scripts).
  • Reference Linux-friendly tools and editors (e.g., VS Code on Linux, JetBrains IDEs, Vim) alongside Visual Studio Code.
  • Add links to documentation for publishing web apps from Linux and macOS platforms.
  • Ensure that sample commands and screenshots are not Windows-specific, or provide Linux equivalents where appropriate.
GitHub Create Pull Request
API Management Set up inbound private endpoint for Azure API Management .../blob/main/articles/api-management/private-endpoint.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing examples and instructions using the Azure portal and Azure CLI, with no mention of Linux-specific tools or command-line patterns. The only command-line example is for Azure CLI, which is cross-platform but presented without explicit Linux shell context or alternative Linux-native instructions. There are no references to PowerShell, but the documentation does not offer Linux-specific guidance or examples, such as using bash scripts, Linux networking tools, or Linux VM setup. All screenshots and UI instructions are based on the Azure portal, which is platform-agnostic but often associated with Windows workflows.
Recommendations
  • Add explicit Linux shell examples (e.g., bash, curl, dig) for key steps, such as testing DNS resolution and API connectivity.
  • Include instructions for setting up and validating private endpoints from a Linux VM, with references to Linux networking tools (e.g., ip, ifconfig, netstat).
  • Clarify that Azure CLI commands work on both Windows and Linux, and provide sample commands in both bash and PowerShell syntax where appropriate.
  • Provide troubleshooting steps specific to Linux environments, such as checking firewall rules or network interfaces.
  • Add screenshots or terminal output from Linux environments to demonstrate parity.
GitHub Create Pull Request
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-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing the Azure portal (a web interface commonly used on Windows) and mentioning Azure PowerShell before Azure CLI and REST API as alternative deployment methods. There are no explicit Linux-specific examples, nor are Linux terminal commands or patterns shown. The documentation does not provide parity in examples for Linux users, such as bash scripts or CLI-first workflows.
Recommendations
  • Add explicit Azure CLI examples for deploying ARM templates, including bash commands suitable for Linux/macOS environments.
  • Present Azure CLI and REST API options before or alongside Azure PowerShell to avoid Windows-first ordering.
  • Include screenshots or instructions that demonstrate deployment from Linux/macOS terminals.
  • Clarify that all deployment methods (portal, CLI, PowerShell, REST) are cross-platform, and provide links to Linux/macOS installation guides for Azure CLI.
  • Where possible, provide parity in resource clean-up instructions using Azure CLI commands.
GitHub Create Pull Request
API Management Azure API Management virtual network injection - network resources .../api-management/virtual-network-injection-resources.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias, primarily in the 'Related content' section, which references connecting virtual networks using PowerShell—a Windows-centric tool—without mentioning Linux alternatives (such as Azure CLI or Bash). No Linux-specific examples or tools are provided, and Windows tooling is referenced before any cross-platform options.
Recommendations
  • Include equivalent instructions or links for Linux/macOS users, such as using Azure CLI or Bash scripts for network configuration and virtual network connections.
  • When referencing PowerShell, also mention Azure CLI as a cross-platform alternative, and provide links to relevant documentation.
  • Ensure that examples and tooling guidance are presented in a platform-neutral manner, or explicitly provide parity for both Windows and Linux environments.
  • Review related content and cross-reference Linux-friendly documentation where available.
GitHub Create Pull Request
API Management Azure API Management - Overview and Key Concepts ...articles/api-management/api-management-key-concepts.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias by listing Windows-centric tools (Azure PowerShell, Visual Studio Code extension) before Linux-friendly equivalents (Azure CLI, REST API) when describing management plane access. There are no explicit Linux examples, and Windows tools are mentioned first in the relevant section. However, the self-hosted gateway is described as Linux-based, and there is no overt exclusion of Linux usage elsewhere.
Recommendations
  • List cross-platform tools (Azure CLI, REST API) before or alongside Windows-specific tools (PowerShell, VS Code extension) when describing management plane access.
  • Explicitly mention Linux support and provide Linux-specific usage examples or references where appropriate.
  • Include links or guidance for Linux users, such as using Azure CLI on Linux, or managing API Management from Linux environments.
  • Ensure parity in tool coverage by referencing both Windows and Linux workflows in quickstart and next steps sections.
GitHub Create Pull Request
API Management Import an Azure web app to Azure API Management | Microsoft Docs ...n/articles/api-management/import-app-service-as-api.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-centric development tools (ASP.NET Core, Visual Studio Code) and providing examples and tutorials that are tailored to Windows environments. There are no Linux-specific instructions, examples, or alternative workflows mentioned for creating or publishing web APIs to Azure App Service, nor is there any mention of Linux command-line tools or deployment patterns.
Recommendations
  • Add Linux-specific examples for creating and publishing web APIs, such as using the Azure CLI, Bash scripts, or deployment via GitHub Actions from Linux environments.
  • Reference tutorials for web API development in other languages and frameworks commonly used on Linux (e.g., Node.js, Python, Java).
  • Include instructions for deploying to Azure App Service from Linux-based development environments, such as using VS Code on Linux, or command-line deployment via Azure CLI.
  • Mention cross-platform tools and workflows explicitly, and ensure parity in step-by-step instructions for both Windows and Linux users.
GitHub Create Pull Request
API Management Set Up Logging for LLM APIs in Azure API Management ...ticles/api-management/api-management-howto-llm-logs.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes configuration and log review using the Azure Portal GUI and Kusto queries, with no mention of command-line or automation options. There are no examples using PowerShell, but also no examples using Azure CLI, Bash, or Linux-native tools. The workflow implicitly assumes use of the Azure Portal, which is most commonly accessed from Windows environments, and omits Linux-oriented or cross-platform automation patterns.
Recommendations
  • Add equivalent instructions for configuring diagnostic settings and log review using Azure CLI commands, which are cross-platform and widely used on Linux.
  • Include examples of exporting logs using Bash scripts or Linux tools (e.g., curl, jq) for automation.
  • Mention that the Azure Portal is accessible from any OS, but provide parity for users who prefer command-line or automated approaches.
  • If PowerShell examples are added in future, ensure Azure CLI or Bash equivalents are provided alongside.
  • Highlight any platform-specific limitations or considerations for Linux users, if applicable.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references Azure PowerShell as a tool for automating subscription key management workflows but does not mention or provide equivalent examples for Linux-friendly tools such as Azure CLI, Bash scripting, or REST API usage. No platform-specific code samples are given, but the only automation tool explicitly named is PowerShell, which is primarily associated with Windows environments.
Recommendations
  • Mention Azure CLI as an alternative to Azure PowerShell for automating subscription key management, and provide example commands.
  • Include REST API examples using curl or similar cross-platform tools to demonstrate key management operations.
  • Explicitly state that all management operations can be performed from Linux, macOS, or Windows, and provide parity in tool recommendations.
  • Where automation is discussed, offer sample scripts or workflows for both PowerShell and Bash environments.
GitHub Create Pull Request
API Management Deploy a Self-Hosted Gateway to Azure Kubernetes Service ...to-deploy-self-hosted-gateway-azure-kubernetes-service.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists Windows-centric tools (Azure PowerShell, Azure portal) before Linux-native options (Azure CLI) when describing how to create an AKS cluster. There is a slight ordering bias favoring Windows tools, and PowerShell is mentioned as an equal alternative to CLI, but no explicit Linux shell examples are given. However, the main deployment steps use cross-platform tools (kubectl) and do not show exclusive Windows or PowerShell commands.
Recommendations
  • List Azure CLI (Linux-native) before Azure PowerShell and Azure portal when describing cluster creation, or clarify that all methods are cross-platform.
  • Provide explicit Linux shell examples or clarify that all commands (kubectl, etc.) work identically on Linux, macOS, and Windows.
  • Add a note about cross-platform compatibility for all command-line instructions.
  • If mentioning PowerShell, also mention Bash or other Linux shells to ensure parity.
GitHub Create Pull Request
API Management Set up inbound private endpoint for Azure API Management .../blob/main/articles/api-management/private-endpoint.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric tools and workflows, such as the Azure portal and Azure CLI, and by providing only Windows-style command-line examples (e.g., nslookup) without Linux-specific alternatives. There are no PowerShell examples, but Linux tools and patterns (such as dig for DNS testing) are mentioned only in passing and not shown in example commands. The documentation does not provide explicit Linux shell commands or instructions for Linux users, nor does it address platform-specific differences in testing or configuration.
Recommendations
  • Add explicit Linux command examples (e.g., show both nslookup and dig commands for DNS testing).
  • Include instructions for connecting to a Linux VM and running validation steps, not just generic 'connect to a VM'.
  • Where CLI commands are shown, clarify that they work on both Windows and Linux, and note any platform-specific differences.
  • Reference Linux tools and workflows (such as using curl or wget for API calls) alongside Windows equivalents.
  • Ensure screenshots and UI instructions are not Windows-centric, or provide notes for Linux users where relevant.
GitHub Create Pull Request
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation primarily describes deployment and management using the Azure portal and mentions Azure PowerShell, Azure CLI, and REST API only briefly and generically. There are no explicit command-line examples for either Windows or Linux, but the ordering and phrasing ('Azure PowerShell, Azure CLI, and REST API') places Windows-centric tools first and does not provide parity examples for Linux users. The documentation does not mention Linux-specific patterns or provide bash examples, and the screenshots and instructions are all based on the Azure portal GUI, which is platform-agnostic but often more familiar to Windows users.
Recommendations
  • Add explicit Azure CLI (bash) command examples for deploying and managing the ARM template, demonstrating parity for Linux/macOS users.
  • When listing deployment methods, alternate the order (e.g., 'Azure CLI, Azure PowerShell, and REST API') or clarify that all tools are cross-platform.
  • Include a section or links to documentation on using ARM templates from Linux/macOS environments.
  • Provide sample scripts for both PowerShell and bash to illustrate cross-platform usage.
GitHub Create Pull Request
API Management https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-llm-logs.md ...ticles/api-management/api-management-howto-llm-logs.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes configuration and log review steps using the Azure portal UI, with no mention of command-line or automation options. There are no examples using PowerShell, CLI, or Linux tools, but the instructions implicitly assume a graphical workflow typical of Windows environments. There is no parity for Linux users who may prefer Azure CLI, Bash, or automation scripts, nor are alternative workflows mentioned.
Recommendations
  • Add equivalent instructions using Azure CLI commands for all major configuration steps (e.g., enabling diagnostic settings, exporting logs).
  • Include examples of how to query logs using Bash scripts or Azure CLI, not just Kusto queries in the portal.
  • Mention automation options for Linux environments, such as using az apim diagnostic or az monitor commands.
  • Provide links to cross-platform tools and documentation, ensuring Linux users can follow along without relying on the portal.
  • Explicitly state that all steps can be performed on Linux, macOS, or Windows, and note any platform-specific differences.
GitHub Create Pull Request
API Management https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-subscriptions.md ...rticles/api-management/api-management-subscriptions.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 or provide parity for Linux-friendly alternatives such as Azure CLI or Bash scripting. No examples or references to Linux tools or command-line patterns are given, and the only automation tool explicitly named is PowerShell, which is primarily associated with Windows environments.
Recommendations
  • Mention Azure CLI alongside Azure PowerShell as a supported tool for automating subscription key management, since Azure CLI is cross-platform and widely used on Linux and macOS.
  • Provide example commands or scripts using Azure CLI for common tasks such as regenerating subscription keys, creating subscriptions, or managing their lifecycle.
  • Explicitly state that both Azure PowerShell and Azure CLI can be used for automation, and link to documentation for both tools.
  • Avoid implying that PowerShell is the only or preferred automation tool by listing cross-platform alternatives first or equally.
  • Consider adding Bash or shell script examples for relevant API calls, especially when demonstrating REST API usage.
GitHub Create Pull Request
API Management https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-versions.md ...ain/articles/api-management/api-management-versions.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page references Azure PowerShell and the Azure portal (both Windows-centric tools) before mentioning cross-platform alternatives like Azure CLI and Resource Manager templates. There are no explicit Linux or Bash examples, and the order of tool presentation favors Windows-first workflows.
Recommendations
  • Present Azure CLI (which is cross-platform) before Azure PowerShell when listing management tools.
  • Include explicit Bash or shell examples alongside PowerShell where command-line usage is demonstrated.
  • Clarify that Azure CLI and Resource Manager templates are fully supported on Linux and macOS.
  • Add a note or section highlighting parity for Linux users, including links to Linux-specific setup guides for Azure API Management.
  • Avoid assuming use of the Azure portal (which is browser-based but often referenced in Windows-centric workflows) as the primary management interface.
GitHub Create Pull Request
API Management https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-key-concepts.md ...articles/api-management/api-management-key-concepts.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias in its references to Azure management tools. The management plane section lists Azure portal, Azure PowerShell, Azure CLI, and Visual Studio Code extension as management options, with PowerShell (a Windows-centric tool) mentioned before Azure CLI (cross-platform). There are no explicit Linux-only examples or tools, and no command-line examples are given for either platform. The self-hosted gateway is described as Linux-based, which is positive for Linux parity, but overall, Windows tools are mentioned first and more prominently.
Recommendations
  • List Azure CLI before Azure PowerShell when describing management tools, as CLI is cross-platform and more widely used on Linux.
  • Include explicit examples or links for managing API Management from Linux environments (e.g., Bash scripts, CLI commands).
  • Mention Linux-native editors (such as Vim or VS Code on Linux) when discussing extensions, or clarify that VS Code is cross-platform.
  • Add a tip or note highlighting parity of management capabilities across Windows, Linux, and macOS.
  • Where possible, provide both PowerShell and Bash/CLI examples for common tasks.
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:34
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 Azure CLI commands, but PowerShell examples are consistently presented immediately after Bash, and the syntax notes and tabs are labeled specifically for PowerShell. There is a strong emphasis on Windows tooling (PowerShell) as the alternative to Bash, with no mention of other Linux shells (e.g., zsh, fish) or macOS-specific considerations. All variable setting examples are either Bash or PowerShell, and there are no explicit Linux-specific troubleshooting steps, nor is there any mention of Linux-native tools or patterns beyond Bash. The Azure portal instructions are platform-neutral, but command-line examples reinforce a Windows-centric view by treating PowerShell as the primary non-Bash alternative.
Recommendations
  • Add explicit Linux shell compatibility notes (e.g., zsh, fish) and clarify that Bash examples are applicable to most Linux distributions and macOS.
  • Consider providing macOS-specific notes or troubleshooting steps where relevant.
  • Include a brief section explaining that PowerShell is available cross-platform, but Bash is the default on most Linux systems.
  • If possible, provide generic shell examples or clarify that Bash syntax is standard for Linux/macOS users.
  • Ensure that troubleshooting and environment preparation steps include Linux-specific details, such as package installation or permissions.
  • Avoid implying PowerShell is the only alternative to Bash; mention other shells or clarify the scope.
GitHub Create Pull Request
API Management https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/protect-with-ddos-protection.md ...rticles/api-management/protect-with-ddos-protection.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page references enabling DDoS IP Protection via a link to a PowerShell-based guide, which is primarily a Windows tool, and does not provide equivalent instructions or examples for Linux users (such as Azure CLI or Bash). There is no mention of Linux-specific tools or cross-platform command-line options, and the only step-by-step instructions are for the Azure portal (web UI), which is platform-neutral. However, for automation or scripting, only Windows-centric tooling is referenced.
Recommendations
  • Add equivalent instructions for enabling DDoS IP Protection using Azure CLI, which is cross-platform and commonly used on Linux.
  • Include Bash or shell script examples where automation is discussed, alongside PowerShell.
  • Explicitly mention that Azure CLI can be used on Windows, Linux, and macOS, and provide links to relevant CLI documentation.
  • When referencing external guides (such as the PowerShell guide), also link to CLI-based guides if available.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation primarily describes deploying and managing Azure API Management instances 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 Linux users (e.g., Bash/CLI commands), and PowerShell is referenced before CLI, suggesting a Windows-first approach. No Linux-specific tools or guidance are provided.
Recommendations
  • Add explicit step-by-step examples for deploying the ARM template using Azure CLI (az commands) in Bash, suitable for Linux and macOS users.
  • Ensure that Azure CLI instructions are presented before or alongside PowerShell examples to avoid Windows-first ordering.
  • Include screenshots or terminal outputs from Linux environments where relevant.
  • Clarify that the Azure portal, CLI, and PowerShell are all cross-platform, and provide links to platform-specific setup guides.
GitHub Create Pull Request
API Management https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/virtual-network-injection-resources.md .../api-management/virtual-network-injection-resources.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias by referencing PowerShell in the related content section ('Connect virtual networks from different deployment models using PowerShell') and by omitting equivalent Linux/CLI examples or links. Windows tools are mentioned exclusively, and there is no parity in mentioning Linux alternatives or Azure CLI commands. The documentation does not provide examples or guidance for Linux users, nor does it reference Bash, Azure CLI, or cross-platform scripting options.
Recommendations
  • Add links to equivalent Azure CLI documentation for connecting virtual networks and other operations, ensuring Linux users have clear guidance.
  • When referencing PowerShell, also mention Azure CLI and Bash scripting alternatives, ideally side-by-side.
  • Include examples or links for common operations using Azure CLI, especially in sections where PowerShell is referenced.
  • Review related content to ensure cross-platform parity, and avoid listing Windows tools exclusively unless there is no alternative.
GitHub Create Pull Request
API Management https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-subscriptions.md ...rticles/api-management/api-management-subscriptions.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page references Azure PowerShell as a tool for automating subscription key management workflows, but does not mention or provide examples for equivalent Linux-friendly tools (such as Azure CLI or REST API usage via curl). No command-line examples are given, but the only tool named is PowerShell, which is primarily associated with Windows environments. There are no explicit Linux or cross-platform examples or tool recommendations.
Recommendations
  • Mention Azure CLI alongside Azure PowerShell as a supported automation tool for managing subscription keys, highlighting its cross-platform compatibility.
  • Provide example commands for both Azure PowerShell and Azure CLI (or REST API via curl) to demonstrate key management tasks.
  • Explicitly state that all management operations can be performed from Linux, macOS, and Windows environments using Azure CLI or REST API.
  • Review other tool references in the documentation to ensure Linux parity and avoid Windows-centric language.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation consistently provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell (Windows) examples are always presented immediately after Bash, and sometimes with explicit syntax notes. There is no mention of Linux-specific tools, patterns, or troubleshooting, and the only shell alternatives shown are Bash and PowerShell, with no reference to other common Linux shells (e.g., zsh) or environments. The documentation assumes familiarity with the Azure portal and CLI, which are cross-platform, but the example structure and syntax guidance slightly favor Windows users by always including PowerShell and sometimes providing extra notes for it.
Recommendations
  • Present Bash (Linux/macOS) examples first, or alternate the order with PowerShell to avoid implicit prioritization.
  • Add explicit notes about running Bash commands in native Linux/macOS terminals, including any differences in environment variable handling or file paths.
  • Include troubleshooting tips or references for common Linux issues (e.g., permissions, networking) when deploying container apps.
  • Consider including zsh or other Linux shell variants if relevant, or clarify that Bash examples are applicable to most Linux environments.
  • Ensure parity in syntax notes: if PowerShell-specific notes are given, provide equivalent notes for Bash/Linux where applicable.
  • Mention that Azure CLI is fully supported on Linux/macOS and link to installation guides for those platforms.
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: 2025-09-15 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references Windows-specific tools (PowerShell) for backend management and omits mention of equivalent Linux/CLI tools. No Linux or cross-platform command-line examples are provided, and the only automation tool highlighted is PowerShell.
Recommendations
  • Include Azure CLI examples alongside or instead of PowerShell for backend management tasks, as Azure CLI is cross-platform.
  • Mention that backend entities can also be managed using Azure CLI, and provide a link to relevant documentation.
  • Ensure that all tool references (e.g., PowerShell) are accompanied by their Linux/cross-platform equivalents.
  • Add a note clarifying that all management operations can be performed from Linux, macOS, and Windows using Azure CLI or REST API.
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: 2025-09-15 00:00
Reviewed by: Unknown
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 consistently lists Bash first, followed by PowerShell. There is a strong focus on Azure CLI, which is cross-platform, but the presence of PowerShell-specific syntax and tabs throughout the document indicates a bias toward Windows users. No Linux-specific tools or patterns are missing, but the parity is maintained mainly through Bash examples, with no explicit mention of Linux environments or considerations.
Recommendations
  • Explicitly mention that Bash examples are suitable for Linux/macOS users and PowerShell for Windows users.
  • Add a note in the prerequisites clarifying that the Azure CLI and all examples work on Linux, macOS, and Windows.
  • Include a brief section or callout highlighting any Linux/macOS-specific considerations (such as file permissions, line endings, or environment variable syntax differences, if applicable).
  • Ensure that any troubleshooting or advanced sections reference both Linux and Windows environments equally.
  • If possible, provide a single cross-platform script example using Azure CLI without OS-specific shell syntax, or link to such resources.
GitHub Create Pull Request
API Management https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/private-endpoint.md .../blob/main/articles/api-management/private-endpoint.md
Medium Priority View Details →
Scanned: 2025-09-15 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by exclusively providing instructions and examples using the Azure portal and Azure CLI, with command-line examples only shown using Azure CLI syntax (which is cross-platform but often associated with Windows environments). There are no explicit Linux-specific examples, nor are there any references to Linux tools or shell environments. Additionally, when suggesting utilities for DNS validation, only nslookup and dig are mentioned, but without explicit Linux or Windows context. There are no PowerShell-specific commands, but the absence of Linux shell or scripting examples and the reliance on the Azure portal (which is often presented from a Windows-centric perspective) further reinforce the bias.
Recommendations
  • Explicitly mention that Azure CLI commands work on both Windows and Linux, and provide example shell commands for both Bash (Linux/macOS) and PowerShell (Windows).
  • Include Linux-specific command-line examples where appropriate, such as using curl or wget for API calls, and show equivalent commands in both Bash and PowerShell.
  • When referencing utilities like nslookup or dig, clarify their availability on both platforms and provide example outputs from both Windows and Linux environments.
  • Add a section or callout for users managing resources from Linux/macOS, highlighting any differences or additional steps (such as installing Azure CLI or required utilities).
  • Where possible, provide screenshots or terminal outputs from both Windows and Linux environments to ensure parity and inclusivity.
GitHub Create Pull Request
← Previous Page 15 of 24 Next →