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 776-800 of 981 flagged pages
Application Gateway WebSocket support in Azure Application Gateway ...s/application-gateway/application-gateway-websocket.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page references Azure PowerShell and links to a 'quick-create-powershell.md' page as the next step for creating an Application Gateway, without mentioning or linking to Azure CLI or ARM template instructions, which are cross-platform. The only tool mentioned for creation is PowerShell, which is primarily associated with Windows, and there are no Linux/macOS-specific examples or parity guidance.
Recommendations
  • Include Azure CLI instructions and links alongside PowerShell for creating and configuring Application Gateway resources.
  • Reference ARM template deployment guides, which are platform-agnostic.
  • Explicitly mention that all configuration steps can be performed from Linux/macOS using Azure CLI or portal.
  • Add example commands for Linux/macOS users where relevant, especially in the 'Next steps' section.
GitHub Create Pull Request
Application Gateway Azure Application Gateway Backend Settings configuration ...les/application-gateway/configuration-http-settings.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation mentions that PowerShell and CLI support for certain TLS validation settings is 'coming soon', but does not provide any examples or instructions for Linux/macOS users. There are no explicit Linux or cross-platform CLI examples, and PowerShell is referenced as the primary automation tool, which is Windows-centric. This creates friction for users on Linux or macOS, as they lack clear guidance for configuring these settings outside the Azure Portal.
Recommendations
  • Add Azure CLI examples for all configuration steps, especially for TLS validation settings, and ensure they are shown alongside or before PowerShell examples.
  • Explicitly state cross-platform support and provide instructions for Linux/macOS users where automation or scripting is discussed.
  • Avoid referencing PowerShell exclusively; mention Azure CLI and REST API as alternatives and provide parity in documentation.
  • When features are not yet supported in CLI, provide a timeline or workaround for Linux/macOS users.
GitHub Create Pull Request
Application Gateway Configure an internal load balancer (ILB) endpoint ...configure-application-gateway-with-private-frontend-ip.md
Medium Priority View Details →
Scanned: 2026-01-13 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 page demonstrates a notable Windows bias: virtual machines are created using Windows Server images only, and all configuration and verification steps (such as installing IIS) rely exclusively on PowerShell commands and Windows tooling. There are no Linux VM examples, nor are there instructions for using Bash, SSH, or Linux-native web servers. This creates friction for users wishing to deploy Linux-based backends or use Linux/macOS for management.
Recommendations
  • Add parallel instructions for creating Linux virtual machines (e.g., Ubuntu) as backend servers.
  • Provide Bash/Azure CLI examples for installing a web server (such as Apache or Nginx) on Linux VMs.
  • Show how to use Azure Cloud Shell in Bash mode, not just PowerShell.
  • Include screenshots and command snippets relevant to Linux/macOS environments.
  • Explicitly mention that backend pools can contain Linux VMs and provide guidance for those setups.
GitHub Create Pull Request
Application Gateway Manage traffic to App Service ...main/articles/application-gateway/configure-web-app.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed PowerShell scripts for every step of the process, but does not include equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). All command-line automation is shown using PowerShell, which is primarily a Windows tool, and there are no instructions or code samples for Linux-native workflows. This creates friction for users on Linux or macOS who may not have PowerShell installed or prefer other tools.
Recommendations
  • Add Azure CLI examples for each step alongside PowerShell, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash script snippets or REST API examples where appropriate.
  • Explicitly mention that PowerShell examples can be run on Linux/macOS (if true), or provide installation guidance for PowerShell Core on non-Windows platforms.
  • Ensure that references to creating self-signed certificates, DNS configuration, and other tasks include Linux/macOS tooling (e.g., OpenSSL, dig, etc.).
  • Order examples so that cross-platform tools (Azure CLI) are shown before or alongside PowerShell.
