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 526-550 of 981 flagged pages
Application Gateway Configure Azure Application Gateway TCP/TLS proxy ...n/articles/application-gateway/how-to-tcp-tls-proxy.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently uses Windows-based SQL Server VM examples and references SQL Server Management Studio (SSMS), a Windows-only tool, for client connectivity. No Linux or macOS alternatives (such as SQL Server on Linux, Azure SQL Edge, or cross-platform SQL clients like sqlcmd or Azure Data Studio) are mentioned. The instructions for creating the SQL Server VM default to Windows Server, and client connection steps assume a Windows environment.
Recommendations
  • Include instructions for deploying SQL Server on Linux (supported on Azure VMs) or mention Azure SQL Edge for cross-platform scenarios.
  • Provide examples of connecting to the SQL Server backend using cross-platform tools such as sqlcmd (available on Linux/macOS), Azure Data Studio, or other open-source SQL clients.
  • Clarify that the Application Gateway TCP/TLS proxy feature works for SQL Server workloads on both Windows and Linux, if applicable.
  • Add screenshots or command-line examples for Linux/macOS users where relevant.
  • Mention any limitations or differences for Linux-based SQL Server deployments if they exist.
GitHub Create Pull Request
Application Gateway Scaling and Zone-redundant Application Gateway v2 ...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page is generally platform-neutral in its conceptual explanations, but in the 'Next steps' section, the only hands-on tutorial linked is for Azure PowerShell, which is Windows-centric and often prioritized for Windows users. There are no equivalent Linux/CLI examples or links provided, and PowerShell is mentioned before any Linux-friendly alternatives.
Recommendations
  • Add links to Azure CLI tutorials for creating autoscaling, zone-redundant Application Gateways, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Ensure that both PowerShell and CLI examples are provided in future tutorials and reference material.
  • Explicitly mention that Azure CLI can be used for these operations and provide guidance or links for Linux/macOS users.
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-25 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 concepts and settings. However, there are two notable instances of Windows bias: (1) troubleshooting guidance for Dedicated Backend Connections references Windows Authentication and Kerberos documentation, and (2) backend server log review is linked to IIS (Windows) configuration. These references appear before any mention of Linux equivalents, and no Linux-specific troubleshooting or authentication guidance is provided.
Recommendations
  • Add troubleshooting guidance for Linux-based backend servers, including links to relevant documentation for Apache, Nginx, or other common Linux web servers.
  • Include examples or references for configuring authentication (such as Kerberos or NTLM) on Linux backends, or clarify if these features are Windows-only.
  • When discussing backend server logs, mention both Windows (IIS) and Linux (Apache/Nginx) log locations and interpretation.
  • Ensure that links and guidance for backend authentication and logging are platform-inclusive, or explicitly state if a feature is Windows-specific.
GitHub Create Pull Request
Application Gateway Azure Application Gateway listener configuration ...rticles/application-gateway/configuration-listeners.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell example for enabling HTTP/2 support but does not offer equivalent examples for Azure CLI, ARM templates, or REST API, which are cross-platform and commonly used on Linux/macOS. There is no mention of Linux-specific tools or guidance, and the only code snippet is Windows/PowerShell-centric.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all configuration tasks, especially for enabling HTTP/2 support.
  • Include ARM template and REST API examples where relevant, as these are platform-agnostic.
  • Explicitly state that all features are available and manageable from Linux/macOS using Azure CLI or portal.
  • Consider reordering or grouping examples so that cross-platform tools (CLI, REST, ARM) are presented before or alongside PowerShell.
