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 201-225 of 981 flagged pages
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/custom-error.md ...blob/main/articles/application-gateway/custom-error.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell examples for configuring custom error pages, without mentioning or providing equivalent Azure CLI, Bash, or Linux-native instructions. The 'devx-track-azurepowershell' tag and references to PowerShell cmdlets reinforce the focus on Windows tooling. No Linux or cross-platform command-line examples are present, and PowerShell is introduced as the primary automation method before any alternatives.
Recommendations
  • Add equivalent Azure CLI examples for both global and listener-level custom error page configuration, using Bash syntax.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux, macOS, and Windows users.
  • Include links to Azure CLI documentation for relevant commands (e.g., az network application-gateway update).
  • Consider reordering sections so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
  • Update metadata and custom tags to reflect cross-platform support, not just PowerShell.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/diagnostics.md ...cles/application-gateway/for-containers/diagnostics.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides detailed instructions and code samples for enabling diagnostic logs using PowerShell, a Windows-centric tool, without offering equivalent examples for Linux or cross-platform CLI tools (such as Azure CLI or Bash). The PowerShell example is presented as the only command-line option, and Windows tools (Excel, Power BI) are mentioned for log viewing, with no mention of Linux-native alternatives. This creates a bias toward Windows users and may hinder Linux users from easily following the documentation.
Recommendations
  • Add equivalent Azure CLI and Bash examples for enabling diagnostic logs, ensuring Linux users have clear, actionable instructions.
  • Mention Linux-native tools for log viewing, such as jq, grep, or open-source dashboard solutions, alongside Excel and Power BI.
  • Present cross-platform command-line options (Azure CLI, REST API) before or alongside PowerShell to avoid Windows-first ordering.
  • Explicitly state that the steps and tools are available on both Windows and Linux where applicable, or provide platform-specific tabs for instructions.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. It exclusively uses Windows Server virtual machines for backend examples, provides only PowerShell commands for configuration (specifically for installing IIS), and refers to Windows-specific tools and file paths (such as editing the hosts file at c:\Windows\System32\drivers\etc and using DOS commands like ipconfig). There are no Linux VM examples, nor are there instructions for installing a web server or editing hosts files on Linux systems. The documentation assumes the reader is using Windows throughout, both for backend servers and for local machine operations.
Recommendations
  • Include parallel instructions for deploying Linux-based backend VMs (e.g., Ubuntu), including steps for installing Apache or Nginx.
  • Provide Linux shell commands (bash) for installing web servers and editing the /etc/hosts file.
  • Show both Windows and Linux examples for host file editing and DNS cache flushing (e.g., using systemd-resolve or service networking restart).
  • Offer Azure CLI or Bash Cloud Shell alternatives to PowerShell commands.
  • Clarify that Application Gateway supports both Windows and Linux backend servers, and demonstrate both in the tutorial.
  • Avoid using Windows-specific screenshots and file paths exclusively; include Linux equivalents where appropriate.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/how-to-tcp-tls-proxy.md ...n/articles/application-gateway/how-to-tcp-tls-proxy.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows environments. It exclusively uses a Windows-based SQL Server VM as the backend example, references only Windows Server images, and assumes the use of SQL Server Management Studio (a Windows-only tool) for client connectivity. There are no instructions or examples for deploying a Linux-based SQL Server VM, nor for connecting from Linux clients using cross-platform tools. The documentation does not mention Linux alternatives or provide parity for users operating in non-Windows environments.
Recommendations
  • Include instructions and screenshots for deploying a SQL Server VM on Linux (e.g., Ubuntu with SQL Server 2022).
  • Provide examples for connecting to the SQL Server backend using cross-platform tools such as Azure Data Studio, sqlcmd, or other Linux-compatible SQL clients.
  • Mention Linux-based deployment options in the VM creation steps, and clarify that both Windows and Linux are supported.
  • Add a section or callout highlighting differences or considerations when using Linux VMs as backend targets for Application Gateway.
  • Ensure that cleanup and monitoring instructions are applicable to both Windows and Linux environments.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/troubleshooting-guide.md ...cation-gateway/for-containers/troubleshooting-guide.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows examples for filtering logs, but the Windows example (using findstr) is presented after the Linux example (using grep). The use of 'cli' for Windows and explicit mention of Windows-specific tools (findstr) shows some Windows bias. However, the majority of commands and troubleshooting steps are platform-neutral (kubectl, helm), and Linux is referenced first in the tabbed examples. There are no missing Linux examples, but Windows tools are mentioned explicitly.
