Application Gateway

372
Total Pages
310
Linux-Friendly Pages
62
Pages with Bias
16.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

172 issues found
Showing 101-125 of 172 flagged pages
Application Gateway Configure Azure Application Gateway TCP/TLS proxy ...n/articles/application-gateway/how-to-tcp-tls-proxy.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a notable Windows bias: it exclusively uses Windows Server as the SQL backend, references SQL Server Management Studio (a Windows-only tool) for client connectivity, and does not mention or provide examples for Linux-based SQL Server VMs or cross-platform SQL clients. No Linux or macOS alternatives are discussed for either the backend or client connection steps.
Recommendations
  • Include instructions for deploying SQL Server on Linux VMs (e.g., Ubuntu) using Azure's supported images.
  • Mention and provide examples for connecting to the SQL server using cross-platform SQL clients such as Azure Data Studio, DBeaver, or sqlcmd.
  • Explicitly state that both Windows and Linux VMs are supported as backend targets for Application Gateway.
  • Add screenshots and step-by-step guidance for Linux-based deployment and connection scenarios.
  • List prerequisites and client options for macOS and Linux users.
GitHub Create Pull Request
Application Gateway Troubleshoot session affinity issues ...oubleshoot-application-gateway-session-affinity-issues.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing PowerShell as the only CLI example for checking Application Gateway settings, referencing Windows-centric tools like Fiddler for web debugging, and using Windows-specific installation instructions (e.g., 'Run as administrator'). There are no equivalent Linux/macOS CLI commands (such as Azure CLI or Bash), nor are alternative cross-platform web debugging tools mentioned. Windows tools and patterns are presented first and exclusively.
Recommendations
  • Add Azure CLI and/or Bash examples for checking Application Gateway settings, alongside PowerShell.
  • Include instructions for using cross-platform web debugging tools (e.g., Wireshark, mitmproxy, curl) in addition to Fiddler.
  • Provide installation and usage steps for Linux/macOS users (e.g., how to install and run Fiddler or alternatives on non-Windows platforms).
  • Ensure screenshots and step-by-step instructions are not Windows-exclusive, or supplement with Linux/macOS equivalents.
GitHub Create Pull Request
Application Gateway Create an ingress controller by using an existing Application Gateway deployment ...ication-gateway/ingress-controller-install-existing.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias, primarily through the frequent use of PowerShell-interactive examples, variable assignment patterns typical of Windows/PowerShell, and the use of Windows-centric tooling (PowerShell) in command snippets. While Azure CLI and Bash examples are present, PowerShell commands are often shown for critical steps (such as role assignment and resource queries), and Windows-style variable assignment is used even in contexts where Bash would be more appropriate. Linux/macOS users may experience friction due to the need to translate PowerShell syntax to Bash, especially for scripting and automation.
Recommendations
  • Provide all command examples in both Bash and PowerShell syntax, or default to Bash for cross-platform compatibility.
  • Avoid using PowerShell variable assignment (e.g., $variable=...) in command snippets unless specifically targeting Windows users; use Bash syntax (e.g., variable=...) for general documentation.
  • Clearly indicate which commands are platform-specific and offer alternatives for Linux/macOS users.
  • Ensure that critical steps (such as role assignment and resource queries) have Bash/Azure CLI equivalents shown first or alongside PowerShell examples.
  • Review and update Cloud Shell references to clarify that it supports Bash by default and that PowerShell is optional.
GitHub Create Pull Request
Application Gateway Configure Application Gateway with a frontend public IPv6 address using the Azure portal ...application-gateway/ipv6-application-gateway-portal.md
Medium Priority View Details →
Scanned: 2026-01-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 exclusively using Windows Server as the backend VM example, providing only PowerShell commands for IIS installation, and omitting Linux VM or CLI examples. The instructions for backend setup and testing are tailored to Windows environments, with no mention of Linux alternatives or parity in the walkthrough.
Recommendations
  • Include parallel instructions for deploying a Linux VM (e.g., Ubuntu) as a backend target.
  • Provide equivalent Azure CLI or Bash commands for installing a web server (e.g., Apache or Nginx) on Linux VMs.
  • Show how to test the Application Gateway using a Linux backend, including relevant screenshots and sample outputs.
  • Mention that both Windows and Linux VMs are supported as backend targets, and link to documentation for Linux setup.
  • Present examples for both platforms side-by-side or alternate which platform is shown first.
