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 501-525 of 981 flagged pages
Application Gateway Health monitoring overview for Azure Application Gateway ...lication-gateway/application-gateway-probe-overview.md
Medium Priority View Details →
Scanned: 2026-02-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page for Azure Application Gateway health monitoring provides conceptual information applicable to all platforms, but it demonstrates bias by exclusively using Azure PowerShell cmdlets for custom probe configuration examples and mentioning PowerShell as a primary method for advanced settings (e.g., MinServers). There are no Azure CLI or ARM template examples, and PowerShell is referenced before other methods. This creates friction for Linux/macOS users who may prefer or require cross-platform tools.
Recommendations
  • Add equivalent Azure CLI examples for custom probe configuration and health response matching.
  • Mention ARM template syntax for advanced settings such as MinServers.
  • Where possible, provide cross-platform guidance and clarify which methods are available on all OSes.
  • Ensure that references to PowerShell are balanced with Azure CLI or REST API options, especially in sections describing configuration steps.
GitHub Create Pull Request
Application Gateway Tutorial: Create and configure an application gateway to host multiple web sites using the Azure portal ...es/application-gateway/create-multiple-sites-portal.md
Medium Priority View Details →
Scanned: 2026-02-28 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The tutorial demonstrates notable Windows bias: it exclusively uses Windows Server VMs as backend targets, provides only PowerShell commands for IIS installation, and gives instructions for editing the hosts file and DNS cache using Windows-specific paths and tools. No Linux/macOS equivalents are mentioned, and Linux scenarios (e.g., using Apache/Nginx, Linux VMs, or Bash) are absent. Windows tools and patterns are referenced throughout, creating friction for Linux/macOS users.
Recommendations
  • Include Linux VM creation steps alongside Windows, e.g., Ubuntu or CentOS.
  • Provide Linux/macOS instructions for editing the hosts file (e.g., /etc/hosts), including appropriate commands for DNS cache flushing (e.g., 'sudo systemctl restart network-manager' or 'sudo dscacheutil -flushcache').
  • Offer Bash/Azure CLI alternatives for IIS installation, such as installing Apache or Nginx on Linux VMs.
  • Clarify that Application Gateway supports both Windows and Linux backend servers, and provide parity in examples.
  • Add notes or links for macOS users regarding hosts file editing and DNS cache management.
GitHub Create Pull Request
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-02-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is notably Windows-centric: it exclusively demonstrates deploying a SQL Server VM using a Windows Server image, and the SQL client connection example relies solely on SQL Server Management Studio (SSMS), a Windows-only tool. There are no examples or guidance for deploying a Linux-based SQL Server VM or for connecting using cross-platform SQL clients. This may create friction for Linux/macOS users wishing to follow the guide.
Recommendations
  • Add instructions for deploying a SQL Server on Linux VM (e.g., Ubuntu with SQL Server 2019/2022) as an alternative to the Windows-based deployment.
  • Include examples of connecting to the SQL Server backend using cross-platform tools such as Azure Data Studio, sqlcmd, or other open-source SQL clients.
  • Explicitly mention that the Application Gateway TCP/TLS proxy works with both Windows and Linux SQL Server backends, if applicable.
  • Where screenshots or steps are OS-specific, provide parallel guidance for Linux/macOS users or clarify any 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-02-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page for Azure Application Gateway v2 shows moderate Windows bias. Migration instructions and tutorials are focused on Azure PowerShell scripts, with no mention of Azure CLI or ARM templates for Linux/macOS users. The 'Next steps' section links only to a PowerShell-based tutorial, and the migration script is described as a PowerShell Gallery resource. While the Azure CLI is referenced for preview registration, the commands shown are actually PowerShell cmdlets, not true Azure CLI commands. There are no Linux/macOS-specific examples or parity guidance.
