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 726-750 of 981 flagged pages
Application Gateway Create a custom probe using the portal ...ion-gateway/application-gateway-create-probe-portal.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents three entry points for creating a custom probe: Azure portal, Azure Resource Manager PowerShell, and Azure Classic PowerShell. Both PowerShell options are Windows-centric, and no Linux/macOS CLI alternatives (such as Azure CLI or Bash scripting) are mentioned or linked. The portal instructions themselves are cross-platform, but the navigation prioritizes Windows/PowerShell tools by listing them before any Linux-friendly options.
Recommendations
  • Add Azure CLI instructions and links alongside PowerShell options for creating and managing probes.
  • Explicitly mention that the Azure portal is accessible from any OS/browser, reinforcing cross-platform compatibility.
  • Reorder or group entry points so that platform-neutral options (portal, Azure CLI) appear before Windows-specific tools.
  • Provide Bash or shell script examples for probe management where applicable.
GitHub Create Pull Request
Application Gateway Externally managed scheduled autoscaling for Application Gateway v2 ...ation-gateway-externally-managed-scheduled-autoscaling.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively provides PowerShell runbook examples and instructions, which are native to Windows environments. There is no mention of Bash, Python, or other cross-platform scripting options, nor are there examples for Linux/macOS users. The use of Azure PowerShell and lack of alternatives creates friction for non-Windows users.
Recommendations
  • Provide equivalent examples using Azure CLI (az) in Bash or shell scripts, which are natively supported on Linux/macOS.
  • Mention that Azure Automation supports Python runbooks and provide sample Python scripts for the same autoscaling task.
  • Clarify that PowerShell Core is cross-platform, but explicitly show how Linux/macOS users can author and run these scripts.
  • Reorder or parallelize examples so that Linux/macOS options are presented alongside Windows/PowerShell instructions.
GitHub Create Pull Request
Application Gateway Use with Internal Load Balancer - Azure Application Gateway ...les/application-gateway/application-gateway-ilb-arm.md
Medium Priority View Details →
Scanned: 2026-01-14 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 exclusively uses Azure PowerShell cmdlets for all examples and instructions, with no mention of Azure CLI, Bash, or Linux/macOS-specific workflows. Windows/PowerShell tools are referenced throughout, and there is no guidance for performing these tasks on Linux or macOS platforms. The documentation assumes familiarity with PowerShell and Windows conventions, which may create friction for users on other operating systems.
Recommendations
  • Add equivalent Azure CLI examples for each PowerShell command, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Include a section or callout at the beginning noting that instructions are PowerShell-specific and provide links to Azure CLI or REST API documentation for non-Windows users.
  • Where possible, provide Bash script examples alongside PowerShell to demonstrate parity.
  • Clarify any platform-specific requirements (e.g., installation steps for Azure CLI on Linux/macOS).
GitHub Create Pull Request
Application Gateway Common key vault errors in Application Gateway ...gateway/application-gateway-key-vault-common-errors.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides troubleshooting steps for Azure Application Gateway key vault errors, but command-line examples are exclusively given in PowerShell, which is primarily a Windows tool. There are no Azure CLI or Bash examples, and PowerShell is presented as the default method for updating certificates, creating friction for Linux/macOS users. Additionally, portal-based instructions do not mention OS-specific differences, but the only automation examples are Windows-centric.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, especially for certificate updates and Key Vault interactions.
  • Explicitly mention that PowerShell commands can be run on Linux/macOS with PowerShell Core, or provide Bash/CLI alternatives.
  • Ensure that troubleshooting steps reference cross-platform tools and avoid assuming Windows as the default environment.
  • Where screenshots or portal instructions are given, clarify any OS-specific nuances if relevant.
