Application Gateway
188
Total Pages
113
Linux-Friendly Pages
75
Pages with Bias
39.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
981 issues found
Showing 976-981 of 981 flagged pages
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-request-routing-rules.md
...ication-gateway/configuration-request-routing-rules.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally avoids OS-specific instructions, but in the section on HTTP-to-HTTPS redirection, the PowerShell (Windows-centric) example is listed before the Azure CLI (cross-platform) example. This ordering subtly prioritizes Windows tooling. However, Linux parity is largely maintained elsewhere, and CLI examples are present.
Recommendations
- List Azure CLI (cross-platform) instructions before PowerShell (Windows-centric) instructions to avoid implying a Windows-first workflow.
- Ensure that all referenced guides (such as those for redirection and external site redirection) provide both PowerShell and CLI examples, and that both are equally visible.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows to reinforce cross-platform support.
- Consider adding Bash or shell script examples where relevant, especially in sections that reference automation or scripting.
Create Pull Request
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/use-server-sent-events.md
...articles/application-gateway/use-server-sent-events.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or commands, but it also lacks any practical configuration examples for either Windows or Linux. This omission can be considered a subtle bias, as users on Linux (or any OS) do not receive guidance on how to configure their backend servers for SSE, such as example commands or configuration snippets for popular web servers (e.g., Nginx, Apache, IIS). The absence of Linux-specific examples is a missed opportunity for parity.
Recommendations
- Add practical configuration examples for both Linux and Windows environments. For Linux, include sample Nginx and Apache configurations showing the required headers for SSE.
- If mentioning Windows/IIS, ensure Linux examples are provided first or alongside.
- Include example shell commands (e.g., curl) for testing SSE endpoints on both Linux and Windows.
- Explicitly mention that the guidance applies to all backend platforms and provide links or references to platform-specific documentation where appropriate.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-components.md
.../application-gateway/application-gateway-components.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page generally avoids OS-specific tooling or examples, but in the 'Next steps' section, instructions for creating an application gateway are listed in the order: Azure Portal, Azure PowerShell, and then Azure CLI. PowerShell is a Windows-centric tool, while Azure CLI is cross-platform. Listing PowerShell before CLI may subtly prioritize Windows users.
Recommendations
- List Azure CLI instructions before or alongside PowerShell to reflect its cross-platform nature and promote parity for Linux and macOS users.
- Explicitly mention that both Azure CLI and PowerShell are supported on multiple platforms, if true, to avoid the impression of Windows preference.
- Wherever possible, provide parallel examples for both PowerShell and CLI in procedural documentation.
- Review other documentation pages for similar ordering or tool prioritization to ensure consistent cross-platform inclusivity.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/create-gateway-internal-load-balancer-app-service-environment.md
...gateway-internal-load-balancer-app-service-environment.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific troubleshooting commands or examples, but it does mention exporting the TLS/SSL certificate using a browser without specifying any platform. However, there are no explicit instructions or examples for Linux users (e.g., using OpenSSL or command-line tools), which may leave Linux administrators without clear guidance.
Recommendations
- Add step-by-step instructions for exporting the ILB certificate using common Linux tools such as OpenSSL.
- Provide both Windows (e.g., using MMC or browser) and Linux (e.g., using curl or OpenSSL) methods for retrieving and exporting certificates.
- Explicitly mention that the browser export method works on all platforms, or clarify any platform-specific steps if necessary.
- Include command-line examples for both Windows (PowerShell) and Linux (bash) where relevant, to ensure parity.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ssl-certificate-management.md
...cles/application-gateway/ssl-certificate-management.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation references both PowerShell and Azure CLI for listing SSL certificates, but it mentions the PowerShell command before the Azure CLI command. No Linux-specific tools or examples are provided, but the CLI example is cross-platform. There are no exclusive Windows tools or patterns, and the rest of the documentation is portal-focused and platform-neutral.
Recommendations
- When listing command-line examples, alternate the order or explicitly mention that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Consider providing a Linux shell example (e.g., Bash) for Azure CLI usage to reinforce cross-platform applicability.
- Add a brief note clarifying that PowerShell is available on Linux and macOS as well, or link to installation instructions for non-Windows users.
- Ensure that any future command-line or scripting examples are balanced between platforms, or use Azure CLI as the default for cross-platform parity.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/use-server-sent-events.md
...articles/application-gateway/use-server-sent-events.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific examples or commands, but it also lacks any practical configuration examples for either Windows or Linux. There is no explicit Windows bias, but the absence of concrete examples (such as using Powershell, Windows tools, or Linux shell commands) means Linux parity is not addressed. If future updates add examples, care should be taken to include both Windows and Linux instructions.
Recommendations
- When adding practical configuration steps, provide both Windows (e.g., Powershell, CMD) and Linux (e.g., Bash, systemd) examples for setting headers and configuring backend servers.
- Include sample commands for setting HTTP headers in both Windows (IIS, Powershell) and Linux (Apache, Nginx, curl) environments.
- If referencing tools or logs, mention both Windows and Linux equivalents (e.g., Event Viewer and journalctl, or IIS logs and Apache/Nginx logs).
- Ensure that any troubleshooting or monitoring steps are cross-platform.