Recommendations
  • Add Azure CLI and/or ARM template examples for migration and deployment tasks, especially in the 'Migrate from v1 to v2' and 'Next steps' sections.
  • Ensure that registration/unregistration instructions use actual Azure CLI syntax, not PowerShell cmdlets.
  • Provide links to tutorials or guides that use cross-platform tools (Azure CLI, Bicep, ARM templates) for creating and managing Application Gateway v2.
  • Explicitly mention that PowerShell instructions are Windows-centric and offer alternatives for Linux/macOS users.
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-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides configuration examples for mutual authentication on Azure Application Gateway with a strong emphasis on PowerShell, listing PowerShell instructions and references first, followed by Azure CLI. There are no explicit Linux/macOS-specific examples (e.g., Bash scripting, OpenSSL usage), and the 'Next steps' section directs users to a PowerShell-focused guide, potentially creating friction for Linux/macOS users.
Recommendations
  • Provide Linux/macOS-friendly examples, such as Bash/Cloud Shell commands, especially for certificate extraction and management.
  • Ensure CLI examples are as detailed as PowerShell ones, and consider listing Azure CLI before PowerShell to avoid a 'Windows-first' impression.
  • Add references or links to cross-platform tools (e.g., OpenSSL) for certificate manipulation.
  • Include a 'Next steps' link to an Azure CLI or ARM/Bicep template guide, not just PowerShell.
GitHub Create Pull Request
Application Gateway Diagnostic logs ...application-gateway/application-gateway-diagnostics.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a PowerShell-only example for enabling diagnostic logging, with no equivalent CLI (az), Bash, or ARM template example. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer cross-platform tools. The only automation example is Windows-centric, and the log conversion tool is referenced as a C#/.NET solution, which is also more common in Windows environments.
Recommendations
  • Add equivalent examples using Azure CLI (az) for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention or provide ARM/Bicep template snippets for enabling diagnostic logging for users who prefer infrastructure-as-code approaches.
  • If referencing log conversion tools, also mention cross-platform alternatives (e.g., Python scripts, jq for JSON processing) or clarify that the .NET tool can be run on Linux/macOS with .NET Core.
  • When showing automation examples, present Azure CLI first or alongside PowerShell to avoid Windows-first bias.
GitHub Create Pull Request
Application Gateway Health monitoring overview for Azure Application Gateway ...lication-gateway/application-gateway-probe-overview.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides PowerShell-centric examples and references, particularly for configuring advanced probe features (e.g., MinServers, probe match criteria). It mentions PowerShell cmdlets and operators exclusively for custom probe configuration, without equivalent Azure CLI or ARM template examples. Additionally, PowerShell is referenced before other methods in the 'Next steps' section, suggesting a Windows-first approach.
Recommendations
  • Add Azure CLI and ARM template examples for custom probe configuration, especially for features like MinServers and probe match criteria.
  • Explicitly mention that these configurations can be performed on Linux/macOS using Azure CLI or ARM templates, not just PowerShell.
  • Provide CLI syntax alongside PowerShell in all code example sections.
  • In the 'Next steps' section, list Azure CLI and ARM template options before or alongside PowerShell to avoid Windows-first ordering.
GitHub Create Pull Request
Application Gateway Azure Application Gateway Backend Settings configuration ...les/application-gateway/configuration-http-settings.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is generally platform-neutral, focusing on Azure Application Gateway configuration concepts. However, there are two notable instances of Windows bias: (1) troubleshooting guidance for Dedicated Backend Connections references Windows Authentication and Kerberos documentation, specifically linking to IIS and Windows authentication configuration; (2) Windows tools and terminology (e.g., Service Principal Name, IIS, Windows Authentication) are mentioned before any Linux equivalents, with no Linux-specific troubleshooting or guidance provided for backend authentication scenarios.
Recommendations
  • Add troubleshooting guidance for Linux-based backend servers, such as Apache, NGINX, or other common Linux web servers, including links to relevant documentation for configuring Kerberos/NTLM or other authentication mechanisms on Linux.
  • When referencing authentication protocols, clarify that NTLM and Kerberos are supported on both Windows and Linux, and provide links to Linux-focused resources (e.g., mod_auth_kerb for Apache, GSSAPI for NGINX).
  • Include examples or notes for Linux backend log analysis and configuration, not just Windows/IIS.
  • Ensure that troubleshooting steps and best practices are presented in a platform-neutral way, or with parity between Windows and Linux guidance.