GitHub Create Pull Request
Application Gateway Diagnostic logs ...application-gateway/application-gateway-diagnostics.md
Medium Priority View Details →
Scanned: 2026-02-25 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 provides a PowerShell-only example for enabling diagnostic logging, with no equivalent Azure CLI, Bash, or ARM template examples. PowerShell is presented as the primary scripting interface, which is more familiar to Windows users. There are also references to viewing logs in Excel and Visual Studio-based tools, which are Windows-centric. No Linux/macOS-specific instructions or parity examples are provided.
Recommendations
  • Add equivalent Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash or shell script examples where relevant.
  • Mention or demonstrate how to view and process logs using Linux/macOS tools (e.g., jq, grep, awk) in addition to Excel and Power BI.
  • Reference cross-platform editors (e.g., VS Code) instead of or alongside Visual Studio.
  • Ensure that any downloadable tools or scripts are compatible with Linux/macOS, or clearly state platform requirements.
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-25 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 PowerShell-centric examples and references, particularly for custom probe configuration and advanced features (e.g., MinServers and probe match criteria). PowerShell cmdlets are used for illustrating probe matching, and the MinServers property is noted as only configurable via PowerShell, Azure CLI, or ARM templates, but the example and guidance focus on PowerShell. Linux equivalents (Azure CLI) are mentioned but not demonstrated, and PowerShell is presented first and most prominently.
Recommendations
  • Add Azure CLI examples alongside PowerShell for configuring custom probes, probe match criteria, and MinServers.
  • Explicitly state that all features can be managed via Azure CLI and ARM templates, and provide links or examples for Linux/macOS users.
  • Where PowerShell is used for illustration, add equivalent CLI syntax and highlight cross-platform options.
  • Consider showing CLI examples before or alongside PowerShell to avoid Windows-first impression.
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-25 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 exhibits moderate Windows bias. Migration and registration/unregistration instructions are provided exclusively using Azure PowerShell commands, with no equivalent Bash or Linux CLI examples. Additionally, the 'Next steps' section links to a PowerShell-based tutorial as the primary onboarding path, rather than offering parity with Bash or cross-platform CLI options. While the core concepts and features are platform-neutral, the operational guidance favors Windows/PowerShell users.
Recommendations
  • Provide Azure CLI (bash) examples alongside PowerShell for migration, registration, and unregistration tasks.
  • Add links to tutorials using Azure CLI or ARM templates for Linux/macOS users in the 'Next steps' section.
  • Clarify that both PowerShell and Azure CLI can be used for management, and offer guidance for cross-platform users.
  • Consider including a note about cross-platform compatibility for all scripts and commands.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page for 'TLS termination with Azure Key Vault certificates' demonstrates a moderate Windows/PowerShell bias. While the conceptual information is cross-platform, the only detailed command-line example for configuring Key Vault integration with Application Gateway uses Azure PowerShell, with no equivalent Azure CLI (cross-platform) or Bicep/ARM template example. The documentation also refers to PowerShell steps and links to a PowerShell-specific next step, with no parallel guidance for Linux/macOS users who may prefer Azure CLI or other tools.
Recommendations
  • Add equivalent Azure CLI examples alongside PowerShell for all command-line configuration steps, especially for referencing Key Vault secrets and configuring Application Gateway.
  • Where PowerShell is referenced, also mention and link to ARM/Bicep/CLI documentation if available.
  • In the 'Next steps' section, provide links to CLI and ARM/Bicep guides in addition to PowerShell.
  • When mentioning command-line tools, avoid implying PowerShell is the primary or only supported method.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for configuring client certificate revocation, but PowerShell is presented first and in more detail, with CLI examples being minimal. There are no explicit Linux/macOS-specific instructions or examples for certificate extraction or management, and the 'Next steps' section points only to a PowerShell-based guide. The documentation does not mention Linux-native tools (e.g., OpenSSL) for certificate handling, nor does it provide parity in step-by-step examples for Linux users.
Recommendations
  • Add Linux/macOS-focused examples for certificate extraction and management, such as using OpenSSL commands to extract and prepare certificate chains.
  • Ensure CLI examples are as detailed as PowerShell examples, including all relevant steps and explanations.
  • In the 'Next steps' section, provide links to both PowerShell and Azure CLI (and, if possible, ARM/Bicep template) guides for mutual authentication configuration.
  • When referencing tools or commands, mention cross-platform alternatives and clarify that Azure CLI is available on all major platforms.
  • Consider reordering sections so that CLI and cross-platform methods are presented before or alongside PowerShell examples.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation references the Windows-specific PFXImportCertStore function for PFX certificate requirements and links the next steps to a PowerShell-based configuration guide, without providing Linux/macOS equivalents or cross-platform alternatives. No Linux or OpenSSL-based certificate creation/import guidance is present, and Windows tooling is mentioned first and exclusively.
Recommendations
  • Add guidance or links for creating and managing PFX certificates using OpenSSL (cross-platform) or Linux/macOS tools, not just referencing Windows APIs.
  • In the 'Next steps' section, provide links to CLI (az CLI), ARM template, or Portal-based configuration guides in addition to or before PowerShell.
  • Where Windows-specific APIs or tools are referenced (e.g., PFXImportCertStore), clarify that this is a Windows API and provide equivalent cross-platform instructions or references.
  • Ensure that examples and walkthroughs are available for Linux/macOS users, especially for certificate preparation and Application Gateway configuration.
