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 26-50 of 981 flagged pages
Application Gateway Certificates required to allow backend servers ...ion-gateway/certificates-for-backend-authentication.md
High Priority View Details →
Scanned: 2026-01-13 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 exclusively provides step-by-step instructions and screenshots for exporting certificates using Windows Certificate Manager, a Windows-only tool. There are no examples or guidance for performing equivalent tasks on Linux or macOS, nor are cross-platform command-line alternatives (such as OpenSSL) mentioned. The only command-line reference is to PowerShell/certmgr, reinforcing a Windows-centric approach.
Recommendations
  • Add equivalent instructions for exporting certificates using OpenSSL on Linux/macOS, including command-line examples.
  • Explicitly mention that the process can be performed on non-Windows platforms and provide links or steps for those environments.
  • Balance screenshots and step-by-step guides by including at least one Linux/macOS example for each major task.
  • Avoid referencing Windows tools (Certificate Manager, PowerShell) as the default or only method; instead, present them as one option among several.
GitHub Create Pull Request
Application Gateway Tutorial: Configure an Application Gateway with TLS termination using the Azure portal ...main/articles/application-gateway/create-ssl-portal.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows, with all certificate creation and backend VM setup examples using Windows PowerShell and Windows Server. There are no instructions or examples for Linux/macOS users on how to create self-signed certificates or configure Linux VMs as backends. Windows tools and workflows are mentioned exclusively and first, making it difficult for non-Windows users to follow the tutorial.
Recommendations
  • Provide equivalent Linux/macOS instructions for creating self-signed certificates (e.g., using OpenSSL).
  • Include examples for deploying Linux virtual machines as backend servers, such as Ubuntu or CentOS, and show how to install a web server (e.g., Apache or Nginx) for testing.
  • Offer cross-platform command alternatives (e.g., Bash, CLI) alongside PowerShell commands.
  • Explicitly state that both Windows and Linux VMs are supported and provide links to relevant documentation for each.
  • Reorder examples to present Windows and Linux options side-by-side, or alternate which platform is shown first.
GitHub Create Pull Request
Application Gateway Deploy Application Gateway Basic (Preview) ...in/articles/application-gateway/deploy-basic-portal.md
High Priority View Details →
Scanned: 2026-01-13 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 exhibits a strong Windows bias, primarily through exclusive use of Azure PowerShell and Windows Server examples. All command-line instructions are given in PowerShell, with no mention of Bash, CLI, or Linux/macOS alternatives. The VM creation walkthrough uses Windows Server 2019 only, and IIS (a Windows web server) is used for backend testing, with no Linux VM or Apache/Nginx example provided. This creates friction for Linux/macOS users and those preferring Bash or Azure CLI.
Recommendations
  • Provide Azure CLI (bash) equivalents for all PowerShell commands, especially for preview registration and VM extension installation.
  • Include Linux VM creation steps alongside Windows, e.g., Ubuntu or CentOS, and show how to install Apache or Nginx for backend testing.
  • When demonstrating backend pool configuration, mention that both Windows and Linux VMs are supported and provide examples for each.
  • Add notes or sections clarifying how Linux/macOS users can perform each step, including using Azure Cloud Shell with Bash.
  • Avoid using only Windows tools (IIS, PowerShell) for verification; offer cross-platform alternatives.
GitHub Create Pull Request
Application Gateway Export trusted client CA certificate chain for client authentication ...ateway/mutual-authentication-certificate-management.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows: all certificate export instructions use Windows GUI tools (Certificate Manager, Certificate Export Wizard), with screenshots and step-by-step guidance for Windows only. There are no Linux/macOS equivalents or CLI-based instructions for exporting certificates. PowerShell and Windows-specific tools are mentioned, while Linux methods are only referenced for concatenation, not for certificate export.
Recommendations
  • Add equivalent instructions for exporting certificates on Linux/macOS, using tools like openssl.
  • Provide CLI-based examples for certificate export, not just GUI walkthroughs.
  • Include screenshots or terminal output for Linux/macOS workflows.
  • Mention cross-platform tools and patterns before or alongside Windows-specific ones.
  • Ensure parity in the 'Prerequisites' and 'Next steps' sections by referencing Linux/macOS documentation and tools.