GitHub Create Pull Request
Application Gateway Azure Application Gateway listener configuration ...rticles/application-gateway/configuration-listeners.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
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 on Application Gateway listeners, with no equivalent example for Azure CLI, Bash, or ARM/Bicep. This creates friction for Linux/macOS users who may not use PowerShell.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all configuration snippets, especially for enabling HTTP/2 support.
  • Where possible, provide ARM template or Bicep examples for infrastructure-as-code users.
  • Explicitly mention that all features are available via Azure CLI and portal, and link to relevant CLI documentation.
  • Consider including Bash shell examples or guidance for cross-platform users.
GitHub Create Pull Request
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-02-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively demonstrates configuring Azure Application Gateway TCP/TLS proxy with a SQL Server VM running Windows Server. All examples and screenshots reference Windows-based SQL Server deployments, and the client connection instructions assume the use of SQL Server Management Studio (SSMS), a Windows-only tool. There are no examples or guidance for deploying SQL Server on Linux, connecting from Linux/macOS clients, or using cross-platform SQL tools.
Recommendations
  • Add instructions and examples for deploying SQL Server on Linux (e.g., Ubuntu) as a backend VM.
  • Include guidance for connecting to the SQL Server via Azure Application Gateway from Linux/macOS clients, using cross-platform tools such as sqlcmd, Azure Data Studio, or other open-source SQL clients.
  • Mention alternative client tools and provide sample connection commands for Linux/macOS environments.
  • Clarify that the procedure is also applicable to SQL Server on Linux, unless there are Azure-specific limitations.
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-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides PowerShell-centric examples and instructions for integrating Azure Application Gateway with Key Vault certificates. While Azure CLI is mentioned, all detailed command-line examples are exclusively in PowerShell, and PowerShell is referenced before CLI or ARM/Bicep in several places. There are no explicit Linux/macOS CLI examples or guidance, and the 'Next steps' section links only to a PowerShell guide.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell command sequences, especially for certificate referencing and managed identity configuration.
  • Include explicit guidance or links for Linux/macOS users, clarifying how to perform tasks using Azure CLI or Bicep.
  • Ensure 'Next steps' includes links to CLI and ARM/Bicep documentation, not just PowerShell.
  • Where PowerShell is referenced, mention that Azure CLI is cross-platform and provide parity in instructions.
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-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation for migrating Azure Application Gateway from V1 to V2 is heavily focused on Azure PowerShell scripts and cmdlets, with all examples, instructions, and tooling centered around PowerShell. There are no references to Azure CLI, Bash, or Linux-native tooling, nor are there examples or guidance for users on Linux or macOS platforms. The script installation and execution instructions assume a Windows/PowerShell environment, which creates friction for Linux/macOS users.
Recommendations
  • Provide equivalent Azure CLI (az) commands and scripts for configuration and traffic migration, alongside PowerShell examples.
  • Add explicit guidance for Linux/macOS users, including how to run PowerShell Core (pwsh) cross-platform, or alternative approaches using Azure CLI.
  • Mention and link to Azure Cloud Shell as a cross-platform option, clarifying that both PowerShell and Bash are available.
  • Where possible, offer Bash script examples or instructions for downloading and running migration scripts from Linux/macOS.
  • Clarify prerequisites for Linux/macOS users, such as installing PowerShell Core or using Azure CLI.
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-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation provides only Windows Server VM examples and uses PowerShell commands for backend setup (IIS installation), with no Linux VM or Linux web server (e.g., Apache, Nginx) examples. The IIS installation is performed via PowerShell, and there are no equivalent instructions for Linux-based VMs or web servers. The documentation also refers to Windows Server as the default VM type in the backend pool creation steps.
Recommendations
  • Add parallel instructions for creating a Linux VM (e.g., Ubuntu) as a backend server.
  • Provide examples for installing a Linux web server (such as Apache or Nginx) using Bash/SSH or Azure CLI.
  • Show how to test the application gateway with a Linux backend (e.g., by browsing to the public IP and seeing the Apache/Nginx default page).
  • Include both Windows and Linux options in backend pool setup, making clear that Application Gateway supports both.
  • If using PowerShell for Windows, provide Bash/SSH/CLI equivalents for Linux.
  • Consider showing both Windows and Linux VM creation steps side-by-side or in separate sections.
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-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides configuration examples for mutual authentication on Azure Application Gateway using PowerShell and Azure CLI, with PowerShell examples and references consistently shown first. There are no explicit Linux/macOS-specific examples or guidance, and the 'Next steps' section directs users to a PowerShell-focused guide, potentially leaving Linux users with less clear guidance.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
  • Include explicit notes or links for Linux/macOS users, especially in sections where PowerShell is referenced, clarifying that Azure CLI provides equivalent functionality.
  • In the 'Next steps' section, add a link to a CLI-based mutual authentication configuration guide, or create such a guide if it does not exist.
  • Wherever possible, ensure that all configuration steps are documented for both Azure CLI and PowerShell, and clarify any platform-specific limitations.
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-02-26 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 is heavily focused on Azure PowerShell scripts and cmdlets for migration, with all examples, instructions, and tooling based on PowerShell. There are no Bash, Azure CLI, or Linux/macOS shell equivalents provided. Installation and execution instructions assume a Windows/PowerShell environment, and PowerShell Gallery is the only script distribution method mentioned. This creates friction for Linux/macOS users who prefer Azure CLI or Bash scripting, and may not have PowerShell installed or configured.
Recommendations
  • Provide Azure CLI equivalents for migration steps, or clearly state if PowerShell is required and offer guidance for Linux/macOS users to install PowerShell Core.
  • Add Bash script examples or instructions for Linux/macOS environments.
  • Mention cross-platform compatibility of PowerShell Core and clarify if scripts work on Linux/macOS, including any prerequisites.
  • Include guidance for running PowerShell scripts in Azure Cloud Shell (which is cross-platform), and highlight this option for non-Windows users.
  • If PowerShell is the only supported method, explicitly state this limitation and provide links to PowerShell Core installation guides for Linux/macOS.
