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 126-150 of 172 flagged pages
Application Gateway Health monitoring overview for Azure Application Gateway ...lication-gateway/application-gateway-probe-overview.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 Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows and PowerShell by exclusively providing PowerShell cmdlet examples (e.g., New-AzApplicationGatewayProbeHealthResponseMatch) and referencing Azure PowerShell for probe configuration. There are no CLI (az), Bash, or Linux/macOS-specific instructions or examples, which may hinder Linux/macOS users who typically use the Azure CLI or REST API. The page also includes metadata tags indicating a PowerShell focus and does not mention Linux tools or workflows.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell cmdlets shown, especially for probe matching and configuration.
  • Include Bash script snippets or REST API examples for configuring health probes.
  • Update 'Next steps' to reference Azure CLI and REST API documentation, not just PowerShell.
  • Ensure parity in instructions and examples for Linux/macOS users throughout the documentation.
  • Remove or balance metadata tags (e.g., devx-track-azurepowershell) with CLI or cross-platform tags.
GitHub Create Pull Request
Application Gateway Configure an internal load balancer (ILB) endpoint ...configure-application-gateway-with-private-frontend-ip.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 notable Windows bias. It exclusively uses Windows Server as the VM image, provides only PowerShell-based instructions for installing IIS, and omits any Linux VM or Bash/Azure CLI examples. All backend server setup is Windows-centric, with no mention of Linux alternatives or parity in tooling.
Recommendations
  • Include parallel instructions for deploying Linux VMs (e.g., Ubuntu) as backend servers.
  • Provide equivalent Bash/Azure CLI commands for installing a web server (such as Apache or Nginx) on Linux VMs.
  • Show both Windows and Linux options for backend pool configuration, including screenshots and command examples.
  • Explicitly mention that both Windows and Linux VMs are supported and link to relevant setup guides for each.
  • Order examples so that Windows and Linux are presented with equal prominence, or alternate which is shown first.
GitHub Create Pull Request
Application Gateway Create Azure Application Gateway custom error pages ...blob/main/articles/application-gateway/custom-error.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 provides configuration instructions for custom error pages in Azure Application Gateway, but only includes Azure PowerShell examples, which are primarily Windows-centric. There are no CLI (az), Bash, or Linux/macOS-friendly instructions, and PowerShell is presented as the sole automation method. The portal instructions are platform-neutral, but the command-line guidance is biased toward Windows users.
Recommendations
  • Add equivalent Azure CLI (az) examples for configuring custom error pages, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS, or link to installation guides for non-Windows platforms.
  • Present CLI and PowerShell examples side-by-side, or at least mention both options.
  • Clarify any platform-specific limitations or requirements for the PowerShell modules.
GitHub Create Pull Request
Application Gateway Configure Azure Monitor alerts for Application Gateway ...application-gateway/configure-alerts-with-templates.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation references a procedure link that prioritizes CLI and PowerShell usage, which are traditionally Windows-centric tools. The linked procedure page title explicitly mentions PowerShell before ARM and CLI, suggesting a Windows-first approach. No Linux/macOS-specific instructions, examples, or tool references (such as Bash or Azure CLI on Linux) are provided directly on this page.
Recommendations
  • Add explicit instructions and examples for using Azure CLI on Linux/macOS, including shell commands.
  • Ensure that referenced procedure pages provide parity between PowerShell and Bash/CLI examples, and clarify cross-platform compatibility.
  • Include notes or sections highlighting any differences or prerequisites for Linux/macOS users.
  • Avoid listing Windows tools (PowerShell) before cross-platform tools (Azure CLI) unless contextually necessary.
