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

853 issues found
Showing 101-125 of 853 flagged pages
Application Gateway Configure Azure Application Gateway TCP/TLS proxy ...n/articles/application-gateway/how-to-tcp-tls-proxy.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows-based SQL Server VM images, referencing SQL Server Management Studio (a Windows-only tool) for connectivity, and omitting any mention of Linux-based SQL Server deployments or Linux client tooling. All examples and screenshots assume a Windows environment, with no guidance for Linux users.
Recommendations
  • Include instructions for deploying SQL Server on Linux VMs (e.g., Ubuntu, Red Hat) in Azure.
  • Provide examples of connecting to the SQL Server backend using cross-platform or Linux-native tools (e.g., sqlcmd, Azure Data Studio, DBeaver).
  • Add screenshots and step-by-step guidance for Linux users, including package installation and command-line connection examples.
  • Explicitly mention that Application Gateway TCP/TLS proxy works with both Windows and Linux backend servers.
  • Ensure parity in troubleshooting and cleanup instructions for Linux environments.
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-11 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 page shows evidence of Windows bias. Windows-specific technologies (NTLM, IIS) are mentioned before their Linux equivalents, and troubleshooting steps reference Windows tools and authentication patterns. Examples and guidance for Linux environments (such as Apache, Nginx, Kerberos, etc.) are missing or less detailed. There are no Linux/POSIX command-line examples, and Windows authentication (NTLM) is discussed without mentioning alternatives for Linux backends.
Recommendations
  • Add troubleshooting examples and guidance for common Linux backend servers (e.g., Apache, Nginx, Tomcat) alongside IIS.
  • Include authentication scenarios relevant to Linux (e.g., Kerberos, OAuth2) when discussing 401 errors, not just NTLM.
  • Provide parity in configuration references (e.g., show how to set timeouts in Apache and Nginx, not just IIS).
  • Offer Linux/POSIX command-line examples for diagnostics (e.g., using curl, grep, tail for logs) where appropriate.
  • Mention Linux-specific logging and monitoring tools (e.g., syslog, journald) in troubleshooting sections.
  • Ensure that references to backend configuration and health probes include both Windows and Linux server environments.
GitHub Create Pull Request
Application Gateway Troubleshoot session affinity issues ...oubleshoot-application-gateway-session-affinity-issues.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 providing PowerShell as the only CLI example for checking settings, exclusively referencing Windows-centric tools (Fiddler, Internet Explorer), and using Windows installation patterns (right-click 'Run as administrator'). There are no Linux or cross-platform alternatives mentioned for these troubleshooting steps, nor are Linux-native tools or commands provided.
Recommendations
  • Provide equivalent CLI examples using Azure CLI and/or Bash scripts for Linux users.
  • Mention and demonstrate Linux-compatible web debugging tools such as mitmproxy, Wireshark, or curl.
  • Include browser-agnostic troubleshooting steps, avoiding exclusive references to Internet Explorer.
  • Add installation instructions for web debugging tools on Linux/macOS (e.g., using package managers like apt, yum, or Homebrew).
  • Clarify that Fiddler is available on non-Windows platforms, or suggest alternatives where Fiddler is not supported.
  • Ensure screenshots and instructions are not exclusively Windows-centric, or provide Linux/macOS equivalents.
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-11 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 moderate Windows bias. Several command examples use PowerShell scripting syntax (e.g., variable assignment with $var and command chaining), which is native to Windows environments and less common on Linux/macOS. The backup instructions reference the Azure portal's Automation section, which often generates PowerShell scripts alongside Bash scripts, but PowerShell is mentioned first. In identity setup and role assignment, PowerShell-style commands are provided, and Linux alternatives (pure Bash) are not shown. There is no explicit mention of Linux-specific tools or shell environments beyond Azure Cloud Shell, which is cross-platform but defaults to Bash unless switched. The documentation does not provide Linux-first or Linux-only examples for scripting, nor does it clarify how to adapt PowerShell commands for Bash users.
Recommendations
  • Provide Bash-only equivalents for all PowerShell command examples, especially for variable assignment and command chaining.
  • When presenting command-line examples, default to Bash syntax or present Bash first, as it is the default shell in most Linux environments.
  • Clarify when PowerShell is required and offer guidance for users on Linux/macOS who may not have PowerShell installed.
  • Ensure that all downloadable scripts (from the Azure portal or elsewhere) include both Bash and PowerShell versions, and reference them equally.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to switch between them if needed.
  • Audit all scripting examples to ensure Linux users can follow along without needing to install or use PowerShell.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates Windows bias by exclusively using Windows Server as the backend VM example and providing only PowerShell instructions for backend configuration (IIS installation). There are no Linux VM examples, nor are there Bash or Linux-native instructions for backend setup or testing. Windows tools and patterns are mentioned without Linux equivalents, and Windows is presented as the default/first option for backend targets.
