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 701-725 of 981 flagged pages
Application Gateway What is Azure Application Gateway v2? .../blob/main/articles/application-gateway/overview-v2.md
Medium Priority View Details →
Scanned: 2026-01-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Application Gateway v2 demonstrates a moderate Windows/PowerShell bias. Migration guidance and preview registration/unregistration are provided exclusively via Azure PowerShell commands, with no equivalent Azure CLI (cross-platform) or Bash examples. The main tutorial link also points to a PowerShell-based walkthrough, and there is no mention of Linux/macOS-specific instructions or parity for these operations. This creates friction for users on Linux/macOS who may prefer or require Azure CLI or Bash scripts.
Recommendations
  • Provide Azure CLI and Bash equivalents for all PowerShell commands, especially for migration and preview registration/unregistration steps.
  • Ensure tutorial links include both PowerShell and Azure CLI/Bash options, or clarify which platforms are supported.
  • Add notes or sections explicitly addressing cross-platform usage, highlighting any differences or limitations.
  • Where PowerShell is referenced, clarify if Azure CLI can be used for the same tasks and link to relevant documentation.
GitHub Create Pull Request
Application Gateway Scaling and Zone-redundant Application Gateway v2 ...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority View Details →
Scanned: 2026-01-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides a link to a tutorial for creating an autoscaling, zone-redundant Application Gateway using Azure PowerShell, but does not mention or link to equivalent instructions for Azure CLI, ARM templates, or Bicep, which are cross-platform and commonly used on Linux/macOS. The only explicit tooling example is Windows-centric (PowerShell).
Recommendations
  • Add links or sections for creating autoscaling, zone-redundant Application Gateways using Azure CLI, ARM templates, or Bicep.
  • Ensure that examples and tutorials are provided for both Windows (PowerShell) and cross-platform tools (CLI, templates).
  • Where possible, present cross-platform options before or alongside Windows-specific ones.
GitHub Create Pull Request
Application Gateway FAQ on V1 retirement ...ob/main/articles/application-gateway/retirement-faq.md
Medium Priority View Details →
Scanned: 2026-01-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page on Application Gateway V1 retirement and migration to V2 heavily references Azure PowerShell scripts for migration tasks, such as configuration migration and public IP retention. There are no CLI (az) or Bash examples provided, nor are Linux/macOS-friendly migration instructions mentioned. The migration tooling and guidance appear to assume a Windows/PowerShell environment, which may create friction for Linux/macOS users.
Recommendations
  • Provide equivalent Azure CLI (az) commands and scripts for migration steps, especially for configuration migration and public IP retention.
  • Include Bash or shell script examples for common migration tasks.
  • Clarify whether the PowerShell scripts can be run cross-platform (e.g., via PowerShell Core on Linux/macOS), and provide installation/setup instructions for non-Windows users.
  • Explicitly mention Linux/macOS support or alternatives in migration guidance sections.
  • Consider linking to or creating migration guides tailored for Linux/macOS environments.
GitHub Create Pull Request
Application Gateway Tutorial: Improve web application access - Azure Application Gateway .../articles/application-gateway/tutorial-autoscale-ps.md
Medium Priority View Details →
Scanned: 2026-01-27 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The tutorial is heavily focused on Azure PowerShell, with all examples and instructions using PowerShell cmdlets and Windows-specific tools (e.g., New-SelfSignedCertificate, Export-PfxCertificate). There are no Bash, Azure CLI, or Linux/macOS alternatives provided, and certificate creation relies on Windows-only PowerShell modules. This creates friction for Linux/macOS users, who must find their own workarounds for several steps.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all resource creation and configuration steps.
  • Include instructions for creating self-signed certificates on Linux/macOS (e.g., using OpenSSL) and how to export to PFX format.
  • Add notes or links to cross-platform tools for certificate management.
  • Indicate which steps are Windows-specific and offer alternatives where possible.
  • Consider reordering examples so that cross-platform solutions are presented first or alongside Windows/PowerShell options.