GitHub Create Pull Request
Application Gateway Diagnostic logs ...application-gateway/application-gateway-diagnostics.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a detailed PowerShell example for enabling diagnostic logging but does not offer equivalent CLI/Bash or Azure CLI examples. The only programmatic example is PowerShell, which is Windows-centric. References to data analysis tools focus on Excel and Visual Studio/C#, which are primarily Windows tools, with no mention of Linux/macOS-friendly alternatives. This creates friction for Linux/macOS users who may prefer or require Azure CLI, Bash, or cross-platform tools.
Recommendations
  • Add equivalent Azure CLI (az) commands for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash or shell script examples where appropriate.
  • When mentioning data analysis tools, include Linux/macOS-compatible options (e.g., jq for JSON processing, pandas in Python, or open-source log viewers).
  • Reference Visual Studio Code (cross-platform) instead of or in addition to Visual Studio.
  • Explicitly state that PowerShell Core is available cross-platform if PowerShell is to be used, and provide installation guidance or alternatives.
GitHub Create Pull Request
Application Gateway Health monitoring overview for Azure Application Gateway ...lication-gateway/application-gateway-probe-overview.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page for Azure Application Gateway health monitoring provides configuration examples and instructions primarily using Azure PowerShell cmdlets, such as New-AzApplicationGatewayProbeHealthResponseMatch, and references PowerShell as the main CLI for advanced probe configuration. There is no equivalent Azure CLI (Linux/macOS-friendly) example or mention, and PowerShell is presented as the default scripting interface for probe customization. Additionally, the 'MinServers' property is noted as only configurable via PowerShell, Azure CLI, or ARM templates, but only PowerShell examples are shown, and PowerShell is mentioned first.
Recommendations
  • Add equivalent Azure CLI examples for probe configuration and matching criteria, especially for tasks shown with PowerShell (e.g., probe health response match).
  • Explicitly mention that all configuration tasks can be performed using Azure CLI or ARM templates, not just PowerShell.
  • Provide links or references to Azure CLI documentation for Application Gateway probe management.
  • Consider showing Azure CLI examples before or alongside PowerShell examples to improve parity.
  • Clarify that PowerShell is cross-platform, but highlight Azure CLI as a Linux/macOS-friendly option.