GitHub Create Pull Request
Application Gateway How to migrate from Azure Application Gateway Ingress Controller Helm to AGIC add-on ...es/application-gateway/ingress-controller-migration.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses Azure CLI and Azure Portal for all command-line and UI examples, which are Microsoft-centric tools available on Windows by default. There are no Linux/macOS-specific instructions, nor are alternative Linux-native tools or shell patterns (e.g., bash, kubectl) discussed. The examples and instructions assume the use of Azure CLI, which, while cross-platform, is most commonly associated with Windows environments and is presented without explicit Linux context.
Recommendations
  • Add explicit instructions for installing and using Azure CLI on Linux/macOS, including any platform-specific caveats.
  • Include examples using bash shell syntax and clarify that the CLI commands work on Linux/macOS terminals.
  • Mention and provide guidance for using kubectl for relevant Kubernetes operations, if applicable.
  • Ensure screenshots and UI instructions clarify parity for Linux/macOS users (e.g., browser access to Azure Portal).
  • Consider adding a note at the start stating that all CLI commands are cross-platform and tested on Linux/macOS as well as Windows.
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-11 06:20
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 towards Windows by providing only PowerShell instructions for resource cleanup and configuring IIS on backend VMs (a Windows web server). There are no Linux-specific examples or alternatives for resource deletion (e.g., Azure CLI or Bash), nor is there mention of deploying Linux VMs or using Linux web servers for validation.
Recommendations
  • Add Azure CLI and Bash examples for resource group deletion alongside PowerShell.
  • Include instructions for deploying Linux VMs in the backend pool, with validation using Apache or Nginx.
  • Clarify that IIS is used for demonstration and provide equivalent steps for Linux-based web servers.
  • Ensure screenshots and walkthroughs are not Windows/IIS-specific, or provide Linux alternatives.
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-11 06:20
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 equivalent Linux instructions or examples. There are no references to Linux VMs, Linux web servers, or Bash/Azure CLI commands for backend setup or testing. This creates friction for users who prefer or require Linux-based environments.
Recommendations
  • Include parallel instructions for creating a Linux VM (e.g., Ubuntu) as a backend target.
  • Provide example commands for installing a web server (e.g., Apache or Nginx) on Linux using Bash or Azure CLI.
  • Offer Azure CLI or Bash alternatives alongside PowerShell for all relevant steps, especially for backend configuration and testing.
  • Explicitly mention that both Windows and Linux VMs are supported as backend targets, and link to relevant Linux setup guides.
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-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 is heavily biased towards Windows and PowerShell environments. All migration scripts, examples, and instructions are provided exclusively for Azure PowerShell (.ps1) scripts, with no mention of Bash, Azure CLI, or cross-platform alternatives. The prerequisites and installation steps assume a Windows/PowerShell setup, and there are no Linux/macOS-specific guidance or examples. This creates friction for users on non-Windows platforms, as they must adapt or find their own workarounds.
Recommendations
  • Provide equivalent Azure CLI (az) scripts and examples for all migration steps, including configuration and traffic migration.
  • Include explicit instructions for running migration scripts in Azure Cloud Shell (which supports Bash and PowerShell) and clarify cross-platform compatibility.
  • Add Linux/macOS-specific notes for prerequisites, such as module installation and script execution.
  • Where PowerShell objects are referenced (e.g., PSApplicationGatewaySslCertificate), explain how to achieve the same outcome using Azure CLI or REST API.
  • Reorder examples so that cross-platform or Azure CLI instructions appear before or alongside PowerShell examples.
  • Add troubleshooting tips for common Linux/macOS issues (e.g., file permissions, path formats, module installation).
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-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 moderate Windows bias. PowerShell examples are provided in detail, with CLI examples present but less comprehensive. The page references PowerShell and CLI as configuration methods, but the PowerShell section is more prominent and detailed. There are no explicit Linux/macOS-specific instructions or examples, and the 'Next steps' section directs users to a PowerShell-based guide, omitting Linux-first or cross-platform guidance.
Recommendations
  • Provide equally detailed Azure CLI examples alongside PowerShell, including all configuration steps.
  • Include explicit instructions or examples for Linux/macOS users, such as using Bash scripts or OpenSSL for certificate management.
  • In 'Next steps', link to both PowerShell and CLI-based guides, or a cross-platform guide.
  • Clarify that Azure CLI is cross-platform and highlight its use for Linux/macOS users.
  • Avoid defaulting to PowerShell in examples and navigation; alternate or parallel presentation of CLI and PowerShell is preferable.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides configuration instructions using Azure CLI, PowerShell, and ARM templates. PowerShell examples are given in detail, including both creation and update scenarios, and are presented before ARM template instructions. PowerShell is a Windows-centric tool, and no Linux/macOS-specific alternatives (such as Bash scripting or REST API examples) are provided. The Azure CLI example is present, but PowerShell receives more coverage and is listed before ARM templates, reinforcing a Windows-first approach. There is also a reference to the Azure SDK for .NET, another Windows-preferred technology, with no mention of cross-platform SDKs.