Recommendations
  • Include parallel instructions for creating and configuring a Linux VM (e.g., Ubuntu) as a backend target.
  • Provide Bash/Azure CLI commands for installing a web server (such as Apache or Nginx) on Linux VMs.
  • Offer both Windows and Linux backend pool configuration examples, ensuring equal visibility and parity.
  • Add notes or sections highlighting differences or considerations for Linux users.
  • Ensure that testing steps (such as verifying connectivity) are described for both Windows and Linux environments.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using IIS (a Windows web server) for backend validation, referencing Windows-centric deployment (IIS setup via VM extensions), and providing only a PowerShell example for resource cleanup. There are no Linux-based examples (e.g., Apache, Nginx) or Bash/Azure CLI commands for equivalent operations, and Windows tools/patterns are mentioned without Linux alternatives.
Recommendations
  • Include examples using Linux virtual machines with popular web servers such as Apache or Nginx for backend validation.
  • Provide Azure CLI and Bash commands for resource cleanup alongside PowerShell examples.
  • Mention and demonstrate Linux VM extensions for web server setup in the ARM template.
  • Ensure screenshots and walkthroughs are platform-neutral or show both Windows and Linux scenarios.
  • Clarify that IIS is used as an example and provide parity for Linux users.
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-11 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 bias toward Windows environments by providing PowerShell-based examples for configuring Azure Application Gateway with Key Vault certificates, without offering equivalent examples using Bash, Azure CLI, or Linux-native tooling. PowerShell is referenced as the primary method for automation and scripting, and the 'Next steps' section directs users to a PowerShell-focused guide. There are no explicit Linux or cross-platform command-line examples, and Windows-centric tools and patterns are mentioned first or exclusively.
Recommendations
  • Add equivalent Azure CLI (bash) examples alongside PowerShell scripts for all configuration steps, especially for referencing Key Vault secrets and configuring Application Gateway.
  • Explicitly mention cross-platform compatibility and provide guidance for Linux/macOS users where applicable.
  • Ensure that references to automation or scripting tools (e.g., ARM templates, Bicep, CLI) are presented before or alongside PowerShell, not after.
  • Update the 'Next steps' section to include links to CLI and ARM template guides, not just PowerShell.
  • Where screenshots or UI instructions are given, clarify any OS-specific requirements or alternatives.
GitHub Create Pull Request
Application Gateway Migrate from V1 to V2 - Azure Application Gateway ...lob/main/articles/application-gateway/migrate-v1-v2.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 Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows environments, specifically PowerShell. All migration instructions, examples, and scripts are provided exclusively in PowerShell, with no mention of Bash, Azure CLI, or Linux-native tools. The installation and usage patterns assume a Windows/PowerShell workflow, and there is no guidance for Linux or macOS users. This creates a significant barrier for users who operate in non-Windows environments.
Recommendations
  • Provide equivalent Azure CLI (az) examples for all migration steps, including script execution, resource management, and certificate handling.
  • Include Bash script examples and instructions for running migration tasks on Linux and macOS.
  • Explicitly mention cross-platform compatibility of the provided scripts, or note any limitations for non-Windows platforms.
  • Add guidance for using Azure Cloud Shell (which supports Bash and PowerShell) for users who do not have PowerShell installed locally.
  • List prerequisites and installation steps for Linux and macOS environments, including how to install and use Azure CLI and PowerShell Core.
  • Where PowerShell objects (e.g., PSApplicationGatewaySslCertificate) are referenced, provide alternatives or mappings for Azure CLI or REST API usage.
  • Ensure that all tooling recommendations (such as PowerShell Gallery) are accompanied by Linux/macOS alternatives or instructions.
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-11 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 predominantly referencing Azure PowerShell scripts and cmdlets for migration and preview registration, with no mention of Linux-specific tools or examples. The 'Next steps' section links to a PowerShell-based tutorial, and all command-line examples use PowerShell syntax, despite Azure CLI being cross-platform. There are no Bash, Linux shell, or platform-neutral examples, nor is there guidance for Linux users. Windows tools and patterns are mentioned exclusively and appear before any cross-platform alternatives.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell commands for all operations, including migration and preview registration.
  • Include explicit instructions or links for Linux and macOS users, clarifying cross-platform compatibility.
  • Balance tutorial links to include both PowerShell and Azure CLI/Bash walkthroughs.
  • Avoid using Windows-centric terminology (e.g., 'PowerShell script') as the only option; mention platform-neutral alternatives.
  • Where possible, provide screenshots or references that are not specific to Windows environments.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by providing detailed PowerShell examples and cmdlet references before Azure CLI examples. PowerShell, a Windows-centric tool, is given prominence, and the CLI section appears after the PowerShell section. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tooling or workflows. The documentation assumes familiarity with PowerShell and Windows patterns, which may disadvantage Linux users.