GitHub Create Pull Request
Application Gateway HTTP to HTTPS redirection in portal - Azure Application Gateway ...s/application-gateway/redirect-http-to-https-portal.md
High Priority View Details →
Scanned: 2026-01-13 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 is heavily biased toward Windows and PowerShell. All code examples for certificate creation and IIS installation use PowerShell and Windows-specific tools, with no mention of Linux equivalents or alternatives. The VM scale set instructions default to Windows Server, and there are no steps for deploying or configuring Linux-based backend servers or using Bash/Azure CLI. This creates friction for Linux/macOS users and may prevent them from completing the tutorial as written.
Recommendations
  • Provide Linux-based examples for creating self-signed certificates (e.g., using OpenSSL) and exporting PFX files.
  • Include instructions for deploying a Linux VM scale set (e.g., Ubuntu) and installing a web server (Apache/Nginx) using Bash or Azure CLI.
  • Offer Azure CLI and Bash alternatives for all PowerShell commands.
  • Clearly indicate OS-specific steps and provide parity for both Windows and Linux users.
  • Add notes or links to relevant Linux documentation where appropriate.
GitHub Create Pull Request
Application Gateway Tutorial: Improve web application access - Azure Application Gateway .../articles/application-gateway/tutorial-autoscale-ps.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All examples and instructions use Azure PowerShell cmdlets and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of Bash, Azure CLI, or Linux/macOS alternatives. The certificate creation steps rely on Windows-only commands, making it difficult for Linux/macOS users to follow the tutorial without significant adaptation.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all steps, especially resource creation and management.
  • Include instructions for creating self-signed certificates on Linux/macOS (e.g., using OpenSSL) and exporting them to PFX format.
  • Clearly indicate which steps are Windows-specific and offer cross-platform alternatives where possible.
  • Reorder examples or provide parallel instructions so that Linux/macOS users are not required to adapt Windows-centric steps.
  • Add notes or links to official guidance for Linux/macOS users on Azure resource management.
GitHub Create Pull Request
Application Gateway Tutorial: Configure an Application Gateway with TLS termination using the Azure portal ...main/articles/application-gateway/create-ssl-portal.md
High Priority View Details →
Scanned: 2026-01-12 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 is heavily biased towards Windows environments. All certificate creation and export steps use Windows PowerShell cmdlets (New-SelfSignedCertificate, Export-PfxCertificate), with no mention of Linux or cross-platform alternatives. The VM creation steps exclusively use Windows Server images, and IIS installation is performed via PowerShell. There are no examples or instructions for Linux users (e.g., using OpenSSL for certificates, deploying Linux VMs, or installing Apache/Nginx). Windows tools and patterns are mentioned exclusively and first, with no Linux parity.
Recommendations
  • Provide equivalent instructions for Linux users, such as using OpenSSL to create and export self-signed certificates.
  • Include examples for deploying Linux-based backend VMs (e.g., Ubuntu, CentOS) and installing a web server like Apache or Nginx.
  • Offer cross-platform command-line examples (e.g., Bash, Azure CLI) alongside PowerShell.
  • Mention Linux tools and patterns (e.g., file paths, certificate management) where relevant.
  • Clearly indicate that both Windows and Linux backend servers are supported, and provide parity in documentation steps.
GitHub Create Pull Request
Application Gateway Private Application Gateway deployment ...tion-gateway/application-gateway-private-deployment.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting Azure PowerShell examples and references before Azure CLI, and by using terminology and screenshots that are closely aligned with Windows-centric workflows (e.g., Azure portal navigation, PowerShell cmdlets). There are no explicit Linux shell or Bash examples, and the CLI instructions are less detailed compared to PowerShell. The documentation also references Windows tools and patterns (PowerShell, Azure portal) more prominently than cross-platform or Linux-native alternatives.
Recommendations
  • Provide Bash/Linux shell examples alongside PowerShell, especially for Azure CLI commands.
  • Ensure CLI instructions are as detailed and prominent as PowerShell instructions, including output examples and troubleshooting notes.
  • Include screenshots or instructions for Azure portal navigation on non-Windows platforms (e.g., browser on Linux/macOS).
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide platform-specific tips where relevant.
  • Consider adding ARM template and Terraform examples for key configuration steps, as these are cross-platform and popular in Linux environments.
  • Review terminology to avoid Windows-centric language and ensure parity for Linux administrators.
