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

841 issues found
Showing 51-75 of 841 flagged pages
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
Application Gateway Renew an Azure Application Gateway certificate ...ain/articles/application-gateway/renew-certificates.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 a Windows bias by presenting Azure PowerShell instructions before Azure CLI, which is more cross-platform. The PowerShell example is detailed and uses Windows-centric patterns (e.g., ConvertTo-SecureString), while the CLI example is less emphasized. There are no Linux-specific instructions, nor are Linux command-line tools (like OpenSSL) mentioned for certificate handling. The portal instructions also implicitly assume a Windows workflow (PFX format, GUI navigation) without discussing Linux alternatives.
Recommendations
  • Provide Linux-specific examples, such as using OpenSSL to generate or convert certificates.
  • Present Azure CLI instructions before or alongside PowerShell, highlighting its cross-platform nature.
  • Mention certificate formats commonly used on Linux (e.g., PEM) and how to convert them to PFX if needed.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and provide command-line steps for Linux users.
  • Add troubleshooting tips for Linux environments, such as file permissions or path conventions.
GitHub Create Pull Request
Application Gateway Generate self-signed certificate with a custom root CA ...ticles/application-gateway/self-signed-certificates.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 exhibits mild Windows bias. Windows and Windows-specific tools (IIS, PowerShell) are mentioned before or more prominently than their Linux equivalents. The Azure PowerShell example is provided in detail, while Azure CLI is only briefly mentioned as an alternative. IIS instructions are listed before Apache and NGINX, and Windows file paths are used in PowerShell examples. There are no Linux-specific automation examples for uploading certificates to Application Gateway.
Recommendations
  • Provide Azure CLI examples alongside or before Azure PowerShell, especially for certificate upload and configuration.
  • Include Linux file path examples in addition to Windows paths in code samples.
  • Offer automation instructions for Linux environments, such as Bash scripts for certificate upload.
  • Balance the order of web server configuration instructions (e.g., alternate between IIS, Apache, and NGINX or group by OS).
  • Explicitly mention Linux equivalents for steps involving Windows tools (e.g., how to add a root certificate to Linux trusted store).
GitHub Create Pull Request
Application Gateway Enabling end to end TLS on Azure Application Gateway ...blob/main/articles/application-gateway/ssl-overview.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 Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific certificate formats (PFX), linking to Windows API documentation (PFXImportCertStore), and providing configuration instructions and next steps primarily via PowerShell. There are no Linux or cross-platform CLI examples, and Windows tools/patterns are mentioned exclusively or before any Linux equivalents. The guidance assumes familiarity with Windows-centric tooling and omits Linux-native certificate management and configuration approaches.
Recommendations
  • Provide equivalent instructions and examples for Linux users, such as using Azure CLI, Bash scripts, or ARM templates for configuration.
  • Reference cross-platform certificate formats and tools (e.g., PEM, OpenSSL) alongside PFX and Windows APIs.
  • Include links to Linux certificate management documentation and tools (e.g., OpenSSL, certbot).
  • Add parity in troubleshooting and configuration guides for both Windows and Linux environments.
  • Ensure that next steps and quickstarts offer both PowerShell and Azure CLI/Bash alternatives.
GitHub Create Pull Request
Application Gateway Tutorial: Protect your application gateway with Azure DDoS Network Protection ...n-gateway/tutorial-protect-application-gateway-ddos.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 demonstrates a Windows bias by exclusively using Windows Server virtual machines as backend examples, providing only PowerShell commands for IIS installation, and omitting any Linux VM or Linux web server setup instructions. Windows tools and patterns (IIS, PowerShell) are mentioned and used without Linux equivalents, and Windows is presented as the default/first choice for backend servers.
Recommendations
  • Include parallel instructions for deploying Linux-based backend VMs (e.g., Ubuntu) alongside Windows examples.
  • Provide Linux-specific commands (such as Bash/SSH and apt-get for installing Apache or Nginx) for web server setup and verification.
  • Offer Azure CLI or Bash script examples in addition to PowerShell for VM extension management and configuration.
  • Explicitly mention that Application Gateway supports both Windows and Linux backends, and illustrate with examples.
  • Balance screenshots and walkthroughs to show both Windows and Linux VM creation and configuration in the Azure portal.
