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 351-375 of 981 flagged pages
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 main certificate generation instructions use OpenSSL (cross-platform), Windows-specific tools and patterns are prioritized or highlighted in several places. The Azure PowerShell example is given in detail, with no equivalent Azure CLI (cross-platform) example. The IIS (Windows web server) configuration is presented before Apache and NGINX, and the file path in the PowerShell example uses a Windows-style path. There is also a reference to editing the hosts file with a link that is Windows-centric.
Recommendations
- Add Azure CLI examples alongside or before Azure PowerShell for certificate upload and configuration, as CLI is cross-platform.
- Present Linux/Unix web server configuration examples (Apache, NGINX) before or alongside IIS, or clarify that order is not indicative of priority.
- Include Linux file path examples in addition to Windows paths in code samples.
- Provide explicit instructions or links for editing the hosts file on both Windows and Linux/macOS.
- Ensure that any references to tools or steps that are Windows-specific are matched with Linux/macOS equivalents where possible.
Create Pull Request
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 demonstrates a Windows bias by exclusively referencing Azure PowerShell scripts for migration tasks, without mentioning or providing examples for Azure CLI, Bash, or other cross-platform tools. There are no Linux-specific instructions or examples, and the only automation method discussed is PowerShell, which is most commonly associated with Windows environments.
Recommendations
- Provide equivalent Azure CLI (az) commands or scripts for all migration steps, ensuring Linux and macOS users have clear guidance.
- Explicitly mention that migration can be performed from any OS, and clarify any OS-specific prerequisites or limitations.
- Include Bash or shell script examples where automation is discussed, or at least reference cross-platform scripting options.
- Add a section comparing PowerShell and CLI approaches, helping users choose the best tool for their environment.
- Ensure that all documentation references to scripts or tools are inclusive of both Windows and Linux users.
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
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias through the exclusive use of Azure PowerShell commands and references to the PowerShell Gallery for migration scripts. Azure CLI is mentioned, but the provided command examples use PowerShell cmdlets and patterns (e.g., Set-AzContext, Register-AzProviderFeature) rather than cross-platform Azure CLI equivalents. There are no Linux-specific or bash shell examples, and no mention of Linux tooling or workflows. The migration script is only referenced as a PowerShell script, with no alternative for Linux users.
Recommendations
- Provide Azure CLI (az) command examples alongside or before PowerShell examples, as Azure CLI is cross-platform and preferred by many Linux users.
- Explicitly mention that the migration script is only available as a PowerShell script, and provide a bash/Azure CLI alternative or instructions for Linux users.
- When listing tools or workflows (e.g., for registering previews), ensure both PowerShell and Azure CLI examples are given, or default to Azure CLI for cross-platform parity.
- Add a section or callout for Linux/macOS users, clarifying supported tools and any differences in workflow.
- Review linked tutorials (e.g., 'tutorial-autoscale-ps.md') to ensure they also provide non-Windows, non-PowerShell options.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller.md
...ploy-application-gateway-for-containers-alb-controller.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias, particularly in the Helm installation section, where Windows instructions (including use of the Windows-specific 'winget' package manager and PowerShell command) are presented before Linux instructions. The Linux example is present but less detailed. There is also a reference to Azure Cloud Shell, which is cross-platform but often used in a Windows context. The rest of the documentation uses Azure CLI and Bash, which are cross-platform, but the explicit ordering and detail of Windows instructions indicate a 'windows_first' and 'windows_tools' bias.
Recommendations
- Present Linux and Windows installation instructions for Helm with equal prominence and detail, ideally side-by-side or in a tabbed format with no ordering preference.
- Provide explicit Bash and PowerShell examples for all relevant commands, not just for Helm installation.
- Include macOS installation instructions for Helm to further improve parity.
- Avoid referencing Windows-specific tools (like 'winget') without providing equivalent Linux package manager examples (e.g., apt, yum, snap).
- Clarify that Azure CLI and Helm commands are cross-platform and can be run in any supported shell environment.
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, with no mention of Azure CLI, Bash, or Linux-native tooling. All migration automation examples and caveats are described in the context of PowerShell, which is traditionally associated with Windows environments. There are no Linux/Unix shell or cross-platform examples, nor is there guidance for users who may prefer or require non-Windows tooling.
Recommendations
- Provide equivalent Azure CLI (az) commands or scripts for migration tasks alongside PowerShell examples.
- Explicitly mention that migration can be performed from Linux/macOS environments using Azure CLI or Bash, and provide relevant instructions.
- Include cross-platform sample scripts or reference documentation for both PowerShell and CLI/Bash to ensure parity.
- Clarify any limitations or differences between PowerShell and CLI approaches, if applicable.
- Add a section addressing Linux/macOS users and their migration workflow.
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
Summary
The documentation page references Azure PowerShell as the only example for creating an autoscaling, zone-redundant application gateway, without mentioning or linking to equivalent instructions for Linux users (such as Azure CLI or ARM templates). This suggests a bias towards Windows tooling and may make it less accessible for users on Linux or macOS platforms.
Recommendations
- Provide equivalent examples and tutorials using Azure CLI, which is cross-platform and widely used on Linux.
- Include references or links to ARM/Bicep template-based deployment guides for users who prefer declarative infrastructure.
- When listing 'Next steps' or providing code samples, ensure that both PowerShell and CLI (and/or template) options are presented side-by-side or with clear links.
- Explicitly mention that Azure PowerShell is available cross-platform, but also clarify when instructions are Windows-specific.
- Audit other documentation pages linked from this one to ensure Linux parity is maintained throughout the user journey.
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 methods, and the documentation implicitly assumes PowerShell as the default automation tool.
Recommendations
- Include links to equivalent tutorials using Azure CLI (az), which is cross-platform and works on Linux, macOS, and Windows.
- Explicitly mention that configuration can be performed using Azure CLI, ARM templates, or REST API, not just PowerShell.
- Provide example commands or scripts for both PowerShell and Azure CLI when demonstrating configuration steps.
- Add a 'Next steps' link to a Linux-friendly or cross-platform guide, such as 'Configure URL redirection using Azure CLI'.
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 CLI as the primary configuration tools, with PowerShell consistently mentioned first. There are no explicit Linux or Bash examples, nor are Linux-native tools or workflows referenced. The guidance and links for configuration focus on PowerShell, and the absence of Linux/Bash-specific instructions or parity in tool coverage may hinder Linux users.
Recommendations
- Include explicit Bash/Azure CLI examples alongside or before PowerShell examples for all configuration steps.
- When referencing configuration tools, use neutral phrasing (e.g., 'Azure CLI or PowerShell') and ensure both are covered equally.
- Add links to Linux/Bash-focused configuration guides, not just PowerShell documentation.
- If mentioning PowerShell, clarify that Azure CLI is fully supported and provide parallel instructions.
- Review all 'Next steps' and instructional links to ensure Linux users are not directed only to PowerShell-based guides.
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 main certificate generation steps use OpenSSL (cross-platform), Windows and PowerShell tools are prioritized or exclusively featured in several areas: Windows is mentioned first in prerequisites, IIS (Windows web server) instructions precede Linux alternatives, and only Azure PowerShell is shown for Application Gateway configuration (no Azure CLI or ARM template examples). File paths and screenshots also reflect Windows environments.
Recommendations
- Provide Azure CLI and/or ARM template examples alongside or before Azure PowerShell for Application Gateway configuration, especially for uploading certificates and backend HTTP settings.
- Balance web server configuration examples by presenting Linux/Unix (Apache, NGINX) before or alongside IIS, or alternate their order.
- Use neutral or Linux-style file paths in examples, or provide both Windows and Linux path variants where relevant.
- In prerequisites, mention Linux before or alongside Windows, and clarify that OpenSSL is available on both platforms.
- Include screenshots and instructions that reflect both Windows and Linux environments, especially for tasks like adding certificates to the trusted root store.
- Where possible, link to both Windows and Linux documentation for related tasks (e.g., editing the hosts file, importing certificates).
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 exhibits a Windows bias by prioritizing PowerShell commands for configuration checks, exclusively recommending Fiddler (a Windows-centric tool) for network debugging, and providing installation instructions that assume a Windows environment (e.g., 'Run as administrator'). There are no Linux or cross-platform alternatives mentioned for command-line or debugging tasks.
Recommendations
- Provide equivalent Azure CLI commands for checking Application Gateway settings, as Azure CLI is cross-platform.
- Include examples using Linux-native tools for network debugging, such as tcpdump, Wireshark, or curl, alongside or instead of Fiddler.
- When referencing downloadable tools, mention cross-platform options (e.g., Wireshark, mitmproxy) and provide installation instructions for both Windows and Linux.
- Avoid language and screenshots that assume a Windows environment (e.g., 'right click and run as administrator'), or supplement with Linux-specific instructions.
- Ensure that troubleshooting steps and log analysis can be performed on both Windows and Linux systems, and provide examples for each.
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 Windows bias by providing only PowerShell-based examples for automating Key Vault integration with Application Gateway, with no equivalent Azure CLI (cross-platform) or Bash/Linux shell examples. PowerShell is mentioned and used exclusively in code samples and step-by-step instructions, and the 'Next steps' section links only to a PowerShell-based guide. There is no mention or prioritization of Linux or cross-platform tooling, and no examples are given for users on non-Windows systems.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell commands, especially for key tasks such as referencing Key Vault secrets and configuring Application Gateway.
- Include Bash or shell script snippets where appropriate to demonstrate cross-platform automation.
- In step-by-step instructions, mention both Azure CLI and PowerShell options, and avoid assuming the user is on Windows.
- Update the 'Next steps' section to include links to Azure CLI and/or Bicep/ARM template guides, not just PowerShell.
- Where screenshots or UI steps are shown, clarify that the instructions apply regardless of OS, and provide CLI alternatives.
- Explicitly state that all operations can be performed from Linux, macOS, or Windows, and ensure parity in documentation coverage.
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
Summary
The documentation page references Azure PowerShell in the 'Next steps' section as the only example for creating an autoscaling, zone redundant application gateway, without mentioning or linking to equivalent Azure CLI (cross-platform) or ARM template instructions. This suggests a bias toward Windows/PowerShell tooling, with no Linux or cross-platform alternatives presented.
Recommendations
- Add links or instructions for creating an autoscaling, zone redundant application gateway using Azure CLI, which is cross-platform and widely used on Linux.
- Include references to ARM/Bicep templates for infrastructure-as-code scenarios, which are platform-agnostic.
- Ensure that examples and tutorials are provided for both PowerShell and CLI in the 'Next steps' section, or provide a general link to all available methods.
- Consider reordering or grouping tooling links so that cross-platform options (CLI, ARM) are presented alongside or before PowerShell examples.
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 Windows bias by providing only PowerShell-based examples for configuring Application Gateway with Key Vault certificates, with no equivalent Azure CLI, Bash, or Linux-native instructions. PowerShell is referenced as the primary automation tool, and the 'Next steps' section links exclusively to a PowerShell guide. There are no Linux-specific or cross-platform command examples, and Windows-centric tools and patterns are mentioned before any alternatives.
Recommendations
- Provide equivalent Azure CLI examples alongside PowerShell for all configuration steps, especially for tasks like referencing Key Vault secrets and configuring Application Gateway listeners.
- Include Bash shell scripts or command-line instructions that are platform-agnostic to ensure Linux users can follow along without needing PowerShell.
- In the 'Next steps' section, add links to guides for Azure CLI and ARM/Bicep templates, not just PowerShell.
- When referencing automation or scripting, mention both PowerShell and CLI options, and avoid presenting PowerShell as the default or only method.
- Explicitly state that all steps can be performed on both Windows and Linux, and provide any necessary notes for cross-platform compatibility.
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, without mentioning or providing examples for cross-platform alternatives such as Azure CLI or REST API. There are no Linux/bash examples or guidance, and the only automation tooling discussed is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Include Azure CLI examples and guidance for migration steps alongside or in place of PowerShell scripts.
- Explicitly state whether the migration scripts and processes are supported on Linux/macOS environments, and provide instructions for those platforms.
- If REST API or ARM template options exist for migration, document them to provide platform-agnostic alternatives.
- Balance references to PowerShell with equivalent bash or shell script examples where possible.
- Clarify prerequisites for running PowerShell scripts on non-Windows systems (e.g., PowerShell Core on Linux/macOS) if PowerShell is the only supported method.
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 primarily referencing PowerShell for configuration tasks and omitting explicit Linux or cross-platform examples. The only configuration guide linked is for PowerShell, and instructions for using the Azure CLI (which is cross-platform) or Linux-native tools are not provided or are mentioned only in passing. The documentation also refers to the PowerShell, CLI, REST API, or Portal for details, but PowerShell is consistently mentioned first, and no Linux-specific guidance or examples are included.
Recommendations
- Add explicit Azure CLI examples for all configuration steps, ensuring parity with PowerShell instructions.
- Include links to both PowerShell and Azure CLI (and, where relevant, REST API) documentation for configuring TLS policies.
- Where referencing command-line tools, alternate the order (e.g., 'CLI or PowerShell') or clarify that CLI is cross-platform.
- Provide at least one example of configuring TLS policy from a Linux environment using Azure CLI.
- Ensure that all 'Next steps' and instructional links include both Windows and Linux/cross-platform options.
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 exhibits mild Windows bias, particularly in the Helm installation section, where Windows instructions (including a PowerShell/winget example) are presented before Linux. The use of Windows-specific tools (winget) is highlighted, and the Windows tab appears before the Linux tab. However, the majority of command-line examples use Azure CLI and Bash syntax, which are cross-platform and Linux-friendly.
Recommendations
- Present Linux and Windows installation instructions in parallel or with Linux first, as Linux is the primary OS for most Kubernetes administrators.
- Avoid prioritizing Windows-specific tools (such as winget) in examples; instead, provide equal prominence to Linux package managers (apt, yum, snap) and Homebrew for macOS.
- Where possible, use cross-platform installation methods or clearly indicate which commands are for which OS, ensuring Linux and macOS are not afterthoughts.
- Explicitly mention macOS where relevant, as it is also a common platform for Kubernetes administrators.
- Ensure that all examples and instructions are tested and validated on both Linux and Windows environments.
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 (Get-AzApplicationGatewayBackendHttpSetting) as the only CLI example for checking configuration, and exclusively referencing Fiddler (a Windows-centric tool) for network debugging. There are no Linux or cross-platform command-line examples (such as Azure CLI or Bash), nor are Linux-friendly tools (like tcpdump, curl, or Wireshark) mentioned. The instructions for downloading and installing Fiddler also assume a Windows environment (e.g., 'run as administrator').
Recommendations
- Add Azure CLI (az network application-gateway http-settings list) and/or Bash examples alongside or before PowerShell commands.
- Mention and provide examples for cross-platform or Linux-native network debugging tools such as tcpdump, Wireshark, or curl.
- When referencing Fiddler, clarify that it is Windows-centric and suggest alternatives for Linux/macOS users (e.g., mitmproxy, Wireshark).
- Ensure installation instructions and screenshots are not exclusive to Windows; provide parity for Linux/macOS where applicable.
- Adopt a tool-agnostic approach in troubleshooting steps, or at least present Windows and Linux options side by side.
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 providing only Azure PowerShell (a Windows-centric tool) examples for migration and preview registration/unregistration, and by referencing PowerShell scripts as the primary automation method. There are no explicit Linux or cross-platform CLI (Azure CLI/bash) examples, and PowerShell is mentioned before or instead of other options. This may hinder Linux users or those preferring cross-platform tooling.
Recommendations
- Add equivalent Azure CLI (bash) command examples alongside PowerShell commands for all operations, including migration, preview registration, and unregistration.
- When referencing automation scripts or tooling, mention both PowerShell and Azure CLI options, or clarify cross-platform support.
- In 'Next steps', provide links to tutorials or modules that use Azure CLI or bash, not just PowerShell.
- Where possible, use neutral language (e.g., 'Azure CLI or PowerShell') instead of listing PowerShell first or exclusively.
- If PowerShell scripts are referenced, note their compatibility with PowerShell Core on Linux/macOS, or provide alternative scripts for bash environments.
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
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation presents configuration steps for Azure Application Gateway Private Link with a clear preference for Windows-centric tools and workflows. The PowerShell section is detailed and appears before the Azure CLI section, and there are no explicit Linux shell or cross-platform scripting examples. The Azure portal and PowerShell are highlighted first, with CLI (the most cross-platform option) coming last. There are no references to Linux-specific tools, nor are there any bash or shell script examples. This may make the documentation less approachable for Linux users or those preferring non-Windows environments.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform parity.
- Include bash/shell script examples for common tasks, especially for subnet and network configuration, to assist Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
- Where possible, provide links or references to Linux-native tools (e.g., using curl or jq for REST API calls) for advanced scenarios.
- Balance the depth and detail of PowerShell and CLI sections to ensure both Windows and Linux users have equally comprehensive guidance.
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 and PowerShell are prioritized or exclusively featured in several areas: Windows is mentioned first in prerequisites, IIS (Windows web server) configuration is described before Apache/NGINX, and only Azure PowerShell is shown for uploading certificates to Application Gateway (with no Azure CLI or ARM template example). The PowerShell code uses Windows-style paths, and there is no explicit Linux/Unix shell or CLI example for the Azure upload step.
Recommendations
- Provide Azure CLI examples alongside Azure PowerShell for uploading certificates to Application Gateway, using Linux-style paths where appropriate.
- List Linux and Windows equally in prerequisites, or mention Linux first when discussing OpenSSL, as it is more native to Linux.
- Include Linux/Unix shell commands or scripts for certificate upload and management, not just PowerShell.
- When discussing web server configuration, alternate the order (e.g., present Apache or NGINX before IIS, or group them without preference).
- Clarify that all steps are cross-platform unless otherwise noted, and provide any OS-specific instructions as needed.
- Where file paths are shown, include both Windows and Linux path examples.
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
Summary
The documentation page demonstrates a Windows bias by providing a PowerShell-based tutorial link as the only concrete example for creating an autoscaling, zone-redundant Application Gateway. There are no equivalent CLI or Linux-native instructions referenced, and the only tool-specific guidance is for Azure PowerShell, which is more commonly used in Windows environments.
Recommendations
- Add links to equivalent tutorials using Azure CLI, which is cross-platform and widely used on Linux and macOS.
- When referencing tool-based guides, mention both Azure PowerShell and Azure CLI options, ideally listing the CLI option first or alongside PowerShell.
- Ensure that Linux and macOS users are explicitly supported in all example workflows and next steps.
- Consider including Bash shell script examples or references where appropriate.
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 instructions and tools (winget, PowerShell) are presented before Linux equivalents. The Windows installation method is described in more detail, and the use of Windows-specific package managers is highlighted. However, Linux instructions are present and functional, and most command-line examples are cross-platform (Azure CLI, Bash, Helm, kubectl).
Recommendations
- Present Linux and Windows installation instructions in parallel tabs or sections, giving equal prominence to both platforms.
- Provide explicit Bash (Linux/macOS) and PowerShell (Windows) command examples where relevant, especially for Helm and other tooling.
- Avoid listing Windows tools (e.g., winget) before Linux equivalents; consider alphabetical or platform-neutral ordering.
- Where possible, mention that Azure CLI and Helm commands work identically on both Windows and Linux, and clarify any platform-specific prerequisites.
- Ensure that any references to Windows tools are matched with equivalent Linux package manager commands (e.g., apt, yum, snap) for parity.
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 primarily a Windows tool. There is no mention of Linux or cross-platform alternatives (such as Azure CLI or ARM templates), and no Linux-specific guidance is provided. This implicitly prioritizes Windows/PowerShell users and may hinder Linux users seeking parity.
Recommendations
- Include links to equivalent tutorials using Azure CLI, which is cross-platform and widely used on Linux.
- Mention both PowerShell and CLI options when referencing configuration steps or next actions.
- Add examples or references for ARM/Bicep templates for users who prefer declarative infrastructure.
- Explicitly state that the features can be configured from any platform, and provide parity in documentation structure for both Windows and Linux users.
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 workflows (e.g., 'PowerShell', 'Listeners blade in portal') as primary means for configuration and inspection. There are no explicit Linux or cross-platform command-line examples (such as Azure CLI on Bash), and the only configuration walkthrough linked is for PowerShell. Linux users are not given parity in instructions or examples.
Recommendations
- Provide Azure CLI examples using Bash or cross-platform shells alongside PowerShell examples for all configuration steps.
- Include explicit references and links to Linux/macOS-compatible instructions and tools, not just PowerShell or the Azure Portal.
- When mentioning command-line interfaces, list Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
- Ensure that all walkthroughs (such as 'Configure TLS policy versions and cipher suites') have both PowerShell and CLI (Bash) versions, and link to both.
- Clarify in notes and tables that all operations can be performed from any OS using Azure CLI, not just from Windows/PowerShell.
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 PowerShell-based command-line examples for configuring Application Gateway with Key Vault certificates, with no equivalent Azure CLI or Bash/Linux shell examples. The guidance and automation steps are presented primarily in the context of PowerShell, which is most familiar to Windows users. References to scripting and automation tools (e.g., 'PowerShell steps', 'use PowerShell', 'Get-Az...') are made before or instead of cross-platform alternatives. There is no mention of Linux-specific workflows or examples, and the 'Next steps' section links only to a PowerShell-based guide.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell scripts, as Azure CLI is cross-platform and widely used on Linux and macOS.
- When referencing scripting or automation, mention both PowerShell and Azure CLI (or Bash) options, and consider presenting CLI examples first or side-by-side.
- Include explicit Linux/macOS shell command examples where relevant, especially for certificate management and deployment.
- Link to both PowerShell and Azure CLI documentation in the 'Next steps' section.
- Avoid language that assumes PowerShell is the default or only automation tool; instead, use neutral phrasing such as 'using PowerShell or Azure CLI'.