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 476-500 of 981 flagged pages
Application Gateway Configure an internal load balancer (ILB) endpoint ...configure-application-gateway-with-private-frontend-ip.md
Medium Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions for configuring an internal load balancer endpoint on Azure Application Gateway Standard v1, but it exhibits notable Windows bias. All virtual machine examples use Windows Server images, and IIS installation is demonstrated exclusively via PowerShell in Azure Cloud Shell. There are no Linux VM examples, nor are Linux-based backend server setup instructions provided. The PowerShell Cloud Shell is used by default, with no mention of Bash or Linux alternatives.
Recommendations
  • Include examples for creating Linux-based backend VMs (e.g., Ubuntu) alongside Windows Server.
  • Provide instructions for installing a web server (such as Apache or Nginx) on Linux VMs, using Bash in Azure Cloud Shell.
  • Show how to use Bash Cloud Shell for relevant steps, or at least mention that Bash is an option.
  • Ensure backend pool addition steps reference both Windows and Linux VMs.
  • Add a note clarifying that backend pools can contain both Windows and Linux servers, and provide parity in examples.
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-03-04 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a notable Windows bias. All backend VM examples use Windows Server, and IIS is installed using PowerShell commands. The hosts file editing instructions and command-line examples are exclusively for Windows (e.g., referencing c:\Windows\System32\drivers\etc, using ipconfig). There are no Linux VM or web server examples, nor are there instructions for editing /etc/hosts or using Linux command-line tools.
Recommendations
  • Provide parallel instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
  • Include examples for installing a Linux web server (e.g., Apache or Nginx) and verifying connectivity.
  • Add guidance for editing the /etc/hosts file on Linux/macOS, including appropriate commands (e.g., using sudo nano /etc/hosts and sudo systemctl restart networking or equivalent).
  • Mention Linux/macOS equivalents for commands like ipconfig (e.g., systemd-resolve --flush-caches or sudo service network-manager restart).
  • Clarify that the Application Gateway supports both Windows and Linux backend servers, and that the choice of OS is flexible.
Medium Priority View Details →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed instructions for enabling diagnostic logging via PowerShell but omits equivalent CLI or Bash examples for Linux/macOS users. The only programmatic example is a PowerShell cmdlet, and references to log conversion tools are .NET/C#-centric. There is no mention of Azure CLI or Bash scripting for enabling diagnostics, nor are Linux-native tools referenced for log analysis or conversion.
Recommendations
  • Add Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash scripting examples for common log management tasks.
  • Mention or link to log conversion tools that are platform-agnostic or provide Python-based alternatives.
  • Ensure that references to visualization tools (e.g., Excel, Power BI) are balanced with Linux-friendly options (e.g., Grafana, Kibana).
  • When referencing PowerShell, clarify that Azure CLI is also available and provide links or examples.
Application Gateway Health monitoring overview for Azure Application Gateway ...lication-gateway/application-gateway-probe-overview.md
Medium Priority View Details →
Scanned: 2026-03-03 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 references primarily using Azure PowerShell cmdlets (e.g., New-AzApplicationGatewayProbeHealthResponseMatch), without equivalent Azure CLI or ARM template examples. The 'MinServers' property is noted as only configurable via PowerShell, Azure CLI, or ARM templates, but only PowerShell is demonstrated. Additionally, PowerShell is mentioned first and exclusively in example sections, which may create friction for Linux/macOS users who prefer Azure CLI or other cross-platform tools.
Recommendations
  • Add equivalent Azure CLI examples for probe matching and custom probe configuration.
  • Provide ARM template snippets for relevant configuration tasks.
  • When listing supported tools, mention Azure CLI and ARM templates before or alongside PowerShell.
  • Clarify that all configuration tasks can be performed on Linux/macOS using Azure CLI or ARM templates.
  • Consider including a table or section comparing PowerShell, Azure CLI, and ARM template approaches for common probe configuration scenarios.
Application Gateway Configure an internal load balancer (ILB) endpoint ...configure-application-gateway-with-private-frontend-ip.md
Medium Priority View Details →
Scanned: 2026-03-03 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 primarily provides instructions for configuring an internal load balancer endpoint using Azure Application Gateway via the Azure portal. When creating backend VMs, only Windows Server is used as the example image, and IIS (a Windows web server) is installed. The Cloud Shell instructions exclusively use PowerShell and Windows-specific commands for IIS installation, with no mention of Linux VM options, Linux web servers (such as Apache or Nginx), or Bash alternatives. This creates friction for Linux/macOS users who may wish to use Linux VMs or different web servers.
Recommendations
  • Provide parallel instructions for creating Linux-based backend VMs (e.g., Ubuntu) and installing a Linux web server (such as Apache or Nginx).
  • Include Bash/CLI examples in Cloud Shell for Linux VM configuration and web server installation.
  • Mention that backend pools can use Linux VMs and provide guidance for Linux users.
  • Where PowerShell is used, offer Bash equivalents or clarify that both shells are supported in Cloud Shell.
