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 151-175 of 981 flagged pages
Application Gateway Deploy Application Gateway Basic (Preview) ...in/articles/application-gateway/deploy-basic-portal.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 First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples for preview registration and VM extension use Azure PowerShell, with no mention of Azure CLI or Bash alternatives. The VM creation walkthrough exclusively uses Windows Server 2019 Datacenter, and IIS (a Windows web server) is installed for testing, with no Linux VM or Apache/Nginx example provided. The instructions for installing IIS use Windows-specific PowerShell commands and extensions, and there is no guidance for deploying or testing with Linux-based backends.
Recommendations
  • Provide Azure CLI and Bash examples alongside Azure PowerShell for preview registration and resource management.
  • Include Linux VM creation steps (e.g., Ubuntu or CentOS) as backend pool options, in addition to Windows.
  • Offer instructions for installing and testing with Apache or Nginx on Linux VMs, paralleling the IIS example.
  • Mention Linux-based tools and patterns where relevant, such as using SSH for VM access and shell scripts for configuration.
  • Ensure screenshots and walkthroughs show parity between Windows and Linux scenarios, or clarify that both are supported.
GitHub Create Pull Request
Application Gateway Diagnostic logs for Application Gateway for Containers ...cles/application-gateway/for-containers/diagnostics.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides detailed instructions for enabling diagnostic logging using the Azure portal and PowerShell, both of which are Windows-centric tools. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or ARM templates. The PowerShell example is given as the only code-based method, and Windows tools are mentioned exclusively for log viewing (Excel, Power BI) before any cross-platform alternatives. This creates a bias toward Windows users and leaves Linux users without parity in instructions.
Recommendations
  • Add Azure CLI examples for enabling diagnostic logging, as CLI is cross-platform and widely used on Linux.
  • Include Bash script samples for log extraction and management.
  • Mention and provide examples for viewing logs using Linux-friendly tools (e.g., jq, grep, less) alongside Excel and Power BI.
  • Ensure that instructions for configuring diagnostic settings are not limited to the Azure portal and PowerShell; include ARM template and REST API options.
  • Reorder sections so that cross-platform tools and examples are presented before or alongside Windows-specific ones.
GitHub Create Pull Request
Application Gateway Troubleshoot Application Gateway for Containers ...cation-gateway/for-containers/troubleshooting-guide.md
High Priority View Details →
Scanned: 2026-01-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 Linux and Windows examples for filtering logs, but the Windows example is given its own tab and uses Windows-specific tools (findstr). The Linux example uses grep, but the Windows example is presented separately and uses CLI syntax. There is no explicit PowerShell example, but the use of Windows tools and the separation of examples can signal a slight Windows-first bias. All other commands are cross-platform (kubectl, helm), and there are no missing Linux examples.
Recommendations
  • Present Linux and Windows examples side-by-side or in a unified format, rather than in separate tabs, to emphasize parity.
  • Explicitly mention that commands (kubectl, helm) are cross-platform and provide any necessary notes for OS-specific behaviors.
  • Consider adding PowerShell examples if Windows CLI is shown, or clarify that findstr works in both Command Prompt and PowerShell.
  • Ensure that Linux examples are not secondary to Windows examples in order or presentation.
  • Add troubleshooting tips for common Linux shell issues (e.g., differences in redirecting output, file permissions) if relevant.
GitHub Create Pull Request
Application Gateway Quickstart: Deploy Application Gateway for Containers ALB Controller ...ploy-application-gateway-for-containers-alb-controller.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits Windows bias in several areas. Windows installation instructions for Helm (using winget and PowerShell) are presented before Linux instructions, and the Windows-specific tool 'winget' is highlighted. The Linux installation is covered, but less prominently. There are no Linux-specific troubleshooting tips or parity notes for command-line differences. The overall flow and examples tend to assume Azure CLI and Windows environments, with Azure Cloud Shell (which is Linux-based) mentioned but not emphasized as a cross-platform solution.
Recommendations
  • Present Linux and Windows instructions in parallel tabs or sections, giving equal prominence to both.
  • Include Linux-first examples where appropriate, or alternate the order of Windows and Linux instructions.
  • Add troubleshooting notes for common Linux issues (e.g., permissions, package manager alternatives).
  • Highlight Azure Cloud Shell as a cross-platform solution more prominently.
  • Provide explicit Bash and PowerShell command examples side-by-side for steps that differ.
  • Mention alternative Linux package managers (e.g., apt, yum, snap) for Helm installation.
  • Ensure all CLI commands are tested and documented for both Windows and Linux environments.