GitHub Create Pull Request
Application Gateway Deploy an Azure Application Gateway with an IPv6 frontend ...ation-gateway/ipv6-application-gateway-arm-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates bias toward Windows environments by exclusively providing PowerShell commands for resource cleanup and configuring IIS on backend VMs (a Windows web server). There are no Linux-specific examples or alternatives for validation or cleanup, and the template appears to deploy Windows VMs by default.
Recommendations
  • Provide equivalent Azure CLI or Bash commands for resource cleanup (e.g., az group delete).
  • Include instructions or examples for deploying Linux-based backend VMs (such as Ubuntu with Apache or Nginx) and validating the deployment using those tools.
  • Clarify whether the ARM template can be customized for Linux VMs and provide guidance if so.
  • Ensure validation steps include Linux-friendly methods (e.g., curl or wget) and mention browser testing is cross-platform.
  • Add notes or links for Linux/macOS users on how to perform each step without relying on Windows-specific tools.
GitHub Create Pull Request
Application Gateway TLS termination with Azure Key Vault certificates ...b/main/articles/application-gateway/key-vault-certs.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, primarily by providing PowerShell-based examples for key configuration steps and referencing Azure PowerShell as the main automation tool. There are no equivalent Azure CLI or bash examples, and the PowerShell example is presented as the canonical method for tasks that could also be performed on Linux/macOS. The 'Next steps' section further reinforces this bias by linking only to PowerShell-based instructions.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all automation/configuration steps, especially for referencing Key Vault secrets and configuring Application Gateway listeners.
  • Explicitly mention that Azure CLI and bash scripts can be used on Linux/macOS, and provide sample commands.
  • In the 'Next steps' section, include links to CLI and ARM/Bicep template documentation, not just PowerShell.
  • When listing tools (PowerShell, CLI, ARM, Bicep), present them in a neutral or rotating order, not always PowerShell first.
GitHub Create Pull Request
Application Gateway Migrate from V1 to V2 - Azure Application Gateway ...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily oriented toward Windows/PowerShell environments. All migration scripts and examples are provided exclusively in PowerShell, with no mention of Bash, Azure CLI, or cross-platform alternatives. The installation and execution instructions assume a Windows/PowerShell context, and there is no guidance for Linux/macOS users. The use of PowerShell Gallery and PowerShell-specific modules/tools is pervasive, and there are no Linux-first or parity examples.
Recommendations
  • Provide equivalent migration scripts and examples using Azure CLI (az) and Bash, which are cross-platform and natively available on Linux/macOS.
  • Explicitly document how Linux/macOS users can run the migration scripts, including using Azure Cloud Shell (which supports Bash and PowerShell) or running PowerShell Core on Linux/macOS.
  • Add installation instructions for PowerShell Core on Linux/macOS, and clarify any platform-specific requirements or limitations.
  • Where possible, offer downloadable scripts in languages/environments that are cross-platform (e.g., Python, Azure CLI), or clarify that the scripts work in PowerShell Core on non-Windows systems.
  • Reorder examples so that cross-platform solutions (Azure CLI, Bash) are presented before or alongside PowerShell examples.
GitHub Create Pull Request
Application Gateway Quickstart: Direct web traffic using the portal ...in/articles/application-gateway/quick-create-portal.md
Medium 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 notable Windows bias, especially in the backend VM creation and configuration steps. It exclusively uses Windows Server VMs as backend examples and provides only PowerShell commands for installing IIS, with no mention of Linux VM options or equivalent instructions for Apache/Nginx installation. The use of Azure PowerShell and Windows features is presented as the default path, with no Linux alternatives or parity.
Recommendations
  • Include Linux VM creation steps alongside Windows, such as Ubuntu or other supported distributions.
  • Provide equivalent instructions for installing a web server (e.g., Apache or Nginx) on Linux VMs, using Bash/Azure CLI.
  • Offer both PowerShell and Bash/CLI commands for backend server setup, and clearly indicate that Application Gateway supports Linux-based backends.
  • Present examples for both platforms in parallel, or alternate which is shown first.
  • Explicitly mention that IIS is optional and that any web server (including those on Linux) can be used for testing.
