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 176-200 of 981 flagged pages
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-10 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 a Windows bias by referencing Windows-specific certificate formats (PFX), linking to Windows API documentation (PFXImportCertStore), and providing configuration guidance primarily through PowerShell and ARM templates. There is no mention of Linux tools or workflows for certificate management, nor are there examples using Linux-native commands or utilities. The 'Next steps' section directs users to a PowerShell-based guide, further reinforcing the Windows-centric approach.
Recommendations
  • Include Linux-based examples for configuring end-to-end TLS, such as using Azure CLI, Bash scripts, or Terraform.
  • Reference cross-platform certificate formats and provide guidance for converting certificates using OpenSSL.
  • Add links to Linux documentation for certificate management and Application Gateway configuration.
  • Ensure that configuration steps are presented in a platform-neutral way, or provide parallel instructions for both Windows and Linux users.
  • Highlight tools and workflows available on Linux, such as Azure CLI, and avoid assuming PowerShell as the default.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation 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 or only option for backend servers.
Recommendations
  • Include parallel instructions for creating Linux virtual machines (e.g., Ubuntu) as backend servers.
  • Provide Linux-based web server setup examples, such as installing Apache or Nginx using Bash/Cloud Shell.
  • Offer both PowerShell and Bash/Azure CLI commands for backend server configuration and extension installation.
  • Explicitly mention that Application Gateway supports both Windows and Linux backend servers, and show examples for each.
  • Balance screenshots and walkthroughs to show both Windows and Linux VM creation and configuration.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-websocket.md ...s/application-gateway/application-gateway-websocket.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 referencing Azure PowerShell and linking to a PowerShell-based quickstart as the next step, without mentioning or providing equivalent Azure CLI (cross-platform) or Linux-native tooling examples. There are no Linux-specific instructions or examples, and the only explicit tool mentioned for deployment is PowerShell.
Recommendations
  • Provide Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • In the 'Next steps' section, include links to both PowerShell and Azure CLI quickstart guides for creating an Application Gateway.
  • Explicitly mention that all configuration steps can be performed from Linux, macOS, or Windows, and provide sample commands for each where relevant.
  • If referencing template deployments, clarify that these can be deployed using both Azure CLI and PowerShell, and provide example commands for both.
  • Avoid assuming the use of Windows or PowerShell as the default tooling in instructions and examples.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-troubleshooting-502.md ...ion-gateway/application-gateway-troubleshooting-502.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 strong Windows bias by providing only Azure PowerShell examples for troubleshooting, referencing Windows-centric tools and patterns (such as IIS and PowerShell cmdlets), and omitting equivalent Linux/CLI commands or examples. There are no Bash, Azure CLI, or Linux troubleshooting instructions, and Windows terminology (e.g., IIS, PowerShell) is used exclusively or before any mention of Linux alternatives.
Recommendations
  • Add Azure CLI (az) and Bash examples alongside PowerShell for all troubleshooting steps.
  • Include Linux-specific troubleshooting guidance, such as checking NSG/UDR/DNS using Linux tools (e.g., curl, dig, ip route).
  • Reference Linux web servers (e.g., Apache, Nginx) in addition to IIS when discussing backend configuration and health probes.
  • Ensure parity in instructions for both Windows and Linux VMs, including network and certificate validation steps.
  • Avoid using Windows-centric terminology exclusively; provide cross-platform context and examples.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/deploy-basic-portal.md ...in/articles/application-gateway/deploy-basic-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits several Windows-centric biases. All command-line examples for preview registration and IIS installation use Azure PowerShell, with no equivalent Azure CLI or Bash/Linux instructions. The VM creation walkthrough exclusively uses Windows Server 2019 Datacenter, and IIS (a Windows web server) is installed for backend testing, with no mention of Linux VMs or Apache/Nginx alternatives. The documentation references Windows tools and patterns first and exclusively, omitting Linux options throughout.
