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

841 issues found
Showing 1-25 of 841 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-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The tutorial is heavily focused on Azure PowerShell and Windows-native tools. All examples use PowerShell cmdlets, and certificate creation relies on New-SelfSignedCertificate, a Windows-specific command. There are no Bash, Azure CLI, or Linux/macOS-compatible instructions, making it difficult for non-Windows users to follow the tutorial.
Recommendations
  • Provide Azure CLI (az) equivalents for all resource creation and configuration steps.
  • Include Bash or cross-platform scripting examples alongside PowerShell.
  • For certificate creation, suggest OpenSSL commands for Linux/macOS users.
  • Clarify which steps are Windows-only and offer alternatives where possible.
  • Add a note about PowerShell Core availability on Linux/macOS, but also highlight Azure CLI as a preferred cross-platform tool.
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-02-16 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, resource management, and cleanup. It references Windows-specific tools (e.g., New-SelfSignedCertificate, Export-PfxCertificate) and assumes a Windows environment (e.g., certificate store paths, file paths like c:\appgwcert.pfx). No Bash, Azure CLI, or Linux/macOS-compatible instructions or examples are provided, and Windows tools are mentioned before any cross-platform alternatives (which are absent).
Recommendations
  • Add Azure CLI examples for each step, as Azure CLI is cross-platform and works on Linux/macOS.
  • For certificate creation, provide Linux/macOS alternatives (e.g., using OpenSSL) alongside Windows PowerShell examples.
  • Clarify which steps are Windows-specific and which can be performed on any OS, and provide guidance for Linux/macOS users.
  • Use generic file paths or explain path differences for non-Windows systems.
  • Mention that Azure PowerShell can be used on Linux/macOS, but provide installation and usage instructions for those platforms.
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-02-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The tutorial exclusively uses Azure PowerShell and Windows PowerShell cmdlets for all steps, including certificate creation with New-SelfSignedCertificate and Export-PfxCertificate, which are Windows-only tools. No Bash, Azure CLI, or Linux/macOS-compatible instructions are provided, and Windows-specific file paths (e.g., c:\appgwcert.pfx) are used throughout. The documentation assumes a Windows environment and does not mention alternatives for Linux/macOS users.
Recommendations
  • Provide Azure CLI equivalents for all steps, especially resource creation and configuration.
  • For certificate creation, include instructions using OpenSSL (cross-platform) alongside New-SelfSignedCertificate.
  • Use generic file paths or note differences for Linux/macOS (e.g., /tmp/appgwcert.pfx).
  • Add a section or callout for Linux/macOS users, clarifying how to adapt the tutorial.
  • Link to cross-platform documentation where possible.
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-02-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 tutorial exclusively uses Azure PowerShell and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with all examples and instructions tailored for Windows environments. There are no Bash, Azure CLI, or Linux/macOS alternatives provided, and Windows-centric patterns (e.g., certificate creation, file paths) are used throughout.
Recommendations
  • Add Azure CLI examples alongside PowerShell for each step, especially for resource creation and configuration.
  • Provide Linux/macOS-compatible instructions for creating self-signed certificates (e.g., using OpenSSL) and exporting PFX files.
  • Use generic file paths or note platform-specific differences where relevant.
  • Mention that Azure PowerShell can be used cross-platform, but highlight any Windows-only cmdlets or steps.
  • Consider linking to Linux/macOS tutorials or documentation for similar 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-02-02 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The tutorial is heavily focused on Azure PowerShell and Windows-specific tooling, such as the use of New-SelfSignedCertificate and Export-PfxCertificate PowerShell cmdlets, which are only available on Windows. There are no CLI (az), Bash, or cross-platform examples provided, and the instructions assume a Windows environment (e.g., referencing C:\ paths and local certificate stores). This creates friction for Linux/macOS users, who cannot follow key steps (like certificate creation) without significant adaptation.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all resource creation steps, especially for resource group, VNet, public IP, and application gateway setup.
  • Include cross-platform instructions for creating self-signed certificates, such as using OpenSSL (available on Linux/macOS/Windows) and explain how to export to PFX format.
  • Avoid hardcoding Windows-specific paths (e.g., c:\appgwcert.pfx) and use environment-agnostic file paths or explain alternatives.
  • Add notes or sections for Linux/macOS users, highlighting differences and providing adapted commands.
  • Consider restructuring the tutorial to offer both PowerShell and CLI/Bash alternatives side-by-side.
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-31 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The tutorial exclusively uses Azure PowerShell and Windows PowerShell cmdlets for all steps, including certificate creation and file paths. There are no Bash, Azure CLI, or Linux/macOS-specific instructions or examples. Windows tools (e.g., New-SelfSignedCertificate, Export-PfxCertificate) are used for certificate creation, which are not available on Linux/macOS by default.
Recommendations
  • Add equivalent Azure CLI (az) commands for all resource creation and configuration steps, as Azure CLI is cross-platform.
  • Provide instructions for creating self-signed certificates on Linux/macOS (e.g., using OpenSSL) and explain how to export them in PFX format.
  • Use platform-neutral file paths in examples, or clarify differences for Linux/macOS users.
  • Include a note or section for Linux/macOS users outlining how to adapt the tutorial for their environment.
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-30 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
This tutorial is heavily focused on Azure PowerShell and Windows tools, with all examples and instructions using PowerShell cmdlets and Windows-specific certificate creation/export commands. There are no CLI (az), Bash, or Linux/macOS alternatives provided, and the certificate steps rely on Windows-only PowerShell modules. The documentation assumes a Windows environment throughout, creating friction for Linux/macOS users.
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 show how to export to PFX format.
  • Clarify which steps are Windows-specific and offer cross-platform alternatives where possible.
  • Reorganize examples so that cross-platform methods (Azure CLI, OpenSSL) are presented alongside or before Windows/PowerShell examples.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The tutorial is exclusively based on Azure PowerShell cmdlets and includes steps (such as certificate creation and export) that use Windows PowerShell-specific tools and file paths (e.g., cert:\localmachine\my, c:\appgwcert.pfx). There are no CLI, Bash, or cross-platform alternatives provided, making it difficult for Linux/macOS users to follow the tutorial end-to-end.