GitHub Create Pull Request
Application Gateway Application Gateway high traffic volume support ...n/articles/application-gateway/high-traffic-support.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 by referencing PowerShell as the primary method for configuring WAF custom rules and TLS policy versions, without mentioning or providing equivalent examples for Linux users (e.g., Azure CLI, Bash). There are no Linux-specific instructions or examples, and Windows-centric tools are referenced exclusively in sections related to configuration.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all configuration tasks currently shown with PowerShell.
  • Explicitly mention cross-platform options (e.g., Azure CLI, REST API) alongside PowerShell in all relevant sections.
  • Add guidance or links for Linux/macOS users on how to perform the same operations.
  • Ensure that configuration instructions do not assume the use of Windows or PowerShell by default.
GitHub Create Pull Request
Application Gateway Configure Azure Application Gateway TCP/TLS proxy ...n/articles/application-gateway/how-to-tcp-tls-proxy.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively using Windows-based SQL Server VM images, referencing SQL Server Management Studio (a Windows-only tool) for client connectivity, and omitting any mention of Linux-based SQL Server deployment or Linux client tools. All examples and screenshots are based on Windows environments, with no Linux alternatives provided.
Recommendations
  • Include instructions for deploying SQL Server on Linux VMs (e.g., Ubuntu or Red Hat) in Azure.
  • Provide examples of connecting to the SQL Server backend using cross-platform or Linux-native tools such as sqlcmd, Azure Data Studio, or DBeaver.
  • Add screenshots and command-line examples for Linux environments where relevant.
  • Explicitly mention that Application Gateway TCP/TLS proxy works with both Windows and Linux backends, and provide parity in documentation steps.
  • List both Windows and Linux SQL Server images as options during VM creation.
GitHub Create Pull Request
Application Gateway Create an ingress controller by using a new Application Gateway deployment .../application-gateway/ingress-controller-install-new.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by recommending Azure Cloud Shell (which defaults to Bash or PowerShell, but is visually represented with PowerShell icons), referencing Windows-centric tools and patterns (such as PowerShell and Azure Portal icons), and omitting explicit Linux shell or terminal instructions. The visual cues and tool recommendations are more familiar to Windows users, and there is little to no mention of Linux-specific environments, shells, or alternative workflows.
Recommendations
  • Add explicit instructions and screenshots for using Linux terminals and shells, such as GNOME Terminal, Konsole, or macOS Terminal.
  • Include examples of running commands in native Linux environments, not just Cloud Shell or PowerShell.
  • Balance visual cues by showing both Bash and PowerShell icons, or clarify that Bash is available and recommended for Linux/macOS users.
  • Mention Linux package managers (apt, yum, zypper, etc.) when listing installation instructions for required tools.
  • Provide troubleshooting tips or notes for common Linux-specific issues (e.g., file permissions, environment variables).
  • Clarify that all CLI commands are cross-platform and provide any necessary adjustments for Linux/macOS users (such as differences in command syntax or file paths).
GitHub Create Pull Request
Application Gateway HTTP response codes - Azure Application Gateway ...in/articles/application-gateway/http-response-codes.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias in several ways: NTLM authentication (a Windows-specific protocol) is discussed without mentioning Linux alternatives; troubleshooting for backend server timeouts lists IIS first and in detail, while Nginx (common on Linux) is mentioned second and less thoroughly; there are no Linux-specific troubleshooting examples or references to Linux tools/logs, and no PowerShell or CLI examples are provided for either platform.
Recommendations
  • Include Linux authentication scenarios (e.g., Kerberos, LDAP) when discussing backend authentication issues.
  • Present Nginx (Linux) and IIS (Windows) backend server timeout configuration with equal detail, and consider listing Nginx first or side-by-side.
  • Add troubleshooting examples using Linux tools (e.g., curl, journalctl, systemd logs) and reference Linux-specific error logs.
  • Provide Azure CLI and Bash examples for troubleshooting, alongside any PowerShell or Windows-specific instructions.
  • Mention common Linux web servers (Apache, Nginx) and their configuration for timeouts and error codes, not just IIS.
