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 226-250 of 981 flagged pages
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ipv6-application-gateway-arm-template.md ...ation-gateway/ipv6-application-gateway-arm-template.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using IIS (a Windows web server) for backend validation, referencing Azure PowerShell for resource cleanup, and omitting Linux-based alternatives or examples (such as Apache or Nginx for backend VMs, and Bash/Azure CLI for resource management). There are no Linux-specific instructions or parity in tooling or validation steps.
Recommendations
  • Provide examples using Linux VMs with Apache or Nginx for backend validation alongside IIS.
  • Include instructions for resource cleanup using Azure CLI (az group delete) and Bash shell commands.
  • Mention Linux-compatible deployment and validation steps, such as using curl or wget to test the application gateway.
  • Clarify that the template can be used with both Windows and Linux VMs, and link to relevant Linux quickstarts or tutorials.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-troubleshooting-502.md ...ion-gateway/application-gateway-troubleshooting-502.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 providing troubleshooting commands and examples exclusively in Azure PowerShell, which is most commonly used on Windows. There are no CLI (az), Bash, or Linux-native tool examples. Windows-centric concepts like IIS and PowerShell are referenced, while Linux equivalents (such as Apache/Nginx or Bash commands) are absent. The documentation does not offer parity for Linux administrators, making it less accessible for cross-platform users.
Recommendations
  • Add equivalent Azure CLI (az) commands alongside PowerShell examples for all troubleshooting steps.
  • Include Linux-native troubleshooting commands (e.g., curl, netstat, dig) where appropriate.
  • Mention and provide examples for common Linux web servers (Apache, Nginx) in relevant sections, not just IIS.
  • Ensure that references to tools and patterns (e.g., checking DNS, health probes) include both Windows and Linux approaches.
  • Where possible, present cross-platform solutions first or in parallel, rather than defaulting to Windows/PowerShell.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-probe-overview.md ...lication-gateway/application-gateway-probe-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 PowerShell-specific cmdlet examples (e.g., New-AzApplicationGatewayProbeHealthResponseMatch) and referencing PowerShell as the primary method for custom probe configuration. There are no equivalent examples or instructions for Linux users (such as Azure CLI, ARM templates, or REST API). The 'Next steps' section also lists PowerShell before other options, and does not mention Linux-friendly alternatives.
Recommendations
  • Provide Azure CLI examples alongside PowerShell cmdlets for all configuration tasks, especially for creating and matching custom health probes.
  • Include references to ARM template and REST API methods for configuring probes, ensuring platform neutrality.
  • In the 'Next steps' section, list Azure CLI and portal instructions before or alongside PowerShell, or present them in a platform-agnostic order.
  • Avoid using only PowerShell-specific terminology (e.g., cmdlet, -Match operator) without Linux/CLI equivalents.
  • Add explicit Linux/Unix shell examples where relevant, and clarify that all features are accessible from non-Windows environments.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-backend-health-troubleshooting.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-backend-health-troubleshooting.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a noticeable Windows bias. Troubleshooting steps and examples frequently use PowerShell commands and Windows-specific tools (such as certlm.msc, netstat, and command prompt instructions), often without providing equivalent Linux commands or workflows. In several cases, Windows methods are described in detail before mentioning Linux alternatives, and some troubleshooting scenarios lack Linux examples entirely.
Recommendations
  • Provide Linux equivalents for all PowerShell and Windows command examples (e.g., use Bash/CLI, OpenSSL, netstat, ss, etc.).
  • Include step-by-step instructions for certificate management and inspection on Linux (e.g., using OpenSSL, certtool, or system utilities).
  • When describing troubleshooting steps, present both Windows and Linux methods side-by-side, or in parallel sections, to ensure parity.
  • Expand examples to include Azure CLI (cross-platform) commands wherever PowerShell is used.
  • Avoid referencing Windows tools (e.g., certlm.msc, command prompt) exclusively; mention Linux alternatives (e.g., /etc/ssl, openssl, systemd commands) with equal prominence.
  • Ensure screenshots and walkthroughs are available for both Windows and Linux environments where applicable.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-ilb-arm.md ...les/application-gateway/application-gateway-ilb-arm.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 and PowerShell. All examples and instructions use Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native tooling. The setup steps and deletion procedures are exclusively shown with PowerShell syntax, and links reference Windows PowerShell documentation. There are no Linux or cross-platform command examples, nor any guidance for users on non-Windows systems.