Recommendations
  • Add Bash and/or shell script examples for Linux/macOS users, especially for update scenarios.
  • Include REST API examples for buffer configuration, which are platform-agnostic.
  • Mention cross-platform SDKs (such as Python, Java, or JavaScript) in the references.
  • Ensure that PowerShell instructions are not given undue prominence over CLI or platform-neutral methods.
  • Clarify that Azure CLI works on all platforms and highlight its parity with PowerShell.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias, especially in the backend VM creation and testing sections. It exclusively uses Windows Server VMs and PowerShell commands to install IIS for testing, without mentioning or providing Linux alternatives (e.g., Ubuntu VM, Apache/Nginx setup). The VM creation walkthrough defaults to Windows Server, and all example scripts use PowerShell, with no Bash or Linux CLI equivalents. This creates friction for Linux/macOS users who may prefer or require Linux-based backend servers.
Recommendations
  • Include parallel instructions for creating a Linux VM (e.g., Ubuntu) as a backend server.
  • Provide Linux-specific commands (Bash/CLI) for installing a web server (e.g., Apache or Nginx) for testing.
  • Offer Azure CLI examples alongside PowerShell, especially for extension installation and VM configuration.
  • Explicitly mention that Application Gateway supports both Windows and Linux backend targets.
  • Present both Windows and Linux options in examples, or clarify that the choice of OS is arbitrary for the gateway.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through its 'Next steps' link, which directs users to a PowerShell-based tutorial. PowerShell is a Windows-centric tool, and no mention is made of Azure CLI, Bash, or Linux/macOS-compatible instructions. The absence of Linux/macOS examples or references creates friction for non-Windows users seeking to configure Application Gateway redirection.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for configuring Application Gateway redirection.
  • Include links to Linux/macOS-friendly tutorials alongside PowerShell instructions.
  • Explicitly state cross-platform options for managing Application Gateway (e.g., Azure CLI, REST API, ARM templates).
  • Order examples so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell.
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-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 notable Windows bias by repeatedly referencing Azure PowerShell scripts as the primary migration tool, without mentioning or providing examples for Linux/macOS alternatives (such as Azure CLI or Bash scripts). All migration automation is described in terms of PowerShell, and no Linux-specific guidance or parity is offered. This may create friction for users on non-Windows platforms.
Recommendations
  • Provide equivalent Azure CLI or Bash script examples for migration tasks, especially for public IP retention and configuration migration.
  • Explicitly mention cross-platform options and clarify which scripts/tools can be run on Linux/macOS.
  • Add guidance or links for installing and using Azure PowerShell on Linux/macOS, if PowerShell is required.
  • Reorder examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
  • Include troubleshooting notes for Linux/macOS users if there are known issues running provided scripts.
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-11 06:20
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 referencing Windows-specific certificate formats (PFX), linking to Windows API documentation for certificate handling, and providing PowerShell as the primary (and only) automation example for configuring end-to-end TLS. There is no mention of Linux/macOS tools or command-line examples (such as Azure CLI, Bash, or OpenSSL), nor are Linux certificate management patterns discussed. The 'Next steps' section directs users exclusively to a PowerShell-based guide, further reinforcing the bias.
Recommendations
  • Add Azure CLI and/or Bash examples for configuring end-to-end TLS, alongside PowerShell.
  • Reference cross-platform certificate creation and management tools (e.g., OpenSSL) and provide guidance for Linux/macOS users.
  • Link to documentation for certificate handling on Linux/macOS, not just Windows APIs.
  • Ensure that automation and scripting instructions are available for both Windows and Linux environments.
  • In 'Next steps', provide links to guides for Linux/macOS users, not just PowerShell.
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-11 06:20
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, especially 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 with Windows-specific commands. There are no Linux VM examples, nor instructions for installing a Linux web server (e.g., Apache or Nginx). The tutorial assumes familiarity with Windows tools and patterns, which may create friction for Linux/macOS users.
Recommendations
  • Add parallel instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
  • Provide Linux-specific commands for installing a web server (e.g., Apache: 'sudo apt update && sudo apt install apache2 -y').
  • Include Azure CLI or Bash Cloud Shell examples alongside PowerShell commands.
  • Clarify that Application Gateway supports both Windows and Linux backend VMs.
  • Present Windows and Linux options side-by-side, or alternate which is shown first.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-listeners.md ...rticles/application-gateway/configuration-listeners.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell-only example for enabling HTTP/2 support, with no equivalent CLI or Bash example for Linux users. There is no mention of Linux tools or cross-platform command-line alternatives, and the only automation example is Windows-centric.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell snippets for all configuration steps, especially for enabling HTTP/2 support.
  • Explicitly mention that configuration can be performed from Linux, macOS, and Windows platforms using Azure CLI or REST API.
  • Where automation is discussed, provide parity between PowerShell and CLI/Bash to ensure Linux users are equally supported.
  • Consider including a table or section comparing available tools (PowerShell, CLI, REST API) for common tasks.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-backend-health.md ...lication-gateway/application-gateway-backend-health.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents PowerShell as the first and only explicit scripting example for backend health retrieval, with no mention of Linux shell alternatives (e.g., Bash). While Azure CLI is included, it is listed after PowerShell and lacks contextual parity (no Linux-specific notes or troubleshooting tools). There are no references to Linux-native tools or troubleshooting patterns, and the troubleshooting section focuses on Azure portal and Windows-centric tools.
