Application Gateway
372
Total Pages
310
Linux-Friendly Pages
62
Pages with Bias
16.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
172 issues found
Showing 151-172 of 172 flagged pages
Application Gateway
Configure Azure Application Gateway Private Link
...articles/application-gateway/private-link-configure.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents configuration options in the order: Azure portal, Azure PowerShell, and Azure CLI. The PowerShell section is detailed and extensive, with full command walkthroughs and cmdlet references, while the Azure CLI section is present but slightly less emphasized. There are no Linux/macOS-specific notes, nor are there Bash or shell script examples. The documentation does not mention Linux tools or patterns, and the PowerShell example precedes the CLI example, which may be more familiar to Linux/macOS users.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
- Add explicit notes confirming that Azure CLI commands work on Linux/macOS and provide installation instructions or links for those platforms.
- Include Bash or shell script snippets for common tasks, where appropriate.
- Add troubleshooting or environment setup tips for Linux/macOS users, such as handling authentication or permissions.
- Ensure parity in detail and completeness between PowerShell and CLI sections.
Create Pull Request
Application Gateway
WebSocket support in Azure Application Gateway
...s/application-gateway/application-gateway-websocket.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias by referencing Azure PowerShell and linking to a PowerShell-based quickstart as the next step, without mentioning or providing equivalent Azure CLI or Linux/macOS-friendly instructions. There are no explicit Linux/macOS examples or tools referenced, and PowerShell is mentioned before alternatives.
Recommendations
- Include references and links to Azure CLI-based quickstart guides alongside PowerShell, ensuring Linux/macOS users have a clear path.
- Explicitly mention that configuration can be performed via Azure CLI, ARM templates, or the Azure portal, not only PowerShell.
- Provide example commands for both Azure PowerShell and Azure CLI when discussing listener or gateway creation.
- Clarify that the backend server can run on any OS, and provide sample backend setup instructions for Linux (e.g., using Nginx or Apache with WebSocket support).
Application Gateway
Troubleshoot Application Gateway for Containers
...cation-gateway/for-containers/troubleshooting-guide.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux and Windows examples for filtering logs, but the Windows example is shown second and uses Windows-specific tooling (findstr). There is no exclusive Windows bias; all core troubleshooting steps use cross-platform tools (kubectl, helm), and Linux examples are present and shown first. No critical steps are Windows-only.
Recommendations
- Continue to provide both Linux and Windows examples for commands involving OS-specific tools.
- Consider grouping OS-specific examples in tabbed sections for clarity and parity.
- Ensure that all troubleshooting steps can be completed on Linux/macOS without requiring Windows-only tools.
- Explicitly mention macOS where Linux instructions apply equally.
Application Gateway
Azure Application Gateway configuration overview
...articles/application-gateway/configuration-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists Windows-centric tools (PowerShell) before cross-platform options (Azure CLI) in the 'Next steps' section, which may subtly prioritize Windows workflows. However, no examples or instructions are given in this overview, and Linux/macOS users are not blocked from completing any tasks.
Recommendations
- List cross-platform tools (Azure CLI) before Windows-specific ones (PowerShell) to avoid implicit prioritization.
- Ensure that subsequent linked articles provide Linux/macOS examples and parity for all configuration steps.
- Explicitly mention that Azure CLI works on Windows, Linux, and macOS to encourage platform-neutral usage.
Application Gateway
Application gateway components
.../application-gateway/application-gateway-components.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page lists Azure PowerShell (Windows-centric) before Azure CLI (cross-platform) in the 'Next steps' section, subtly prioritizing Windows tooling. However, throughout the main content, there are no examples, commands, or references that are exclusive to Windows or PowerShell, nor are there missing Linux/macOS equivalents.
Recommendations
- List Azure CLI before Azure PowerShell in the 'Next steps' section to emphasize cross-platform support.
- Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, if relevant.
- Ensure future examples and walkthroughs include both CLI and PowerShell commands, or default to CLI for parity.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for viewing backend health, but PowerShell is presented first and with more descriptive context, which may subtly prioritize Windows users. There are no Linux/macOS-specific tools or troubleshooting patterns mentioned, and no explicit Linux examples (e.g., Bash scripting or Linux-native troubleshooting tools). However, Azure CLI is cross-platform and included, mitigating most friction.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform parity.
- Explicitly mention that Azure CLI works on Linux/macOS and provide a Bash example for scripting or automation.
- Add troubleshooting tips or references relevant to Linux environments (e.g., using curl, openssl, or Linux network tools for backend health verification).
- Clarify that PowerShell Core is available on Linux/macOS if PowerShell usage is recommended.
Application Gateway
Configure Azure Monitor alerts for Application Gateway
...application-gateway/configure-alerts-with-templates.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page references the procedure for using ARM templates via a link that prioritizes CLI, PowerShell, and ARM methods, with PowerShell commonly associated with Windows. There is no explicit mention or example of Linux/macOS-specific tools or workflows, and no Bash or Azure CLI examples are shown directly on the page. The 'Deploy to Azure' button relies on the Azure Portal, which is cross-platform, but the referenced procedure link lists PowerShell before CLI and ARM, subtly prioritizing Windows tooling.
Recommendations
- Add explicit Azure CLI (bash) examples for deploying ARM templates, alongside or before PowerShell examples.
- Clarify that all procedures can be performed on Linux/macOS using Azure CLI, and provide direct links to Linux/macOS instructions.
- Ensure referenced links and procedures do not prioritize Windows/PowerShell over cross-platform tools.
- Include notes or sections for Linux/macOS users to highlight parity and any platform-specific considerations.
Application Gateway
Private Application Gateway deployment
...tion-gateway/application-gateway-private-deployment.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides onboarding and feature registration instructions for Azure Application Gateway using the Azure portal, PowerShell, and CLI. The PowerShell examples (which are Windows-centric) are presented before CLI examples in each section, and there is a notable emphasis on PowerShell commands and outputs. However, Azure CLI instructions are present and accurate, and no critical steps are Windows-only. There are no explicit Linux/macOS tool gaps, but the ordering and prominence of PowerShell may create minor friction for non-Windows users.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly mention that Azure CLI works on Linux/macOS and provide installation links for CLI on those platforms.
- Where possible, add notes or links for using Bash scripts or shell environments for automation on Linux/macOS.
- Ensure screenshots and UI references are not Windows-specific (e.g., avoid showing only Windows browser UI if relevant).
Application Gateway
Container networking with Azure Application Gateway for Containers
...ication-gateway/for-containers/container-networking.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits minor Windows bias in the 'Next steps' section, where the link to 'Deploy ALB Controller' specifically points to a Windows Helm installation tab by default. There are no explicit Linux/macOS examples or references, and no mention of Linux-specific tools or commands. The rest of the content is platform-neutral, focusing on Kubernetes networking concepts.
Recommendations
- Update the 'Deploy ALB Controller' link to either default to a platform-neutral tab or provide equal visibility for Linux/macOS installation instructions.
- Ensure all referenced quickstarts and tutorials include both Windows and Linux/macOS examples, especially for command-line operations (e.g., Helm, kubectl).
- Explicitly mention Linux/macOS compatibility and provide troubleshooting tips for non-Windows environments where relevant.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller
...ploy-application-gateway-for-containers-alb-controller.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates mild Windows bias, particularly in the Helm installation section, where Windows instructions and the use of Windows Package Manager (winget) are presented before Linux instructions. The only explicit command-line example for Helm installation on Windows uses PowerShell and winget, while the Linux example uses curl/bash. The rest of the documentation uses Azure CLI and Helm, which are cross-platform, but Windows-specific tools are mentioned first and more prominently.
Recommendations
- Present Linux and Windows installation instructions for Helm side-by-side or in parallel tabs, rather than listing Windows first.
- Include explicit macOS installation instructions for Helm, as macOS is a common platform for Kubernetes administrators.
- Avoid highlighting Windows-specific tools (e.g., winget) before cross-platform alternatives; mention them as one of several options.
- Ensure all command examples (Azure CLI, Helm, kubectl) are clearly stated to work on Linux, macOS, and Windows equally.
- Add a note clarifying that Azure CLI, Helm, and kubectl commands are cross-platform and provide troubleshooting tips for each OS.
Application Gateway
HTTP response codes - Azure Application Gateway
...in/articles/application-gateway/http-response-codes.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation exhibits mild Windows bias, notably in the troubleshooting section for HTTP 504 errors, where IIS (a Windows web server) is discussed first and in greater detail than Nginx (a common Linux web server). The IIS reference includes a direct link to Microsoft's documentation and specific configuration attributes, while the Nginx guidance is briefer and lacks equivalent detail or links. Additionally, NTLM authentication (Windows-specific) is mentioned in the 401 section, with no Linux authentication alternatives discussed.
Recommendations
- Provide Linux and macOS equivalents alongside Windows examples, especially for server configuration (e.g., Apache, Nginx, Caddy).
- Include links to official documentation for Linux tools (e.g., Nginx, Apache) similar to the IIS link.
- Discuss Linux authentication mechanisms (e.g., Kerberos, LDAP) in the 401 section, not just NTLM.
- Ensure troubleshooting steps and examples are balanced between Windows and Linux environments.
- When referencing server configuration, present Linux and Windows options in parallel or in separate, clearly labeled sections.
Application Gateway
How to migrate from Azure Application Gateway Ingress Controller Helm to AGIC add-on
...es/application-gateway/ingress-controller-migration.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively uses Azure CLI and Azure Portal for all examples and instructions, without mentioning or providing Linux/macOS-specific alternatives or considerations. There are no references to PowerShell, but the reliance on Azure CLI and Portal may implicitly favor Windows users, especially since no Linux shell or Kubernetes-native (kubectl, Helm) commands are shown for migration steps.
Recommendations
- Explicitly state that Azure CLI commands work on Linux/macOS and provide shell compatibility notes.
- Include examples using bash/zsh for Linux/macOS users, clarifying any differences in environment variables or command syntax.
- Mention that Azure Portal is web-based and platform-agnostic.
- Provide alternative steps using kubectl or Helm where possible, as these are cross-platform Kubernetes tools.
- Add troubleshooting notes for common issues on Linux/macOS (e.g., Azure CLI installation, authentication).
Application Gateway
What is Azure Application Gateway
...ocs/blob/main/articles/application-gateway/overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation lists Azure PowerShell as a primary method for creating an Application Gateway, with PowerShell examples referenced before Azure CLI. This ordering subtly prioritizes Windows-centric tooling. However, Azure CLI is also mentioned, and no examples are given directly in the overview, so Linux/macOS users are not blocked from completing tasks.
Recommendations
- List Azure CLI before PowerShell in 'Next steps' to reflect cross-platform parity.
- Explicitly state that Azure CLI works on Linux/macOS and is recommended for cross-platform scenarios.
- Ensure that all referenced quickstarts and tutorials provide both PowerShell and CLI examples, or link to platform-specific instructions.
- Consider adding a note about platform compatibility for each tool.
Application Gateway
Quickstart: Direct web traffic using Bicep
...ain/articles/application-gateway/quick-create-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment, validation, and cleanup. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented immediately alongside CLI in every example. There are no Linux/macOS-specific instructions or notes, nor any mention of Bash scripting, shell environments, or platform-specific considerations. The use of PowerShell may create friction for Linux/macOS users, as it is not natively available on those platforms.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Present Azure CLI examples first, with PowerShell as an alternative for Windows users.
- Add notes or links for installing Azure CLI on Linux/macOS.
- Consider removing PowerShell examples from the main flow, or placing them in a separate tab labeled 'Windows/PowerShell'.
- Add a brief section clarifying platform compatibility and recommending tools for each OS.
Application Gateway
Listener TLS certificate management in Application Gateway
...cles/application-gateway/ssl-certificate-management.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions both PowerShell and Azure CLI commands for listing SSL certificates, but PowerShell (a Windows-centric tool) is referenced first. No Linux/macOS-specific tools or examples are provided, and the CLI example is generic. There are no explicit Windows-only instructions, but the ordering shows a subtle Windows-first bias.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly mention that Azure CLI works on Linux/macOS and provide installation links.
- If PowerShell is referenced, clarify that PowerShell Core is available cross-platform, or provide Bash examples where relevant.
- Add a note or section for Linux/macOS users to ensure parity and clarity.
Application Gateway
Azure Monitor metrics for Application Gateway
...les/application-gateway/application-gateway-metrics.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias, primarily in the 'Next steps' section, where Power BI (a Microsoft/Windows-centric tool) is promoted for log visualization, with no mention of Linux/macOS-friendly alternatives. No command-line examples (PowerShell, Bash) are present, but the visualization and alerting instructions reference GUI workflows that are platform-agnostic. However, the exclusive mention of Power BI and lack of Linux-native visualization tools or examples may create friction for non-Windows users.
Recommendations
- Include examples or references to cross-platform log visualization tools, such as Grafana, Kibana, or open-source alternatives.
- If Power BI is mentioned, also provide instructions or links for using Azure Monitor logs with Linux/macOS-compatible tools.
- Explicitly state that the Azure portal and monitoring features are accessible from any OS/browser.
- Add CLI examples (Azure CLI, Bash) for metric retrieval and alert configuration to ensure parity for Linux/macOS users.
Application Gateway
Configure Azure Application Gateway Private Link
...articles/application-gateway/private-link-configure.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents configuration options for Azure Application Gateway Private Link via the Azure portal, PowerShell, and Azure CLI. The PowerShell section is detailed and extensive, with full command walkthroughs and cmdlet references, which may favor Windows users. The CLI section is present and provides parity in terms of step coverage, but PowerShell is listed before CLI in both the configuration options and the tab order, and the PowerShell section is slightly more verbose. There are no Linux/macOS-specific examples or notes, and no mention of Bash scripting or Linux-native tools. However, the CLI instructions are cross-platform and sufficient for Linux/macOS users.
Recommendations
- List Azure CLI before PowerShell in configuration options and tab order to signal cross-platform parity.
- Explicitly mention that Azure CLI commands work on Linux/macOS and provide a Bash example for scripting.
- Add a note clarifying that PowerShell Core is available on Linux/macOS, or link to installation instructions.
- Consider adding troubleshooting tips or environment setup notes for Linux/macOS users (e.g., Azure CLI installation, shell compatibility).
Application Gateway
What is Azure Application Gateway
...ocs/blob/main/articles/application-gateway/overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists Azure PowerShell (Windows-centric) as a primary method for creating an Application Gateway before mentioning Azure CLI, which is cross-platform. No explicit Linux/macOS bias is present, but the ordering may subtly prioritize Windows tools.
Recommendations
- List Azure CLI before Azure PowerShell in 'Next steps' to emphasize cross-platform support.
- Explicitly state that Azure CLI works on Linux/macOS/Windows to encourage non-Windows users.
- Ensure that all referenced quickstart guides (portal, PowerShell, CLI) provide parity in instructions and examples for Linux/macOS users.
Application Gateway
Quickstart: Direct web traffic using Bicep
...ain/articles/application-gateway/quick-create-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, validation, and cleanup tasks. However, PowerShell is featured equally alongside CLI, and there is no mention of Linux-specific tools or shell environments. The order of presentation sometimes puts CLI first, but PowerShell is always present as an alternative. There are no Windows-only tools or patterns, but the presence of PowerShell may imply a Windows-centric approach, especially since Linux users are more likely to use Bash or shell scripts with Azure CLI.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily for Windows (or PowerShell Core for cross-platform).
- Add a note clarifying that all CLI examples are suitable for Bash (Linux/macOS) and Windows Command Prompt/PowerShell.
- Consider including Bash script examples for automation, or links to Linux/macOS-specific guidance.
- If PowerShell is shown, clarify its cross-platform availability (PowerShell Core) or provide links for Linux/macOS installation.
- Ensure that CLI examples are shown first to reinforce cross-platform parity.
Application Gateway
Listener TLS certificate management in Application Gateway
...cles/application-gateway/ssl-certificate-management.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by listing PowerShell commands before Azure CLI equivalents when referencing command-line management of SSL certificates. There are no Linux/macOS-specific examples or tools mentioned, and the only CLI example provided is Azure CLI, which is cross-platform, but PowerShell is referenced first. No explicit Windows-only tools or patterns are present, and the main focus is on portal-based management.
Recommendations
- List Azure CLI examples before PowerShell commands to emphasize cross-platform compatibility.
- Explicitly mention that Azure CLI works on Linux/macOS and provide links or notes for installation on those platforms.
- Add examples or references for certificate management using Bash or other Linux-native tools where relevant.
- Clarify that all portal operations are OS-agnostic and accessible from any supported browser.
Application Gateway
Generate self-signed certificate with a custom root CA
...ticles/application-gateway/self-signed-certificates.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by listing Windows before Linux in prerequisites, providing IIS (Windows) instructions before Apache/NGINX, and offering only Azure PowerShell sample code for uploading certificates to Application Gateway (with no Azure CLI or REST API example). The PowerShell sample uses Windows-style file paths and assumes a Windows environment. However, the core certificate generation steps use OpenSSL, which is cross-platform, and Linux web server configuration is covered.
Recommendations
- Add Azure CLI and/or REST API examples for uploading the root certificate and configuring Application Gateway, alongside the PowerShell sample.
- List Linux and Windows equally in prerequisites, or mention Linux first if OpenSSL is more commonly used there.
- Provide explicit instructions or links for importing certificates on Linux/macOS (e.g., adding to trusted root store), not just Windows.
- Use platform-neutral file paths in code samples, or provide both Windows and Linux/macOS examples.
- Ensure that web server configuration examples (Apache, NGINX) are as detailed as the IIS section, and consider listing Linux servers first.
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 lists Azure PowerShell as the first option for creating an Application Gateway, before mentioning Azure CLI. This ordering may suggest a Windows-centric bias, as PowerShell is traditionally associated with Windows environments, while Azure CLI is cross-platform and more commonly used on Linux and macOS. No explicit Linux-only examples or tools are missing, but the ordering could imply preference.
Recommendations
- List Azure CLI before Azure PowerShell when presenting cross-platform instructions, as CLI is natively supported on Linux, macOS, and Windows.
- Explicitly mention that both Azure CLI and PowerShell are available on all major platforms, and provide parity in examples for both.
- Consider adding examples or links for ARM templates or Terraform, which are platform-agnostic and popular in Linux environments.
- Review other documentation pages linked from this one to ensure Linux parity in walkthroughs and examples.