GitHub Create Pull Request
Application Gateway Create Azure Application Gateway custom error pages ...blob/main/articles/application-gateway/custom-error.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only Azure PowerShell examples for configuring custom error pages, with no mention of Azure CLI, Bash, or Linux/macOS workflows. The PowerShell section is the sole code-based configuration method shown, and it appears before any mention of alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer CLI/Bash tools.
Recommendations
  • Add equivalent Azure CLI examples for both global and listener-level custom error page configuration.
  • Explicitly mention that Azure CLI and REST API can also be used, with links to relevant documentation.
  • Clarify cross-platform options in the requirements or configuration sections.
  • If PowerShell is required for certain features, state this clearly and provide guidance for Linux/macOS users on installing PowerShell Core or using CLI alternatives.
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
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The tutorial demonstrates a notable Windows bias: it exclusively uses Windows Server VMs as backend examples, provides only Windows PowerShell commands for IIS installation, and details editing the Windows hosts file with Windows-specific instructions and tools. There are no Linux VM examples, nor are there Linux shell commands or hosts file instructions for Linux/macOS users. Windows tools and patterns (e.g., ipconfig) are mentioned exclusively.
Recommendations
  • Include parallel instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
  • Provide Linux/macOS shell commands for installing a web server (e.g., Apache or Nginx) and editing the hosts file.
  • Add hosts file editing steps for Linux/macOS (e.g., using sudo nano /etc/hosts) and relevant commands (e.g., systemd-resolve --flush-caches).
  • Offer PowerShell and Bash/Azure CLI alternatives for VM extension installation.
  • Clarify that Application Gateway supports both Windows and Linux backends, and link to relevant documentation.
GitHub Create Pull Request
Application Gateway Diagnostic logs for Application Gateway for Containers ...cles/application-gateway/for-containers/diagnostics.md
Medium Priority View Details →
Scanned: 2026-01-13 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 logs using the Azure portal and PowerShell, both of which are Windows-centric tools. There are no CLI (az), Bash, or Linux/macOS-native examples for configuring diagnostic settings, and PowerShell is presented as the only command-line option. This creates friction for Linux/macOS users who may prefer or require cross-platform tools.
Recommendations
  • Add equivalent Azure CLI (az) examples for enabling diagnostic logs, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash script examples or instructions for Linux/macOS users.
  • Explicitly mention that PowerShell Core is available cross-platform if PowerShell must be used, but prioritize CLI examples.
  • Ensure that examples for Linux/macOS tools are presented alongside or before Windows-specific tools to avoid perceived prioritization.
GitHub Create Pull Request
Application Gateway Configure Azure Application Gateway TCP/TLS proxy ...n/articles/application-gateway/how-to-tcp-tls-proxy.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. It exclusively references deploying a SQL Server VM using Windows Server, and the only client tool mentioned for connecting to SQL Server is SQL Server Management Studio (SSMS), which is Windows-only. There are no examples or guidance for deploying SQL Server on Linux, nor are cross-platform SQL client tools (such as Azure Data Studio or sqlcmd) mentioned. This may create friction for users on Linux or macOS platforms.
Recommendations
  • Include instructions or options for deploying SQL Server on Linux (e.g., Ubuntu) in Azure.
  • Mention and provide examples for connecting to SQL Server using cross-platform tools such as Azure Data Studio, sqlcmd, or DBeaver.
  • Where screenshots or steps reference Windows-specific tools, add equivalent steps for Linux/macOS environments.
  • Clarify that the procedure is applicable to both Windows and Linux SQL Server VMs, if true, and note any differences.
GitHub Create Pull Request
Application Gateway Troubleshoot session affinity issues ...oubleshoot-application-gateway-session-affinity-issues.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. Troubleshooting steps reference Windows-specific tools (Fiddler, Internet Explorer), provide PowerShell as the only CLI example, and installation instructions assume a Windows environment (e.g., 'Run as administrator' for Fiddler setup). There are no Linux/macOS equivalents or examples for key steps such as CLI commands or web debugging, and Windows tools are mentioned first and exclusively.
Recommendations
  • Provide Azure CLI and/or REST API examples alongside PowerShell for checking Application Gateway settings.
  • Include instructions and screenshots for using cross-platform web debugging tools (e.g., Wireshark, mitmproxy, or browser developer tools) on Linux/macOS.
  • Mention browser compatibility issues with session affinity for browsers available on Linux/macOS (e.g., Firefox, Chrome), not just Internet Explorer.
  • Add installation and usage steps for Fiddler alternatives or Fiddler on non-Windows platforms.
  • Ensure troubleshooting steps are platform-agnostic or offer parallel guidance for Linux/macOS users.
