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 51-75 of 981 flagged pages
Application Gateway Use with Internal Load Balancer - Azure Application Gateway ...les/application-gateway/application-gateway-ilb-arm.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses Windows PowerShell (Az module) for all examples and instructions, with no mention of Azure CLI, Bash, or Linux-native tools. The setup and management steps are presented only with PowerShell cmdlets, and references to switching PowerShell modes and using Windows PowerShell are made before any alternative is discussed (none are provided). This creates a strong Windows-centric bias and excludes Linux/macOS users who may prefer or require cross-platform tools.
Recommendations
  • Add equivalent Azure CLI (az) commands for each step, with Bash syntax examples.
  • Include notes or sections for Linux/macOS users, clarifying how to perform the same operations from those platforms.
  • Reference Azure Cloud Shell, which supports both PowerShell and Bash, as a cross-platform option.
  • Avoid language such as 'switch PowerShell mode' or 'Using Windows PowerShell' unless alternatives are also presented.
  • Ensure that links and references include documentation for both PowerShell and CLI approaches.
GitHub Create Pull Request
Application Gateway TLS policy overview for Azure Application Gateway ...ion-gateway/application-gateway-ssl-policy-overview.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily through its references to PowerShell for configuration and details retrieval, with no mention of Linux-specific tools or examples (such as Bash, Azure CLI on Linux, or OpenSSL). PowerShell is listed first and most prominently as the method for viewing cipher suite ordering and for configuring TLS policies, and the 'Next steps' section links only to a PowerShell-based configuration guide. There are no Linux, Bash, or cross-platform CLI examples provided, nor is there mention of how to perform these tasks on Linux systems.
Recommendations
  • Add Azure CLI examples for configuring and viewing TLS policies, ensuring they work on both Windows and Linux.
  • Provide Bash script examples for Linux users where applicable.
  • Include references and links to Linux-friendly tools (e.g., OpenSSL, curl) for testing TLS connections and cipher suites.
  • Ensure that documentation for configuration and management tasks is platform-neutral, or explicitly provides both Windows (PowerShell) and Linux (CLI/Bash) instructions.
  • Update 'Next steps' to include links to cross-platform guides, not just PowerShell.
GitHub Create Pull Request
Application Gateway Certificates required to allow backend servers ...ion-gateway/certificates-for-backend-authentication.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively provides certificate export instructions using Windows Certificate Manager and PowerShell, with screenshots and step-by-step guidance tailored to Windows users. There are no examples or guidance for performing equivalent operations on Linux or macOS, nor are cross-platform tools (such as OpenSSL) mentioned. The 'Next steps' section also references PowerShell specifically for further configuration.
Recommendations
  • Add equivalent certificate export instructions for Linux and macOS using OpenSSL or other native tools.
  • Provide command-line examples for exporting certificates in Base-64 encoded X.509 (.CER) format using OpenSSL.
  • Include screenshots or terminal output for Linux/macOS workflows.
  • Mention cross-platform tools and clarify that the process is not limited to Windows.
  • Update 'Next steps' to reference both PowerShell and CLI/Bash alternatives for configuring Application Gateway.
GitHub Create Pull Request
Application Gateway WebSocket support in Azure Application Gateway ...s/application-gateway/application-gateway-websocket.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily by referencing Azure PowerShell and linking to a 'quick-create-powershell.md' page as the next step, without mentioning or providing equivalent Linux or cross-platform CLI examples. There is no mention of Azure CLI, Bash, or Linux-specific tooling, nor are there examples or guidance for users on non-Windows platforms. The configuration snippets are generic ARM template JSON, which is platform-neutral, but the operational guidance and next steps are Windows-centric.
Recommendations
  • Include Azure CLI (az) examples alongside or before PowerShell examples for creating and configuring Application Gateway listeners and backend pools.
  • Update the 'Next steps' section to reference both PowerShell and Azure CLI quick-create guides, or provide a unified guide with both sets of instructions.
  • Explicitly mention that configuration can be performed on Linux, macOS, or Windows, and provide links to cross-platform tooling.
  • Add Bash or shell script examples where appropriate, especially for backend server configuration or health probe testing.
  • Ensure parity in documentation by reviewing all operational instructions for platform neutrality and including Linux/macOS alternatives wherever Windows/PowerShell is referenced.