GitHub Create Pull Request
Application Gateway Manage traffic to App Service ...main/articles/application-gateway/configure-web-app.md
High Priority View Details →
Scanned: 2026-01-12 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 extensive PowerShell-based examples for all configuration steps, but does not include equivalent Linux shell (Bash/CLI) commands or scripts. All command-line automation is shown using Azure PowerShell, which is most commonly used on Windows. There is no mention of Azure CLI (az), Bash, or Linux-native tooling, and no examples for Linux users. This creates a bias toward Windows users and workflows.
Recommendations
  • Add equivalent Azure CLI (az) examples for each configuration step alongside PowerShell scripts.
  • Explicitly mention that both PowerShell and Azure CLI can be used, and provide guidance for Linux/macOS users.
  • Include Bash script examples for testing (e.g., using curl instead of Invoke-WebRequest).
  • Reference cross-platform tools and patterns where possible, rather than Windows-centric ones.
  • Ensure troubleshooting and testing instructions include Linux-compatible commands.
GitHub Create Pull Request
Application Gateway Troubleshoot Bad Gateway errors - Azure Application Gateway ...ion-gateway/application-gateway-troubleshooting-502.md
High Priority View Details →
Scanned: 2026-01-12 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 page demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples and referencing Windows-centric tools and patterns (e.g., IIS, PowerShell cmdlets, classic VM endpoints). There are no CLI (az), Bash, or Linux-specific troubleshooting commands or examples. Windows tools and terminology are mentioned before or instead of Linux equivalents, and Linux troubleshooting steps are missing throughout.
Recommendations
  • Add Azure CLI (az) and Bash examples alongside PowerShell for all resource queries and configuration checks.
  • Include troubleshooting steps and examples for Linux-based backend servers (e.g., Apache, Nginx), not just IIS.
  • Reference Linux firewall tools (e.g., iptables, ufw) and commands for checking port and network connectivity.
  • Provide parity in endpoint configuration guidance for Linux VMs, not just classic Windows VM endpoints.
  • Ensure that documentation language and examples are platform-neutral or explicitly cover both Windows and Linux scenarios.
GitHub Create Pull Request
Application Gateway Deploy Application Gateway Basic (Preview) ...in/articles/application-gateway/deploy-basic-portal.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples for registering/unregistering the preview and installing backend software use Azure PowerShell and Windows-specific tools (e.g., Add-WindowsFeature for IIS). The virtual machine creation steps exclusively use Windows Server as the example OS, with no mention of Linux alternatives or equivalent commands for Bash/CLI. There are no Linux VM setup instructions, nor examples for installing a web server on Linux. Windows tools and patterns are presented exclusively and before any Linux equivalents, which are entirely absent.
Recommendations
  • Provide equivalent Azure CLI (az) commands for registering/unregistering the preview, alongside PowerShell examples.
  • Include Linux VM creation steps in the backend pool section, such as creating Ubuntu or other Linux VMs.
  • Add instructions for installing a web server (e.g., Apache or Nginx) on Linux VMs, using Bash scripts or Azure VM extensions.
  • Show how to add Linux VMs to the backend pool, and demonstrate testing the application gateway with Linux-based backends.
  • Ensure screenshots and walkthroughs are OS-neutral or include both Windows and Linux variants.
  • Explicitly mention that Application Gateway supports both Windows and Linux backend servers, and provide parity in documentation examples.
GitHub Create Pull Request
Application Gateway Configure Azure Application Gateway TCP/TLS proxy ...n/articles/application-gateway/how-to-tcp-tls-proxy.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server as the SQL backend, referencing SQL Server Management Studio (a Windows-only tool) for client connectivity, and omitting any mention of Linux-based SQL server deployment or Linux-compatible client tools. All examples and screenshots are based on Windows environments, with no guidance for Linux users.
Recommendations
  • Include instructions for deploying SQL Server on Linux (e.g., Ubuntu) as an alternative backend VM.
  • Provide examples of connecting to the Application Gateway using Linux-compatible SQL clients such as sqlcmd, Azure Data Studio, or DBeaver.
  • Add screenshots and command-line examples for Linux environments where appropriate.
  • Explicitly mention cross-platform options and parity in prerequisites and tool recommendations.
  • Ensure that resource cleanup instructions cover both Windows and Linux scenarios.
