Application Gateway

372
Total Pages
310
Linux-Friendly Pages
62
Pages with Bias
16.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

172 issues found
Showing 1-25 of 172 flagged pages
Application Gateway Tutorial: Improve web application access - Azure Application Gateway .../articles/application-gateway/tutorial-autoscale-ps.md
High Priority View Details →
Scanned: 2026-02-10 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 exclusively uses Azure PowerShell and Windows PowerShell cmdlets for all steps, including certificate creation (New-SelfSignedCertificate, Export-PfxCertificate), and does not provide any Bash, Azure CLI, or Linux/macOS-compatible alternatives. Windows-specific file paths (e.g., c:\appgwcert.pfx) are used throughout. There is no mention of how to perform these tasks on Linux or macOS, nor are cross-platform tools or instructions provided.
Recommendations
  • Add Azure CLI examples for each step alongside PowerShell, as Azure CLI is cross-platform.
  • Provide instructions for creating self-signed certificates using OpenSSL (common on Linux/macOS) as an alternative to New-SelfSignedCertificate.
  • Use generic file paths or note differences for Linux/macOS (e.g., /home/user/appgwcert.pfx).
  • Clarify that Azure PowerShell can be run on Linux/macOS, and provide guidance for those environments.
  • Include a note or section for Linux/macOS users outlining equivalent commands and tools.
GitHub Create Pull Request
Application Gateway Tutorial: Improve web application access - Azure Application Gateway .../articles/application-gateway/tutorial-autoscale-ps.md
High Priority View Details →
Scanned: 2026-01-25 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 tools, such as the use of New-SelfSignedCertificate and Export-PfxCertificate, which are only available on Windows. All code examples are in PowerShell, and there are no CLI, Bash, or Linux/macOS alternatives provided. The instructions for certificate creation and file paths (e.g., c:\appgwcert.pfx) are Windows-centric, making it difficult for Linux/macOS users to follow the tutorial without significant adaptation.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all resource creation and management steps.
  • Include instructions for creating self-signed certificates on Linux/macOS (e.g., using OpenSSL) and exporting them to PFX format.
  • Use platform-neutral file paths in examples, or clarify how to adapt them for Linux/macOS.
  • Add notes or sections explicitly addressing how Linux/macOS users can complete each step.
  • Consider offering downloadable scripts or templates for both PowerShell and Bash/CLI.
GitHub Create Pull Request
Application Gateway Tutorial: Improve web application access - Azure Application Gateway .../articles/application-gateway/tutorial-autoscale-ps.md
High Priority View Details →
Scanned: 2026-01-24 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 tools, such as New-SelfSignedCertificate and Export-PfxCertificate, with all examples and instructions using PowerShell syntax. There are no Bash, Azure CLI, or Linux/macOS alternatives provided, and the certificate creation steps rely on Windows-only cmdlets. This creates notable friction for Linux/macOS users who cannot easily follow the steps as written.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all 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 clarifying cross-platform options and limitations, and link to relevant cross-platform documentation.
  • Consider reordering or parallelizing examples so Linux/macOS methods are presented alongside Windows/PowerShell methods.
GitHub Create Pull Request
Application Gateway Tutorial: Create and configure an application gateway to host multiple web sites using the Azure portal ...es/application-gateway/create-multiple-sites-portal.md
High Priority View Details →
Scanned: 2026-01-12 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 demonstrates a significant Windows bias. Virtual machine creation is shown only for Windows Server, IIS installation is performed exclusively via Azure PowerShell and Windows-specific commands, and hosts file editing instructions are tailored for Windows (including command prompt and ipconfig usage). No Linux or macOS equivalents are provided for VM creation, web server setup, or hosts file editing.
Recommendations
  • Add parallel instructions for creating a Linux VM (e.g., Ubuntu) and installing a web server such as Apache or Nginx, including relevant Azure CLI or portal steps.
  • Provide Linux/macOS commands for editing the hosts file (e.g., using sudo nano /etc/hosts) and for flushing DNS (e.g., systemd-resolve --flush-caches, dscacheutil -flushcache for macOS).
  • Include Azure CLI examples alongside PowerShell, or clarify that both can be used.
  • Explicitly state that Application Gateway supports both Windows and Linux backend servers, and link to relevant documentation.
  • Reorder examples so that OS-neutral or Linux instructions are presented alongside or before Windows-specific ones where possible.