GitHub Create Pull Request
Application Gateway Azure Application Gateway infrastructure configuration ...es/application-gateway/configuration-infrastructure.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily through its use of Azure PowerShell cmdlets for operational examples (such as restarting the Application Gateway), without providing equivalent Azure CLI or Linux shell commands. References to tooling and operational steps are Windows-centric, and there are no explicit Linux or cross-platform examples or instructions. This may disadvantage users who prefer or require Linux-based workflows.
Recommendations
  • Provide Azure CLI examples alongside PowerShell commands for all operational tasks, especially for actions like restarting the Application Gateway.
  • Explicitly mention that both PowerShell and Azure CLI are supported, and link to cross-platform installation guides for Azure CLI.
  • Where possible, include bash/Linux shell command snippets for common tasks, or clarify that instructions apply equally to Linux and macOS environments.
  • Review all sections for implicit assumptions of Windows environments and add clarifications or alternatives for Linux users.
  • Add a note or section on cross-platform management, highlighting parity between Windows and Linux tooling for Azure operations.
GitHub Create Pull Request
Application Gateway Configure an internal load balancer (ILB) endpoint ...configure-application-gateway-with-private-frontend-ip.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively using Windows Server as the VM image in examples, providing only PowerShell-based instructions for backend setup (IIS installation), and omitting Linux-based alternatives or CLI examples. Windows tools and patterns (IIS, PowerShell) are mentioned and used without reference to Linux equivalents, and Windows is presented as the default/only option for backend servers.
Recommendations
  • Include Linux-based examples, such as using Ubuntu or CentOS as VM images.
  • Provide instructions for installing a web server (e.g., Apache or Nginx) on Linux VMs using Bash/Azure CLI.
  • Offer both PowerShell and Bash/Azure CLI commands for VM extension configuration.
  • Present Windows and Linux options side-by-side or in parallel sections to ensure parity.
  • Explicitly mention that backend pools can use Linux VMs and provide guidance for their setup.
GitHub Create Pull Request
Application Gateway Create Azure Application Gateway custom error pages ...blob/main/articles/application-gateway/custom-error.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively provides Azure PowerShell examples for configuring custom error pages in Application Gateway, with no mention of Azure CLI, Bash, or Linux-native tooling. The configuration section is labeled 'Azure PowerShell configuration' and links only to PowerShell cmdlet references. There are no Linux or cross-platform command-line instructions, and PowerShell is presented as the sole automation method, which may disadvantage users on Linux or macOS platforms.
Recommendations
  • Add equivalent Azure CLI examples for all configuration steps, demonstrating how to set custom error pages using az network application-gateway commands.
  • Include Bash script snippets for Linux users, showing how to automate configuration via Azure CLI.
  • Explicitly mention that both PowerShell and CLI can be used, and provide links to CLI documentation.
  • Ensure screenshots and UI instructions do not assume a Windows environment.
  • Review references and links to ensure parity between PowerShell and CLI documentation.
GitHub Create Pull Request
Application Gateway Tutorial: Create and configure an application gateway to host multiple web sites using the Azure portal ...es/application-gateway/create-multiple-sites-portal.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a clear Windows bias. Virtual machine creation is demonstrated exclusively with Windows Server, and all backend configuration and testing instructions (IIS installation, hosts file editing, DNS commands) use Windows-specific tools and paths. PowerShell is the only scripting environment referenced for VM extension management. There are no Linux VM examples, nor are Linux equivalents (such as Apache/Nginx setup, /etc/hosts editing, or Bash commands) provided or mentioned.
Recommendations
  • Provide parallel instructions for creating Linux VMs (e.g., Ubuntu), including steps for installing a web server such as Apache or Nginx.
  • Include Linux-specific commands for editing /etc/hosts and managing DNS cache (e.g., 'sudo nano /etc/hosts', 'sudo systemd-resolve --flush-caches').
  • Offer Bash/Azure CLI examples alongside PowerShell for VM extension management and other automation tasks.
  • Clarify that Application Gateway supports both Windows and Linux backends, and show how to configure each.
  • Add screenshots or code snippets demonstrating Linux workflows where appropriate.