Recommendations
  • Provide equivalent Azure CLI (az) commands for each step, especially for resource creation and management.
  • Include instructions for creating and exporting self-signed certificates on Linux/macOS (e.g., using OpenSSL) alongside the PowerShell method.
  • Use platform-neutral file paths in examples, or show both Windows and Linux/macOS paths where relevant.
  • Explicitly note any steps that are Windows-only and offer alternatives or workarounds for other platforms.
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: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The tutorial exclusively uses Azure PowerShell and Windows PowerShell cmdlets for all steps, including certificate creation and resource management. It assumes a local administrative PowerShell session, and the certificate creation relies on Windows-only tools (New-SelfSignedCertificate, Export-PfxCertificate), with no mention of Linux/macOS alternatives. There are no Bash, Azure CLI, or cross-platform instructions, making it difficult for Linux/macOS users to follow the tutorial as written.
Recommendations
  • Add equivalent Azure CLI (az) commands for all resource creation and management steps.
  • Provide instructions for creating self-signed certificates on Linux/macOS (e.g., using OpenSSL) and explain how to use them in Azure.
  • Clarify which steps are Windows-specific and offer cross-platform alternatives where possible.
  • Include notes or links to cross-platform documentation for users who do not have access to Windows or PowerShell.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides certificate export instructions using Windows tools (Certificate Manager, PowerShell), with step-by-step GUI screenshots and references to Windows-specific paths and dialogs. There are no examples or instructions for performing the same tasks on Linux or macOS, nor are any cross-platform command-line alternatives (e.g., OpenSSL) mentioned. The only automation reference is to PowerShell. This creates significant friction for non-Windows users.