GitHub Create Pull Request
Application Gateway Create an ingress controller by using an existing Application Gateway deployment ...ication-gateway/ingress-controller-install-existing.md
Medium Priority View Details →
Scanned: 2026-01-13 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-line examples use PowerShell syntax and variables, especially in identity and role assignment steps. PowerShell commands are presented before or instead of pure Bash alternatives, and the use of PowerShell variables ($var) is prevalent. While Azure CLI and Bash are also used, Linux/macOS users may encounter friction due to the PowerShell-centric examples and lack of explicit Bash equivalents for some steps.
Recommendations
  • Provide Bash equivalents for all PowerShell examples, especially for identity and role assignment steps.
  • Avoid using PowerShell variable syntax ($var) in CLI examples; use Bash-compatible syntax where possible.
  • Clearly indicate which commands are cross-platform and which are Windows-specific.
  • Where PowerShell is required, add a note or alternative for Linux/macOS users.
  • Ensure that examples using Azure CLI are shown in Bash syntax first, with PowerShell as an alternative if needed.
GitHub Create Pull Request
Application Gateway Deploy an Azure Application Gateway with an IPv6 frontend ...ation-gateway/ipv6-application-gateway-arm-template.md
Medium Priority View Details →
Scanned: 2026-01-13 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 by providing only PowerShell instructions for resource cleanup and configuring IIS on backend VMs (a Windows web server). There are no Linux-specific examples or alternatives for validation or cleanup, and the template appears to deploy Windows VMs by default.
Recommendations
  • Include Azure CLI and Bash examples for resource cleanup (e.g., 'az group delete').
  • Provide instructions for validating the deployment using a Linux-based web server (such as Apache or Nginx) in addition to IIS.
  • Offer an ARM template variant or parameter to deploy Linux VMs in the backend pool.
  • Ensure that all steps (validation, cleanup) have cross-platform instructions and examples.
GitHub Create Pull Request
Application Gateway Overview of mutual authentication on Azure Application Gateway .../application-gateway/mutual-authentication-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 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 moderate Windows bias. PowerShell examples and references are provided in detail, with CLI examples included but less emphasized. The 'Next steps' section directs users to a PowerShell-focused guide, and PowerShell is mentioned before CLI in several places. There are no explicit Linux/macOS-specific instructions or examples, and the documentation does not mention Linux tools or workflows for certificate management or validation.
Recommendations
  • Provide Linux/macOS-specific examples for certificate extraction and management (e.g., using OpenSSL commands).
  • Include step-by-step CLI instructions equivalent to PowerShell, and ensure CLI examples are as comprehensive.
  • Reference Linux-native tools and workflows for certificate handling, such as keytool, OpenSSL, or bash scripting.
  • Alternate the order of PowerShell and CLI examples, or present them side-by-side.
  • Add links to documentation or guides for configuring mutual authentication using Linux/macOS environments.
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
Medium Priority View Details →
Scanned: 2026-01-13 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 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 equivalent Linux shell commands or instructions for installing a web server on Linux. The use of Windows tools and patterns is prevalent, and Linux alternatives are not mentioned.
Recommendations
  • Include parallel instructions for deploying a Linux VM (e.g., Ubuntu) as a backend target.
  • Provide Linux shell commands (e.g., using Bash in Cloud Shell) for installing a web server such as Apache or Nginx.
  • Offer both Windows and Linux examples side-by-side for backend setup and testing.
  • Clarify that backend VMs can be Linux or Windows and link to relevant Linux setup guides.
  • Mention that Azure Cloud Shell supports Bash and show how to use it for Linux VM configuration.