GitHub Create Pull Request
Application Gateway Tutorial: Create an application gateway with URL path-based routing rules using Azure portal ...rticles/application-gateway/create-url-route-portal.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. It exclusively uses Windows Server virtual machines as backend examples, provides only PowerShell commands for configuration (specifically for installing IIS), and focuses on IIS (a Windows web server) for testing. There are no Linux VM creation steps, no Linux web server installation instructions (e.g., Apache or Nginx), and no Bash or Azure CLI examples for Linux users. Windows tools and patterns are mentioned first and exclusively throughout the tutorial.
Recommendations
  • Add parallel instructions for creating Linux virtual machines (e.g., Ubuntu) as backend servers.
  • Include steps to install a Linux web server (such as Apache or Nginx) on the Linux VMs, with corresponding commands.
  • Provide Azure CLI or Bash examples for installing web servers and configuring VM extensions on Linux.
  • Mention Linux as a supported backend OS in the prerequisites and throughout the tutorial.
  • Show screenshots and test results for both Windows (IIS) and Linux (Apache/Nginx) backend pools.
  • Ensure that references to tools and commands are platform-neutral or presented in both Windows and Linux variants.
GitHub Create Pull Request
Application Gateway Diagnostic logs for Application Gateway for Containers ...cles/application-gateway/for-containers/diagnostics.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides detailed instructions for enabling diagnostic logging via the Azure portal and PowerShell, both of which are Windows-centric tools. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or ARM templates. The PowerShell example is the only command-line method shown, and it is presented before any mention of Linux alternatives (which are absent). This creates a bias toward Windows users and may hinder Linux users from easily following the documentation.
Recommendations
  • Add equivalent Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux.
  • Include Bash script samples for common logging tasks.
  • Mention and provide examples for ARM template or Bicep deployments for diagnostic settings.
  • Explicitly state that the instructions apply to both Windows and Linux, and clarify tool availability.
  • Reorder examples so that cross-platform tools (Azure CLI, ARM templates) are presented before or alongside PowerShell.
GitHub Create Pull Request
Application Gateway What is Application Gateway for Containers? ...rticles/application-gateway/for-containers/overview.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page shows evidence of Windows bias primarily in the 'Deployment strategies' section, where Windows-centric tools (Azure portal, CLI, PowerShell, Terraform) are listed for resource management. PowerShell is mentioned explicitly, and no Linux-specific tools or examples (such as Bash, Azure CLI on Linux, or kubectl commands) are provided. The order of tools also places PowerShell before Terraform, which may reinforce a Windows-first perspective. There are no explicit Linux or cross-platform command examples, nor is there guidance for Linux users.
Recommendations
  • Include Linux-specific and cross-platform examples, such as Azure CLI commands run from Bash or shell scripts.
  • Clarify that Azure CLI and Terraform are cross-platform and can be used on Linux, macOS, and Windows.
  • Provide example workflows for both Windows (PowerShell) and Linux (Bash/shell), especially for resource provisioning and management.
  • Avoid listing PowerShell before cross-platform tools unless contextually relevant; consider grouping tools by platform or indicating their cross-platform nature.
  • Add a note or section highlighting parity and best practices for Linux users managing Application Gateway for Containers.
GitHub Create Pull Request
Application Gateway Troubleshoot session affinity issues ...oubleshoot-application-gateway-session-affinity-issues.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. PowerShell is the only CLI example given for checking settings, and Fiddler (a Windows-only tool) is exclusively used for traffic analysis, with installation instructions referencing Windows-specific actions (e.g., 'Run as administrator'). No Linux equivalents (such as Azure CLI, tcpdump, curl, or Wireshark) are mentioned, nor are Linux troubleshooting workflows or tools provided.
Recommendations
  • Provide Azure CLI examples for checking Application Gateway settings, alongside PowerShell.
  • Include Linux-compatible web debugging tools (e.g., Wireshark, mitmproxy, curl) and show how to use them for session affinity troubleshooting.
  • Add installation and usage instructions for these tools on Linux and macOS.
  • Ensure screenshots and step-by-step guides are platform-agnostic or include both Windows and Linux workflows.
  • Explicitly mention that Fiddler is Windows-only and suggest alternatives for other operating systems.
GitHub Create Pull Request
Application Gateway HTTP response codes - Azure Application Gateway ...in/articles/application-gateway/http-response-codes.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates Windows bias by referencing NTLM authentication (a Windows-specific protocol) and linking to Windows documentation first when discussing backend authentication issues. IIS (a Windows web server) is mentioned and explained in detail before Nginx (a popular Linux web server), with configuration guidance and links provided for IIS but less detail for Nginx. There are no examples or troubleshooting steps using Linux tools or environments, and no mention of Linux-specific authentication mechanisms or troubleshooting patterns.
Recommendations
  • Include Linux-specific authentication scenarios (e.g., Kerberos, LDAP) and troubleshooting steps alongside NTLM.
  • Provide equivalent configuration and troubleshooting details for popular Linux web servers (e.g., Apache, Nginx) before or alongside IIS.
  • Add examples and links for Linux tools and commands (e.g., curl, journalctl, systemd logs) for troubleshooting.
  • Ensure that references to backend server configuration (timeouts, authentication) are presented in a cross-platform manner, not Windows-first.
  • Balance documentation by providing parity in detail and guidance for both Windows and Linux environments.