Application Gateway Deploy Application Gateway Basic (Preview) ...in/articles/application-gateway/deploy-basic-portal.md
Medium Priority View Details →
Scanned: 2026-03-02 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 notable Windows bias. Azure PowerShell is used exclusively for preview registration and IIS installation, with no equivalent Bash/CLI or Linux examples. The VM creation section defaults to Windows Server, and IIS is used for backend testing, omitting Linux VM or Apache/Nginx alternatives. Linux users must adapt steps without guidance.
Recommendations
  • Provide Azure CLI (Bash) commands for preview registration/unregistration alongside PowerShell.
  • Include Linux VM creation steps (e.g., Ubuntu) as backend pool alternatives.
  • Offer instructions for installing Apache or Nginx on Linux VMs for backend testing.
  • Show both Windows and Linux examples for backend pool configuration.
  • Clarify that backend VMs can be Linux and link to relevant Linux documentation.
Application Gateway Scaling and Zone-redundant Application Gateway v2 ...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page is generally platform-neutral in its conceptual explanations, but the 'Next steps' section highlights Azure PowerShell as the primary tool for creating an autoscaling, zone-redundant Application Gateway. No equivalent Linux/macOS CLI (Azure CLI or ARM template) example or tutorial is referenced, and PowerShell is mentioned before any other tooling.
Recommendations
  • Add links or references to Azure CLI tutorials for creating autoscaling, zone-redundant Application Gateways.
  • Include ARM template or Bicep deployment examples for cross-platform parity.
  • Mention Azure CLI alongside PowerShell in the 'Next steps' section to guide Linux/macOS users.
  • Ensure that future tutorials and examples are available for both PowerShell and Azure CLI.
