Application Gateway

176
Total Pages
117
Linux-Friendly Pages
59
Pages with Bias
33.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (93)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/redirect-overview.md [View Details]
Scanned: 2025-07-17 00:00 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First Powershell Heavy
Summary:
The documentation page does not provide any command-line examples, but the only 'Next steps' link points to a PowerShell-based tutorial, which is Windows-centric. There are no references to Linux tools, Bash, or cross-platform CLI usage. This suggests a bias towards Windows and PowerShell, with Linux users left without clear guidance.
Recommendations:
  • Add links to equivalent tutorials using Azure CLI (az), which is cross-platform and commonly used on Linux.
  • Include Bash or shell script examples alongside PowerShell where command-line configuration is discussed.
  • Ensure that 'Next steps' and further reading sections provide parity for both Windows and Linux users.
  • Explicitly mention that Application Gateway can be managed from any OS using Azure CLI or REST API, and provide documentation links.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/how-to-troubleshoot-application-gateway-session-affinity-issues.md [View Details]
Scanned: 2025-07-17 00:00 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation demonstrates a Windows bias by providing PowerShell as the only CLI example for checking Application Gateway settings, exclusively recommending Fiddler (a Windows-centric tool) for network debugging, and referencing 'Run as administrator' for setup. There are no Linux or cross-platform alternatives or examples provided for these steps.
Recommendations:
  • Provide equivalent Azure CLI (az) and/or Azure Resource Manager (ARM) template examples for checking and configuring Application Gateway settings, which are cross-platform.
  • Include Linux-friendly network debugging tools such as tcpdump, Wireshark, or mitmproxy, with example usage for capturing and analyzing HTTP/HTTPS traffic.
  • When referencing setup steps, avoid Windows-specific instructions like 'Run as administrator' unless also providing the Linux/macOS equivalent.
  • Explicitly mention that Fiddler is one option and suggest alternatives for users on Linux or macOS.
  • Ensure screenshots and walkthroughs are not exclusively from Windows environments; include examples from other platforms where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/key-vault-certs.md [View Details]
Scanned: 2025-07-17 00:00 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for command-line operations, referencing PowerShell before (or instead of) Azure CLI or other cross-platform tools, and omitting Linux/Unix-specific instructions or examples. The use of PowerShell commands and terminology assumes a Windows environment, and there are no equivalent CLI/bash examples or guidance for Linux users.
Recommendations:
  • Provide Azure CLI examples alongside or before PowerShell examples for all command-line operations, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Where PowerShell is referenced, explicitly mention that the steps can be performed on any OS with PowerShell Core, or provide equivalent bash/CLI scripts.
  • Add Linux-specific notes or screenshots where portal navigation or file formats may differ.
  • Ensure that all ARM template and scripting examples are presented in a platform-neutral way, or provide both Windows (PowerShell) and Linux (CLI/bash) variants.
  • Update the 'Next steps' section to include links to CLI-based guides, not just PowerShell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/tutorial-autoscale-ps.md [View Details]
Scanned: 2025-07-17 00:00 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation is heavily biased toward 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 equivalents. The tutorial assumes a Windows environment (e.g., file paths like c:\appgwcert.pfx), and does not provide alternative instructions for Linux or cross-platform users.
Recommendations:
  • Provide equivalent Azure CLI (az) commands for each step, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include instructions for generating self-signed certificates using OpenSSL, which is available on all platforms, not just New-SelfSignedCertificate (Windows-only).
  • Use platform-agnostic file paths or note differences (e.g., c:\appgwcert.pfx vs. ~/appgwcert.pfx).
  • Explicitly mention that the tutorial can be followed on Linux/macOS and provide any required adjustments.
  • Add a section or callouts for Linux/macOS users, including how to install and use Azure PowerShell or Azure CLI on those platforms.
  • Consider providing a toggle or tabs for PowerShell and Azure CLI/Bash examples throughout the tutorial.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-overview.md [View Details]
Scanned: 2025-07-16 00:00 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation lists 'Create an application gateway using PowerShell' before 'using the Azure CLI' in the 'Next steps' section, which may suggest a Windows-first bias. However, the main content is platform-neutral and does not provide OS-specific examples or mention Windows-only tools elsewhere.
Recommendations:
  • List Azure CLI before PowerShell in the 'Next steps' section, as Azure CLI is cross-platform and more inclusive for Linux and macOS users.
  • Ensure that all example links and walkthroughs provide both PowerShell and Azure CLI options, or clearly indicate parity.
  • Consider adding explicit Linux/macOS instructions or references where appropriate to reinforce cross-platform support.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/how-to-troubleshoot-application-gateway-session-affinity-issues.md [View Details]
Scanned: 2025-07-16 00:00 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation demonstrates a Windows bias by providing PowerShell as the only CLI example for checking settings, exclusively referencing Fiddler (a Windows-centric tool) for network debugging, and using Windows-specific instructions such as 'Run as administrator.' There are no Linux or cross-platform alternatives or examples provided for these key troubleshooting steps.
Recommendations:
  • Provide Azure CLI and/or Azure Cloud Shell examples alongside or instead of PowerShell for checking Application Gateway settings, as these are cross-platform.
  • Include examples of using Linux-compatible network debugging tools such as tcpdump, Wireshark, or mitmproxy for capturing and analyzing HTTP/HTTPS traffic.
  • When referencing tools like Fiddler, mention cross-platform alternatives and provide installation and usage instructions for Linux and macOS.
  • Avoid instructions that are specific to Windows (e.g., 'right click and run as administrator') or provide equivalent steps for Linux/macOS environments.
  • Ensure screenshots and walkthroughs are not exclusively from Windows environments; include or link to examples from other platforms where possible.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/key-vault-certs.md [View Details]
Scanned: 2025-07-16 00:00 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by providing only PowerShell-based examples for configuring Azure Application Gateway with Key Vault certificates. There are no equivalent Azure CLI (cross-platform) or Bash/Linux examples, and PowerShell is referenced as the primary automation tool. The guidance and code snippets assume a Windows-centric workflow, with no mention of Linux shell environments or tooling. Additionally, the 'Next steps' section links only to a PowerShell-based guide.
Recommendations:
  • Add equivalent Azure CLI examples for all PowerShell code snippets, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Where automation steps are described, provide both PowerShell and Bash/Azure CLI workflows.
  • In sections referencing PowerShell, mention Azure CLI as an alternative and provide links to relevant CLI documentation.
  • Ensure that all portal-based instructions clarify that they are OS-agnostic, and avoid implying that PowerShell is the only automation option.
  • Update the 'Next steps' section to include links to Azure CLI and ARM/Bicep template guides, not just PowerShell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ssl-overview.md [View Details]
Scanned: 2025-07-16 00:00 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (such as the PFXImportCertStore function), providing configuration guidance and next steps primarily via PowerShell, and omitting Linux or cross-platform CLI examples. There is no mention of Linux tools or workflows for certificate management or Application Gateway configuration, and the only automation examples referenced are Windows-centric.
Recommendations:
  • Provide equivalent Azure CLI and/or Azure Cloud Shell examples for configuring Application Gateway and end-to-end TLS, alongside or before PowerShell instructions.
  • Reference cross-platform certificate management tools (such as OpenSSL) for preparing certificates, including how to generate and convert certificates to PFX format on Linux/macOS.
  • Link to documentation or guides for Linux users on how to manage certificates and interact with Azure Application Gateway.
  • Avoid referencing Windows APIs (such as PFXImportCertStore) as the primary or only source for supported algorithms; instead, summarize requirements in a platform-neutral way or provide equivalent Linux references.
  • Ensure that troubleshooting and next steps sections include both Windows and Linux workflows, or explicitly state that the instructions are cross-platform where applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/tutorial-autoscale-ps.md [View Details]
Scanned: 2025-07-16 00:00 • Page-level bias detected
▼

Page-Level Analysis

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 Bash, Azure CLI, or Linux/macOS equivalents. The instructions assume a Windows environment (e.g., file paths like c:\appgwcert.pfx), and there are no alternative steps or code samples for Linux users.
Recommendations:
  • Provide parallel examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux/macOS.
  • Include instructions for creating self-signed certificates using OpenSSL, which is standard on Linux/macOS, alongside the PowerShell method.
  • Use platform-neutral file paths (e.g., ~/appgwcert.pfx or ./appgwcert.pfx) or clarify the differences for Windows and Linux/macOS.
  • Explicitly state that the tutorial can be followed from Linux/macOS and provide any necessary prerequisites or differences.
  • Add a section or callouts for Linux/macOS users, highlighting any steps that differ or require alternative tools.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-infrastructure.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page exhibits a mild Windows bias, primarily through the exclusive use of PowerShell cmdlets for operational instructions (such as restarting the Application Gateway), and by referencing Azure PowerShell before Azure CLI when discussing how to change the subnet of an existing Application Gateway. There are no Linux shell or Azure CLI command examples provided, and no mention of Linux-specific tools or workflows, which may disadvantage users on non-Windows platforms.
Recommendations:
  • Provide equivalent Azure CLI (az) command examples alongside PowerShell cmdlets for all operational tasks, such as stopping and starting the Application Gateway.
  • When referencing tools for management (e.g., 'use Azure PowerShell or the Azure CLI'), list Azure CLI first or equally, and provide direct links to both sets of documentation.
  • Include example commands or scripts for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) environments to ensure platform parity.
  • Where possible, avoid assuming the use of PowerShell as the default, and clarify that all operations can be performed from any supported OS using the Azure CLI.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/certificates-for-backend-authentication.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Powershell Heavy 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. The only command-line reference is to PowerShell/certmgr, and the 'Next steps' section links to a PowerShell-specific guide. Linux tools and workflows are not mentioned or demonstrated.
Recommendations:
  • Add parallel instructions for exporting certificates using common Linux tools such as openssl, including command-line examples for exporting public keys and root certificates in Base-64 encoded X.509 (.CER) format.
  • Include screenshots or terminal output from Linux environments to illustrate the process.
  • Mention Linux and macOS as supported platforms explicitly, and provide guidance for users on those systems.
  • Balance references to Windows tools by listing Linux and cross-platform alternatives (e.g., openssl, certutil).
  • Update the 'Next steps' section to include links to Linux and cross-platform guides, not just PowerShell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/create-gateway-internal-load-balancer-app-service-environment.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation does not provide any OS-specific troubleshooting commands or examples, but in the one instance where it describes exporting a certificate, it only mentions using a browser to export the certificate in Base-64 encoded CER format. There are no instructions or examples for performing this task using command-line tools, such as PowerShell (Windows) or OpenSSL (Linux), nor is there any mention of Linux-specific tools or workflows. This omission may disadvantage Linux users who commonly use OpenSSL or similar utilities for certificate management.