GitHub Create Pull Request
Application Gateway Application Gateway high traffic volume support ...n/articles/application-gateway/high-traffic-support.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias, primarily through references to PowerShell for configuration tasks (e.g., WAF custom rules, TLS policy configuration) and the lack of equivalent Linux/CLI examples. No explicit Linux tools or shell commands are provided, and PowerShell is mentioned as the method for certain advanced configurations. There are no examples or instructions for Bash, Azure CLI, or other cross-platform tools, which may disadvantage Linux users.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all tasks currently described with PowerShell, especially for configuring WAF custom rules and TLS policies.
  • Mention cross-platform tools (e.g., Azure CLI, REST API) before or alongside PowerShell, making it clear that these tasks can be performed on Linux, macOS, and Windows.
  • Add links to documentation pages that describe how to perform the same configuration steps using Azure CLI or ARM templates.
  • Review all configuration and automation instructions to ensure Linux parity and avoid implying PowerShell is the only or preferred method.
GitHub Create Pull Request
Application Gateway Create an ingress controller by using an existing Application Gateway deployment ...ication-gateway/ingress-controller-install-existing.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Several command examples use PowerShell scripting and variables (e.g., $resourceGroup, $identityName), which are specific to Windows environments and not directly compatible with Linux/macOS shells. PowerShell examples are provided before or instead of Bash equivalents in key identity and role assignment steps. The backup section references PowerShell scripts as part of the exported templates. While Azure CLI and Bash commands are present, the use of PowerShell syntax and variables may hinder Linux parity and accessibility.
Recommendations
  • Provide all command examples in both Bash (sh) and PowerShell, or default to Bash for cross-platform compatibility.
  • Replace PowerShell variable syntax ($var) with Bash equivalents (var=value) and use Bash command substitution where appropriate.
  • Explicitly mention Linux/macOS compatibility for all CLI commands and scripts.
  • Ensure that any referenced scripts (e.g., in exported templates) include Bash versions alongside PowerShell.
  • Review and update all code blocks to use Bash unless a Windows-specific scenario is being described.
  • Add a note clarifying that PowerShell commands are for Windows users and provide Bash alternatives for Linux/macOS users.
GitHub Create Pull Request
Application Gateway Configure Application Gateway with a frontend public IPv6 address using the Azure portal ...application-gateway/ipv6-application-gateway-portal.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates Windows bias by exclusively using Windows Server as the backend VM example and providing only PowerShell commands for backend configuration (IIS installation). There are no Linux VM examples, nor are there instructions for installing a web server on Linux or using Bash/CLI commands. Windows tools and patterns are mentioned exclusively, and Linux alternatives are absent.
Recommendations
  • Add Linux VM examples alongside Windows, such as Ubuntu or CentOS, for backend pool configuration.
  • Provide instructions for installing a web server (e.g., Apache or Nginx) on a Linux VM, including relevant Bash/CLI commands.
  • Include Azure CLI and/or Bash script examples for backend configuration, not just PowerShell.
  • Mention that both Windows and Linux VMs are supported as backend targets, and link to relevant documentation for each.
  • Ensure screenshots and walkthroughs demonstrate parity between Windows and Linux scenarios.
GitHub Create Pull Request
Application Gateway Hosting multiple sites on Azure Application Gateway ...articles/application-gateway/multiple-site-overview.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently mentioning Azure PowerShell before Azure CLI in both instructions and links, and by providing PowerShell-specific flags and examples. The 'Next steps' section lists PowerShell before CLI, and the wildcard host names section gives PowerShell syntax first. There are no Linux-specific tools or shell examples (e.g., Bash), and the CLI instructions are generic rather than tailored for Linux environments. The documentation assumes familiarity with PowerShell, a Windows-centric tool, and does not provide parity for Linux users beyond the CLI.
Recommendations
  • Alternate the order of PowerShell and CLI instructions, or list CLI first to balance representation.
  • Provide explicit Bash shell examples for CLI commands, including Linux-specific nuances (such as quoting, environment variables, etc.).
  • Include a section or note for Linux users, highlighting any differences or considerations when using Azure CLI on Linux.
  • Reference cross-platform tools (e.g., Terraform, ARM templates) earlier and more prominently to avoid Windows tool bias.
  • Ensure that all examples and walkthroughs are available for both PowerShell and CLI, and consider adding screenshots or terminal outputs from Linux environments.