Recommendations
  • Provide bash shell examples alongside Azure CLI commands to demonstrate usage in native Linux environments.
  • Reorder the example tabs so that Azure CLI (cross-platform) appears before PowerShell, or at least give both equal prominence.
  • Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any OS-specific caveats if relevant.
  • Include troubleshooting or workflow notes for Linux users, such as file path conventions, environment setup, or differences in command output.
  • Avoid exclusive references to Windows tools (e.g., PowerShell) and ensure that documentation is inclusive of cross-platform scenarios.
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-11 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 Azure CLI equivalents, and by omitting Linux-specific certificate management or extraction instructions. The 'Next steps' section directs users to a PowerShell-focused guide, reinforcing a Windows-centric workflow. There are no examples or guidance for Linux tools (e.g., OpenSSL) for certificate extraction, nor are there references to Linux-native scripting or automation approaches.
Recommendations
  • Add Linux-focused examples for certificate extraction and management, such as using OpenSSL commands to extract and format certificate chains.
  • Provide step-by-step instructions for configuring mutual authentication using Linux shell scripts or Bash, alongside PowerShell.
  • Ensure that Azure CLI examples are as detailed and prominent as PowerShell examples, and consider presenting CLI examples before PowerShell to avoid implicit Windows-first bias.
  • Include references to Linux tools and workflows in the 'Next steps' section, such as a link to a guide for configuring Application Gateway mutual authentication using Linux and Azure CLI.
  • Clarify that both Windows and Linux environments are supported, and highlight any platform-specific considerations.