GitHub Create Pull Request
Application Gateway Scaling and Zone-redundant Application Gateway v2 ...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides a PowerShell-based tutorial link for creating an autoscaling, zone-redundant Application Gateway, without offering equivalent Linux/macOS CLI or ARM template examples. The PowerShell example is listed as the only explicit 'how-to' in the 'Next steps' section, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI and/or ARM template tutorials for creating autoscaling, zone-redundant Application Gateway.
  • List Azure CLI and PowerShell options side-by-side in the 'Next steps' section to ensure parity.
  • Explicitly mention that PowerShell is available cross-platform, but also provide native CLI examples for Linux/macOS users.
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-23 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 a conceptual overview of end-to-end TLS on Azure Application Gateway. While the main content is platform-neutral, the 'Next steps' section exclusively links to a PowerShell-based configuration guide, implying Windows-centric tooling. No Linux or cross-platform CLI (Azure CLI, Bash) configuration examples or links are provided, and Windows-specific certificate formats (PFX) are referenced with links to Windows API documentation before mentioning cross-platform alternatives.
Recommendations
  • Add links to equivalent Azure CLI or Bash-based configuration guides for end-to-end TLS setup.
  • Include examples or references for certificate creation and management using cross-platform tools (e.g., OpenSSL) instead of only referencing Windows PFX and Wincrypt APIs.
  • Ensure that Linux/macOS users are provided with parity in guidance for configuring Application Gateway, including certificate preparation and upload.
  • In the 'Next steps' section, offer multiple options (PowerShell, Azure CLI, ARM templates) for configuration, not just 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-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page repeatedly references Azure PowerShell scripts as the primary migration tool, without mentioning or providing equivalent CLI (az CLI) or Linux/macOS-friendly alternatives. All migration automation examples and recommendations are PowerShell-centric, and there is no guidance for users on non-Windows platforms. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Provide az CLI (Azure Command-Line Interface) examples and scripts for migration tasks alongside PowerShell scripts.
  • Explicitly mention that PowerShell Core is cross-platform, and provide instructions for installing and running migration scripts on Linux/macOS.
  • Add guidance or links for Linux/macOS users to alternative migration approaches or tools.
  • Ensure that all script references clarify platform compatibility and offer parity for non-Windows environments.
