Application Gateway
188
Total Pages
113
Linux-Friendly Pages
75
Pages with Bias
39.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
981 issues found
Showing 426-450 of 981 flagged pages
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/mutual-authentication-overview.md
.../application-gateway/mutual-authentication-overview.md
High Priority
View Details →
Detected Bias Types
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.
Create Pull Request
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/tutorial-autoscale-ps.md
.../articles/application-gateway/tutorial-autoscale-ps.md
High Priority
View Details →
Detected Bias Types
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.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller.md
...ploy-application-gateway-for-containers-alb-controller.md
High Priority
View Details →
Detected Bias Types
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.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-autoscaling-zone-redundant.md
...eway/application-gateway-autoscaling-zone-redundant.md
High Priority
View Details →
Detected Bias Types
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.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-ilb-arm.md
...les/application-gateway/application-gateway-ilb-arm.md
High Priority
View Details →
Detected Bias Types
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.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-backend-health-troubleshooting.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-backend-health-troubleshooting.md
High Priority
View Details →
Detected Bias Types
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.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-diagnostics.md
...application-gateway/application-gateway-diagnostics.md
High Priority
View Details →
Detected Bias Types
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.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-externally-managed-scheduled-autoscaling.md
...ation-gateway-externally-managed-scheduled-autoscaling.md
High Priority
View Details →
Detected Bias Types
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.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-key-vault-common-errors.md
...gateway/application-gateway-key-vault-common-errors.md
High Priority
View Details →
Detected Bias Types
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).
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-private-deployment.md
...tion-gateway/application-gateway-private-deployment.md
High Priority
View Details →
Detected Bias Types
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.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-probe-overview.md
...lication-gateway/application-gateway-probe-overview.md
High Priority
View Details →
Detected Bias Types
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.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-ssl-policy-overview.md
...ion-gateway/application-gateway-ssl-policy-overview.md
High Priority
View Details →
Detected Bias Types
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.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/certificates-for-backend-authentication.md
...ion-gateway/certificates-for-backend-authentication.md
High Priority
View Details →
Detected Bias Types
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.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/classic-to-resource-manager.md
...les/application-gateway/classic-to-resource-manager.md
High Priority
View Details →
Detected Bias Types
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.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-infrastructure.md
...es/application-gateway/configuration-infrastructure.md
High Priority
View Details →
Detected Bias Types
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.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-troubleshooting-502.md
...ion-gateway/application-gateway-troubleshooting-502.md
High Priority
View Details →
Detected Bias Types
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).
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-websocket.md
...s/application-gateway/application-gateway-websocket.md
High Priority
View Details →
Detected Bias Types
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.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configure-application-gateway-with-private-frontend-ip.md
...configure-application-gateway-with-private-frontend-ip.md
High Priority
View Details →
Detected Bias Types
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.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/create-multiple-sites-portal.md
...es/application-gateway/create-multiple-sites-portal.md
High Priority
View Details →
Detected Bias Types
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.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/create-ssl-portal.md
...main/articles/application-gateway/create-ssl-portal.md
High Priority
View Details →
Detected Bias Types
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.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/custom-error.md
...blob/main/articles/application-gateway/custom-error.md
High Priority
View Details →
Detected Bias Types
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).
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/create-url-route-portal.md
...rticles/application-gateway/create-url-route-portal.md
High Priority
View Details →
Detected Bias Types
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.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/deploy-basic-portal.md
...in/articles/application-gateway/deploy-basic-portal.md
High Priority
View Details →
Detected Bias Types
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.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ipv6-application-gateway-arm-template.md
...ation-gateway/ipv6-application-gateway-arm-template.md
High Priority
View Details →
Detected Bias Types
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.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configure-web-app.md
...main/articles/application-gateway/configure-web-app.md
High Priority
View Details →
Detected Bias Types
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.