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 801-825 of 981 flagged pages
Application Gateway Quickstart: Direct web traffic using Bicep ...ain/articles/application-gateway/quick-create-bicep.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment, validation, and cleanup tasks. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is mentioned in every example tab. There is no mention of Linux-specific tools or shell patterns (such as Bash), nor are there any explicit Linux VM management or SSH examples. The use of PowerShell may suggest a Windows bias, especially for users who are not on Windows platforms.
Recommendations
  • Clarify that Azure CLI is cross-platform and can be used on Windows, macOS, and Linux.
  • Add explicit Bash shell examples or notes for Linux/macOS users, especially for command-line tasks.
  • Mention SSH as a method to connect to Linux VMs, if relevant to the scenario.
  • If PowerShell is included, consider noting that PowerShell Core is available cross-platform, or provide Bash alternatives.
  • Ensure that any VM configuration steps (such as IIS setup) also mention Linux alternatives (e.g., Apache or Nginx) if the backend could be Linux.
GitHub Create Pull Request
Application Gateway Container networking with Azure Application Gateway for Containers ...ication-gateway/for-containers/container-networking.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the 'Next steps' section, where the link to 'Deploy ALB Controller' defaults to Windows instructions (install-helm-windows tab) and does not mention Linux or cross-platform alternatives. There are no explicit Linux or bash examples, and Windows tooling is implicitly prioritized by the tab default.
Recommendations
  • Provide equal visibility and instructions for Linux/macOS environments alongside Windows, especially in quickstart and deployment guides.
  • Ensure links to installation guides default to a cross-platform or neutral tab, or clearly offer both Windows and Linux/macOS tabs.
  • Include bash or Linux CLI examples where relevant, not just Windows/PowerShell.
  • Review all referenced quickstart and deployment documentation to ensure Linux parity in examples and tooling.
GitHub Create Pull Request
Application Gateway Azure Application Gateway configuration overview ...articles/application-gateway/configuration-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page lists PowerShell (a Windows-centric tool) before Azure CLI in the 'Next steps' section, suggesting a Windows-first approach. While Azure CLI is mentioned, there are no explicit Linux-specific examples or references, and PowerShell is given prominence, which may indicate a bias toward Windows users.
Recommendations
  • List Azure CLI before PowerShell in 'Next steps', as CLI is cross-platform and widely used on Linux.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows.
  • Provide examples or links for configuring Application Gateway using Linux-native tools or environments.
  • Add a note clarifying platform compatibility for each tool (PowerShell vs Azure CLI).
  • Consider including walkthroughs or screenshots from Linux environments where relevant.
GitHub Create Pull Request
Application Gateway Azure Application Gateway request routing rules configuration ...ication-gateway/configuration-request-routing-rules.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by listing PowerShell-based instructions and links before their Azure CLI equivalents in several places. PowerShell is primarily a Windows tool, while Azure CLI is cross-platform. There are no Linux-specific examples or tools mentioned, and no explicit parity between Windows and Linux workflows is established.
Recommendations
  • Present Azure CLI and PowerShell instructions side-by-side, or list CLI first to emphasize cross-platform support.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide examples for Linux shell usage where relevant.
  • Add a section or callout for Linux users, highlighting any platform-specific considerations or best practices.
  • Ensure that all referenced guides (e.g., redirect guides) include both PowerShell and CLI examples, and avoid implying PowerShell is the default or preferred method.
GitHub Create Pull Request
Application Gateway Configure Azure Monitor alerts for Application Gateway ...application-gateway/configure-alerts-with-templates.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by exclusively referencing the Azure Portal and linking to procedures that prioritize CLI, PowerShell, and ARM template usage without mentioning Linux-specific tools or workflows. There are no examples or guidance for Linux users (e.g., Azure CLI on bash, shell scripting, or cross-platform deployment methods). The 'Deploy to Azure' button links directly to the Azure Portal, which is platform-agnostic but often associated with Windows workflows, and the referenced procedure page lists PowerShell before CLI, reinforcing a Windows-first pattern.
Recommendations
  • Add explicit examples using Azure CLI on Linux (bash) for deploying ARM templates and configuring alerts.
  • Include instructions or links for using cross-platform tools (e.g., Azure CLI, REST API) to create and manage alert rules.
  • Ensure referenced procedures present CLI and PowerShell options side-by-side, or lead with CLI for platform neutrality.
  • Clarify that the Azure Portal and ARM templates are accessible from any OS, and mention Linux compatibility where relevant.