GitHub Create Pull Request
Application Gateway Overview of mutual authentication on Azure Application Gateway .../application-gateway/mutual-authentication-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples and references are provided in detail, with CLI examples included but less emphasized. The 'Next steps' section directs users specifically to a PowerShell-based guide, and there is no mention of Linux-specific tools or workflows (e.g., OpenSSL, Bash scripting) for certificate extraction or management. Portal support is noted as unavailable, but no Linux/macOS GUI alternatives are suggested. The ordering and depth of examples favor Windows/PowerShell users, and Linux users may need to infer or adapt steps.
Recommendations
  • Add Linux/macOS-specific examples for certificate extraction and management, such as using OpenSSL commands.
  • Provide Bash or shell script equivalents for configuration tasks where PowerShell is shown.
  • In 'Next steps', link to both PowerShell and Azure CLI guides, or a cross-platform guide.
  • Explicitly mention that Azure CLI works cross-platform and provide parity in example depth.
  • Include troubleshooting notes for Linux users (e.g., file permissions, PEM format specifics).
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway v2? .../blob/main/articles/application-gateway/overview-v2.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias. The migration section references an Azure PowerShell script as the primary migration tool, with no mention of Bash, Azure CLI, or Linux/macOS alternatives. The registration/unregistration preview instructions use Azure CLI, but the examples are shown in PowerShell style (Set-AzContext, Register-AzProviderFeature), which are PowerShell cmdlets and not cross-platform Azure CLI commands. The tutorial link for creating an autoscaling gateway points to a PowerShell-based tutorial, and there are no Linux/macOS-specific instructions or examples. Windows tools and patterns are mentioned exclusively and appear before any cross-platform alternatives.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for migration and management tasks, ensuring Linux/macOS users can follow along without PowerShell.
  • Clarify which commands are PowerShell-specific and offer cross-platform alternatives where possible.
  • Add links to Linux/macOS-focused tutorials and documentation for Application Gateway v2.
  • When referencing scripts or tools, specify their platform compatibility and offer alternatives for non-Windows users.
  • Reorder examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell examples.
GitHub Create Pull Request
Application Gateway Configure Request and Response Buffers ...lob/main/articles/application-gateway/proxy-buffers.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides examples for Azure CLI, PowerShell, and ARM templates. PowerShell (a Windows-centric tool) is given a dedicated section with both creation and update examples, and is listed before ARM templates. There is no mention of Linux/macOS-specific tools or shell scripting, and no Bash or cross-platform scripting examples. The reference to Azure SDK is .NET-focused, which is more common on Windows. The PowerShell method is detailed, reinforcing a Windows bias.
Recommendations
  • Add Bash examples for Linux/macOS users, especially for scripting with Azure CLI.
  • Clarify that Azure CLI works cross-platform and provide sample commands in Bash syntax.
  • Mention cross-platform SDKs (e.g., Python, Java) in the reference section.
  • Consider listing Azure CLI before PowerShell, as CLI is more universal.
  • Explicitly state platform compatibility for each method.
GitHub Create Pull Request
Application Gateway Quickstart: Direct web traffic using a Resource Manager template .../articles/application-gateway/quick-create-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, especially in the resource cleanup section, where only a PowerShell example is provided for deleting resources. Throughout the page, Windows-centric tools (PowerShell) are mentioned before Linux-friendly alternatives (Azure CLI), and no explicit Linux/macOS command examples are given for key tasks. This creates friction for Linux/macOS users who may prefer or require CLI/bash instructions.
Recommendations
  • Provide Azure CLI examples alongside PowerShell for resource cleanup (e.g., 'az group delete --name <resource group name>').
  • Ensure that all command-line instructions are available for both Windows (PowerShell) and Linux/macOS (CLI/bash).
  • When listing options (Azure portal, PowerShell, CLI), alternate or randomize order, or explicitly state parity.
  • Include notes or links for Linux/macOS users on how to perform equivalent actions.
