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 76-100 of 853 flagged pages
Application Gateway Quickstart: Direct web traffic using a Resource Manager template .../articles/application-gateway/quick-create-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 page demonstrates a bias toward Windows by exclusively using IIS (a Windows web server) for backend validation, providing only PowerShell commands for resource cleanup, and omitting Linux-based examples (such as Apache or Nginx) and Bash/Azure CLI equivalents for key operations. No Linux-specific instructions or parity are present in deployment, validation, or cleanup steps.
Recommendations
  • Provide Linux-based backend VM examples (e.g., install Apache or Nginx) alongside IIS, and show how to validate the Application Gateway using those.
  • Include Azure CLI and Bash commands for resource cleanup (e.g., az group delete) in addition to PowerShell.
  • Mention both Windows and Linux options when describing VM configuration and validation steps.
  • Ensure screenshots and instructions are platform-neutral or offer alternatives for Linux users.
  • Add explicit guidance for users deploying on Linux, such as SSH access and web server setup.
GitHub Create Pull Request
Application Gateway Renew an Azure Application Gateway certificate ...ain/articles/application-gateway/renew-certificates.md
High Priority View Details →
Scanned: 2026-01-11 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 appears before the Azure CLI example. There are no explicit Linux-specific instructions, nor are there examples using bash or Linux-native tools. The CLI example is generic, but the overall flow and ordering suggest a Windows-first bias, with PowerShell emphasized and no mention of Linux shell environments or certificate management tools.
Recommendations
  • Add explicit Linux/bash examples for certificate renewal, including command-line steps for uploading certificates using Azure CLI in a Linux environment.
  • Reorder examples so that Azure CLI (cross-platform) instructions appear before PowerShell, or present both side-by-side.
  • Mention Linux-native certificate management tools (e.g., OpenSSL) for preparing certificates before upload.
  • Clarify that Azure CLI commands work identically on Windows, Linux, and macOS, and provide any environment-specific notes if needed.
  • Include screenshots or instructions for Linux users where relevant, especially for file paths and certificate formats.
GitHub Create Pull Request
Application Gateway Redirect overview for Azure Application Gateway ...main/articles/application-gateway/redirect-overview.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 Powershell Heavy
Summary
The documentation page demonstrates Windows bias by referencing only the Azure portal and PowerShell for configuration guidance, with no mention of Linux tools or CLI equivalents. The 'Next steps' section specifically links to a PowerShell-based tutorial, and there are no examples or instructions for Linux users (e.g., Azure CLI, Bash, or ARM templates).
Recommendations
  • Add equivalent examples and tutorials using Azure CLI and Bash scripts for configuring redirection, ensuring Linux users have clear guidance.
  • Include references to ARM template configuration for redirection to support cross-platform automation.
  • Ensure that 'Next steps' links include both PowerShell and CLI-based guides, and make it clear that all platforms are supported.
  • Explicitly mention that redirection can be configured from any OS, and provide parity in documentation for both Windows and Linux environments.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits Windows bias by exclusively referencing Azure PowerShell in the 'Next steps' section for creating an autoscaling, zone redundant application gateway. No equivalent Linux/CLI examples or links are provided, and PowerShell is mentioned before any cross-platform alternatives, implying a preference for Windows tooling.
Recommendations
  • Add equivalent Azure CLI examples and tutorials for Linux/macOS users alongside PowerShell instructions.
  • Reference cross-platform tools (such as Azure CLI) before or alongside PowerShell in 'Next steps' and throughout the documentation.
  • Explicitly mention that autoscaling and configuration can be performed using both PowerShell and Azure CLI, and provide links to both sets of instructions.
  • Ensure that all code samples and walkthroughs are available for both Windows and Linux environments to improve parity.