GitHub Create Pull Request
Application Gateway Quickstart: Create Application Gateway for Containers managed by ALB Controller ...ation-gateway-for-containers-managed-by-alb-controller.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides command-line examples exclusively using Azure CLI and kubectl, which are cross-platform tools. However, there is implicit Windows bias in the variable assignment syntax and command formatting (e.g., use of single quotes, reliance on bash-style variable expansion, and lack of explicit mention of Linux or macOS environments). There are no PowerShell or Windows-specific tools, but the examples do not clarify compatibility or provide parallel instructions for Linux/macOS users, nor do they address common issues such as line endings or shell differences.
Recommendations
  • Explicitly state that the Azure CLI and kubectl commands work on Linux, macOS, and Windows (with WSL or bash).
  • Provide notes or examples for running commands in PowerShell, CMD, and bash, especially for variable assignment and multi-line commands.
  • Clarify any platform-specific requirements (e.g., use of tr -d '\r' for line endings in Windows).
  • Add troubleshooting tips for common cross-platform issues, such as differences in quoting, environment variable syntax, and command chaining.
  • Consider adding a 'Platform compatibility' section to highlight any differences or requirements for Linux, macOS, and Windows users.
GitHub Create Pull Request
Application Gateway Quickstart: Deploy Application Gateway for Containers ALB Controller ...ploy-application-gateway-for-containers-alb-controller.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides installation instructions for Helm on both Windows and Linux, but the Windows instructions (using winget) are presented first, and the Windows-specific tool (winget) is mentioned explicitly. The Linux instructions are present and functional, but Windows is given priority in ordering and tool mention. No PowerShell-heavy bias or missing Linux examples are found, as most commands are cross-platform Azure CLI and Bash. However, the documentation could improve parity by balancing the order and detail of platform-specific instructions.
Recommendations
  • Present Windows and Linux installation instructions for Helm in parallel, or alternate which platform is listed first.
  • Mention Linux package managers (e.g., apt, yum, dnf) as alternatives for Helm installation, not just the curl script.
  • Provide explicit guidance for running Azure CLI commands on Linux (e.g., ensure az CLI is installed and available in PATH).
  • Avoid implying Windows as the default by listing it first; use neutral phrasing or alphabetical order.
  • Include a note that all Azure CLI and Helm commands are cross-platform unless otherwise specified.
GitHub Create Pull Request
Application Gateway Application Gateway Ingress Controller troubleshooting ...application-gateway/ingress-controller-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page consistently recommends Azure Cloud Shell as the primary troubleshooting environment and provides all command-line examples using Bash. While Bash is cross-platform, the documentation does not mention or provide guidance for running commands on native Linux or macOS terminals, nor does it address differences in local environments versus Cloud Shell. There are no references to Windows-specific tools (e.g., PowerShell), but the documentation assumes the use of Azure Cloud Shell, which is more commonly used by Windows users and may not be the default for Linux administrators. There is a lack of explicit Linux parity, as the instructions do not discuss how to perform troubleshooting steps outside of Cloud Shell or on Linux systems.
Recommendations
  • Add explicit instructions for running troubleshooting commands on native Linux and macOS terminals, including any prerequisites (such as installing kubectl, Azure CLI, etc.).
  • Clarify that Bash commands provided can be run on any Bash-compatible shell, not just Azure Cloud Shell.
  • Include a section comparing troubleshooting in Azure Cloud Shell versus local Linux/macOS environments, highlighting any differences or additional steps required.
  • If relevant, mention how to perform troubleshooting using PowerShell for Windows users to ensure parity for all platforms.
  • Avoid language that implies Azure Cloud Shell is the only or preferred method, and instead present it as one of several options.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway ...ocs/blob/main/articles/application-gateway/overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents Azure PowerShell as a primary method for creating an Application Gateway, listing it before Azure CLI in the 'Next steps' section. This ordering, along with explicit mention of PowerShell, subtly prioritizes Windows-centric tooling and patterns. While Azure CLI is included (which is cross-platform), the emphasis and ordering suggest a Windows-first approach. There are no Linux-specific examples or references to Linux-native tools or shell environments.