Recommendations
  • Provide Azure CLI and/or Bash examples alongside Azure PowerShell for preview registration and resource management.
  • Include instructions for creating Linux-based backend VMs (e.g., Ubuntu) and installing a Linux web server (e.g., Apache or Nginx) for parity.
  • Offer examples for installing web servers on Linux VMs using cloud-init or custom script extensions.
  • Explicitly mention that Application Gateway supports both Windows and Linux backend servers.
  • Balance screenshots and walkthroughs to show both Windows and Linux scenarios where applicable.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/create-url-route-portal.md ...rticles/application-gateway/create-url-route-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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, and the only instructions for installing a web server use PowerShell and IIS (Windows-only). There are no examples or guidance for deploying Linux VMs or using Linux-native web servers (e.g., Apache, Nginx), nor are there Bash or Azure CLI commands for Linux setup. Windows tools and patterns (IIS, PowerShell) are mentioned exclusively and before any Linux equivalents, which are entirely absent.
Recommendations
  • Add parallel instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
  • Provide examples for installing a web server on Linux VMs (e.g., using Bash to install Apache or Nginx).
  • Include Azure CLI or Bash scripts for Linux VM setup alongside PowerShell examples.
  • Mention Linux-native web servers and show how to configure them for testing the application gateway.
  • Ensure screenshots and walkthroughs include both Windows and Linux scenarios to improve parity.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/high-traffic-support.md ...n/articles/application-gateway/high-traffic-support.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias, primarily through references to PowerShell for configuration tasks (e.g., WAF custom rules, TLS policy configuration) and a lack of equivalent Linux CLI (Azure CLI, Bash) examples or mentions. There are no explicit Linux-specific instructions, and all command-line guidance is Windows-centric, which may hinder Linux users seeking parity.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for all configuration tasks, especially for WAF custom rules and TLS policy setup.
  • Explicitly mention cross-platform tools (e.g., Azure CLI) and provide guidance for both Windows and Linux environments.
  • Where PowerShell is referenced, include a note or link to equivalent Linux instructions.
  • Review linked documentation to ensure Linux parity in all referenced configuration guides.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/how-to-troubleshoot-application-gateway-session-affinity-issues.md ...oubleshoot-application-gateway-session-affinity-issues.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. PowerShell is the only CLI example provided for checking settings, with no mention of Azure CLI or other cross-platform tools. Fiddler, a Windows-only web debugger, is exclusively used for traffic analysis, with installation instructions referencing Windows-specific actions like 'Run as administrator.' There are no Linux or macOS alternatives or examples for these troubleshooting steps.
Recommendations
  • Include Azure CLI examples alongside PowerShell for configuration checks, as Azure CLI is cross-platform.
  • Mention and provide examples for Linux/macOS-compatible web debugging tools (e.g., Wireshark, mitmproxy, Charles Proxy) in addition to Fiddler.
  • Provide installation and usage instructions for these alternative tools on Linux/macOS.
  • Avoid Windows-specific instructions (e.g., 'Run as administrator') or provide equivalent steps for other operating systems.
  • Ensure screenshots and step-by-step guides are not exclusively Windows-centric.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/mutual-authentication-overview.md .../application-gateway/mutual-authentication-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and references before Azure CLI, and by linking to a PowerShell-focused configuration guide as the next step. There are no Linux-specific examples or mentions of Linux-native tools (such as Bash or OpenSSL commands for certificate management), and the documentation assumes familiarity with Windows/PowerShell patterns. The Azure CLI example is present but less detailed, and there is no parity in guidance for Linux users.
Recommendations
  • Provide Linux/Bash-based examples for certificate extraction, chain management, and Application Gateway configuration using Azure CLI.
  • Ensure that Azure CLI examples are as detailed and prominent as PowerShell examples, and consider presenting CLI examples before or alongside PowerShell.
  • Include references or links to Linux-native tools (e.g., OpenSSL) for certificate management tasks.
  • Balance 'Next steps' links to include both PowerShell and CLI/Linux-focused guides.
  • Explicitly mention cross-platform support and provide guidance for both Windows and Linux administrators.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/renew-certificates.md ...ain/articles/application-gateway/renew-certificates.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation presents certificate renewal steps for Azure Application Gateway using the Azure portal, Azure PowerShell, and Azure CLI. The PowerShell example is detailed and appears before the CLI example, which may suggest a Windows-first approach. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tooling or workflows. The CLI example is generic but lacks context for Linux users (e.g., file path conventions, shell environment).
