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 576-594 of 594 flagged pages
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/how-to-deploy-self-hosted-gateway-azure-kubernetes-service.md
...to-deploy-self-hosted-gateway-azure-kubernetes-service.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions creating an Azure Kubernetes cluster using the Azure CLI, Azure PowerShell, or the Azure portal, with PowerShell (a Windows-centric tool) listed before the portal and after the CLI. However, the main deployment instructions use kubectl commands, which are cross-platform and standard for Kubernetes. No explicit Linux or Bash examples are missing, but the ordering in the prerequisites may subtly prioritize Windows tooling.
Recommendations
- List cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell) in prerequisites to avoid suggesting a Windows-first approach.
- Explicitly mention that all kubectl commands work on Windows, Linux, and macOS terminals.
- If possible, provide links to Linux/macOS-specific instructions for creating AKS clusters, or clarify that the Azure CLI is recommended for all platforms.
- Ensure parity in documentation by not listing Windows tools before cross-platform or Linux tools unless there is a technical reason.
Create Pull Request
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 a hosts file editing example, mentioning the Windows path (%SystemDrive%\drivers\etc\hosts) before the Linux/macOS equivalent (/etc/hosts). No other OS-specific tools or commands are referenced, and no PowerShell or Windows-only tools are used elsewhere. However, the ordering prioritizes Windows.
Recommendations
- List Linux and Windows hosts file paths in parallel or mention Linux/macOS first to balance representation.
- Where possible, provide explicit examples for both Linux and Windows, not just file paths but also editing commands (e.g., using 'nano /etc/hosts' for Linux, 'notepad' for Windows).
- Review other documentation sections for similar ordering or implicit prioritization and adjust for parity.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-using-with-internal-vnet.md
...-management/api-management-using-with-internal-vnet.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally maintains cross-platform neutrality, but in the section on editing the hosts file for DNS testing, the Windows file path is mentioned before the Linux/macOS equivalent. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present. However, the ordering of operating systems in the hosts file path reference subtly prioritizes Windows.
Recommendations
- List Linux/macOS and Windows hosts file paths in parallel or alternate the order to avoid implicit prioritization.
- Where file paths or commands are referenced, provide both Windows and Linux/macOS examples side by side.
- Review related links to ensure they do not disproportionately reference Windows-specific documentation (e.g., the 'Creating a record in DNS' link points to a Windows 2000 Server article; consider adding a Linux/BIND equivalent or a cross-platform Azure DNS guide).
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/private-endpoint.md
.../blob/main/articles/api-management/private-endpoint.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page provides instructions and examples that are platform-neutral for most tasks, primarily using the Azure portal and REST APIs. However, the only command-line example given for disabling public network access uses the Azure CLI, which is cross-platform, but there are no explicit Linux shell or Bash examples for DNS validation or network testing. The only DNS validation example uses nslookup, which is available on both Windows and Linux, but no explicit Linux/Bash command (such as dig or host) is shown. There are no PowerShell-specific commands or Windows-only tools mentioned, and the Azure CLI is correctly used as a cross-platform tool.
Recommendations
- When providing DNS validation examples, include both nslookup and dig/host commands to demonstrate parity for Linux users.
- Explicitly mention that Azure CLI commands work on Windows, macOS, and Linux, and provide sample shell prompts for Bash/zsh where appropriate.
- If referencing command-line utilities, clarify their availability across platforms or suggest installation instructions for Linux if needed.
- Consider adding a short section or callout for Linux users, especially in testing and validation steps, to ensure inclusivity.
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 references both Windows and Linux/macOS paths for the hosts file, but lists the Windows path first. There are no command-line examples or tooling references that are Windows-specific, and no examples are missing for Linux. However, the ordering of Windows before Linux in the hosts file path is a subtle form of Windows-first bias.
Recommendations
- List Linux/macOS and Windows hosts file paths in parallel or alternate the order to avoid implying priority.
- Where possible, provide explicit command-line examples for both Windows (e.g., PowerShell) and Linux/macOS (e.g., Bash) if relevant operations are discussed.
- Review other documentation pages for similar ordering or implicit prioritization and strive for platform neutrality.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-authenticate-authorize-azure-openai.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-authenticate-authorize-azure-openai.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display explicit Windows bias in terms of command-line examples or tool references, as it focuses on Azure portal steps and XML policy snippets. However, there is a lack of parity for Linux users: no CLI (Azure CLI, Bash, or cross-platform scripting) examples are provided, and all instructions are GUI-based or use XML policies, which may implicitly favor users familiar with Windows-centric Azure workflows.
Recommendations
- Add Azure CLI and/or Bash examples for key steps, such as creating named values, configuring managed identities, and setting policies.
- Include cross-platform command-line instructions alongside portal-based steps to ensure Linux and macOS users can follow along without relying on the Azure portal.
- Explicitly mention that all steps can be performed using the Azure CLI or ARM templates, and provide links or snippets where appropriate.
- Review for any implicit assumptions about the user's operating system and clarify that the instructions are OS-agnostic where possible.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-using-with-internal-vnet.md
...-management/api-management-using-with-internal-vnet.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally maintains cross-platform language, but in the section on editing the hosts file for DNS testing, the Windows path is listed before the Linux/macOS equivalent. No command-line examples (PowerShell, Bash, etc.) are present, and no Windows-specific tools or patterns are emphasized elsewhere. However, the ordering of Windows before Linux in the hosts file path is a subtle form of 'windows_first' bias.
Recommendations
- List Linux/macOS and Windows hosts file paths in parallel or alternate the order to avoid implying priority.
- Where possible, provide explicit examples for both Windows and Linux/macOS users, especially for common administrative tasks.
- If command-line instructions are added in the future, ensure both PowerShell (Windows) and Bash (Linux/macOS) examples are included.
- Review related links and references to ensure they are not disproportionately focused on Windows-only documentation.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/how-to-deploy-self-hosted-gateway-azure-kubernetes-service.md
...to-deploy-self-hosted-gateway-azure-kubernetes-service.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists Windows-centric tools (Azure PowerShell, Azure portal) before Linux/CLI options when describing how to create an Azure Kubernetes cluster. However, the main deployment steps and examples use cross-platform tools (kubectl, YAML), and there are no PowerShell-specific commands or Windows-only tools in the core workflow.
Recommendations
- List cross-platform or Linux-native tools (such as Azure CLI) before Windows-specific tools (Azure PowerShell, Azure portal) in prerequisite sections.
- Explicitly mention that all deployment steps and commands (kubectl, YAML) are cross-platform and can be run from Linux, macOS, or Windows.
- If possible, provide links or notes for Linux/macOS users on installing and using Azure CLI and kubectl.
- Ensure future documentation avoids ordering that implies Windows is the primary or preferred platform.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/developer-portal-self-host.md
.../articles/api-management/developer-portal-self-host.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page generally uses cross-platform tools (Git, Node.js, Azure CLI) and avoids OS-specific commands. However, in Step 6, it explicitly mentions 'Open Windows Command Prompt, PowerShell, or other command shell,' listing Windows shells first and not mentioning Linux or macOS terminals by name. No Linux/macOS-specific examples or shell references are provided, which may make Linux users feel like an afterthought.
Recommendations
- Explicitly mention Linux and macOS terminals alongside Windows shells in instructions (e.g., 'Open your terminal (such as Windows Command Prompt, PowerShell, macOS Terminal, or Linux shell)').
- Where possible, provide examples or notes for common Linux/macOS environments, especially if there are differences in command syntax or prerequisites.
- Review for any subtle language that centers Windows as the default, and adjust to be more platform-neutral.
- Consider adding a short section or note confirming that all commands work cross-platform, or call out any OS-specific caveats.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/developer-portal-self-host.md
.../articles/api-management/developer-portal-self-host.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally uses cross-platform tools (Git, Node.js, npm, Azure CLI) and avoids OS-specific commands. However, in Step 6, the instructions for uploading static files explicitly mention 'Open Windows Command Prompt, PowerShell, or other command shell,' listing Windows shells first and not mentioning Linux or macOS shells by name. No Linux- or macOS-specific examples or shell references are provided, and there is no explicit guidance for non-Windows users.
Recommendations
- Use neutral, cross-platform language when referring to command shells. For example: 'Open a terminal or command shell (such as Windows Command Prompt, PowerShell, Bash, or Terminal on macOS/Linux)'.
- Explicitly mention that the Azure CLI commands work on Windows, Linux, and macOS, and provide example shell commands for both Windows and Bash (Linux/macOS) where relevant.
- If there are any OS-specific considerations (such as path separators or environment variable syntax), document them for both Windows and Linux/macOS.
- Consider adding a short note in the prerequisites or first command section clarifying that all commands are cross-platform unless otherwise noted.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/how-to-deploy-self-hosted-gateway-azure-kubernetes-service.md
...to-deploy-self-hosted-gateway-azure-kubernetes-service.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows-specific tooling (Azure PowerShell) before Linux/CLI alternatives when describing how to create an Azure Kubernetes cluster. However, the main deployment instructions use cross-platform tools (kubectl) and do not show a strong bias in the core workflow. No explicit Linux examples are missing, but the ordering in prerequisites subtly prioritizes Windows tools.
Recommendations
- List cross-platform tools (such as Azure CLI) before Windows-specific tools (such as Azure PowerShell) in prerequisites and instructions.
- Explicitly mention that all kubectl commands work on Windows, Linux, and macOS to reinforce cross-platform compatibility.
- If possible, provide links to Linux/macOS-specific getting started guides alongside Windows/PowerShell links.
- Review related content and ensure parity in references to platform-specific tooling or portals.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/upgrade-and-scale.md
...blob/main/articles/api-management/upgrade-and-scale.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page exclusively describes how to upgrade and scale an Azure API Management instance using the Azure Portal UI, with no command-line examples or automation instructions. There are no references to Windows-specific tools, but there is also a complete absence of CLI-based instructions (such as Azure CLI, PowerShell, or Bash), which are important for Linux users and automation scenarios. This omission results in an implicit bias toward portal-based workflows, which are often associated with Windows-centric documentation, and does not provide parity for Linux users who may prefer or require CLI-based management.
Recommendations
- Add step-by-step examples for scaling and upgrading using the Azure CLI (az apim commands), which work cross-platform on Linux, macOS, and Windows.
- If PowerShell examples are provided in the future, ensure equivalent Azure CLI or Bash examples are included and presented with equal prominence.
- Explicitly mention that all CLI instructions are cross-platform and do not require Windows.
- Include links to relevant Azure CLI documentation for API Management operations.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/how-to-deploy-self-hosted-gateway-azure-kubernetes-service.md
...to-deploy-self-hosted-gateway-azure-kubernetes-service.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists Windows-centric tools (Azure CLI, Azure PowerShell, Azure portal) in the prerequisites, with PowerShell mentioned before the Azure portal and no explicit mention of Linux-native tools or workflows. However, the main deployment steps use kubectl commands, which are cross-platform and standard for Kubernetes. There are no PowerShell-specific scripts or Windows-only tools in the main instructions, but the ordering and lack of explicit Linux parity in the prerequisites suggest a mild 'windows_first' bias.
Recommendations
- When listing ways to create an Azure Kubernetes cluster, mention Linux-native tools (such as Azure CLI) first, or clarify that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Include explicit notes or examples for Linux/macOS users, such as using bash/zsh terminals, where relevant.
- If referencing Azure PowerShell, balance with a note about Bash/CLI usage on Linux.
- Consider adding a section or callout confirming that all kubectl commands and YAML deployment steps are fully supported and tested on Linux and macOS, not just Windows.
- Where possible, avoid implying that the Azure portal or PowerShell are the default or preferred options.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/developer-portal-self-host.md
.../articles/api-management/developer-portal-self-host.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally uses cross-platform tools (Git, Node.js, Azure CLI) and generic shell commands, but in Step 6 it explicitly lists 'Windows Command Prompt, PowerShell, or other command shell' as options for running Azure CLI, mentioning Windows shells first and not providing Linux/macOS-specific terminal guidance or examples. No Linux- or macOS-specific instructions or screenshots are provided, and the phrase order subtly prioritizes Windows environments.
Recommendations
- When referencing command shells, list platforms in a neutral or rotating order, e.g., 'Open a terminal (such as Windows Command Prompt, PowerShell, macOS Terminal, or Linux shell)'.
- Explicitly state that all commands work on Windows, Linux, and macOS, and provide platform-agnostic instructions.
- Where relevant, add notes or examples for Linux/macOS users (e.g., how to open a terminal, or differences in environment variable syntax).
- Consider including screenshots or terminal prompts from multiple platforms to reinforce cross-platform support.
- Avoid phrases that implicitly prioritize Windows (such as always listing Windows shells first).
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/how-to-deploy-self-hosted-gateway-azure-kubernetes-service.md
...to-deploy-self-hosted-gateway-azure-kubernetes-service.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists Windows-specific tools (Azure PowerShell, Azure portal) before Linux-friendly options (Azure CLI) when describing how to create an Azure Kubernetes cluster. However, the main deployment instructions use cross-platform tools (kubectl) and do not otherwise show a Windows or PowerShell bias. There are no missing Linux examples, and no exclusive use of Windows tools or patterns in the main workflow.
Recommendations
- List Azure CLI (which is cross-platform and preferred in Linux environments) before Azure PowerShell and Azure portal in the prerequisites.
- Explicitly mention that all kubectl commands work identically on Windows, Linux, and macOS.
- If possible, provide links or notes for Linux/macOS users regarding installation of required tools (kubectl, Azure CLI).
- Ensure that any referenced scripts or commands are not PowerShell-specific, and clarify when a command is platform-agnostic.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/integrate-vnet-outbound.md
...ain/articles/api-management/integrate-vnet-outbound.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not provide any OS-specific examples or commands, but all configuration steps are described exclusively through the Azure Portal UI. There are no CLI, PowerShell, or Linux shell examples, which may disadvantage users who prefer or require command-line automation, especially on Linux. The absence of CLI or Linux-native instructions constitutes a subtle bias by omission.
Recommendations
- Add Azure CLI examples for all configuration steps, as the Azure CLI is cross-platform and widely used on Linux.
- If PowerShell examples are added in the future, ensure equivalent Bash/Azure CLI examples are provided.
- Explicitly mention that all steps can be performed via the Azure CLI or ARM templates, and link to relevant documentation.
- Include sample commands for subnet delegation, resource provider registration, and network integration using both Azure CLI and PowerShell, with Linux/Bash examples shown first or equally.
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 demonstrates a subtle Windows bias by listing the Windows hosts file path before the Linux/macOS equivalent when describing how to update the hosts file for DNS testing. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present, but the ordering suggests a preference for Windows environments.
Recommendations
- List both Windows and Linux/macOS hosts file paths together, or alternate the order in which they are presented to avoid implying a preference.
- Wherever possible, provide explicit examples or screenshots for both Windows and Linux environments.
- Review the documentation for other subtle ordering or phrasing that may suggest Windows is the primary or default platform.
API Management
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/private-endpoint.md
.../blob/main/articles/api-management/private-endpoint.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page provides step-by-step instructions for configuring Azure API Management private endpoints, but it lacks any OS-specific bias such as Windows/Powershell-heavy examples or exclusive mention of Windows tools. The only command-line example is an Azure CLI command, which is cross-platform. However, in the 'Test in virtual network' section, the only DNS lookup example given is with nslookup, and there is no mention of Linux/Unix alternatives such as dig. There are no references to Windows-specific tools, Powershell, or patterns, and the Azure portal instructions are OS-agnostic.
Recommendations
- Add Linux/Unix command examples alongside nslookup, such as 'dig my-apim-service.privatelink.azure-api.net', to ensure parity for users on non-Windows systems.
- When suggesting utilities, mention both 'nslookup' and 'dig' as options for DNS lookups.
- Explicitly state that Azure CLI commands work on Windows, Linux, and macOS to reinforce cross-platform support.
- Continue to avoid Windows/Powershell-specific instructions unless parity is provided for other platforms.
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 generally maintains cross-platform neutrality, but in the section describing hosts file editing for DNS testing, the Windows path (%SystemDrive%\drivers\etc\hosts) is mentioned before the Linux/macOS path (/etc/hosts). No command-line examples are given, and no Windows-specific tools or PowerShell commands are used elsewhere.
Recommendations
- When mentioning file paths for cross-platform features (like the hosts file), list Linux/macOS paths first or present them in parallel (e.g., 'on Linux/macOS: /etc/hosts; on Windows: %SystemDrive%\drivers\etc\hosts').
- If providing examples or screenshots, ensure parity by including both Windows and Linux equivalents where appropriate.
- Continue to avoid platform-specific tooling or commands unless absolutely necessary, and always provide alternatives for other platforms.