Recommendations
  • List Azure CLI before PowerShell in example and quickstart links to emphasize cross-platform parity.
  • Explicitly mention that Azure CLI works natively on Linux/macOS and Windows, and provide shell/bash examples where appropriate.
  • Add a note or section highlighting Linux/macOS usage, including any relevant differences or tips for those platforms.
  • Ensure future tutorials and quickstarts provide equal coverage and visibility for Linux users, possibly including screenshots or walkthroughs using Linux environments.
GitHub Create Pull Request
Application Gateway Backend health ...lication-gateway/application-gateway-backend-health.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents PowerShell as the first code example for programmatic access to backend health, followed by Azure CLI. PowerShell is a Windows-centric tool, and its precedence may suggest a Windows bias. There are no explicit Linux shell examples (e.g., Bash), nor are Linux troubleshooting tools or patterns mentioned. The documentation does not provide parity in example ordering or alternative Linux-native approaches.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first, as it is cross-platform.
  • Include Bash shell examples for REST API calls using curl or httpie, demonstrating how Linux users can retrieve backend health.
  • Explicitly mention that Azure CLI works on Windows, Linux, and macOS to reinforce cross-platform support.
  • Add troubleshooting steps or tool recommendations relevant to Linux environments, such as using openssl or curl for backend server certificate checks.
  • Ensure that documentation links and examples do not assume a Windows environment by default.
GitHub Create Pull Request
Application Gateway Azure Application Gateway listener configuration ...rticles/application-gateway/configuration-listeners.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a PowerShell-only example for enabling HTTP/2 support on Application Gateway listeners, with no equivalent example for Azure CLI, Bash, or other Linux-friendly tools. This suggests a bias towards Windows users and administrators, as PowerShell is primarily associated with Windows environments. No Linux-specific tools or commands are mentioned, and the only code snippet is Windows-centric.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell snippets, especially for enabling HTTP/2 support.
  • Include Bash or shell script examples where relevant, to assist Linux users.
  • Explicitly mention cross-platform tools and approaches (e.g., Azure CLI, REST API) alongside PowerShell.
  • Review other sections for similar single-platform examples and ensure parity in documentation for both Windows and Linux users.
GitHub Create Pull Request
Application Gateway Azure Application Gateway request routing rules configuration ...ication-gateway/configuration-request-routing-rules.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page shows mild Windows bias by listing PowerShell-based instructions before Azure CLI equivalents in multiple places, and by providing explicit PowerShell links for key tasks. While Azure CLI is mentioned, PowerShell (a Windows-centric tool) is consistently listed first, and there are no Linux-specific examples or references.
Recommendations
  • Alternate the order of PowerShell and Azure CLI instructions so that CLI (cross-platform) is sometimes listed first.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide examples or links for Linux users.
  • Add a short section or note clarifying that all CLI instructions are cross-platform, and provide sample commands for Linux shells (e.g., bash).
  • Ensure parity in documentation by providing equivalent walkthroughs or screenshots for Linux environments where relevant.
GitHub Create Pull Request
Application Gateway Troubleshoot an Application Gateway in Azure – ILB ASE | Microsoft Docs ...gateway-internal-load-balancer-app-service-environment.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation describes troubleshooting steps for Azure Application Gateway with ILB ASE but omits explicit examples or instructions for Linux environments. The certificate export process is described generically (using a browser), but does not mention Linux command-line tools (e.g., OpenSSL) or provide Linux-specific guidance. There is an implicit bias toward Windows workflows, as no Linux alternatives or parity are provided.
Recommendations
  • Add Linux-specific instructions for exporting certificates, such as using OpenSSL commands.
  • Include examples of troubleshooting using Linux command-line tools alongside browser-based or Windows methods.
  • Explicitly mention that the steps apply to both Windows and Linux, or clarify any platform-specific differences.
  • Provide parity in examples and tool recommendations for both Windows and Linux environments.