GitHub Create Pull Request
Application Gateway Create an ingress controller by using an existing Application Gateway deployment ...ication-gateway/ingress-controller-install-existing.md
High Priority View Details →
Scanned: 2026-01-10 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 moderate Windows bias. Several command examples use PowerShell syntax and variables, especially in identity and role assignment steps, despite Azure CLI and Bash being cross-platform. The backup instructions reference the Azure portal and mention PowerShell scripts as restoration options alongside Bash, but do not clarify Linux parity. PowerShell-based examples appear before or instead of pure Bash alternatives, and there is no explicit guidance for Linux users regarding differences or equivalence.
Recommendations
  • Provide all command examples in both PowerShell and Bash/Azure CLI syntax, or default to Bash for cross-platform compatibility.
  • Clearly indicate which commands are platform-specific and offer Linux equivalents where PowerShell is used.
  • When referencing downloadable scripts (e.g., in backups), specify which are for Windows and which for Linux, and ensure both are present.
  • Avoid using PowerShell variable syntax ($var) in CLI examples unless specifically targeting Windows users; prefer Bash syntax for general documentation.
  • Add a note at the beginning clarifying that all steps can be performed on Linux, macOS, and Windows, and highlight any platform-specific considerations.
  • Ensure that any automation or scripting instructions are available in Bash for Linux users, not just PowerShell.
GitHub Create Pull Request
Application Gateway Deploy an Azure Application Gateway with an IPv6 frontend ...ation-gateway/ipv6-application-gateway-arm-template.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates bias towards Windows by exclusively using IIS (a Windows web server) for backend validation, referencing only Azure PowerShell for resource cleanup, and omitting Linux-based alternatives or CLI examples. There are no instructions or examples for deploying or validating with Linux VMs, nor is Bash/Azure CLI used for resource management.
Recommendations
  • Include examples using Linux VMs in the backend pool, such as deploying Apache or Nginx for validation.
  • Provide instructions for validating the deployment using Linux tools (e.g., curl, wget) from a Linux VM.
  • Add Azure CLI or Bash examples for resource cleanup alongside PowerShell.
  • Mention Linux VM configuration steps in the ARM template review and deployment sections.
  • Balance screenshots and walkthroughs to show both Windows and Linux scenarios.
GitHub Create Pull Request
Application Gateway TLS termination with Azure Key Vault certificates ...b/main/articles/application-gateway/key-vault-certs.md
High Priority View Details →
Scanned: 2026-01-10 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 bias towards Windows and PowerShell by providing only PowerShell-based command-line examples for configuring Application Gateway with Key Vault certificates. There are no equivalent examples using Bash, Azure CLI, or Linux-native tools. References to scripting and automation are exclusively in the context of PowerShell, which is traditionally associated with Windows environments. The documentation also refers to the Azure portal and PowerShell before mentioning the Azure CLI or ARM templates, and does not provide Linux-specific guidance or parity in example commands.
Recommendations
  • Provide equivalent Azure CLI (az) command examples alongside PowerShell for all configuration steps, especially for referencing Key Vault secrets and configuring Application Gateway.
  • Include Bash script examples for automation tasks to cater to Linux users.
  • Explicitly mention that all steps can be performed on Linux, macOS, and Windows, and clarify any platform-specific considerations.
  • Reorder sections to present Azure CLI and PowerShell examples together, or alternate which is presented first.
  • Add a 'Platform compatibility' note indicating that PowerShell Core is available cross-platform, but also provide native Linux/Bash/CLI alternatives.
  • Ensure troubleshooting and error investigation steps include CLI and Bash options, not just portal or PowerShell.
GitHub Create Pull Request
Application Gateway Overview of mutual authentication on Azure Application Gateway .../application-gateway/mutual-authentication-overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell examples and references, listing PowerShell before Azure CLI in configuration instructions, and lacking explicit Linux-oriented command-line examples or guidance. The 'Next steps' section directs users to a PowerShell-focused guide, reinforcing the Windows-centric approach. There are no Bash or Linux shell examples, and the CLI coverage is minimal compared to PowerShell.
Recommendations
  • Provide Bash/Linux shell examples alongside PowerShell and Azure CLI, especially for certificate extraction and management tasks.
  • Ensure Azure CLI instructions are as detailed and prominent as PowerShell, including step-by-step configuration for mutual authentication and certificate revocation.
  • Add links to Linux-focused guides in the 'Next steps' section, such as configuring mutual authentication using Azure CLI or ARM templates from a Linux environment.
  • Explicitly mention cross-platform compatibility for all tools and commands, clarifying usage on both Windows and Linux.
  • Include troubleshooting and best practices for Linux users, such as handling PEM/CER files and using OpenSSL for certificate operations.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway v2? .../blob/main/articles/application-gateway/overview-v2.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 First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias primarily through the exclusive use of Azure PowerShell scripts and references for migration and preview registration/unregistration tasks. No Linux-specific CLI (az CLI, bash) examples are provided, and the only tutorial linked is PowerShell-based. Windows tools and patterns (PowerShell Gallery, Set-AzContext) are mentioned without Linux alternatives, and instructions for key operations are presented in a Windows-first manner.