Recommendations:
  • Add step-by-step instructions for exporting the ILB certificate using OpenSSL on Linux, e.g., using 'openssl s_client' to retrieve the certificate and 'openssl x509' to convert it to Base-64 encoded CER format.
  • If providing browser-based export instructions, clarify that this method is OS-agnostic, or provide alternative CLI-based methods for both Windows (PowerShell) and Linux (OpenSSL).
  • Include explicit examples for both Windows and Linux environments when describing certificate retrieval and upload processes.
  • Review the documentation for other potential OS-specific assumptions and ensure parity in troubleshooting steps for both Windows and Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-key-vault-common-errors.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation page demonstrates a Windows bias by providing only PowerShell command examples for certificate management, omitting equivalent Azure CLI (cross-platform) or Bash examples. The troubleshooting steps and automation guidance focus on PowerShell, which is traditionally associated with Windows environments. There is no mention of Linux or cross-platform workflows, and the use of PowerShell is presented as the default or only option for scripting and automation.
Recommendations:
  • Add equivalent Azure CLI (az) command examples alongside PowerShell for all certificate management and troubleshooting tasks.
  • Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide Bash script examples where appropriate.
  • Where PowerShell is referenced, clarify that it is available cross-platform, but also offer Bash/CLI alternatives to ensure Linux users are not excluded.
  • Review all automation and scripting guidance to ensure parity between Windows and Linux tooling, and avoid presenting Windows tools as the default.
  • Include a section or note highlighting cross-platform support and linking to relevant Azure CLI documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/create-multiple-sites-portal.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a strong Windows bias. It exclusively uses Windows Server as the backend VM OS, provides only PowerShell commands for configuration (with no Bash or Linux CLI alternatives), and instructs users to edit the Windows hosts file using Windows-specific paths and tools. There are no examples or instructions for Linux users, either for backend VM creation, web server installation, or local name resolution.
Recommendations:
  • Provide parallel instructions for creating Linux-based backend VMs (e.g., Ubuntu) and installing a web server such as Apache or Nginx.
  • Include Azure CLI/Bash examples alongside PowerShell for tasks like installing web servers or managing resources.
  • Add a section on editing the /etc/hosts file for Linux/macOS users, including appropriate commands (e.g., using sudo nano /etc/hosts).
  • Mention cross-platform tools and commands where possible, or clearly indicate when steps are Windows-specific.
  • Balance screenshots and code snippets to show both Windows and Linux environments where relevant.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/create-ssl-portal.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily biased toward Windows environments. All command-line examples for certificate creation and backend server setup use Windows PowerShell and Windows Server. There are no Linux or cross-platform alternatives provided for creating self-signed certificates, exporting PFX files, or setting up backend servers. The documentation assumes the user is running Windows locally and uses Windows-specific tools and patterns throughout.
Recommendations:
  • Provide equivalent Linux and macOS instructions for creating self-signed certificates (e.g., using OpenSSL) and exporting PFX files.
  • Include examples for deploying Linux-based backend servers (such as Ubuntu VMs) and installing a web server (e.g., Apache or Nginx) for testing.
  • When referencing command-line tools, offer both Windows (PowerShell) and Linux/macOS (Bash/OpenSSL) alternatives side by side.
  • Clarify in the prerequisites that the tutorial is currently Windows-centric, or update it to be explicitly cross-platform.
  • Consider using Azure CLI examples, which are cross-platform, for steps such as VM creation and extension installation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-listeners.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example
Summary:
The documentation provides a PowerShell example for enabling HTTP/2 support but does not include equivalent CLI or Linux-native examples (such as Azure CLI or ARM template snippets). There are no references to Windows-specific tools, but the exclusive use of PowerShell for code snippets and lack of Linux/CLI parity may disadvantage users on non-Windows platforms.
Recommendations:
  • Provide Azure CLI examples alongside PowerShell snippets for all configuration tasks, especially for enabling HTTP/2 support.
  • Include ARM template or Bicep examples where applicable to ensure cross-platform automation parity.
  • Explicitly mention that all configuration steps can be performed from any OS using the Azure CLI, and provide links to relevant CLI documentation.
  • Review the documentation for other sections where only PowerShell is used and add Linux-friendly alternatives.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-request-routing-rules.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation generally avoids OS-specific instructions, but in the section on HTTP-to-HTTPS redirection, the PowerShell (Windows-centric) example is listed before the Azure CLI (cross-platform) example. This ordering subtly prioritizes Windows tooling. However, Linux parity is largely maintained elsewhere, and CLI examples are present.
Recommendations:
  • List Azure CLI (cross-platform) instructions before PowerShell (Windows-centric) instructions to avoid implying a Windows-first workflow.
  • Ensure that all referenced guides (such as those for redirection and external site redirection) provide both PowerShell and CLI examples, and that both are equally visible.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows to reinforce cross-platform support.
  • Consider adding Bash or shell script examples where relevant, especially in sections that reference automation or scripting.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/how-to-tcp-tls-proxy.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a Windows bias by providing only Windows-based SQL Server VM creation instructions (with the default image being 'SQL Server 2022 Developer on Windows Server 2022'), and by instructing users to connect using SQL Server Management Studio, a Windows-only tool. There are no examples or guidance for deploying a Linux-based SQL Server VM or for connecting from Linux clients using cross-platform tools.
Recommendations:
  • Include instructions for creating a SQL Server VM on Linux (e.g., Ubuntu) as an alternative to the Windows-based VM.
  • Provide examples of connecting to the SQL Server backend using cross-platform tools such as Azure Data Studio, sqlcmd, or other CLI clients available on Linux and macOS.
  • Mention both Windows and Linux options when describing VM image selection, and clarify that the procedure works for both OS types.
  • Add screenshots or command-line examples for Linux users where appropriate, such as using the Azure CLI or SSH.
  • Ensure that any references to client tools (like SQL Server Management Studio) are accompanied by alternatives that work on Linux and macOS.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/how-to-troubleshoot-application-gateway-session-affinity-issues.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation demonstrates a Windows bias by providing PowerShell as the only CLI example for checking Application Gateway settings, exclusively recommending Fiddler (a Windows-centric tool) for HTTP debugging, and referencing Windows installation patterns (e.g., 'Run as administrator'). There are no Linux or cross-platform CLI examples (such as Azure CLI or Bash), nor are Linux-friendly web debugging tools (like tcpdump, Wireshark, or mitmproxy) mentioned. Instructions and screenshots are tailored to Windows environments, and Windows tools are introduced before any alternatives.
Recommendations:
  • Provide equivalent Azure CLI (az network application-gateway ...) and/or Bash examples for checking Application Gateway settings, alongside or before PowerShell.
  • Mention and give examples for cross-platform or Linux-friendly web debugging tools such as mitmproxy, Wireshark, or tcpdump, not just Fiddler.
  • Include installation and usage instructions for these tools on Linux/macOS as well as Windows.
  • Avoid Windows-specific instructions like 'Run as administrator' unless also providing the equivalent for other platforms.
  • Where screenshots are used, consider including examples from Linux desktops or web-based tools to ensure parity.
  • Explicitly state that the troubleshooting steps can be performed on any OS, and provide guidance for users on non-Windows systems.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/diagnostics.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation provides detailed instructions and code samples for enabling diagnostic logs using the Azure Portal and PowerShell, both of which are Windows-centric tools. There are no equivalent CLI or Bash examples for Linux/macOS users, and PowerShell is presented as the only scripting option. This creates a bias toward Windows environments and leaves out Linux-native workflows.
Recommendations:
  • Add Azure CLI (az) examples for enabling diagnostic logging, as the Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash shell script examples alongside PowerShell, or at least reference how Linux users can accomplish the same tasks.
  • Explicitly mention that PowerShell Core is cross-platform if retaining PowerShell examples, but still provide native Bash/Azure CLI alternatives.
  • Ensure that documentation sections do not assume a Windows environment by default; present cross-platform options equally or list Linux-friendly methods first where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ipv6-application-gateway-arm-template.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a bias toward Windows environments by only providing a PowerShell command (Remove-AzResourceGroup) for resource cleanup, referencing IIS (a Windows web server) for validation, and omitting any Linux-based examples or equivalent CLI commands. There are no instructions or examples for performing these tasks using Azure CLI, Bash, or Linux-native tools.
Recommendations:
  • Provide equivalent Azure CLI (az group delete) and/or Bash commands for resource cleanup alongside the PowerShell example.
  • Include validation steps using a Linux-based web server (such as Apache or Nginx) in addition to IIS, or clarify that the backend VMs could run either Windows or Linux.
  • Offer guidance or examples for users deploying and validating the setup from Linux/macOS environments, not just Windows.
  • Ensure that all code snippets and instructions are cross-platform where possible, or explicitly provide alternatives for both Windows and Linux users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/key-vault-certs.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a bias toward Windows and PowerShell by providing only PowerShell-based command-line examples for configuring Application Gateway with Key Vault certificates. There are no equivalent Azure CLI (cross-platform) or Bash/Linux shell examples. The instructions and code samples assume the use of PowerShell, which is most commonly associated with Windows environments, and the 'Next steps' section links exclusively to a PowerShell guide. This may hinder Linux or macOS users who prefer or require CLI/Bash-based workflows.
Recommendations:
  • Add equivalent Azure CLI (az) command examples alongside PowerShell for all configuration steps, especially for referencing Key Vault secrets and managing Application Gateway.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI or Bash, and provide links to relevant documentation.
  • In the 'Next steps' section, include links to guides for Azure CLI and ARM/Bicep templates, not just PowerShell.
  • Where possible, provide Bash script snippets or instructions for common Linux workflows (e.g., using environment variables, jq for JSON parsing, etc.).
  • Ensure that references to tools and commands are cross-platform or, if not, that alternatives are clearly documented.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/retirement-faq.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation page exclusively references Azure PowerShell scripts for migration, without mentioning or providing examples for Azure CLI or other cross-platform tools. There are no Linux-specific instructions or examples, and the guidance assumes use of PowerShell, which is traditionally associated with Windows environments. This creates a bias towards Windows users and may hinder Linux or cross-platform users.
Recommendations:
  • Provide equivalent Azure CLI commands and scripts for all migration steps, ensuring Linux and macOS users have clear, supported options.
  • Explicitly mention that Azure PowerShell is cross-platform, if relevant, and provide installation instructions for Linux/macOS if PowerShell must be used.
  • Include examples or references for Bash scripting or automation, not just PowerShell.
  • Add a section comparing migration approaches/tools for both Windows and Linux environments.
  • Ensure all tooling recommendations are platform-agnostic or offer parity between Windows and Linux.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ssl-overview.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and APIs (such as the PFXImportCertStore function), providing configuration guidance primarily via PowerShell, and omitting equivalent Linux or cross-platform command-line examples. The 'Next steps' section directs users to a PowerShell-based guide, and there is no mention of Azure CLI, Bash, or Linux certificate management tools. The documentation assumes familiarity with Windows-centric certificate formats and management patterns, with no guidance for Linux users.
Recommendations:
  • Include Azure CLI and/or Bash examples alongside or before PowerShell instructions for configuring Application Gateway and TLS.
  • Reference cross-platform certificate management tools (e.g., OpenSSL) for creating and managing certificates, and provide sample commands for exporting to PFX format on Linux.
  • Link to or provide guidance for Linux/macOS users on how to generate, convert, and upload certificates, including how to handle certificate chains.
  • Mention that PFX files can be created and managed on non-Windows systems, and provide relevant documentation links.
  • In the 'Next steps' section, add links to guides for configuring end-to-end TLS using Azure CLI, ARM templates, and the Azure Portal, not just PowerShell.
  • Where Windows APIs or tools are referenced, provide equivalent cross-platform alternatives or clarify that the process is not Windows-specific.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/migrate-v1-v2.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation is heavily biased toward Windows and PowerShell usage. All migration instructions, code samples, and tooling references are exclusively for Azure PowerShell, with no mention of Azure CLI, Bash, or cross-platform scripting. The prerequisites, script download, and execution steps assume a PowerShell environment, and there are no Linux- or macOS-specific instructions or examples. This creates a significant barrier for users on non-Windows platforms or those who prefer CLI/Bash scripting.