GitHub Create Pull Request
Application Gateway Azure Application Gateway listener configuration ...rticles/application-gateway/configuration-listeners.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
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 on an Application Gateway listener, without offering equivalent Azure CLI, ARM template, or REST API examples that are platform-agnostic or Linux/macOS-friendly. No Windows-specific tools or patterns are otherwise emphasized, but the lack of cross-platform command examples introduces friction for non-Windows users.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all configuration snippets, especially for enabling HTTP/2 support.
  • Where possible, provide ARM template or REST API examples for tasks that can be automated, ensuring parity for users on all platforms.
  • Explicitly mention that all operations can be performed via the Azure portal, Azure CLI, PowerShell, and REST API, with links to relevant documentation.
  • If PowerShell is shown first, consider showing Azure CLI first or side-by-side to avoid implicit Windows-first bias.
GitHub Create Pull Request
Application Gateway Azure Application Gateway Backend Settings configuration ...les/application-gateway/configuration-http-settings.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is generally platform-neutral, focusing on Azure Application Gateway backend settings. However, in the troubleshooting section for Dedicated Backend Connections, Windows-specific authentication protocols (NTLM, Kerberos) and links to Windows/IIS documentation are referenced first and exclusively. There are no equivalent Linux authentication examples or links, and the troubleshooting guidance is tailored to Windows environments. Additionally, references to backend logs and authentication are Windows-centric, with no mention of Linux alternatives.
Recommendations
  • Add troubleshooting guidance for Linux-based backend servers, including common authentication mechanisms (such as LDAP, OAuth, or Kerberos on Linux).
  • Provide links to Linux documentation for Kerberos authentication and web server log analysis (e.g., Apache, NGINX).
  • Clarify that NTLM and Windows Authentication are Windows-specific, and offer alternative guidance for Linux users.
  • Include examples or notes for Linux-based backend applications where relevant.
GitHub Create Pull Request
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-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily demonstrates the configuration of Azure Application Gateway TCP/TLS proxy using a SQL Server VM running Windows Server. All examples and screenshots reference Windows-based SQL Server and SQL Server Management Studio (SSMS), which is a Windows-only tool. There are no examples or guidance for Linux-based SQL Server VMs or Linux/macOS-compatible SQL clients, and Windows patterns are presented exclusively and first.
Recommendations
  • Add instructions and screenshots for deploying SQL Server on a Linux VM in Azure, or clarify that Linux is supported.
  • Include examples of connecting to the SQL Server backend using cross-platform SQL clients such as Azure Data Studio, sqlcmd, or other Linux/macOS-compatible tools.
  • Mention any differences or considerations when using Linux-based SQL Server as a backend for Application Gateway.
  • Explicitly state if the procedure is equally applicable to Linux SQL Server VMs, or clarify any 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-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page for Azure Application Gateway v2 shows moderate Windows bias. Migration instructions and registration/unregistration examples are provided exclusively using Azure PowerShell commands, with no equivalent Bash or Linux CLI examples. Additionally, the 'Next steps' section links to a PowerShell tutorial first, suggesting Windows-centric workflows. No Linux/macOS-specific guidance or parity is offered for these tasks.
Recommendations
  • Add Azure CLI (bash) examples alongside PowerShell for migration, registration, and unregistration tasks.
  • Ensure tutorials and quickstarts are available and linked for both PowerShell and Azure CLI users.
  • Explicitly mention that all commands can be run cross-platform if true, or clarify any Windows-only requirements.
  • Consider linking to Linux/macOS-specific guidance where relevant.