Recommendations
  • Provide equivalent Azure CLI (az CLI) examples for all PowerShell commands, ensuring Linux and macOS users have clear guidance.
  • Include links to tutorials and migration guides that use az CLI and bash scripting, not just PowerShell.
  • Explicitly mention cross-platform support for management tasks, and clarify which commands work on Linux/macOS.
  • Add a section or callout for Linux users, highlighting any differences or additional steps needed.
  • Ensure that all code blocks are labeled with the platform they target (e.g., PowerShell, Bash, az CLI) and offer parity in examples.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates Windows bias in several ways: the only virtual machine example uses Windows Server 2019 Datacenter, and the only backend configuration and testing instructions involve installing IIS via Azure PowerShell (with Windows-specific commands). There are no Linux VM examples, nor instructions for deploying or testing with a Linux backend (e.g., Apache or Nginx). The PowerShell-based IIS installation is presented as the default method for backend testing, with no Bash or Linux alternatives.
Recommendations
  • Add parallel instructions for creating a Linux VM (e.g., Ubuntu or CentOS) as a backend target, including portal steps and configuration.
  • Provide Linux-based testing instructions, such as installing Apache or Nginx via Bash/Cloud Shell, and verifying connectivity using curl or similar tools.
  • Include Bash/CLI examples alongside PowerShell for backend configuration and extension installation.
  • Clarify that both Windows and Linux VMs are supported as backend targets, and provide links or references to relevant Linux documentation.
  • Present Windows and Linux examples side-by-side or alternate their order to avoid implicit prioritization.
GitHub Create Pull Request
Application Gateway Migrate from V1 to V2 - Azure Application Gateway ...lob/main/articles/application-gateway/migrate-v1-v2.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 Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows and PowerShell. All migration scripts, examples, and instructions are provided exclusively for Azure PowerShell, with no mention of Bash, Azure CLI, or Linux-native tooling. Script installation and usage patterns assume a Windows/PowerShell environment, and there is no guidance for Linux or cross-platform users. The documentation does not provide parity for Linux users, omitting equivalent Azure CLI commands or Bash script examples.
Recommendations
  • Add Azure CLI examples and scripts for all migration steps, including configuration and traffic migration.
  • Provide Bash script equivalents for certificate handling and resource management tasks.
  • Include explicit instructions for running migration scripts in Azure Cloud Shell (Bash) and on Linux/macOS environments.
  • Clarify cross-platform compatibility of provided PowerShell scripts, and document any prerequisites for running them on Linux/macOS (e.g., PowerShell Core, Az module installation).
  • List both PowerShell and Azure CLI options side-by-side in prerequisites and step-by-step guides.
  • Ensure script download and installation steps are platform-agnostic, or provide alternatives for Linux users (e.g., wget/curl for script download, manual execution instructions).
GitHub Create Pull Request
Application Gateway Export trusted client CA certificate chain for client authentication ...ateway/mutual-authentication-certificate-management.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily Windows-centric: all certificate export steps use Windows GUI tools (Certificate Manager, Certificate Export Wizard), with screenshots and instructions for Windows only. PowerShell and Windows-specific paths are referenced, while Linux equivalents (e.g., openssl commands, file locations) are missing. Only in the final concatenation step is a Linux command shown, and even there, the Windows command is listed first.
Recommendations
  • Add step-by-step instructions for exporting certificates using Linux tools such as openssl, including commands for extracting public certificates and CA chains.
  • Include screenshots or terminal output examples for Linux workflows.
  • Present Linux and Windows instructions in parallel, or clearly separate them, rather than listing Windows first.
  • Reference Linux certificate storage locations and management tools (e.g., /etc/ssl/certs, update-ca-certificates).
  • Avoid assuming GUI access; provide CLI alternatives for both platforms.