GitHub Create Pull Request
Application Gateway Troubleshoot backend health issues in Azure Application Gateway ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-backend-health-troubleshooting.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by frequently providing PowerShell commands and Windows-specific troubleshooting steps (such as using certlm.msc and netstat via cmd), while Linux equivalents are either missing or mentioned after Windows. Examples for connectivity checks and certificate management are predominantly Windows-oriented, and Linux tools (like OpenSSL) are referenced less frequently and often without detailed step-by-step instructions. There is a lack of parity in example commands and troubleshooting workflows for Linux users.
Recommendations
  • Provide Linux CLI equivalents for all PowerShell commands (e.g., use az CLI, curl, netcat, ss, or ip commands).
  • Include Linux-specific troubleshooting steps for certificate management (e.g., using openssl, viewing certificates in /etc/ssl/certs, using systemctl for service status).
  • Offer example commands for network connectivity checks on Linux (e.g., nc, curl, telnet) alongside Windows Test-NetConnection.
  • Ensure that instructions for accessing certificate details and exporting certificates are available for Linux (e.g., openssl x509 -in ... -text, or using desktop environments' certificate viewers).
  • Present Windows and Linux examples side-by-side, or alternate which platform is mentioned first to avoid implicit prioritization.
  • Explicitly state that all troubleshooting steps apply to both Windows and Linux, and link to platform-specific guides where appropriate.
GitHub Create Pull Request
Application Gateway Private Application Gateway deployment ...tion-gateway/application-gateway-private-deployment.md
High Priority View Details →
Scanned: 2026-01-11 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 listing Azure PowerShell instructions before Azure CLI, providing detailed PowerShell command examples, and referencing Windows-centric tools and patterns (e.g., PowerShell cmdlets, screenshots of the Azure portal, and terminology familiar to Windows administrators). Linux-specific patterns, shell examples, or screenshots are absent, and the CLI instructions are less detailed. There is no mention of Linux-native tooling or shell scripting, nor any guidance for Linux users beyond the generic Azure CLI commands.
Recommendations
  • Alternate the order of PowerShell and CLI instructions, or present CLI examples first to avoid implicit prioritization of Windows tools.
  • Expand CLI sections to include more detailed output examples and troubleshooting steps, matching the depth of PowerShell coverage.
  • Include Linux shell scripting examples (e.g., bash scripts for feature registration and status checks) alongside PowerShell.
  • Add screenshots or walkthroughs using Azure CLI in a Linux terminal, not just the Azure portal.
  • Reference Linux-native tools and workflows where applicable, such as using curl for REST API calls or jq for output parsing.
  • Explicitly state that all features and steps are supported on Linux, and provide links to Linux-specific guidance where available.
GitHub Create Pull Request
Application Gateway Configure Azure Monitor alerts for Application Gateway ...application-gateway/configure-alerts-with-templates.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing the Azure Portal and linking to procedures that prioritize PowerShell and CLI usage, without providing Linux-specific instructions or examples. The 'Deploy to Azure' button and referenced guides assume a Windows-centric workflow, omitting Linux shell or cross-platform CLI examples for deploying ARM templates and configuring alerts.
Recommendations
  • Include explicit instructions and examples for deploying ARM templates using Azure CLI on Linux/macOS, such as 'az deployment group create' commands.
  • Provide Bash shell examples alongside any PowerShell or Windows-centric instructions.
  • Clarify that the Azure CLI is cross-platform and highlight usage on Linux/macOS where appropriate.
  • Add links to documentation or quickstart guides for Linux users, ensuring parity in workflow descriptions.
  • Avoid assuming use of the Azure Portal or Windows tools as the default; present platform-neutral options first or in parallel.
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-11 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 example OS for backend VMs, providing only PowerShell commands for IIS installation, and omitting any Linux-based examples or equivalent Bash/CLI instructions. The workflow assumes Windows tooling and patterns throughout, with no mention of Linux alternatives or parity.
Recommendations
  • Include parallel Linux examples for backend VM creation, such as using Ubuntu or CentOS images.
  • Provide Bash/Azure CLI commands for installing a web server (e.g., Apache or Nginx) on Linux VMs.
  • Add instructions for configuring backend pools with Linux VMs, including screenshots if possible.
  • Present both Windows and Linux options side-by-side in relevant sections, or alternate which OS is used first.
  • Clarify that Application Gateway supports both Windows and Linux backend servers.
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-11 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 instructions use Windows GUI tools (Certificate Manager, Certificate Export Wizard) and screenshots, with only a brief mention of PowerShell. There are no Linux or cross-platform CLI instructions for exporting certificates, and Linux is only referenced in the final concatenation step. The workflow assumes access to Windows-specific tools and patterns, leaving Linux users without guidance for equivalent tasks.
Recommendations
  • Add Linux-specific instructions for exporting certificates, such as using openssl or certtool.
  • Include CLI-based, cross-platform examples for certificate export and inspection.
  • Provide screenshots or terminal output for Linux workflows where appropriate.
  • Present both Windows and Linux methods side-by-side or in parallel sections, rather than Windows-first.
  • Reference Linux documentation and tools (e.g., openssl, gnome-keyring, etc.) where relevant.
GitHub Create Pull Request
← Previous Page 3 of 34 Next →