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 301-325 of 981 flagged pages
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 demonstrates a Windows bias by exclusively referencing Azure PowerShell scripts for migration tasks, with no mention of Azure CLI or Linux-native tooling. All migration automation examples and caveats are centered around 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 examples and scripts for migration tasks alongside PowerShell references.
- Explicitly mention that migration can be performed from Linux/macOS environments using Azure CLI or PowerShell Core, and provide instructions for those platforms.
- Add a section comparing PowerShell and CLI approaches, highlighting any differences or limitations.
- Ensure that all automation and scripting guidance is cross-platform, or clearly indicate platform requirements.
- Include troubleshooting and support guidance for users on Linux or macOS.
Create Pull Request
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller.md
...ploy-application-gateway-for-containers-alb-controller.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows a mild Windows bias, particularly in the Helm installation section, where Windows installation instructions (including a PowerShell/winget example) are presented before Linux instructions. The Windows-specific tool 'winget' is highlighted, and the PowerShell command is shown, while the Linux install is given as a generic bash command. The rest of the documentation is largely cross-platform, using Azure CLI and Helm commands that work on both Windows and Linux, but the ordering and tool emphasis favor Windows.
Recommendations
- Present Linux and Windows installation instructions in parallel tabs or in the same order (Linux first or alphabetical), rather than Windows first.
- Provide equal detail for both Linux and Windows installation steps, including package manager options for Linux (e.g., apt, yum, snap) in addition to the curl script.
- Avoid highlighting Windows-specific tools (like winget) without mentioning Linux equivalents (e.g., apt, yum, snap, or Homebrew for Linux).
- Where possible, use cross-platform commands and clarify when a command is OS-specific.
- Explicitly state that all Azure CLI and Helm commands are cross-platform and can be run in Bash, PowerShell, or Azure Cloud Shell.
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
Summary
The documentation demonstrates a moderate Windows bias. While the core certificate generation steps use OpenSSL (cross-platform), Windows and PowerShell are prioritized or exclusively featured in several areas: Windows is mentioned first in prerequisites, IIS (Windows web server) is documented before Apache/NGINX, and only Azure PowerShell is shown for Application Gateway configuration with no Azure CLI or ARM template equivalents. The only provided automation script is for PowerShell, and file paths in examples use Windows conventions.
Recommendations
- Provide Azure CLI and/or ARM template examples alongside or before Azure PowerShell for Application Gateway configuration.
- List Linux and Windows equally in prerequisites, or mention Linux first when OpenSSL is the primary tool.
- Alternate or parallelize web server configuration instructions (e.g., show Apache/NGINX before or alongside IIS).
- Include Linux-style file paths in examples, or clarify that file paths are OS-dependent.
- Where possible, link to cross-platform documentation for tasks like importing certificates into trusted stores.
- Explicitly state that all OpenSSL commands work identically on Linux and Windows, and provide any OS-specific notes if needed.
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 command-line example, exclusively referencing Windows-centric tools like Fiddler (with installation instructions that assume Windows), and omitting equivalent Linux or cross-platform alternatives. There are no CLI or Bash examples, and troubleshooting steps focus on Windows workflows, with no mention of Linux-compatible tools or methods.
Recommendations
- Provide Azure CLI (az) or Bash examples alongside PowerShell commands for checking Application Gateway settings.
- Mention and provide instructions for using cross-platform or Linux-friendly web debugging tools (e.g., Wireshark, mitmproxy, curl) in addition to Fiddler.
- Include Linux-specific steps for collecting and analyzing logs, such as using jq to parse ARM template JSON or using Azure CLI on Linux.
- Avoid assuming the user is on Windows (e.g., 'Run as administrator', '.NET 4', 'right click the setup executable') and offer parallel instructions for Linux/macOS environments.
- List both Windows and Linux tools and workflows in troubleshooting sections, or explicitly state when a tool is Windows-only and suggest alternatives.
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
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing only Azure PowerShell examples for scripting and automation, referencing PowerShell steps before (or instead of) Azure CLI or cross-platform alternatives, and omitting Linux-specific or cross-platform command-line examples. The 'Next steps' section also directs users to a PowerShell-based guide, reinforcing the bias. There is no mention of Bash, Linux shell, or platform-agnostic scripting for certificate management or deployment.
Recommendations
- Provide equivalent Azure CLI (az) examples alongside PowerShell for all automation steps, especially for referencing Key Vault secrets and configuring Application Gateway.
- Include Bash/Linux shell script examples for certificate management and deployment tasks.
- In sections where PowerShell is referenced, mention Azure CLI and provide links or inline examples for both platforms.
- Update the 'Next steps' section to include links to CLI and ARM/Bicep template guides, not just PowerShell.
- Explicitly state that all steps can be performed on both Windows and Linux, and clarify any platform-specific requirements.
- Where screenshots or UI steps are shown, clarify that the Azure portal is cross-platform and accessible from any OS.
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 Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell scripts and cmdlets for migration and preview registration, without providing equivalent Azure CLI (cross-platform) or Bash examples. The only command-line examples use PowerShell syntax, and the migration script is specifically described as an Azure PowerShell script. There is no mention of Linux or Bash alternatives, and the PowerShell approach is presented as the default or only method.
Recommendations
- Provide Azure CLI (az) command examples alongside PowerShell for all operations, especially for migration and preview registration/unregistration.
- Clarify that Azure CLI commands are cross-platform and can be used on Windows, Linux, and macOS.
- Where PowerShell scripts are referenced, link to or provide equivalent Bash/CLI scripts if available.
- In 'Next steps', include links to tutorials or modules that use Azure CLI or Bash, not just PowerShell.
- Avoid presenting PowerShell as the default or only automation method; mention both PowerShell and CLI equally, or lead with CLI for cross-platform inclusivity.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-autoscaling-zone-redundant.md
...eway/application-gateway-autoscaling-zone-redundant.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
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 equivalent instructions or links for Linux users (e.g., using Azure CLI, ARM templates, or Bicep), and PowerShell is a Windows-centric tool. This prioritizes Windows tooling and patterns, potentially excluding or inconveniencing users on Linux or macOS.
Recommendations
- Add equivalent Azure CLI tutorials and links for creating autoscaling, zone redundant application gateways.
- Include ARM template and/or Bicep deployment examples for cross-platform parity.
- Ensure that references to tooling in 'Next steps' and throughout the documentation are balanced, mentioning both PowerShell and CLI (and other cross-platform options) together.
- Where possible, provide code snippets for both PowerShell and CLI in the main documentation body, not just in linked tutorials.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-ssl-policy-overview.md
...ion-gateway/application-gateway-ssl-policy-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and Windows-centric tools and patterns as the primary or sole method for configuring and viewing TLS policies. There is a lack of Linux/Unix-specific examples or parity in instructions, and PowerShell is mentioned before or instead of cross-platform or Linux-native tools. The 'Next steps' section links only to a PowerShell-based guide, and throughout the page, PowerShell is referenced as the main interface for configuration and information retrieval, with no mention of Bash, Azure CLI on Linux, or REST API usage from non-Windows environments.
Recommendations
- Provide equivalent Linux/Bash/Azure CLI examples alongside or before PowerShell examples for all configuration and retrieval tasks.
- Explicitly mention that Azure CLI and REST API can be used from any platform, and provide sample commands for Linux/macOS users.
- In the 'Next steps' section, link to both PowerShell and Azure CLI (and/or REST API) guides for configuring TLS policy.
- Avoid referencing PowerShell as the default or only method; instead, present cross-platform tools (like Azure CLI) first or equally.
- Add a section or callout for Linux/macOS administrators, highlighting any platform-specific considerations or steps.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller.md
...ploy-application-gateway-for-containers-alb-controller.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation displays a mild Windows bias, particularly in the Helm installation section, where Windows installation instructions (including a PowerShell/winget example) are presented before Linux, and Windows-specific tooling (winget) is mentioned explicitly. The Linux installation is covered, but the ordering and detail favor Windows. The rest of the guide uses cross-platform tools (Azure CLI, Helm, kubectl) and Bash-style scripting, which is generally Linux-friendly, but the explicit Windows-first ordering and inclusion of Windows package manager commands indicate a subtle bias.
Recommendations
- Present Linux and Windows installation instructions in parallel tabs or in the same order (Linux first or alphabetical), to avoid privileging Windows.
- Provide equivalent package manager commands for Linux (e.g., apt, yum, snap) alongside the Windows winget example for Helm installation.
- Ensure that all examples and instructions are equally detailed for both Windows and Linux, including troubleshooting notes.
- Where possible, use cross-platform shell syntax or clearly mark which commands are for which OS.
- Consider adding explicit macOS instructions where relevant, to further improve cross-platform parity.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-private-deployment.md
...tion-gateway/application-gateway-private-deployment.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Azure PowerShell instructions before Azure CLI, referencing PowerShell-specific cmdlets for status checks even in CLI sections, and omitting explicit Linux shell or cross-platform command-line examples. The workflow and screenshots are oriented around the Azure Portal and PowerShell, which are more familiar to Windows users, with no mention of Bash, Linux-specific tooling, or guidance for non-Windows environments.
Recommendations
- Present Azure CLI instructions before or alongside PowerShell to emphasize cross-platform support.
- Ensure all command-line examples are shown in both PowerShell and Bash (Linux/macOS) syntax, especially for status checks (e.g., use 'az feature show' instead of referencing Get-AzProviderFeature in CLI sections).
- Include explicit guidance or notes for Linux/macOS users, such as terminal screenshots or shell-specific tips.
- Avoid referencing PowerShell cmdlets in CLI sections; use the appropriate CLI commands for status checks and other operations.
- Where possible, provide ARM/Bicep/Terraform examples in addition to Portal, PowerShell, and CLI to further enhance platform neutrality.
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
Windows Tools
Missing Linux Example
Summary
The documentation page exclusively references Azure PowerShell scripts for migration tasks and does not mention or provide examples for alternative tools or platforms, such as Azure CLI or Bash scripts. There are no Linux or cross-platform migration instructions, and the only automation method discussed is PowerShell, which is most commonly associated with Windows environments.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for all migration steps, ensuring Linux and macOS users have clear, first-class guidance.
- Explicitly mention that migration can be performed from any platform (Windows, Linux, macOS) and clarify any platform-specific requirements or limitations.
- Include Bash script examples or references for common migration tasks, especially for configuration and traffic migration.
- If certain features are only available in PowerShell, state this clearly and provide a roadmap or alternatives for non-Windows users.
- Add a section comparing PowerShell and CLI approaches, helping users choose the best tool for their environment.
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
Windows Tools
Summary
The documentation page exhibits a strong Windows bias. PowerShell is the only command-line example provided for configuring Key Vault integration, with no equivalent Azure CLI (cross-platform) or Bash/Linux shell examples. The 'Next steps' section exclusively links to a PowerShell-based guide. Throughout the document, PowerShell and ARM templates are mentioned before the Azure CLI, and there are no Linux- or macOS-specific instructions or examples. This may hinder Linux users or those preferring cross-platform tools.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell command snippets, especially for critical tasks like referencing Key Vault secrets and configuring Application Gateway.
- In the 'Next steps' section, include links to Azure CLI and/or Bash-based guides alongside PowerShell guides.
- When listing tools or methods (e.g., PowerShell, CLI, ARM templates), mention Azure CLI first or equally, and clarify that all steps can be performed cross-platform.
- Add explicit Linux/macOS shell examples where relevant, or note that all steps are supported on non-Windows platforms.
- Review screenshots and UI instructions to ensure they are not Windows-specific, or add notes for Linux/macOS users if differences exist.
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 cmdlets for migration and preview registration tasks, with no explicit mention of Linux or cross-platform alternatives. The CLI examples provided use Azure CLI, but the commands shown are actually PowerShell cmdlets (e.g., Set-AzContext), which are not native to Linux/macOS environments. There is no mention of Bash, Cloud Shell, or Linux-specific workflows, and the only migration script referenced is a PowerShell script. This may create the impression that Windows or PowerShell is the default or only supported environment.
Recommendations
- Provide equivalent Bash/Azure CLI examples for all PowerShell commands, especially for registration, unregistration, and migration tasks.
- Clarify which commands are PowerShell-specific and offer cross-platform alternatives where possible.
- Reference Azure Cloud Shell as a cross-platform option for both PowerShell and Bash users.
- Include explicit instructions or links for Linux/macOS users, ensuring parity in tooling and workflow documentation.
- If migration scripts are only available in PowerShell, note this limitation and provide guidance or a roadmap for Linux support.
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 shows a Windows bias by providing PowerShell as the only CLI example for checking settings, exclusively recommending Fiddler (a Windows-centric tool) for network capture, and referencing Windows installation patterns (e.g., 'Run as administrator'). There are no Linux or cross-platform CLI examples (such as Azure CLI or Bash), nor are Linux-friendly network tools (like tcpdump, Wireshark, or curl) mentioned. The step-by-step instructions and screenshots are all based on Windows environments.
Recommendations
- Provide Azure CLI (az) and/or REST API examples alongside PowerShell for configuration checks, with sample commands for Linux/macOS users.
- Include Linux-friendly network capture and debugging tools (e.g., tcpdump, Wireshark, curl, httpie) as alternatives to Fiddler, with brief usage instructions.
- When referencing installation steps, add Linux/macOS equivalents (e.g., 'use sudo to install', 'install via apt/yum/brew').
- Add screenshots or terminal output examples from Linux environments where relevant.
- Use neutral language such as 'your preferred web debugger' and list both Windows and Linux options.
- Ensure that troubleshooting steps and tool recommendations are platform-agnostic or provide parity for all major operating systems.
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 core certificate generation steps use OpenSSL (a cross-platform tool) and mention both Windows and Linux, several sections prioritize or exclusively provide Windows-centric instructions and tools. The IIS section is detailed and links to Windows Server documentation, while Apache and NGINX are only given brief configuration snippets. The Azure PowerShell example is provided in detail, but there is no equivalent Azure CLI (cross-platform) example. Instructions for adding the root certificate to the trusted store are vague and do not provide Linux-specific guidance. The hosts file editing note links to a generic article, not platform-specific instructions.
Recommendations
- Provide Azure CLI examples alongside Azure PowerShell for uploading certificates and configuring Application Gateway, as Azure CLI is cross-platform.
- Expand the Linux guidance for adding the root certificate to the trusted root store (e.g., update-ca-certificates on Ubuntu, trust anchors on RHEL, etc.).
- Offer parity in web server configuration instructions: include links to official documentation for Apache and NGINX, similar to the detailed IIS section.
- When referencing file paths (e.g., C:\Users\...), provide Linux equivalents or use generic paths.
- When mentioning editing the hosts file, provide explicit instructions or links for both Windows and Linux.
- Review the order of presentation to avoid always listing Windows tools or instructions first.
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 Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by primarily referencing Azure PowerShell scripts and cmdlets for migration and preview registration/unregistration, and by listing Azure PowerShell before Azure CLI and portal in the 'Next steps' section. There are no explicit Linux or Bash examples, and the use of 'Set-AzContext', 'Get-AzProviderFeature', and 'Register-AzProviderFeature' are PowerShell-specific, which may not be familiar to Linux users. The documentation does mention Azure CLI, but the commands shown are actually PowerShell cmdlets, not true Azure CLI (az) commands.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside or before PowerShell examples, especially for registration, unregistration, and migration tasks.
- Clearly distinguish between Azure PowerShell and Azure CLI commands, and ensure that Azure CLI examples use the correct syntax (e.g., 'az feature register' instead of 'Register-AzProviderFeature').
- Include Bash shell examples for common tasks to improve accessibility for Linux users.
- In the 'Next steps' and other instructional sections, list Azure CLI and portal options before or alongside PowerShell to avoid the perception of Windows-first bias.
- Review and update any references to Windows-specific tools or patterns to ensure Linux parity throughout the documentation.
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
Windows Tools
Summary
The documentation page demonstrates a significant Windows bias. PowerShell is the only command-line example provided for configuring Application Gateway with Key Vault certificates, with no equivalent Azure CLI (cross-platform) or Bash/Linux shell examples. The narrative and examples prioritize Windows-centric tools and workflows (PowerShell, Azure portal), and there is no mention of Linux-specific considerations or parity in the walkthroughs. This may hinder Linux users or those preferring cross-platform automation tools.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell command sequences, especially for certificate referencing and managed identity configuration.
- Include Bash or shell script snippets where relevant, or clarify that Azure CLI commands are cross-platform.
- When listing tools or methods (e.g., PowerShell, CLI, ARM templates), avoid listing Windows-specific tools first or exclusively; present Azure CLI and ARM/Bicep as primary, cross-platform options.
- Explicitly mention that the steps are applicable on both Windows and Linux, or highlight any OS-specific considerations.
- Add a 'Linux/CLI Example' section parallel to the PowerShell example, ensuring Linux users have clear, actionable guidance.
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 referencing Windows-centric tools like Fiddler for network debugging, and giving installation instructions that assume a Windows environment (e.g., 'Run as administrator' for .exe files). There are no Linux or cross-platform alternatives mentioned for these tasks, and Windows tools and patterns are presented first and exclusively.
Recommendations
- Provide equivalent Azure CLI or Azure Cloud Shell examples for checking Application Gateway settings, as these are cross-platform and work on Linux, macOS, and Windows.
- Include Linux-friendly network debugging alternatives to Fiddler, such as tcpdump, Wireshark, or mitmproxy, and provide basic usage instructions for these tools.
- When referencing installation steps, include Linux-specific instructions (e.g., using package managers or running tools from the terminal) alongside Windows instructions.
- Use neutral language when referring to tools (e.g., 'web debugging tool of your choice') and ensure that screenshots and examples are not exclusively from Windows environments.
- Explicitly mention that the troubleshooting steps can be performed from any OS, and provide parity in examples and tool recommendations.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-autoscaling-zone-redundant.md
...eway/application-gateway-autoscaling-zone-redundant.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure PowerShell for automation and deployment tasks, particularly in the 'Next steps' section. There are no examples or links for Linux users (e.g., Azure CLI, Bash scripts), and Windows-centric tools are mentioned without Linux equivalents. This can make it harder for Linux users to follow or implement the guidance.
Recommendations
- Include Azure CLI examples and tutorials alongside or before PowerShell examples, especially in the 'Next steps' section.
- Provide Bash script samples for common automation tasks.
- Ensure that documentation references both Windows and Linux tools equally, or at least in parallel.
- Explicitly mention cross-platform options (e.g., Azure CLI works on Windows, Linux, and macOS) when discussing automation or scripting.
- Add links to Linux-focused tutorials or documentation where available.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-ssl-policy-overview.md
...ion-gateway/application-gateway-ssl-policy-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing PowerShell and CLI as the primary configuration tools, with PowerShell mentioned first and linked directly for configuration tasks. There are no explicit Linux or Bash examples, nor are Linux-native tools or workflows mentioned. The guidance and examples are oriented toward Windows administrators, and Linux parity is not addressed.
Recommendations
- Provide explicit Bash/Azure CLI examples alongside or before PowerShell examples for all configuration tasks.
- Include references to Linux-native workflows and tools (e.g., Bash shell, Linux command line) in the documentation.
- Ensure that links to configuration guides include both PowerShell and Bash/CLI options, not just PowerShell.
- Use neutral language when referring to tools (e.g., 'using Azure CLI or PowerShell' instead of 'using PowerShell or CLI'), and avoid always listing Windows tools first.
- Add a section or callout for Linux administrators to clarify that all operations can be performed on Linux systems using Azure CLI or REST API.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller.md
...ploy-application-gateway-for-containers-alb-controller.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation displays a mild Windows bias, particularly in the Helm installation section, where Windows installation instructions (including the use of the Windows-specific 'winget' package manager and a PowerShell code block) are presented before Linux instructions. The Linux installation is provided, but the structure and ordering give Windows precedence. Additionally, the only package manager mentioned by name is 'winget', a Windows tool, with no mention of common Linux package managers (e.g., apt, yum, snap). The rest of the guide uses cross-platform tools (Azure CLI, Helm, kubectl) and Bash syntax, which are generally platform-agnostic, but the explicit Windows-first ordering and tool mention stand out.
Recommendations
- Present Linux and Windows installation instructions in parallel tabs or in alphabetical order (Linux first, Windows second, or vice versa, but consistently).
- For Helm installation, provide explicit package manager examples for both Windows (winget, choco) and Linux (apt, yum, snap), or link to the official Helm install page for both.
- Avoid giving Windows-specific tools (like winget) exclusive mention; if a Windows tool is mentioned, provide Linux equivalents.
- Consider using neutral language such as 'On Windows, you can use...' and 'On Linux, you can use...' rather than listing Windows first.
- Where possible, use cross-platform shell commands or clarify which commands are for which OS, ensuring parity in detail and clarity.
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
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively referencing Azure PowerShell scripts for migration, without mentioning or providing examples for Azure CLI, Bash, or other cross-platform tools. There are no Linux/Unix-specific instructions or examples, and the PowerShell approach is presented as the default and only method for migration tasks.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for all migration steps, alongside PowerShell examples.
- Explicitly mention that migration can be performed from Linux/macOS environments using Azure CLI or Bash scripts.
- Include sample Bash scripts or command-line instructions for Linux users.
- Clarify tool parity and recommend cross-platform tools where possible, not just PowerShell.
- Reorder examples or explanations to present cross-platform solutions (Azure CLI, REST API) before or alongside PowerShell.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/redirect-overview.md
...main/articles/application-gateway/redirect-overview.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation page does not provide any platform-specific command-line examples, but the only 'Next steps' link points to a PowerShell-based tutorial, which is Windows-centric. There is no mention of Linux tools, Bash, or cross-platform CLI options, and the documentation implicitly assumes PowerShell as the default automation method.
Recommendations
- Include links to equivalent tutorials using Azure CLI (az), which is cross-platform and commonly used on Linux.
- Explicitly mention that configuration can be performed using Azure CLI, ARM templates, or REST API, not just PowerShell.
- Provide example commands or links for both PowerShell and Azure CLI in the 'Next steps' section.
- Consider adding a table or section comparing configuration steps across PowerShell, Azure CLI, and the Azure Portal to ensure parity for Linux users.
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 provides a generally cross-platform approach for certificate generation using OpenSSL, which is available on both Windows and Linux. However, there is a noticeable Windows bias in several areas: (1) Windows tools and patterns (such as IIS and PowerShell) are mentioned first or exclusively, (2) the Azure PowerShell example is detailed while no equivalent Azure CLI (cross-platform) example is provided, (3) references to file paths and certificate stores use Windows conventions, and (4) instructions for adding certificates to the trusted root store and web server configuration are more explicit for Windows (IIS) than for Linux equivalents (Apache/NGINX).
Recommendations
- Provide Azure CLI examples alongside or before Azure PowerShell examples for uploading certificates to Application Gateway.
- Include explicit instructions or links for adding root certificates to trusted stores on Linux (e.g., update-ca-certificates on Ubuntu) and macOS, not just Windows.
- When referencing file paths, use cross-platform or Linux examples (e.g., /home/user/contoso.cer) in addition to Windows paths (e.g., C:\Users\...).
- Balance server configuration guidance by providing step-by-step instructions or official documentation links for Apache and NGINX (Linux) equivalent to those given for IIS (Windows).
- When mentioning editing the hosts file, provide Linux/macOS file locations (/etc/hosts) and editing instructions, not just a generic link.
- Consider listing Linux/Apache/NGINX examples before or alongside Windows/IIS examples to avoid 'windows_first' ordering.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-autoscaling-zone-redundant.md
...eway/application-gateway-autoscaling-zone-redundant.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
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 CLI (cross-platform) or Linux-specific instructions or examples provided, and the only explicit tooling reference is to PowerShell, which is traditionally associated with Windows environments. This may give the impression that Windows or PowerShell is the preferred or only supported environment for these operations.
Recommendations
- Include equivalent Azure CLI (az) instructions and tutorials alongside PowerShell examples to ensure cross-platform accessibility.
- In the 'Next steps' section, provide links to both PowerShell and CLI-based tutorials for creating and managing autoscaling Application Gateways.
- Explicitly mention that all features are available via both PowerShell and CLI, and provide parity in documentation coverage.
- If possible, add Bash script examples or references for Linux users.
- Avoid listing Windows/PowerShell tools before their cross-platform or Linux equivalents, or present them together.