GitHub Create Pull Request
Application Gateway Scaling and Zone-redundant Application Gateway v2 ...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority View Details →
Scanned: 2026-01-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides a 'Next steps' link that exclusively references Azure PowerShell for creating an autoscaling, zone-redundant Application Gateway, without mentioning or linking to equivalent Azure CLI or ARM template instructions. This creates a subtle bias toward Windows/PowerShell users, as PowerShell is most commonly used on Windows and is often presented as the default automation tool in Azure documentation.
Recommendations
  • Add links or examples for creating autoscaling, zone-redundant Application Gateway using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include ARM/Bicep template instructions or links for infrastructure-as-code parity.
  • Present cross-platform options (CLI, PowerShell, templates) together or in parallel, rather than PowerShell-only or PowerShell-first.
GitHub Create Pull Request
Application Gateway Migrate from V1 to V2 - Azure Application Gateway ...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority View Details →
Scanned: 2026-01-26 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation for migrating Azure Application Gateway from V1 to V2 is heavily focused on PowerShell-based scripts and workflows, with all examples, instructions, and tooling centered around Azure PowerShell. There are no Bash, Azure CLI, or Linux/macOS-specific instructions or examples provided. The installation and usage patterns (e.g., Install-Script, .ps1 files, PowerShell Gallery) are Windows-centric and may create friction for users on Linux or macOS platforms, who typically use Bash and Azure CLI. The documentation does not mention or provide alternatives for non-Windows environments, nor does it clarify cross-platform compatibility of the provided scripts.
Recommendations
  • Explicitly state whether the PowerShell scripts are cross-platform and can be run on PowerShell Core on Linux/macOS.
  • Provide Azure CLI equivalents for key migration steps, or clarify if such automation is not available.
  • Add Bash shell examples for common operations (e.g., retrieving resource IDs, uploading certificates) using Azure CLI.
  • Include installation and usage instructions for PowerShell on Linux/macOS, or link to official guidance.
  • Mention and link to Azure Cloud Shell as a cross-platform alternative for running PowerShell scripts.
  • Add a section addressing Linux/macOS users, outlining any limitations or required adaptations.
GitHub Create Pull Request
Application Gateway Overview of mutual authentication on Azure Application Gateway .../application-gateway/mutual-authentication-overview.md
Medium Priority View Details →
Scanned: 2026-01-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides configuration instructions for mutual authentication on Azure Application Gateway, with a notable emphasis on Azure PowerShell examples and references. PowerShell instructions are given first and in more detail, while Azure CLI examples are present but less comprehensive. There is no mention of Linux-specific tools or workflows, and the CLI example is minimal compared to the PowerShell section. The 'Next steps' section directs users to a PowerShell-focused guide, further reinforcing the Windows-first approach. No Linux/macOS-specific certificate management or workflow examples are provided.
Recommendations
  • Expand Azure CLI examples to match the detail and coverage of PowerShell instructions, including full configuration steps.
  • Provide explicit guidance or examples for Linux/macOS users, such as using OpenSSL for certificate extraction and management.
  • Ensure that 'Next steps' includes links to both PowerShell and CLI-based guides, or a cross-platform guide.
  • Clarify that both CLI and PowerShell are supported equally for configuration tasks, and highlight any platform-specific considerations.
GitHub Create Pull Request
Application Gateway FAQ on V1 retirement ...ob/main/articles/application-gateway/retirement-faq.md
Medium Priority View Details →
Scanned: 2026-01-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation on Application Gateway V1 retirement and migration to V2 is heavily focused on Azure PowerShell scripts for migration, with no mention of Azure CLI, Bash, or Linux/macOS-compatible tooling. All migration automation references are to PowerShell, and there are no examples or guidance for users on Linux or macOS platforms. This creates friction for non-Windows users who may not have access to PowerShell or prefer cross-platform tools.
Recommendations
  • Provide equivalent migration instructions and scripts using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include Bash or shell script examples for common migration tasks.
  • Explicitly mention platform compatibility for provided scripts, and offer guidance for Linux/macOS users on how to run or adapt the migration process.
  • List both PowerShell and CLI options side-by-side where automation is discussed.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway v2? .../blob/main/articles/application-gateway/overview-v2.md