GitHub Create Pull Request
Application Gateway Certificates required to allow backend servers ...ion-gateway/certificates-for-backend-authentication.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation exclusively uses Windows Certificate Manager and PowerShell for certificate export instructions, with screenshots and step-by-step guidance tailored to Windows. There are no examples or instructions for performing equivalent tasks on Linux or macOS, nor are cross-platform tools mentioned. The only tool referenced is Windows Certificate Manager, and the 'Next steps' section points to a PowerShell guide, further reinforcing Windows bias.
Recommendations
  • Add equivalent instructions for exporting certificates using OpenSSL, which is available on Linux and macOS.
  • Include command-line examples for Linux/macOS users, such as using openssl to extract public keys and root certificates.
  • Mention cross-platform certificate management tools (e.g., Keychain Access for macOS, or certtool for Linux).
  • Provide screenshots or terminal output examples for Linux/macOS workflows.
  • Ensure that references to PowerShell are complemented by Bash or shell script examples for Linux/macOS.
GitHub Create Pull Request
Application Gateway Tutorial: Configure an Application Gateway with TLS termination using the Azure portal ...main/articles/application-gateway/create-ssl-portal.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias, especially in the certificate creation and backend VM setup steps. Only Windows PowerShell commands are provided for creating and exporting self-signed certificates, with no mention of Linux or macOS alternatives (e.g., OpenSSL). The backend VM creation is exclusively shown with Windows Server, and IIS installation is performed using PowerShell scripts. There are no examples or guidance for Linux VMs, Apache/Nginx web servers, or Linux/macOS certificate creation workflows.
Recommendations
  • Provide Linux/macOS instructions for creating self-signed certificates using OpenSSL, including export to PFX format.
  • Include examples for creating Linux VMs (e.g., Ubuntu) as backend servers, and show how to install Apache or Nginx for testing.
  • Offer equivalent shell commands for certificate management and web server setup on Linux/macOS.
  • Clearly state that Application Gateway supports both Windows and Linux backend servers, and link to cross-platform setup guides.
  • Present examples for both platforms side-by-side or in separate sections to improve parity.
GitHub Create Pull Request
Application Gateway Deploy Application Gateway Basic (Preview) ...in/articles/application-gateway/deploy-basic-portal.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All command-line instructions for preview registration and IIS installation use Azure PowerShell and Windows-specific tooling, with no mention of Bash, CLI, or Linux alternatives. The VM creation walkthrough exclusively uses Windows Server, and IIS (a Windows-only web server) is the only backend test method described. No Linux VM or Apache/Nginx examples are provided, and all automation is shown with PowerShell scripts.
Recommendations
  • Provide equivalent Azure CLI (az) commands for preview registration and unregistration, suitable for Linux/macOS users.
  • Include instructions for creating a Linux VM (e.g., Ubuntu) as a backend server, alongside the Windows VM example.
  • Offer steps to install Apache or Nginx on Linux VMs for backend testing, with sample Bash commands.
  • Present both Windows and Linux examples side-by-side, or clearly indicate alternatives for non-Windows users.
  • Avoid assuming PowerShell is the default shell; mention Cloud Shell Bash and cross-platform options.
GitHub Create Pull Request
Application Gateway Tutorial: Create an application gateway with URL path-based routing rules using Azure portal ...rticles/application-gateway/create-url-route-portal.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The tutorial demonstrates a strong Windows bias: all VM creation instructions use Windows Server, IIS is the only web server installed, and the only automation example is via PowerShell. There are no Linux VM options, no Linux web server (e.g., Apache, Nginx) instructions, and no Bash/Azure CLI examples for setup or verification. This may confuse or exclude Linux/macOS users who wish to follow the tutorial using their preferred platforms.
Recommendations
  • Provide parallel instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
  • Include steps to install a Linux web server (such as Apache or Nginx) and verify its operation.
  • Offer Azure CLI or Bash script examples for VM extension installation and configuration, alongside PowerShell.
  • Clearly state that backend pools can use both Windows and Linux VMs, and link to relevant Linux setup guides.
  • Show Linux verification screenshots and commands in the 'Test the application gateway' section.