Recommendations
  • Ensure that Linux and Windows examples are presented with equal prominence, possibly using side-by-side tabs or clear headings.
  • Consider providing macOS examples if relevant, or clarifying that Linux commands generally work on macOS.
  • Where possible, use platform-neutral commands or highlight differences only when necessary.
  • Avoid referring to Windows tools (e.g., findstr) without also mentioning their Linux equivalents (e.g., grep), and vice versa.
  • Add a note clarifying that most commands are cross-platform, and specify any platform-specific caveats.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/http-response-codes.md ...in/articles/application-gateway/http-response-codes.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific authentication (NTLM), linking to Windows documentation first, and providing IIS (Windows web server) configuration guidance before mentioning Nginx (Linux web server). There are no Linux-specific troubleshooting examples, and Linux tools or patterns are only briefly mentioned after Windows equivalents.
Recommendations
  • Provide Linux-specific authentication troubleshooting examples (e.g., Kerberos, PAM, etc.) alongside NTLM.
  • Include Apache and other common Linux web server configuration guidance for time-out and error handling, not just Nginx.
  • Present Linux and Windows examples in parallel, or alternate the order to avoid Windows-first bias.
  • Reference Linux documentation (e.g., official Nginx, Apache docs) with equal prominence to Windows/IIS links.
  • Add troubleshooting steps and examples using Linux command-line tools (curl, journalctl, systemctl) where appropriate.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Several command examples use PowerShell syntax and variables, especially in identity and role assignment steps, rather than pure Bash or cross-platform shell. PowerShell examples are provided without Linux/Bash equivalents, and the use of PowerShell variables and scripting patterns may be unfamiliar or unsupported on Linux/macOS. The backup instructions reference PowerShell scripts as part of the exported template, and the Azure Cloud Shell is mentioned as the preferred environment, which is cross-platform but often defaults to a Windows-like experience. There are no explicit Linux-only examples, and PowerShell commands are presented before or instead of Bash alternatives in key steps.
Recommendations
  • Provide Bash equivalents for all PowerShell command examples, especially for identity and role assignment steps.
  • Avoid using PowerShell-specific variable syntax (e.g., $variable) in examples; use POSIX-compliant shell syntax where possible.
  • Clearly indicate which commands are cross-platform and which are Windows-specific; group examples by platform if necessary.
  • Reference Linux tools/scripts in backup and restore instructions, not just PowerShell.
  • Ensure that all steps can be performed in a standard Linux/macOS terminal, not just Azure Cloud Shell or Windows PowerShell.
  • Add a note or section for Linux/macOS users, clarifying any differences in command usage or environment setup.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ingress-controller-troubleshoot.md ...application-gateway/ingress-controller-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows/Azure environments by exclusively referencing Azure Cloud Shell for all command-line interactions, without mentioning or providing instructions for local Linux or macOS terminals. All examples assume use of Azure Cloud Shell, which is a Microsoft-managed environment, and there is no discussion of running commands from a native Linux shell or alternative platforms. There are no PowerShell-specific commands, but the documentation implicitly prioritizes Windows/Azure tooling and does not address Linux parity.