GitHub Create Pull Request
Application Gateway Container networking with Azure Application Gateway for Containers ...ication-gateway/for-containers/container-networking.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Next steps' section, where the link to the ALB Controller deployment quickstart explicitly defaults to the Windows installation tab (install-helm-windows). There are no Linux-specific examples, instructions, or parity in tooling references throughout the page, and no mention of Linux shell commands or patterns for deployment or configuration.
Recommendations
  • Update the 'Next steps' link to either a neutral tab (not defaulting to Windows) or provide both Windows and Linux installation tabs equally.
  • Ensure that all referenced quickstarts and guides include Linux (bash) examples alongside Windows (PowerShell) instructions.
  • Explicitly mention Linux compatibility and provide Linux-specific steps or notes where relevant, especially in deployment and configuration sections.
  • Review referenced media and diagrams for OS-neutral terminology and visuals.
GitHub Create Pull Request
Application Gateway Quickstart: Create Application Gateway for Containers managed by ALB Controller ...ation-gateway-for-containers-managed-by-alb-controller.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively using Azure CLI commands (which are most commonly installed and used on Windows, though available cross-platform) and referencing Azure-specific resource management patterns. There are no Linux-specific examples, nor is there any mention of Linux shell alternatives or considerations for Linux users. The instructions and examples assume the use of Azure CLI and Bash, but do not address Linux-specific nuances or provide parity for Linux-native tools or environments.
Recommendations
  • Explicitly state that all CLI examples work on Linux, macOS, and Windows, and provide installation instructions for Azure CLI on Linux.
  • Include notes or examples for Linux users, such as handling environment variables, line endings, and shell differences.
  • Mention cross-platform compatibility for all commands and tools used, and provide troubleshooting tips for common Linux issues (e.g., permissions, path differences).
  • Where possible, offer alternative commands using native Linux tools (e.g., curl, jq) for resource querying and manipulation.
  • Add a section or callout for Linux users to ensure parity and inclusivity in the documentation.
GitHub Create Pull Request
Application Gateway Application Gateway Ingress Controller troubleshooting ...application-gateway/ingress-controller-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently recommends Azure Cloud Shell as the troubleshooting environment and provides all command-line examples in Bash, which is cross-platform. However, there is a strong emphasis on using Azure Cloud Shell, which is most commonly accessed via a browser on Windows, and there is no mention of Linux-native workflows, local Linux terminals, or alternative shells. There are no PowerShell-specific examples, but the documentation does not acknowledge or provide guidance for users who may prefer or require troubleshooting from a local Linux environment or other non-Azure shells.
Recommendations
  • Explicitly mention that all Bash commands work natively on Linux terminals and macOS, not just in Azure Cloud Shell.
  • Provide instructions or notes for users who wish to run troubleshooting steps from their own Linux or macOS environments, including any prerequisites (e.g., Azure CLI, kubectl).
  • Clarify that Azure Cloud Shell is cross-platform and can be accessed from any OS, but users can also use their local shell if preferred.
  • Add troubleshooting steps or examples for users who may be running AKS clusters from Linux workstations, including how to authenticate and access Azure resources from a local shell.
  • Consider including a brief section comparing Azure Cloud Shell, Windows PowerShell, and Linux/macOS Bash environments for troubleshooting, to ensure parity and inclusivity.