GitHub Create Pull Request
Application Gateway Export trusted client CA certificate chain for client authentication ...ateway/mutual-authentication-certificate-management.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily Windows-centric, with all certificate export steps described using Windows GUI tools (Certificate Manager, Certificate Export Wizard) and screenshots. Linux methods for exporting certificates (e.g., using openssl or command-line tools) are not mentioned or demonstrated. The only Linux-specific content is the 'cat' command for concatenating certificates, which appears after the Windows 'type' command. There is also reference to opening Certificate Manager via PowerShell, reinforcing a Windows-first approach.
Recommendations
  • Add equivalent Linux/macOS instructions for exporting public and CA certificates, using openssl or other standard command-line tools.
  • Include Linux/macOS screenshots or terminal examples where appropriate.
  • Present Windows and Linux/macOS instructions in parallel sections or clearly label them for each OS.
  • Avoid referencing Windows tools (Certificate Manager, PowerShell) exclusively; mention cross-platform alternatives.
  • Ensure next steps reference Linux/macOS options (e.g., CLI, Azure CLI) alongside PowerShell.
GitHub Create Pull Request
Application Gateway HTTP to HTTPS redirection in portal - Azure Application Gateway ...s/application-gateway/redirect-http-to-https-portal.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily biased toward Windows and PowerShell. All CLI examples use PowerShell cmdlets, including certificate creation and IIS installation. The virtual machine scale set instructions default to Windows Server, with no mention of Linux alternatives. There are no Bash, Linux, or OpenSSL examples for certificate creation, nor instructions for deploying Linux VMs or web servers (e.g., Apache, Nginx). The file paths and tooling (e.g., c:\appgwcert.pfx) are Windows-specific.
Recommendations
  • Provide parallel examples using Bash and Azure CLI for Linux/macOS users.
  • Include instructions for creating self-signed certificates with OpenSSL.
  • Show how to deploy a Linux VM scale set (e.g., Ubuntu) and install a web server like Apache or Nginx.
  • Use platform-neutral file paths and clarify steps for both Windows and Linux environments.
  • Explicitly mention Linux/macOS compatibility and provide links to relevant documentation.
GitHub Create Pull Request
Application Gateway Tutorial: Improve web application access - Azure Application Gateway .../articles/application-gateway/tutorial-autoscale-ps.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell. All examples use Azure PowerShell cmdlets, and certificate creation relies on Windows-specific PowerShell commands and file paths. There are no CLI (az), Bash, or Linux/macOS instructions or examples, making it difficult for non-Windows users to follow the tutorial without significant adaptation.
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).
  • Use platform-agnostic file paths and note differences where necessary.
  • Explicitly mention cross-platform alternatives and provide links to relevant documentation.
  • Consider reordering examples so that platform-neutral options (Azure CLI) appear first, or present both PowerShell and CLI side-by-side.
GitHub Create Pull Request
Application Gateway Tutorial: Configure an Application Gateway with TLS termination using the Azure portal ...main/articles/application-gateway/create-ssl-portal.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows, with all certificate creation and VM setup examples using Windows PowerShell and Windows Server. There are no instructions or examples for Linux/macOS users for creating self-signed certificates or backend servers, and Windows tools and patterns are referenced exclusively.
Recommendations
  • Add equivalent instructions for creating self-signed certificates on Linux/macOS (e.g., using OpenSSL).
  • Provide examples for deploying Linux VMs as backend servers, including installation of a web server (e.g., Apache or Nginx) for testing.
  • Include Linux/macOS command-line alternatives for certificate export and management.
  • Ensure screenshots and step-by-step instructions are not Windows-specific where possible, or provide Linux/macOS variants.
  • Mention cross-platform compatibility and clarify that Application Gateway supports both Windows and Linux backend pools.
GitHub Create Pull Request
Application Gateway Export trusted client CA certificate chain for client authentication ...ateway/mutual-authentication-certificate-management.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily Windows-centric, with all certificate export instructions and screenshots based on Windows GUI tools (Certificate Manager and Certificate Export Wizard). PowerShell and Windows-specific navigation are referenced, and there are no Linux/macOS CLI or GUI instructions for exporting certificates. Only the final concatenation step provides both Windows and Linux commands.
Recommendations
  • Add equivalent Linux/macOS instructions for exporting certificates, such as using openssl to extract public and CA certificates from .pfx/.pem files.
  • Include CLI examples for Linux/macOS users, avoiding reliance on GUI-based Windows tools.
  • Provide screenshots or step-by-step guidance for Linux certificate management (e.g., using openssl or certtool).
  • Ensure that Linux/macOS instructions are presented alongside Windows instructions, not only at the end.
  • Mention cross-platform tools and patterns where possible, such as openssl, to improve accessibility.