Medium Priority View Details →
Scanned: 2026-01-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for Azure Application Gateway v2 demonstrates a moderate Windows/PowerShell bias. Key migration and registration/unregistration instructions are provided exclusively using Azure PowerShell commands, with no equivalent Azure CLI (cross-platform) or Bash examples. The 'Next steps' section links to a PowerShell-based tutorial, and PowerShell is referenced before CLI in preview registration instructions. This creates friction for Linux/macOS users who may prefer or require CLI/Bash instructions.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell commands for all registration, migration, and management tasks.
  • Ensure tutorials and quickstarts are available for both PowerShell and Azure CLI workflows, and link to both in 'Next steps'.
  • When listing command examples, present Azure CLI (cross-platform) instructions first or equally with PowerShell.
  • Clarify in each section that both PowerShell and CLI can be used, and link to relevant cross-platform documentation.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway v2? .../blob/main/articles/application-gateway/overview-v2.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page for Azure Application Gateway v2 shows a moderate Windows bias. Migration guidance and registration/unregistration for the Basic SKU preview are provided only with Azure PowerShell commands, and the main tutorial link is PowerShell-focused. There are no Linux/macOS CLI (az CLI) or ARM template examples, and PowerShell is presented as the default method for key operations.
Recommendations
  • Add equivalent Azure CLI (az) command examples for registration, unregistration, and migration tasks, ensuring Linux/macOS users have clear guidance.
  • Include links to ARM template or Bicep deployment guides where relevant.
  • When listing tutorials, offer parity by linking to both PowerShell and Azure CLI versions, or clarify which platforms are supported.
  • Explicitly state that PowerShell commands can be run cross-platform (if true), or provide platform-specific notes.
GitHub Create Pull Request
Application Gateway Migrate from V1 to V2 - Azure Application Gateway ...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation for migrating Azure Application Gateway from V1 to V2 is heavily focused on Azure PowerShell scripts and cmdlets, with all examples and instructions using PowerShell syntax. There is no mention of Bash, Azure CLI, or cross-platform alternatives, nor are there Linux/macOS-specific instructions or examples. The guidance assumes the use of PowerShell modules and tools, which are native to Windows and only recently supported on Linux/macOS, potentially creating friction for non-Windows users.
Recommendations
  • Provide equivalent Azure CLI (az) commands and scripts for all migration steps, including configuration cloning and IP retention.
  • Add explicit instructions for running PowerShell scripts on Linux/macOS, including prerequisites (e.g., installing PowerShell Core, Az modules).
  • Include Bash script examples or references for common migration tasks.
  • Clarify cross-platform support for the provided PowerShell scripts (e.g., test and document compatibility with PowerShell Core on Linux/macOS).
  • Mention Azure Cloud Shell as a cross-platform alternative more prominently, and provide direct links or guidance for using it.
GitHub Create Pull Request
Application Gateway Overview of mutual authentication on Azure Application Gateway .../application-gateway/mutual-authentication-overview.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides configuration instructions and examples for mutual authentication on Azure Application Gateway, with a notable emphasis on Azure PowerShell. PowerShell examples are given in detail, and the 'Next steps' section directs users to a PowerShell-specific guide. While Azure CLI is mentioned and a CLI example is provided, the PowerShell instructions are more comprehensive and appear first. There is no mention of Linux-specific tools or workflows, and no explicit Linux/macOS parity guidance is offered.
Recommendations
  • Ensure CLI examples are as detailed as PowerShell examples, including step-by-step instructions for all major configuration tasks.
  • Add explicit guidance for Linux/macOS users, such as certificate extraction/management using OpenSSL or other cross-platform tools.
  • In the 'Next steps' section, provide links to both PowerShell and CLI guides, or a unified guide with platform-specific tabs.
  • Where possible, avoid presenting PowerShell examples before CLI unless there is a technical reason (e.g., feature parity lag in CLI).