GitHub Create Pull Request
Application Gateway Hosting multiple sites on Azure Application Gateway ...articles/application-gateway/multiple-site-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by consistently mentioning Azure PowerShell before Azure CLI when describing configuration steps and examples. PowerShell is referenced in feature explanations and in the 'Next steps' section prior to CLI, suggesting a prioritization of Windows-centric tooling. While Azure CLI is included and no examples are exclusively Windows-only, the ordering and emphasis favor PowerShell, which is more commonly used on Windows platforms.
Recommendations
  • Alternate the order of Azure PowerShell and Azure CLI references throughout the documentation, or list CLI first in some sections to balance platform representation.
  • Include explicit notes that both Azure PowerShell and Azure CLI are cross-platform, and provide links to installation guides for Linux and macOS users.
  • Add example commands for both Azure PowerShell and Azure CLI side-by-side in relevant sections, highlighting their usage on different operating systems.
  • Consider including Bash scripts or Linux-specific usage scenarios where appropriate, especially in step-by-step guides.
  • Ensure that screenshots and UI references do not imply a Windows-only environment unless necessary.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway ...ocs/blob/main/articles/application-gateway/overview.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page lists Azure PowerShell as a primary method for creating and managing Application Gateway, and mentions it before Azure CLI. This ordering and emphasis can be interpreted as a subtle Windows bias, as PowerShell is traditionally associated with Windows environments. There are no explicit Linux-only examples or tools highlighted, and the CLI is mentioned after PowerShell, which may suggest a prioritization of Windows-centric tools.
Recommendations
  • Present Azure CLI and Azure PowerShell options together, or list Azure CLI first to reflect its cross-platform nature.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and provide parity in examples and quickstarts for both CLI and PowerShell.
  • Add a note or section highlighting Linux compatibility and usage patterns, such as scripting with Bash or integrating with Linux-based automation tools.
  • Ensure that screenshots, walkthroughs, and sample commands are balanced between Windows and Linux environments.
GitHub Create Pull Request
Application Gateway Quickstart: Direct web traffic using Bicep ...ain/articles/application-gateway/quick-create-bicep.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment, validation, and cleanup, but PowerShell is featured equally alongside CLI, and no Linux-specific shell or tool examples (such as Bash scripting, SSH, or Linux VM configuration) are provided. The configuration of backend VMs references IIS and web pages, which implies Windows VMs, with no mention of Linux alternatives (e.g., Apache, Nginx). There is no explicit Linux bias, but the lack of Linux-specific examples or parity in backend configuration demonstrates a subtle Windows-first approach.
Recommendations
  • Include Linux VM configuration steps (e.g., install Apache or Nginx) alongside IIS examples.
  • Add Bash shell examples where appropriate, especially for scripting or automation.
  • Clarify that Azure CLI commands work cross-platform and provide explicit instructions for Linux/Mac users (e.g., use Bash, SSH).
  • Mention Linux VM images as alternatives in the Bicep template or deployment steps.
  • Provide links to Linux-focused tutorials or documentation in the 'Next steps' section.
GitHub Create Pull Request
Application Gateway Listener TLS certificate management in Application Gateway ...cles/application-gateway/ssl-certificate-management.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by listing PowerShell commands before Azure CLI commands when describing how to view SSL certificates. This ordering implicitly prioritizes Windows tooling. There are no Linux-specific examples, nor is there mention of Linux-native tools or workflows. The only command-line examples given are PowerShell and Azure CLI, both cross-platform, but PowerShell is listed first, which may suggest a Windows-centric approach.
Recommendations
  • Present Azure CLI examples before PowerShell, as Azure CLI is more commonly used on Linux and macOS.
  • Explicitly state that both PowerShell and Azure CLI are cross-platform, and provide installation/use guidance for Linux users.
  • Add a brief example or note on how Linux users can manage certificates (e.g., using Azure CLI from Bash, or referencing certificate file formats and tools common on Linux).
  • Avoid language or ordering that implies Windows is the default or preferred platform.
GitHub Create Pull Request
Application Gateway Azure Application Gateway configuration overview ...articles/application-gateway/configuration-overview.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates Windows bias by listing PowerShell (a Windows-centric tool) as a primary method for creating an Application Gateway before mentioning the Azure CLI, which is cross-platform and commonly used on Linux. The 'Next steps' section presents PowerShell before Azure CLI, suggesting a preference for Windows tooling. No Linux-specific examples or tools are provided, and there is no mention of Bash scripting or Linux command-line patterns.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
  • Include explicit Bash or Linux shell examples where relevant, especially for command-line operations.
  • Add notes or sections highlighting Linux compatibility and usage patterns to ensure parity.
  • Avoid listing Windows-centric tools (like PowerShell) before cross-platform alternatives unless contextually justified.
  • Where possible, provide links to both PowerShell and CLI documentation in parallel, rather than sequentially.