GitHub Create Pull Request
Application Gateway Configure Request and Response Buffers ...lob/main/articles/application-gateway/proxy-buffers.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides configuration examples using Azure CLI, PowerShell, and ARM templates. PowerShell examples are detailed and cover both creation and update scenarios, while no equivalent Linux shell (bash) or cross-platform scripting examples are given. PowerShell is a Windows-centric tool, and its usage is emphasized with multiple code blocks and update scenarios. There is no mention of Linux-specific tools or patterns, such as Bash scripting or Cloud Shell usage. The reference to Azure SDK for .NET further reinforces a Windows-centric approach.
Recommendations
  • Add explicit Bash shell examples for Linux users, especially for updating existing Application Gateways.
  • Clarify that Azure CLI commands work cross-platform and provide sample usage in Bash.
  • Include references to cross-platform SDKs (e.g., Python, Java) in addition to .NET.
  • Mention Azure Cloud Shell as a platform-neutral way to run CLI commands.
  • Balance PowerShell and CLI coverage, ensuring Linux users are not left out in update scenarios.
GitHub Create Pull Request
Application Gateway Migrate from V1 to V2 - Azure Application Gateway ...lob/main/articles/application-gateway/migrate-v1-v2.md
High Priority View Details →
Scanned: 2026-01-12 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 page exhibits a strong Windows bias. All migration instructions, examples, and scripts are provided exclusively using PowerShell, with no mention of Bash, Azure CLI, or Linux-native tooling. Script installation and usage patterns are tailored to Windows/PowerShell environments, and there is no guidance for Linux or macOS users. The documentation assumes familiarity with PowerShell and Windows-centric workflows, omitting equivalent steps for cross-platform or Linux-native environments.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell commands and scripts, including examples for Linux/macOS terminals.
  • Include Bash script samples or instructions for running migration tasks on Linux.
  • Document how to use Azure Cloud Shell (Bash) for migration, not just PowerShell.
  • Explicitly state cross-platform compatibility of scripts, or provide platform-specific instructions where needed.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., file permissions, module installation).
  • List prerequisites and installation steps for Linux and macOS environments alongside Windows.
  • Ensure all downloadable scripts are tested and supported on Linux/macOS PowerShell (pwsh) and Azure CLI.
GitHub Create Pull Request
Application Gateway Quickstart: Direct web traffic using a Resource Manager template .../articles/application-gateway/quick-create-template.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively providing PowerShell commands for resource cleanup, referencing IIS (a Windows web server) for validation, and omitting Linux-based examples or alternatives (such as using Apache/Nginx or Bash/Azure CLI for resource management). No Linux-specific instructions or parity is offered for users deploying or validating on Linux VMs.
Recommendations
  • Provide equivalent resource cleanup instructions using Azure CLI (az group delete) and Bash shell commands.
  • Include validation steps for Linux VMs, such as installing Apache or Nginx and testing with curl or a browser.
  • Offer examples for both Windows and Linux VM configurations in the ARM template and validation sections.
  • Ensure that references to tools (e.g., IIS, PowerShell) are balanced with Linux alternatives and not presented as the default or only option.
GitHub Create Pull Request
Application Gateway FAQ on V1 retirement ...ob/main/articles/application-gateway/retirement-faq.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell scripts for migration tasks, without mentioning or providing examples for Azure CLI, Bash, or other cross-platform tools. There are no Linux or platform-agnostic migration instructions or examples, and the only automation guidance is centered on PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Provide equivalent Azure CLI (az) commands or scripts for all migration steps, ensuring Linux and macOS users have clear guidance.
  • Explicitly mention that migration can be performed from any OS, and clarify if PowerShell Core (cross-platform) is supported, or provide Bash alternatives.
  • Include examples or references for Bash scripts or automation using other cross-platform tools (e.g., Terraform, ARM templates) where applicable.
  • Reorder or supplement sections to present cross-platform options (Azure CLI, Bash) before or alongside PowerShell, to avoid implying Windows is the primary or only supported environment.
GitHub Create Pull Request
Application Gateway Redirect overview for Azure Application Gateway ...main/articles/application-gateway/redirect-overview.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates Windows bias by referencing only Windows-centric tools and workflows (e.g., Azure portal, PowerShell tutorial), and omitting Linux-specific examples or CLI instructions. The 'Next steps' section links exclusively to a PowerShell-based tutorial, with no mention of Azure CLI or Bash alternatives. There is no guidance for Linux users or parity in example commands.
Recommendations
  • Add equivalent Azure CLI and Bash examples for configuring redirects, alongside PowerShell instructions.
  • Include links to tutorials for Linux users, such as 'Configure URL redirection using Azure CLI' or 'Configure URL redirection using Bash'.
  • Ensure that references to configuration steps do not prioritize Windows tools (PowerShell, Azure portal) over cross-platform options.
  • Explicitly mention that Application Gateway configuration can be performed from Linux, macOS, and Windows environments, and provide parity in documentation.
