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 101-112 of 112 flagged pages
API Management
VNet configuration settings | Azure API Management
...n/articles/api-management/virtual-network-reference.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows Specific Section
Summary
The documentation is largely platform-neutral, focusing on Azure networking concepts and configuration. However, there are sections that reference Windows-specific infrastructure, such as guidance for configuring outbound connectivity for Windows VMs to the KMS endpoint and for Windows Update/Defender endpoints. No Linux/macOS-specific tools, endpoints, or patterns are mentioned, and the only explicit OS-specific guidance is for Windows.
Recommendations
- Add equivalent guidance for Linux VMs, such as required outbound ports for package updates (e.g., apt, yum, zypper) and security updates.
- Mention Linux/macOS endpoints or patterns where relevant, such as for activation or update services.
- Clarify which sections are Windows-specific and provide parity for other platforms where applicable.
- If PowerShell or Windows tools are referenced elsewhere (e.g., in related content), ensure CLI or Bash equivalents are provided.
Create Pull Request
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page primarily describes operations using the Azure portal and Azure CLI, which are cross-platform. However, when mentioning command-line tools for disabling routing to a regional gateway, it lists Azure PowerShell (a Windows-centric tool) before Linux-native alternatives, and does not provide explicit Linux/macOS shell examples (e.g., bash, zsh) or clarify CLI usage on those platforms. No Windows-only tools or patterns are required, but the ordering and lack of explicit Linux/macOS parity in examples suggest a mild Windows-first bias.
Recommendations
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS, and provide example shell commands for Linux/macOS environments where appropriate.
- When listing tools, avoid putting Windows-centric tools (like PowerShell) before cross-platform alternatives unless contextually justified.
- Add notes or examples for Linux/macOS users, such as using bash/zsh for Azure CLI, and clarify any platform-specific considerations.
- If PowerShell is mentioned, also mention that Azure CLI is fully supported on Linux/macOS and provide parity in example commands.
API Management
Azure API Management - Overview and Key Concepts
...articles/api-management/api-management-key-concepts.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page references Azure PowerShell and the Azure portal as primary management tools, listing them before Azure CLI and REST API. It also mentions a Visual Studio Code extension, which is more commonly associated with Windows development environments. There are no explicit Linux/macOS examples or tool recommendations, and no mention of Linux-specific management patterns. However, the self-hosted gateway is described as a Linux-based Docker container, showing some Linux awareness.
Recommendations
- List Azure CLI before or alongside Azure PowerShell and portal when describing management plane tools, as CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention that all management operations can be performed from Linux/macOS using Azure CLI and REST API.
- Provide links or brief examples for using Azure CLI for common tasks (e.g., provisioning, configuration) alongside PowerShell and portal references.
- Include a note that Visual Studio Code is cross-platform and can be used on Linux/macOS.
- Add a section or tip for Linux/macOS users highlighting parity and any platform-specific considerations.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell, with PowerShell (a Windows-centric tool) given equal prominence to CLI. There is no explicit Linux/macOS bias, but PowerShell is featured as a primary method, which may not be as relevant for Linux/macOS users. The CLI example is cross-platform, but PowerShell is Windows-first and not as commonly used on Linux/macOS. No Linux-specific tools or shell examples (e.g., Bash) are provided.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Consider adding Bash shell examples for Linux users, especially for scripting scenarios.
- De-emphasize PowerShell as a primary method, or note its cross-platform availability (if relevant), but clarify its Windows origins.
- Add a note or section for Linux/macOS users, confirming that all steps are supported and providing any OS-specific tips.
API Management
Self-Host the API Management Developer Portal
.../articles/api-management/developer-portal-self-host.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias in the section describing how to upload static files to Azure Blob Storage. It explicitly mentions 'Windows Command Prompt, PowerShell, or other command shell' and does not provide Linux/macOS-specific instructions or examples. The rest of the documentation uses cross-platform tools (Git, Node.js, Azure CLI) and provides examples that work on all platforms, but the upload step could be clearer for non-Windows users.
Recommendations
- Replace 'Open Windows Command Prompt, PowerShell, or other command shell.' with 'Open your preferred command shell (Windows Command Prompt, PowerShell, Bash, Terminal, etc.).'
- Add a note confirming that the Azure CLI command works on Linux/macOS terminals as well as Windows.
- Optionally, provide an explicit Bash example or clarify that the CLI command syntax is cross-platform.
- Avoid mentioning Windows shells first unless there is a platform-specific reason.
API Management
Set up inbound private endpoint for Azure API Management
.../blob/main/articles/api-management/private-endpoint.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation primarily uses Azure Portal (GUI) and Azure CLI for configuration steps, which are cross-platform. However, in the 'Test in virtual network' section, only the 'nslookup' utility is mentioned as an example for DNS validation, which is available on both Windows and Linux, but no Linux-specific alternatives (like 'dig') are shown. There are no PowerShell-specific examples, nor are Windows-only tools or patterns mentioned. The order of examples and instructions does not explicitly prioritize Windows, but the lack of explicit Linux/macOS command examples (e.g., 'dig', shell scripting) and the absence of references to Linux-specific troubleshooting or validation steps indicate a mild Windows bias.
Recommendations
- Add Linux/macOS-specific examples for DNS validation, such as using 'dig' in addition to 'nslookup'.
- Explicitly mention that Azure CLI is cross-platform and provide sample commands for both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) environments where relevant.
- Include troubleshooting steps or validation commands that are common in Linux/macOS environments (e.g., 'host', 'curl', shell scripting).
- Clarify that the Azure Portal and REST API methods are OS-agnostic.
API Management
Deploy a Self-Hosted Gateway to Azure Container Apps - Azure API Management
...nt/how-to-deploy-self-hosted-gateway-container-apps.md
Low Priority
View Details →
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 explicitly labels them as 'PowerShell syntax'. There are no Linux-specific tools or patterns mentioned, but the parity of examples is maintained. However, the presence of PowerShell examples and syntax notes may create a subtle Windows bias, especially since PowerShell is primarily associated with Windows, even though it is cross-platform. No Windows-only tools or instructions are present, and Linux/macOS users can complete all tasks as described.
Recommendations
- Clarify that PowerShell syntax is also valid on Linux/macOS where PowerShell Core is available.
- Consider including explicit instructions or notes for macOS users (e.g., file path differences, shell environment setup).
- Add a note that Bash examples are suitable for most Linux/macOS environments, and PowerShell examples are for users who prefer PowerShell, regardless of OS.
- If possible, provide a generic 'sh' example or indicate that Bash commands work in most POSIX shells.
API Management
Azure API Management virtual network injection - network resources
.../api-management/virtual-network-injection-resources.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates minor Windows bias primarily in the 'Related content' section, where a link is provided to instructions for connecting virtual networks using PowerShell—a Windows-centric tool—without mentioning or linking to equivalent Linux/macOS methods (such as Azure CLI or Bash). No explicit Linux examples or cross-platform alternatives are referenced, and Windows tools are mentioned before any Linux equivalents.
Recommendations
- Add links or references to Azure CLI or Bash instructions for connecting virtual networks, ensuring parity for Linux/macOS users.
- Where PowerShell is mentioned, clarify that Azure CLI and other cross-platform tools are also supported and provide links to relevant documentation.
- Review other related tasks and ensure examples and guidance are provided for both Windows and Linux/macOS environments.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/self-hosted-gateway-overview.md
...rticles/api-management/self-hosted-gateway-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a mild 'windows_first' bias by listing 'PowerShell' as a primary configuration tool in the management plane description, before mentioning other technologies. However, the rest of the documentation is platform-neutral, with a strong emphasis on Linux-based deployment (Docker, Kubernetes) and no exclusive use of Windows tools or examples. There are no PowerShell-heavy sections, missing Linux examples, or exclusive references to Windows tools.
Recommendations
- When listing configuration tools for the management plane, mention cross-platform tools (such as Azure CLI or REST API) before or alongside PowerShell to avoid implying Windows is the default or preferred environment.
- Provide explicit examples or references for Linux/macOS users where command-line interaction is discussed, ensuring parity with any PowerShell or Windows-specific mentions.
- If PowerShell is mentioned, clarify that it is available cross-platform, or provide alternative commands for Bash/Azure CLI where appropriate.
- Continue emphasizing Linux-based deployment and containerization, as this aligns with cross-platform best practices.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/inject-vnet-v2.md
...cs/blob/main/articles/api-management/inject-vnet-v2.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides instructions for updating the hosts file for DNS testing, mentioning the Windows path (%SystemDrive%\drivers\etc\hosts) before the Linux/macOS equivalent (/etc/hosts). No PowerShell-heavy examples or exclusive use of Windows tools are present, and Linux is acknowledged, but the ordering suggests a mild Windows-first bias.
Recommendations
- List Linux/macOS hosts file location before or alongside the Windows path to avoid implicit prioritization.
- Provide explicit examples for both Windows and Linux/macOS when referencing file paths or commands.
- Consider including screenshots or step-by-step instructions for both platforms if relevant.
- Review other sections for similar ordering or tool references to ensure parity.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/inject-vnet-v2.md
...cs/blob/main/articles/api-management/inject-vnet-v2.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions both Windows and Linux/macOS locations for the hosts file when describing DNS testing, but lists the Windows path first. No PowerShell-heavy examples, exclusive Windows tools, or missing Linux examples are present. The overall instructions are platform-neutral except for the ordering in the hosts file example.
Recommendations
- List both Windows and Linux/macOS hosts file paths together, or alternate the order in which they are presented to avoid implicit prioritization.
- Explicitly provide example commands for editing the hosts file on both platforms (e.g., using Notepad on Windows, nano/vim on Linux/macOS).
- Ensure future examples and screenshots show parity between Windows and Linux environments where applicable.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/virtual-network-workspaces-resources.md
...api-management/virtual-network-workspaces-resources.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions both Windows and Linux/macOS locations for the hosts file, but lists the Windows path first. No command-line examples (PowerShell, Bash, etc.) are given, and no Windows-specific tools or patterns are emphasized. However, the ordering of the hosts file paths is a subtle instance of Windows-first bias.
Recommendations
- List Linux/macOS hosts file location before Windows, or present both simultaneously (e.g., '/etc/hosts (Linux/macOS), %SystemDrive%\drivers\etc\hosts (Windows)').
- Provide explicit examples for updating the hosts file on both Windows and Linux/macOS, including sample commands (e.g., using 'echo' or 'notepad' on Windows, 'echo' or 'nano' on Linux).
- Ensure future documentation includes parity in examples and tool references for both platforms, especially when manual configuration steps are described.