GitHub Create Pull Request
Application Gateway Migrate from V1 to V2 - Azure Application Gateway ...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page is heavily biased toward Windows and PowerShell environments. All migration scripts, examples, and installation instructions are provided exclusively for Azure PowerShell (.ps1) scripts, with no mention of Bash, Azure CLI, or Linux/macOS-specific alternatives. The guidance assumes the user is running PowerShell locally or in Azure Cloud Shell, and all code samples use PowerShell cmdlets. There are no Linux or macOS shell examples, nor any references to cross-platform scripting or CLI equivalents. This creates friction for users on Linux or macOS who may prefer or require Bash/Azure CLI workflows.
Recommendations
  • Provide equivalent Azure CLI (az) commands and scripts for all migration steps, including configuration and traffic migration.
  • Include Bash shell examples for script invocation and parameter passing.
  • Explicitly document how Linux/macOS users can run the migration scripts (e.g., via Azure Cloud Shell, PowerShell Core, or alternative methods).
  • Add a section clarifying cross-platform support and limitations, and recommend best practices for non-Windows environments.
  • If PowerShell is required, provide instructions for installing and running PowerShell Core on Linux/macOS, or highlight Azure Cloud Shell as a platform-neutral option.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway v2? .../blob/main/articles/application-gateway/overview-v2.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows/Powershell bias. The only migration script referenced is a PowerShell script, and the registration/unregistration commands for the Basic SKU preview use Azure CLI but are shown with PowerShell-specific context commands (Set-AzContext, Get-AzProviderFeature, Register-AzProviderFeature), which are part of the Azure PowerShell module, not the cross-platform Azure CLI. There are no explicit Linux/macOS command-line examples or guidance, and no mention of Bash or shell equivalents. This may create friction for Linux/macOS users unfamiliar with PowerShell or those who prefer Bash/Azure CLI.
Recommendations
  • Provide equivalent Bash/Azure CLI command examples for all registration/unregistration and management tasks.
  • If the migration script is only available in PowerShell, clarify whether it can be run cross-platform (e.g., with PowerShell Core on Linux/macOS) and provide instructions for those environments.
  • Where possible, offer migration scripts or tooling in cross-platform languages (e.g., Python, Bash, or Azure CLI).
  • Clearly distinguish between Azure CLI and Azure PowerShell commands, and avoid using PowerShell-specific commands in sections labeled as Azure CLI.
  • Add explicit notes or links for Linux/macOS users on how to perform the same tasks.
GitHub Create Pull Request
Application Gateway Configure Request and Response Buffers ...lob/main/articles/application-gateway/proxy-buffers.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides Azure CLI, PowerShell, and ARM template methods for configuring buffer settings. PowerShell examples are extensive and given their own section, with multiple code blocks for both creation and update scenarios. PowerShell is a Windows-centric tool, and its prominence may disadvantage Linux/macOS users. The Azure CLI example is present and cross-platform, but PowerShell is shown second and in more detail. There are no Linux/macOS-specific shell examples (e.g., Bash), and no mention of platform differences or parity. The reference to Azure SDK for .NET is also Windows-oriented.
Recommendations
  • Add explicit Bash shell examples for Azure CLI usage on Linux/macOS.
  • Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Consider providing examples using Azure SDK for Python or Java, which are more common on Linux/macOS.
  • Reorder examples to show Azure CLI first, emphasizing its cross-platform nature.
  • Mention that PowerShell Core is available on Linux/macOS, if relevant, and provide usage notes.
GitHub Create Pull Request
Application Gateway Redirect overview for Azure Application Gateway ...main/articles/application-gateway/redirect-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page references a tutorial for configuring URL redirection using PowerShell, which is primarily a Windows tool. There are no examples or links for Linux/macOS users (e.g., Azure CLI, Bash, or ARM templates). The only next step provided is PowerShell-based, and no Linux-native tools or cross-platform instructions are mentioned.
Recommendations
  • Add equivalent tutorials and examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include Bash or shell script examples for common redirection scenarios.
  • Reference ARM/Bicep template approaches for declarative configuration.
  • Ensure that next steps include links for both Windows (PowerShell) and Linux/macOS (CLI/Bash) users.
