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 126-150 of 981 flagged pages
Application Gateway
Tutorial: Protect your application gateway with Azure DDoS Network Protection
...n-gateway/tutorial-protect-application-gateway-ddos.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a clear Windows bias by exclusively using Windows Server virtual machines as backend targets and providing only PowerShell-based instructions for installing IIS. There are no examples or instructions for deploying Linux VMs, installing a web server on Linux, or using Bash/CLI commands. Windows tools and patterns (IIS, PowerShell) are mentioned exclusively and before any Linux equivalents, which are entirely absent.
Recommendations
- Include parallel instructions for deploying Linux-based backend VMs (e.g., Ubuntu or CentOS) alongside Windows examples.
- Provide steps to install a web server (such as Apache or Nginx) on Linux VMs using Bash or Azure CLI commands.
- Offer both PowerShell and Bash/CLI command examples for resource configuration and extension installation.
- Explicitly state that Application Gateway supports both Windows and Linux backend servers, and link to relevant documentation for Linux setup.
- Balance screenshots and walkthroughs to show both Windows and Linux scenarios where appropriate.
Create Pull Request
Application Gateway
Generate self-signed certificate with a custom root CA
...ticles/application-gateway/self-signed-certificates.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates mild Windows bias. Windows and Windows tools (IIS, PowerShell) are mentioned before or more prominently than Linux equivalents. The Azure PowerShell example is provided, but no Azure CLI or ARM template example is shown. IIS instructions are given before Apache/NGINX, and Windows file paths are used in PowerShell sample code. There is no explicit Linux-focused section for uploading certificates to Application Gateway, nor are Linux-specific automation examples provided.
Recommendations
- Add Azure CLI and/or ARM template examples for uploading certificates to Application Gateway, alongside the PowerShell sample.
- Provide Linux-specific instructions or examples for certificate upload and management, including file paths and shell commands.
- Alternate the order of IIS and Apache/NGINX sections, or group them together to avoid implicit prioritization.
- Include screenshots or instructions for Linux certificate stores (e.g., update-ca-certificates on Ubuntu) when adding the root certificate.
- Use neutral file paths in code samples (e.g., /home/user/contoso.cer) or provide both Windows and Linux paths.
- Explicitly mention cross-platform compatibility in each step, especially for certificate handling and web server configuration.
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 (e.g., New-SelfSignedCertificate, Export-PfxCertificate), with no mention of Linux equivalents or cross-platform alternatives. The prerequisites and instructions assume a Windows environment and do not provide Bash/CLI or Linux-native workflows. There is no parity for Linux users, and Windows tools are presented exclusively and first.
Recommendations
- Provide equivalent Azure CLI (az) examples alongside PowerShell for each step, as Azure CLI is cross-platform.
- Include instructions for creating self-signed certificates on Linux/macOS (e.g., using OpenSSL) and exporting to PFX format.
- Add notes or sections for running tutorials on Linux/macOS, including installation and usage of Azure CLI.
- Avoid assuming a Windows environment for file paths (e.g., use generic or platform-agnostic paths).
- Mention cross-platform alternatives in prerequisites, such as Azure CLI and Bash.
- Ensure that all code samples and instructions are available for both Windows and Linux users, ideally side-by-side.
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 Tools
Windows First
Summary
The documentation page demonstrates Windows bias by exclusively referencing Azure PowerShell in the 'Next steps' section for creating an autoscaling, zone redundant application gateway. No Linux/CLI examples or references are provided, and PowerShell is mentioned as the primary tool for deployment tasks, which may disadvantage Linux users or those preferring cross-platform tools.
Recommendations
- Include Azure CLI examples and links alongside PowerShell instructions for deployment and configuration tasks.
- Explicitly mention cross-platform tools and provide parity in walkthroughs for both Windows and Linux environments.
- Add guidance or tutorials for Linux users, such as using Bash scripts or Azure CLI on Linux/macOS.
- Review all referenced tutorials and ensure that Linux-compatible instructions are available and easily discoverable.
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 is heavily biased towards Windows and PowerShell usage. All examples and instructions use Azure PowerShell cmdlets, with no mention of Azure CLI, Bash, or Linux-native tooling. The prerequisite steps and links reference Windows PowerShell and do not provide Linux alternatives. There are no Bash or Azure CLI examples, and the workflow assumes a Windows-centric environment.
Recommendations
- Add equivalent Azure CLI (az) examples for each PowerShell command, suitable for Bash and cross-platform usage.
- Include a 'Choose your environment' section at the top, guiding users to select instructions for PowerShell (Windows) or Azure CLI (Linux/macOS/Windows).
- Reference installation instructions for Azure CLI alongside PowerShell, with links for Linux/macOS users.
- Ensure terminology and links do not assume Windows as the default platform (e.g., avoid 'Using Windows PowerShell with Resource Manager' as the only option).
- Provide notes or callouts for platform-specific differences, if any, in resource creation and management.
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 exhibits Windows bias primarily by referencing Azure PowerShell for operational tasks (such as restarting the Application Gateway) without providing equivalent Azure CLI or Linux shell examples. The only explicit tooling mentioned for management is PowerShell, and no Linux-specific or cross-platform command-line instructions are given. This can disadvantage users who work primarily on Linux or macOS systems, or who prefer Azure CLI over PowerShell.
Recommendations
- Include Azure CLI examples alongside PowerShell instructions for all operational tasks, such as restarting the Application Gateway.
- When referencing commands or scripts, provide both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) equivalents.
- Explicitly mention that all management operations can be performed via Azure CLI, and link to relevant CLI documentation.
- Review all procedural sections to ensure parity between Windows and Linux tooling, avoiding implicit prioritization of Windows tools.
- Add notes or tips for cross-platform usage, clarifying that Azure CLI is available on all major operating systems.
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 backend VM OS, providing only PowerShell-based instructions for IIS installation, and omitting Linux alternatives (such as Ubuntu, Apache, and Bash/Azure CLI examples). Windows tools and patterns are mentioned first and exclusively, with no parity for Linux users.
Recommendations
- Include Linux-based backend VM examples (e.g., Ubuntu with Apache or Nginx) alongside Windows Server.
- Provide Azure CLI and Bash instructions for backend setup and IIS/Apache installation, not just PowerShell.
- Show how to install a web server on Linux VMs (e.g., using apt-get for Apache/Nginx) in addition to Windows IIS.
- Mention Linux images as options when creating virtual machines.
- Ensure screenshots and code snippets reflect both Windows and Linux scenarios.
- Add notes or sections for Linux users to clarify differences in setup and management.
Application Gateway
What is Application Gateway for Containers?
...rticles/application-gateway/for-containers/overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the 'Deployment strategies' section, where Azure portal, CLI, PowerShell, and Terraform are listed as deployment tools, with PowerShell (a Windows-centric tool) mentioned explicitly and before any Linux-native alternatives. There are no Linux-specific examples or references to Bash, shell scripts, or Linux tooling. The documentation does not provide parity in examples or instructions for Linux users, nor does it clarify cross-platform compatibility for the listed tools.
Recommendations
- Explicitly mention Bash, shell scripts, or Linux CLI usage alongside PowerShell when listing deployment tools.
- Provide example commands for both PowerShell and Bash/Azure CLI to demonstrate cross-platform deployment.
- Clarify that Azure CLI and Terraform are cross-platform and provide links or instructions for Linux installation and usage.
- Avoid listing PowerShell before Linux-native tools, or present them together to avoid perceived prioritization.
- Add a section or note on platform compatibility for all deployment tools, ensuring Linux users are equally supported.
Application Gateway
Troubleshoot session affinity issues
...oubleshoot-application-gateway-session-affinity-issues.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. PowerShell is the only CLI example provided for checking settings, and Fiddler (a Windows-only tool) is exclusively used for web debugging. Installation instructions reference Windows-specific actions (e.g., 'Run as administrator'), and there are no Linux or cross-platform alternatives or examples given for these troubleshooting steps.
Recommendations
- Provide equivalent Azure CLI or Bash examples for checking Application Gateway settings, alongside or before PowerShell commands.
- Mention and demonstrate cross-platform web debugging tools such as Wireshark, mitmproxy, or curl for capturing and analyzing HTTP/HTTPS traffic.
- Include installation and usage instructions for these tools on Linux and macOS, not just Windows.
- Avoid Windows-specific terminology (e.g., 'Run as administrator') unless also providing Linux/macOS equivalents (e.g., 'sudo').
- Ensure screenshots and walkthroughs include examples from non-Windows environments where possible.
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 (e.g., Remove-AzResourceGroup) for resource cleanup and referencing IIS (a Windows web server) for validation. There are no Linux-specific examples, such as using Azure CLI for cleanup or deploying Linux-based web servers (e.g., Apache or Nginx) for testing. The page does mention Azure CLI as an alternative in the introduction, but does not provide CLI commands or Linux-centric validation steps.
Recommendations
- Provide equivalent Azure CLI commands for resource cleanup (e.g., az group delete) alongside PowerShell examples.
- Include examples of deploying and validating with Linux-based web servers (such as Apache or Nginx) in the backend pool.
- Offer browser-based or cross-platform validation steps that do not assume IIS is present.
- Ensure that both Windows and Linux patterns/tools are presented in parallel throughout the documentation.
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 exhibits a Windows bias through frequent use of PowerShell commands and Windows-specific troubleshooting steps, such as referencing certlm.msc, netstat via Windows command prompt, and Test-NetConnection. Windows tools and patterns are often mentioned before or instead of Linux equivalents, and Linux-specific examples are sparse or missing in many sections. While some Linux commands (like OpenSSL) are mentioned, they are less detailed and less frequent than their Windows counterparts.
Recommendations
- Provide equivalent Linux CLI commands (e.g., curl, netcat, ss, openssl) alongside PowerShell examples for network and certificate troubleshooting.
- Include Linux-specific instructions for viewing and exporting certificates (e.g., using openssl, certtool, or GUI tools like GNOME Certificates).
- Balance examples by alternating or combining Windows and Linux approaches, especially in sections where only Windows tools are referenced.
- Add troubleshooting steps using Bash and Linux utilities for checking backend server status, network connectivity, and firewall rules.
- Explicitly mention that all steps can be performed on both Windows and Linux, and provide parity in detail and guidance for both platforms.
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
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation exclusively provides PowerShell examples for implementing scheduled autoscaling with Azure Automation, without mentioning or providing equivalent Bash, Azure CLI, or Python runbook examples. PowerShell is primarily associated with Windows environments, and its exclusive use suggests a bias toward Windows users. There is no discussion of how to perform these tasks using Linux-native tools or scripting languages, nor any guidance for users who may prefer or require non-Windows automation approaches.
Recommendations
- Add equivalent examples using Azure CLI and Bash scripts for runbooks, which are commonly used in Linux environments.
- Include Python runbook examples, as Python is supported in Azure Automation and widely used across platforms.
- Explicitly mention that Azure Automation supports multiple runbook types (PowerShell, Python, Graphical, etc.) and provide links or references to documentation for each.
- Present examples for both Windows and Linux users side-by-side, or clarify cross-platform compatibility in the overview.
- Avoid assuming PowerShell as the default or only automation language; introduce alternatives early in the documentation.
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 exhibits a Windows bias by providing only PowerShell examples for certificate management and update operations, with no equivalent Azure CLI or bash examples for Linux/macOS users. Troubleshooting steps and instructions consistently reference the Azure portal and PowerShell, which are more commonly used on Windows. There is no mention of Linux-specific tools, nor are Linux/CLI examples presented alongside or before Windows-centric instructions.
Recommendations
- Add Azure CLI (az) examples for all certificate management and troubleshooting steps, especially where PowerShell is currently used.
- Include bash script snippets for common operations to assist Linux/macOS users.
- Explicitly mention cross-platform options (e.g., Azure CLI, REST API) in troubleshooting steps and resolutions.
- Ensure that instructions for using the Azure portal clarify that it is web-based and accessible from all platforms.
- Where PowerShell is referenced, provide equivalent CLI commands side-by-side, or link to CLI documentation.
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. The workflow for enabling logging is described first using PowerShell, with no mention of Azure CLI, Bash, or Linux-native tools. Recommendations for log analysis and conversion also focus on Windows tools, with no parity for Linux or open-source alternatives.
Recommendations
- Add 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, sed, csvkit).
- Reference open-source or cross-platform log conversion tools, not just Visual Studio/C#.
- Mention data visualization options available on Linux (e.g., Grafana, LibreOffice Calc) in addition to Excel and Power BI.
- Ensure that examples and tool recommendations are presented in a platform-neutral order, or provide both Windows and Linux alternatives side by side.
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 First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell examples for configuring custom health probe match criteria, referencing Windows-centric tools and cmdlets (e.g., New-AzApplicationGatewayProbeHealthResponseMatch), and omitting equivalent examples for Linux users (such as Azure CLI or ARM template snippets). Additionally, the 'Next steps' section lists PowerShell before the Azure portal, reinforcing a Windows-first approach. There are no references to Linux-native tools or cross-platform scripting options.
Recommendations
- Add Azure CLI examples for all PowerShell cmdlet usages, especially for configuring custom health probe match criteria.
- Include ARM template or Bicep configuration snippets to provide platform-agnostic options.
- Present cross-platform examples (Azure CLI, REST API) before or alongside PowerShell examples to avoid Windows-first ordering.
- Explicitly mention that all configuration steps can be performed on Linux, macOS, and Windows, and provide links to platform-specific guides where relevant.
Application Gateway
Private Application Gateway deployment
...tion-gateway/application-gateway-private-deployment.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting Azure PowerShell instructions before Azure CLI, using PowerShell-specific cmdlets and outputs, and omitting explicit Linux shell examples (e.g., Bash). The CLI examples are present, but there are no Bash-specific instructions or screenshots, and the PowerShell outputs are shown even in the CLI section. There is no mention of Linux-specific tools, patterns, or troubleshooting steps, and the workflow assumes familiarity with Windows-centric tooling.
Recommendations
- Add explicit Bash shell examples for Azure CLI commands, including sample outputs as seen in Linux terminals.
- Ensure CLI instructions and outputs are distinct from PowerShell, avoiding reuse of PowerShell output formatting in CLI sections.
- Include screenshots or walkthroughs of Azure CLI usage in Linux environments, not just the Azure portal.
- Mention Linux-native automation tools (e.g., shell scripts, Ansible) where appropriate alongside PowerShell and ARM templates.
- Clarify that Azure CLI is cross-platform and provide parity in troubleshooting and validation steps for both Windows and Linux users.
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 by referencing PowerShell and Windows-centric tools as primary mechanisms for viewing or configuring TLS policies. There is no mention of Linux-specific tools or command-line examples (such as Bash, OpenSSL, or Linux CLI usage), and PowerShell is listed before CLI and REST API in several places. The 'Next steps' section links only to a PowerShell-based configuration guide, omitting Linux or cross-platform alternatives.
Recommendations
- Provide Linux/Bash-based examples for configuring TLS policies, such as using Azure CLI on Linux or REST API calls from Bash.
- Reference cross-platform tools (e.g., Azure CLI) before or alongside PowerShell, ensuring parity in instructions.
- Include links to documentation pages for configuring TLS policies using Azure CLI on Linux and REST API, not just PowerShell.
- Explicitly mention that Azure CLI is available on Linux, macOS, and Windows, and provide sample commands for each.
- Avoid listing PowerShell before CLI/REST API unless contextually justified; strive for neutral ordering.
- Add troubleshooting or verification steps using Linux-native tools (e.g., OpenSSL) to check TLS policy application.
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 for troubleshooting steps, referencing Windows-centric tools (such as IIS), and omitting equivalent Azure CLI, Bash, or Linux-based commands. There are no Linux-specific troubleshooting instructions or examples, and Windows tools/patterns are mentioned before any cross-platform alternatives.
Recommendations
- Add Azure CLI and Bash examples alongside PowerShell for all command-line instructions.
- Include troubleshooting steps and examples relevant to Linux-based backend servers (e.g., Apache, Nginx), not just IIS.
- Reference cross-platform tools and commands (e.g., curl, netcat, dig) for network and DNS validation.
- Ensure that documentation sections do not assume Windows as the default platform; mention Linux and Windows equivalently.
- Provide links to Linux-specific documentation where appropriate.
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 demonstrates Windows bias by referencing Azure PowerShell and linking to a PowerShell-based quickstart as the next step, without mentioning or providing equivalent Linux/CLI examples. The only tooling mentioned for creating listeners is Azure PowerShell, and there is no reference to Azure CLI, ARM templates, or Linux-native workflows. No Linux-specific examples or guidance are provided.
Recommendations
- Include Azure CLI examples alongside PowerShell for configuration steps.
- Reference ARM template deployment and portal workflows equally, not just PowerShell.
- Update the 'Next steps' section to link to both PowerShell and Azure CLI quickstart guides.
- Explicitly mention that all steps can be performed on Linux, macOS, and Windows, and provide cross-platform command examples.
- Add notes or examples for Linux administrators, such as using Bash or shell scripts to interact with Azure resources.
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 step-by-step screenshots and references to Windows-specific tools and UI. There are no examples or guidance for performing equivalent tasks on Linux or macOS, nor are cross-platform CLI tools (such as OpenSSL) mentioned. The documentation assumes a Windows environment throughout.
Recommendations
- Add equivalent instructions for exporting certificates using OpenSSL on Linux and macOS, including CLI commands and example outputs.
- Include screenshots or terminal output for Linux-based workflows where appropriate.
- Mention cross-platform tools (e.g., OpenSSL, certtool) alongside Windows Certificate Manager, and clarify that the process can be performed on any OS.
- Provide parity in guidance order: present Windows and Linux/macOS options side-by-side or in parallel sections.
- Update 'Next steps' to reference cross-platform configuration guides, not only PowerShell.
Application Gateway
Manage traffic to App Service
...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 exclusively provides automation and CLI examples using Azure PowerShell, which is primarily a Windows-centric tool. There are no examples using Azure CLI (cross-platform), Bash, or Linux-native scripting. All command-line instructions assume PowerShell usage, and references to certificate creation link to PowerShell-based instructions. This creates a bias towards Windows users and leaves out Linux/macOS users who may prefer or require Bash/Azure CLI. The absence of Linux-oriented or cross-platform examples makes the documentation less accessible for non-Windows environments.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell scripts, using Bash syntax where appropriate.
- Include notes or tabs indicating which commands are cross-platform and which are Windows-specific.
- Reference certificate creation and management using OpenSSL or Azure CLI, not just PowerShell.
- Explicitly mention Linux/macOS compatibility and provide troubleshooting or setup notes for those platforms.
- Ensure parity in step-by-step instructions for both Azure portal, PowerShell, and Azure CLI/Bash workflows.
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 demonstrates a strong Windows bias. It exclusively uses Windows Server as the backend VM OS, provides only PowerShell commands for IIS installation, and references Windows-specific tools and file paths (e.g., editing the hosts file at c:\Windows\System32\drivers\etc and using ipconfig commands). There are no examples or instructions for Linux VMs, Linux web servers, or equivalent Linux commands and file locations.
Recommendations
- Include parallel instructions for deploying Linux-based backend VMs (e.g., Ubuntu, CentOS) and installing a web server such as Apache or Nginx.
- Provide Linux shell commands (e.g., Bash) for installing web servers and editing the hosts file (typically /etc/hosts).
- Mention Linux equivalents for DNS cache management (e.g., systemd-resolve --flush-caches or sudo service network-manager restart).
- Clarify that Application Gateway supports both Windows and Linux backend servers, and provide guidance for both platforms.
- Where PowerShell is used, offer Bash/Azure CLI alternatives for Linux users.
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 for backend examples, provides only PowerShell commands for IIS installation, and references Windows-specific tooling (IIS) without mentioning Linux alternatives. There are no instructions or examples for deploying Linux VMs, installing web servers like Apache or Nginx, or using Bash/CLI commands. Windows patterns and tools are presented first and exclusively.
Recommendations
- Add parallel instructions for creating Linux virtual machines (e.g., Ubuntu) as backend servers.
- Include examples for installing a web server on Linux VMs (such as Apache or Nginx) using Bash or Azure CLI commands.
- Provide both PowerShell and Bash/CLI scripts for configuration steps.
- Mention Linux as a supported backend OS and clarify that the Application Gateway works with both Windows and Linux servers.
- Show screenshots or outputs from Linux-based backend servers to demonstrate parity.
- Consider a section comparing Windows and Linux backend setup, highlighting differences and similarities.
Application Gateway
Tutorial: Configure an Application Gateway with TLS termination using the Azure portal
...main/articles/application-gateway/create-ssl-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates significant Windows bias. All examples for certificate creation, exporting, and VM setup use Windows PowerShell commands and Windows-specific tools (New-SelfSignedCertificate, Export-PfxCertificate, Set-AzVMExtension with Windows features). The tutorial exclusively creates Windows Server VMs for backend servers and installs IIS using PowerShell, with no mention of Linux alternatives or cross-platform instructions. There are no Linux shell or OpenSSL examples, nor guidance for deploying Linux VMs or web servers.
Recommendations
- Provide Linux equivalents for certificate creation and export, such as using OpenSSL commands.
- Include instructions for creating Linux VMs (e.g., Ubuntu) as backend servers.
- Demonstrate how to install a web server (e.g., Apache or Nginx) on Linux VMs for testing.
- Show how to upload certificates generated on Linux to the Azure portal.
- Ensure examples and screenshots cover both Windows and Linux scenarios, or clarify platform-specific steps.
- Add notes or links to cross-platform documentation where relevant.
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 provides configuration instructions for Azure Application Gateway custom error pages with a strong emphasis on Azure PowerShell, which is primarily a Windows-centric tool. No CLI (az), Bash, or Linux-native examples are provided, and the only automation/configuration examples use PowerShell cmdlets. There is no mention of Linux tools or workflows, nor are cross-platform alternatives presented. The PowerShell section appears before any mention of other automation methods, and the page metadata references 'devx-track-azurepowershell', further reinforcing the Windows bias.
Recommendations
- Add equivalent Azure CLI (az) examples for both global and listener-level custom error page configuration.
- Include Bash shell script snippets to demonstrate cross-platform automation.
- Explicitly mention that Azure CLI and REST API can be used from Linux, macOS, and Windows, and provide links to relevant documentation.
- Reorder sections so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell.
- Update metadata and guidance to clarify that PowerShell is not required and that Linux/macOS users have full parity via CLI and API.