GitHub Create Pull Request
Application Gateway HTTP to HTTPS redirection in portal - Azure Application Gateway ...s/application-gateway/redirect-http-to-https-portal.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily biased toward Windows and PowerShell, with all command-line examples using PowerShell and Windows-specific tools (e.g., New-SelfSignedCertificate, Export-PfxCertificate). The creation of the backend VM scale set defaults to Windows Server, and installation instructions for IIS use PowerShell scripts. There are no Linux or Bash equivalents provided for certificate creation, VM scale set configuration, or web server setup, making it difficult for Linux/macOS users to follow the tutorial without significant adaptation.
Recommendations
  • Provide equivalent Bash/CLI examples for certificate creation (e.g., using OpenSSL) and exporting .pfx files.
  • Include instructions for creating a Linux-based VM scale set (e.g., Ubuntu) and installing a web server such as Apache or Nginx.
  • Offer both PowerShell and Bash/Azure CLI command snippets side-by-side where possible.
  • Clarify which steps are OS-agnostic and which require adaptation for Linux/macOS.
  • Add notes or links to Linux/macOS-specific documentation for related tasks.
GitHub Create Pull Request
Application Gateway Tutorial: Improve web application access - Azure Application Gateway .../articles/application-gateway/tutorial-autoscale-ps.md
High Priority View Details →
Scanned: 2026-01-11 06:20
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 biased towards Windows and PowerShell usage. All examples use Azure PowerShell cmdlets, and certificate creation relies on Windows-specific PowerShell commands (New-SelfSignedCertificate, Export-PfxCertificate). There are no CLI or Linux/macOS alternatives provided, and the instructions assume a Windows environment (e.g., file paths like c:\appgwcert.pfx). This creates friction for Linux/macOS users, who may not have access to these tools or may need to find alternative methods.
Recommendations
  • Add equivalent Azure CLI examples for all resource creation and configuration steps.
  • Provide instructions for creating self-signed certificates using OpenSSL (cross-platform) as an alternative to New-SelfSignedCertificate.
  • Use platform-neutral file paths in examples, or clarify differences for Linux/macOS users.
  • Explicitly mention how Linux/macOS users can install and use Azure PowerShell, or offer CLI alternatives as the primary or parallel workflow.
  • Reorder examples so that cross-platform methods (Azure CLI, OpenSSL) are presented first or alongside PowerShell.
GitHub Create Pull Request
Application Gateway Use with Internal Load Balancer - Azure Application Gateway ...les/application-gateway/application-gateway-ilb-arm.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses Azure PowerShell cmdlets for all examples and instructions, with no mention of Azure CLI, Bash, or Linux/macOS workflows. Windows PowerShell is referenced directly, and all setup steps assume PowerShell usage. There are no Linux/macOS-specific instructions or parity examples, and the article does not acknowledge cross-platform alternatives.
Recommendations
  • Add equivalent Azure CLI (az) commands for each step, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI, and provide links to relevant CLI documentation.
  • Include a section comparing PowerShell and CLI approaches, helping users choose the best tool for their platform.
  • Avoid referencing 'Windows PowerShell' unless necessary; use 'PowerShell' generically or clarify cross-platform support.
  • Add notes or callouts for Linux/macOS users, including prerequisites for running Azure CLI or PowerShell Core.
GitHub Create Pull Request
Application Gateway Deploy an Azure Application Gateway with an IPv6 frontend ...ation-gateway/ipv6-application-gateway-arm-template.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 by exclusively using IIS (a Windows web server) for backend validation, referencing only PowerShell for resource cleanup, and omitting Linux-based alternatives or examples (such as Apache/Nginx or Bash/Azure CLI commands). There are no Linux VM validation steps or cleanup instructions using Linux-friendly tools.
Recommendations
  • Include examples of deploying Linux VMs (e.g., Ubuntu) in the backend pool and instructions for validating deployment using Apache or Nginx.
  • Provide resource cleanup instructions using Azure CLI (az group delete) and Bash, alongside PowerShell.
  • Add browser-based validation steps for both Windows and Linux VMs, showing expected responses from different web servers.
  • Mention that IIS is used for demonstration and offer equivalent steps for Linux-based web servers.
  • Ensure parity in screenshots and instructions for both Windows and Linux environments.