GitHub Create Pull Request
Application Gateway Redirect overview for Azure Application Gateway ...main/articles/application-gateway/redirect-overview.md
Medium 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 references configuration via PowerShell in the 'Next steps' section and links to a tutorial that is PowerShell-specific, which is a Windows-centric tool. There are no examples or guidance for Linux/macOS users (e.g., Azure CLI, Bash, or ARM templates), and Windows tools are mentioned first and exclusively. This creates friction for non-Windows users who may not have access to PowerShell or prefer other platforms.
Recommendations
  • Add equivalent configuration instructions using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include ARM template or REST API examples for redirect configuration.
  • Ensure that links in 'Next steps' include both PowerShell and CLI/Template options, or provide a platform selector.
  • Explicitly mention that PowerShell is available cross-platform, if relevant, or clarify prerequisites for Linux/macOS users.
GitHub Create Pull Request
Application Gateway FAQ on V1 retirement ...ob/main/articles/application-gateway/retirement-faq.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias by repeatedly referencing Azure PowerShell scripts as the primary migration tool, without mentioning or providing equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash). All migration automation is described in terms of PowerShell, and no Linux-native instructions or alternatives are offered. This may create friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI and Bash script examples for migration tasks alongside PowerShell.
  • Explicitly mention platform compatibility for provided scripts (e.g., if PowerShell scripts work on PowerShell Core on Linux/macOS).
  • Provide links to cross-platform migration tools or documentation.
  • List both Windows and Linux/macOS options when describing migration workflows.
  • Clarify any limitations or requirements for running scripts on non-Windows systems.
GitHub Create Pull Request
Application Gateway Generate self-signed certificate with a custom root CA ...ticles/application-gateway/self-signed-certificates.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides parity in certificate generation and web server configuration for both Windows and Linux, primarily using OpenSSL and including examples for IIS (Windows), Apache, and NGINX (Linux). However, in the section on uploading the root certificate to Application Gateway, only Azure PowerShell examples are given, with no Azure CLI or REST API equivalents. Additionally, the PowerShell sample uses Windows-style file paths and is presented before any mention of Linux alternatives, which may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI and/or REST API examples for uploading the root certificate and configuring Application Gateway, using Linux-style file paths.
  • Explicitly mention that Azure PowerShell is available cross-platform, but provide CLI commands for users who prefer native Linux tools.
  • When showing file paths or commands, provide both Windows and Linux/macOS variants, or use generic paths.
  • Consider listing Azure CLI examples before or alongside PowerShell to avoid Windows-first impression.
GitHub Create Pull Request
Application Gateway Renew an Azure Application Gateway certificate ...ain/articles/application-gateway/renew-certificates.md
Medium 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 presents certificate renewal steps with a clear Windows bias: Azure PowerShell instructions (primarily Windows-centric) are given before Azure CLI, and no explicit Linux/macOS shell examples or guidance are provided. The CLI example is generic, but the PowerShell script is detailed and assumes familiarity with Windows tools. There are no references to Linux-specific certificate handling, file paths, or shell environments.
Recommendations
  • Add explicit Linux/macOS shell examples, such as bash commands for certificate manipulation and uploading.
  • Include notes on file path formats and certificate file handling differences between Windows and Linux/macOS.
  • Present Azure CLI instructions before or alongside PowerShell, as CLI is cross-platform.
  • Clarify that Azure CLI works on all platforms and provide troubleshooting tips for Linux/macOS users.
  • Mention any platform-specific prerequisites or limitations.