Recommendations:
  • Provide equivalent Azure CLI (az) commands and scripts for each PowerShell example, including authentication, resource queries, and migration steps.
  • Include explicit instructions for running the migration from Linux/macOS environments, such as using Azure Cloud Shell (Bash) or installing PowerShell Core cross-platform.
  • Mention and demonstrate how to use the Azure CLI to retrieve resource IDs, manage certificates, and perform other prerequisite steps.
  • Clarify whether the migration script can be run in Azure Cloud Shell (Bash) or if it requires PowerShell, and provide alternatives if possible.
  • Add a section comparing PowerShell and CLI approaches, helping users choose the best tool for their environment.
  • Ensure that any references to downloading and running scripts include Linux/macOS-compatible instructions (e.g., using wget/curl, handling .nupkg files without Windows tools).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/self-signed-certificates.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation displays a moderate Windows bias. While the main certificate generation workflow uses cross-platform OpenSSL commands, several sections and examples prioritize or exclusively reference Windows tools, paths, or procedures. The Azure PowerShell example is provided in detail, but there is no equivalent Azure CLI (cross-platform) example. Instructions for editing the hosts file and importing certificates into IIS link to Windows-specific resources, and file paths in PowerShell examples use Windows conventions. Linux-specific instructions or parity are often missing or appear after Windows references.
Recommendations:
  • Provide Azure CLI examples alongside or before Azure PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
  • Include Linux-specific instructions for editing the hosts file (e.g., /etc/hosts) and importing certificates into popular Linux web servers.
  • When referencing file paths, use cross-platform conventions or show both Windows and Linux examples.
  • When linking to web server documentation, include links for both Windows (IIS) and Linux (Apache, NGINX) equally and in parallel.
  • Explicitly mention Linux procedures for adding a root certificate to the trusted store (e.g., update-ca-certificates on Debian/Ubuntu).
  • Balance the order of presentation so that Linux and Windows tools/examples are given equal prominence.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configure-application-gateway-with-private-frontend-ip.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy Windows Tools
Summary:
The documentation demonstrates a clear Windows bias: it only provides instructions for deploying Windows Server virtual machines, uses PowerShell exclusively for scripting (including the Azure Cloud Shell example), and installs IIS (a Windows web server) as the backend workload. There are no examples or guidance for deploying Linux VMs, using Bash/CLI, or installing a Linux-based web server such as Apache or Nginx.
Recommendations:
  • Provide parallel instructions for creating Linux virtual machines (e.g., Ubuntu) as backend servers.
  • Include examples for installing a web server on Linux VMs (e.g., using apt to install Apache or Nginx).
  • Offer Azure CLI (Bash) equivalents for all PowerShell commands, especially for VM extension/script installation.
  • When referencing OS images, mention both Windows and popular Linux distributions, allowing users to choose.
  • Balance screenshots and walkthroughs to show both Windows and Linux scenarios where applicable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-ilb-arm.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation is heavily biased towards Windows and PowerShell. All command-line examples use Azure PowerShell cmdlets, with no mention or examples of Azure CLI (which is cross-platform and preferred on Linux/macOS) or ARM templates. The prerequisites and instructions reference Windows PowerShell and related tools exclusively. There are no Linux shell, Bash, or Azure CLI equivalents provided, nor any guidance for users on non-Windows platforms.
Recommendations:
  • Provide equivalent Azure CLI (az) command examples alongside or in place of PowerShell examples, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include a section or callout for Linux/macOS users, clarifying that all steps can be performed using Azure CLI and linking to relevant CLI documentation.
  • Avoid language that assumes the user is on Windows or using PowerShell (e.g., 'switch PowerShell mode'), or at least provide parallel instructions for Bash/CLI environments.
  • Consider including ARM/Bicep template examples for users who prefer declarative infrastructure-as-code approaches, which are platform-agnostic.
  • Update the prerequisites to mention both Azure PowerShell and Azure CLI, with links to installation instructions for all major platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-diagnostics.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation page demonstrates a Windows bias by providing only PowerShell examples for enabling logging, omitting equivalent Azure CLI or Bash examples that would be more familiar to Linux users. The use of PowerShell is presented as the primary (and only) scripting interface, and there is no mention of cross-platform tools or Linux-specific workflows. Additionally, tools like Excel and Visual Studio are referenced for log analysis and conversion, which are traditionally Windows-centric, without suggesting Linux-friendly alternatives. The ordering of examples and tool recommendations further reinforces a Windows-first perspective.
Recommendations:
  • Add equivalent Azure CLI and/or Bash examples alongside PowerShell commands for enabling diagnostic logging.
  • Explicitly mention that Azure CLI is cross-platform and provide usage instructions for Linux/macOS users.
  • Include references to Linux-friendly tools for log analysis, such as jq, csvkit, or open-source alternatives to Excel and Visual Studio.
  • Ensure that tool recommendations (e.g., for log conversion) include cross-platform or Linux-native options, such as Python scripts or open-source utilities.
  • Balance the order of presentation so that Windows and Linux approaches are given equal prominence, or alternate which is presented first.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configure-alerts-with-templates.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page references a procedure link that prioritizes CLI, PowerShell, and ARM template usage, but does not provide explicit Linux or cross-platform command-line examples. The 'Deploy to Azure' button leads to the Azure Portal, which is platform-agnostic, but the only procedural link mentions PowerShell before CLI and does not clarify Linux compatibility. There are no Linux-specific instructions or examples, and no mention of Bash or cross-platform scripting.
Recommendations:
  • Explicitly provide both Azure CLI (bash) and PowerShell examples for creating and managing alert rules, ensuring Linux users have clear, native instructions.
  • In procedural links and references, mention Azure CLI (bash) before or alongside PowerShell to avoid the appearance of Windows-first bias.
  • Add a section or note clarifying that all ARM template deployments and Azure CLI commands are fully supported on Linux, macOS, and Windows.
  • Where possible, include screenshots or walkthroughs using the Azure CLI in a Linux terminal environment.
  • Audit linked documentation to ensure Linux parity in all referenced procedures.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-backend-health.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by providing a dedicated PowerShell example and section before the Azure CLI example, without offering any Linux shell or Bash-specific guidance. There is no mention of Linux-native tools or workflows, and the PowerShell example is more prominently featured. This may make Linux users feel less supported or require them to adapt Windows-centric instructions.
Recommendations:
  • Add explicit Bash or Linux shell examples alongside PowerShell, especially for common tasks.
  • Present Azure CLI examples before or alongside PowerShell, as Azure CLI is cross-platform and more familiar to Linux users.
  • Include troubleshooting steps or tool recommendations that are relevant for Linux environments (e.g., using curl, openssl, or Linux-based network troubleshooting tools).
  • Ensure that any references to scripts or automation include both PowerShell and Bash equivalents where possible.
  • Review the order of examples and avoid always listing Windows/PowerShell first unless there is a clear reason.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-overview.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation page lists PowerShell (a Windows-centric tool) before Azure CLI in the 'Next steps' section, suggesting a preference for Windows tooling. No Linux-specific examples or tools are highlighted, and PowerShell is mentioned before the more cross-platform Azure CLI.
Recommendations:
  • List Azure CLI before PowerShell in the 'Next steps' section, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that both PowerShell and Azure CLI are available on Windows, Linux, and macOS, to avoid implying a Windows-only workflow.
  • Where possible, provide example commands for both PowerShell and Azure CLI in relevant sections, or link to both sets of instructions equally.
  • Consider adding a note or section highlighting Linux compatibility and common Linux tools for managing Azure resources.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/use-server-sent-events.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation does not provide any platform-specific examples or commands, but it also lacks any practical configuration examples for either Windows or Linux. This omission can be considered a subtle bias, as users on Linux (or any OS) do not receive guidance on how to configure their backend servers for SSE, such as example commands or configuration snippets for popular web servers (e.g., Nginx, Apache, IIS). The absence of Linux-specific examples is a missed opportunity for parity.
Recommendations:
  • Add practical configuration examples for both Linux and Windows environments. For Linux, include sample Nginx and Apache configurations showing the required headers for SSE.
  • If mentioning Windows/IIS, ensure Linux examples are provided first or alongside.
  • Include example shell commands (e.g., curl) for testing SSE endpoints on both Linux and Windows.
  • Explicitly mention that the guidance applies to all backend platforms and provide links or references to platform-specific documentation where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configure-web-app.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation page provides extensive PowerShell-based automation and scripting examples for configuring Azure Application Gateway with App Service, but does not include equivalent examples for Linux/Unix users (e.g., Azure CLI, Bash). All command-line automation is shown exclusively in PowerShell, which is primarily associated with Windows environments. There is no mention of cross-platform tools or Linux-native workflows, and no Bash, Azure CLI, or REST API examples are provided.
Recommendations:
  • Add Azure CLI examples for all PowerShell scripts, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Where automation is shown, provide both PowerShell and Bash/Azure CLI tabs, or at least link to equivalent Azure CLI documentation.
  • Explicitly mention that all PowerShell commands can be run on Linux/macOS with PowerShell Core, or provide guidance for non-Windows users.
  • Include REST API or ARM template examples for users who prefer declarative or cross-platform approaches.
  • Review and update the 'ms.custom' metadata to reflect cross-platform tooling, not just 'devx-track-azurepowershell'.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/mutual-authentication-overview.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation demonstrates a bias toward Windows and PowerShell by providing detailed PowerShell examples and references first, with Azure CLI examples following and no explicit Linux shell (bash) or cross-platform scripting examples. The 'Next steps' section directs users to a PowerShell-specific guide, and there is no mention of Linux tools or workflows for certificate extraction or management. The documentation assumes familiarity with Windows-centric tools and patterns.
Recommendations:
  • Provide equivalent bash/Linux shell examples for certificate extraction, management, and Azure CLI usage.
  • In the 'Next steps' section, include links to both PowerShell and Azure CLI (bash) guides for mutual authentication configuration.
  • When listing configuration options (Portal, PowerShell, CLI), avoid always listing PowerShell first; alternate or clarify that CLI is cross-platform.
  • Add references or examples for common Linux tools (e.g., openssl) for certificate chain extraction and validation.
  • Explicitly state that Azure CLI commands can be run on Windows, Linux, or macOS, and provide sample commands in bash syntax where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/tutorial-autoscale-ps.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation is heavily biased toward Windows environments by exclusively using Azure PowerShell and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate) for all steps. There are no examples or instructions for Linux users (e.g., using Azure CLI, OpenSSL, or Bash), and the prerequisites and workflow assume a Windows administrative PowerShell session. This makes it difficult for users on Linux or macOS to follow the tutorial.