GitHub Create Pull Request
Application Gateway Diagnostic logs ...application-gateway/application-gateway-diagnostics.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides explicit instructions for enabling diagnostic logging via PowerShell, but does not offer equivalent CLI or Bash examples for Linux/macOS users. The only command-line example is a PowerShell cmdlet, and references to log conversion tools are tied to Visual Studio and C#, which are Windows-centric. There is no mention of Azure CLI or Bash scripting, nor are Linux/macOS-friendly tools or workflows discussed.
Recommendations
  • Add Azure CLI examples for enabling diagnostic logging, alongside the PowerShell example.
  • Mention Bash scripting or cross-platform approaches for log management.
  • Reference log conversion tools that do not require Visual Studio or C#, or provide alternatives for Linux/macOS users.
  • Ensure that instructions for viewing and analyzing logs include cross-platform tools (e.g., jq, csvkit, Python scripts) in addition to Excel and Power BI.
  • Where possible, present Windows and Linux/macOS methods side-by-side, or clarify that PowerShell can be used on Linux/macOS if relevant.
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-23 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 4xx Errors with Dedicated Backend Connections' section, Windows authentication mechanisms (NTLM and Kerberos) and IIS configuration are referenced, with links to Windows and IIS documentation. These references appear before any mention of Linux equivalents or alternatives, and no Linux authentication guidance is provided. Additionally, the troubleshooting guidance is Windows-centric, potentially creating friction for Linux users.
Recommendations
  • Add troubleshooting guidance for Linux-based backend servers, such as Apache, NGINX, or other common Linux web servers.
  • Include links to documentation for configuring authentication (e.g., Kerberos) on Linux backends.
  • Clarify that NTLM and IIS are Windows-specific and provide alternative authentication mechanisms for Linux environments.
  • Ensure examples and troubleshooting steps are balanced between Windows and Linux backend scenarios.
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-23 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 instructions for mutual authentication on Azure Application Gateway. While the feature itself is cross-platform, the documentation exhibits Windows bias by prioritizing PowerShell examples and references, mentioning PowerShell before Azure CLI, and linking to a PowerShell-specific 'Next steps' guide. Azure CLI examples are present but less detailed, and there are no explicit Linux/macOS-specific guidance or examples. Portal support is noted as unavailable, but no Linux-native tools or workflows are discussed.
Recommendations
  • Provide equally detailed Azure CLI examples alongside PowerShell, including step-by-step CLI workflows.
  • Link to both PowerShell and Azure CLI guides in the 'Next steps' section, or create a Linux/macOS-focused configuration guide.
  • Explicitly mention that all CLI commands are cross-platform and can be run on Linux/macOS.
  • Add notes or examples for certificate extraction and management using Linux-native tools (e.g., openssl) where relevant.
  • Ensure that references to PowerShell do not precede CLI or are presented in parallel, to avoid Windows-first impression.
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-23 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 notable Windows bias. It exclusively uses Windows Server as the backend SQL VM example and references SQL Server Management Studio (SSMS), a Windows-only client, for connectivity testing. No Linux or cross-platform alternatives (such as SQL Server on Linux, Azure Data Studio, or command-line tools) are mentioned. All screenshots and instructions assume Windows environments, and Linux users are not provided with equivalent guidance.
Recommendations
  • Include instructions and examples for deploying SQL Server on Linux (supported by Azure SQL VM images).
  • Provide alternative client connection methods, such as using Azure Data Studio (cross-platform) or sqlcmd (available on Linux/macOS).
  • Add notes or sections for Linux/macOS users, including screenshots and step-by-step guidance.
  • Mention that SSMS is Windows-only and suggest cross-platform tools for non-Windows users.
  • Ensure backend pool configuration examples reference both Windows and Linux SQL Server VMs.
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-23 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 Azure PowerShell scripts and cmdlets for all migration steps, with no mention of Azure CLI, Bash, or cross-platform alternatives. All code examples, installation instructions, and operational guidance assume the use of PowerShell, which is traditionally associated with Windows environments. There is no guidance for Linux/macOS users, and no CLI or REST API equivalents are provided. This creates friction for users on non-Windows platforms and may prevent them from easily completing the migration.
Recommendations
  • Provide equivalent Azure CLI (az) commands and scripts for all major migration steps, including configuration cloning and public IP retention.
  • Explicitly state whether the provided PowerShell scripts are compatible with PowerShell Core on Linux/macOS, and provide installation/setup instructions for those platforms.
  • Include Bash or shell script examples where possible, or at least reference how Linux/macOS users can perform the same tasks.
  • Add a section or callout for Linux/macOS users, summarizing their options and any platform-specific caveats.
  • If certain steps are only possible with PowerShell, clarify this and provide guidance on using Azure Cloud Shell (which is cross-platform) as an alternative.
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-23 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 exhibits moderate Windows bias, primarily through the use of Azure PowerShell and Azure CLI examples that utilize PowerShell syntax. The migration script is only mentioned as available via PowerShell, and the 'Next steps' tutorial links to a PowerShell-based guide. There are no explicit Linux/bash examples or references to cross-platform CLI usage, and PowerShell is presented as the default scripting environment. However, the core content and features described are platform-agnostic, and Linux users can generally use Azure CLI or ARM templates for equivalent tasks.
Recommendations
  • Provide Azure CLI examples using bash syntax alongside PowerShell examples, especially for registration and migration tasks.
  • Clarify that Azure CLI commands can be run on Linux/macOS and provide explicit bash examples.
  • Link to tutorials or migration guides that use Azure CLI in bash or ARM templates, not just PowerShell.
  • Mention that the migration script may require PowerShell and suggest alternatives for Linux/macOS users if available.
  • Ensure 'Next steps' includes cross-platform options, not only PowerShell-based tutorials.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page presents Azure PowerShell examples first and in greater detail, with CLI examples following but less emphasized. References to PowerShell commands and links are more prominent, and the 'Next steps' section directs users to a PowerShell-specific guide. There are no explicit Linux/macOS-specific examples or guidance, and the use of PowerShell is implicitly prioritized, which may create friction for Linux/macOS users who prefer Azure CLI or other tools.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, ensuring equal detail and clarity.
  • Add explicit guidance for Linux/macOS users, including notes about CLI usage and any platform-specific considerations.
  • In the 'Next steps' section, include links to CLI-based configuration guides or ARM/Bicep template guides, not just PowerShell.
  • Where possible, clarify that PowerShell is not required and that all configuration steps can be performed with Azure CLI or REST API.
  • Ensure all referenced tools and commands are cross-platform, and avoid implying PowerShell is the default or preferred method.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page on Application Gateway V1 retirement and migration to V2 repeatedly references Azure PowerShell scripts as the primary migration tooling, without mentioning Azure CLI or Bash alternatives. PowerShell is a Windows-centric tool, and its exclusive mention creates friction for Linux/macOS users. There are no Linux/macOS-specific examples or guidance, and PowerShell is presented as the default solution for migration tasks.