Recommendations
  • Provide explicit instructions or notes for users running commands from local Linux or macOS terminals, including any prerequisites or differences in environment setup.
  • Mention that all kubectl and curl commands are cross-platform and can be run from any terminal with the appropriate tools installed, not just Azure Cloud Shell.
  • Include a section or callout for users who prefer to use their own local shell (Linux, macOS, or Windows) rather than Azure Cloud Shell, outlining any necessary authentication steps (e.g., az login) and environment configuration.
  • Where screenshots show Azure Cloud Shell, consider adding equivalent terminal output from a generic Linux shell to reinforce cross-platform compatibility.
  • Clarify that Azure Cloud Shell is a convenience but not a requirement, and that all troubleshooting steps can be performed from any supported OS with the right tools.
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-09 00:34
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 command-line operations, referencing Azure PowerShell and CLI together but exclusively showing PowerShell commands. There are no Bash or Linux shell examples, and PowerShell is mentioned before CLI or ARM templates in most cases. The lack of Linux-native command-line instructions (e.g., Bash, az CLI) may hinder parity for Linux users.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell command snippets, especially for certificate referencing and managed identity configuration.
  • Explicitly mention and demonstrate how Linux users can perform the same operations using Bash and Azure CLI.
  • Where multiple tools are supported (PowerShell, CLI, ARM templates, Bicep), present examples for each, or at least alternate the order so Windows tools are not always first.
  • Include notes or links to platform-specific guidance for both Windows and Linux environments.
  • Review all step-by-step instructions to ensure they are not implicitly tailored to Windows users (e.g., screenshots, terminology).
GitHub Create Pull Request
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates bias towards Windows environments by exclusively using IIS (a Windows web server) for backend validation, referencing Azure PowerShell for resource cleanup, and omitting Linux-based examples or alternatives (such as Nginx/Apache for backend VMs or Azure CLI/Bash for resource management). No Linux-specific instructions or parity are provided for deployment, validation, or cleanup steps.
Recommendations
  • Include examples of deploying Linux VMs in the backend pool, using common Linux web servers (e.g., Nginx or Apache) for validation.
  • Provide resource cleanup instructions using Azure CLI (az group delete) and Bash commands alongside PowerShell.
  • Clarify that IIS is used for demonstration purposes and offer parallel steps for Linux-based validation.
  • Ensure screenshots and walkthroughs do not assume a Windows-only environment.
  • Add notes or sections highlighting cross-platform compatibility and options.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ipv6-application-gateway-portal.md ...application-gateway/ipv6-application-gateway-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server as the backend VM example, providing only PowerShell commands for backend configuration (IIS installation), and omitting any Linux-based backend or CLI/Bash examples. There is no mention of Linux VMs, nor are there instructions for installing a web server on Linux or using Bash/Azure CLI for automation.
Recommendations
  • Include parallel instructions for deploying a Linux VM (e.g., Ubuntu) as a backend target.
  • Provide examples for installing a web server (such as Apache or Nginx) on Linux, using Bash or Azure CLI.
  • Offer Azure CLI commands alongside PowerShell for resource creation and configuration.
  • Clarify that both Windows and Linux VMs are supported as backend targets, and link to relevant Linux documentation.
  • Present Linux examples with equal prominence and detail as Windows examples, rather than only referencing Windows.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/migrate-v1-v2.md ...lob/main/articles/application-gateway/migrate-v1-v2.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page is heavily biased towards Windows and PowerShell usage. All migration scripts, examples, and instructions are provided exclusively in PowerShell, with no mention of Bash, Azure CLI, or Linux-native tooling. The installation and execution steps assume a Windows/PowerShell environment, and references to script downloads and module management are specific to PowerShell Gallery and Windows conventions. There are no Linux or cross-platform alternatives, nor any guidance for users who may be working in a Linux shell or prefer Azure CLI. This creates a significant barrier for Linux users and those working in non-Windows environments.
Recommendations
  • Provide equivalent Azure CLI (az) commands and scripts for all migration operations, including configuration cloning and public IP retention.
  • Include Bash shell examples for script execution and parameter handling, especially for certificate management and file operations.
  • Document how to use Azure Cloud Shell in Bash mode, and clarify that all operations can be performed from Linux/macOS terminals.
  • Offer downloadable scripts in a cross-platform format (e.g., Python, shell scripts) or clarify PowerShell Core compatibility on Linux/macOS.
  • Add a section explicitly addressing Linux/macOS users, outlining any prerequisites, installation steps, and differences in workflow.
  • Ensure that references to PowerShell Gallery are supplemented with instructions for Linux users (e.g., using pwsh, or alternative package managers).
  • Where possible, present Azure CLI examples before or alongside PowerShell examples to avoid 'windows_first' bias.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/mutual-authentication-certificate-management.md ...ateway/mutual-authentication-certificate-management.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows environments. All certificate export instructions rely on Windows GUI tools (Certificate Manager, Certificate Export Wizard) and PowerShell references, with no equivalent Linux or cross-platform CLI instructions. Linux is only mentioned in the context of concatenating files, and even then, the Windows command is listed first. There are no examples using Linux tools (e.g., openssl) for certificate management.