GitHub Create Pull Request
Application Gateway Configure Request and Response Buffers ...lob/main/articles/application-gateway/proxy-buffers.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides configuration examples using Azure CLI, PowerShell, and ARM templates. PowerShell, a Windows-centric tool, is given a dedicated section with both creation and update examples, while Linux-native tools (such as Bash scripting or cloud-init) are not mentioned. The reference to Azure SDK for .NET further reinforces a Windows/Windows developer bias. There are no Linux-specific examples or explicit parity for Linux users beyond the Azure CLI, which is cross-platform but presented generically.
Recommendations
  • Add explicit Bash shell examples for Azure CLI usage, showing Linux command-line patterns (e.g., environment variables, piping, jq for JSON parsing).
  • Include instructions or examples for using cloud-init or Ansible for buffer configuration, which are popular on Linux.
  • Mention that Azure CLI is cross-platform and provide OS-specific installation or usage notes.
  • Reference Azure SDKs for other languages (e.g., Python, Java) that are popular in Linux environments.
  • Clarify any platform-specific limitations or differences in the 'Limitations' section, especially regarding PowerShell support on Linux.
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-11 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 by referencing Windows-specific certificate formats (PFX), linking to Windows API documentation for certificate handling, and providing PowerShell as the primary or sole example for configuration. There is no mention of Linux tools or command-line utilities for certificate management, nor are there examples using Azure CLI, Bash, or OpenSSL. The 'Next steps' section directs users to a PowerShell-based guide, further reinforcing the Windows-centric approach.
Recommendations
  • Include Linux-focused examples for configuring Application Gateway end-to-end TLS, such as using Azure CLI, Bash scripts, or OpenSSL for certificate management.
  • Reference cross-platform certificate formats and tools (e.g., PEM, OpenSSL) alongside PFX and Windows APIs.
  • Provide parity in documentation by offering both PowerShell and Azure CLI/Bash walkthroughs for all configuration steps.
  • Add troubleshooting and certificate validation instructions using Linux tools (e.g., openssl s_client) in addition to Windows methods.
  • Update 'Next steps' to include links to guides for Linux users and cross-platform configuration options.
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-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 demonstrates a Windows bias by exclusively using Windows Server virtual machines as backend examples, providing only PowerShell commands for IIS installation, and referencing Windows-specific tooling (IIS, Add-WindowsFeature). There are no Linux VM examples, nor instructions for deploying or testing with Linux-based web servers (e.g., Apache, Nginx). The step-by-step VM creation process defaults to Windows Server, and the testing section relies on IIS, further reinforcing the bias.
Recommendations
  • Include parallel instructions for deploying Linux VMs (e.g., Ubuntu) as backend servers.
  • Provide example commands for installing and configuring a Linux web server (such as Apache or Nginx), using Bash/SSH and Azure CLI.
  • Offer both PowerShell and Bash/CLI examples for backend setup and extension installation.
  • Mention Linux as a supported backend option explicitly in the VM creation section.
  • Add screenshots and walkthroughs for Linux VM configuration and testing, similar to those provided for Windows/IIS.
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-11 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 strong Windows bias. All command-line examples use PowerShell, including certificate creation and IIS installation. The virtual machine scale set is configured with Windows Server 2016 Datacenter as the default OS, and only Windows-based tools and workflows (such as New-SelfSignedCertificate, Export-PfxCertificate, and IIS) are mentioned. There are no Linux equivalents or examples provided for certificate creation, backend server setup, or web server installation.
Recommendations
  • Provide equivalent Linux examples for all command-line operations, such as using OpenSSL for certificate creation and exporting.
  • Include instructions for deploying a Linux-based VM scale set (e.g., Ubuntu) and installing a web server like Apache or Nginx.
  • Offer Bash/Azure CLI commands alongside PowerShell examples to ensure cross-platform accessibility.
  • Mention Linux tools and patterns (e.g., using /home/azureuser/appgwcert.pfx instead of c:\appgwcert.pfx) and provide parity in file paths and OS-specific steps.
  • Clarify that both Windows and Linux backend pools are supported, and link to relevant documentation for Linux scenarios.