Recommendations
  • Add equivalent Azure CLI (az) command examples for each PowerShell step, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include a section or note explaining how to perform these tasks on Linux/macOS, referencing Bash or shell environments.
  • Update links and references to include Azure CLI documentation alongside PowerShell.
  • Where possible, provide both PowerShell and CLI code blocks, labeling them clearly for user choice.
  • Mention that Azure CLI can be installed and used on Windows, Linux, and macOS, promoting platform neutrality.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/deploy-basic-portal.md ...in/articles/application-gateway/deploy-basic-portal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use Azure PowerShell, with no mention of Azure CLI or Bash alternatives. The VM creation walkthrough exclusively uses Windows Server, and IIS (a Windows-only web server) is installed for testing, with no Linux VM or Apache/Nginx example provided. The instructions for registering/unregistering the preview and installing extensions are all PowerShell-centric, and the testing steps assume a Windows backend. There is no guidance for Linux users or parity in tooling or examples.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell commands for preview registration/unregistration and VM extension installation.
  • Include instructions for creating a Linux VM (e.g., Ubuntu) as a backend server, with steps for installing Apache or Nginx for testing.
  • Offer parity in backend pool examples by showing both Windows and Linux VM configurations.
  • Mention cross-platform options for command-line usage (e.g., Azure CLI, Bash, Cloud Shell Bash) early in the prerequisites.
  • Clarify that IIS is optional and provide alternative Linux-based web server testing steps.
  • Ensure screenshots and walkthroughs do not exclusively show Windows-centric workflows.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ingress-controller-install-existing.md ...ication-gateway/ingress-controller-install-existing.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias. Several command examples use PowerShell syntax and variables, especially in the identity and role assignment sections, which may be less familiar or directly usable for Linux users. The backup instructions reference the Azure portal's export, which includes PowerShell scripts alongside Bash scripts, but PowerShell is mentioned first. The use of Azure Cloud Shell is platform-neutral, but the presence of PowerShell-specific command blocks and variable usage (e.g., $variable) suggests a Windows-centric approach. Linux equivalents (pure Bash) are not always provided, and PowerShell commands appear before or instead of Bash alternatives in some key steps.
Recommendations
  • Provide all command examples in both Bash and PowerShell syntax, or default to Bash for cross-platform compatibility.
  • Avoid using PowerShell variable syntax ($variable) in examples unless explicitly targeting Windows users; prefer Bash syntax for general documentation.
  • When referencing downloadable scripts (e.g., in backups), clarify which are for Windows/PowerShell and which are for Linux/Bash, and present Bash options first.
  • Explicitly state that all steps can be performed on Linux, macOS, or Windows, and highlight any platform-specific caveats.
  • Where PowerShell is used, offer a Bash equivalent immediately after, especially for Azure CLI commands, which are cross-platform.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/create-multiple-sites-portal.md ...es/application-gateway/create-multiple-sites-portal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 clear Windows bias: virtual machine creation uses Windows Server exclusively, IIS installation is shown only via Azure PowerShell and Windows-specific commands, and hosts file editing instructions are tailored for Windows (with DOS commands and Windows file paths). There are no Linux VM examples, nor instructions for installing a web server or editing hosts files on Linux systems.
Recommendations
  • Provide parallel instructions for creating Linux VMs (e.g., Ubuntu) and installing a web server (such as Apache or Nginx) using Bash or Azure CLI.
  • Include Linux-specific steps for editing the /etc/hosts file and flushing DNS (e.g., using 'sudo nano /etc/hosts' and 'sudo systemd-resolve --flush-caches').
  • Offer Azure CLI or Bash alternatives to PowerShell commands for VM extension installation.
  • Clarify that Application Gateway supports both Windows and Linux backend servers, and show examples for both.
  • When presenting host file editing, mention both Windows and Linux locations and commands, and avoid using only Windows-centric examples.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/redirect-http-to-https-portal.md ...s/application-gateway/redirect-http-to-https-portal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 throughout. All code examples use PowerShell, and instructions for creating certificates and installing IIS are exclusively Windows-centric. The virtual machine scale set is created with Windows Server 2016 Datacenter as the default OS, with no mention of Linux alternatives. There are no examples or guidance for Linux users, such as using OpenSSL for certificates or deploying a Linux-based backend (e.g., NGINX/Apache). Windows tools and patterns are referenced exclusively, and Linux equivalents are missing.