GitHub Create Pull Request
Application Gateway What is Azure Application Gateway ...ocs/blob/main/articles/application-gateway/overview.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page lists Azure PowerShell (a Windows-centric tool) before Azure CLI in the 'Next steps' section, and references PowerShell as a primary method for creating Application Gateways. This ordering and emphasis may suggest a bias toward Windows environments and tools, potentially making Linux users feel secondary. No explicit Linux-only examples or tools are mentioned, and there is no discussion of platform-specific considerations.
Recommendations
  • List Azure CLI before Azure PowerShell in example and quickstart links, as CLI is cross-platform and widely used on Linux.
  • Explicitly mention that Azure CLI is available and supported on Linux, macOS, and Windows.
  • Include examples or notes for Linux users, such as shell commands or environment setup tips.
  • Avoid implying PowerShell is the default or preferred method; present CLI and PowerShell as equal options.
  • Add a section or note about platform parity, reassuring users that all features and management options are available on Linux.
GitHub Create Pull Request
Application Gateway Backend health ...lication-gateway/application-gateway-backend-health.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides explicit PowerShell examples and mentions PowerShell before Azure CLI, which is more cross-platform. There are no Linux-specific tools or troubleshooting patterns referenced, and no mention of Bash or Linux shell equivalents. The troubleshooting tools and examples are platform-neutral, but the scripting guidance leans toward Windows/PowerShell.
Recommendations
  • Add Bash or shell script examples for Linux users alongside PowerShell examples.
  • Mention Azure CLI before or alongside PowerShell, emphasizing its cross-platform nature.
  • Include troubleshooting steps or links relevant to Linux environments (e.g., using curl, openssl for certificate checks).
  • Clarify that PowerShell Core is available on Linux, or provide guidance for Linux users where relevant.
GitHub Create Pull Request
Application Gateway Azure Application Gateway Backend Settings configuration ...les/application-gateway/configuration-http-settings.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page does not provide any OS-specific configuration examples, but it does mention PowerShell and CLI support for certain features, with PowerShell listed first. There are no Linux-specific tools or examples, and no explicit parity between Windows and Linux command-line usage. The absence of Linux shell examples or references to Linux tools (e.g., Bash, OpenSSL) suggests a mild Windows bias.
Recommendations
  • When mentioning command-line support, list Azure CLI and Bash examples alongside PowerShell, and avoid listing PowerShell first unless it is the most widely used option.
  • Provide configuration examples using both PowerShell and Bash/Azure CLI to ensure parity for Linux users.
  • Reference cross-platform tools (such as OpenSSL for certificate management) where relevant, and clarify any OS-specific steps.
  • Explicitly state that all features are available and supported on both Windows and Linux platforms, if true.
  • Add links or sections for Linux-specific troubleshooting or configuration steps, especially for certificate handling and scripting.
GitHub Create Pull Request
Application Gateway Configure Azure Monitor alerts for Application Gateway ...application-gateway/configure-alerts-with-templates.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing the Azure Portal and linking to procedures that prioritize CLI, PowerShell, and ARM template usage without explicitly mentioning or providing Linux-specific examples or alternatives (such as Azure CLI on Bash or deployment via Linux shell). The 'Deploy to Azure' button directs users to the Azure Portal, which is platform-agnostic but often associated with Windows workflows. There are no examples or instructions tailored for Linux users, such as Bash scripts or Linux command-line usage.
Recommendations
  • Include explicit Linux/Bash examples for deploying ARM templates, such as using Azure CLI commands in a Bash shell.
  • Provide instructions or links for using the Azure CLI on Linux, alongside PowerShell and Portal methods.
  • Clarify that the Azure Portal and ARM templates are platform-agnostic, and highlight any differences or considerations for Linux users.
  • Add sample deployment commands for both Windows (PowerShell) and Linux (Bash/Azure CLI) to ensure parity.
GitHub Create Pull Request
← Previous Page 33 of 40 Next →