GitHub Create Pull Request
Application Gateway Health monitoring overview for Azure Application Gateway ...lication-gateway/application-gateway-probe-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 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 by exclusively providing PowerShell examples and cmdlets for configuring custom health probes and matching criteria. There are no CLI (az), Bash, or Linux/macOS shell examples, and PowerShell tooling is referenced as the primary method for probe configuration. Additionally, the 'devx-track-azurepowershell' custom tag and the 'Next steps' section mention PowerShell before other platforms, reinforcing the Windows-first approach.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell cmdlets, especially for creating and configuring custom health probes and matching criteria.
  • Include Bash or shell script snippets where appropriate to demonstrate Linux/macOS workflows.
  • Reference cross-platform tools (Azure CLI, REST API, ARM templates) alongside PowerShell in all instructional sections.
  • Adjust the 'Next steps' section to mention Azure CLI and portal options before or alongside PowerShell.
  • Remove or balance any custom tags that suggest PowerShell is the primary or preferred method.
GitHub Create Pull Request
Application Gateway WebSocket support in Azure Application Gateway ...s/application-gateway/application-gateway-websocket.md
Medium Priority View Details →
Scanned: 2026-01-14 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 for next steps, suggesting a Windows-centric workflow. There are no explicit Linux or cross-platform CLI examples, nor are Linux tools or workflows mentioned. The only tooling referenced is Azure PowerShell, which is traditionally Windows-first, and the next steps reinforce this bias by pointing to a PowerShell-specific guide.
Recommendations
  • Include Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • In 'Next steps', link to both PowerShell and Azure CLI quick-create guides, or a unified guide that covers both.
  • Explicitly mention that all configuration steps can be performed using Azure CLI, ARM templates, or the Azure Portal, and provide links or examples for each.
  • Avoid implying that PowerShell is the default or only method for Azure resource creation.
GitHub Create Pull Request
Application Gateway Private Application Gateway deployment ...tion-gateway/application-gateway-private-deployment.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions for feature registration and management using the Azure portal, PowerShell, and CLI. PowerShell examples are given equal prominence to CLI, but CLI examples are shown after PowerShell. There are no explicit Linux/macOS shell (e.g., Bash) examples, and output examples for CLI use PowerShell cmdlets (Get-AzProviderFeature), which is not available in Bash or native Linux environments. The documentation does not mention platform-specific differences or provide guidance for Linux/macOS users beyond Azure CLI.
Recommendations
  • Ensure CLI examples use only az commands and show az output, not PowerShell cmdlets.
  • Provide explicit Bash shell examples for Linux/macOS users, including expected output from az commands.
  • Clarify that Azure CLI is cross-platform and available on Linux/macOS, and avoid implying PowerShell is required for non-Windows users.
  • When listing management options, mention CLI before PowerShell to reflect platform neutrality.
  • Add notes or links for installing Azure CLI on Linux/macOS.
  • If PowerShell is referenced, clarify that Azure PowerShell is available cross-platform, or link to installation instructions for Linux/macOS.
GitHub Create Pull Request
Application Gateway TLS policy overview for Azure Application Gateway ...ion-gateway/application-gateway-ssl-policy-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing PowerShell and Windows-centric tools as primary mechanisms for viewing or configuring TLS policy details. For example, users are directed to PowerShell, CLI, REST API, or the Azure Portal to view cipher suite ordering, but PowerShell is listed first and is the only tool with a dedicated configuration link in the 'Next steps' section. There are no explicit Linux/macOS shell (bash, az CLI) examples or references, and the configuration walkthrough is only linked for PowerShell, leaving Linux/macOS users without direct guidance.
Recommendations
  • Add explicit Linux/macOS examples using Azure CLI (az) and bash where configuration steps are shown.
  • Ensure that references to PowerShell are balanced with CLI and REST API instructions, ideally listing CLI before or alongside PowerShell.
  • Provide direct links to configuration guides for CLI and REST API, not just PowerShell.
  • Clarify that all operations can be performed cross-platform and highlight any platform-specific differences or limitations.