Recommendations
  • Include explicit bash shell examples for certificate renewal using Azure CLI, demonstrating Linux file path usage and environment.
  • Add notes or sections highlighting Linux compatibility and any differences in workflow or prerequisites.
  • Present CLI examples before PowerShell examples to avoid implicit prioritization of Windows tooling.
  • Reference Linux-native tools (such as OpenSSL) for certificate management where relevant.
  • Clarify that both PowerShell and CLI are cross-platform, but provide guidance for Linux users where needed.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-backend-health-troubleshooting.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-backend-health-troubleshooting.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing PowerShell-based troubleshooting commands and examples, referencing Windows-specific tools (such as certlm.msc and netstat via cmd), and listing Windows methods before Linux alternatives. Linux equivalents (e.g., OpenSSL commands) are mentioned less frequently and often after Windows instructions. Several troubleshooting steps and examples lack explicit Linux guidance, making it harder for Linux users to follow along.
Recommendations
  • Provide CLI and Bash examples alongside PowerShell commands for all troubleshooting steps, especially for network and certificate diagnostics.
  • Include Linux-specific instructions and tools (e.g., using netstat, ss, or lsof for port listening, and openssl for certificate inspection) wherever Windows tools like certlm.msc or cmd are referenced.
  • Ensure that Linux methods are presented with equal prominence and detail as Windows methods, ideally listing both side-by-side.
  • Add screenshots or terminal output examples from Linux environments to match the Windows screenshots.
  • Review all troubleshooting steps to ensure Linux users can perform each action without needing to translate Windows-specific instructions.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-autoscaling-zone-redundant.md ...eway/application-gateway-autoscaling-zone-redundant.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell in the 'Next steps' section for creating an autoscaling, zone redundant application gateway. There are no examples or links for Linux-native tools (such as Azure CLI or ARM templates), and PowerShell is mentioned before any cross-platform alternatives. This may lead Linux users to perceive the documentation as less relevant or accessible for their environment.
Recommendations
  • Add equivalent instructions and links for creating autoscaling, zone redundant application gateways using Azure CLI, which is cross-platform and widely used on Linux.
  • Include ARM template or Bicep deployment examples for infrastructure-as-code parity.
  • Ensure that examples and tutorials are presented in a platform-neutral order, or explicitly highlight both Windows and Linux approaches side-by-side.
  • Review other referenced tutorials to confirm Linux parity and update them as needed.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-create-probe-portal.md ...ion-gateway/application-gateway-create-probe-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page presents instructions for creating a custom probe in Azure Application Gateway primarily through the Azure Portal, with additional navigation links for Azure Resource Manager PowerShell and Azure Classic PowerShell. There are no CLI (az cli), Bash, or Linux-native instructions or examples provided. The PowerShell options are listed before any mention of cross-platform tools, and there is no guidance for Linux users or parity with Linux command-line tooling.