GitHub Create Pull Request
Application Gateway FAQ on V1 retirement ...ob/main/articles/application-gateway/retirement-faq.md
Medium Priority View Details →
Scanned: 2026-01-24 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation repeatedly references Azure PowerShell scripts as the primary migration tooling, with no mention of Azure CLI or Bash alternatives. All automation and migration examples are PowerShell-centric, which may create friction for Linux/macOS users who prefer Bash or Azure CLI. There are no Linux/macOS-specific instructions or parity examples.
Recommendations
  • Provide equivalent Azure CLI or Bash script examples for migration tasks, especially for public IP retention and configuration migration.
  • Explicitly state OS/platform requirements for the PowerShell scripts and link to cross-platform PowerShell installation guides.
  • Add guidance or references for Linux/macOS users on how to perform migration steps using their preferred tools.
  • Where possible, offer downloadable scripts in both PowerShell and Bash/Azure CLI formats.
GitHub Create Pull Request
Application Gateway Scaling and Zone-redundant Application Gateway v2 ...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides a link to a tutorial for creating an autoscaling, zone redundant application gateway using Azure PowerShell, without mentioning or linking to equivalent instructions for Linux/macOS users (e.g., Azure CLI, ARM templates, or Bicep). This suggests a bias toward Windows/PowerShell tooling, potentially creating friction for users on other platforms.
Recommendations
  • Add links or references to equivalent tutorials using Azure CLI, ARM templates, or Bicep, which are cross-platform and commonly used on Linux/macOS.
  • Where PowerShell is mentioned, clarify that Azure CLI or other tools can also be used, and provide examples or links.
  • Ensure that step-by-step guides for key tasks (such as creating an autoscaling, zone redundant application gateway) are available for both PowerShell and CLI/ARM/Bicep.
GitHub Create Pull Request
Application Gateway FAQ on V1 retirement ...ob/main/articles/application-gateway/retirement-faq.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page for Application Gateway V1 retirement and migration to V2 demonstrates a notable Windows bias. Migration instructions and tooling are centered around Azure PowerShell scripts, with no mention of Azure CLI or Bash alternatives. All automation and example references are PowerShell-specific, and there are no Linux/macOS-friendly migration workflows or sample commands provided.
Recommendations
  • Provide equivalent Azure CLI (az) commands and scripts for migration tasks, especially for configuration and public IP retention.
  • Include Bash or shell script examples for common migration scenarios.
  • Clearly state platform requirements for provided scripts, and offer guidance for Linux/macOS users.
  • Reference cross-platform tooling where possible, and clarify any limitations or differences in migration workflows for non-Windows environments.
GitHub Create Pull Request
Application Gateway Migrate from V1 to V2 - Azure Application Gateway ...lob/main/articles/application-gateway/migrate-v1-v2.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily focused on Azure PowerShell scripts and cmdlets for migration, with all examples and instructions using PowerShell syntax. There are no CLI (az), Bash, or Linux/macOS-specific examples or guidance. The installation and usage instructions assume a PowerShell environment, which is native to Windows but only optionally available on Linux/macOS. This creates friction for users on non-Windows platforms who may prefer or require Bash/CLI workflows.
Recommendations
  • Provide equivalent Azure CLI (az) commands and scripts for migration tasks, or clarify if PowerShell is strictly required.
  • Include instructions for running PowerShell scripts on Linux/macOS (e.g., via PowerShell Core), and note any platform-specific caveats.
  • Add Bash or shell script examples where possible, especially for certificate handling and file operations.
  • Explicitly state platform requirements and alternatives at the start of the documentation.
  • Consider linking to cross-platform migration tools or community scripts if official support is limited.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway v2? .../blob/main/articles/application-gateway/overview-v2.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for Azure Application Gateway v2 shows a notable Windows/PowerShell bias. Migration guidance and preview registration/unregistration steps are provided only as Azure PowerShell commands, with no equivalent Azure CLI (bash) or ARM template examples. The main tutorial linked is PowerShell-based, and PowerShell is referenced before any cross-platform alternatives. This creates friction for Linux/macOS users who may prefer or require bash/CLI workflows.