GitHub Create Pull Request
Application Gateway Quickstart: Direct web traffic using the portal ...in/articles/application-gateway/quick-create-portal.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 page demonstrates a Windows bias in several ways: it exclusively uses Windows Server virtual machines as backend examples, provides only Windows IIS installation instructions (via PowerShell), and omits any Linux VM or web server setup. The PowerShell-based IIS installation is presented as the sole method for backend configuration, and no Linux equivalents (such as Apache or Nginx installation) or Bash/CLI commands are offered. The quickstart implicitly assumes a Windows environment for backend testing and validation.
Recommendations
  • Include parallel instructions for deploying Linux VMs (e.g., Ubuntu) as backend servers.
  • Provide Linux web server setup steps (e.g., installing Apache or Nginx) using Bash/CLI commands.
  • Offer both PowerShell and Bash/CLI examples for backend configuration and testing.
  • Clarify that Application Gateway supports both Windows and Linux backends, and show examples for each.
  • Ensure screenshots and walkthroughs reflect both Windows and Linux scenarios where applicable.
GitHub Create Pull Request
Application Gateway Redirect overview for Azure Application Gateway ...main/articles/application-gateway/redirect-overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page exhibits Windows bias by referencing only Windows-centric tools and workflows, such as the Azure portal and a PowerShell-based tutorial for configuring URL redirection. There are no examples or guidance for Linux users (e.g., using Azure CLI, Bash, or ARM templates), and the 'Next steps' section links exclusively to a PowerShell tutorial, implicitly prioritizing Windows environments.
Recommendations
  • Add equivalent Linux-focused examples, such as configuring redirects using Azure CLI or Bash scripts.
  • Provide links to tutorials for configuring Application Gateway redirection using ARM templates or REST API, which are platform-agnostic.
  • Ensure that 'Next steps' includes both Windows (PowerShell) and Linux (CLI/Bash) options, or a cross-platform guide.
  • Explicitly mention that the configuration can be performed from any OS using platform-neutral tools.
GitHub Create Pull Request
Application Gateway Configure Azure Application Gateway Private Link ...articles/application-gateway/private-link-configure.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples and references before Azure CLI, which is more cross-platform. The PowerShell section is more extensive, with a longer script and a dedicated cmdlet reference list, while the CLI section is shorter and lacks equivalent depth. There are no Linux-specific instructions, troubleshooting, or tool recommendations, and the use of PowerShell (a Windows-centric tool) is emphasized. The Azure portal instructions also implicitly favor Windows users, as the portal experience is most seamless on Windows.
Recommendations
  • Ensure Azure CLI examples are as detailed and comprehensive as PowerShell examples, including troubleshooting and command references.
  • Add explicit notes or sections for Linux/macOS users, such as shell environment setup, common issues, or platform-specific tips.
  • Consider providing Bash or shell script equivalents for automation tasks, especially for steps currently only shown in PowerShell.
  • Clarify that Azure CLI is fully supported on Linux/macOS and encourage its use for cross-platform scenarios.
  • Where possible, avoid listing PowerShell before CLI, or alternate the order to avoid implicit prioritization.
  • Include links to install and configure Azure CLI on Linux/macOS, and mention compatibility.
GitHub Create Pull Request
Application Gateway Configure Request and Response Buffers ...lob/main/articles/application-gateway/proxy-buffers.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 First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides configuration examples using Azure CLI, PowerShell, and ARM templates. PowerShell is given a dedicated section with detailed examples for both creating and updating the Application Gateway, while no equivalent Linux shell (e.g., Bash) or cross-platform scripting examples are provided. The CLI examples use 'az', which is cross-platform, but the PowerShell section is more extensive and appears before any mention of Linux-specific tools or patterns. There is no mention of Linux-native tools or scripting approaches, nor are there Bash or shell script examples. The reference to the Azure SDK is for .NET, which is more commonly used on Windows.
Recommendations
  • Add Bash/shell script examples for Linux users alongside PowerShell examples.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Include references to cross-platform SDKs (e.g., Python, Java) in addition to .NET.
  • Avoid giving PowerShell examples more prominence or detail than Linux equivalents.
  • Consider adding a section on automating buffer configuration using Linux-native tools or scripts.
GitHub Create Pull Request
Application Gateway HTTP to HTTPS redirection in portal - Azure Application Gateway ...s/application-gateway/redirect-http-to-https-portal.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 First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use PowerShell, including certificate creation and IIS installation. The virtual machine scale set is configured with Windows Server 2016 Datacenter by default, and only Windows-centric tools and workflows (PowerShell, IIS) are mentioned. There are no Linux equivalents or examples provided for certificate creation, backend server setup, or web server installation.
Recommendations
  • Provide equivalent Linux examples for all command-line operations, such as using OpenSSL for certificate creation and Bash/Azure CLI for resource management.
  • Include instructions for deploying a Linux-based VM scale set (e.g., Ubuntu) and installing a web server like Apache or Nginx.
  • Offer both PowerShell and Azure CLI/Bash script options for automation steps.
  • Mention Linux-compatible tools and patterns alongside Windows ones, and avoid assuming Windows as the default OS for backend servers.
  • Reorder examples or provide parallel instructions so that Linux options are presented with equal prominence.