GitHub Create Pull Request
Application Gateway Tutorial: Improve web application access - Azure Application Gateway .../articles/application-gateway/tutorial-autoscale-ps.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell. All examples use Azure PowerShell cmdlets and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of equivalent Linux or cross-platform approaches. There are no Bash, Azure CLI, or Linux-native certificate generation examples, and prerequisites assume a Windows/PowerShell environment. This may exclude or inconvenience users on Linux or macOS platforms.
Recommendations
  • Provide equivalent Azure CLI (az) examples alongside PowerShell for each step.
  • Include Linux/macOS instructions for generating self-signed certificates (e.g., using openssl).
  • Clarify that Azure PowerShell can be used cross-platform, but also offer Bash/CLI alternatives.
  • Mention and link to platform-agnostic tools and documentation where possible.
  • Reorder or parallelize examples so that Windows and Linux approaches are presented together, not Windows first.
GitHub Create Pull Request
Application Gateway Troubleshoot backend health issues in Azure Application Gateway ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-backend-health-troubleshooting.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias through frequent use of PowerShell commands and examples, prioritization of Windows tools and workflows (such as certlm.msc, netstat, and Windows command prompt), and lack of equivalent Linux command examples in several troubleshooting steps. While OpenSSL is mentioned for certificate inspection, most step-by-step instructions and troubleshooting commands are Windows-centric, with Linux alternatives either missing or relegated to brief mentions.
Recommendations
  • Provide Linux command-line equivalents for all PowerShell and Windows command prompt examples (e.g., use curl, nc, ss, ip, and OpenSSL for connectivity and certificate checks).
  • Include Linux-specific instructions for inspecting certificates (e.g., using openssl, certtool, or viewing certificate stores on common Linux distributions).
  • When listing troubleshooting steps, present both Windows and Linux methods side-by-side, or in parallel sections, to ensure parity.
  • Reference cross-platform tools (such as Azure CLI) before or alongside platform-specific tools like PowerShell.
  • Add screenshots or terminal outputs from Linux environments where Windows screenshots are provided.
  • Explicitly mention that all steps can be performed on both Windows and Linux, and clarify any platform-specific differences.
GitHub Create Pull Request
Application Gateway Scaling and Zone-redundant Application Gateway v2 ...eway/application-gateway-autoscaling-zone-redundant.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell in the 'Next steps' section for creating an autoscaling, zone redundant application gateway. There are no examples or links for equivalent Linux-friendly tools such as Azure CLI, nor are Linux-specific patterns or commands mentioned. This prioritizes Windows tooling and may hinder Linux users from finding relevant guidance.
Recommendations
  • Add equivalent Azure CLI instructions and tutorials for creating autoscaling, zone redundant application gateways.
  • Reference both PowerShell and CLI options in 'Next steps', ensuring parity for Linux and macOS users.
  • Where examples are given, provide both PowerShell and CLI syntax side-by-side.
  • Explicitly mention cross-platform support and link to documentation for Linux/macOS environments.
GitHub Create Pull Request
Application Gateway Backend health ...lication-gateway/application-gateway-backend-health.md
High Priority View Details →
Scanned: 2026-01-12 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 Windows bias by providing a PowerShell example before the Azure CLI example, and by omitting any Linux-specific commands or troubleshooting tools. The use of PowerShell as a primary example and lack of explicit mention of Linux shell usage or Linux troubleshooting approaches suggests a preference for Windows environments.
Recommendations
  • Provide Bash or Linux shell examples alongside PowerShell, especially for Azure CLI usage.
  • Explicitly mention that Azure CLI commands work cross-platform and show usage in a Linux terminal.
  • Include troubleshooting steps or tool recommendations relevant to Linux environments (e.g., curl, openssl for certificate checks).
  • Balance the order of examples so that Windows and Linux approaches are presented equally, or clarify platform applicability.
  • Add notes or links for Linux administrators on how to perform backend health checks and certificate troubleshooting using native Linux tools.