Recommendations
  • Add equivalent instructions and examples for Azure CLI (az cli), which is cross-platform and commonly used on Linux and macOS.
  • Include Bash shell command examples where appropriate, especially for scripting or automation scenarios.
  • Ensure that any scripting or automation guidance is not limited to PowerShell, and provide parity for Linux users.
  • Reorder navigation tabs or selectors to present cross-platform tools (Azure CLI) before or alongside PowerShell.
  • Explicitly mention that the Azure Portal and Azure CLI are both cross-platform, and clarify when a tool is Windows-specific.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-externally-managed-scheduled-autoscaling.md ...ation-gateway-externally-managed-scheduled-autoscaling.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation exclusively uses Azure PowerShell runbooks and commands for implementing scheduled autoscaling, with no mention of Bash, Azure CLI, or Python alternatives. This approach assumes familiarity with PowerShell, which is traditionally a Windows-centric tool, and omits Linux-native or cross-platform automation options. The instructions and examples are presented from a Windows/PowerShell perspective, with no parity for Linux users.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for runbooks, which are more common on Linux systems.
  • Mention Python runbooks as an alternative, as Azure Automation supports Python and this is popular in cross-platform automation.
  • Clarify that Azure Automation supports multiple runbook types (PowerShell, Python, Graphical, Bash) and link to relevant documentation.
  • Present examples for both PowerShell and CLI/Bash side by side, or indicate which steps are platform-agnostic.
  • Avoid assuming PowerShell as the default, and explicitly state that Linux users can use CLI or Python for automation tasks.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-key-vault-common-errors.md ...gateway/application-gateway-key-vault-common-errors.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 command examples for certificate management and update operations, with no equivalent Azure CLI or Linux shell examples. The troubleshooting steps and resolutions consistently reference the Azure portal and PowerShell, which are more commonly used on Windows platforms, and do not mention or prioritize Linux-friendly tools or workflows. There are no bash/CLI examples, and PowerShell is presented as the default automation method.
Recommendations
  • Add Azure CLI (az) command examples alongside PowerShell for all certificate management and troubleshooting steps.
  • Explicitly mention that all steps can be performed on Linux, macOS, and Windows, and provide platform-agnostic instructions where possible.
  • Include screenshots or instructions for the Azure portal on non-Windows platforms if there are differences.
  • Where PowerShell is referenced, also provide bash or shell script equivalents for Linux users.
  • Review all troubleshooting steps to ensure Linux users are not excluded and that parity is maintained in guidance and examples.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-private-deployment.md ...tion-gateway/application-gateway-private-deployment.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Azure PowerShell examples and terminology, referencing PowerShell cmdlets before Azure CLI, and using output examples from PowerShell even in CLI sections. There is a lack of explicit Linux or cross-platform command-line examples, and the documentation assumes familiarity with Windows-centric tools and workflows.
Recommendations
  • Ensure all command-line examples are provided for both Azure PowerShell and Azure CLI, with CLI examples shown first or in parallel to avoid Windows-first ordering.
  • Use CLI output examples in the Azure CLI sections instead of PowerShell output, to reflect the actual user experience on Linux/macOS.
  • Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, and provide links to installation guides for non-Windows platforms.
  • Include screenshots or instructions for using the Azure portal from Linux/macOS browsers, if relevant.
  • Where possible, add notes or sections for Linux administrators, such as using bash scripts or integrating with Linux-native automation tools.
  • Audit for terminology that is Windows-specific (e.g., 'PowerShell', 'cmdlet') and ensure parity in explanations for CLI users.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-diagnostics.md ...application-gateway/application-gateway-diagnostics.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. The workflow for enabling logging is presented first with PowerShell, with no mention of Azure CLI, Bash, or automation via Linux-native tools. The log conversion example references a .NET/C# tool, with no alternatives for Python or other cross-platform languages. There are no Linux shell or Azure CLI examples, nor guidance for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI examples for enabling diagnostic logging, suitable for Linux and macOS users.
  • Include instructions for viewing and analyzing logs using Linux-native tools (e.g., jq, awk, sed) and open-source visualization options.
  • Reference cross-platform programming languages (e.g., Python) for log conversion, and link to relevant tools or scripts.
  • Present both Windows and Linux/macOS workflows side-by-side, or clarify platform requirements for each method.
  • Avoid exclusive references to Windows tools (Excel, Power BI, Visual Studio) and suggest open-source or cross-platform alternatives (e.g., LibreOffice, Grafana, VS Code).
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-ilb-arm.md ...les/application-gateway/application-gateway-ilb-arm.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively uses Windows PowerShell and Azure PowerShell cmdlets for all examples and instructions, with no mention or examples of equivalent Azure CLI commands or Bash scripts. References to switching PowerShell modes and links to Windows PowerShell documentation further reinforce a Windows-centric approach. There are no Linux or cross-platform instructions, and the use of PowerShell is assumed throughout.
Recommendations
  • Add equivalent Azure CLI examples for each PowerShell command, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include a section or callouts for Bash scripting and usage on Linux/macOS environments.
  • Reference Azure CLI documentation alongside PowerShell documentation, and clarify that both tools are supported.
  • Where possible, use neutral terminology (e.g., 'command line' instead of 'PowerShell') and avoid assuming the user is on Windows.
  • Add notes or links for installing and using Azure CLI on Linux/macOS.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-probe-overview.md ...lication-gateway/application-gateway-probe-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 and PowerShell environments. All command-line examples and configuration snippets are provided exclusively in Azure PowerShell, with no equivalent Azure CLI (cross-platform) or ARM template examples. The documentation references PowerShell cmdlets for probe configuration and does not mention or provide examples for Linux users or other cross-platform tools. There is also a custom metadata tag indicating Azure PowerShell tracking, further reinforcing the Windows-centric approach.