Recommendations
  • Provide Azure CLI (bash) equivalents for all PowerShell commands, especially for migration and preview registration/unregistration steps.
  • Link to or create tutorials using Azure CLI and ARM templates, not just PowerShell.
  • When listing command-line instructions, present cross-platform (CLI) examples before or alongside PowerShell examples.
  • Clarify that PowerShell commands can be run on Linux/macOS, but highlight CLI alternatives for users who do not use PowerShell.
GitHub Create Pull Request
Application Gateway Tutorial: Improve web application access - Azure Application Gateway .../articles/application-gateway/tutorial-autoscale-ps.md
Medium Priority View Details →
Scanned: 2026-01-23 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The tutorial is heavily focused on Azure PowerShell and Windows-specific tooling, such as the use of PowerShell cmdlets and Windows certificate management commands. No equivalent Bash, Azure CLI, or Linux/macOS instructions are provided, and Windows tools (e.g., New-SelfSignedCertificate, Export-PfxCertificate) are used for certificate creation and export. This creates friction for Linux/macOS users, who must find alternative methods to complete key steps.
Recommendations
  • Provide Azure CLI equivalents for all Azure resource creation and management steps.
  • Include instructions for creating self-signed certificates on Linux/macOS (e.g., using OpenSSL) and exporting to PFX format.
  • Add notes or links to cross-platform tools and methods where PowerShell or Windows-specific commands are used.
  • Consider reordering or parallelizing examples so that Linux/macOS methods are presented alongside Windows/PowerShell approaches.
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
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a notable Windows bias. PowerShell commands are consistently used for examples and troubleshooting steps, with Windows-specific tools (e.g., certlm.msc, netstat via cmd) described in detail. Linux equivalents are either omitted or mentioned briefly and after Windows instructions. Many troubleshooting steps and certificate management instructions focus on Windows workflows, making it harder for Linux/macOS users to follow along.
Recommendations
  • Provide equivalent CLI and Bash examples alongside PowerShell commands, especially for network and certificate troubleshooting.
  • Include Linux/macOS workflows for certificate inspection and export (e.g., using OpenSSL, keytool, or certutil).
  • When describing steps like checking listening ports or exporting certificates, offer both Windows and Linux/macOS instructions in parallel.
  • Avoid presenting Windows tools and commands first; alternate or group by platform.
  • Ensure all troubleshooting steps are platform-agnostic or have clear alternatives for non-Windows users.
GitHub Create Pull Request
Application Gateway Azure Application Gateway listener configuration ...rticles/application-gateway/configuration-listeners.md
Medium Priority View Details →
Scanned: 2026-01-14 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, which is primarily a Windows-centric tool. There are no equivalent examples for Azure CLI, Bash, or other cross-platform tools. This creates friction for Linux/macOS users who may not use PowerShell.
Recommendations
  • Add equivalent Azure CLI examples for all configuration tasks currently shown with PowerShell.
  • Explicitly mention that Azure CLI and REST API can be used for these operations, and provide links or examples.
  • Ensure that any code snippets or tool recommendations are presented in a cross-platform manner, or at least provide parity.
GitHub Create Pull Request
Application Gateway Create Azure Application Gateway custom error pages ...blob/main/articles/application-gateway/custom-error.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides configuration instructions for custom error pages in Azure Application Gateway, but only includes Azure PowerShell examples and links. There are no CLI (az), Bash, or Linux/macOS-specific instructions, and PowerShell is presented as the sole automation method. This creates friction for users on Linux or macOS, who may prefer or require cross-platform tools.
Recommendations
  • Add equivalent Azure CLI (az) examples for configuring custom error pages at both global and listener levels.
  • Explicitly mention that Azure PowerShell is available cross-platform, but provide Bash and CLI syntax for parity.
  • Include links to Azure CLI documentation for relevant commands.
  • Consider reordering or presenting CLI and PowerShell examples side-by-side to avoid Windows-first impression.