Recommendations
  • Provide parallel Linux examples for key steps, such as creating self-signed certificates with OpenSSL and installing a web server (e.g., Apache or NGINX) on Linux VMSS instances.
  • Include instructions and screenshots for deploying a Linux-based VM scale set as the backend pool, alongside the Windows example.
  • Offer Bash/Azure CLI code snippets in addition to PowerShell, and clarify when steps differ between Windows and Linux environments.
  • Mention Linux-friendly file paths and certificate handling, and avoid assuming Windows file system conventions (e.g., c:\appgwcert.pfx).
  • Add a section or callout for Linux users, linking to relevant Azure documentation for Linux VM management and web server setup.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/key-vault-certs.md ...b/main/articles/application-gateway/key-vault-certs.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 key configuration steps, referencing Azure PowerShell and CLI before other tools, and omitting Linux-specific guidance or examples (such as Bash scripts or Linux shell commands). The use of PowerShell as the sole example for referencing Key Vault secrets and configuring Application Gateway listeners further reinforces this bias, making it less accessible for Linux users.
Recommendations
  • Provide equivalent examples using Azure CLI (az commands) and Bash scripts alongside PowerShell, especially for steps involving Key Vault and Application Gateway configuration.
  • Explicitly mention cross-platform compatibility for all command-line steps, clarifying that Azure CLI can be used on Linux, macOS, and Windows.
  • Add Linux-specific troubleshooting tips or notes where relevant, such as file format handling (PFX) and environment setup.
  • Ensure that references to tools and commands do not default to Windows/PowerShell first; present CLI and PowerShell examples side-by-side or in parallel sections.
  • Include links to official Azure CLI documentation and Linux setup guides in the 'Next steps' section.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/overview-v2.md .../blob/main/articles/application-gateway/overview-v2.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell scripts and cmdlets for migration and preview registration tasks, with no mention of Bash, Linux shell, or cross-platform CLI alternatives. The 'Next steps' section links to a PowerShell-based tutorial as the primary onboarding path. There is no guidance or examples for Linux users, and Windows tools/patterns are referenced first and exclusively.
Recommendations
  • Provide Azure CLI (bash/shell) examples alongside PowerShell for all management and migration tasks.
  • Explicitly mention cross-platform support and clarify which instructions are Windows-specific.
  • Add links to Linux-focused tutorials or documentation, especially for onboarding and migration.
  • Ensure that both PowerShell and CLI examples are presented in parallel throughout the documentation.
  • Review and update references to tools to include Linux equivalents where applicable (e.g., Bash, shell scripting).
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/redirect-overview.md ...main/articles/application-gateway/redirect-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates Windows bias by referencing only the Azure portal and a PowerShell-based tutorial for configuring URL redirection, without mentioning or providing examples for Linux-friendly tools such as Azure CLI or ARM templates. No Linux-specific commands or cross-platform configuration methods are discussed, and the 'Next steps' section links exclusively to a PowerShell tutorial, which is primarily used on Windows.
Recommendations
  • Add equivalent examples and tutorials using Azure CLI, which is cross-platform and widely used on Linux and macOS.
  • Include references to ARM template or Bicep-based configuration for infrastructure-as-code scenarios, which are platform-agnostic.
  • Ensure that 'Next steps' links include both PowerShell and Azure CLI tutorials, and clarify which tools are available on which platforms.
  • Explicitly mention that configuration can be performed from Linux, macOS, and Windows, and provide guidance for each environment.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/mutual-authentication-overview.md .../application-gateway/mutual-authentication-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation shows a moderate Windows bias. PowerShell is presented as the first and most detailed configuration example, with CLI examples following but less detailed. There are no explicit Linux or cross-platform shell (bash) examples, and the guidance for next steps points users to a PowerShell-specific tutorial. The documentation also references PowerShell and CLI as configuration options, but does not mention Linux-specific tools or provide parity in example depth.