Recommendations:
  • Provide parallel instructions and code examples using Azure CLI (az) for all resource creation and management steps.
  • Include Linux/macOS-compatible commands for certificate creation (e.g., using OpenSSL) and file path conventions.
  • Update the prerequisites section to mention both Azure PowerShell and Azure CLI, and clarify which is required for each example.
  • Where possible, use cross-platform tools or note platform-specific differences, ensuring Linux users are not excluded.
  • Reorder or balance examples so that Linux and Windows approaches are presented equally, rather than Windows-first.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools
Summary:
The documentation demonstrates a mild Windows bias, particularly in the Helm installation section, where Windows installation instructions (including a PowerShell/winget example) are presented before Linux instructions. The Windows-specific tool 'winget' is highlighted, and the PowerShell command is shown, while the Linux example is more generic. However, both platforms are covered, and most of the rest of the guide uses cross-platform Azure CLI and Bash commands.
Recommendations:
  • Present Linux and Windows installation instructions in parallel tabs or in the same order (Linux first or alphabetically) to avoid implicit prioritization.
  • Provide equally detailed installation steps for both Windows and Linux, including package manager options for Linux (e.g., apt, yum, snap) rather than only a curl script.
  • Avoid highlighting Windows-specific tools (like winget) without mentioning Linux equivalents (such as apt, yum, or snap).
  • Where possible, use cross-platform commands and clarify when a command is platform-specific.
  • Consider adding a macOS section if relevant, to further improve parity and inclusivity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-components.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation page generally avoids OS-specific tooling or examples, but in the 'Next steps' section, instructions for creating an application gateway are listed in the order: Azure Portal, Azure PowerShell, and then Azure CLI. PowerShell is a Windows-centric tool, while Azure CLI is cross-platform. Listing PowerShell before CLI may subtly prioritize Windows users.
Recommendations:
  • List Azure CLI instructions before or alongside PowerShell to reflect its cross-platform nature and promote parity for Linux and macOS users.
  • Explicitly mention that both Azure CLI and PowerShell are supported on multiple platforms, if true, to avoid the impression of Windows preference.
  • Wherever possible, provide parallel examples for both PowerShell and CLI in procedural documentation.
  • Review other documentation pages for similar ordering or tool prioritization to ensure consistent cross-platform inclusivity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-listeners.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example
Summary:
The documentation provides a PowerShell example for enabling HTTP/2 support but does not include equivalent Azure CLI or ARM template examples, which are more commonly used on Linux and cross-platform environments. No Linux-specific tools or command-line examples are mentioned, and the only automation example is Windows-centric.
Recommendations:
  • Add Azure CLI examples alongside PowerShell for all configuration steps, especially for enabling HTTP/2 support.
  • Include ARM/Bicep template snippets for declarative configuration, which are platform-agnostic.
  • Explicitly mention that all features are available via Azure CLI and portal, and provide links or examples.
  • Where PowerShell is used, provide a note or tabbed code blocks to show equivalent commands for Linux/macOS users.
  • Review for any other sections where only Windows tooling is referenced and ensure Linux parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-autoscaling-zone-redundant.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell for deployment tutorials and omitting equivalent Linux-friendly tools or examples (such as Azure CLI or ARM templates). The 'Next steps' section specifically links only to a PowerShell-based tutorial, and there are no mentions or examples for Linux users, which may hinder accessibility for non-Windows administrators.
Recommendations:
  • Include Azure CLI examples and tutorials alongside PowerShell instructions to ensure Linux and macOS users have clear guidance.
  • Add references to ARM/Bicep templates for platform-neutral, declarative deployments.
  • In the 'Next steps' section, provide parallel links for both PowerShell and Azure CLI tutorials.
  • Review and update all example commands and scripts to offer both Windows (PowerShell) and cross-platform (CLI/ARM) alternatives.
  • Explicitly mention that all features are accessible via multiple tools, not just PowerShell, to avoid implying Windows-only support.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-ilb-arm.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation exclusively uses Azure PowerShell cmdlets for all instructions and examples, with no mention or examples of equivalent Azure CLI (cross-platform) or Bash commands. It references 'Windows PowerShell' and links to PowerShell-specific resources, implicitly prioritizing Windows tooling and workflows. There are no Linux or macOS-specific instructions or parity examples, and no mention of using the Azure Cloud Shell or Bash, which are common for Linux users.
Recommendations:
  • Provide equivalent Azure CLI (az) command examples alongside or in place of PowerShell cmdlets for each step.
  • Include a section or callout for Linux/macOS users, clarifying that all operations can be performed from Bash or Azure Cloud Shell.
  • Avoid referring to 'Windows PowerShell' unless the instructions are truly Windows-specific; use 'PowerShell' or 'Azure CLI' as appropriate.
  • Link to both PowerShell and Azure CLI installation guides.
  • When referencing external documentation, include links to both PowerShell and CLI management guides.
  • Consider reordering examples or providing tabs for PowerShell and CLI to avoid Windows-first bias.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-backend-health-troubleshooting.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by providing PowerShell commands as the primary or only CLI examples, referencing Windows-specific tools (e.g., certlm.msc, netstat via cmd), and giving step-by-step instructions for Windows environments before or instead of Linux equivalents. Linux commands and workflows are mentioned less frequently, often as secondary notes or not at all, leading to an imbalance in cross-platform guidance.
Recommendations:
  • For every PowerShell example, provide an equivalent Azure CLI and, where relevant, Bash/Linux shell command.
  • When referencing Windows tools (e.g., certlm.msc, netstat in cmd), include parallel instructions for Linux (e.g., using openssl, ss, or netstat in a Linux shell).
  • In troubleshooting steps, avoid phrases like 'by using a browser or PowerShell' and instead say 'by using a browser, PowerShell, Azure CLI, or Bash', with examples for each.
  • When listing methods to check certificates or network connectivity, present Linux and Windows options together, or alternate which comes first.
  • Add explicit Linux/Bash command examples for tasks like checking open ports, viewing certificates, and resolving DNS (e.g., 'ss -tlnp', 'openssl', 'dig' or 'nslookup').
  • Ensure that all step-by-step instructions have Linux equivalents, not just Windows.
  • Consider a dedicated section or callouts for Linux users where workflows differ significantly.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-diagnostics.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
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. The 'Enable logging' section exclusively features a PowerShell cmdlet, and there is no mention of cross-platform tools or Linux command-line alternatives. Additionally, the workflow and screenshots are oriented toward tools and patterns more familiar to Windows users, such as PowerShell and Excel, and the page references Visual Studio and C# for log conversion, further reinforcing a Windows-centric approach.
Recommendations:
  • Add equivalent Azure CLI examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash or shell script examples where appropriate, especially for log retrieval and processing.
  • Mention and provide examples for viewing and analyzing logs using Linux-native tools (e.g., jq, grep, awk) in addition to Excel and Power BI.
  • Reference cross-platform editors and tools (such as VS Code) instead of, or alongside, Visual Studio.
  • Ensure that all step-by-step instructions and screenshots are applicable to users on both Windows and Linux platforms.
  • Explicitly state that all operations can be performed from Linux, macOS, or Windows, and provide links to relevant cross-platform documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-externally-managed-scheduled-autoscaling.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation exclusively provides PowerShell-based examples and instructions for implementing scheduled autoscaling with Azure Automation, with no mention of Bash, Azure CLI, or Python runbooks. This creates a Windows-centric bias, as PowerShell is primarily associated with Windows environments, and Linux-native approaches are not addressed.
Recommendations:
  • Add equivalent examples using Azure CLI (bash) scripts for Linux users, demonstrating how to adjust Application Gateway autoscale settings.
  • Include guidance or sample runbooks written in Python, which is supported by Azure Automation and widely used in cross-platform and Linux environments.
  • Explicitly mention that both PowerShell and Python runbooks are supported in Azure Automation, and provide links or references to relevant documentation.
  • Present examples for both Windows (PowerShell) and Linux (CLI/Python) side by side, or at least mention Linux-friendly alternatives before or alongside Windows-centric tools.
  • Clarify that Azure Automation is cross-platform and not limited to PowerShell or Windows tooling.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-key-vault-common-errors.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation page demonstrates a Windows bias by providing PowerShell-only command-line examples for certificate management, referencing Azure PowerShell and ARM templates, and omitting equivalent Azure CLI (cross-platform) or Bash examples. The troubleshooting steps and resolutions focus on Azure Portal and PowerShell, which are more familiar to Windows users, with no explicit guidance for Linux or non-Windows environments.
Recommendations:
  • Add Azure CLI (az) command examples alongside PowerShell for certificate upload and management, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Where PowerShell scripts are shown, provide equivalent Bash/CLI scripts or commands.
  • When mentioning tools or automation (e.g., ARM templates, PowerShell), also reference cross-platform alternatives (e.g., Azure CLI, Terraform).
  • Explicitly state that all operations can be performed from Linux/macOS using Azure CLI, and link to relevant documentation.
  • Balance the order of presentation so that cross-platform tools (CLI) are mentioned before or alongside Windows-specific tools (PowerShell).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-private-deployment.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation demonstrates a moderate Windows bias. PowerShell is given its own tab and is referenced multiple times, with explicit PowerShell cmdlets shown for preview registration and status checks. The CLI tab is present, but some instructions (such as viewing registration status) reference PowerShell cmdlets even in the CLI section. There are no explicit Linux/Bash shell examples or screenshots, and the workflow assumes familiarity with PowerShell and the Azure Portal (which is platform-agnostic but often associated with Windows environments). No Linux-specific tools, shell commands, or screenshots are provided.
Recommendations:
  • Ensure that all CLI sections use only Azure CLI commands and do not reference PowerShell cmdlets for status checks or outputs.
  • Add explicit Bash/Linux shell examples where applicable, especially for scripting or automation scenarios.
  • Include screenshots or terminal outputs from Linux environments where possible, or clarify that the CLI commands are cross-platform.
  • Consider adding a section or note clarifying that Azure CLI is fully supported on Linux/macOS and that all CLI examples are platform-agnostic.
  • If referencing PowerShell, also mention cross-platform PowerShell Core, or provide equivalent Bash scripts for parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-probe-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates a Windows bias by exclusively providing PowerShell cmdlet examples (e.g., New-AzApplicationGatewayProbeHealthResponseMatch) for configuring custom health probes, and by referencing Azure PowerShell as the primary automation tool. There are no equivalent examples or instructions for Linux users (e.g., Azure CLI, Bash, or ARM templates), and the 'devx-track-azurepowershell' custom tag further signals a Windows/PowerShell-centric approach. The 'Next steps' section also lists PowerShell before the Azure Portal, with no mention of Linux-friendly tooling.
Recommendations:
  • Add equivalent Azure CLI (az network application-gateway probe ...) examples alongside PowerShell cmdlets for all configuration tasks.
  • Include Bash or shell scripting examples where relevant, especially for automation scenarios.
  • Reference ARM/Bicep templates for declarative configuration, which are platform-agnostic.
  • Update 'Next steps' to mention Azure CLI and ARM/Bicep options, not just PowerShell.
  • Consider removing or balancing the 'devx-track-azurepowershell' tag with 'devx-track-azurecli' or similar.
  • Wherever PowerShell is mentioned, provide a parallel Linux/CLI example or a link to equivalent documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-ssl-policy-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by referencing PowerShell multiple times as the primary or sole method for configuration and details retrieval. There are no explicit Linux or Bash examples, and the only command-line tool mentioned by name is PowerShell. When mentioning CLI, it is not clarified whether this refers to Azure CLI (which is cross-platform) or something else, and PowerShell is always listed first. The 'Next steps' section links only to a PowerShell-based configuration guide, omitting Linux/Bash or Azure CLI examples.