GitHub Create Pull Request
Application Gateway FAQ on V1 retirement ...ob/main/articles/application-gateway/retirement-faq.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a notable Windows bias, primarily by referencing Azure PowerShell scripts as the main migration tool and providing no mention of Linux/macOS alternatives (such as Azure CLI or Bash scripts). All migration automation examples and caveats are centered around PowerShell, which is traditionally a Windows-first tool. There are no examples or guidance for Linux or macOS users, nor is there any mention of cross-platform tooling. This may create friction for users on non-Windows platforms attempting to follow migration steps.
Recommendations
  • Provide equivalent Azure CLI or Bash script examples for migration tasks, especially for configuration and public IP retention.
  • Explicitly state whether the PowerShell scripts can be run on Linux/macOS (e.g., via PowerShell Core), and provide installation instructions if so.
  • Add links or references to cross-platform tools and clarify any platform-specific limitations.
  • Present examples for both Windows and Linux/macOS environments, or at least mention alternatives.
  • Reorder sections to avoid always listing Windows/PowerShell solutions first.
GitHub Create Pull Request
Application Gateway Quickstart: Direct web traffic using a Resource Manager template .../articles/application-gateway/quick-create-template.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias in the resource cleanup section, where only a PowerShell example is provided for deleting resources. No Linux/macOS equivalent (such as Azure CLI or Bash) is shown. Additionally, the validation steps assume the use of IIS, which is a Windows-centric web server, without mentioning Linux alternatives. While the page references Azure CLI in navigation and introductory text, actionable examples and commands are Windows/PowerShell-focused.
Recommendations
  • Provide Azure CLI and/or Bash examples for resource cleanup (e.g., 'az group delete --name <resource group name> --yes --no-wait') alongside PowerShell.
  • Mention Linux-based web servers (such as Apache or Nginx) as alternatives to IIS for backend validation, or provide instructions for Linux VM setup.
  • Ensure that all critical actions (deployment, validation, cleanup) have both Windows and Linux/macOS command examples.
  • Consider showing CLI examples before or alongside PowerShell to avoid implicit Windows-first ordering.
GitHub Create Pull Request
Application Gateway Renew an Azure Application Gateway certificate ...ain/articles/application-gateway/renew-certificates.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides renewal instructions for Azure Application Gateway certificates using the Azure portal, Azure PowerShell, and Azure CLI. The PowerShell example is given in detail, and the CLI example is present but lacks explicit Linux/macOS context. There are no Linux-specific shell examples, nor any mention of platform differences or parity. The ordering and depth of examples favor Windows-centric tools (PowerShell) and workflows.
Recommendations
  • Add explicit Bash/Linux shell examples for the Azure CLI, including file path conventions and password handling.
  • Clarify that Azure CLI commands work cross-platform and provide notes for Linux/macOS users where relevant.
  • Consider listing CLI examples before PowerShell, or side-by-side, to avoid Windows-first impression.
  • Mention any platform-specific caveats (e.g., certificate file formats, path separators) that may affect Linux/macOS users.
GitHub Create Pull Request
Application Gateway Generate self-signed certificate with a custom root CA ...ticles/application-gateway/self-signed-certificates.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates mild Windows bias: Windows is mentioned first in prerequisites, IIS (Windows web server) is described before Apache/NGINX, and the only code sample for uploading the certificate to Application Gateway uses Azure PowerShell (Windows-centric). There is no equivalent Azure CLI (cross-platform) example, and references to file paths use Windows conventions. However, the main certificate generation steps use OpenSSL, which is cross-platform, and Linux web servers are covered.
Recommendations
  • Add Azure CLI examples for uploading certificates and configuring Application Gateway, alongside PowerShell.
  • Present Linux and Windows prerequisites equally (e.g., 'on Windows, Linux, or macOS').
  • Alternate or parallelize IIS and Apache/NGINX configuration sections, or present Linux examples first.
  • Use neutral file path examples or show both Windows and Linux paths.
  • Explicitly mention macOS support where applicable.