Recommendations
  • Provide bash/Linux shell examples alongside PowerShell and Azure CLI, especially for certificate extraction and management tasks.
  • Ensure that CLI examples are as detailed as PowerShell examples, including step-by-step configuration, not just single-line updates.
  • In 'Next steps', link to both PowerShell and CLI (and, if available, ARM/Bicep) tutorials, not just PowerShell.
  • Explicitly mention cross-platform compatibility and provide guidance for Linux/macOS users, including any OS-specific considerations for certificate handling.
  • Where possible, avoid assuming PowerShell as the default scripting environment; present CLI or bash as equally valid starting points.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/self-signed-certificates.md ...ticles/application-gateway/self-signed-certificates.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates moderate Windows bias. Windows and Windows-specific tools (IIS, PowerShell) are mentioned before or more prominently than their Linux equivalents. The Azure PowerShell example is provided, but no Azure CLI or ARM template equivalent is shown. IIS instructions are given before Apache and NGINX, and Windows file paths are used in PowerShell examples. The private certificate generator tool is web-based and not platform-specific, but the overall flow and examples lean toward Windows-first presentation.
Recommendations
  • Provide Azure CLI and/or ARM template examples alongside Azure PowerShell for certificate upload and configuration.
  • Include Linux-specific instructions for importing certificates into trusted root stores (e.g., update-ca-certificates on Ubuntu).
  • Alternate the order of web server configuration examples (e.g., present Apache or NGINX before IIS, or group by OS).
  • Use platform-neutral file paths in code samples, or provide both Windows and Linux path examples.
  • Explicitly mention Linux equivalents for any Windows-specific steps, such as hosts file editing or certificate management.
  • Add screenshots or instructions for Linux certificate trust store management.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-template.md .../articles/application-gateway/quick-create-template.md
High Priority View Details →
Scanned: 2025-09-07 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by providing only PowerShell commands for resource cleanup, referencing IIS (a Windows-only web server) for validation, and omitting Linux/CLI alternatives for these steps. There are no examples or instructions for Linux users, such as using Bash, Azure CLI, or Linux-based web servers for validation.
Recommendations
  • Provide equivalent Azure CLI (az) commands for resource cleanup alongside the PowerShell example, as Azure CLI is cross-platform.
  • Include instructions for validating the deployment using a Linux-based web server (e.g., Apache or Nginx) in addition to IIS, or clarify how Linux users can test the deployment.
  • Add Bash shell examples for common operations where appropriate.
  • Ensure that references to tools or commands are platform-neutral or that both Windows and Linux alternatives are presented side by side.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-infrastructure.md ...es/application-gateway/configuration-infrastructure.md
High Priority View Details →
Scanned: 2025-09-06 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. It references Azure PowerShell explicitly for restarting the Application Gateway, without providing equivalent Azure CLI (cross-platform) or Bash examples. The only command-line tooling mentioned is PowerShell, and there are no Linux/Unix-specific instructions or examples. This may make the documentation less approachable for Linux or cross-platform users.
Recommendations
  • Wherever Azure PowerShell commands are referenced, provide equivalent Azure CLI (az) commands and examples.
  • When mentioning how to restart or manage Application Gateway resources, include both PowerShell and CLI/Bash command snippets side by side.
  • Ensure that all instructions and examples are platform-neutral or explicitly include both Windows and Linux usage patterns.
  • Add a note clarifying that both Azure PowerShell and Azure CLI are supported, and link to relevant cross-platform installation guides.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/overview-v2.md .../blob/main/articles/application-gateway/overview-v2.md
High Priority View Details →
Scanned: 2025-09-06 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell scripts and commands for migration and preview registration, with no mention of Linux or cross-platform alternatives such as Azure CLI (bash) or ARM templates. The only command-line examples provided use PowerShell cmdlets, and the migration script is specifically described as an Azure PowerShell script. There are no Linux shell/bash examples, and the documentation does not explicitly mention Linux or macOS compatibility for these operations.
Recommendations
  • Provide equivalent Azure CLI (bash) examples for all PowerShell commands, especially for registration, unregistration, and migration tasks.
  • Mention that Azure CLI is cross-platform and can be used from Linux, macOS, and Windows.
  • If a migration script is only available in PowerShell, clarify whether it can be run on PowerShell Core (pwsh) on Linux/macOS, or provide a CLI/ARM/Bicep alternative.
  • Include links or references to documentation on using Azure Application Gateway with Linux-based tools and environments.
  • Ensure that tutorials and next steps include both PowerShell and CLI options, and avoid defaulting to Windows-centric tools.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-template.md .../articles/application-gateway/quick-create-template.md
