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 451-475 of 981 flagged pages
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/high-traffic-support.md
...n/articles/application-gateway/high-traffic-support.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by referencing PowerShell and Windows-centric tooling for configuration tasks (e.g., configuring WAF custom rules, TLS policy), without providing equivalent CLI or Linux-native examples. There are no Linux shell (Bash/Azure CLI) commands or guidance, and PowerShell is mentioned as the method for advanced configuration. This may hinder Linux users or those preferring cross-platform tools.
Recommendations
- For every PowerShell-based configuration example or reference, provide an equivalent Azure CLI (az) example, which is cross-platform and works natively on Linux, macOS, and Windows.
- When referencing documentation for configuration (e.g., WAF custom rules, TLS policy), link to both PowerShell and Azure CLI guides, or provide a unified guide with both sets of instructions.
- Explicitly mention that all configuration steps can be performed using Azure CLI or ARM templates, and provide sample commands/scripts.
- Avoid implying PowerShell is the only or primary way to perform advanced configuration; instead, present PowerShell and Azure CLI as equal options.
- Add a section or callout for Linux/macOS users, highlighting cross-platform tools and any OS-specific considerations.
Create Pull Request
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/how-to-troubleshoot-application-gateway-session-affinity-issues.md
...oubleshoot-application-gateway-session-affinity-issues.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by providing PowerShell as the only CLI example for checking settings, exclusively recommending Fiddler (a Windows-centric tool) for network debugging, and referencing Windows-specific patterns such as 'Run as administrator'. There are no Linux or cross-platform alternatives offered for these tasks, and Windows tools are mentioned first and exclusively.
Recommendations
- Provide equivalent Azure CLI or Bash examples for checking Application Gateway settings, not just PowerShell.
- Mention and give examples using cross-platform or Linux-native network debugging tools such as tcpdump, Wireshark, or mitmproxy alongside Fiddler.
- Include instructions for Linux/macOS users, such as how to install and use these tools on their platforms.
- Avoid Windows-specific instructions like 'Right click the setup executable, and run as administrator' without offering Linux/macOS installation guidance.
- When referencing tools or commands, present cross-platform options first or in parallel, rather than defaulting to Windows.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/http-response-codes.md
...in/articles/application-gateway/http-response-codes.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias, particularly in the 504 Gateway time-out section, where IIS (a Windows web server) is mentioned first and in more detail than Nginx (a common Linux web server). The IIS section provides a direct link and specific configuration attribute, while the Nginx section is less detailed and lacks a direct link to official documentation. There are no PowerShell-specific examples, but Windows-centric tools and patterns are prioritized. No Linux command-line or troubleshooting examples are provided elsewhere.
Recommendations
- Present Nginx (Linux) and IIS (Windows) backend configuration guidance with equal detail, including direct links to official Nginx documentation (e.g., https://nginx.org/en/docs/) and explicit configuration examples.
- When mentioning backend server types, alternate the order (e.g., Nginx first in some cases) or mention both together to avoid implicit prioritization.
- Add troubleshooting examples or references for common Linux-based backend servers (such as Apache, Nginx, or Tomcat), not just IIS.
- Where possible, provide cross-platform command-line examples (e.g., curl, tcpdump, or Linux log file locations) alongside any Windows-specific guidance.
- Explicitly state that Application Gateway supports both Windows and Linux backend servers, and ensure parity in troubleshooting steps and documentation coverage.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ingress-controller-install-existing.md
...ication-gateway/ingress-controller-install-existing.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing several PowerShell-based command examples (marked as 'powershell-interactive'), using Windows-style variable assignment and scripting patterns, and referencing tools and workflows (such as Azure portal automation exports) that are more familiar to Windows users. Equivalent Linux/bash-native examples are missing or less prominent, and PowerShell is used even where bash would be more cross-platform appropriate. The documentation does not explicitly address Linux users or provide parity in scripting examples.
Recommendations
- For every PowerShell example, provide an equivalent bash shell example, especially for variable assignment and scripting blocks.
- When referencing automation exports from the Azure portal, clarify which scripts are bash and which are PowerShell, and ensure both are available and referenced equally.
- Avoid using PowerShell-specific syntax (e.g., $var=...) in generic command examples; prefer bash syntax or provide both.
- Explicitly state that all commands work in both Windows and Linux environments, or note any differences.
- Where possible, use Azure CLI commands in bash syntax as the primary example, as Azure CLI is cross-platform.
- Add a section or callouts for Linux/macOS users to clarify any differences in procedure or tooling.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ipv6-application-gateway-portal.md
...application-gateway/ipv6-application-gateway-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server as the backend VM example and providing only Azure PowerShell commands (with Windows-specific IIS installation) for backend setup and testing. There are no Linux-based backend examples, nor are there Bash/CLI or Linux-native instructions for deploying or testing the backend. This may hinder users who prefer or require Linux environments.
Recommendations
- Include parallel instructions for creating a Linux VM (e.g., Ubuntu) as a backend target, alongside the Windows Server example.
- Provide Azure CLI (Bash) commands for installing a simple web server (such as nginx or Apache) on a Linux VM for testing, in addition to the PowerShell/IIS example.
- Explicitly mention that both Windows and Linux VMs are supported as backend targets, and link to relevant documentation for both.
- Where scripting is required, offer both PowerShell and Bash/CLI examples, or reference cross-platform scripts.
- Ensure that screenshots and walkthroughs do not assume a Windows-only environment, and clarify any OS-specific steps.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/key-vault-certs.md
...b/main/articles/application-gateway/key-vault-certs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing only Azure PowerShell examples for command-line operations, referencing PowerShell steps before mentioning the Azure CLI, and omitting explicit Linux/bash examples. The 'Next steps' section also directs users to a PowerShell-specific guide, reinforcing the Windows-centric approach. While Azure CLI is mentioned as a supported method, no CLI or bash examples are provided, and the only detailed command-line walkthrough uses PowerShell.
Recommendations
- Add equivalent Azure CLI (az) command examples alongside PowerShell for all command-line instructions, especially in sections where PowerShell is currently the only example.
- When referencing command-line tools, mention Azure CLI and PowerShell together, or list Azure CLI first to balance platform representation.
- Include bash shell snippets for ARM template deployments and secret referencing, demonstrating cross-platform usage.
- In the 'Next steps' section, provide links to both PowerShell and Azure CLI/Linux guides for configuring TLS termination with Key Vault certificates.
- Explicitly state that all operations can be performed from Linux/macOS using Azure CLI, and provide relevant instructions or links.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/mutual-authentication-certificate-management.md
...ateway/mutual-authentication-certificate-management.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias. All certificate export steps are described using Windows GUI tools (Certificate Manager and Certificate Export Wizard), with screenshots and instructions specific to Windows. There are no equivalent instructions or screenshots for performing these tasks on Linux (e.g., using OpenSSL or command-line tools). The only Linux-specific content is a single 'cat' command for concatenating certificates, which is presented after the Windows 'type' command. The prerequisites, export, and certificate management sections omit Linux approaches entirely.
Recommendations
- Add parallel Linux instructions for exporting certificates, using OpenSSL or similar command-line tools, including example commands and expected outputs.
- Provide Linux-specific screenshots or terminal outputs where appropriate.
- Present Windows and Linux instructions side-by-side or clearly label them, rather than defaulting to Windows-first.
- Include a section or note on how to locate and manage certificates on Linux systems.
- Avoid referencing Windows-only tools (like Certificate Export Wizard) without Linux alternatives.
- Ensure parity in detail and clarity between Windows and Linux instructions throughout the documentation.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/migrate-v1-v2.md
...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 is heavily focused on PowerShell-based migration, with all instructions, code snippets, and tooling references centered around PowerShell and the PowerShell Gallery. There are no examples or guidance for Linux or cross-platform users (e.g., Bash, Azure CLI), and the use of Windows-centric tools and patterns (such as .ps1 scripts, PowerShell modules, and Windows file paths) is pervasive. This creates a significant Windows bias and may hinder users on Linux or macOS from following the migration process.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for all major steps, including authentication, resource discovery, and migration.
- Offer Bash shell script examples or instructions for Linux/macOS users, especially for certificate handling and script execution.
- Clearly state platform compatibility of the migration script and, if it is PowerShell Core compatible, provide explicit instructions for installing and running it on Linux/macOS.
- Include download and execution instructions for the migration script that do not assume Windows or PowerShell Gallery (e.g., using wget/curl and pwsh).
- Mention cross-platform Azure Cloud Shell as a primary option, and provide parity in examples for both PowerShell and Bash environments.
- Add a section or callouts for Linux/macOS users, highlighting any prerequisites, differences, or limitations.
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 Windows bias by providing detailed PowerShell examples and references before Azure CLI, omitting Linux-native command-line or OpenSSL examples for certificate handling, and directing users to a PowerShell-based configuration guide as the next step. There is no mention of Linux tools or workflows for extracting or managing certificates, and the CLI section is less detailed than the PowerShell section.
Recommendations
- Provide equal depth and detail for Azure CLI examples as for PowerShell, including multi-step workflows if needed.
- Include Linux-native commands (e.g., OpenSSL) for extracting and managing certificate chains, especially in sections discussing certificate preparation.
- When referencing further configuration guides, offer both PowerShell and CLI/Linux-based guides as next steps.
- Avoid positioning PowerShell or Windows tools as the default or primary method; present CLI and cross-platform approaches first or in parallel.
- Explicitly mention that all configuration steps can be performed on Linux/macOS using Azure CLI, and provide any necessary command-line differences or caveats.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/overview-v2.md
.../blob/main/articles/application-gateway/overview-v2.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell scripts and commands for migration and preview registration, with no explicit mention or examples of equivalent Bash or Linux shell commands. The 'Next steps' section also prioritizes PowerShell and does not provide Linux/CLI-focused tutorials. Azure CLI commands are shown, but the usage is wrapped in PowerShell cmdlets (e.g., Set-AzContext), which are not cross-platform, and there is no guidance for Linux users.
Recommendations
- Provide explicit Bash/Linux shell examples for all Azure CLI operations, avoiding reliance on PowerShell-specific cmdlets like Set-AzContext.
- When referencing scripts for migration or management, mention both PowerShell and Bash/CLI alternatives, or clarify if only PowerShell is supported.
- In 'Next steps' and tutorial links, include Linux/CLI-focused guides alongside or before PowerShell-based tutorials.
- Where Azure CLI is used, ensure the examples are platform-agnostic and do not assume a PowerShell environment.
- Add a section or note clarifying cross-platform support and linking to relevant Linux documentation.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/private-link-configure.md
...articles/application-gateway/private-link-configure.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed configuration steps for Azure Application Gateway Private Link using the Azure portal, Azure PowerShell, and Azure CLI. However, the PowerShell section is more extensive and appears before the CLI section, which may suggest a Windows-first approach. There are no explicit Linux/Bash-specific examples or references to Linux tools, and the CLI section, while present, lacks parity in depth and troubleshooting guidance compared to PowerShell. No Linux-specific considerations or screenshots are provided.
Recommendations
- Ensure that Azure CLI (cross-platform) examples are as detailed and comprehensive as the PowerShell examples, including troubleshooting tips and references.
- Consider placing Azure CLI instructions before or alongside PowerShell to avoid a Windows-first impression.
- Add explicit notes or examples for Linux/macOS users, such as shell syntax, environment setup, and common issues.
- Include screenshots or walkthroughs from a Linux environment where relevant.
- Reference cross-platform tools (e.g., Bash, Cloud Shell) and clarify that Azure CLI works natively on Linux/macOS/Windows.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/proxy-buffers.md
...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 detailed PowerShell examples for configuring request and response buffers, which are specific to Windows environments. While Azure CLI examples are included (which are cross-platform), the PowerShell section is more comprehensive, covering both creation and update scenarios. There are no explicit Linux shell (bash) or scripting examples, and the documentation references .NET SDK, which is more common in Windows-centric development. No Linux-specific tools or workflows are mentioned.
Recommendations
- Add bash (Linux shell) scripting examples for creating and updating Application Gateway buffer settings, similar to the PowerShell section.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide sample usage in a Linux terminal context.
- Include references to cross-platform SDKs (such as Python, Java, or Node.js) in addition to .NET, to ensure parity for non-Windows developers.
- Avoid presenting PowerShell as the only scripting option for automation; offer alternatives or note cross-platform options.
- Consider reordering examples to present Azure CLI (cross-platform) before PowerShell, or group them together to avoid a 'Windows-first' impression.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-portal.md
...in/articles/application-gateway/quick-create-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows Server virtual machines as backend examples, providing only PowerShell commands for configuration (specifically for installing IIS), and omitting any Linux-based VM or CLI/Bash examples. The installation and testing instructions are tailored to Windows (IIS, PowerShell), with no mention of Linux alternatives (such as NGINX/Apache or Bash scripting). This may hinder Linux users from following the quickstart without additional research.
Recommendations
- Include parallel instructions for creating and configuring Linux VMs (e.g., Ubuntu) as backend servers.
- Provide Linux-based examples for installing a web server (e.g., using Bash to install NGINX or Apache).
- Offer Azure CLI and/or Bash script equivalents for all PowerShell commands, especially for installing and configuring backend servers.
- When referencing VM images, mention both Windows and popular Linux distributions, and clarify that Application Gateway supports both.
- Ensure screenshots and walkthroughs are not exclusively tied to Windows workflows or tools.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-template.md
.../articles/application-gateway/quick-create-template.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 providing only a PowerShell example for resource cleanup, referencing IIS (a Windows web server) for validation, and omitting Linux/CLI alternatives for these steps. While the page mentions that the quickstart can be completed using the Azure portal, PowerShell, or CLI, the actual walkthrough and examples focus on Windows-centric tools and patterns, with no Linux or cross-platform command-line examples provided inline.
Recommendations
- Provide equivalent Azure CLI commands for resource cleanup (e.g., az group delete) alongside the PowerShell example.
- Include validation steps using a Linux-based web server (such as Apache or Nginx) in addition to IIS, or clarify how the template could be modified for a Linux VM.
- When referencing tools or commands, present cross-platform (CLI) options first or in parallel with Windows-specific (PowerShell) options.
- Add explicit Linux/CLI walkthroughs or links to them in the main flow, not just in the 'Next steps' section.
- Clarify in the prerequisites or template review that the example VMs are Windows-based, and provide guidance for users who prefer Linux.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/redirect-http-to-https-portal.md
...s/application-gateway/redirect-http-to-https-portal.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. All command-line examples use PowerShell, including certificate creation and IIS installation. The VM scale set is explicitly created with Windows Server 2016 Datacenter, and IIS (a Windows web server) is installed via PowerShell scripts. There are no Linux or cross-platform alternatives provided for certificate creation, backend server OS, or web server setup.
Recommendations
- Provide equivalent Linux examples for all command-line steps, such as using OpenSSL for certificate creation and Bash/Azure CLI for automation.
- Include instructions for deploying a Linux-based VM scale set (e.g., Ubuntu) and installing a Linux web server (e.g., Nginx or Apache) as the backend pool.
- Offer both PowerShell and Bash/Azure CLI scripts for all automation steps, and clarify which OS each applies to.
- Mention Linux tools and patterns alongside Windows ones, and avoid assuming Windows as the default environment.
- Add a section or callouts for cross-platform considerations, helping users choose the right instructions for their environment.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/renew-certificates.md
...ain/articles/application-gateway/renew-certificates.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides step-by-step instructions for renewing certificates on Azure Application Gateway, with detailed examples for Azure PowerShell and Azure CLI. However, the PowerShell example is presented before the Azure CLI example, and there is no explicit mention or example of Linux-native tools or workflows (such as Bash scripting or OpenSSL usage). The CLI example is generic but does not clarify Linux compatibility, and the PowerShell example is Windows-centric. There are no references to Linux file paths, shell environments, or common Linux certificate management patterns.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Linux-specific notes where relevant (e.g., file path formats, certificate file permissions).
- Include a Bash shell example for uploading or renewing certificates, especially for scenarios where scripting is involved.
- Reference common Linux tools (such as OpenSSL) for certificate preparation or validation.
- Add a section or note on how to perform these tasks from a Linux environment, including any prerequisites or differences.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/retirement-faq.md
...ob/main/articles/application-gateway/retirement-faq.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively references Azure PowerShell scripts for migration tasks, with no mention of Azure CLI, Bash, or Linux-native tooling. All migration automation examples and caveats are centered on PowerShell, which is traditionally associated with Windows environments. There are no examples or guidance for Linux users or those preferring cross-platform tools.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for migration tasks alongside PowerShell examples.
- Explicitly mention that migration can be performed from Linux/macOS using Azure CLI or PowerShell Core, and provide relevant instructions.
- Include Bash or shell script examples where automation is discussed, or clarify cross-platform compatibility of provided scripts.
- Add a section comparing PowerShell and CLI approaches, helping users choose the best tool for their environment.
- Ensure that all references to tooling (scripts, automation, troubleshooting) include both Windows and Linux-friendly options.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/self-signed-certificates.md
...ticles/application-gateway/self-signed-certificates.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While the main certificate generation workflow uses OpenSSL (cross-platform), Windows tools and patterns are frequently mentioned first or exclusively. The IIS section is more detailed than Linux alternatives, and the only automation example for uploading certificates to Application Gateway is in Azure PowerShell, with no Azure CLI (cross-platform) or ARM/Bicep alternatives. The hosts file editing link is Windows-specific, and some instructions assume a Windows file path structure.
Recommendations
- Provide Azure CLI examples alongside or before Azure PowerShell for certificate upload and configuration, as CLI is cross-platform.
- Include Linux/macOS-specific instructions for editing the hosts file (e.g., /etc/hosts), not just a Windows link.
- Balance the web server configuration sections: give equal detail for Apache and NGINX as for IIS, including links to official documentation for Linux.
- Use neutral file path examples (e.g., ~/Downloads/contoso.cer or /home/user/contoso.cer) instead of Windows paths (C:\Users\...).
- Mention that OpenSSL is available on macOS as well as Linux and Windows.
- If referencing GUI tools or wizards, ensure Linux alternatives are mentioned or clarify if they are Windows-only.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/tutorial-protect-application-gateway-ddos.md
...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 Windows bias by exclusively using Windows Server as the backend VM example, providing only PowerShell commands for configuration (specifically for installing IIS), and omitting any Linux-based examples or equivalent Bash/CLI instructions. The tutorial assumes the use of Windows tools and environments, with no mention of Linux alternatives or parity.
Recommendations
- Provide parallel instructions for deploying Linux-based backend VMs (e.g., Ubuntu) alongside the Windows Server example.
- Include Bash/Azure CLI commands for installing a web server (such as Apache or Nginx) on Linux VMs, in addition to the PowerShell/IIS example.
- Explicitly mention that Application Gateway supports both Windows and Linux backend servers, and offer guidance for both.
- When showing code or command-line examples, present both PowerShell (for Windows) and Bash/CLI (for Linux) versions.
- Balance the order of presentation so that Linux and Windows options are given equal prominence, or clarify that the steps are similar for both platforms.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ssl-overview.md
...blob/main/articles/application-gateway/ssl-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Windows-specific tools and APIs (such as the PFXImportCertStore function), providing configuration guidance and next steps only for PowerShell (a Windows-centric tool), and omitting Linux or cross-platform command-line examples. The documentation also references ARM templates, but PowerShell is emphasized as the primary method. There are no Linux-native instructions or examples, nor are cross-platform tools (like Azure CLI or Bash) mentioned.
Recommendations
- Provide equivalent Azure CLI (az) examples for all PowerShell-based instructions, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Linux/Bash shell command examples for certificate management tasks (such as converting certificates to PFX using OpenSSL), not just references to Windows APIs.
- Reference cross-platform certificate tools (e.g., OpenSSL) alongside or before Windows-specific tools and APIs.
- In 'Next steps', offer links to both PowerShell and Azure CLI (and/or ARM template) guides for configuring end-to-end TLS.
- Where possible, use neutral language (e.g., 'use your preferred tool' or 'using PowerShell, Azure CLI, or the Azure Portal') rather than defaulting to Windows/PowerShell.
- Add troubleshooting and configuration notes relevant to Linux environments (such as file permissions, certificate storage locations, etc.).
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 and PowerShell usage. All examples and instructions use Azure PowerShell cmdlets and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of Linux or cross-platform alternatives. There are no CLI, Bash, or Linux-native certificate generation examples, and the tutorial assumes a Windows environment throughout.
Recommendations
- Provide equivalent Azure CLI (az) commands for all resource creation and configuration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Linux-native instructions for generating self-signed certificates (e.g., using OpenSSL) alongside the PowerShell examples.
- Clearly indicate which steps are platform-specific and offer alternatives for non-Windows users.
- Reorganize the documentation so that cross-platform (CLI) examples are presented first or in parallel with PowerShell/Windows-specific instructions.
- Add notes or links to relevant documentation for Linux/macOS users, such as installing Azure CLI or using Bash scripts.
Application Gateway
Deploy Application Gateway Basic (Preview)
...in/articles/application-gateway/deploy-basic-portal.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates notable Windows bias. Azure PowerShell is the only CLI method shown for preview registration and IIS installation, with no equivalent Bash/Azure CLI or Linux examples. The VM creation example uses Windows Server exclusively, and IIS is used for backend testing, omitting Linux VM or web server alternatives. This creates friction for Linux/macOS users, though the portal-based steps are cross-platform.
Recommendations
- Provide Azure CLI (bash) examples for preview registration and unregistration alongside PowerShell.
- Include instructions for creating Linux VMs (e.g., Ubuntu) as backend targets, not just Windows Server.
- Offer Linux web server setup (e.g., Apache or Nginx) for backend testing, with sample install commands.
- Clarify that backend pools can use Linux VMs and provide parity in examples.
- Ensure that CLI instructions are presented for both PowerShell and Bash/Azure CLI, or link to equivalent Linux/macOS guidance.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page provides explicit instructions for enabling diagnostic logging via PowerShell, but does not offer equivalent CLI (az), Bash, or Linux/macOS examples. The only command-line example is a PowerShell cmdlet, which is Windows-centric. Additionally, references to log conversion tools are tied to Visual Studio and C#, which are more commonly associated with Windows environments. There is no mention of Linux/macOS-friendly alternatives or parity in command-line instructions.
Recommendations
- Add Azure CLI (az) examples for enabling diagnostic logging, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include Bash or shell script examples where relevant.
- Mention or link to log conversion tools that can be used on Linux/macOS, such as Python scripts or open-source alternatives.
- When referencing PowerShell, clarify that PowerShell Core is available cross-platform, but provide CLI alternatives for users who may not wish to install PowerShell.
- Ensure that examples and screenshots are not exclusively Windows-centric, and consider including Linux/macOS UI screenshots if relevant.
Application Gateway
Azure Application Gateway listener configuration
...rticles/application-gateway/configuration-listeners.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a PowerShell example for enabling HTTP/2 support but does not offer equivalent CLI (az), Bash, or Cloud Shell examples, nor does it mention Linux/macOS tooling. This may create friction for users who do not use PowerShell or Windows environments.
Recommendations
- Add Azure CLI (az) command examples alongside PowerShell for configuration tasks, especially for enabling HTTP/2 support.
- Explicitly mention that configuration can be performed from any OS using the Azure portal or Azure CLI.
- Where PowerShell is shown, provide Bash/CLI equivalents or link to cross-platform instructions.
- Clarify that PowerShell Core is available cross-platform if relevant, or recommend the Azure Cloud Shell for OS-agnostic scripting.
Application Gateway
Health monitoring overview for Azure Application Gateway
...lication-gateway/application-gateway-probe-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides PowerShell-centric examples and references, particularly for custom probe configuration and advanced parameters (e.g., MinServers, probe match criteria). Linux equivalents (Azure CLI, ARM templates) are mentioned but not demonstrated, and PowerShell is presented as the primary method for advanced configuration. Additionally, PowerShell cmdlets are shown before any mention of other tools, creating a Windows-first impression.
Recommendations
- Add Azure CLI examples for probe configuration and match criteria, especially for custom probes and advanced settings like MinServers.
- Include ARM template snippets for relevant configuration tasks.
- Explicitly state parity between PowerShell and Azure CLI/ARM for all probe-related operations.
- Where PowerShell is used, provide equivalent CLI commands or links to CLI documentation.
- Consider showing CLI examples before PowerShell or side-by-side for cross-platform clarity.