GitHub Create Pull Request
Application Gateway Externally managed scheduled autoscaling for Application Gateway v2 ...ation-gateway-externally-managed-scheduled-autoscaling.md
High Priority View Details →
Scanned: 2026-01-12 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 exclusively provides PowerShell examples and instructions for implementing scheduled autoscaling with Azure Automation, without mentioning or demonstrating Linux-friendly alternatives such as Azure CLI, Bash, or Python runbooks. The use of PowerShell and references to 'runbooks' implicitly favor Windows environments and tooling, potentially making it less accessible for Linux users or those preferring cross-platform solutions.
Recommendations
  • Add equivalent examples using Azure CLI and/or Bash scripts for runbooks to demonstrate Linux compatibility.
  • Explicitly mention that Azure Automation supports Python and Bash runbooks, and provide sample code for those.
  • Reorder or supplement instructions to present both Windows/PowerShell and Linux/Azure CLI approaches side by side.
  • Clarify that PowerShell is not required and that cross-platform alternatives are available for all steps.
  • Include troubleshooting and alerting links relevant to Linux-based runbooks, not just PowerShell.
GitHub Create Pull Request
Application Gateway Common key vault errors in Application Gateway ...gateway/application-gateway-key-vault-common-errors.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for certificate management and update operations, with no equivalent examples for Azure CLI or Bash. Troubleshooting steps and UI navigation are described primarily in terms of the Azure Portal, which is platform-agnostic but often used on Windows. There is no mention of Linux-specific tools, nor are Linux/Bash/CLI examples provided alongside PowerShell commands.
Recommendations
  • Add Azure CLI (az) command examples for all certificate management and troubleshooting steps, especially where PowerShell is currently used.
  • Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and provide Bash/CLI equivalents.
  • Where UI navigation is described, clarify that the Azure Portal is accessible from any OS and avoid implying a Windows-only workflow.
  • Include links to cross-platform documentation and note any differences in command syntax or tool availability between Windows and Linux.
GitHub Create Pull Request
Application Gateway Health monitoring overview for Azure Application Gateway ...lication-gateway/application-gateway-probe-overview.md
High Priority View Details →
Scanned: 2026-01-12 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 page demonstrates a bias toward Windows and PowerShell by exclusively providing PowerShell cmdlet examples (e.g., New-AzApplicationGatewayProbeHealthResponseMatch) and referencing Azure PowerShell as the primary automation/configuration tool. There are no CLI (az), Bash, or Linux-native examples or instructions. The 'devx-track-azurepowershell' custom metadata and the 'Next steps' section also prioritize PowerShell over cross-platform alternatives, reinforcing a Windows-centric approach.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell cmdlets, especially for probe configuration and matching criteria.
  • Include Bash script snippets or Linux shell commands where appropriate to demonstrate cross-platform usage.
  • Mention cross-platform tools (Azure CLI, REST API, Terraform) alongside PowerShell in all instructional sections and 'Next steps'.
  • Adjust metadata and page structure to highlight platform neutrality (e.g., 'devx-track-azurecli' or both).
  • Ensure that all configuration steps and automation patterns are shown for both Windows and Linux environments.
GitHub Create Pull Request
Application Gateway Diagnostic logs ...application-gateway/application-gateway-diagnostics.md
High Priority View Details →
Scanned: 2026-01-12 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 page demonstrates a Windows bias by providing only PowerShell examples for enabling diagnostic logging, referencing Windows-centric tools (Excel, Power BI, Visual Studio, C#), and omitting equivalent Linux/CLI/Bash instructions. Windows tools and patterns are mentioned exclusively or before any cross-platform alternatives, and there are no examples using Azure CLI, Bash, or Linux-native workflows for log management.
Recommendations
  • Add equivalent Azure CLI and Bash examples for enabling diagnostic logging, alongside PowerShell.
  • Include instructions for viewing and analyzing logs using Linux-native tools (e.g., jq, awk, grep) and open-source visualization platforms (e.g., Grafana).
  • Reference cross-platform editors and tools (e.g., VS Code, LibreOffice Calc) in addition to Windows-specific ones like Excel and Visual Studio.
  • Ensure that examples and tool recommendations are presented in a platform-neutral order or grouped by OS, rather than Windows-first.
  • Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and provide links to relevant cross-platform documentation.
GitHub Create Pull Request
← Previous Page 2 of 40 Next →