Recommendations
  • Add step-by-step instructions for exporting certificates using Linux command-line tools such as openssl.
  • Include screenshots or terminal output examples for Linux workflows.
  • Present Linux and Windows commands side-by-side, or in parallel sections, rather than listing Windows first.
  • Reference cross-platform tools (e.g., openssl, certtool) for certificate management.
  • Avoid exclusive reliance on Windows GUI tools; provide CLI alternatives for automation and Linux users.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/proxy-buffers.md ...lob/main/articles/application-gateway/proxy-buffers.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring buffer settings, but PowerShell (a Windows-centric tool) is given a dedicated section with more detailed examples, including both creation and update scenarios. The reference to the Azure SDK for .NET (primarily Windows-focused) further reinforces Windows bias. There are no Linux shell (e.g., Bash) or cross-platform SDK examples, and PowerShell is mentioned before ARM templates, which are platform-neutral.
Recommendations
  • Add explicit Bash shell examples for Azure CLI to demonstrate Linux usage.
  • Include cross-platform SDK examples (e.g., Python, Java) to balance .NET references.
  • Clarify that Azure CLI commands work identically on Windows, Linux, and macOS.
  • If mentioning PowerShell, also mention Bash or other Linux-native tools where applicable.
  • Reorder sections so platform-neutral methods (Azure CLI, ARM templates) appear before Windows-specific tools like PowerShell.
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-09 00:34
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 Windows bias primarily through the exclusive use of Azure PowerShell scripts for migration guidance and preview registration/unregistration, with no mention of Bash, Linux, or cross-platform CLI alternatives. The 'Next steps' section links only to PowerShell-based tutorials, and the page references Azure PowerShell Gallery as the source for migration scripts. There are no Linux-specific instructions or examples, nor are Bash or Azure CLI (outside of PowerShell context) commands provided. Windows tools and patterns are mentioned first and exclusively, leaving Linux users without clear guidance.
Recommendations
  • Include Azure CLI (bash/shell) examples alongside PowerShell commands for all operations, such as migration, preview registration, and unregistration.
  • Provide links to tutorials and scripts that are platform-agnostic or explicitly support Linux/macOS environments.
  • Mention cross-platform compatibility for scripts and tools, and clarify any Windows-specific limitations.
  • Add a section or callout for Linux users, highlighting any differences or additional steps required.
  • Ensure that code blocks are labeled clearly as PowerShell or Bash, and provide both where possible.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively providing PowerShell commands for resource cleanup, referencing IIS (a Windows web server) for validation, and omitting Linux-specific examples or alternatives (such as Bash, Azure CLI, or Apache/Nginx for backend validation). The use of Windows-centric tools and patterns is present throughout, with no mention of Linux equivalents or parity.
Recommendations
  • Include Azure CLI and Bash examples for resource group deletion alongside PowerShell.
  • Provide instructions for validating the deployment using Linux-based web servers (e.g., Apache or Nginx) in addition to IIS.
  • Offer sample ARM templates or deployment options that use Linux VMs in the backend pool.
  • Ensure that all steps (deployment, validation, cleanup) have both Windows and Linux command examples, presented with equal prominence.
  • Reference cross-platform tools and patterns (e.g., Azure CLI, REST API) before or alongside Windows-specific tools.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-portal.md ...in/articles/application-gateway/quick-create-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways. The virtual machine creation example exclusively uses Windows Server 2016 Datacenter, and the backend verification is performed using IIS (a Windows-only web server). The instructions for installing IIS rely on Azure PowerShell and Windows-specific commands, with no mention of Linux VM creation or using Linux-native web servers (such as Apache or Nginx). All code examples for backend setup use PowerShell, and there is no parity for Linux users or Bash/CLI alternatives in the main flow.