GitHub Create Pull Request
Application Gateway Renew an Azure Application Gateway certificate ...ain/articles/application-gateway/renew-certificates.md
High Priority View Details →
Scanned: 2026-01-10 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 in the Azure portal, Azure PowerShell, and Azure CLI, but PowerShell is given a dedicated section and example before the CLI. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tooling or workflows. The CLI example is generic, but the overall structure and emphasis favor Windows/PowerShell users.
Recommendations
  • Add explicit bash shell examples for certificate renewal using Azure CLI, demonstrating usage on Linux/Mac systems.
  • Ensure CLI examples use cross-platform file paths and conventions, not Windows-specific ones.
  • Consider presenting Azure CLI instructions before PowerShell, as CLI is cross-platform.
  • Mention Linux certificate management tools or workflows where relevant.
  • Clarify that all CLI commands work on Linux, macOS, and Windows, and provide troubleshooting tips for non-Windows environments.
GitHub Create Pull Request
Application Gateway FAQ on V1 retirement ...ob/main/articles/application-gateway/retirement-faq.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell scripts for migration tasks, without mentioning or providing examples for Linux-friendly alternatives such as Azure CLI, Bash scripts, or ARM templates. There are no Linux or cross-platform command-line examples, and the only automation path described is via PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Provide equivalent Azure CLI (az) commands or scripts for all migration steps currently covered by PowerShell.
  • Explicitly mention that PowerShell Core is cross-platform, if PowerShell must be used, and provide installation guidance for Linux/macOS users.
  • Include Bash script examples or ARM/Bicep template alternatives for configuration and migration tasks.
  • Ensure that any referenced scripts or tooling are tested and documented for both Windows and Linux environments.
  • Add a section or note clarifying support for Linux/macOS users and recommend best practices for cross-platform automation.
GitHub Create Pull Request
Application Gateway Tutorial: Improve web application access - Azure Application Gateway .../articles/application-gateway/tutorial-autoscale-ps.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 Missing Linux Example Windows First
Summary
The documentation is heavily biased toward Windows and PowerShell usage. All examples and instructions rely exclusively on Azure PowerShell cmdlets and Windows-specific tools (e.g., New-SelfSignedCertificate, Export-PfxCertificate), with no mention of Bash, Azure CLI, or Linux/macOS alternatives. The certificate creation steps use Windows PowerShell modules and file paths (e.g., c:\appgwcert.pfx), and there is no guidance for users on Linux or macOS platforms. The prerequisites and workflow assume a Windows environment and do not offer parity for cross-platform users.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all steps, as Azure CLI is cross-platform and works on Linux/macOS.
  • Include instructions for creating self-signed certificates on Linux/macOS (e.g., using OpenSSL) and exporting to PFX format.
  • Use platform-neutral file paths in examples, or show both Windows and Linux/macOS paths.
  • Add a section or callout for Linux/macOS users, outlining any differences or additional steps required.
  • Where possible, link to cross-platform documentation or tools, and avoid assuming PowerShell is the only option.
GitHub Create Pull Request
Application Gateway Generate self-signed certificate with a custom root CA ...ticles/application-gateway/self-signed-certificates.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows and Windows-specific tools (IIS, PowerShell) are mentioned before or more prominently than their Linux equivalents. The PowerShell example for uploading the certificate to Application Gateway is provided, but no equivalent Azure CLI or Bash example is shown. IIS instructions are listed before Apache/NGINX, and references to Windows file paths (e.g., C:\Users\...) appear in code samples. While OpenSSL is used for certificate generation (which is cross-platform), the page overall favors Windows workflows and tools.
Recommendations
  • Add Azure CLI and Bash examples for uploading certificates to Application Gateway, alongside PowerShell.
  • Provide Linux file path examples in addition to Windows paths in code samples.
  • Present Apache and NGINX configuration instructions before or alongside IIS, or clarify that order does not indicate preference.
  • Include explicit instructions for managing trusted root certificates on Linux (e.g., update-ca-certificates), not just on Windows.
  • Ensure references to Windows-specific tools (like IIS and PowerShell) are balanced with Linux alternatives.
GitHub Create Pull Request
← Previous Page 7 of 40 Next →