GitHub Create Pull Request
Application Gateway Enabling end to end TLS on Azure Application Gateway ...blob/main/articles/application-gateway/ssl-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias primarily through its reliance on PowerShell for configuration guidance and by referencing Windows-specific certificate tooling and APIs. The 'Next steps' section directs users exclusively to a PowerShell-based configuration guide, and certificate format support is linked to a Windows API reference. There are no Linux/macOS-specific examples, nor are cross-platform CLI or portal instructions provided, which may hinder non-Windows users.
Recommendations
  • Add equivalent step-by-step instructions for configuring end-to-end TLS using Azure CLI and/or the Azure Portal, which are platform-agnostic.
  • Include examples for certificate management and uploading using Linux/macOS tools (e.g., OpenSSL for certificate creation and manipulation).
  • Reference cross-platform documentation for certificate formats and handling, rather than Windows API documentation.
  • Ensure that links to configuration guides include both PowerShell and Azure CLI/Portal options, with clear navigation for each platform.
GitHub Create Pull Request
Application Gateway Tutorial: Protect your application gateway with Azure DDoS Network Protection ...n-gateway/tutorial-protect-application-gateway-ddos.md
Medium 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 notable Windows bias, particularly in the backend VM creation and configuration steps. Only Windows Server is used as the example OS for backend VMs, and IIS installation is performed exclusively via Azure PowerShell using Windows-specific commands. There are no Linux VM examples, nor instructions for installing a Linux web server (e.g., Apache or Nginx), and no Bash or CLI alternatives are provided for Linux users.
Recommendations
  • Include parallel instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
  • Provide Linux-specific steps for installing a web server (e.g., Apache or Nginx) using Bash/CLI or Azure CLI.
  • Offer Azure CLI or Bash script alternatives to the PowerShell commands for VM extension installation.
  • Explicitly mention that Application Gateway supports both Windows and Linux backend VMs.
  • Present both Windows and Linux examples side-by-side, or alternate which OS is shown first.
GitHub Create Pull Request
Application Gateway Common key vault errors in Application Gateway ...gateway/application-gateway-key-vault-common-errors.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides troubleshooting steps for Azure Application Gateway key vault errors, but command-line examples are exclusively given in PowerShell, with no Azure CLI or Bash equivalents. All procedural instructions reference the Azure Portal (which is cross-platform), but where automation or scripting is shown, only Windows/PowerShell is covered. This creates friction for Linux/macOS users who rely on Azure CLI or Bash scripts.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands shown, especially for certificate updates and Key Vault operations.
  • Where scripting is referenced, provide both PowerShell and Bash/CLI options, or link to cross-platform automation guides.
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide links to relevant documentation.
  • Ensure that examples and instructions do not assume a Windows environment unless strictly necessary.
GitHub Create Pull Request
Application Gateway TLS termination with Azure Key Vault certificates ...b/main/articles/application-gateway/key-vault-certs.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, primarily through the exclusive use of Azure PowerShell for command-line examples and step-by-step instructions. There are no equivalent Azure CLI (cross-platform) or Bash examples, and PowerShell is referenced as the default automation tool. The 'Next steps' section also directs users to a PowerShell-specific guide, further reinforcing the bias. This creates friction for Linux/macOS users who typically use Azure CLI or Bash.
Recommendations
  • Provide equivalent Azure CLI and Bash examples alongside PowerShell commands for all automation steps.
  • Reference Azure CLI documentation in the 'Next steps' section, not just PowerShell.
  • Explicitly mention that all steps can be completed on Linux/macOS using Azure CLI, and link to relevant guides.
  • Where screenshots or UI instructions are given, clarify any platform-specific differences or limitations.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway v2? .../blob/main/articles/application-gateway/overview-v2.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias. The migration section references an Azure PowerShell script as the primary migration tool, and the registration/unregistration examples use Azure CLI commands with Set-AzContext, which is PowerShell-specific and most familiar to Windows users. The 'Next steps' section links first to a PowerShell-based tutorial. There are no explicit Linux/macOS CLI examples, nor are cross-platform alternatives (such as Bash or Azure CLI in Bash) mentioned. The documentation assumes familiarity with PowerShell and Windows-centric tools, potentially creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent Bash/Azure CLI examples for registration, unregistration, and migration tasks.
  • Clarify that Azure CLI commands can be run in Bash, Cloud Shell, or PowerShell, and provide syntax for each where relevant.
  • Include links to cross-platform tutorials (e.g., Bash, Python SDK) alongside PowerShell-based guides.
  • Mention platform-agnostic tools and workflows first, or in parallel with Windows/PowerShell options.
  • Explicitly state OS requirements or compatibility for scripts and tools referenced.