GitHub Create Pull Request
Application Gateway Quickstart: Direct web traffic using the portal ...in/articles/application-gateway/quick-create-portal.md
Medium Priority View Details →
Scanned: 2026-01-14 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 page demonstrates a notable Windows bias. VM creation is shown only for Windows Server, and IIS installation/testing is exclusively via Azure PowerShell using Windows-specific commands. No Linux VM creation or Linux web server (e.g., Apache, Nginx) examples are provided, nor are Bash/Azure CLI commands for backend setup. The documentation assumes Windows as the default platform for backend servers and testing, which may create friction for Linux users.
Recommendations
  • Include parallel instructions for creating a Linux VM (e.g., Ubuntu) in the backend pool.
  • Provide examples for installing a Linux web server (such as Apache or Nginx) using Azure CLI or Bash scripts.
  • Show how to test the application gateway using a Linux backend (e.g., curl to Apache/Nginx default page).
  • Present both Windows and Linux options for backend setup and testing, or clarify that either OS is supported.
  • Offer Azure CLI or Bash alternatives for backend configuration and extension installation.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway v2? .../blob/main/articles/application-gateway/overview-v2.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias, primarily through its reliance on Azure PowerShell scripts and cmdlets for migration and preview registration tasks. The only provided command-line examples use PowerShell-specific cmdlets (e.g., Set-AzContext, Get-AzProviderFeature), with no equivalent Azure CLI (az) or Bash/Linux-native instructions. This could create friction for Linux/macOS users who may not have PowerShell installed or prefer Bash/CLI workflows.
Recommendations
  • Provide equivalent Azure CLI (az) command examples for all PowerShell scripts and registration/unregistration steps.
  • Include explicit notes or links for Linux/macOS users on how to perform migration and management tasks using their preferred tools.
  • When referencing scripts or tools, clarify if they are cross-platform or provide alternatives if they are Windows-only.
  • Ensure that tutorials and 'next steps' include both PowerShell and Azure CLI/Bash options.
GitHub Create Pull Request
Application Gateway Diagnostic logs ...application-gateway/application-gateway-diagnostics.md
Medium Priority View Details →
Scanned: 2026-01-14 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 moderate Windows bias. The only CLI example for enabling logging is given using PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS-compatible commands. The log conversion tip references a C#/.NET tool (Visual Studio), which is Windows-centric. There are no Linux/macOS-specific instructions or parity examples, and the CLI workflow is presented before the portal workflow. This may create friction for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention Bash or shell scripting options for automation, or clarify that PowerShell Core is available cross-platform.
  • Reference log conversion tools that work on Linux/macOS, such as Python scripts or open-source utilities, in addition to the C#/.NET option.
  • Explicitly state platform compatibility for each tool or command.
  • Present CLI and portal workflows in parallel, or clarify that both are available regardless of OS.
GitHub Create Pull Request
Application Gateway Backend health ...lication-gateway/application-gateway-backend-health.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides explicit PowerShell examples for viewing backend health, with the PowerShell method described before Azure CLI. No Linux/macOS-specific shell examples (e.g., Bash) or troubleshooting tools are mentioned, and the CLI example is generic without platform-specific context. There is a slight preference for Windows tools and patterns, and Linux users may need to infer their own workflows.
Recommendations
  • Add Bash or shell script examples for Linux/macOS users, especially for Azure CLI usage.
  • Clarify that Azure CLI commands work cross-platform and provide troubleshooting steps relevant to Linux environments.
  • Balance the order of examples by presenting CLI and PowerShell methods together or listing CLI first.
  • Mention platform-agnostic troubleshooting tools or note any platform-specific limitations.
GitHub Create Pull Request
← Previous Page 29 of 40 Next →