GitHub Create Pull Request
Application Gateway Tutorial: Protect your application gateway with Azure DDoS Network Protection ...n-gateway/tutorial-protect-application-gateway-ddos.md
Medium Priority View Details →
Scanned: 2026-01-13 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 notable Windows bias, especially in the backend VM setup and testing sections. Only Windows Server is used as the backend example, and IIS installation is performed exclusively via Azure PowerShell and Windows-specific commands. There are no Linux VM or Apache/Nginx examples, nor is there any mention of Bash or Linux-native tools. This may create friction for users who prefer or require Linux-based backends.
Recommendations
  • Provide parallel instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
  • Include examples for installing a web server on Linux (e.g., Apache or Nginx) using Bash or Azure CLI.
  • Offer both PowerShell and Bash/CLI commands for VM extension installation and configuration.
  • Explicitly mention that Application Gateway supports both Windows and Linux backend servers.
  • Present Windows and Linux examples side-by-side or alternate which is shown first.
GitHub Create Pull Request
Application Gateway Enabling end to end TLS on Azure Application Gateway ...blob/main/articles/application-gateway/ssl-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias primarily through its exclusive use of PowerShell and Windows-centric tools for configuration guidance. The 'Next steps' section directs users to a PowerShell-based guide, and references to certificate formats and APIs (such as PFXImportCertStore) are Windows-specific. There are no Linux or cross-platform CLI examples, and Windows tooling is mentioned before any Linux alternatives (which are absent). This creates friction for Linux/macOS users who may not use PowerShell or Windows certificate tooling.
Recommendations
  • Provide equivalent configuration instructions using Azure CLI and/or REST API, which are cross-platform.
  • Include Linux/macOS-compatible certificate management steps (e.g., using OpenSSL for PFX creation and validation).
  • Reference cross-platform documentation for certificate formats and import procedures, not just Windows APIs.
  • Offer example workflows for configuring Application Gateway TLS from Linux/macOS environments.
GitHub Create Pull Request
Application Gateway Azure Application Gateway listener configuration ...rticles/application-gateway/configuration-listeners.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell-only example for enabling HTTP/2 support on Application Gateway listeners, with no equivalent CLI or Bash example for Linux users. There is no mention of Azure CLI or cross-platform tools, and the only code snippet is Windows-centric. This may hinder Linux and macOS users who do not use PowerShell.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for all configuration tasks, especially for enabling HTTP/2 support.
  • Explicitly mention that Azure CLI is cross-platform and provide links to relevant CLI documentation.
  • Ensure that all code snippets are available in both PowerShell and CLI/Bash formats, and present them in parallel or with clear tabs.
  • Review other sections for implicit Windows-first patterns and update them to reference cross-platform tools where applicable.
GitHub Create Pull Request
Application Gateway Troubleshoot Application Gateway for Containers ...cation-gateway/for-containers/troubleshooting-guide.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Linux and Windows examples for filtering logs, but the Windows example is presented after the Linux example and uses Windows-specific tools (findstr). There is a slight bias in that Windows command-line tools are explicitly called out, and the documentation uses a '[Linux]' and '[Windows]' tab structure, which can sometimes lead to Windows-first presentation in other contexts. However, most of the core troubleshooting steps use cross-platform tools (kubectl, helm) and Bash syntax, which are more common in Linux environments.
Recommendations
  • Ensure that Linux and Windows examples are presented with equal prominence and clarity.
  • Consider using a neutral tab structure (e.g., 'Linux/macOS' and 'Windows') and avoid implying one platform is primary.
  • Where possible, provide examples for macOS as well, or clarify that Linux commands work on macOS.
  • If using platform-specific tools (e.g., findstr for Windows), briefly explain their purpose and provide links to documentation for users unfamiliar with them.
  • Review the order of examples to avoid unintentional prioritization of Windows commands or tools.
GitHub Create Pull Request
← Previous Page 32 of 40 Next →