GitHub Create Pull Request
Application Gateway FAQ on V1 retirement ...ob/main/articles/application-gateway/retirement-faq.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 Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell scripts for migration tasks, without mentioning or providing examples for Linux/Unix environments or alternative tools such as Azure CLI, Bash, or ARM templates. The migration process, troubleshooting, and automation are all described in terms of PowerShell usage, which is natively a Windows-centric tool. There are no Linux/Unix command examples or explicit guidance for non-Windows users.
Recommendations
  • Provide equivalent Azure CLI (az) commands and scripts for all PowerShell-based migration steps, ensuring Linux and macOS users have clear guidance.
  • Explicitly mention cross-platform options (such as Azure CLI, Bash, or REST API) alongside PowerShell wherever automation or scripting is discussed.
  • Add examples and links for running migration tasks from Linux/macOS environments, including any prerequisites or differences in workflow.
  • Clarify whether the provided PowerShell scripts can be run in cross-platform environments (e.g., PowerShell Core on Linux/macOS) and provide instructions if so.
  • Ensure that documentation does not assume a Windows environment by default; use neutral language and tool ordering (e.g., 'using Azure CLI or PowerShell') rather than always listing Windows tools first.
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-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 demonstrates a clear Windows bias by exclusively using Windows Server virtual machines as backend targets and providing only PowerShell-based instructions for installing IIS. There are no examples or instructions for deploying Linux VMs, installing a web server on Linux, or using Bash/CLI commands. Windows tools and patterns (IIS, PowerShell) are mentioned exclusively and before any Linux equivalents, which are entirely absent.
Recommendations
  • Include parallel instructions for deploying Linux-based backend VMs (e.g., Ubuntu or CentOS) alongside Windows examples.
  • Provide steps to install a web server (such as Apache or Nginx) on Linux VMs using Bash or Azure CLI commands.
  • Offer both PowerShell and Bash/CLI command examples for resource configuration and extension installation.
  • Explicitly state that Application Gateway supports both Windows and Linux backend servers, and link to relevant documentation for Linux setup.
  • Balance screenshots and walkthroughs to show both Windows and Linux scenarios where appropriate.
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-11 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 and Windows tools (IIS, PowerShell) are mentioned before or more prominently than Linux equivalents. The Azure PowerShell example is provided, but no Azure CLI or ARM template example is shown. IIS instructions are given before Apache/NGINX, and Windows file paths are used in PowerShell sample code. There is no explicit Linux-focused section for uploading certificates to Application Gateway, nor are Linux-specific automation examples provided.
Recommendations
  • Add Azure CLI and/or ARM template examples for uploading certificates to Application Gateway, alongside the PowerShell sample.
  • Provide Linux-specific instructions or examples for certificate upload and management, including file paths and shell commands.
  • Alternate the order of IIS and Apache/NGINX sections, or group them together to avoid implicit prioritization.
  • Include screenshots or instructions for Linux certificate stores (e.g., update-ca-certificates on Ubuntu) when adding the root certificate.
  • Use neutral file paths in code samples (e.g., /home/user/contoso.cer) or provide both Windows and Linux paths.
  • Explicitly mention cross-platform compatibility in each step, especially for certificate handling and web server configuration.
GitHub Create Pull Request
Application Gateway Tutorial: Improve web application access - Azure Application Gateway .../articles/application-gateway/tutorial-autoscale-ps.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 Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell. All examples use Azure PowerShell cmdlets and Windows-specific tools (e.g., New-SelfSignedCertificate, Export-PfxCertificate), with no mention of Linux equivalents or cross-platform alternatives. The prerequisites and instructions assume a Windows environment and do not provide Bash/CLI or Linux-native workflows. There is no parity for Linux users, and Windows tools are presented exclusively and first.
Recommendations
  • Provide equivalent Azure CLI (az) examples alongside PowerShell for each step, as Azure CLI is cross-platform.
  • Include instructions for creating self-signed certificates on Linux/macOS (e.g., using OpenSSL) and exporting to PFX format.
  • Add notes or sections for running tutorials on Linux/macOS, including installation and usage of Azure CLI.
  • Avoid assuming a Windows environment for file paths (e.g., use generic or platform-agnostic paths).
  • Mention cross-platform alternatives in prerequisites, such as Azure CLI and Bash.
  • Ensure that all code samples and instructions are available for both Windows and Linux users, ideally side-by-side.
GitHub Create Pull Request
Application Gateway Scaling and Zone-redundant Application Gateway v2 ...eway/application-gateway-autoscaling-zone-redundant.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates Windows bias by exclusively referencing Azure PowerShell in the 'Next steps' section for creating an autoscaling, zone redundant application gateway. No Linux/CLI examples or references are provided, and PowerShell is mentioned as the primary tool for deployment tasks, which may disadvantage Linux users or those preferring cross-platform tools.
Recommendations
  • Include Azure CLI examples and links alongside PowerShell instructions for deployment and configuration tasks.
  • Explicitly mention cross-platform tools and provide parity in walkthroughs for both Windows and Linux environments.
  • Add guidance or tutorials for Linux users, such as using Bash scripts or Azure CLI on Linux/macOS.
  • Review all referenced tutorials and ensure that Linux-compatible instructions are available and easily discoverable.
GitHub Create Pull Request
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-10 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 is heavily biased towards Windows and PowerShell usage. All examples and instructions use Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native tooling. The prerequisite steps and links reference Windows PowerShell and do not provide Linux alternatives. There are no Bash or Azure CLI examples, and the workflow assumes a Windows-centric environment.
Recommendations
  • Add equivalent Azure CLI (az) examples for each PowerShell command, suitable for Bash and cross-platform usage.
  • Include a 'Choose your environment' section at the top, guiding users to select instructions for PowerShell (Windows) or Azure CLI (Linux/macOS/Windows).
  • Reference installation instructions for Azure CLI alongside PowerShell, with links for Linux/macOS users.
  • Ensure terminology and links do not assume Windows as the default platform (e.g., avoid 'Using Windows PowerShell with Resource Manager' as the only option).
  • Provide notes or callouts for platform-specific differences, if any, in resource creation and management.