Recommendations:
  • Provide explicit Azure CLI (az) examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
  • Clarify in all references to 'CLI' that this means Azure CLI, and provide Bash syntax examples where appropriate.
  • Include links in the 'Next steps' section to both PowerShell and Azure CLI/Bash configuration guides.
  • Wherever PowerShell is mentioned, ensure parity by also mentioning and providing examples for Linux/Bash environments.
  • Avoid listing PowerShell before CLI in lists or instructions; alternate or use neutral ordering.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/certificates-for-backend-authentication.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary:
The documentation exclusively describes certificate export using Windows tools (Certificate Manager, PowerShell), with detailed step-by-step instructions and screenshots for the Windows GUI. There are no Linux or cross-platform command-line examples, nor are alternative tools (like OpenSSL) mentioned. The only referenced automation is via PowerShell, and the 'Next steps' section links to a PowerShell-specific guide. This creates a strong Windows bias and leaves Linux users without guidance.
Recommendations:
  • Add equivalent instructions for exporting certificates using OpenSSL or other standard Linux tools.
  • Provide command-line examples for both Windows (certutil, PowerShell) and Linux/macOS (OpenSSL).
  • Include screenshots or terminal output for Linux workflows where appropriate.
  • Mention cross-platform tools early in the documentation, not just Windows-specific ones.
  • In the 'Next steps' section, link to Linux and cross-platform guides in addition to PowerShell.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/classic-to-resource-manager.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by providing detailed PowerShell-based instructions and commands for managing and migrating classic Application Gateway resources, with no equivalent Bash, Azure CLI, or Linux-native examples for key operations. PowerShell is referenced as the primary tool for both legacy and migration tasks, and the step-by-step cleanup process is exclusively shown using PowerShell cmdlets. While Azure CLI is mentioned as an option for deployment, no CLI or Linux shell examples are provided for migration or cleanup steps.
Recommendations:
  • Provide equivalent Azure CLI (bash) commands for all PowerShell examples, especially for migration and cleanup tasks.
  • Include Linux/macOS-specific instructions or notes where relevant, such as authentication and environment setup.
  • When listing deployment options, alternate the order or explicitly state parity between PowerShell and CLI to avoid 'windows_first' perception.
  • Reference cross-platform tools (e.g., Azure CLI) in all sections where PowerShell is mentioned, and link to their documentation.
  • Add a section or examples for managing classic resources using Azure CLI or REST API, if supported, or clarify if such options are unavailable.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-infrastructure.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page exhibits a mild Windows bias, primarily through the exclusive mention of Azure PowerShell for operational tasks (such as restarting the Application Gateway) and the absence of Linux/CLI examples or references. Where tooling is mentioned, PowerShell is referenced first or exclusively, and there are no explicit Linux command-line (Bash/Azure CLI) equivalents provided. This could make the documentation less approachable for Linux users or those who prefer cross-platform tools.
Recommendations:
  • Whenever PowerShell is referenced for operational tasks (e.g., restarting the Application Gateway), provide equivalent Azure CLI (az) commands, ideally in Bash syntax.
  • If referencing a tool or command, mention both PowerShell and CLI options, or present CLI first for neutrality.
  • Add explicit Linux/Bash examples where relevant, especially for common administrative tasks.
  • Review all procedural instructions to ensure they are not Windows-centric and are accessible to users on all platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-request-routing-rules.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation references both PowerShell and Azure CLI for configuration tasks, but PowerShell (a Windows-centric tool) is consistently mentioned before Azure CLI (cross-platform) in all relevant links. There are no Linux-specific examples or tools, and the ordering of examples and links subtly prioritizes Windows/PowerShell usage.
Recommendations:
  • Alternate the order of PowerShell and Azure CLI references so that CLI is sometimes mentioned first, or list them alphabetically to avoid perceived prioritization.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Wherever possible, provide example commands for both PowerShell and Azure CLI side by side.
  • Consider adding a short section or note for Linux users, clarifying that all CLI instructions are fully supported on Linux.
  • If relevant, include Bash shell examples or references to Linux-native tools/utilities.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-troubleshooting-502.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell (Windows-centric) commands for all troubleshooting steps, referencing Windows tools and patterns (such as IIS and PowerShell cmdlets), and omitting equivalent Azure CLI, Bash, or Linux-native instructions. There are no Linux-specific troubleshooting examples or mentions of Linux-based backend servers, and Windows/PowerShell approaches are always presented first and often exclusively.
Recommendations:
  • Provide Azure CLI (az) command examples alongside or before PowerShell cmdlets for all troubleshooting steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash shell command examples for network diagnostics (e.g., using curl, dig, nslookup, traceroute) to check DNS, connectivity, and health probe responses from Linux VMs.
  • Mention and give examples for common Linux web servers (such as Apache, Nginx) in addition to IIS when discussing backend configuration and health checks.
  • Clarify that Application Gateway supports both Windows and Linux backend servers, and provide troubleshooting guidance relevant to both.
  • Where referencing Windows-specific tools or patterns (such as PowerShell or IIS), always provide Linux equivalents or alternatives.
  • Add troubleshooting steps for checking firewall rules and service status on Linux (e.g., using systemctl, ufw, firewalld).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-websocket.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation page exhibits a Windows bias by referencing Azure PowerShell and linking to a PowerShell-based quickstart as the next step, without mentioning or providing equivalent Azure CLI (cross-platform) or Linux-native instructions. There are no Linux-specific or cross-platform command examples, and the only tooling mentioned for creating the gateway is Azure PowerShell, which is more commonly used on Windows.
Recommendations:
  • Include Azure CLI examples alongside or before Azure PowerShell instructions, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Update the 'Next steps' section to link to both PowerShell and Azure CLI quickstart guides, or to a neutral landing page where users can choose their preferred platform.
  • Explicitly mention that configuration can be performed using Azure CLI, ARM templates, or the Azure Portal, not just PowerShell.
  • If referencing sample template files, clarify that these can be deployed using both Azure CLI and PowerShell, and provide example commands for both.
  • Consider adding a short section or note for Linux/macOS users to ensure parity and inclusivity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy
Summary:
The documentation page lists PowerShell (a Windows-centric tool) before Azure CLI in the 'Next steps' section, suggesting a Windows-first approach. While both PowerShell and Azure CLI are mentioned, there is an implicit prioritization of Windows tooling. No explicit Linux examples or Linux-specific tools are highlighted.
Recommendations:
  • List Azure CLI before PowerShell in the 'Next steps' section to avoid implying Windows-first bias, as Azure CLI is cross-platform.
  • Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, and provide links to installation guides for both.
  • Add a note or section highlighting cross-platform support, reassuring Linux and macOS users that all configuration steps can be performed on their systems.
  • Where possible, provide example commands for both Azure CLI and PowerShell in the main body, not just in linked articles.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configure-alerts-with-templates.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page references the procedure to use ARM templates by linking to a guide that lists 'CLI, PowerShell, ARM' in its URL and description, but does not provide explicit Linux (Bash/Azure CLI) examples or instructions on this page. The only actionable deployment method shown is the 'Deploy to Azure' button, which opens the Azure Portal, a web-based tool, but there is no mention or example of how to deploy using cross-platform tools like Azure CLI from Linux/macOS. This may lead Linux users to feel unsupported or unclear about non-Windows deployment options.
Recommendations:
  • Add explicit Azure CLI (Bash) examples for deploying the ARM templates, suitable for Linux/macOS users.
  • Mention that ARM templates can be deployed using cross-platform tools such as Azure CLI, and provide a sample command.
  • Ensure that references to procedures or guides do not prioritize PowerShell or Windows tools in their naming or ordering.
  • If linking to external guides, clarify which steps are cross-platform and which are Windows-specific.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configure-application-gateway-with-private-frontend-ip.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy Windows Tools
Summary:
The documentation exhibits a strong Windows bias. It exclusively uses Windows Server as the VM OS in all examples, provides only PowerShell-based instructions for backend configuration (IIS installation), and does not mention or provide alternatives for Linux-based VMs or command-line tools (such as Bash or Azure CLI). The use of Windows-specific tooling and the absence of Linux guidance may hinder users who prefer or require Linux environments.
Recommendations:
  • Include parallel Linux-based examples for VM creation (e.g., using Ubuntu or CentOS images) alongside Windows Server.
  • Provide Bash/Azure CLI commands for installing a web server (such as Apache or Nginx) on Linux VMs, in addition to the PowerShell/IIS example.
  • Explicitly mention that both Windows and Linux VMs are supported as backend pool members, and link to relevant documentation for both.
  • Where scripts or commands are shown, offer both PowerShell (for Windows) and Bash (for Linux) alternatives.
  • Consider reordering or balancing the presentation so that Linux and Windows options are given equal prominence, rather than Windows-first.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/create-multiple-sites-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a clear Windows bias: it exclusively uses Windows Server for backend VMs, provides only PowerShell commands for configuration (specifically for installing IIS), and gives instructions for editing the Windows hosts file and using Windows-specific networking commands (ipconfig). There are no Linux-based examples, nor are there instructions for performing equivalent steps on Linux systems.
Recommendations:
  • Include parallel Linux examples for backend VMs, such as using Ubuntu or another popular Linux distribution.
  • Provide Bash/Azure CLI commands for installing a web server (e.g., Apache or Nginx) on Linux VMs, alongside the PowerShell/IIS example.
  • Add instructions for editing the /etc/hosts file on Linux/macOS systems, and mention the use of 'sudo systemctl restart systemd-resolved' or 'sudo systemd-resolve --flush-caches' for DNS cache flushing.
  • When referencing command-line tools, offer both Windows (ipconfig) and Linux/macOS (ifconfig, ip, or systemd-resolve) equivalents.
  • Where possible, use cross-platform Azure CLI commands instead of (or in addition to) PowerShell.
  • Explicitly state that the Application Gateway supports both Windows and Linux backend servers, and provide guidance for both.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ingress-controller-migration.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows Tools
Summary:
The documentation page primarily uses Azure CLI commands and references the Azure Portal for all examples and instructions. While Azure CLI is cross-platform, there are no explicit Linux shell or script examples, nor any mention of Linux-specific tools or workflows. The documentation assumes use of the Azure Portal (a web UI) and CLI, both of which are accessible from Windows, macOS, and Linux, but does not provide parity examples for Linux-native environments or mention Linux-specific considerations. There is also no mention of PowerShell, but the absence of Linux-specific examples or references constitutes a subtle Windows/Portal bias.
Recommendations:
  • Include explicit Linux shell (bash) examples where relevant, especially for scripting or automation.
  • Mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample commands for common Linux shells.
  • If referencing the Azure Portal, clarify that it is web-based and platform-agnostic, but also provide CLI-only workflows for users who prefer terminal-based management.
  • Add troubleshooting or migration notes for users running AKS clusters on Linux-based systems, if applicable.
  • Consider including Helm command examples for uninstalling AGIC, as Helm is often used in Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/create-gateway-internal-load-balancer-app-service-environment.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation does not provide any OS-specific troubleshooting commands or examples, but it does mention exporting the TLS/SSL certificate using a browser without specifying any platform. However, there are no explicit instructions or examples for Linux users (e.g., using OpenSSL or command-line tools), which may leave Linux administrators without clear guidance.