GitHub Create Pull Request
Application Gateway Troubleshoot Bad Gateway errors - Azure Application Gateway ...ion-gateway/application-gateway-troubleshooting-502.md
Medium Priority View Details →
Scanned: 2026-01-14 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 notable Windows bias by exclusively providing Azure PowerShell examples and referencing Windows-centric tools and patterns (e.g., PowerShell cmdlets, IIS web server). No Azure CLI, Bash, or Linux-native troubleshooting commands are provided, and Windows/PowerShell examples are given first and exclusively. This creates friction for Linux/macOS users who may prefer or require cross-platform tools.
Recommendations
  • Add equivalent Azure CLI (az) commands for all PowerShell examples, with clear syntax and output samples.
  • Include Bash and Linux-native troubleshooting steps (e.g., using curl, dig, ip, netstat, systemctl) where relevant.
  • When referencing web servers, mention both IIS (Windows) and common Linux servers (Apache, Nginx), with configuration notes for both.
  • Present cross-platform examples side-by-side or alternate which platform is shown first.
  • Explicitly state that all steps can be performed on Linux/macOS and provide links to platform-specific guidance.
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-14 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. The virtual machine creation example exclusively uses Windows Server as the image, and the IIS installation instructions rely solely on PowerShell commands. There are no Linux VM examples, nor are there equivalent instructions for installing a web server (such as Apache or Nginx) on Linux. The use of PowerShell in Azure Cloud Shell is assumed, with no mention of Bash or Linux alternatives. This creates friction for users who prefer or require Linux-based backend servers.
Recommendations
  • Provide parallel instructions for creating Linux virtual machines (e.g., Ubuntu) as backend servers.
  • Include examples for installing a web server (such as Apache or Nginx) on Linux VMs, using Bash commands.
  • Show how to use Azure CLI or Bash in Cloud Shell for Linux-based deployments.
  • Present both Windows and Linux options for backend pool configuration, ideally side-by-side.
  • Avoid assuming PowerShell as the default shell; mention that Bash is available and provide equivalent commands.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides extensive PowerShell-based examples for all configuration steps, but does not offer equivalent CLI (az), Bash, or Linux/macOS shell examples. All code samples for automation and scripting use Azure PowerShell cmdlets, which are most commonly used on Windows. There is no mention of cross-platform tools or instructions for Linux/macOS users, nor are any Linux-native commands (such as Azure CLI) provided. This creates friction for users on non-Windows platforms who may not have access to PowerShell or prefer Bash/CLI workflows.