Recommendations
  • Add equivalent instructions for Linux and macOS using OpenSSL to export public keys and root certificates in Base-64 encoded X.509 (.CER) format.
  • Include command-line examples for certificate export, not just GUI steps, to support headless/server environments.
  • Mention and demonstrate cross-platform tools (e.g., OpenSSL, certutil) before or alongside Windows-specific tools.
  • Clarify that the process can be performed on any OS, not just Windows, and provide links to relevant platform-specific documentation.
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-14 00:00
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 strong Windows bias. All VM creation examples use Windows Server, and IIS (a Windows-only web server) is installed for backend verification. The only shell example provided is Azure PowerShell, with no mention of Linux VMs, Linux web servers (such as Apache or Nginx), or Bash/CLI alternatives. Linux users are left without guidance for completing the tutorial using their preferred OS or tools.
Recommendations
  • Provide parallel instructions for creating Linux VMs (e.g., Ubuntu) and installing a Linux web server (Apache, Nginx) for backend verification.
  • Include Azure CLI and Bash examples for VM extension installation and other automation steps.
  • Explicitly mention that the tutorial is applicable to both Windows and Linux, and link to Linux-specific guides if available.
  • Show both Windows and Linux options side-by-side in relevant steps, especially for backend server setup and verification.
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-14 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, with all certificate creation and VM setup examples using Windows PowerShell and Windows Server. There are no instructions or examples for Linux/macOS users to create self-signed certificates or configure backend servers, making it difficult for non-Windows users to follow the tutorial without external resources.
Recommendations
  • Provide equivalent Linux/macOS instructions for creating self-signed certificates (e.g., using OpenSSL).
  • Include examples for deploying Linux VMs as backend servers, with steps for installing a web server (e.g., Apache or Nginx).
  • Show how to export certificates on Linux/macOS and upload them to the Azure portal.
  • Present cross-platform options side-by-side or indicate alternatives for non-Windows users.
  • Avoid assuming the use of Windows tools (PowerShell, Windows Server) as the default.
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-14 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 instructions and screenshots based on Windows GUI tools (Certificate Manager, Certificate Export Wizard). Linux equivalents (e.g., using OpenSSL or command-line tools) are not provided for the critical steps of exporting certificates. PowerShell and Windows-specific navigation are mentioned, while Linux/macOS users are only referenced in the final concatenation step, which provides a 'cat' command. This creates friction for non-Windows users attempting to follow the guide.
Recommendations
  • Add step-by-step instructions for exporting certificates using OpenSSL or other common Linux/macOS tools.
  • Include Linux/macOS screenshots or terminal output examples where appropriate.
  • Present both Windows and Linux/macOS methods side-by-side, or clearly separate them in sections.
  • Avoid referencing Windows tools (e.g., Certificate Manager, PowerShell) as the default or only method.
  • Ensure parity in detail and clarity between Windows and Linux/macOS instructions.
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-14 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 page demonstrates a strong Windows bias. All command-line examples use PowerShell, and certificate creation relies on Windows-specific tools (New-SelfSignedCertificate, Export-PfxCertificate). The virtual machine scale set is provisioned with Windows Server only, and IIS installation is shown via PowerShell scripts. There are no Linux or cross-platform alternatives provided for certificate creation, backend VM OS selection, or web server setup.
Recommendations
  • Provide Linux/macOS equivalents for certificate creation, such as using OpenSSL commands.
  • Include instructions for creating a VM scale set with Linux images (e.g., Ubuntu) and installing a web server like Apache or Nginx.
  • Show how to install and configure a web server on Linux VMs using Bash scripts or Azure CLI.
  • Offer Azure CLI examples alongside PowerShell for cross-platform compatibility.
  • Present Windows and Linux options side-by-side, or clarify which steps are OS-specific.
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-13 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 exhibits a strong Windows bias by exclusively using Windows Server virtual machines as backend examples, providing only PowerShell commands for IIS installation, and referencing IIS (a Windows-only web server) for backend verification. There are no Linux VM creation steps, no Linux web server (e.g., Apache, Nginx) setup instructions, and no Bash/Azure CLI examples for VM configuration. All example commands and screenshots are Windows-centric, making it difficult for Linux/macOS users to follow or adapt the tutorial.
Recommendations
  • Add parallel instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
  • Provide examples for installing a web server on Linux VMs (e.g., Apache or Nginx) using Bash or Azure CLI.
  • Include Bash/Azure CLI commands for VM extension installation and web server setup.
  • Show screenshots and verification steps for Linux web servers.
  • Clearly indicate that backend pools can use both Windows and Linux VMs, and provide guidance for both.
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-13 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 focused on Windows and PowerShell, with all examples and instructions using Azure PowerShell cmdlets. There are no CLI (az) or Bash examples, nor any mention of Linux/macOS tooling or workflows. Windows/PowerShell tools are referenced exclusively and first, making it difficult for Linux/macOS users to follow the guide without adaptation.
Recommendations
  • Add equivalent Azure CLI (az) commands for all steps, with Bash syntax examples.
  • Include notes or sections clarifying cross-platform support and differences.
  • Reference installation and usage instructions for Azure CLI on Linux/macOS.
  • Present CLI and PowerShell examples side-by-side or in tabs for parity.
  • Avoid language implying PowerShell is required; clarify that Azure CLI is fully supported.
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-13 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 exclusively provides step-by-step instructions and screenshots for exporting certificates using Windows Certificate Manager, a Windows-only tool. There are no examples or guidance for performing equivalent tasks on Linux or macOS, nor are cross-platform command-line alternatives (such as OpenSSL) mentioned. The only command-line reference is to PowerShell/certmgr, reinforcing a Windows-centric approach.
Recommendations
  • Add equivalent instructions for exporting certificates using OpenSSL on Linux/macOS, including command-line examples.
  • Explicitly mention that the process can be performed on non-Windows platforms and provide links or steps for those environments.
  • Balance screenshots and step-by-step guides by including at least one Linux/macOS example for each major task.
  • Avoid referencing Windows tools (Certificate Manager, PowerShell) as the default or only method; instead, present them as one option among several.
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-13 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, with all certificate creation and backend VM setup examples using Windows PowerShell and Windows Server. There are no instructions or examples for Linux/macOS users on how to create self-signed certificates or configure Linux VMs as backends. Windows tools and workflows are mentioned exclusively and first, making it difficult for non-Windows users to follow the tutorial.
Recommendations
  • Provide equivalent Linux/macOS instructions for creating self-signed certificates (e.g., using OpenSSL).
  • Include examples for deploying Linux virtual machines as backend servers, such as Ubuntu or CentOS, and show how to install a web server (e.g., Apache or Nginx) for testing.
  • Offer cross-platform command alternatives (e.g., Bash, CLI) alongside PowerShell commands.
  • Explicitly state that both Windows and Linux VMs are supported and provide links to relevant documentation for each.
  • Reorder examples to present Windows and Linux options side-by-side, or alternate which platform is shown first.
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-13 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 exhibits a strong Windows bias, primarily through exclusive use of Azure PowerShell and Windows Server examples. All command-line instructions are given in PowerShell, with no mention of Bash, CLI, or Linux/macOS alternatives. The VM creation walkthrough uses Windows Server 2019 only, and IIS (a Windows web server) is used for backend testing, with no Linux VM or Apache/Nginx example provided. This creates friction for Linux/macOS users and those preferring Bash or Azure CLI.
Recommendations
  • Provide Azure CLI (bash) equivalents for all PowerShell commands, especially for preview registration and VM extension installation.
  • Include Linux VM creation steps alongside Windows, e.g., Ubuntu or CentOS, and show how to install Apache or Nginx for backend testing.
  • When demonstrating backend pool configuration, mention that both Windows and Linux VMs are supported and provide examples for each.
  • Add notes or sections clarifying how Linux/macOS users can perform each step, including using Azure Cloud Shell with Bash.
  • Avoid using only Windows tools (IIS, PowerShell) for verification; offer cross-platform alternatives.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows: all certificate export instructions use Windows GUI tools (Certificate Manager, Certificate Export Wizard), with screenshots and step-by-step guidance for Windows only. There are no Linux/macOS equivalents or CLI-based instructions for exporting certificates. PowerShell and Windows-specific tools are mentioned, while Linux methods are only referenced for concatenation, not for certificate export.