Medium Priority View Details →
Scanned: 2026-03-02 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 detailed guidance for enabling diagnostic logging on Azure Application Gateway, but only includes PowerShell examples for command-line configuration. There are no equivalent CLI or Bash examples for Linux/macOS users. Additionally, references to log conversion tools are Windows-centric (Visual Studio, C#), and data visualization recommendations focus on Excel and Power BI, which are more commonly used on Windows. No Linux-specific tools or workflows are mentioned.
Recommendations
  • Add Azure CLI and/or Bash examples alongside PowerShell for enabling diagnostic logging.
  • Mention cross-platform log conversion tools (e.g., Python scripts, jq) for processing JSON logs.
  • Include references to Linux/macOS-friendly data visualization tools (e.g., Grafana, Kibana) in addition to Excel and Power BI.
  • Ensure that instructions for retrieving resource IDs and configuring diagnostic settings are platform-neutral or provide alternatives for Linux/macOS users.
Application Gateway Health monitoring overview for Azure Application Gateway ...lication-gateway/application-gateway-probe-overview.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides PowerShell-centric examples for configuring custom health probe match criteria, specifically referencing the New-AzApplicationGatewayProbeHealthResponseMatch cmdlet. The MinServers property is described as only configurable via PowerShell, Azure CLI, or ARM templates, but the example and guidance focus on PowerShell. Additionally, PowerShell is mentioned before Azure CLI or ARM templates, and the 'devx-track-azurepowershell' custom tag suggests a Windows/PowerShell-first approach. There are no explicit Linux/CLI examples, and the 'Next steps' section links to a PowerShell guide before mentioning the Azure portal.
Recommendations
  • Add equivalent Azure CLI examples for probe configuration and match criteria, especially for Linux/macOS users.
  • Explicitly mention ARM template and REST API options where applicable, with links or examples.
  • Ensure 'Next steps' includes links to CLI and ARM template guides alongside PowerShell and portal.
  • Balance PowerShell and CLI coverage in examples and explanations.
  • Consider a section highlighting cross-platform management options for Application Gateway.
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-03-02 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: backend VM creation is only shown for Windows Server, IIS installation uses PowerShell, and hosts file editing is described exclusively for Windows (with DOS commands and Windows file paths). No Linux/macOS equivalents are provided for VM creation, web server setup, or hosts file editing, making the experience less accessible for non-Windows users.
Recommendations
  • Add instructions for creating Linux VMs (e.g., Ubuntu) as backend servers, including web server installation (such as Apache or Nginx) via Bash or Azure CLI.
  • Provide Linux/macOS steps for editing the hosts file (e.g., /etc/hosts), including commands for flushing DNS cache (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo dscacheutil -flushcache').
  • Include Azure CLI or Bash alternatives for IIS/web server setup, avoiding exclusive reliance on PowerShell.
  • Clarify that Application Gateway supports both Windows and Linux backend VMs, and offer parity in examples.
Application Gateway Azure Application Gateway Backend Settings configuration ...les/application-gateway/configuration-http-settings.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is generally platform-neutral and focuses on Azure Application Gateway configuration concepts. However, there are two notable instances of Windows bias: (1) troubleshooting guidance for Dedicated Backend Connections references Windows-specific authentication mechanisms (NTLM, Kerberos) and links to Windows and IIS documentation, and (2) Windows Authentication is mentioned before any Linux equivalents or generic authentication approaches. No PowerShell-heavy or missing Linux example bias is present, but Windows tools and patterns are referenced exclusively in troubleshooting sections.
Recommendations
  • Add troubleshooting guidance for Linux-based backend authentication scenarios (e.g., SPNEGO, Kerberos on Linux, or generic OAuth/OpenID Connect).
  • Include links to Linux documentation for Kerberos/SPN configuration and authentication, not just Windows/IIS.
  • Clarify that backend authentication mechanisms may differ depending on the OS and provide parity for Linux/macOS users where possible.
  • Where possible, mention generic approaches or cross-platform tools before Windows-specific ones.
Application Gateway Azure Application Gateway listener configuration ...rticles/application-gateway/configuration-listeners.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a code example for enabling HTTP/2 support using Azure PowerShell only, with no equivalent Azure CLI, Bash, or cross-platform example. This may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Add equivalent Azure CLI example(s) for enabling HTTP/2 support, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Wherever possible, provide both PowerShell and CLI examples for configuration tasks.
  • Explicitly mention that the Azure portal can be used for these configurations, and clarify if any features are only available via PowerShell.
  • Review the documentation for any other sections where only Windows-centric tools or patterns are referenced, and add Linux-friendly alternatives.
Application Gateway Configure an internal load balancer (ILB) endpoint ...configure-application-gateway-with-private-frontend-ip.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a notable Windows bias. All virtual machine examples use Windows Server images, and the only backend setup instructions involve installing IIS via PowerShell. The Cloud Shell is explicitly set to PowerShell, and the provided script is Windows-specific. There are no Linux VM examples, nor are there instructions for configuring a Linux-based backend (e.g., using NGINX or Apache). This makes it difficult for Linux users to follow the guide without significant adaptation.
Recommendations
  • Provide parallel instructions for creating Linux virtual machines (e.g., Ubuntu) as backend servers.
  • Include Linux-based backend configuration steps, such as installing NGINX or Apache using Bash/Cloud Shell.
  • Show both PowerShell and Bash examples where scripts are required.
  • Clarify that IIS/Windows is only one possible backend, and link to Linux-based backend pool configuration guides.
Application Gateway Scaling and Zone-redundant Application Gateway v2 ...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority View Details →
Scanned: 2026-03-01 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 the 'Next steps' section prominently features a PowerShell-based tutorial for creating an autoscaling, zone redundant application gateway. This suggests a Windows/PowerShell bias, as Linux/macOS users may prefer Azure CLI or ARM template examples, which are not mentioned or linked.
Recommendations
  • Add links to equivalent tutorials using Azure CLI and ARM templates for creating autoscaling, zone redundant Application Gateway v2.
  • Ensure that PowerShell examples are not the only option in 'Next steps'; provide parity for Linux/macOS users.
  • Consider listing Azure CLI or ARM template options before or alongside PowerShell to avoid 'windows_first' bias.
Medium Priority View Details →
Scanned: 2026-03-01 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 Azure CLI, Bash, or cross-platform instructions. It also references tools like Excel and Visual Studio for log analysis, which are primarily Windows-centric, and does not mention Linux/macOS alternatives. This creates friction for Linux/macOS users who may not use PowerShell or Windows-specific tools.
Recommendations
  • Add Azure CLI and/or Azure Cloud Shell examples for enabling diagnostic logging, as these are cross-platform and widely used by Linux/macOS users.
  • Include references or examples for analyzing logs using Linux/macOS-friendly tools (e.g., jq for JSON processing, csvkit, or open-source visualization tools).
  • When mentioning Excel or Visual Studio, also mention alternatives such as LibreOffice Calc, VS Code, or command-line tools.
  • Clarify that PowerShell Core is available cross-platform, if relevant, and provide installation links or notes.
  • Consider providing Bash or Python script examples for common log processing tasks.
Application Gateway Configure an internal load balancer (ILB) endpoint ...configure-application-gateway-with-private-frontend-ip.md
Medium Priority View Details →
Scanned: 2026-03-01 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 provides only Windows-based examples for backend VMs (Windows Server 2019) and uses PowerShell scripts to install IIS, with no mention of Linux alternatives. All instructions for backend setup and verification are Windows-centric, and the only automation example is a PowerShell command. There are no examples or guidance for deploying Linux VMs or using Bash/SSH for configuration.
Recommendations
  • Include parallel instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
  • Provide Bash/Cloud Shell (Bash) examples for installing a web server (e.g., Apache or Nginx) on Linux VMs.
  • Add notes or sections explaining how to use SSH to connect to Linux VMs for backend configuration.
  • Ensure that automation examples (e.g., VM extensions) are shown for both Windows and Linux, or clarify if only Windows is supported.
  • When listing VM image choices, mention both Windows and Linux options, or clarify that either is supported.
Application Gateway Azure Application Gateway Backend Settings configuration ...les/application-gateway/configuration-http-settings.md
Medium Priority View Details →
Scanned: 2026-03-01 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 authentication troubleshooting links point to IIS and Windows-specific resources before mentioning general concepts. No PowerShell-heavy or missing Linux example bias is present, but Windows tools and patterns are referenced exclusively in troubleshooting sections.
Recommendations
  • Add links or references to Linux-based authentication troubleshooting guides (e.g., Apache, NGINX, or generic Kerberos/SPN configuration on Linux).
  • Clarify that backend authentication concepts (NTLM, Kerberos, SPN) may apply to both Windows and Linux backends, and provide platform-neutral guidance where possible.
  • When referencing backend logs or authentication, mention that Linux-based web servers (such as Apache or NGINX) may require different log review steps and configuration.
  • If possible, provide examples or troubleshooting steps for common Linux backend scenarios alongside Windows/IIS examples.
Application Gateway Azure Application Gateway listener configuration ...rticles/application-gateway/configuration-listeners.md
Medium Priority View Details →
Scanned: 2026-03-01 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 include equivalent Azure CLI, Bash, or ARM template examples. This creates friction for Linux/macOS users who may not use PowerShell as their primary automation tool.
Recommendations
  • Add Azure CLI examples alongside PowerShell for configuration tasks such as enabling HTTP/2 support.
  • Where possible, provide Bash or cross-platform scripting examples.
  • Consider including ARM/Bicep template snippets for infrastructure-as-code users.
  • Explicitly state when a feature can only be configured via PowerShell, if that is the case.
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-03-01 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. All VM examples use Windows Server, IIS installation is shown only via Azure PowerShell (with Windows-specific commands), and hosts file editing is described exclusively for Windows (with DOS commands and Windows file paths). No Linux VM, Apache/Nginx, or Linux/macOS hosts file instructions are provided, and Windows tools (ipconfig) are used without Linux/macOS equivalents.
Recommendations
  • Provide parallel instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
  • Include examples for installing Apache or Nginx on Linux VMs, using Bash or Azure CLI.
  • Add hosts file editing steps for Linux/macOS (e.g., /etc/hosts, using sudo nano or vi).
  • Mention Linux/macOS commands for DNS cache refresh (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo dscacheutil -flushcache').
  • Clarify that backend pools can use any OS and provide links to relevant Linux documentation.
  • Show Azure CLI examples alongside PowerShell for cross-platform parity.
Application Gateway Deploy Application Gateway Basic (Preview) ...in/articles/application-gateway/deploy-basic-portal.md
Medium Priority View Details →
Scanned: 2026-03-01 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 notable Windows bias. Azure PowerShell is used exclusively for preview registration and IIS installation, with no mention of Azure CLI or Bash alternatives. The VM creation example uses Windows Server 2019 Datacenter, and IIS (a Windows web server) is installed for testing, with no Linux VM or Apache/Nginx examples. All command-line instructions are Windows/PowerShell-centric, and Windows tools/patterns are referenced before any Linux equivalents (which are absent).
Recommendations
  • Provide Azure CLI (bash) equivalents for preview registration and unregistration steps.
  • Include Linux VM creation instructions alongside Windows, using Ubuntu or another common distribution.
  • Offer guidance for installing Apache or Nginx on Linux VMs for backend testing, in addition to IIS.
  • Add examples for Linux users in the backend pool configuration and testing sections.
  • Mention that Application Gateway can work with both Windows and Linux backend servers, and link to relevant Linux documentation.
Application Gateway Deploy Application Gateway Basic (Preview) ...in/articles/application-gateway/deploy-basic-portal.md
Medium Priority View Details →
Scanned: 2026-02-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. All CLI examples for registering/unregistering the preview and installing IIS are provided exclusively in Azure PowerShell, with no Bash, Azure CLI, or Linux shell equivalents. The VM creation walkthrough uses Windows Server as the default example, and IIS (a Windows web server) is used for backend testing, with no mention of Linux VMs or Apache/Nginx alternatives. Linux users are left to infer their own steps, creating friction.
Recommendations
  • Provide Azure CLI (Bash) equivalents for preview registration/unregistration steps.
  • Include Linux VM creation instructions alongside Windows, or clarify that any OS can be used.
  • Offer examples for installing a Linux web server (e.g., Apache or Nginx) for backend testing.
  • Explicitly state that backend VMs can run any OS and provide links to Linux quickstarts.
  • Balance screenshots and walkthroughs to show both Windows and Linux scenarios.
Application Gateway Scaling and Zone-redundant Application Gateway v2 ...eway/application-gateway-autoscaling-zone-redundant.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 is generally platform-neutral in its conceptual explanations, but the 'Next steps' section prominently features a PowerShell-based tutorial for creating an autoscaling, zone redundant Application Gateway. This suggests a Windows/PowerShell bias, as no equivalent Linux/bash/CLI example is referenced or linked. Additionally, PowerShell is mentioned before any cross-platform tools, which may create friction for Linux/macOS users.
Recommendations
  • Add links to equivalent Azure CLI tutorials for autoscaling and zone redundancy, or explicitly state if PowerShell is required.
  • Ensure that conceptual and procedural examples are provided for both PowerShell and Azure CLI, with clear guidance for Linux/macOS users.
  • In the 'Next steps' section, list cross-platform tools (Azure CLI, ARM templates) before or alongside PowerShell to avoid Windows-first bias.
Application Gateway Azure Application Gateway Backend Settings configuration ...les/application-gateway/configuration-http-settings.md
Medium Priority View Details →
Scanned: 2026-02-28 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 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 Linux authentication examples or guidance, and the troubleshooting steps assume Windows-based backend servers.
Recommendations
  • Add guidance for Linux-based backend authentication scenarios, such as using Kerberos on Linux (e.g., Apache, NGINX, or other web servers) and how to configure SPNs and review logs in those environments.
  • Include troubleshooting steps and links for common Linux web server authentication issues when using Dedicated Backend Connections.
  • When referencing backend server logs, mention both Windows (IIS) and Linux (Apache, NGINX) log locations and formats.
  • Clarify that NTLM is Windows-specific, and provide alternatives or note limitations for Linux backends.
Application Gateway Azure Application Gateway listener configuration ...rticles/application-gateway/configuration-listeners.md
Medium Priority View Details →
Scanned: 2026-02-28 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 CLI or Linux-native examples (e.g., Azure CLI or ARM template). This creates friction for users on Linux/macOS who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add Azure CLI examples alongside PowerShell for configuration tasks, especially for enabling HTTP/2 support.
  • Where possible, provide ARM/Bicep template snippets for configuration to support infrastructure-as-code users on all platforms.
  • Clearly indicate that PowerShell is just one option and link to cross-platform alternatives.
  • Consider adding a table or section summarizing commands for PowerShell, Azure CLI, and portal UI for parity.
Medium Priority View Details →
Scanned: 2026-02-28 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 Azure CLI, Bash, or cross-platform scripting example. It also references Excel and Visual Studio-based tools for log analysis and conversion, which are primarily Windows-centric. There are no Linux/macOS-specific instructions or parity in command-line examples.
Recommendations
  • Add 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 appropriate.
  • Mention and provide examples for using jq, awk, or other common Linux tools to process and analyze JSON logs.
  • Reference open-source or cross-platform log conversion tools, or provide instructions for converting logs using Python or other platform-agnostic languages.
  • When suggesting tools like Excel or Visual Studio, also mention alternatives available on Linux/macOS (e.g., LibreOffice Calc, VS Code, or Python pandas).