GitHub Create Pull Request
Application Gateway Diagnostic logs ...application-gateway/application-gateway-diagnostics.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 providing only PowerShell examples for enabling diagnostic logging, referencing Windows-centric tools (Excel, Power BI, Visual Studio, C#), and omitting equivalent Linux or cross-platform CLI instructions. There are no Bash, Azure CLI, or Linux-native tool examples, and the workflow assumes familiarity with Windows environments and tooling.
Recommendations
  • Add equivalent Azure CLI (az) examples for enabling diagnostic logging, which are cross-platform and widely used on Linux.
  • Include instructions for downloading and analyzing logs using Linux-native tools (e.g., jq for JSON, csvkit for CSV conversion, grep/awk for filtering).
  • Reference open-source or cross-platform log converter tools, and provide examples in languages other than C# (e.g., Python).
  • Mention viewing logs in Linux-friendly visualization tools (e.g., Grafana) alongside Power BI and Excel.
  • Reorder examples so that cross-platform or Linux options are presented before or alongside Windows/PowerShell options.
GitHub Create Pull Request
Application Gateway Externally managed scheduled autoscaling for Application Gateway v2 ...ation-gateway-externally-managed-scheduled-autoscaling.md
High Priority View Details →
Scanned: 2026-01-11 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 exclusively provides PowerShell examples for implementing scheduled autoscaling with Azure Automation, without mentioning or demonstrating Bash, Azure CLI, or other Linux-friendly alternatives. The instructions and code samples are tailored to PowerShell, which is traditionally associated with Windows environments, and there is no guidance for users who may prefer or require Linux-native tools or scripting languages.
Recommendations
  • Add equivalent Azure CLI and Bash script examples for all automation steps, including runbook creation and autoscale configuration.
  • Explicitly mention that Azure Automation supports both PowerShell and Python runbooks, and provide links or samples for non-PowerShell options.
  • Reorder sections or add notes to clarify that both Windows and Linux users can implement scheduled autoscaling, and provide parity in tooling recommendations.
  • Reference cross-platform documentation and best practices for Azure Automation, ensuring Linux users are equally supported.
GitHub Create Pull Request
Application Gateway Common key vault errors in Application Gateway ...gateway/application-gateway-key-vault-common-errors.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 only PowerShell examples for certificate management and updates, without any equivalent Azure CLI or Bash examples. The troubleshooting steps and resolutions consistently reference the Azure portal and PowerShell, which are more commonly used on Windows, and do not mention Linux-specific workflows or tools. There is no guidance for Linux users or parity in command-line instructions.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all certificate management and update operations.
  • Include Bash script snippets where appropriate to demonstrate cross-platform compatibility.
  • Explicitly mention that all operations can be performed on Linux and macOS, and provide links to relevant CLI documentation.
  • Ensure troubleshooting steps reference both portal and CLI workflows, clarifying platform-agnostic approaches.
  • Review all command-line instructions to ensure they are not Windows-centric and provide alternatives for Linux users.
GitHub Create Pull Request
Application Gateway Health monitoring overview for Azure Application Gateway ...lication-gateway/application-gateway-probe-overview.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 providing PowerShell examples (e.g., New-AzApplicationGatewayProbeHealthResponseMatch) for configuring health probe matching criteria, referencing Azure PowerShell cmdlets as the primary automation method, and omitting equivalent CLI or Linux-native examples. The 'devx-track-azurepowershell' custom tag and the 'Next steps' section prioritize PowerShell-based configuration, with no mention of Azure CLI, REST API, or ARM template alternatives that are platform-agnostic. There are no references to Linux tools, and Windows/PowerShell patterns are presented first and exclusively.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets shown, especially for probe configuration and matching criteria.
  • Include references and examples for REST API and ARM template methods to configure health probes, which are platform-neutral.
  • Ensure 'Next steps' and instructional sections mention both PowerShell and CLI/REST/ARM options, giving equal prominence to Linux-friendly tooling.
  • Remove or balance any custom tags (e.g., 'devx-track-azurepowershell') with tags for CLI or other cross-platform tools.
  • Explicitly state that all configuration steps can be performed on Linux, macOS, and Windows, and provide links to cross-platform documentation.
GitHub Create Pull Request
Application Gateway TLS policy overview for Azure Application Gateway ...ion-gateway/application-gateway-ssl-policy-overview.md
High Priority View Details →
Scanned: 2026-01-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 referencing PowerShell and CLI as the main tools for viewing and configuring TLS policies, with PowerShell consistently mentioned first. There are no explicit Linux shell (bash) examples or references to Linux-native tools or workflows. The 'Next steps' section links only to a PowerShell-based configuration guide, omitting Linux CLI or Bash alternatives.
Recommendations
  • Provide explicit bash/Azure CLI examples for configuring TLS policies, alongside PowerShell examples.
  • Reference Linux-native tools and workflows (e.g., az CLI commands in bash) equally and not subordinate to PowerShell.
  • Ensure that links in the 'Next steps' section include guides for both Windows (PowerShell) and Linux (bash/CLI) users.
  • Where the documentation refers to 'PowerShell, CLI, REST API or the Listeners blade', clarify that CLI examples are cross-platform and provide bash syntax when appropriate.
  • Add a section or callout for Linux administrators, highlighting any platform-specific considerations or steps.
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-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 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 workflows. Windows/PowerShell tools are referenced exclusively and repeatedly, including links to Windows PowerShell documentation. There are no Linux or cross-platform command examples, nor any guidance for users on non-Windows systems.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all steps, as Azure CLI is cross-platform and commonly used on Linux and macOS.
  • Include a section or callout for Linux/macOS users, noting how to install and use Azure CLI and/or PowerShell Core on those platforms.
  • Reference Bash or shell scripting alternatives where appropriate, especially for automation scenarios.
  • Update links and instructions to clarify cross-platform options (e.g., link to Azure CLI install docs alongside PowerShell).
  • Consider reordering or parallelizing examples so that Linux-friendly tools are presented alongside or before Windows/PowerShell instructions.
GitHub Create Pull Request
Application Gateway Troubleshoot Bad Gateway errors - Azure Application Gateway ...ion-gateway/application-gateway-troubleshooting-502.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 exhibits a strong Windows bias, primarily through the exclusive use of Azure PowerShell cmdlets for all troubleshooting steps and configuration examples. There are no Azure CLI, Bash, or Linux-native command examples provided, nor are Linux troubleshooting patterns or tools mentioned. Windows-centric tools and terminology (e.g., IIS, PowerShell, Windows endpoints) are referenced without Linux equivalents, and Windows methods are presented first and exclusively.
Recommendations
  • Add equivalent Azure CLI examples for each PowerShell command, demonstrating cross-platform usage.
  • Include Bash shell commands and Linux troubleshooting steps (e.g., using curl, netcat, dig, systemctl) where relevant.
  • Reference Linux web servers (e.g., Apache, Nginx) alongside IIS in backend configuration and SSL certificate sections.
  • Ensure that troubleshooting steps and examples are presented for both Windows and Linux environments, or clarify when steps are OS-agnostic.
  • Where JSON output is shown, demonstrate how to retrieve and parse it using both PowerShell and Bash/CLI tools.
  • Explicitly mention that Azure PowerShell is available on Linux and macOS, but provide CLI alternatives for users who prefer native Linux tooling.
GitHub Create Pull Request
Application Gateway Certificates required to allow backend servers ...ion-gateway/certificates-for-backend-authentication.md
High Priority View Details →
Scanned: 2026-01-11 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 page exclusively provides certificate export instructions using Windows Certificate Manager and PowerShell, with step-by-step screenshots of the Windows GUI. There are no examples or guidance for performing equivalent tasks on Linux or macOS systems, nor are cross-platform CLI tools (such as OpenSSL) mentioned. The 'Next steps' section also references PowerShell specifically for further configuration.
Recommendations
  • Add equivalent certificate export instructions for Linux and macOS using OpenSSL or other native tools.
  • Provide CLI-based examples (e.g., OpenSSL commands) for exporting public keys and root certificates in Base-64 encoded X.509 (.CER) format.
  • Include screenshots or terminal output for Linux/macOS workflows, not just Windows GUI.
  • Mention cross-platform tools and clarify that the process can be performed on non-Windows systems.
  • Ensure that PowerShell and Windows-specific instructions are not presented as the only or primary method.
GitHub Create Pull Request
Application Gateway WebSocket support in Azure Application Gateway ...s/application-gateway/application-gateway-websocket.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily by referencing Azure PowerShell and linking to a PowerShell-based 'quick create' guide as the next step, without mentioning or providing equivalent Linux-friendly options such as Azure CLI or ARM template deployment via Bash. There are no examples or instructions for Linux users, and Windows tools/patterns are mentioned before any alternatives.
Recommendations
  • Include Azure CLI examples for creating and configuring Application Gateway with WebSocket support, alongside or before PowerShell references.
  • Provide links to Linux/Bash-based quick start guides, or ARM template deployment instructions usable on any platform.
  • Explicitly mention that all configuration steps can be performed on Linux, macOS, and Windows, and clarify tool parity.
  • Add sample commands or walkthroughs using cross-platform tools (e.g., Azure CLI, REST API) in addition to PowerShell.
  • Ensure that references to PowerShell are balanced with equivalent Linux-friendly options throughout the documentation.
GitHub Create Pull Request
Application Gateway Azure Application Gateway infrastructure configuration ...es/application-gateway/configuration-infrastructure.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 page demonstrates mild Windows bias by referencing Azure PowerShell cmdlets for gateway management (restart operations) without providing Azure CLI or Linux shell equivalents. The only explicit tooling example is PowerShell, and no Linux-specific commands or examples are given. The documentation does not mention Windows tools exclusively, but when command-line instructions are referenced, Windows/PowerShell is prioritized or presented as the sole option.
Recommendations
  • Provide Azure CLI examples alongside PowerShell for all management operations, especially restart/start/stop actions.
  • Explicitly mention that both Azure CLI and PowerShell can be used for operations, and link to relevant cross-platform documentation.
  • Include Linux shell command examples where appropriate, especially for tasks that can be performed on both Windows and Linux.
  • Review all command references and ensure parity between Windows and Linux tooling, avoiding implicit prioritization of Windows/PowerShell.
GitHub Create Pull Request
Application Gateway Manage traffic to App Service ...main/articles/application-gateway/configure-web-app.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 page demonstrates a strong Windows bias by exclusively providing automation and CLI examples using Azure PowerShell, which is primarily a Windows-centric tool. There are no examples using cross-platform or Linux-native tools such as Azure CLI (az), Bash, or scripting languages commonly used on Linux. All command-line instructions, including setup, configuration, and testing, are shown only in PowerShell. There is no mention of Linux shell equivalents, nor are there instructions for users who may be working from Linux or macOS environments.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell scripts, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash shell script examples for common configuration and testing steps, especially for tasks like DNS verification and HTTP requests (e.g., using curl).
  • Explicitly mention that the steps can be performed from Linux, macOS, or Windows, and provide guidance for users on non-Windows platforms.
  • Review and update any references to Windows-specific tools or patterns to ensure Linux parity, such as using platform-neutral terminology and instructions.
  • Consider adding a section or tab for 'Linux/macOS' users, outlining any platform-specific considerations or differences.
GitHub Create Pull Request
Application Gateway Tutorial: Create and configure an application gateway to host multiple web sites using the Azure portal ...es/application-gateway/create-multiple-sites-portal.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All virtual machine examples use Windows Server, and IIS installation is performed exclusively via Azure PowerShell and Windows-specific commands. The hosts file editing instructions are written for Windows, with no mention of Linux equivalents. There are no examples or guidance for deploying Linux VMs, installing web servers on Linux, or editing Linux hosts files.
Recommendations
  • Include parallel instructions for creating Linux virtual machines (e.g., Ubuntu) and installing a web server (such as Apache or Nginx) using Bash or Azure CLI.
  • Provide Linux-specific guidance for editing the /etc/hosts file and flushing DNS cache (e.g., using 'sudo systemctl restart systemd-resolved' or 'sudo service network-manager restart').
  • Offer Azure CLI or Bash script alternatives to PowerShell commands for VM extension installation.
  • Clarify that Application Gateway supports both Windows and Linux backend servers, and show examples for both.
  • Present hosts file editing instructions for both Windows and Linux, either side-by-side or in separate sections.
GitHub Create Pull Request
Application Gateway Create Azure Application Gateway custom error pages ...blob/main/articles/application-gateway/custom-error.md
High Priority View Details →
Scanned: 2026-01-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 provides configuration instructions for Azure Application Gateway custom error pages with a heavy emphasis on Azure PowerShell, which is primarily a Windows-centric tool. There are no examples or references to Linux-native tools (such as Azure CLI, Bash, or ARM templates), and the only scripted configuration guidance is in PowerShell. This creates a bias toward Windows users and may hinder Linux users from easily following the instructions.
Recommendations
  • Add equivalent configuration examples using Azure CLI (az network application-gateway ...), which is cross-platform and widely used on Linux and macOS.
  • Include Bash script snippets for common configuration tasks, or reference ARM/Bicep templates for infrastructure-as-code approaches.
  • Explicitly mention that PowerShell is available cross-platform, but provide links or instructions for installing and using it on Linux/macOS if PowerShell must be used.
  • Reorder or supplement the configuration section so that CLI and template-based methods are presented alongside or before PowerShell, to ensure parity and inclusivity for Linux users.
GitHub Create Pull Request
Application Gateway Diagnostic logs for Application Gateway for Containers ...cles/application-gateway/for-containers/diagnostics.md
High Priority View Details →
Scanned: 2026-01-11 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 page demonstrates Windows bias by providing a detailed PowerShell example for enabling diagnostic logging, without offering equivalent CLI or Bash examples for Linux/macOS users. The only automation script is in PowerShell, and Windows-centric tools (PowerShell, Excel) are mentioned for log access, while Linux-friendly alternatives are absent. The PowerShell example appears before any mention of cross-platform options, and there is no Azure CLI or Bash script provided.
Recommendations
  • Add equivalent Azure CLI and Bash examples for enabling diagnostic logging, ensuring Linux/macOS users have clear guidance.
  • Mention cross-platform tools for log analysis, such as jq, grep, or open-source log viewers, alongside Excel and Power BI.
  • Present Azure CLI/Bash examples before or alongside PowerShell, to avoid implying Windows-first workflows.
  • Explicitly state that all steps can be performed on Linux/macOS as well as Windows, and link to cross-platform tool documentation.
GitHub Create Pull Request
Application Gateway Tutorial: Configure an Application Gateway with TLS termination using the Azure portal ...main/articles/application-gateway/create-ssl-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 certificate creation and export steps use Windows PowerShell cmdlets (New-SelfSignedCertificate, Export-PfxCertificate) with no mention of Linux or cross-platform alternatives. The virtual machine creation example exclusively uses Windows Server, and IIS installation is performed via PowerShell. There are no examples or instructions for Linux-based certificate creation, Linux VMs, or web servers, nor are Linux command-line tools referenced.
Recommendations
  • Provide equivalent Linux instructions for creating self-signed certificates (e.g., using openssl) and exporting them to PFX format.
  • Include examples for deploying Linux virtual machines (such as Ubuntu) as backend servers.
  • Show how to install a web server (e.g., Apache or Nginx) on Linux VMs for testing.
  • Offer both Windows and Linux command-line examples side by side, or clearly indicate cross-platform alternatives.
  • Reference Linux tools and patterns (e.g., bash, openssl, scp) where appropriate.
  • Add notes clarifying that Application Gateway supports both Windows and Linux backends, and provide parity in documentation steps.
GitHub Create Pull Request
Application Gateway Tutorial: Create an application gateway with URL path-based routing rules using Azure portal ...rticles/application-gateway/create-url-route-portal.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias: it exclusively uses Windows Server virtual machines as backend examples, provides only PowerShell commands for IIS installation, and references Windows-specific tooling (IIS). There are no Linux VM creation steps, no Linux web server installation instructions (e.g., Apache, Nginx), and no Bash or Azure CLI examples for backend setup. The tutorial assumes the reader will use Windows and PowerShell, omitting Linux alternatives entirely.
Recommendations
  • Add parallel instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
  • Provide Linux web server setup steps (e.g., installing Apache or Nginx) with Bash/CLI commands.
  • Include Azure CLI or Bash script examples for backend configuration alongside PowerShell.
  • Mention both Windows and Linux options when describing backend pool composition.
  • Ensure screenshots and test examples include both IIS and Linux web server responses.
  • Clarify that the application gateway supports both Windows and Linux backends, and link to relevant cross-platform setup guides.
GitHub Create Pull Request
Application Gateway Deploy Application Gateway Basic (Preview) ...in/articles/application-gateway/deploy-basic-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 Azure PowerShell, with no mention of Azure CLI or Bash alternatives. The VM creation walkthrough exclusively uses Windows Server 2019, and the backend verification relies on installing IIS (a Windows web server) via PowerShell. There are no examples or instructions for deploying Linux VMs, using Linux-native tools (such as Apache or Nginx), or performing equivalent operations with Linux shell commands. Windows tooling and patterns are presented exclusively and before any Linux alternatives (which are entirely missing).
Recommendations
  • Provide Azure CLI and/or Bash examples alongside Azure PowerShell commands, especially for preview registration and resource management.
  • Include instructions for creating Linux-based backend VMs (e.g., Ubuntu or CentOS) and installing a Linux web server (such as Apache or Nginx) for testing.
  • Offer Linux shell commands for backend server setup and verification, in addition to Windows PowerShell/IIS steps.
  • Explicitly mention that Application Gateway supports both Windows and Linux backend pools, and provide parity in documentation examples.
  • Add a section comparing Windows and Linux deployment patterns, highlighting any differences or considerations.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page references Windows-centric tools (PowerShell, Azure portal, CLI, Terraform) as deployment options, listing PowerShell explicitly and without mentioning Linux-specific equivalents or patterns (e.g., Bash, Azure CLI on Linux, kubectl usage). The order of tool listing places PowerShell before cross-platform or Linux-native options, and there are no Linux-specific examples or guidance. This may unintentionally signal a preference for Windows workflows and tools, and does not provide parity for Linux users.
Recommendations
  • Explicitly mention that Azure CLI and Terraform are cross-platform and provide example commands for both Windows (PowerShell) and Linux (Bash).
  • Include Linux-native deployment examples, such as using Bash scripts or kubectl commands, especially for Kubernetes resource management.
  • Reorder tool listings to avoid placing Windows-specific tools (PowerShell) before cross-platform or Linux-native options.
  • Clarify that all deployment strategies and tools are supported on both Windows and Linux, and provide links to platform-specific guidance where appropriate.
  • Add a section or callout for Linux users, highlighting any considerations or best practices for deploying Application Gateway for Containers from Linux environments.
GitHub Create Pull Request
Application Gateway Quickstart: Deploy Application Gateway for Containers ALB Controller ...ploy-application-gateway-for-containers-alb-controller.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 a mild Windows bias, particularly in the Helm installation section, where Windows instructions and the use of the Windows Package Manager (winget) are presented before Linux instructions. The only explicit OS-specific command example is for Windows (winget), and the documentation references Windows tools directly. However, Linux instructions are present and reasonably complete, and most of the workflow is cross-platform (Azure CLI, Helm, kubectl).
Recommendations
  • Present Linux and Windows installation instructions in parallel tabs or sections, or list Linux first to avoid implicit prioritization.
  • Include explicit examples for macOS where relevant, or clarify cross-platform support for all commands.
  • When referencing OS-specific package managers (e.g., winget), also mention Linux equivalents (e.g., apt, yum, snap) and provide corresponding commands.
  • Clarify that Azure CLI, Helm, and kubectl commands are cross-platform and can be run in Bash, PowerShell, or other shells.
  • Add a note or table summarizing OS compatibility for all steps, ensuring parity and clarity for Linux users.
GitHub Create Pull Request
Application Gateway Application Gateway high traffic volume support ...n/articles/application-gateway/high-traffic-support.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias, primarily through references to PowerShell for configuration tasks (e.g., WAF custom rules, TLS policy configuration), and lacks equivalent Linux CLI (Azure CLI, Bash) examples or mentions. There are no explicit examples or instructions for Linux users, and Windows-centric tools are referenced exclusively for key configuration steps.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell instructions for all configuration tasks, especially for WAF custom rules and TLS policy setup.
  • Explicitly mention cross-platform options (Azure CLI, REST API, portal) wherever PowerShell is referenced.
  • Add notes or sections for Linux/macOS users to ensure parity and inclusivity.
  • Review all referenced links to ensure Linux-compatible instructions are present and visible.
  • Avoid implying PowerShell is the default or only method; present it as one of several options.
GitHub Create Pull Request
Application Gateway Troubleshoot Application Gateway for Containers ...cation-gateway/for-containers/troubleshooting-guide.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 provides both Linux and Windows examples for filtering logs, but the Windows example is given directly after the Linux example and uses Windows-specific tools (findstr). There is a slight preference for Windows in the ordering and explicit mention of Windows tools, while Linux is referenced only in passing. No PowerShell examples are present, but Windows CLI tools are used. The rest of the documentation is platform-agnostic, focusing on kubectl and helm commands, which work cross-platform.
Recommendations
  • Present Linux and Windows examples in parallel tabs or sections, rather than listing Linux first and Windows second.
  • Explicitly mention that kubectl and helm commands work on both Linux and Windows, and provide guidance for MacOS users if relevant.
  • For log filtering, consider using platform-neutral tools (e.g., kubectl's built-in filtering or cross-platform scripting) or provide equivalent examples for MacOS.
  • Ensure that any Windows-specific tool (like findstr) is explained for users unfamiliar with it, and provide alternatives for other platforms.
  • Review future troubleshooting steps to ensure parity in examples and avoid implicit prioritization of one platform over another.
GitHub Create Pull Request
← Previous Page 4 of 35 Next →