Recommendations
  • Add equivalent Azure CLI (az) examples for each PowerShell script section, ensuring Linux/macOS users can follow along without needing PowerShell.
  • Explicitly mention that Azure CLI can be used on all platforms and provide links to CLI documentation.
  • Where possible, include Bash script snippets for common tasks (e.g., DNS verification, certificate management) to demonstrate Linux parity.
  • Clarify prerequisites for PowerShell usage (e.g., installation on Linux/macOS) and link to cross-platform PowerShell installation guides if PowerShell is required.
  • Consider reordering examples so that cross-platform tools (Azure CLI) are shown before or alongside PowerShell.
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-14 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. All virtual machine creation examples use Windows Server, and IIS installation is performed exclusively via Azure PowerShell and Windows-specific commands. The hosts file editing instructions are tailored for Windows, with no mention of Linux/macOS equivalents. Windows command-line tools (ipconfig) are used for DNS cache management, and screenshots and file paths are Windows-centric. There are no examples or instructions for Linux VM creation, Apache/Nginx setup, or Linux/macOS hosts file editing.
Recommendations
  • Include parallel instructions for creating Linux VMs (e.g., Ubuntu) and installing a web server such as Apache or Nginx.
  • Provide Linux/macOS commands for editing the hosts file (e.g., /etc/hosts) and for flushing DNS cache (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo dscacheutil -flushcache').
  • Show examples using Bash or Azure CLI, not just PowerShell.
  • Add notes or sections highlighting cross-platform differences and considerations.
  • Present Windows and Linux/macOS instructions side-by-side or in separate tabs for clarity.
GitHub Create Pull Request
Application Gateway Configure Azure Monitor alerts for Application Gateway ...application-gateway/configure-alerts-with-templates.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references the procedure for using ARM templates via a link that prioritizes CLI, PowerShell, and ARM, but the linked page and context suggest a bias toward PowerShell and Windows workflows. There are no explicit Linux/macOS instructions or examples, and the 'Deploy to Azure' button directs users to the Azure Portal, which is platform-agnostic but does not address command-line or automation scenarios for Linux users. The absence of Linux-specific CLI examples or parity in instructions may create friction for non-Windows users.
Recommendations
  • Add explicit Azure CLI examples for Linux/macOS users alongside any PowerShell instructions.
  • Ensure referenced procedures (such as the linked 'Create a new alert rule using an ARM template') include both PowerShell and Azure CLI workflows, with clear platform notes.
  • Include a section or note clarifying that all steps can be performed on Linux/macOS using Azure CLI, and provide sample commands.
  • Avoid referencing PowerShell or Windows tools first; present CLI and PowerShell options in parallel.
GitHub Create Pull Request
Application Gateway Deploy Application Gateway Basic (Preview) ...in/articles/application-gateway/deploy-basic-portal.md
Medium Priority View Details →
Scanned: 2026-01-14 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 exhibits a notable Windows bias. All command-line examples use Azure PowerShell, with no mention of Azure CLI or Bash alternatives. The VM creation walkthrough exclusively uses Windows Server, and IIS installation is performed via PowerShell scripts. There are no Linux VM examples, nor is there guidance for installing a web server on Linux (e.g., Apache or Nginx). The documentation assumes familiarity with Windows tools and patterns, potentially creating friction for Linux/macOS users.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell commands for preview registration and resource management.
  • Include Linux VM creation steps in addition to Windows Server, with instructions for installing a web server (e.g., Apache or Nginx) using Bash.
  • Offer parity in screenshots and walkthroughs for Linux-based backend pools.
  • Explicitly mention that Application Gateway supports both Windows and Linux backends, and link to relevant Linux documentation.
  • Reorder examples or provide tabs for both Windows and Linux scenarios to avoid Windows-first presentation.
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-14 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 using the Azure portal (a GUI, typically accessed from Windows) and PowerShell, but does not include equivalent examples for Linux/macOS users (such as Azure CLI or Bash). PowerShell is a Windows-centric tool, and its exclusive use for scripting creates friction for users on non-Windows platforms. There is no mention of Azure CLI, Bash, or cross-platform automation options, and Windows-oriented tools are presented before any alternatives.
Recommendations
  • Add equivalent Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash script snippets for log configuration where appropriate.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell must be used, and provide installation guidance.
  • Present cross-platform tools (Azure CLI, REST API) before or alongside Windows-specific tools.
  • Clarify that the Azure portal is accessible from any OS, but also provide command-line alternatives for automation.
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-14 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 Server as the SQL VM image, referencing SQL Server Management Studio (a Windows-only tool) for connectivity, and omitting any Linux-based SQL Server deployment or client connection examples. No mention is made of Linux SQL Server images, Linux client tools, or cross-platform alternatives.
Recommendations
  • Include instructions for deploying SQL Server on Linux VMs (e.g., Ubuntu or Red Hat) using supported SQL Server Linux images.
  • Provide examples of connecting to the SQL Server backend using cross-platform tools such as Azure Data Studio, sqlcmd, or other Linux-compatible SQL clients.
  • Explicitly mention that the procedure is applicable to both Windows and Linux SQL Server deployments, and highlight any differences in configuration steps.
  • Add screenshots or command-line examples for Linux environments where appropriate.
GitHub Create Pull Request
Application Gateway Application Gateway high traffic volume support ...n/articles/application-gateway/high-traffic-support.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation references PowerShell for configuring WAF custom rules and TLS policy versions, but does not mention or provide equivalent instructions for Linux/macOS users (e.g., Azure CLI, Bash, or ARM templates). This creates friction for non-Windows users who may not use PowerShell. No explicit Windows-only tools are mentioned, but the repeated use of PowerShell as the configuration method implies a Windows-centric approach. No Linux/macOS-specific examples or parity guidance are provided.
Recommendations
  • Provide equivalent Azure CLI and/or Bash examples for all configuration tasks currently shown with PowerShell.
  • Explicitly mention that PowerShell Core is cross-platform, or clarify if instructions require Windows-only PowerShell.
  • Add ARM template and REST API instructions for configuration tasks where possible.
  • Ensure all referenced configuration guides (e.g., for WAF custom rules, TLS policy) include Linux/macOS-friendly methods.
GitHub Create Pull Request
Application Gateway Troubleshoot session affinity issues ...oubleshoot-application-gateway-session-affinity-issues.md
Medium Priority View Details →
Scanned: 2026-01-14 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 and tooling examples are heavily oriented toward Windows environments, such as exclusive use of PowerShell cmdlets and Fiddler (a Windows-centric tool). There is no mention of Linux/macOS alternatives for command-line or web debugging tasks, and Windows methods are presented first and exclusively.
Recommendations
  • Provide equivalent CLI examples using Azure CLI (az) for Linux/macOS users alongside PowerShell.
  • Mention and demonstrate cross-platform or Linux-native web debugging tools such as mitmproxy, Wireshark, or tcpdump.
  • Explicitly state that Fiddler is Windows-focused and suggest alternatives for other platforms.
  • Ensure screenshots and step-by-step instructions include Linux/macOS workflows where applicable.
  • Reorder examples so that platform-neutral or cross-platform solutions are presented first, or in parallel.
GitHub Create Pull Request
Application Gateway How to migrate from Azure Application Gateway Ingress Controller Helm to AGIC add-on ...es/application-gateway/ingress-controller-migration.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses Azure CLI and Portal examples for all steps, without mentioning or providing Linux/macOS-specific commands or guidance. While Azure CLI is cross-platform, there is no reference to Linux-native tools, shell differences, or considerations for Linux/macOS users. The Portal instructions are also Windows-centric by default. No PowerShell is shown, but the lack of Linux/macOS parity is notable.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS and provide any necessary shell syntax differences (e.g., variable assignment, quoting).
  • Include Linux/macOS-specific notes or examples, such as bash/zsh usage, and clarify any differences in command behavior or prerequisites.
  • Mention that the Azure Portal is accessible from any OS/browser, not just Windows.
  • If relevant, provide kubectl or Helm commands that are platform-agnostic, and clarify any OS-specific steps for uninstalling Helm deployments.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server as the backend VM example, providing only PowerShell commands for IIS installation, and omitting equivalent Linux instructions or examples. There are no references to Linux VMs, Bash, or Linux web servers, and the only scripting example uses Azure PowerShell with Windows-specific features.
Recommendations
  • Include instructions for deploying a Linux VM (e.g., Ubuntu) as a backend target.
  • Provide Bash/CLI examples for installing a web server (e.g., Apache or Nginx) on Linux VMs.
  • Show how to use Azure CLI (cross-platform) for backend configuration and extension installation.
  • Present both Windows and Linux examples side-by-side, or alternate which is shown first.
  • Clarify that backend VMs can be Linux or Windows, and link to relevant Linux setup guides.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. Several command examples use PowerShell syntax and variables (e.g., $resourceGroup, $identityName), especially in identity setup and role assignment sections. PowerShell is used for scripting Azure CLI commands, which is not standard on Linux/macOS. While Bash examples are present, PowerShell commands are shown first or exclusively in critical steps. The documentation references the Azure portal and Cloud Shell (which is cross-platform but defaults to Bash), but scripting patterns and variable usage favor Windows/PowerShell users. There are no explicit Linux/macOS-only examples, and Linux equivalents for PowerShell scripting are missing.
Recommendations
  • Provide all command examples in both Bash and PowerShell, or default to Bash for scripting Azure CLI commands.
  • Avoid using PowerShell variable syntax ($var) in CLI examples; use Bash syntax (var=value) for cross-platform compatibility.
  • Explicitly state that all Azure CLI commands can be run in Bash, and provide Bash script blocks for identity and role assignment steps.
  • Add notes or sections for Linux/macOS users, clarifying how to adapt PowerShell examples to Bash.
  • Ensure that critical steps (e.g., role assignment, resource queries) have Bash equivalents shown before or alongside PowerShell.
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-14 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 exclusively providing a PowerShell example for resource cleanup, referencing IIS (a Windows web server) for backend validation, and omitting equivalent Linux commands or validation steps (such as using Apache/Nginx or Azure CLI for cleanup). No Linux/macOS-specific instructions or parity examples are present.
Recommendations
  • Add Azure CLI and/or Bash examples for resource group deletion (e.g., 'az group delete --name <name> --yes --no-wait').
  • Include validation steps using Linux-based web servers (e.g., Apache, Nginx) or clarify how Linux users can validate deployment.
  • Provide cross-platform instructions for all command-line steps, not just PowerShell.
  • Explicitly mention that the template can be used with Linux VMs and provide guidance for such scenarios.
GitHub Create Pull Request
Application Gateway TLS termination with Azure Key Vault certificates ...b/main/articles/application-gateway/key-vault-certs.md
Medium Priority View Details →
Scanned: 2026-01-14 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 notable Windows bias: PowerShell is the only command-line example provided for configuring Application Gateway with Key Vault certificates, with no equivalent Azure CLI, Bash, or Linux/macOS instructions. References to scripting and automation are PowerShell-centric, and the 'Next steps' section links exclusively to a PowerShell guide. This creates friction for Linux/macOS users who typically use Azure CLI or Bash.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell command sequences, especially for certificate referencing and managed identity configuration.
  • Explicitly mention that Azure CLI and ARM templates can be used from Linux/macOS environments, and link to relevant documentation.
  • In the 'Next steps' section, add links to Azure CLI and ARM template guides for TLS termination with Key Vault certificates.
  • Where possible, show both PowerShell and CLI/Bash examples side-by-side, or indicate parity.
  • Clarify that PowerShell is cross-platform, but acknowledge that many Linux/macOS users prefer Azure CLI or Bash.
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-14 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 toward Windows and PowerShell environments. All migration scripts and operational examples are provided exclusively in PowerShell, with no mention of Bash, Azure CLI, or Linux/macOS-specific workflows. The instructions assume the use of PowerShell modules and tools, and do not address how Linux or macOS users should perform these tasks. There is no guidance for running the scripts in cross-platform environments, nor are alternative methods (such as Azure CLI or REST API) referenced.
Recommendations
  • Provide equivalent Azure CLI examples and scripts for all migration steps, including configuration and traffic migration.
  • Explicitly document how to run PowerShell scripts on Linux/macOS (e.g., using PowerShell Core), including installation prerequisites.
  • Reference Azure Cloud Shell as a cross-platform solution and clarify its usage for both Bash and PowerShell environments.
  • Include notes or sections for Linux/macOS users, addressing any differences in script execution, module installation, or environment setup.
  • Where possible, offer REST API or ARM template alternatives for migration tasks.
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-14 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 are provided in detail, with CLI examples present but less emphasized. References to PowerShell cmdlets are given before CLI equivalents, and the 'Next steps' section directs users to a PowerShell-focused guide. There are no Linux-specific examples or guidance, and the documentation does not mention Linux/macOS certificate management tools or patterns.
Recommendations
  • Provide Linux/macOS-specific examples for certificate extraction and management (e.g., using OpenSSL commands).
  • Ensure CLI examples are as detailed as PowerShell examples, and present them with equal prominence.
  • Include references to Linux tools and workflows for certificate handling, such as keytool, OpenSSL, or relevant shell commands.
  • Balance 'Next steps' links to include guides for both PowerShell and CLI workflows.
  • Explicitly mention cross-platform compatibility and note any OS-specific considerations.
GitHub Create Pull Request
← Previous Page 30 of 40 Next →