Recommendations
  • Add equivalent instructions for exporting certificates on Linux/macOS, using tools like openssl.
  • Provide CLI-based examples for certificate export, not just GUI walkthroughs.
  • Include screenshots or terminal output for Linux/macOS workflows.
  • Mention cross-platform tools and patterns before or alongside Windows-specific ones.
  • Ensure parity in the 'Prerequisites' and 'Next steps' sections by referencing Linux/macOS documentation and tools.
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-13 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 toward Windows and PowerShell. All code examples for certificate creation and IIS installation use PowerShell and Windows-specific tools, with no mention of Linux equivalents or alternatives. The VM scale set instructions default to Windows Server, and there are no steps for deploying or configuring Linux-based backend servers or using Bash/Azure CLI. This creates friction for Linux/macOS users and may prevent them from completing the tutorial as written.
Recommendations
  • Provide Linux-based examples for creating self-signed certificates (e.g., using OpenSSL) and exporting PFX files.
  • Include instructions for deploying a Linux VM scale set (e.g., Ubuntu) and installing a web server (Apache/Nginx) using Bash or Azure CLI.
  • Offer Azure CLI and Bash alternatives for all PowerShell commands.
  • Clearly indicate OS-specific steps and provide parity for both Windows and Linux users.
  • Add notes or links to relevant Linux documentation where appropriate.
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-13 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 usage. All examples and instructions use Azure PowerShell cmdlets and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of Bash, Azure CLI, or Linux/macOS alternatives. The certificate creation steps rely on Windows-only commands, making it difficult for Linux/macOS users to follow the tutorial without significant adaptation.
Recommendations
  • Provide equivalent Azure CLI (az) commands for all steps, especially resource creation and management.
  • Include instructions for creating self-signed certificates on Linux/macOS (e.g., using OpenSSL) and exporting them to PFX format.
  • Clearly indicate which steps are Windows-specific and offer cross-platform alternatives where possible.
  • Reorder examples or provide parallel instructions so that Linux/macOS users are not required to adapt Windows-centric steps.
  • Add notes or links to official guidance for Linux/macOS users on Azure resource management.
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 is heavily biased towards Windows environments. All certificate creation and export steps use Windows PowerShell cmdlets (New-SelfSignedCertificate, Export-PfxCertificate), with no mention of Linux or cross-platform alternatives. The VM creation steps exclusively use Windows Server images, and IIS installation is performed via PowerShell. There are no examples or instructions for Linux users (e.g., using OpenSSL for certificates, deploying Linux VMs, or installing Apache/Nginx). Windows tools and patterns are mentioned exclusively and first, with no Linux parity.
Recommendations
  • Provide equivalent instructions for Linux users, such as using OpenSSL to create and export self-signed certificates.
  • Include examples for deploying Linux-based backend VMs (e.g., Ubuntu, CentOS) and installing a web server like Apache or Nginx.
  • Offer cross-platform command-line examples (e.g., Bash, Azure CLI) alongside PowerShell.
  • Mention Linux tools and patterns (e.g., file paths, certificate management) where relevant.
  • Clearly indicate that both Windows and Linux backend servers are supported, and provide parity in documentation steps.