Recommendations
  • Add Azure CLI examples for all PowerShell-based configuration steps, especially for creating and configuring custom health probes.
  • Include ARM/Bicep template snippets for infrastructure-as-code users, which are platform-agnostic.
  • Explicitly mention that configuration can be performed from Linux, macOS, and Windows, and provide links to cross-platform tooling.
  • Balance the order of presentation: when mentioning configuration options, list Azure CLI and ARM/Bicep before or alongside PowerShell.
  • Review and update custom metadata tags to reflect cross-platform support, not just Azure PowerShell.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/certificates-for-backend-authentication.md ...ion-gateway/certificates-for-backend-authentication.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses Windows tools (Certificate Manager, PowerShell) for certificate export and management, with step-by-step instructions and screenshots for Windows. There are no examples or instructions for performing equivalent tasks on Linux or macOS, nor are cross-platform CLI tools (like OpenSSL) mentioned. The 'Next steps' section also references PowerShell specifically for further configuration.
Recommendations
  • Add equivalent instructions for Linux and macOS using OpenSSL or other platform-agnostic CLI tools for exporting certificates.
  • Include examples and screenshots for certificate export on Linux (e.g., using OpenSSL commands) and macOS (e.g., Keychain Access or OpenSSL).
  • Mention cross-platform tools and provide guidance for users who do not have access to Windows environments.
  • Reference Azure CLI and REST API methods for configuring Application Gateway, in addition to PowerShell.
  • Reorganize examples so that Windows and Linux/macOS instructions are presented in parallel, or clarify that the steps apply to all platforms where possible.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-ssl-policy-overview.md ...ion-gateway/application-gateway-ssl-policy-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing PowerShell as the primary method for viewing or configuring TLS policy details, mentioning PowerShell before CLI and REST API, and linking only to PowerShell-based configuration guides. There are no explicit Linux or Bash examples, nor are Linux-native tools or workflows discussed. The absence of Linux-specific instructions or parity in examples makes the documentation less accessible to Linux administrators.
Recommendations
  • Provide Linux/Bash examples alongside PowerShell for all configuration steps, including viewing and setting TLS policies.
  • Reference Azure CLI and REST API equally or before PowerShell when listing management options.
  • Add links to Linux-focused configuration guides (e.g., using Azure CLI on Linux, Bash scripts, or automation tools like Ansible).
  • Explicitly mention that all operations can be performed from Linux environments and provide sample commands.
  • Ensure that terminology and instructions do not assume a Windows environment or tooling.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-infrastructure.md ...es/application-gateway/configuration-infrastructure.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing Azure PowerShell commands (e.g., Stop-AzApplicationGateway, Start-AzApplicationGateway) without providing equivalent Azure CLI (cross-platform) or Linux-native instructions. The only explicit command-line tooling mentioned is PowerShell, and no Bash or Linux shell examples are given. This may create the impression that Windows/PowerShell is the primary or preferred environment for managing Azure Application Gateway infrastructure.