GitHub Create Pull Request
Application Gateway Export trusted client CA certificate chain for client authentication ...ateway/mutual-authentication-certificate-management.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily Windows-centric: all certificate export steps rely on Windows GUI tools (Certificate Manager, Certificate Export Wizard) and PowerShell is mentioned as the way to open certificate management. Linux alternatives (such as using OpenSSL or command-line tools) are not provided for exporting certificates or viewing certificate chains. Only in the final concatenation step is a Linux command shown, and even there, the Windows command is listed first. There are no screenshots or step-by-step instructions for Linux environments.
Recommendations
  • Provide equivalent Linux instructions for exporting certificates, e.g., using OpenSSL to extract public and CA certificates.
  • Include Linux command-line examples for viewing certificate details and exporting certificate chains.
  • Add screenshots or terminal output examples for Linux workflows.
  • Mention Linux tools (such as openssl, certtool) alongside Windows tools, and avoid listing Windows steps first by default.
  • Clarify that the process can be performed on both Windows and Linux, and provide parity in guidance for both platforms.
GitHub Create Pull Request
Application Gateway Deploy an Azure Application Gateway with an IPv6 frontend ...ation-gateway/ipv6-application-gateway-arm-template.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates bias towards Windows environments by exclusively using IIS (a Windows web server) for backend validation, referencing Azure PowerShell for resource cleanup, and omitting Linux-based alternatives or examples. There are no instructions or examples for deploying or validating with Linux VMs (e.g., using Apache or Nginx), nor are Linux command-line tools (such as Azure CLI or Bash) used for resource management.
Recommendations
  • Include examples for deploying Linux VMs in the backend pool, such as Ubuntu with Apache or Nginx, alongside or instead of IIS.
  • Provide validation steps using Linux-based web servers (e.g., curl to test Apache/Nginx response) in addition to IIS.
  • Offer resource cleanup instructions using Azure CLI (az group delete) and Bash, not just Azure PowerShell.
  • Clarify that both Windows and Linux VMs are supported and provide parity in documentation examples.
  • Add notes or links to relevant Linux documentation for users who prefer non-Windows environments.
GitHub Create Pull Request
Application Gateway TLS termination with Azure Key Vault certificates ...b/main/articles/application-gateway/key-vault-certs.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for key configuration steps, referencing PowerShell before Azure CLI or ARM templates, and omitting explicit Linux shell (bash) or cross-platform CLI instructions. The use of PowerShell-centric tooling and terminology may disadvantage Linux users or those preferring bash/CLI workflows.
Recommendations
  • Provide equivalent Azure CLI (bash) examples alongside PowerShell for all configuration steps, especially for referencing Key Vault secrets and configuring Application Gateway.
  • Explicitly mention cross-platform compatibility and clarify which steps can be performed using CLI, ARM templates, or Bicep, not just PowerShell.
  • Reorder examples so that CLI/bash instructions are presented before or alongside PowerShell, ensuring Linux parity.
  • Add troubleshooting and automation guidance for Linux environments, including scripting with Azure CLI.
  • Include notes or links to platform-agnostic documentation for certificate management and deployment.
GitHub Create Pull Request
Application Gateway Overview of mutual authentication on Azure Application Gateway .../application-gateway/mutual-authentication-overview.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and references before CLI equivalents, and by omitting any Linux-specific certificate management or command-line examples (e.g., OpenSSL). The 'Next steps' section directs users to a PowerShell-focused guide, reinforcing the Windows-centric approach. There is no mention of Linux tools or workflows for certificate extraction, management, or validation, and the CLI example is minimal compared to the PowerShell section.
Recommendations
  • Add Linux-specific examples for certificate extraction and management, such as using OpenSSL commands to extract and prepare certificate chains.
  • Provide parity in example depth for Azure CLI and PowerShell, ensuring CLI instructions are as comprehensive as PowerShell ones.
  • Include references to Linux tools and workflows (e.g., bash scripts, OpenSSL, keytool) for certificate handling and validation.
  • In 'Next steps', link to both PowerShell and Azure CLI guides, and consider adding a Linux-focused walkthrough.
  • Explicitly mention cross-platform compatibility and provide guidance for both Windows and Linux users throughout the documentation.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway v2? .../blob/main/articles/application-gateway/overview-v2.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell scripts and commands for migration and preview registration, with no mention of Linux shell equivalents or cross-platform CLI usage. The 'Next steps' section links to a PowerShell-based tutorial, and the migration guidance centers on a PowerShell script from the PowerShell Gallery. There is no coverage of Bash, Azure CLI, or Linux-native tooling, nor are Linux-specific examples or instructions provided.
