Application Gateway
188
Total Pages
113
Linux-Friendly Pages
75
Pages with Bias
39.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
841 issues found
Showing 26-50 of 841 flagged pages
Application Gateway
Troubleshoot Bad Gateway errors - Azure Application Gateway
...ion-gateway/application-gateway-troubleshooting-502.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples and referencing Windows-centric tools and patterns (e.g., IIS, PowerShell cmdlets, classic VM endpoints). There are no CLI (az), Bash, or Linux-specific troubleshooting commands or examples. Windows tools and terminology are mentioned before or instead of Linux equivalents, and Linux troubleshooting steps are missing throughout.
Recommendations
- Add Azure CLI (az) and Bash examples alongside PowerShell for all resource queries and configuration checks.
- Include troubleshooting steps and examples for Linux-based backend servers (e.g., Apache, Nginx), not just IIS.
- Reference Linux firewall tools (e.g., iptables, ufw) and commands for checking port and network connectivity.
- Provide parity in endpoint configuration guidance for Linux VMs, not just classic Windows VM endpoints.
- Ensure that documentation language and examples are platform-neutral or explicitly cover both Windows and Linux scenarios.
Create Pull Request
Application Gateway
Deploy Application Gateway Basic (Preview)
...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 bias. All command-line examples for registering/unregistering the preview and installing backend software use Azure PowerShell and Windows-specific tools (e.g., Add-WindowsFeature for IIS). The virtual machine creation steps exclusively use Windows Server as the example OS, with no mention of Linux alternatives or equivalent commands for Bash/CLI. There are no Linux VM setup instructions, nor examples for installing a web server on Linux. Windows tools and patterns are presented exclusively and before any Linux equivalents, which are entirely absent.
Recommendations
- Provide equivalent Azure CLI (az) commands for registering/unregistering the preview, alongside PowerShell examples.
- Include Linux VM creation steps in the backend pool section, such as creating Ubuntu or other Linux VMs.
- Add instructions for installing a web server (e.g., Apache or Nginx) on Linux VMs, using Bash scripts or Azure VM extensions.
- Show how to add Linux VMs to the backend pool, and demonstrate testing the application gateway with Linux-based backends.
- Ensure screenshots and walkthroughs are OS-neutral or include both Windows and Linux variants.
- Explicitly mention that Application Gateway supports both Windows and Linux backend servers, and provide parity in documentation examples.
Application Gateway
Configure Azure Application Gateway TCP/TLS proxy
...n/articles/application-gateway/how-to-tcp-tls-proxy.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server as the SQL backend, referencing SQL Server Management Studio (a Windows-only tool) for client connectivity, and omitting any mention of Linux-based SQL server deployment or Linux-compatible client tools. All examples and screenshots are based on Windows environments, with no guidance for Linux users.
Recommendations
- Include instructions for deploying SQL Server on Linux (e.g., Ubuntu) as an alternative backend VM.
- Provide examples of connecting to the Application Gateway using Linux-compatible SQL clients such as sqlcmd, Azure Data Studio, or DBeaver.
- Add screenshots and command-line examples for Linux environments where appropriate.
- Explicitly mention cross-platform options and parity in prerequisites and tool recommendations.
- Ensure that resource cleanup instructions cover both Windows and Linux scenarios.
Application Gateway
Configure Request and Response Buffers
...lob/main/articles/application-gateway/proxy-buffers.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation provides configuration examples using Azure CLI, PowerShell, and ARM templates. PowerShell examples are detailed and cover both creation and update scenarios, while no equivalent Linux shell (bash) or cross-platform scripting examples are given. PowerShell is a Windows-centric tool, and its usage is emphasized with multiple code blocks and update scenarios. There is no mention of Linux-specific tools or patterns, such as Bash scripting or Cloud Shell usage. The reference to Azure SDK for .NET further reinforces a Windows-centric approach.
Recommendations
- Add explicit Bash shell examples for Linux users, especially for updating existing Application Gateways.
- Clarify that Azure CLI commands work cross-platform and provide sample usage in Bash.
- Include references to cross-platform SDKs (e.g., Python, Java) in addition to .NET.
- Mention Azure Cloud Shell as a platform-neutral way to run CLI commands.
- Balance PowerShell and CLI coverage, ensuring Linux users are not left out in update scenarios.
Application Gateway
Migrate from V1 to V2 - Azure Application Gateway
...lob/main/articles/application-gateway/migrate-v1-v2.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits a strong Windows bias. All migration instructions, examples, and scripts are provided exclusively using PowerShell, with no mention of Bash, Azure CLI, or Linux-native tooling. Script installation and usage patterns are tailored to Windows/PowerShell environments, and there is no guidance for Linux or macOS users. The documentation assumes familiarity with PowerShell and Windows-centric workflows, omitting equivalent steps for cross-platform or Linux-native environments.
Recommendations
- Provide Azure CLI equivalents for all PowerShell commands and scripts, including examples for Linux/macOS terminals.
- Include Bash script samples or instructions for running migration tasks on Linux.
- Document how to use Azure Cloud Shell (Bash) for migration, not just PowerShell.
- Explicitly state cross-platform compatibility of scripts, or provide platform-specific instructions where needed.
- Add troubleshooting notes for common Linux/macOS issues (e.g., file permissions, module installation).
- List prerequisites and installation steps for Linux and macOS environments alongside Windows.
- Ensure all downloadable scripts are tested and supported on Linux/macOS PowerShell (pwsh) and Azure CLI.
Application Gateway
Quickstart: Direct web traffic using a Resource Manager template
.../articles/application-gateway/quick-create-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively providing PowerShell commands for resource cleanup, referencing IIS (a Windows web server) for validation, and omitting Linux-based examples or alternatives (such as using Apache/Nginx or Bash/Azure CLI for resource management). No Linux-specific instructions or parity is offered for users deploying or validating on Linux VMs.
Recommendations
- Provide equivalent resource cleanup instructions using Azure CLI (az group delete) and Bash shell commands.
- Include validation steps for Linux VMs, such as installing Apache or Nginx and testing with curl or a browser.
- Offer examples for both Windows and Linux VM configurations in the ARM template and validation sections.
- Ensure that references to tools (e.g., IIS, PowerShell) are balanced with Linux alternatives and not presented as the default or only option.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell scripts for migration tasks, without mentioning or providing examples for Azure CLI, Bash, or other cross-platform tools. There are no Linux or platform-agnostic migration instructions or examples, and the only automation guidance is centered on PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Provide equivalent Azure CLI (az) commands or scripts for all migration steps, ensuring Linux and macOS users have clear guidance.
- Explicitly mention that migration can be performed from any OS, and clarify if PowerShell Core (cross-platform) is supported, or provide Bash alternatives.
- Include examples or references for Bash scripts or automation using other cross-platform tools (e.g., Terraform, ARM templates) where applicable.
- Reorder or supplement sections to present cross-platform options (Azure CLI, Bash) before or alongside PowerShell, to avoid implying Windows is the primary or only supported environment.
Application Gateway
Redirect overview for Azure Application Gateway
...main/articles/application-gateway/redirect-overview.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates Windows bias by referencing only Windows-centric tools and workflows (e.g., Azure portal, PowerShell tutorial), and omitting Linux-specific examples or CLI instructions. The 'Next steps' section links exclusively to a PowerShell-based tutorial, with no mention of Azure CLI or Bash alternatives. There is no guidance for Linux users or parity in example commands.
Recommendations
- Add equivalent Azure CLI and Bash examples for configuring redirects, alongside PowerShell instructions.
- Include links to tutorials for Linux users, such as 'Configure URL redirection using Azure CLI' or 'Configure URL redirection using Bash'.
- Ensure that references to configuration steps do not prioritize Windows tools (PowerShell, Azure portal) over cross-platform options.
- Explicitly mention that Application Gateway configuration can be performed from Linux, macOS, and Windows environments, and provide parity in documentation.
Application Gateway
Tutorial: Improve web application access - Azure Application Gateway
.../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 towards Windows and PowerShell. All examples use Azure PowerShell cmdlets and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of equivalent Linux or cross-platform approaches. There are no Bash, Azure CLI, or Linux-native certificate generation examples, and prerequisites assume a Windows/PowerShell environment. This may exclude or inconvenience users on Linux or macOS platforms.
Recommendations
- Provide equivalent Azure CLI (az) examples alongside PowerShell for each step.
- Include Linux/macOS instructions for generating self-signed certificates (e.g., using openssl).
- Clarify that Azure PowerShell can be used cross-platform, but also offer Bash/CLI alternatives.
- Mention and link to platform-agnostic tools and documentation where possible.
- Reorder or parallelize examples so that Windows and Linux approaches are presented together, not Windows first.
Application Gateway
Troubleshoot backend health issues in Azure Application Gateway
...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 through frequent use of PowerShell commands and examples, prioritization of Windows tools and workflows (such as certlm.msc, netstat, and Windows command prompt), and lack of equivalent Linux command examples in several troubleshooting steps. While OpenSSL is mentioned for certificate inspection, most step-by-step instructions and troubleshooting commands are Windows-centric, with Linux alternatives either missing or relegated to brief mentions.
Recommendations
- Provide Linux command-line equivalents for all PowerShell and Windows command prompt examples (e.g., use curl, nc, ss, ip, and OpenSSL for connectivity and certificate checks).
- Include Linux-specific instructions for inspecting certificates (e.g., using openssl, certtool, or viewing certificate stores on common Linux distributions).
- When listing troubleshooting steps, present both Windows and Linux methods side-by-side, or in parallel sections, to ensure parity.
- Reference cross-platform tools (such as Azure CLI) before or alongside platform-specific tools like PowerShell.
- Add screenshots or terminal outputs from Linux environments where Windows screenshots are provided.
- Explicitly mention that all steps can be performed on both Windows and Linux, and clarify any platform-specific differences.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell in the 'Next steps' section for creating an autoscaling, zone redundant application gateway. There are no examples or links for equivalent Linux-friendly tools such as Azure CLI, nor are Linux-specific patterns or commands mentioned. This prioritizes Windows tooling and may hinder Linux users from finding relevant guidance.
Recommendations
- Add equivalent Azure CLI instructions and tutorials for creating autoscaling, zone redundant application gateways.
- Reference both PowerShell and CLI options in 'Next steps', ensuring parity for Linux and macOS users.
- Where examples are given, provide both PowerShell and CLI syntax side-by-side.
- Explicitly mention cross-platform support and link to documentation for Linux/macOS environments.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing a PowerShell example before the Azure CLI example, and by omitting any Linux-specific commands or troubleshooting tools. The use of PowerShell as a primary example and lack of explicit mention of Linux shell usage or Linux troubleshooting approaches suggests a preference for Windows environments.
Recommendations
- Provide Bash or Linux shell examples alongside PowerShell, especially for Azure CLI usage.
- Explicitly mention that Azure CLI commands work cross-platform and show usage in a Linux terminal.
- Include troubleshooting steps or tool recommendations relevant to Linux environments (e.g., curl, openssl for certificate checks).
- Balance the order of examples so that Windows and Linux approaches are presented equally, or clarify platform applicability.
- Add notes or links for Linux administrators on how to perform backend health checks and certificate troubleshooting using native Linux tools.
Application Gateway
Externally managed scheduled autoscaling for Application Gateway v2
...ation-gateway-externally-managed-scheduled-autoscaling.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively provides PowerShell examples and instructions for implementing scheduled autoscaling with Azure Automation, without mentioning or demonstrating Linux-friendly alternatives such as Azure CLI, Bash, or Python runbooks. The use of PowerShell and references to 'runbooks' implicitly favor Windows environments and tooling, potentially making it less accessible for Linux users or those preferring cross-platform solutions.
Recommendations
- Add equivalent examples using Azure CLI and/or Bash scripts for runbooks to demonstrate Linux compatibility.
- Explicitly mention that Azure Automation supports Python and Bash runbooks, and provide sample code for those.
- Reorder or supplement instructions to present both Windows/PowerShell and Linux/Azure CLI approaches side by side.
- Clarify that PowerShell is not required and that cross-platform alternatives are available for all steps.
- Include troubleshooting and alerting links relevant to Linux-based runbooks, not just PowerShell.
Application Gateway
Common key vault errors in Application Gateway
...gateway/application-gateway-key-vault-common-errors.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for certificate management and update operations, with no equivalent examples for Azure CLI or Bash. Troubleshooting steps and UI navigation are described primarily in terms of the Azure Portal, which is platform-agnostic but often used on Windows. There is no mention of Linux-specific tools, nor are Linux/Bash/CLI examples provided alongside PowerShell commands.
Recommendations
- Add Azure CLI (az) command examples for all certificate management and troubleshooting steps, especially where PowerShell is currently used.
- Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and provide Bash/CLI equivalents.
- Where UI navigation is described, clarify that the Azure Portal is accessible from any OS and avoid implying a Windows-only workflow.
- Include links to cross-platform documentation and note any differences in command syntax or tool availability between Windows and Linux.
Application Gateway
Health monitoring overview for Azure Application Gateway
...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 bias toward Windows and PowerShell by exclusively providing PowerShell cmdlet examples (e.g., New-AzApplicationGatewayProbeHealthResponseMatch) and referencing Azure PowerShell as the primary automation/configuration tool. There are no CLI (az), Bash, or Linux-native examples or instructions. The 'devx-track-azurepowershell' custom metadata and the 'Next steps' section also prioritize PowerShell over cross-platform alternatives, reinforcing a Windows-centric approach.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell cmdlets, especially for probe configuration and matching criteria.
- Include Bash script snippets or Linux shell commands where appropriate to demonstrate cross-platform usage.
- Mention cross-platform tools (Azure CLI, REST API, Terraform) alongside PowerShell in all instructional sections and 'Next steps'.
- Adjust metadata and page structure to highlight platform neutrality (e.g., 'devx-track-azurecli' or both).
- Ensure that all configuration steps and automation patterns are shown for both Windows and Linux environments.
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 providing only PowerShell examples for enabling diagnostic logging, referencing Windows-centric tools (Excel, Power BI, Visual Studio, C#), and omitting equivalent Linux/CLI/Bash instructions. Windows tools and patterns are mentioned exclusively or before any cross-platform alternatives, and there are no examples using Azure CLI, Bash, or Linux-native workflows for log management.
Recommendations
- Add equivalent Azure CLI and Bash examples for enabling diagnostic logging, alongside PowerShell.
- Include instructions for viewing and analyzing logs using Linux-native tools (e.g., jq, awk, grep) and open-source visualization platforms (e.g., Grafana).
- Reference cross-platform editors and tools (e.g., VS Code, LibreOffice Calc) in addition to Windows-specific ones like Excel and Visual Studio.
- Ensure that examples and tool recommendations are presented in a platform-neutral order or grouped by OS, rather than Windows-first.
- Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and provide links to relevant cross-platform documentation.
Application Gateway
Use with Internal Load Balancer - Azure Application Gateway
...les/application-gateway/application-gateway-ilb-arm.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively uses Windows PowerShell (Az module) for all examples and instructions, with no mention of Azure CLI, Bash, or Linux-native tools. The setup and management steps are presented only with PowerShell cmdlets, and references to switching PowerShell modes and using Windows PowerShell are made before any alternative is discussed (none are provided). This creates a strong Windows-centric bias and excludes Linux/macOS users who may prefer or require cross-platform tools.
Recommendations
- Add equivalent Azure CLI (az) commands for each step, with Bash syntax examples.
- Include notes or sections for Linux/macOS users, clarifying how to perform the same operations from those platforms.
- Reference Azure Cloud Shell, which supports both PowerShell and Bash, as a cross-platform option.
- Avoid language such as 'switch PowerShell mode' or 'Using Windows PowerShell' unless alternatives are also presented.
- Ensure that links and references include documentation for both PowerShell and CLI approaches.
Application Gateway
TLS policy overview for Azure Application Gateway
...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 Windows bias primarily through its references to PowerShell for configuration and details retrieval, with no mention of Linux-specific tools or examples (such as Bash, Azure CLI on Linux, or OpenSSL). PowerShell is listed first and most prominently as the method for viewing cipher suite ordering and for configuring TLS policies, and the 'Next steps' section links only to a PowerShell-based configuration guide. There are no Linux, Bash, or cross-platform CLI examples provided, nor is there mention of how to perform these tasks on Linux systems.
Recommendations
- Add Azure CLI examples for configuring and viewing TLS policies, ensuring they work on both Windows and Linux.
- Provide Bash script examples for Linux users where applicable.
- Include references and links to Linux-friendly tools (e.g., OpenSSL, curl) for testing TLS connections and cipher suites.
- Ensure that documentation for configuration and management tasks is platform-neutral, or explicitly provides both Windows (PowerShell) and Linux (CLI/Bash) instructions.
- Update 'Next steps' to include links to cross-platform guides, not just PowerShell.
Application Gateway
Certificates required to allow backend servers
...ion-gateway/certificates-for-backend-authentication.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exclusively provides certificate export instructions using Windows Certificate Manager and PowerShell, with screenshots and step-by-step guidance tailored to Windows users. There are no examples or guidance for performing equivalent operations on Linux or macOS, nor are cross-platform tools (such as OpenSSL) mentioned. The 'Next steps' section also references PowerShell specifically for further configuration.
Recommendations
- Add equivalent certificate export instructions for Linux and macOS using OpenSSL or other native tools.
- Provide command-line examples for exporting certificates in Base-64 encoded X.509 (.CER) format using OpenSSL.
- Include screenshots or terminal output for Linux/macOS workflows.
- Mention cross-platform tools and clarify that the process is not limited to Windows.
- Update 'Next steps' to reference both PowerShell and CLI/Bash alternatives for configuring Application Gateway.
Application Gateway
WebSocket support in Azure Application Gateway
...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 Windows bias primarily by referencing Azure PowerShell and linking to a 'quick-create-powershell.md' page as the next step, without mentioning or providing equivalent Linux or cross-platform CLI examples. There is no mention of Azure CLI, Bash, or Linux-specific tooling, nor are there examples or guidance for users on non-Windows platforms. The configuration snippets are generic ARM template JSON, which is platform-neutral, but the operational guidance and next steps are Windows-centric.
Recommendations
- Include Azure CLI (az) examples alongside or before PowerShell examples for creating and configuring Application Gateway listeners and backend pools.
- Update the 'Next steps' section to reference both PowerShell and Azure CLI quick-create guides, or provide a unified guide with both sets of instructions.
- Explicitly mention that configuration can be performed on Linux, macOS, or Windows, and provide links to cross-platform tooling.
- Add Bash or shell script examples where appropriate, especially for backend server configuration or health probe testing.
- Ensure parity in documentation by reviewing all operational instructions for platform neutrality and including Linux/macOS alternatives wherever Windows/PowerShell is referenced.
Application Gateway
Azure Application Gateway infrastructure configuration
...es/application-gateway/configuration-infrastructure.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily through its use of Azure PowerShell cmdlets for operational examples (such as restarting the Application Gateway), without providing equivalent Azure CLI or Linux shell commands. References to tooling and operational steps are Windows-centric, and there are no explicit Linux or cross-platform examples or instructions. This may disadvantage users who prefer or require Linux-based workflows.
Recommendations
- Provide Azure CLI examples alongside PowerShell commands for all operational tasks, especially for actions like restarting the Application Gateway.
- Explicitly mention that both PowerShell and Azure CLI are supported, and link to cross-platform installation guides for Azure CLI.
- Where possible, include bash/Linux shell command snippets for common tasks, or clarify that instructions apply equally to Linux and macOS environments.
- Review all sections for implicit assumptions of Windows environments and add clarifications or alternatives for Linux users.
- Add a note or section on cross-platform management, highlighting parity between Windows and Linux tooling for Azure operations.
Application Gateway
Configure an internal load balancer (ILB) endpoint
...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 page demonstrates a Windows bias by exclusively using Windows Server as the VM image in examples, providing only PowerShell-based instructions for backend setup (IIS installation), and omitting Linux-based alternatives or CLI examples. Windows tools and patterns (IIS, PowerShell) are mentioned and used without reference to Linux equivalents, and Windows is presented as the default/only option for backend servers.
Recommendations
- Include Linux-based examples, such as using Ubuntu or CentOS as VM images.
- Provide instructions for installing a web server (e.g., Apache or Nginx) on Linux VMs using Bash/Azure CLI.
- Offer both PowerShell and Bash/Azure CLI commands for VM extension configuration.
- Present Windows and Linux options side-by-side or in parallel sections to ensure parity.
- Explicitly mention that backend pools can use Linux VMs and provide guidance for their setup.
Application Gateway
Create Azure Application Gateway custom error pages
...blob/main/articles/application-gateway/custom-error.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively provides Azure PowerShell examples for configuring custom error pages in Application Gateway, with no mention of Azure CLI, Bash, or Linux-native tooling. The configuration section is labeled 'Azure PowerShell configuration' and links only to PowerShell cmdlet references. There are no Linux or cross-platform command-line instructions, and PowerShell is presented as the sole automation method, which may disadvantage users on Linux or macOS platforms.
Recommendations
- Add equivalent Azure CLI examples for all configuration steps, demonstrating how to set custom error pages using az network application-gateway commands.
- Include Bash script snippets for Linux users, showing how to automate configuration via Azure CLI.
- Explicitly mention that both PowerShell and CLI can be used, and provide links to CLI documentation.
- Ensure screenshots and UI instructions do not assume a Windows environment.
- Review references and links to ensure parity between PowerShell and CLI documentation.
Application Gateway
Tutorial: Create and configure an application gateway to host multiple web sites using the Azure portal
...es/application-gateway/create-multiple-sites-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits a clear Windows bias. Virtual machine creation is demonstrated exclusively with Windows Server, and all backend configuration and testing instructions (IIS installation, hosts file editing, DNS commands) use Windows-specific tools and paths. PowerShell is the only scripting environment referenced for VM extension management. There are no Linux VM examples, nor are Linux equivalents (such as Apache/Nginx setup, /etc/hosts editing, or Bash commands) provided or mentioned.
Recommendations
- Provide parallel instructions for creating Linux VMs (e.g., Ubuntu), including steps for installing a web server such as Apache or Nginx.
- Include Linux-specific commands for editing /etc/hosts and managing DNS cache (e.g., 'sudo nano /etc/hosts', 'sudo systemd-resolve --flush-caches').
- Offer Bash/Azure CLI examples alongside PowerShell for VM extension management and other automation tasks.
- Clarify that Application Gateway supports both Windows and Linux backends, and show how to configure each.
- Add screenshots or code snippets demonstrating Linux workflows where appropriate.
Application Gateway
Tutorial: Create an application gateway with URL path-based routing rules using Azure portal
...rticles/application-gateway/create-url-route-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. It exclusively uses Windows Server virtual machines as backend examples, provides only PowerShell commands for configuration (specifically for installing IIS), and focuses on IIS (a Windows web server) for testing. There are no Linux VM creation steps, no Linux web server installation instructions (e.g., Apache or Nginx), and no Bash or Azure CLI examples for Linux users. Windows tools and patterns are mentioned first and exclusively throughout the tutorial.
Recommendations
- Add parallel instructions for creating Linux virtual machines (e.g., Ubuntu) as backend servers.
- Include steps to install a Linux web server (such as Apache or Nginx) on the Linux VMs, with corresponding commands.
- Provide Azure CLI or Bash examples for installing web servers and configuring VM extensions on Linux.
- Mention Linux as a supported backend OS in the prerequisites and throughout the tutorial.
- Show screenshots and test results for both Windows (IIS) and Linux (Apache/Nginx) backend pools.
- Ensure that references to tools and commands are platform-neutral or presented in both Windows and Linux variants.