Recommendations
  • Provide parallel instructions for creating Linux virtual machines (e.g., Ubuntu) as backend servers.
  • Include examples for installing and testing with Linux-native web servers (such as Apache or Nginx), using Bash or Azure CLI commands.
  • Offer both PowerShell and Bash/CLI scripts for backend setup and verification steps.
  • Explicitly mention that Application Gateway supports both Windows and Linux VMs in backend pools.
  • Reorder or balance examples so that Linux and Windows options are presented with equal prominence.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/retirement-faq.md ...ob/main/articles/application-gateway/retirement-faq.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias, primarily through exclusive use of Azure PowerShell scripts for migration guidance and tooling. There are no references to Linux-native tools, Bash, Azure CLI, or cross-platform migration approaches. All automation and scripting examples are PowerShell-centric, which is most commonly used on Windows. This may disadvantage users on Linux or macOS platforms, who typically use Bash or Azure CLI.
Recommendations
  • Provide equivalent migration scripts and automation examples using Azure CLI and Bash to ensure Linux and macOS users have clear guidance.
  • Explicitly mention cross-platform compatibility of migration tools, or note any limitations.
  • Add documentation sections or links for Linux/macOS users, including troubleshooting and environment setup for non-Windows platforms.
  • Where PowerShell is referenced, clarify if it can be used on Linux/macOS, and provide installation instructions if relevant.
  • Ensure that any references to tools or scripts are accompanied by alternatives or parity for Linux environments.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All command-line examples use PowerShell, and certificate creation is demonstrated exclusively with Windows tools (New-SelfSignedCertificate, Export-PfxCertificate). The backend VM scale set is configured with Windows Server 2016, and IIS installation is performed via PowerShell scripts. There are no Linux equivalents or examples provided for certificate creation, backend OS selection, or web server setup. The instructions and screenshots assume a Windows-centric workflow throughout.
Recommendations
  • Provide equivalent Linux examples for certificate creation (e.g., using OpenSSL) and exporting .pfx files.
  • Include instructions for creating a VM scale set with a Linux OS (such as Ubuntu) as the backend pool.
  • Demonstrate web server installation on Linux (e.g., Apache or Nginx) using Bash scripts or Azure CLI.
  • Offer Azure CLI or Bash alternatives to PowerShell commands throughout the tutorial.
  • Add screenshots and walkthroughs for Linux-based backend configuration and testing.
  • Clearly indicate OS-specific steps and provide parity for both Windows and Linux users.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page exhibits Windows bias by referencing only the Azure portal and a PowerShell-based tutorial for configuring URL redirection, without mentioning or providing examples for Linux-based tools or command-line interfaces such as Azure CLI or ARM templates. The 'Next steps' section specifically links to a PowerShell tutorial, and there is no mention of Bash, Linux shell, or cross-platform alternatives. This may disadvantage users on Linux or macOS platforms.
Recommendations
  • Include equivalent configuration examples using Azure CLI, which is cross-platform and widely used on Linux and macOS.
  • Provide links to tutorials for configuring Application Gateway redirection using ARM templates or REST API, which are platform-neutral.
  • Ensure that 'Next steps' includes both PowerShell and CLI/ARM/REST options, so users on any OS can follow along.
  • Explicitly mention that configuration can be performed from Linux/macOS using CLI or portal, not just PowerShell.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/tutorial-autoscale-ps.md .../articles/application-gateway/tutorial-autoscale-ps.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All examples use Azure PowerShell cmdlets and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of Linux equivalents or cross-platform alternatives. The prerequisites and instructions assume a Windows environment and do not provide guidance for users on Linux or macOS. There are no Bash, Azure CLI, or OpenSSL examples, and the certificate creation process is entirely Windows-centric.