Recommendations
  • Add Azure CLI examples or scripts for migration tasks, especially for configuration and public IP retention.
  • Explicitly mention whether the PowerShell scripts can be run cross-platform (e.g., with PowerShell Core on Linux/macOS) and provide installation guidance if so.
  • Provide Bash or shell script alternatives for common migration steps.
  • Clarify if any migration steps are only possible with PowerShell, and offer workarounds or alternatives for Linux/macOS users.
GitHub Create Pull Request
Application Gateway Scaling and Zone-redundant Application Gateway v2 ...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides a link to a tutorial for creating an autoscaling, zone-redundant Application Gateway using Azure PowerShell, but does not mention or link to equivalent instructions for Azure CLI or ARM templates, which are cross-platform. This creates a bias toward Windows/PowerShell users and may cause friction for Linux/macOS users.
Recommendations
  • Add links to tutorials or instructions for creating autoscaling, zone-redundant Application Gateway using Azure CLI and ARM/Bicep templates.
  • Mention Azure CLI and ARM/Bicep as alternative, cross-platform tools alongside PowerShell.
  • Ensure examples and walkthroughs are provided for both PowerShell and CLI, or at least reference CLI documentation.
GitHub Create Pull Request
Application Gateway Diagnostic logs ...application-gateway/application-gateway-diagnostics.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides a PowerShell-only example for enabling diagnostic logging, with no equivalent CLI or Bash example for Linux/macOS users. It also references Visual Studio and a .NET-based log converter tool, which are Windows-centric. There are no Linux-first or Linux-parity examples for command-line log configuration or log conversion.
Recommendations
  • Add Azure CLI and/or Bash examples for enabling diagnostic logging, alongside the PowerShell example.
  • Mention cross-platform log converter tools or provide instructions for converting logs using Python or other open-source tools.
  • Reference alternative editors and tools (such as VS Code or command-line utilities) for log analysis, not just Visual Studio.
  • Ensure that all critical workflows (log enabling, log conversion, log analysis) have Linux/macOS-friendly guidance.
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-22 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, in the troubleshooting section for Dedicated Backend Connections, Windows-specific tools and patterns are referenced (Service Principal Name configuration and Windows Authentication/IIS documentation), and Windows authentication mechanisms (NTLM, Kerberos) are discussed without mentioning Linux equivalents or guidance. Additionally, Windows terminology and links are presented first and exclusively in this context.
Recommendations
  • Add guidance for troubleshooting backend authentication issues on Linux-based servers (e.g., Apache, NGINX, Samba, MIT Kerberos).
  • Include references or links to Linux authentication documentation and tools where relevant.
  • Clarify that NTLM and Kerberos are cross-platform and provide examples or troubleshooting steps for Linux environments.
  • Where backend server logs are referenced, mention both Windows (IIS) and Linux (Apache, NGINX) log locations/formats.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively demonstrates the configuration of Azure Application Gateway TCP/TLS proxy using a SQL Server virtual machine running Windows Server. All examples and screenshots reference Windows-based SQL Server VMs, and the client connection step recommends SQL Server Management Studio (SSMS), a Windows-only tool. There are no examples or guidance for Linux-based SQL Server VMs or cross-platform SQL clients, which may create friction for Linux/macOS users.
Recommendations
  • Include instructions for deploying a SQL Server VM on Linux (e.g., Ubuntu) as a backend, or clarify if only Windows SQL Server is supported.
  • Provide examples of connecting to the SQL Server via cross-platform SQL clients (e.g., Azure Data Studio, sqlcmd, DBeaver) in addition to SSMS.
  • Add notes or guidance for Linux/macOS users regarding any platform-specific requirements or limitations.
  • If the feature supports Linux SQL Server VMs, add screenshots and walkthroughs for those scenarios.
GitHub Create Pull Request
← Previous Page 22 of 40 Next →