Recommendations
  • Provide equivalent Azure CLI (bash/shell) examples for all PowerShell commands, especially for migration and preview registration/unregistration.
  • Include links to tutorials for creating and managing Application Gateway using Azure CLI on Linux/macOS.
  • Explicitly mention cross-platform support and clarify which instructions are OS-agnostic.
  • Where PowerShell scripts are referenced, note how Linux users can run them (e.g., via Azure Cloud Shell) or provide alternative scripts in Bash.
  • Ensure that Linux and macOS users are considered in all step-by-step guides and migration instructions.
GitHub Create Pull Request
Application Gateway Configure Azure Application Gateway Private Link ...articles/application-gateway/private-link-configure.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell examples and cmdlet references, which are native to Windows environments. The PowerShell tab and examples precede the Azure CLI section, and the CLI examples are less detailed. There is no mention of Linux-specific tools, shell environments, or cross-platform scripting considerations. The documentation assumes familiarity with Windows-centric tools and patterns, which may disadvantage Linux users.
Recommendations
  • Provide Bash shell examples alongside Azure CLI commands, including environment setup and scripting best practices for Linux users.
  • Ensure CLI examples are as detailed and comprehensive as PowerShell examples, covering all steps and edge cases.
  • Mention and link to Linux-specific documentation or troubleshooting guides where relevant.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, and provide guidance for installing and using CLI on Linux.
  • Consider reordering sections so that CLI examples appear before or alongside PowerShell, to avoid implicit prioritization of Windows tools.
  • Include notes or tips for Linux users, such as handling environment variables, file paths, and permissions.
GitHub Create Pull Request
Application Gateway Quickstart: Direct web traffic using the portal ...in/articles/application-gateway/quick-create-portal.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively using Windows Server virtual machines as backend targets and providing only Windows-specific instructions (such as installing IIS via PowerShell). There are no Linux VM examples, nor instructions for installing a Linux web server (e.g., Apache or Nginx). The only VM creation walkthrough uses Windows Server, and the only backend setup uses IIS and PowerShell. The testing and verification steps are also Windows-centric. While Azure CLI is mentioned as an alternative, all concrete examples and screenshots are Windows-focused.
Recommendations
  • Add parallel instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
  • Provide Linux-specific commands for installing a web server (such as Apache or Nginx) for testing.
  • Include examples using Bash/SSH in Azure Cloud Shell, not just PowerShell.
  • Show how to add Linux VMs to the backend pool and verify connectivity.
  • Ensure screenshots and walkthroughs represent both Windows and Linux scenarios.
  • Explicitly mention that Application Gateway supports both Windows and Linux backends, and link to relevant documentation.
GitHub Create Pull Request
Application Gateway HTTP to HTTPS redirection in portal - Azure Application Gateway ...s/application-gateway/redirect-http-to-https-portal.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All command-line examples use PowerShell, and instructions for certificate creation, IIS installation, and VM scale set configuration are tailored exclusively for Windows environments. The VM scale set defaults to Windows Server, and there are no equivalent Linux instructions or examples provided. Windows tools and patterns (e.g., New-SelfSignedCertificate, Export-PfxCertificate, IIS installation via PowerShell) are mentioned without Linux alternatives.
Recommendations
  • Provide equivalent Linux examples for certificate creation (e.g., using OpenSSL) and exporting certificates.
  • Include instructions for deploying a Linux-based VM scale set (e.g., Ubuntu) and configuring a web server such as Apache or Nginx.
  • Offer Bash/Azure CLI command alternatives alongside PowerShell commands.
  • Clarify that both Windows and Linux backend pools are supported, and link to relevant Linux documentation.
  • Demonstrate how to install and configure a web server on Linux VMs using Custom Script Extension or cloud-init.
GitHub Create Pull Request
← Previous Page 3 of 40 Next →