GitHub Create Pull Request
Application Gateway Quickstart: Direct web traffic using a Resource Manager template .../articles/application-gateway/quick-create-template.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 instructions for resource cleanup, referencing IIS (a Windows-only web server) for validation, and omitting Linux/macOS equivalents for key steps. No Bash/Azure CLI example is shown for deleting resources, and the validation relies on IIS, which is not available on Linux VMs by default. Windows-centric tools and patterns are mentioned exclusively or before Linux alternatives.
Recommendations
  • Provide Azure CLI or Bash examples for resource group deletion alongside PowerShell.
  • Include instructions for validating the deployment using a Linux-based web server (e.g., Apache or Nginx), or clarify how Linux users can adapt the validation step.
  • Offer parity in examples and tooling references, ensuring Linux/macOS users have clear, first-class guidance.
  • Where multiple platforms are supported, present CLI/Bash examples before or alongside PowerShell to avoid implicit prioritization.
GitHub Create Pull Request
Application Gateway Renew an Azure Application Gateway certificate ...ain/articles/application-gateway/renew-certificates.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides certificate renewal instructions for Azure Application Gateway using the Azure portal, Azure PowerShell, and Azure CLI. PowerShell examples are given in detail, which are Windows-centric, and are presented before CLI examples. There are no explicit Linux/macOS shell examples or notes about platform differences, and the CLI example uses generic syntax without clarifying Linux-specific nuances (e.g., file paths, quoting). No Linux-specific tools or troubleshooting are mentioned.
Recommendations
  • Add explicit Bash or shell examples for Linux/macOS users, especially for CLI commands.
  • Clarify any platform-specific differences in file paths, certificate formats, or command syntax.
  • Present CLI examples before PowerShell, or side-by-side, to avoid Windows-first bias.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., file permissions, password input).
GitHub Create Pull Request
Application Gateway Backend health ...lication-gateway/application-gateway-backend-health.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides explicit PowerShell examples for viewing backend health before mentioning Azure CLI, and references PowerShell as a primary method. There are no Linux/macOS-specific instructions or examples, and PowerShell is a Windows-centric tool, potentially creating friction for non-Windows users.
Recommendations
  • Provide Bash or shell script examples for Linux/macOS users where applicable.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • List Azure CLI instructions before PowerShell to avoid Windows-first ordering.
  • Explicitly mention platform compatibility for each method (e.g., PowerShell for Windows, Azure CLI for all platforms).
GitHub Create Pull Request
Application Gateway Create a custom probe using the portal ...ion-gateway/application-gateway-create-probe-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents three entry points for creating a custom probe: Azure portal, Azure Resource Manager PowerShell, and Azure Classic PowerShell. Both PowerShell options are Windows-centric, and there is no mention of Azure CLI or Bash examples, which are more common on Linux/macOS. The portal instructions themselves are platform-neutral, but the alternative automation options are Windows-first and PowerShell-heavy, with no Linux/macOS equivalents referenced.
Recommendations
  • Add Azure CLI instructions as an alternative to PowerShell for creating and managing probes, ensuring Linux/macOS users have parity.
  • Explicitly mention that the Azure portal is accessible from any OS/browser to reinforce platform neutrality.
  • Reorder or present automation options (PowerShell, CLI, etc.) in a way that does not prioritize Windows tools.
  • Include links to cross-platform scripting documentation (e.g., Bash, Azure CLI) where relevant.
GitHub Create Pull Request
← Previous Page 5 of 7 Next →