Recommendations
  • Provide Bash/Linux shell examples alongside PowerShell, especially for backend health retrieval.
  • Explicitly mention that Azure CLI is cross-platform and provide usage notes for Linux/macOS environments.
  • Include troubleshooting steps or tools that are relevant for Linux environments (e.g., curl, openssl for certificate checks).
  • Avoid listing PowerShell before CLI or Bash unless there is a clear reason; consider presenting CLI first for cross-platform parity.
  • Add notes or links for Linux users regarding certificate management and backend server diagnostics.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-overview.md ...articles/application-gateway/configuration-overview.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page lists Windows-centric tools and workflows (PowerShell) before Linux-friendly alternatives (Azure CLI) in the 'Next steps' section, suggesting a Windows-first approach. There is an explicit mention of PowerShell, which is primarily associated with Windows, and it appears before the Azure CLI, which is more commonly used on Linux and cross-platform environments. No Linux-specific examples or tools are provided, and no parity is shown for Linux users in terms of command-line instructions or workflows.
Recommendations
  • List Azure CLI instructions before PowerShell to avoid implicit Windows-first bias.
  • Include explicit Linux examples or workflows where relevant, such as using Bash or shell scripts.
  • Clarify that Azure CLI is cross-platform and provide links to installation guides for Linux and macOS.
  • Consider adding a table or section comparing PowerShell and CLI usage for common tasks, highlighting Linux compatibility.
  • Ensure that screenshots and step-by-step guides do not assume a Windows environment unless necessary.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/quickstart-create-application-gateway-for-containers-managed-by-alb-controller.md ...ation-gateway-for-containers-managed-by-alb-controller.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation relies exclusively on Azure CLI commands and Bash scripting, which are cross-platform but are most commonly used in Windows environments via Azure Cloud Shell or Windows Subsystem for Linux (WSL). There is no explicit mention of Linux-specific tools, nor are there examples tailored for Linux-native environments. The instructions for subnet and resource management use Azure CLI, which is available on Linux, but the documentation does not clarify Linux compatibility or provide Linux-specific notes. There is no evidence of PowerShell usage, but the focus on Azure CLI without explicit Linux context may suggest a subtle Windows-first bias.
Recommendations
  • Explicitly state that all Azure CLI and kubectl commands work natively on Linux, macOS, and Windows.
  • Add notes or examples showing command execution in a Linux shell (e.g., Ubuntu terminal), especially for users running AKS on Linux hosts.
  • Mention installation instructions for Azure CLI and kubectl on Linux systems.
  • If any commands have different syntax or requirements on Linux (e.g., environment variable handling), provide those details.
  • Consider adding a 'Platform compatibility' section to clarify that the steps are OS-agnostic and highlight any platform-specific caveats.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ssl-certificate-management.md ...cles/application-gateway/ssl-certificate-management.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by mentioning PowerShell commands before Azure CLI commands when describing how to list SSL certificate objects. No Linux-specific tools or examples are provided, and the only command-line references are to PowerShell and Azure CLI, with PowerShell listed first. There are no explicit Linux examples or references to Linux certificate management tools or workflows.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more commonly used on Linux.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide installation or usage links for Linux users.
  • Include references or examples for managing certificates using Linux-native tools (e.g., OpenSSL for certificate creation or inspection).
  • Avoid listing Windows-specific tools or commands first unless there is a technical reason; strive for parity in example ordering.
  • Add a section or note for Linux administrators, highlighting any platform-specific considerations or best practices.