GitHub Create Pull Request
Application Gateway Configure Application Gateway with a frontend public IPv6 address using the Azure portal ...application-gateway/ipv6-application-gateway-portal.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates Windows bias by exclusively using Windows Server as the backend VM example and providing only PowerShell-based instructions for backend configuration (IIS installation). There are no Linux VM examples, nor are there Linux command-line instructions (e.g., Bash, SSH, cloud-init) for backend setup or testing. The documentation references Azure PowerShell as an alternative to the portal, but does not mention Azure CLI or provide parity for Linux users.
Recommendations
  • Include Linux VM examples (e.g., Ubuntu or CentOS) as backend targets alongside Windows Server.
  • Provide instructions for installing a web server (e.g., Apache or Nginx) on Linux VMs using Bash/SSH commands or cloud-init scripts.
  • Offer Azure CLI commands as alternatives to Azure PowerShell for resource creation and configuration.
  • Explicitly mention cross-platform options for testing connectivity (e.g., curl, wget) from Linux/macOS terminals.
  • Ensure that both Windows and Linux setup/testing instructions are presented with equal prominence and detail.
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-09 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 page demonstrates a Windows bias by providing only PowerShell examples for enabling diagnostic logging, with no equivalent Azure CLI, Bash, or Linux-native instructions. It references Windows-centric tools (PowerShell, Excel, Visual Studio, C#) for log manipulation and analysis, and does not mention or prioritize Linux-friendly alternatives. The absence of cross-platform command-line examples and reliance on Windows tools may hinder accessibility for Linux users.
Recommendations
  • Add Azure CLI examples alongside PowerShell for enabling and configuring diagnostic logging, as Azure CLI is cross-platform and widely used on Linux.
  • Include Bash or shell script snippets for common tasks, such as downloading and processing logs.
  • Mention and provide examples for Linux-native tools (e.g., jq, awk, sed) for parsing and analyzing JSON log files.
  • Reference cross-platform editors and data visualization tools (e.g., VS Code, LibreOffice Calc, or open-source log viewers) instead of or in addition to Excel and Visual Studio.
  • Ensure that all code and tool references are either cross-platform or have Linux equivalents clearly documented.
  • Consider reordering sections so that cross-platform or Linux-friendly methods are presented before or alongside Windows/PowerShell approaches.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-ilb-arm.md ...les/application-gateway/application-gateway-ilb-arm.md
High Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All examples and instructions use Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native workflows. Windows/PowerShell tools are referenced exclusively and repeatedly, and there are no Linux or cross-platform alternatives provided. The documentation assumes the user is working in a Windows/PowerShell environment from the outset.
Recommendations
  • Add equivalent Azure CLI (az) command examples for each PowerShell step, with clear instructions for running them on Linux, macOS, and Windows.
  • Include a section at the beginning outlining both PowerShell and CLI options, and recommend the CLI for cross-platform scenarios.
  • Reference Bash and shell scripting alternatives where appropriate, especially for automation.
  • Avoid language such as 'switch PowerShell mode' or 'Using Windows PowerShell' unless also providing guidance for CLI users.
  • Ensure all code samples are available in both PowerShell and CLI formats, and alternate their order or present them side-by-side.
  • Explicitly mention that Azure CLI is supported on Linux, macOS, and Windows, and link to installation instructions.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-websocket.md ...s/application-gateway/application-gateway-websocket.md
High Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily by referencing Azure PowerShell and linking to a 'quick-create-powershell.md' page as the next step, without mentioning or providing equivalent Azure CLI or Linux shell examples. The only tooling mentioned for creating listeners is Azure PowerShell and the portal, with no reference to cross-platform or Linux-native tools. There are no examples or instructions for Linux users, nor is Azure CLI (which is cross-platform) mentioned.
Recommendations
  • Include Azure CLI examples alongside or before PowerShell examples to ensure Linux and macOS users are supported.
  • Mention that both Azure PowerShell and Azure CLI can be used to configure Application Gateway, and provide links to both sets of documentation.
  • Update the 'Next steps' section to reference both PowerShell and Azure CLI quick-create guides.
  • Explicitly state that configuration can be performed from any OS, and provide guidance for Linux users where relevant.
  • Add sample commands or scripts for Linux environments, such as bash shell or Azure CLI, especially in sections describing listener creation or gateway setup.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-create-probe-portal.md ...ion-gateway/application-gateway-create-probe-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page provides instructions for creating a custom probe in Azure Application Gateway primarily through the Azure Portal and PowerShell. The navigation selector lists 'Azure Resource Manager PowerShell' and 'Azure Classic PowerShell' as alternatives, with no mention of Azure CLI (which is cross-platform and Linux-friendly), Bash, or Linux-specific tools. All command-line examples and references are PowerShell-centric, and there are no Linux/Unix shell or Azure CLI equivalents provided. This structure prioritizes Windows tools and patterns, making it less accessible for Linux users.
Recommendations
  • Add Azure CLI examples for all operations currently shown with PowerShell, as Azure CLI is cross-platform and widely used on Linux.
  • Include Bash or shell script snippets where relevant, especially for automation scenarios.
  • Mention Azure CLI as an alternative in the selector at the top, alongside PowerShell.
  • Ensure that any references to command-line tools or automation scripts are balanced between Windows (PowerShell) and Linux (Bash/Azure CLI).
  • Explicitly state that the Azure Portal is accessible from any OS, but provide parity in command-line instructions.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-externally-managed-scheduled-autoscaling.md ...ation-gateway-externally-managed-scheduled-autoscaling.md
High Priority View Details →
Scanned: 2026-01-09 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 exclusively provides PowerShell-based examples for creating and managing Azure Automation runbooks, which is a Windows-centric tool. There are no Bash, Azure CLI, or Python examples, nor is there mention of using Linux-based automation options. The workflow and tooling described (PowerShell runbooks, Az module) are more familiar to Windows users, and no Linux-first or cross-platform alternatives are presented.
Recommendations
  • Provide equivalent examples using Azure CLI and/or Python runbooks, which are more familiar to Linux users.
  • Explicitly mention that Azure Automation supports Python and Bash runbooks, and link to relevant documentation.
  • Add a section or note highlighting cross-platform options and when to use each (PowerShell, Python, Bash, etc.).
  • Ensure that Linux-friendly tools and patterns are described with parity to Windows/PowerShell approaches.
  • Consider reordering or parallelizing examples so that Windows and Linux approaches are presented together.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-key-vault-common-errors.md ...gateway/application-gateway-key-vault-common-errors.md
High Priority View Details →
Scanned: 2026-01-09 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 demonstrates a Windows bias by providing only PowerShell command examples for certificate management and updates, without offering equivalent Azure CLI or Bash examples. The use of PowerShell as the sole scripting tool assumes a Windows environment. Additionally, when mentioning programmatic alternatives to the portal, 'ARM template, CLI, or PowerShell' are listed, but only PowerShell examples are shown. There are no Linux-specific instructions or screenshots, and the portal navigation assumes a GUI typical of Windows users.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all PowerShell scripts, especially for certificate upload/update and Key Vault operations.
  • Where programmatic options are mentioned (ARM template, CLI, PowerShell), provide examples for both CLI and PowerShell.
  • Explicitly state that the Azure CLI commands can be run on Linux, macOS, and Windows, and provide Bash shell examples where appropriate.
  • Include screenshots or instructions for using the Azure portal from non-Windows environments (e.g., browser-agnostic language).
  • Review the order of tool mentions to avoid always listing Windows tools first; alternate or group by platform.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-infrastructure.md ...es/application-gateway/configuration-infrastructure.md
High Priority View Details →
Scanned: 2026-01-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing Azure PowerShell cmdlets for restarting the Application Gateway, without providing equivalent Azure CLI (cross-platform) or Bash examples. There are no explicit Linux or Bash examples, and the only command-line instructions are PowerShell-specific. This could hinder Linux or macOS users who may prefer or require CLI/Bash instructions.
Recommendations
  • For every PowerShell example or reference, provide an equivalent Azure CLI (az) command, ideally with Bash syntax.
  • When referencing command-line operations (e.g., restarting the Application Gateway), include both PowerShell and CLI/Bash instructions, or link to cross-platform documentation.
  • Avoid assuming PowerShell as the default tool; mention both PowerShell and CLI equally, or lead with CLI/Bash for improved Linux parity.
  • Add a note clarifying that all operations can be performed via Azure CLI on any platform, and provide links to relevant CLI documentation.
GitHub Create Pull Request
← Previous Page 1 of 7 Next →