GitHub Create Pull Request
Application Gateway Azure Application Gateway infrastructure configuration ...es/application-gateway/configuration-infrastructure.md
High Priority View Details →
Scanned: 2026-01-10 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 for operational tasks (such as restarting the Application Gateway) without providing equivalent Azure CLI or Linux shell examples. The only explicit tooling mentioned for management is PowerShell, and no Linux-specific or cross-platform command-line instructions are given. This can disadvantage users who work primarily on Linux or macOS systems, or who prefer Azure CLI over PowerShell.
Recommendations
  • Include Azure CLI examples alongside PowerShell instructions for all operational tasks, such as restarting the Application Gateway.
  • When referencing commands or scripts, provide both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) equivalents.
  • Explicitly mention that all management operations can be performed via Azure CLI, and link to relevant CLI documentation.
  • Review all procedural sections to ensure parity between Windows and Linux tooling, avoiding implicit prioritization of Windows tools.
  • Add notes or tips for cross-platform usage, clarifying that Azure CLI is available on all major operating systems.
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-10 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 backend VM OS, providing only PowerShell-based instructions for IIS installation, and omitting Linux alternatives (such as Ubuntu, Apache, and Bash/Azure CLI examples). Windows tools and patterns are mentioned first and exclusively, with no parity for Linux users.
Recommendations
  • Include Linux-based backend VM examples (e.g., Ubuntu with Apache or Nginx) alongside Windows Server.
  • Provide Azure CLI and Bash instructions for backend setup and IIS/Apache installation, not just PowerShell.
  • Show how to install a web server on Linux VMs (e.g., using apt-get for Apache/Nginx) in addition to Windows IIS.
  • Mention Linux images as options when creating virtual machines.
  • Ensure screenshots and code snippets reflect both Windows and Linux scenarios.
  • Add notes or sections for Linux users to clarify differences in setup and management.
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-10 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 primarily in the 'Deployment strategies' section, where Azure portal, CLI, PowerShell, and Terraform are listed as deployment tools, with PowerShell (a Windows-centric tool) mentioned explicitly and before any Linux-native alternatives. There are no Linux-specific examples or references to Bash, shell scripts, or Linux tooling. The documentation does not provide parity in examples or instructions for Linux users, nor does it clarify cross-platform compatibility for the listed tools.
Recommendations
  • Explicitly mention Bash, shell scripts, or Linux CLI usage alongside PowerShell when listing deployment tools.
  • Provide example commands for both PowerShell and Bash/Azure CLI to demonstrate cross-platform deployment.
  • Clarify that Azure CLI and Terraform are cross-platform and provide links or instructions for Linux installation and usage.
  • Avoid listing PowerShell before Linux-native tools, or present them together to avoid perceived prioritization.
  • Add a section or note on platform compatibility for all deployment tools, ensuring Linux users are equally supported.
GitHub Create Pull Request
Application Gateway Troubleshoot session affinity issues ...oubleshoot-application-gateway-session-affinity-issues.md
High Priority View Details →
Scanned: 2026-01-10 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 provided for checking settings, and Fiddler (a Windows-only tool) is exclusively used for web debugging. Installation instructions reference Windows-specific actions (e.g., 'Run as administrator'), and there are no Linux or cross-platform alternatives or examples given for these troubleshooting steps.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for checking Application Gateway settings, alongside or before PowerShell commands.
  • Mention and demonstrate cross-platform web debugging tools such as Wireshark, mitmproxy, or curl for capturing and analyzing HTTP/HTTPS traffic.
  • Include installation and usage instructions for these tools on Linux and macOS, not just Windows.
  • Avoid Windows-specific terminology (e.g., 'Run as administrator') unless also providing Linux/macOS equivalents (e.g., 'sudo').
  • Ensure screenshots and walkthroughs include examples from non-Windows environments where possible.
GitHub Create Pull Request
← Previous Page 5 of 35 Next →