GitHub Create Pull Request
Application Gateway Troubleshoot Application Gateway for Containers ...cation-gateway/for-containers/troubleshooting-guide.md
Low Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Linux and Windows command examples for filtering logs, but the Linux example is presented first, followed by the Windows example. All other instructions and examples use cross-platform tools (kubectl, helm) and are not Windows-specific. No sections are Windows-only or missing Linux/macOS equivalents.
Recommendations
  • Maintain parity by always providing both Linux and Windows examples where OS-specific commands differ.
  • Consider using tabbed sections or clear headings for OS-specific commands, as already done, to improve clarity.
  • If possible, mention that most commands are cross-platform and only filtering/log parsing differs.
GitHub Create Pull Request
Application Gateway Quickstart: Deploy Application Gateway for Containers ALB Controller - Helm ...application-gateway-for-containers-alb-controller-helm.md
Low Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell is featured equally and sometimes first, and Windows-specific tooling (winget) is mentioned for Helm installation. While Linux examples are present, Windows tools and patterns are referenced prominently, and PowerShell is given parity with Azure CLI rather than Bash. The Helm installation section gives Windows instructions first, and only briefly notes Linux installation. There are no Bash-only or Linux-first examples, and PowerShell is used for resource management tasks that could be done with Bash/Azure CLI. However, Linux users can complete all tasks, and the Azure CLI is cross-platform.
Recommendations
  • Provide Bash examples alongside Azure CLI for Linux/macOS users, especially for scripting and environment setup.
  • In the Helm installation section, list Linux installation instructions before Windows, or present both equally.
  • Mention package managers for Linux (apt, yum, snap) for Helm installation, not just curl.
  • Clarify that Azure CLI commands can be run in Bash or PowerShell, and provide Bash syntax where relevant.
  • Consider reducing PowerShell-specific examples unless they offer unique functionality not available in Azure CLI.
  • Ensure all steps can be completed with Azure CLI/Bash on Linux/macOS, and highlight cross-platform compatibility.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway ...ocs/blob/main/articles/application-gateway/overview.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists Windows-centric tools (Azure PowerShell) before cross-platform options (Azure CLI) in the 'Next steps' section. This ordering may subtly signal a preference for Windows environments, and the explicit mention of PowerShell as a primary method can reinforce Windows bias, even though CLI is available. No Linux/macOS-specific examples or tools are mentioned.
Recommendations
  • List Azure CLI before Azure PowerShell in example links, as CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly state that Azure CLI works on Linux/macOS and provide links to installation guides for those platforms.
  • Add a note clarifying that all features are available via CLI and portal, ensuring Linux/macOS users are not disadvantaged.
  • Consider including a Linux/macOS-specific quickstart or example to demonstrate parity.
GitHub Create Pull Request
Application Gateway Application gateway components .../application-gateway/application-gateway-components.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation lists Azure PowerShell (Windows-centric) before Azure CLI (cross-platform) in the 'Next steps' section, suggesting a subtle preference for Windows tools. No examples or instructions are given in this article, so there is no evidence of missing Linux examples or exclusive use of Windows tools. The rest of the content is platform-neutral.
Recommendations
  • List Azure CLI before Azure PowerShell in 'Next steps', as CLI is cross-platform and more accessible to Linux/macOS users.
  • Ensure future articles linked from this page provide both PowerShell and CLI examples, or prioritize CLI for parity.
  • Explicitly mention that both CLI and PowerShell are supported and link to platform-specific instructions if available.
GitHub Create Pull Request
Application Gateway Private Application Gateway deployment ...tion-gateway/application-gateway-private-deployment.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Azure portal instructions first, followed by Azure PowerShell and then Azure CLI. PowerShell examples are detailed and include output, while CLI examples are present but less emphasized. There is a slight preference for Windows-centric tools (PowerShell) and ordering, which may create friction for Linux/macOS users who typically use Azure CLI or REST API. However, CLI instructions are present and functional, and REST API, ARM Template, Bicep, and Terraform are mentioned as options for configuration, though not exemplified.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to better support Linux/macOS users.
  • Include REST API, ARM Template, Bicep, and Terraform example snippets for feature registration and configuration.
  • Clarify that Azure CLI works cross-platform and highlight its usage for non-Windows environments.
  • Ensure output examples for CLI commands are as detailed as those for PowerShell.
  • Add explicit notes or sections for Linux/macOS users where relevant.
GitHub Create Pull Request
← Previous Page 6 of 7 Next →