Recommendations:
  • Add step-by-step instructions for exporting the ILB certificate using common Linux tools such as OpenSSL.
  • Provide both Windows (e.g., using MMC or browser) and Linux (e.g., using curl or OpenSSL) methods for retrieving and exporting certificates.
  • Explicitly mention that the browser export method works on all platforms, or clarify any platform-specific steps if necessary.
  • Include command-line examples for both Windows (PowerShell) and Linux (bash) where relevant, to ensure parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/create-ssl-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a strong Windows bias. All command-line examples for certificate creation and backend server setup use Windows PowerShell and Windows-specific tools (e.g., New-SelfSignedCertificate, Export-PfxCertificate, Add-WindowsFeature). The tutorial instructs users to create Windows Server VMs and install IIS using PowerShell, with no mention of Linux alternatives or how to perform equivalent steps on Linux systems. There are no Linux shell, OpenSSL, or Apache/Nginx examples, and Linux VMs are not discussed as backend options.
Recommendations:
  • Provide equivalent Linux instructions for creating a self-signed certificate using OpenSSL, including export to PFX format.
  • Include examples for deploying Linux VMs (e.g., Ubuntu) as backend servers, and show how to install a web server (e.g., Apache or Nginx) for testing.
  • Show how to upload certificates generated on Linux to the Azure portal.
  • Where PowerShell is used, offer Bash or CLI alternatives for Linux/macOS users.
  • Explicitly state that both Windows and Linux VMs are supported as backends, and provide parity in setup instructions.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/custom-error.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation provides only Azure PowerShell examples for configuring custom error pages, with no mention of Azure CLI, Bash, or other cross-platform tools. This creates a Windows-centric bias, as PowerShell is most commonly associated with Windows environments, and Linux users are not given equivalent guidance.
Recommendations:
  • Add Azure CLI examples for all configuration steps, especially for creating and updating custom error pages at both global and listener levels.
  • Explicitly mention that Azure CLI and Bash can be used on Linux and MacOS, and provide equivalent commands.
  • Where PowerShell is referenced, clarify that it is available cross-platform, but still provide CLI/Bash alternatives for parity.
  • Consider including a table or section comparing PowerShell and CLI commands for common tasks.
  • Review screenshots and UI instructions to ensure they are not Windows-specific (e.g., file paths, UI elements).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/create-url-route-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy Windows Tools
Summary:
The documentation demonstrates a strong Windows bias. All virtual machine creation steps use Windows Server as the OS, and IIS (a Windows-only web server) is installed for backend testing. The only shell/command-line example provided is in PowerShell, with no mention of Linux VMs, Linux web servers (such as Apache or Nginx), or Bash/CLI equivalents. No Linux setup or validation steps are included, and the documentation assumes a Windows-centric workflow throughout.
Recommendations:
  • Provide parallel instructions for creating Linux-based backend VMs (e.g., Ubuntu or CentOS) alongside Windows VMs.
  • Include examples for installing a Linux web server (such as Apache or Nginx) on the Linux VMs, with corresponding validation steps.
  • Offer Bash/Azure CLI command examples for installing web servers and configuring VMs, not just PowerShell.
  • When referencing OS choices, present Windows and Linux options equally (e.g., 'Select Windows Server or Ubuntu from the list').
  • Add screenshots and validation steps for Linux-based backend servers to ensure parity.
  • Avoid assuming IIS or Windows-specific tools as the default for backend validation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/deploy-basic-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates a strong Windows and PowerShell bias. All command-line instructions use Azure PowerShell, with no mention of Azure CLI or Bash. The example virtual machines are Windows Server only, and the web server setup uses IIS via PowerShell scripts. There are no Linux VM examples, nor instructions for installing a Linux-based web server (e.g., Apache or Nginx). Windows tools and patterns are presented exclusively, with no Linux alternatives or parity.
Recommendations:
  • Provide Azure CLI (bash) equivalents for all PowerShell commands, especially for preview registration and VM extension management.
  • Include an example for deploying a Linux VM (e.g., Ubuntu) as a backend, alongside or instead of the Windows VM example.
  • Demonstrate how to install a web server (e.g., Apache or Nginx) on a Linux VM for backend testing, including the relevant shell commands.
  • When referencing VM creation, mention both Windows and Linux options, and clarify that Application Gateway supports both.
  • Balance screenshots and walkthroughs to show both Windows and Linux scenarios where possible.
  • Add a note or section highlighting cross-platform support and linking to Linux-specific documentation if available.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ipv6-application-gateway-arm-template.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation page demonstrates Windows bias by providing only a PowerShell command (Remove-AzResourceGroup) for resource cleanup, referencing IIS (a Windows web server) as the default backend and validation method, and omitting any Linux/CLI/bash alternatives for deployment, validation, or cleanup. There are no examples or instructions for users on Linux or macOS platforms.
Recommendations:
  • Provide equivalent Azure CLI (az group delete) and/or Bash commands for resource cleanup alongside the PowerShell example.
  • Include instructions or examples for deploying and validating the application gateway using Linux-based VMs (e.g., using Nginx or Apache instead of IIS).
  • Add notes or links for users on Linux/macOS platforms, clarifying how to perform each step without relying on Windows-specific tools.
  • Ensure that all code snippets and validation steps have both Windows and Linux/macOS equivalents, presented with parity or with Linux/CLI examples first where appropriate.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configure-web-app.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools Windows First
Summary:
The documentation page demonstrates a strong Windows bias by exclusively providing automation and CLI examples using Azure PowerShell cmdlets, with no equivalent Azure CLI (cross-platform) or Bash examples. All scripting and command-line instructions are written in PowerShell, which is most familiar to Windows users. There is no mention of Linux-native tools or workflows, and no guidance for users who prefer or require Bash or Azure CLI. The structure and examples assume a Windows-centric environment and toolset.
Recommendations:
  • Add equivalent Azure CLI (az) command examples for every PowerShell script block, using Bash syntax where appropriate.
  • Explicitly mention that both Azure PowerShell and Azure CLI are supported, and provide guidance for users on both Windows and Linux.
  • Where scripting is shown (e.g., for DNS, certificate management, backend pool configuration), provide Bash/Azure CLI alternatives alongside PowerShell.
  • Avoid assuming PowerShell as the default automation tool; present both PowerShell and CLI/Bash options in parallel tabs.
  • Include a note in the prerequisites or introduction clarifying that all steps can be performed on both Windows and Linux, and link to cross-platform tool installation guides.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/high-traffic-support.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation page demonstrates a bias towards Windows by referencing PowerShell and Windows-centric tooling for configuration tasks (e.g., configuring WAF custom rules, TLS policy), without providing equivalent CLI or Linux-native examples. There are no Linux shell (Bash/Azure CLI) commands or guidance, and PowerShell is mentioned as the method for advanced configuration. This may hinder Linux users or those preferring cross-platform tools.
Recommendations:
  • For every PowerShell-based configuration example or reference, provide an equivalent Azure CLI (az) example, which is cross-platform and works natively on Linux, macOS, and Windows.
  • When referencing documentation for configuration (e.g., WAF custom rules, TLS policy), link to both PowerShell and Azure CLI guides, or provide a unified guide with both sets of instructions.
  • Explicitly mention that all configuration steps can be performed using Azure CLI or ARM templates, and provide sample commands/scripts.
  • Avoid implying PowerShell is the only or primary way to perform advanced configuration; instead, present PowerShell and Azure CLI as equal options.
  • Add a section or callout for Linux/macOS users, highlighting cross-platform tools and any OS-specific considerations.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/how-to-troubleshoot-application-gateway-session-affinity-issues.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation demonstrates a Windows bias by providing PowerShell as the only CLI example for checking settings, exclusively recommending Fiddler (a Windows-centric tool) for network debugging, and referencing Windows-specific patterns such as 'Run as administrator'. There are no Linux or cross-platform alternatives offered for these tasks, and Windows tools are mentioned first and exclusively.
Recommendations:
  • Provide equivalent Azure CLI or Bash examples for checking Application Gateway settings, not just PowerShell.
  • Mention and give examples using cross-platform or Linux-native network debugging tools such as tcpdump, Wireshark, or mitmproxy alongside Fiddler.
  • Include instructions for Linux/macOS users, such as how to install and use these tools on their platforms.
  • Avoid Windows-specific instructions like 'Right click the setup executable, and run as administrator' without offering Linux/macOS installation guidance.
  • When referencing tools or commands, present cross-platform options first or in parallel, rather than defaulting to Windows.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/how-to-tcp-tls-proxy.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by providing only Windows-based examples for the SQL Server VM (specifically 'SQL Server 2022 Developer on Windows Server 2022') and by instructing users to use SQL Server Management Studio, a Windows-only tool, for connectivity testing. There are no Linux-based deployment or client examples, nor are cross-platform tools mentioned.
Recommendations:
  • Include instructions and screenshots for deploying a SQL Server VM on Linux (e.g., Ubuntu or Red Hat) as an alternative to Windows.
  • Provide examples for connecting to the SQL Server using cross-platform tools such as Azure Data Studio, sqlcmd, or other CLI/database clients available on Linux and macOS.
  • Explicitly mention that the process is similar on Linux and provide any Linux-specific configuration notes (e.g., firewall, authentication).
  • Wherever client tools are referenced, list both Windows and Linux options, and avoid assuming the user is on a Windows machine.
  • Consider including bash/CLI commands for relevant steps (e.g., using Azure CLI to create resources) alongside portal instructions.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/http-response-codes.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a mild Windows bias, particularly in the 504 Gateway time-out section, where IIS (a Windows web server) is mentioned first and in more detail than Nginx (a common Linux web server). The IIS section provides a direct link and specific configuration attribute, while the Nginx section is less detailed and lacks a direct link to official documentation. There are no PowerShell-specific examples, but Windows-centric tools and patterns are prioritized. No Linux command-line or troubleshooting examples are provided elsewhere.