High Priority View Details →
Scanned: 2025-09-06 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively providing PowerShell commands for resource cleanup and focusing on IIS (a Windows web server) for validation. There are no Linux-specific examples, such as using Bash, Azure CLI, or deploying Linux-based web servers (e.g., Apache or Nginx) for testing the Application Gateway. The instructions and screenshots are tailored to Windows-centric workflows.
Recommendations
  • Provide equivalent Azure CLI and Bash commands for resource cleanup, such as 'az group delete --name <resource group name>'.
  • Include examples of deploying Linux-based VMs with Apache or Nginx for backend validation, alongside IIS.
  • Offer validation steps using Linux tools (e.g., curl, wget) to test the Application Gateway.
  • Ensure screenshots and instructions are platform-neutral or include both Windows and Linux perspectives.
  • Explicitly mention that the template and process work for both Windows and Linux VMs, and link to Linux-specific quickstarts where relevant.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/overview-v2.md .../blob/main/articles/application-gateway/overview-v2.md
High Priority View Details →
Scanned: 2025-09-05 00:00
Reviewed by: Unknown
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 primarily referencing Azure PowerShell scripts and commands for migration and preview registration, without providing equivalent Azure CLI (cross-platform) or Bash examples. The only code snippets for registering/unregistering the preview use PowerShell cmdlets, and migration guidance references a PowerShell script in the PowerShell Gallery. There are no explicit Linux/Bash/CLI examples, and the documentation does not mention Linux tooling or workflows. Additionally, the 'Next steps' section lists a PowerShell-based tutorial before mentioning the Azure CLI, reinforcing a Windows-first approach.
Recommendations
  • Provide Azure CLI and/or Bash examples alongside PowerShell for all command-line operations, including migration and preview registration/unregistration.
  • Reference cross-platform tools and workflows (e.g., Azure CLI, Bash scripts) equally or before Windows-specific tools.
  • Include links to tutorials and modules that use Azure CLI or Bash, not just PowerShell.
  • Explicitly state that all features and scripts are available and supported on Linux/macOS as well as Windows, where applicable.
  • Where PowerShell scripts are referenced (such as for migration), provide or link to equivalent Azure CLI or Bash scripts, or clarify if none exist.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-template.md .../articles/application-gateway/quick-create-template.md
High Priority View Details →
Scanned: 2025-09-05 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows environments by providing only PowerShell commands for resource cleanup and focusing on IIS (a Windows web server) for validation. There are no Linux/Unix shell (Bash) examples for resource management, nor is there mention of Linux-based web servers (such as Apache or Nginx) for backend validation. The use of IIS and PowerShell without Linux alternatives may hinder parity for users on Linux or macOS.
Recommendations
  • Provide equivalent Azure CLI (Bash) commands for resource group deletion, such as 'az group delete --name <your resource group name>'.
  • Include instructions or notes for validating the deployment using a Linux-based web server (e.g., Apache or Nginx) as an alternative to IIS.
  • When referencing tools or commands, present both Windows (PowerShell) and Linux (CLI/Bash) options, or link to sections that cover both.
  • Clarify that the template can be used with both Windows and Linux VMs, and provide guidance for customizing the template for Linux scenarios.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-template.md .../articles/application-gateway/quick-create-template.md
High Priority View Details →
Scanned: 2025-09-04 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by providing only a PowerShell example for resource cleanup, referencing IIS (a Windows-only web server) for validation, and omitting equivalent Linux/CLI examples for these steps. No Linux-native tools or commands are mentioned, and the validation process assumes a Windows environment.
Recommendations
  • Provide Azure CLI and/or Bash examples for resource cleanup (e.g., using 'az group delete').
  • Include instructions for deploying and validating with a Linux-based web server (such as Nginx or Apache) as an alternative to IIS.
  • Ensure that all command-line instructions are presented with both PowerShell and CLI/Bash equivalents, or at least reference where to find them.
  • Explicitly mention that IIS is used for demonstration but that Linux-based VMs/web servers are equally supported, with links or steps for those scenarios.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/overview-v2.md .../blob/main/articles/application-gateway/overview-v2.md