GitHub Create Pull Request
Application Gateway FAQ on V1 retirement ...ob/main/articles/application-gateway/retirement-faq.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation repeatedly references an Azure PowerShell script as the primary or sole migration tool, with no mention of Azure CLI, Bash, or cross-platform alternatives. There are no Linux/macOS-specific migration instructions or examples, and the PowerShell script is referenced as the main automation method for migration and public IP retention. This creates friction for users on Linux/macOS who may not have PowerShell installed or prefer native tools.
Recommendations
  • Provide Azure CLI (az) equivalents for migration steps and scripts, or explicitly state if such alternatives are not available.
  • Clarify whether the PowerShell script can be run cross-platform (e.g., via PowerShell Core on Linux/macOS), and provide installation guidance if so.
  • Add Bash or shell script examples for common migration tasks, or reference any available cross-platform tools.
  • Explicitly note any Windows-only requirements for the migration scripts, so Linux/macOS users can plan accordingly.
GitHub Create Pull Request
Application Gateway Tutorial: Improve web application access - Azure Application Gateway .../articles/application-gateway/tutorial-autoscale-ps.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The tutorial exclusively uses Azure PowerShell and Windows PowerShell cmdlets for all steps, including certificate creation, resource management, and cleanup. Windows-specific tools (e.g., New-SelfSignedCertificate, Export-PfxCertificate) are used without mention of Linux/macOS alternatives. No Bash, Azure CLI, or cross-platform scripting examples are provided, and instructions assume a Windows environment (e.g., certificate store paths, file paths).
Recommendations
  • Add Azure CLI (az) examples for each step alongside PowerShell, as Azure CLI is cross-platform.
  • For certificate creation, provide Linux/macOS alternatives (e.g., using OpenSSL) and explain how to export/import certificates.
  • Clarify which steps are Windows-specific and offer guidance for Linux/macOS users where possible.
  • Use generic file paths or note differences for Windows vs. Linux/macOS.
  • Mention that Azure PowerShell can be used in Cloud Shell (which is cross-platform) and provide instructions for Cloud Shell usage.
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-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for 'TLS termination with Azure Key Vault certificates' demonstrates a notable Windows/PowerShell bias. PowerShell is the only command-line example provided for configuring Application Gateway with Key Vault using RBAC, with no equivalent Azure CLI (cross-platform) or Bash examples. The documentation references PowerShell steps and links to a PowerShell-specific guide in the 'Next steps' section, while Linux/macOS users are left to infer or adapt the process themselves. Although Azure CLI is mentioned as a supported tool, no CLI or Linux-native examples are shown.
Recommendations
  • Provide Azure CLI (az) command-line examples alongside PowerShell for all configuration steps, especially for referencing Key Vault secrets and configuring Application Gateway.
  • Where PowerShell is referenced, add equivalent Bash/CLI snippets or clearly indicate cross-platform alternatives.
  • In the 'Next steps' section, link to both PowerShell and Azure CLI guides, or create CLI documentation if it does not exist.
  • Ensure that screenshots and UI instructions are platform-neutral or clarify when a step is platform-specific.
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-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references the PFXImportCertStore function from the Windows API when describing supported certificate formats, and links 'Next steps' to a PowerShell-based configuration guide. There are no explicit Linux/macOS CLI examples or references to Linux-native certificate tooling, and Windows/PowerShell tools are mentioned first or exclusively in actionable sections.
Recommendations
  • When referencing certificate formats, provide Linux/macOS equivalents (e.g., OpenSSL commands for creating and converting certificates to PFX).
  • In 'Next steps', include links to Azure CLI, Azure Portal, or ARM template guides for configuring end-to-end TLS, not just PowerShell.
  • Where Windows-specific APIs or tools are mentioned, add notes or links for cross-platform alternatives.
  • Consider including example commands or workflows for Linux/macOS users, especially for certificate preparation and gateway configuration.
GitHub Create Pull Request
← Previous Page 21 of 40 Next →