Recommendations:
  • Present Nginx (Linux) and IIS (Windows) backend configuration guidance with equal detail, including direct links to official Nginx documentation (e.g., https://nginx.org/en/docs/) and explicit configuration examples.
  • When mentioning backend server types, alternate the order (e.g., Nginx first in some cases) or mention both together to avoid implicit prioritization.
  • Add troubleshooting examples or references for common Linux-based backend servers (such as Apache, Nginx, or Tomcat), not just IIS.
  • Where possible, provide cross-platform command-line examples (e.g., curl, tcpdump, or Linux log file locations) alongside any Windows-specific guidance.
  • Explicitly state that Application Gateway supports both Windows and Linux backend servers, and ensure parity in troubleshooting steps and documentation coverage.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ingress-controller-install-existing.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a Windows bias by providing several PowerShell-based command examples (marked as 'powershell-interactive'), using Windows-style variable assignment and scripting patterns, and referencing tools and workflows (such as Azure portal automation exports) that are more familiar to Windows users. Equivalent Linux/bash-native examples are missing or less prominent, and PowerShell is used even where bash would be more cross-platform appropriate. The documentation does not explicitly address Linux users or provide parity in scripting examples.
Recommendations:
  • For every PowerShell example, provide an equivalent bash shell example, especially for variable assignment and scripting blocks.
  • When referencing automation exports from the Azure portal, clarify which scripts are bash and which are PowerShell, and ensure both are available and referenced equally.
  • Avoid using PowerShell-specific syntax (e.g., $var=...) in generic command examples; prefer bash syntax or provide both.
  • Explicitly state that all commands work in both Windows and Linux environments, or note any differences.
  • Where possible, use Azure CLI commands in bash syntax as the primary example, as Azure CLI is cross-platform.
  • Add a section or callouts for Linux/macOS users to clarify any differences in procedure or tooling.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ipv6-application-gateway-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by exclusively using Windows Server as the backend VM example and providing only Azure PowerShell commands (with Windows-specific IIS installation) for backend setup and testing. There are no Linux-based backend examples, nor are there Bash/CLI or Linux-native instructions for deploying or testing the backend. This may hinder users who prefer or require Linux environments.
Recommendations:
  • Include parallel instructions for creating a Linux VM (e.g., Ubuntu) as a backend target, alongside the Windows Server example.
  • Provide Azure CLI (Bash) commands for installing a simple web server (such as nginx or Apache) on a Linux VM for testing, in addition to the PowerShell/IIS example.
  • Explicitly mention that both Windows and Linux VMs are supported as backend targets, and link to relevant documentation for both.
  • Where scripting is required, offer both PowerShell and Bash/CLI examples, or reference cross-platform scripts.
  • Ensure that screenshots and walkthroughs do not assume a Windows-only environment, and clarify any OS-specific steps.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/key-vault-certs.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by providing only Azure PowerShell examples for command-line operations, referencing PowerShell steps before mentioning the Azure CLI, and omitting explicit Linux/bash examples. The 'Next steps' section also directs users to a PowerShell-specific guide, reinforcing the Windows-centric approach. While Azure CLI is mentioned as a supported method, no CLI or bash examples are provided, and the only detailed command-line walkthrough uses PowerShell.
Recommendations:
  • Add equivalent Azure CLI (az) command examples alongside PowerShell for all command-line instructions, especially in sections where PowerShell is currently the only example.
  • When referencing command-line tools, mention Azure CLI and PowerShell together, or list Azure CLI first to balance platform representation.
  • Include bash shell snippets for ARM template deployments and secret referencing, demonstrating cross-platform usage.
  • In the 'Next steps' section, provide links to both PowerShell and Azure CLI/Linux guides for configuring TLS termination with Key Vault certificates.
  • Explicitly state that all operations can be performed from Linux/macOS using Azure CLI, and provide relevant instructions or links.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/mutual-authentication-certificate-management.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Windows Tools Powershell Heavy
Summary:
The documentation demonstrates a strong Windows bias. All certificate export steps are described using Windows GUI tools (Certificate Manager and Certificate Export Wizard), with screenshots and instructions specific to Windows. There are no equivalent instructions or screenshots for performing these tasks on Linux (e.g., using OpenSSL or command-line tools). The only Linux-specific content is a single 'cat' command for concatenating certificates, which is presented after the Windows 'type' command. The prerequisites, export, and certificate management sections omit Linux approaches entirely.
Recommendations:
  • Add parallel Linux instructions for exporting certificates, using OpenSSL or similar command-line tools, including example commands and expected outputs.
  • Provide Linux-specific screenshots or terminal outputs where appropriate.
  • Present Windows and Linux instructions side-by-side or clearly label them, rather than defaulting to Windows-first.
  • Include a section or note on how to locate and manage certificates on Linux systems.
  • Avoid referencing Windows-only tools (like Certificate Export Wizard) without Linux alternatives.
  • Ensure parity in detail and clarity between Windows and Linux instructions throughout the documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/migrate-v1-v2.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation is heavily focused on PowerShell-based migration, with all instructions, code snippets, and tooling references centered around PowerShell and the PowerShell Gallery. There are no examples or guidance for Linux or cross-platform users (e.g., Bash, Azure CLI), and the use of Windows-centric tools and patterns (such as .ps1 scripts, PowerShell modules, and Windows file paths) is pervasive. This creates a significant Windows bias and may hinder users on Linux or macOS from following the migration process.
Recommendations:
  • Provide equivalent Azure CLI (az) commands and scripts for all major steps, including authentication, resource discovery, and migration.
  • Offer Bash shell script examples or instructions for Linux/macOS users, especially for certificate handling and script execution.
  • Clearly state platform compatibility of the migration script and, if it is PowerShell Core compatible, provide explicit instructions for installing and running it on Linux/macOS.
  • Include download and execution instructions for the migration script that do not assume Windows or PowerShell Gallery (e.g., using wget/curl and pwsh).
  • Mention cross-platform Azure Cloud Shell as a primary option, and provide parity in examples for both PowerShell and Bash environments.
  • Add a section or callouts for Linux/macOS users, highlighting any prerequisites, differences, or limitations.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/multiple-site-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First
Summary:
The documentation page demonstrates a mild Windows bias by referencing Azure PowerShell before Azure CLI in both instructional text and example links. PowerShell-specific instructions are provided with more detail, and the PowerShell tutorial is consistently mentioned before the CLI equivalent. There are no explicit Linux/Windows tool differences in Azure CLI or PowerShell, but the ordering and emphasis may suggest a preference for Windows-centric tooling.
Recommendations:
  • Alternate the order of Azure CLI and Azure PowerShell references throughout the documentation to avoid implying a preference.
  • Provide equal detail and prominence to both Azure CLI and PowerShell instructions and examples.
  • Explicitly mention that both Azure CLI and PowerShell are cross-platform, and suitable for use on Windows, Linux, and macOS.
  • Consider including Bash or shell script examples where appropriate, especially for tasks that can be performed outside of Azure CLI/PowerShell.
  • Add a note or section clarifying that all features described are accessible from both Windows and Linux environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/mutual-authentication-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation demonstrates a Windows bias by providing detailed PowerShell examples and references before Azure CLI, omitting Linux-native command-line or OpenSSL examples for certificate handling, and directing users to a PowerShell-based configuration guide as the next step. There is no mention of Linux tools or workflows for extracting or managing certificates, and the CLI section is less detailed than the PowerShell section.
Recommendations:
  • Provide equal depth and detail for Azure CLI examples as for PowerShell, including multi-step workflows if needed.
  • Include Linux-native commands (e.g., OpenSSL) for extracting and managing certificate chains, especially in sections discussing certificate preparation.
  • When referencing further configuration guides, offer both PowerShell and CLI/Linux-based guides as next steps.
  • Avoid positioning PowerShell or Windows tools as the default or primary method; present CLI and cross-platform approaches first or in parallel.
  • Explicitly mention that all configuration steps can be performed on Linux/macOS using Azure CLI, and provide any necessary command-line differences or caveats.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/overview-v2.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell scripts and commands for migration and preview registration, with no explicit mention or examples of equivalent Bash or Linux shell commands. The 'Next steps' section also prioritizes PowerShell and does not provide Linux/CLI-focused tutorials. Azure CLI commands are shown, but the usage is wrapped in PowerShell cmdlets (e.g., Set-AzContext), which are not cross-platform, and there is no guidance for Linux users.
Recommendations:
  • Provide explicit Bash/Linux shell examples for all Azure CLI operations, avoiding reliance on PowerShell-specific cmdlets like Set-AzContext.
  • When referencing scripts for migration or management, mention both PowerShell and Bash/CLI alternatives, or clarify if only PowerShell is supported.
  • In 'Next steps' and tutorial links, include Linux/CLI-focused guides alongside or before PowerShell-based tutorials.
  • Where Azure CLI is used, ensure the examples are platform-agnostic and do not assume a PowerShell environment.
  • Add a section or note clarifying cross-platform support and linking to relevant Linux documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/private-link-configure.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation provides detailed configuration steps for Azure Application Gateway Private Link using the Azure portal, Azure PowerShell, and Azure CLI. However, the PowerShell section is more extensive and appears before the CLI section, which may suggest a Windows-first approach. There are no explicit Linux/Bash-specific examples or references to Linux tools, and the CLI section, while present, lacks parity in depth and troubleshooting guidance compared to PowerShell. No Linux-specific considerations or screenshots are provided.
Recommendations:
  • Ensure that Azure CLI (cross-platform) examples are as detailed and comprehensive as the PowerShell examples, including troubleshooting tips and references.
  • Consider placing Azure CLI instructions before or alongside PowerShell to avoid a Windows-first impression.
  • Add explicit notes or examples for Linux/macOS users, such as shell syntax, environment setup, and common issues.
  • Include screenshots or walkthroughs from a Linux environment where relevant.
  • Reference cross-platform tools (e.g., Bash, Cloud Shell) and clarify that Azure CLI works natively on Linux/macOS/Windows.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/proxy-buffers.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First Missing Linux Example
Summary:
The documentation provides detailed PowerShell examples for configuring request and response buffers, which are specific to Windows environments. While Azure CLI examples are included (which are cross-platform), the PowerShell section is more comprehensive, covering both creation and update scenarios. There are no explicit Linux shell (bash) or scripting examples, and the documentation references .NET SDK, which is more common in Windows-centric development. No Linux-specific tools or workflows are mentioned.
Recommendations:
  • Add bash (Linux shell) scripting examples for creating and updating Application Gateway buffer settings, similar to the PowerShell section.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide sample usage in a Linux terminal context.
  • Include references to cross-platform SDKs (such as Python, Java, or Node.js) in addition to .NET, to ensure parity for non-Windows developers.
  • Avoid presenting PowerShell as the only scripting option for automation; offer alternatives or note cross-platform options.
  • Consider reordering examples to present Azure CLI (cross-platform) before PowerShell, or group them together to avoid a 'Windows-first' impression.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation demonstrates a Windows bias by exclusively using Windows Server virtual machines as backend examples, providing only PowerShell commands for configuration (specifically for installing IIS), and omitting any Linux-based VM or CLI/Bash examples. The installation and testing instructions are tailored to Windows (IIS, PowerShell), with no mention of Linux alternatives (such as NGINX/Apache or Bash scripting). This may hinder Linux users from following the quickstart without additional research.
Recommendations:
  • Include parallel instructions for creating and configuring Linux VMs (e.g., Ubuntu) as backend servers.
  • Provide Linux-based examples for installing a web server (e.g., using Bash to install NGINX or Apache).
  • Offer Azure CLI and/or Bash script equivalents for all PowerShell commands, especially for installing and configuring backend servers.
  • When referencing VM images, mention both Windows and popular Linux distributions, and clarify that Application Gateway supports both.
  • Ensure screenshots and walkthroughs are not exclusively tied to Windows workflows or tools.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-template.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation page demonstrates a Windows bias by providing only a PowerShell example for resource cleanup, referencing IIS (a Windows web server) for validation, and omitting Linux/CLI alternatives for these steps. While the page mentions that the quickstart can be completed using the Azure portal, PowerShell, or CLI, the actual walkthrough and examples focus on Windows-centric tools and patterns, with no Linux or cross-platform command-line examples provided inline.
Recommendations:
  • Provide equivalent Azure CLI commands for resource cleanup (e.g., az group delete) alongside the PowerShell example.
  • Include validation steps using a Linux-based web server (such as Apache or Nginx) in addition to IIS, or clarify how the template could be modified for a Linux VM.
  • When referencing tools or commands, present cross-platform (CLI) options first or in parallel with Windows-specific (PowerShell) options.
  • Add explicit Linux/CLI walkthroughs or links to them in the main flow, not just in the 'Next steps' section.
  • Clarify in the prerequisites or template review that the example VMs are Windows-based, and provide guidance for users who prefer Linux.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-terraform.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a bias towards Windows by only including the creation of an Azure Windows Virtual Machine in the checklist, with no mention or example of creating a Linux virtual machine. There are no Linux-specific instructions or parity in the resource creation steps, and the only VM example is Windows-based.
Recommendations:
  • Include steps and Terraform resource examples for creating an Azure Linux Virtual Machine (using azurerm_linux_virtual_machine) alongside or as an alternative to the Windows VM example.
  • Update the checklist to mention both Windows and Linux VM creation, or provide a choice for the user.
  • Where applicable, provide verification and troubleshooting steps that are relevant for both Windows and Linux VMs.
  • Ensure that any scripts, commands, or code snippets (such as those for retrieving outputs or testing connectivity) are cross-platform or include both Windows and Linux command examples.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/redirect-http-to-https-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example Windows Tools
Summary:
The documentation is heavily biased towards Windows and PowerShell. All command-line examples use PowerShell, including certificate creation and IIS installation. The VM scale set is explicitly created with Windows Server 2016 Datacenter, and IIS (a Windows web server) is installed via PowerShell scripts. There are no Linux or cross-platform alternatives provided for certificate creation, backend server OS, or web server setup.
Recommendations:
  • Provide equivalent Linux examples for all command-line steps, such as using OpenSSL for certificate creation and Bash/Azure CLI for automation.
  • Include instructions for deploying a Linux-based VM scale set (e.g., Ubuntu) and installing a Linux web server (e.g., Nginx or Apache) as the backend pool.
  • Offer both PowerShell and Bash/Azure CLI scripts for all automation steps, and clarify which OS each applies to.
  • Mention Linux tools and patterns alongside Windows ones, and avoid assuming Windows as the default environment.
  • Add a section or callouts for cross-platform considerations, helping users choose the right instructions for their environment.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/redirect-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example Windows First
Summary:
The documentation page does not provide any OS-specific command-line examples, but the only 'Next steps' link points to a PowerShell-based tutorial, which is Windows-centric. There is no mention of Linux tools, Bash, or cross-platform CLI alternatives, and the guidance implicitly assumes a Windows-first approach by directing users to PowerShell.
Recommendations:
  • Provide equivalent examples and tutorials using Azure CLI (az), which is cross-platform and works on Linux, macOS, and Windows.
  • Include links to both PowerShell and Bash/Azure CLI tutorials in the 'Next steps' section.
  • Explicitly mention that configuration can be performed from any OS using the Azure Portal or Azure CLI, not just PowerShell.
  • Where possible, add code snippets or configuration steps for both Windows (PowerShell) and Linux (Bash/Azure CLI) environments.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/renew-certificates.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows First Missing Linux Example
Summary:
The documentation provides step-by-step instructions for renewing certificates on Azure Application Gateway, with detailed examples for Azure PowerShell and Azure CLI. However, the PowerShell example is presented before the Azure CLI example, and there is no explicit mention or example of Linux-native tools or workflows (such as Bash scripting or OpenSSL usage). The CLI example is generic but does not clarify Linux compatibility, and the PowerShell example is Windows-centric. There are no references to Linux file paths, shell environments, or common Linux certificate management patterns.
Recommendations:
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more familiar to Linux users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Linux-specific notes where relevant (e.g., file path formats, certificate file permissions).
  • Include a Bash shell example for uploading or renewing certificates, especially for scenarios where scripting is involved.
  • Reference common Linux tools (such as OpenSSL) for certificate preparation or validation.
  • Add a section or note on how to perform these tasks from a Linux environment, including any prerequisites or differences.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/retirement-faq.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Missing Linux Example Windows Tools
Summary:
The documentation page exclusively references Azure PowerShell scripts for migration tasks, with no mention of Azure CLI, Bash, or Linux-native tooling. All migration automation examples and caveats are centered on PowerShell, which is traditionally associated with Windows environments. There are no examples or guidance for Linux users or those preferring cross-platform tools.
Recommendations:
  • Provide equivalent Azure CLI (az) commands and scripts for migration tasks alongside PowerShell examples.
  • Explicitly mention that migration can be performed from Linux/macOS using Azure CLI or PowerShell Core, and provide relevant instructions.
  • Include Bash or shell script examples where automation is discussed, or clarify cross-platform compatibility of provided scripts.
  • Add a section comparing PowerShell and CLI approaches, helping users choose the best tool for their environment.
  • Ensure that all references to tooling (scripts, automation, troubleshooting) include both Windows and Linux-friendly options.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/self-signed-certificates.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Powershell Heavy Windows Tools Missing Linux Example
Summary:
The documentation demonstrates a moderate Windows bias. While the main certificate generation workflow uses OpenSSL (cross-platform), Windows tools and patterns are frequently mentioned first or exclusively. The IIS section is more detailed than Linux alternatives, and the only automation example for uploading certificates to Application Gateway is in Azure PowerShell, with no Azure CLI (cross-platform) or ARM/Bicep alternatives. The hosts file editing link is Windows-specific, and some instructions assume a Windows file path structure.
Recommendations:
  • Provide Azure CLI examples alongside or before Azure PowerShell for certificate upload and configuration, as CLI is cross-platform.
  • Include Linux/macOS-specific instructions for editing the hosts file (e.g., /etc/hosts), not just a Windows link.
  • Balance the web server configuration sections: give equal detail for Apache and NGINX as for IIS, including links to official documentation for Linux.
  • Use neutral file path examples (e.g., ~/Downloads/contoso.cer or /home/user/contoso.cer) instead of Windows paths (C:\Users\...).
  • Mention that OpenSSL is available on macOS as well as Linux and Windows.
  • If referencing GUI tools or wizards, ensure Linux alternatives are mentioned or clarify if they are Windows-only.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ssl-certificate-management.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First
Summary:
The documentation references both PowerShell and Azure CLI for listing SSL certificates, but it mentions the PowerShell command before the Azure CLI command. No Linux-specific tools or examples are provided, but the CLI example is cross-platform. There are no exclusive Windows tools or patterns, and the rest of the documentation is portal-focused and platform-neutral.
Recommendations:
  • When listing command-line examples, alternate the order or explicitly mention that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Consider providing a Linux shell example (e.g., Bash) for Azure CLI usage to reinforce cross-platform applicability.
  • Add a brief note clarifying that PowerShell is available on Linux and macOS as well, or link to installation instructions for non-Windows users.
  • Ensure that any future command-line or scripting examples are balanced between platforms, or use Azure CLI as the default for cross-platform parity.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/tutorial-protect-application-gateway-ddos.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example Powershell Heavy Windows Tools
Summary:
The documentation demonstrates a Windows bias by exclusively using Windows Server as the backend VM example, providing only PowerShell commands for configuration (specifically for installing IIS), and omitting any Linux-based examples or equivalent Bash/CLI instructions. The tutorial assumes the use of Windows tools and environments, with no mention of Linux alternatives or parity.
Recommendations:
  • Provide parallel instructions for deploying Linux-based backend VMs (e.g., Ubuntu) alongside the Windows Server example.
  • Include Bash/Azure CLI commands for installing a web server (such as Apache or Nginx) on Linux VMs, in addition to the PowerShell/IIS example.
  • Explicitly mention that Application Gateway supports both Windows and Linux backend servers, and offer guidance for both.
  • When showing code or command-line examples, present both PowerShell (for Windows) and Bash/CLI (for Linux) versions.
  • Balance the order of presentation so that Linux and Windows options are given equal prominence, or clarify that the steps are similar for both platforms.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ssl-overview.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Windows First Missing Linux Example
Summary:
The documentation page exhibits a Windows bias by referencing Windows-specific tools and APIs (such as the PFXImportCertStore function), providing configuration guidance and next steps only for PowerShell (a Windows-centric tool), and omitting Linux or cross-platform command-line examples. The documentation also references ARM templates, but PowerShell is emphasized as the primary method. There are no Linux-native instructions or examples, nor are cross-platform tools (like Azure CLI or Bash) mentioned.
Recommendations:
  • Provide equivalent Azure CLI (az) examples for all PowerShell-based instructions, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Linux/Bash shell command examples for certificate management tasks (such as converting certificates to PFX using OpenSSL), not just references to Windows APIs.
  • Reference cross-platform certificate tools (e.g., OpenSSL) alongside or before Windows-specific tools and APIs.
  • In 'Next steps', offer links to both PowerShell and Azure CLI (and/or ARM template) guides for configuring end-to-end TLS.
  • Where possible, use neutral language (e.g., 'use your preferred tool' or 'using PowerShell, Azure CLI, or the Azure Portal') rather than defaulting to Windows/PowerShell.
  • Add troubleshooting and configuration notes relevant to Linux environments (such as file permissions, certificate storage locations, etc.).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/tutorial-autoscale-ps.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Powershell Heavy Windows Tools Missing Linux Example Windows First
Summary:
The documentation is heavily biased toward 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 Linux or cross-platform alternatives. There are no CLI, Bash, or Linux-native certificate generation examples, and the tutorial assumes a Windows environment throughout.
Recommendations:
  • Provide equivalent Azure CLI (az) commands for all resource creation and configuration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Linux-native instructions for generating self-signed certificates (e.g., using OpenSSL) alongside the PowerShell examples.
  • Clearly indicate which steps are platform-specific and offer alternatives for non-Windows users.
  • Reorganize the documentation so that cross-platform (CLI) examples are presented first or in parallel with PowerShell/Windows-specific instructions.
  • Add notes or links to relevant documentation for Linux/macOS users, such as installing Azure CLI or using Bash scripts.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/use-server-sent-events.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Missing Linux Example
Summary:
The documentation does not provide any platform-specific examples or commands, but it also lacks any practical configuration examples for either Windows or Linux. There is no explicit Windows bias, but the absence of concrete examples (such as using Powershell, Windows tools, or Linux shell commands) means Linux parity is not addressed. If future updates add examples, care should be taken to include both Windows and Linux instructions.
Recommendations:
  • When adding practical configuration steps, provide both Windows (e.g., Powershell, CMD) and Linux (e.g., Bash, systemd) examples for setting headers and configuring backend servers.
  • Include sample commands for setting HTTP headers in both Windows (IIS, Powershell) and Linux (Apache, Nginx, curl) environments.
  • If referencing tools or logs, mention both Windows and Linux equivalents (e.g., Event Viewer and journalctl, or IIS logs and Apache/Nginx logs).
  • Ensure that any troubleshooting or monitoring steps are cross-platform.