Recommendations
  • For every PowerShell command or reference, provide an equivalent Azure CLI example (e.g., az network application-gateway stop/start) and link to both sets of documentation.
  • When suggesting tools for managing or scripting Azure resources, mention Azure CLI first or alongside PowerShell, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include explicit Linux/Bash shell examples where relevant, especially for common administrative tasks.
  • Clarify in notes or tips that all management operations can be performed from any OS using Azure CLI, Azure Portal, or PowerShell (with cross-platform support), and provide links to installation guides for each.
  • Review all command references and ensure parity between Windows/PowerShell and Linux/Azure CLI instructions throughout the documentation.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configure-web-app.md ...main/articles/application-gateway/configure-web-app.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 a strong Windows bias by exclusively providing PowerShell-based CLI examples for all automation/configuration steps, with no Bash, Azure CLI, or Linux shell equivalents. All scripting and command-line instructions use Windows-centric tools (Azure PowerShell), and there is no mention of cross-platform alternatives or Linux-friendly workflows. The structure and examples prioritize Windows/PowerShell usage, implicitly assuming a Windows environment for automation and scripting.
Recommendations
  • Provide equivalent Azure CLI (az) examples for each PowerShell script, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash shell script examples for common tasks, especially for testing and automation steps.
  • Explicitly mention that all steps can be performed from Linux/macOS environments using Azure CLI, and link to relevant cross-platform documentation.
  • Add notes or tabs for Linux/macOS users, clarifying any differences in workflow or tool usage.
  • Avoid assuming PowerShell as the default automation tool; present both PowerShell and Azure CLI examples side-by-side.
  • Where referencing certificate creation or management, include OpenSSL-based instructions for Linux users in addition to Windows-centric methods.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configure-application-gateway-with-private-frontend-ip.md ...configure-application-gateway-with-private-frontend-ip.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 VM image, providing only PowerShell-based instructions for backend configuration (IIS installation), and omitting any Linux-based examples or alternatives (such as using Ubuntu and Apache/Nginx, or Bash/CLI commands). The use of Windows tools and patterns is pervasive, and Linux options are neither mentioned nor presented as alternatives.
Recommendations
  • Include parallel instructions for creating Linux-based backend VMs (e.g., Ubuntu) and installing a web server (Apache or Nginx) using Bash or Azure CLI.
  • Provide both PowerShell and Bash/Azure CLI examples for VM extension configuration.
  • Mention Linux as a supported backend OS and highlight differences or considerations for Linux users.
  • Add screenshots and code snippets that demonstrate Linux workflows in the Azure portal and Cloud Shell.
  • Ensure that examples and steps do not assume Windows as the default, and present both Windows and Linux options side-by-side where applicable.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/create-ssl-portal.md ...main/articles/application-gateway/create-ssl-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 steps exclusively use Windows Server, and IIS is installed for testing, again with only Windows-specific instructions. There are no examples or guidance for performing these tasks on Linux systems, nor are Linux tools or patterns mentioned.
Recommendations
  • Provide equivalent Linux instructions for creating self-signed certificates (e.g., using openssl) and exporting to PFX format.
  • Include examples for deploying Linux-based backend VMs (e.g., Ubuntu, CentOS) and installing a web server such as Apache or Nginx for testing.
  • Add cross-platform Azure CLI or Bash examples alongside PowerShell commands, especially for certificate management and VM extension installation.
  • Mention Linux tools and patterns (openssl, systemd, etc.) where relevant, and ensure parity in step-by-step guidance for both operating systems.
  • Clearly indicate that Application Gateway supports both Windows and Linux backend servers, and provide links to relevant Linux documentation.
GitHub Create Pull Request
← Previous Page 8 of 40 Next →