Recommendations
  • Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and widely used on Linux and macOS.
  • Include instructions for creating self-signed certificates using OpenSSL, which is available on Linux and macOS.
  • Add notes or sections for Linux/macOS users, specifying any differences in setup or command usage.
  • Reorder or parallelize examples so that Windows and Linux approaches are presented together, rather than Windows-first.
  • Clarify that Azure PowerShell can be used on Linux/macOS, but provide installation and usage guidance for those platforms.
  • Where file paths are mentioned (e.g., c:\appgwcert.pfx), provide Linux/macOS equivalents (e.g., /home/user/appgwcert.pfx).
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/tutorial-protect-application-gateway-ddos.md ...n-gateway/tutorial-protect-application-gateway-ddos.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 significant Windows bias. All virtual machine examples use Windows Server, and IIS is installed for testing using PowerShell commands. There are no Linux VM examples, nor instructions for deploying or testing with Linux-based backends (e.g., Apache, Nginx). The only provided automation is via Azure PowerShell, with no Bash, CLI, or Linux-native alternatives. Windows tools and patterns are mentioned exclusively and before any Linux equivalents (which are absent).
Recommendations
  • Include parallel instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
  • Provide Linux-based web server setup steps (e.g., install Apache or Nginx) alongside IIS.
  • Offer Azure CLI and Bash script examples for automation, not just Azure PowerShell.
  • Explicitly mention that Application Gateway supports both Windows and Linux backends.
  • Add screenshots and walkthroughs for Linux VM configuration and testing.
  • Ensure that references to backend server OS are inclusive and not Windows-centric.
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-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows and Windows-specific tools (IIS, PowerShell) are mentioned first or exclusively in several places. The Azure PowerShell example is provided in detail, while Azure CLI is only mentioned in passing. IIS configuration is described with links, while Apache and NGINX are shown as code snippets. The certificate generator tool is web-based but references Windows file paths in PowerShell examples. There is no Linux-specific automation or example for uploading certificates to Application Gateway, nor is there parity in CLI usage.
Recommendations
  • Provide Azure CLI examples alongside or before Azure PowerShell for certificate upload and configuration.
  • Include Linux-specific instructions for managing trusted root certificates (e.g., update-ca-certificates on Ubuntu).
  • Balance IIS instructions with step-by-step guides for Apache and NGINX, not just code snippets.
  • Avoid referencing Windows file paths in examples; use generic or platform-neutral paths.
  • Explicitly mention Linux equivalents for all Windows tools and steps, especially for certificate management and web server configuration.
  • Clarify that the instructions are cross-platform and highlight any platform-specific differences.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ssl-overview.md ...blob/main/articles/application-gateway/ssl-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page displays a Windows bias by referencing Windows-specific tools and APIs (such as PFXImportCertStore), providing configuration guidance and next steps primarily through PowerShell, and omitting Linux or cross-platform alternatives for certificate management and Application Gateway configuration. Windows terminology and tools are mentioned first or exclusively, with no examples or instructions for Linux users.
Recommendations
  • Include equivalent Linux/OpenSSL commands for certificate creation, conversion, and management alongside Windows/PFX references.
  • Provide Azure CLI and/or REST API examples for configuring Application Gateway and TLS settings, as these are cross-platform.
  • Add links or sections for configuring end-to-end TLS using Linux tools and workflows, such as using PEM certificates and OpenSSL.
  • Ensure that troubleshooting and next steps cover both Windows and Linux environments, not just PowerShell.
  • Mention cross-platform certificate formats (PEM, CRT) and how to convert between them and PFX using OpenSSL.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-diagnostics.md ...application-gateway/application-gateway-diagnostics.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 Windows bias by providing only PowerShell examples for enabling diagnostic logging, referencing Windows-centric tools (Excel, Power BI, Visual Studio, C#), and omitting equivalent Linux/CLI/Bash instructions. The guidance and tooling recommendations are presented from a Windows-first perspective, with no mention of Linux-native workflows or open-source alternatives.
Recommendations
  • Add Azure CLI (az) and Bash examples for enabling diagnostic logging, alongside PowerShell.
  • Include instructions for viewing and analyzing logs using Linux-native tools (e.g., jq, grep, awk, csvkit) and open-source visualization platforms (e.g., Grafana).
  • Reference cross-platform editors and programming languages (e.g., Python, VS Code) for log conversion and analysis, not just Visual Studio and C#.
  • Ensure that examples and tool recommendations are presented in a platform-neutral order, or provide both Windows and Linux alternatives side-by-side.
  • Explicitly state platform compatibility for all tools and scripts mentioned, and link to Linux installation guides where appropriate.
GitHub Create Pull Request
← Previous Page 9 of 40 Next →