GitHub Create Pull Request
Application Gateway Private Application Gateway deployment ...tion-gateway/application-gateway-private-deployment.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting Azure PowerShell examples and references before Azure CLI, and by using terminology and screenshots that are closely aligned with Windows-centric workflows (e.g., Azure portal navigation, PowerShell cmdlets). There are no explicit Linux shell or Bash examples, and the CLI instructions are less detailed compared to PowerShell. The documentation also references Windows tools and patterns (PowerShell, Azure portal) more prominently than cross-platform or Linux-native alternatives.
Recommendations
  • Provide Bash/Linux shell examples alongside PowerShell, especially for Azure CLI commands.
  • Ensure CLI instructions are as detailed and prominent as PowerShell instructions, including output examples and troubleshooting notes.
  • Include screenshots or instructions for Azure portal navigation on non-Windows platforms (e.g., browser on Linux/macOS).
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide platform-specific tips where relevant.
  • Consider adding ARM template and Terraform examples for key configuration steps, as these are cross-platform and popular in Linux environments.
  • Review terminology to avoid Windows-centric language and ensure parity for Linux administrators.
GitHub Create Pull Request
Application Gateway Manage traffic to App Service ...main/articles/application-gateway/configure-web-app.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides extensive PowerShell-based examples for all configuration steps, but does not include equivalent Linux shell (Bash/CLI) commands or scripts. All command-line automation is shown using Azure PowerShell, which is most commonly used on Windows. There is no mention of Azure CLI (az), Bash, or Linux-native tooling, and no examples for Linux users. This creates a bias toward Windows users and workflows.
Recommendations
  • Add equivalent Azure CLI (az) examples for each configuration step alongside PowerShell scripts.
  • Explicitly mention that both PowerShell and Azure CLI can be used, and provide guidance for Linux/macOS users.
  • Include Bash script examples for testing (e.g., using curl instead of Invoke-WebRequest).
  • Reference cross-platform tools and patterns where possible, rather than Windows-centric ones.
  • Ensure troubleshooting and testing instructions include Linux-compatible commands.
GitHub Create Pull Request
← Previous Page 1 of 34 Next →