High Priority View Details →
Scanned: 2025-09-04 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by prioritizing Azure PowerShell scripts and cmdlets for migration and preview registration/unregistration tasks, with no mention or examples of Bash, Linux shell, or cross-platform CLI alternatives. The only command-line examples use PowerShell syntax and cmdlets (e.g., Set-AzContext, Register-AzProviderFeature), and the migration script is only referenced as a PowerShell solution. There is no guidance or parity for Linux or macOS users, nor are Azure CLI (az) commands provided as alternatives.
Recommendations
  • Provide equivalent Azure CLI (az) command examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Mention both Azure PowerShell and Azure CLI as supported options for management and migration tasks, and avoid implying that PowerShell is the default or only supported tool.
  • If migration scripts are only available in PowerShell, clarify this limitation and provide guidance or links for Linux/macOS users (e.g., running PowerShell Core on Linux, or alternative migration approaches).
  • In 'Next steps' and tutorial links, ensure that both PowerShell and CLI-based tutorials are referenced equally, or provide a choice.
  • Review all code blocks and command references to ensure Linux users are not excluded, and add Bash/CLI examples where appropriate.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/overview-v2.md .../blob/main/articles/application-gateway/overview-v2.md
High Priority View Details →
Scanned: 2025-09-02 00:00
Reviewed by: Unknown
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 primarily referencing Azure PowerShell scripts and cmdlets for migration and preview registration tasks, and by linking to PowerShell-based tutorials. There are no explicit Linux or Bash examples, and the use of PowerShell is presented as the default or only method for several operations. Azure CLI commands are shown, but the examples use PowerShell-style cmdlets (Set-AzContext, Get-AzProviderFeature), which are not cross-platform. There is no mention of Linux-specific tools, nor are Bash or cross-platform CLI examples provided alongside PowerShell instructions.
Recommendations
  • Provide parallel examples using Azure CLI (az) commands in Bash for all PowerShell script references, especially for migration and preview registration.
  • Clearly indicate when a command is PowerShell-specific and offer equivalent instructions for Linux/macOS users.
  • Include links to tutorials and documentation that use Bash/Azure CLI as well as PowerShell.
  • Avoid using PowerShell cmdlets in code blocks labeled as Azure CLI unless they are truly cross-platform.
  • Add a section or note highlighting cross-platform management options for Azure Application Gateway (e.g., Azure CLI, REST API, ARM templates) and when to use each.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-template.md .../articles/application-gateway/quick-create-template.md
High Priority View Details →
Scanned: 2025-09-02 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits Windows bias by exclusively providing PowerShell commands for resource cleanup, referencing IIS (a Windows web server) for validation, and omitting Linux-specific instructions or examples. The only command-line example is PowerShell, and the validation step assumes IIS is installed on backend VMs, which is a Windows-centric pattern. There are no Linux alternatives or parity in examples, and Windows tools are mentioned before any Linux equivalents (which are absent).
Recommendations
  • Provide equivalent Azure CLI commands for resource cleanup (e.g., az group delete) alongside PowerShell examples.
  • Include instructions for deploying and validating with a Linux-based web server (e.g., Apache or Nginx) in the backend VMs.
  • Offer Linux shell (bash) examples for interacting with Azure resources and validating deployments.
  • Explicitly mention cross-platform options and ensure that Linux users are supported throughout the quickstart.
  • Reorder or parallelize examples so that Windows and Linux approaches are presented together, not Windows-first.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/overview-v2.md .../blob/main/articles/application-gateway/overview-v2.md
High Priority View Details →
Scanned: 2025-09-01 00:00
Reviewed by: Unknown
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 primarily referencing Azure PowerShell scripts and commands for migration and preview registration, with no mention of Bash, Linux, or cross-platform CLI alternatives. The only command-line examples use PowerShell cmdlets (Set-AzContext, Get-AzProviderFeature, Register-AzProviderFeature), and the migration script is only described as a PowerShell script. There are no explicit Linux or Bash examples, and the documentation does not mention or prioritize cross-platform tools or workflows.
Recommendations
  • Provide Azure CLI (az) command equivalents for all PowerShell examples, especially for migration and feature registration/unregistration.
  • Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Where scripts are referenced (e.g., migration script), clarify if a Bash or cross-platform version is available, or provide one.
  • In 'Next steps', include links to tutorials or documentation that use Azure CLI or Bash.
  • When listing tools or interfaces (portal, PowerShell, CLI), avoid always listing PowerShell first; alternate or clarify cross-platform parity.
  • Add a note or section addressing Linux/macOS users and their options for managing Application Gateway.
GitHub Create Pull Request
← Previous Page 10 of 40 Next →