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