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 376-400 of 981 flagged pages
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 Application Gateway settings, exclusively recommending Fiddler (a Windows-centric tool) for network debugging, and referencing 'Run as administrator' for installation. There are no Linux or cross-platform alternatives or examples provided for these troubleshooting steps.
Recommendations
- Provide equivalent Azure CLI (az) commands for checking Application Gateway settings, alongside or instead of PowerShell examples.
- Include Linux-friendly network debugging tools such as tcpdump, Wireshark, or mitmproxy, and show basic usage examples.
- When referencing installation steps, avoid Windows-specific instructions like 'Run as administrator' unless also providing Linux/macOS equivalents.
- Mention cross-platform tools and approaches first, or at least in parallel with Windows-specific ones, to ensure parity.
- Clarify that Fiddler is one option and suggest alternatives for non-Windows users.
Create Pull Request
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 by primarily referencing Azure PowerShell scripts and cmdlets for migration and preview registration/unregistration, with no mention of Bash, Linux, or cross-platform CLI alternatives. The Azure CLI examples shown use PowerShell-style commands (Set-AzContext, Register-AzProviderFeature), which are typically associated with PowerShell rather than the cross-platform az CLI. There are no Linux- or Bash-specific instructions or examples, and the PowerShell approach is presented as the default or only method for key operations.
Recommendations
- Provide equivalent Azure CLI (az) commands for all operations currently shown with Azure PowerShell, especially for migration and preview registration/unregistration.
- Clearly distinguish between Azure PowerShell and Azure CLI, and ensure both are represented in code examples.
- Add explicit Bash/Linux shell examples where relevant, and clarify that all operations can be performed from non-Windows platforms.
- When listing tools or methods (e.g., Azure portal, PowerShell, CLI), do not default to PowerShell firstβeither list CLI first or present both together.
- Include a note or section on cross-platform compatibility, reassuring users that all features and scripts are available on Linux and macOS as well as Windows.
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 centered around PowerShell, which is traditionally associated with Windows environments. There are no Linux or cross-platform command-line examples, nor is there guidance for users who may prefer or require non-Windows tooling.
Recommendations
- Provide equivalent Azure CLI (az) examples and scripts for migration tasks, alongside PowerShell.
- Explicitly mention that migration can be performed from Linux/macOS environments using Azure CLI or cross-platform PowerShell Core.
- Include Bash script examples or references for common migration tasks.
- Clarify any limitations or differences when using Linux/macOS versus Windows for migration.
- Add a section or note about cross-platform support and tooling options for users not on Windows.
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 generally provides cross-platform guidance 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 (IIS, PowerShell, Windows file paths) are mentioned before or more prominently than their Linux equivalents; (2) The Azure PowerShell example for uploading certificates is provided, but there is no equivalent Azure CLI (cross-platform) example; (3) The IIS section is listed before Apache and NGINX, and the PowerShell script uses Windows-style file paths.
Recommendations
- Add Azure CLI examples alongside or before Azure PowerShell for certificate upload and configuration, as CLI is cross-platform.
- When referencing web servers, alternate the order (e.g., list Apache or NGINX before IIS, or group them without implied priority).
- Include Linux-style file paths in examples (e.g., /home/user/contoso.cer) or note that file paths should be adapted to the user's OS.
- Explicitly state that all OpenSSL commands work identically on Linux and Windows, and provide any OS-specific caveats if needed.
- Where possible, provide screenshots or instructions for both Windows and Linux environments (e.g., adding root certificates to trusted stores).
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 a PowerShell/winget example) are presented before Linux instructions. The Windows-specific tool 'winget' is highlighted, while the Linux section is less detailed. However, most command-line instructions throughout the document use Azure CLI and Bash-compatible syntax, which is cross-platform. There are no Linux examples missing, but the ordering and detail favor Windows slightly.
Recommendations
- Present Linux and Windows installation instructions for Helm with equal prominence and detail, possibly using side-by-side tabs or presenting Linux first.
- Include explicit Bash and PowerShell equivalents for any command-line examples where differences exist.
- Avoid highlighting Windows-specific tools (like winget) before cross-platform or Linux-native methods; instead, mention both approaches together or in parallel.
- Ensure that all instructions are equally accessible and detailed for both Windows and Linux users, including troubleshooting tips or common issues for both platforms.
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 tools for configuration and management, with PowerShell consistently mentioned first. There are no explicit Linux or Bash examples, and the only configuration walkthrough linked is for PowerShell. The documentation does not provide parity for Linux users or mention Linux-native tools or shell commands.
Recommendations
- Provide explicit Bash/Azure CLI examples alongside or before PowerShell examples for all configuration steps.
- Include links to Linux/Bash-focused configuration guides, not just PowerShell.
- When referencing tools or commands, use cross-platform terminology (e.g., 'Azure CLI or PowerShell'), and ensure both are covered equally.
- Add a 'Platform compatibility' section clarifying that all features are available via both Windows and Linux command-line tools.
- Ensure that all 'Next steps' and example links include both PowerShell and Bash/CLI walkthroughs.
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 (e.g., Azure CLI, ARM templates, or Bicep). This creates a bias toward Windows users and PowerShell-centric workflows, while omitting Linux-preferred tools and examples.
Recommendations
- Add links to equivalent tutorials using Azure CLI, ARM templates, or Bicep for creating autoscaling, zone redundant application gateways.
- When listing 'Next steps', ensure that both PowerShell and CLI (cross-platform) options are presented, ideally with CLI listed first or alongside PowerShell.
- Explicitly mention that Azure CLI and ARM/Bicep templates are supported and provide references or code snippets for these tools.
- Review the documentation for other sections where only PowerShell is referenced and add Linux-friendly alternatives.
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 Application Gateway settings, exclusively referencing the Windows-only Fiddler tool for network debugging, and omitting equivalent Linux command-line or tool instructions. No Linux-native alternatives (such as Azure CLI, curl, tcpdump, or Wireshark) are mentioned, and the order of presentation assumes a Windows environment by default.
Recommendations
- Provide Azure CLI examples (az network application-gateway ...) alongside or instead of PowerShell for cross-platform parity.
- Mention and give examples using Linux-compatible network debugging tools such as tcpdump, Wireshark, or mitmproxy in addition to Fiddler.
- Include instructions for installing and using these tools on Linux/macOS, not just Windows.
- When referencing tools or commands, avoid assuming the user is on Windows; present cross-platform options or note OS-specific steps.
- Ensure screenshots and walkthroughs include at least one example from a Linux or macOS 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 demonstrates a significant Windows bias. PowerShell is the only scripting example provided for configuring Key Vault integration with Application Gateway, with no equivalent Azure CLI (cross-platform) or Bash/Linux shell examples. The narrative and examples prioritize PowerShell and Windows-centric tools, and the 'Next steps' section links only to a PowerShell-based guide. There is no mention of Linux-specific workflows or parity in command-line instructions.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell scripts, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash or shell script snippets where appropriate, especially for deployment automation.
- In sections where PowerShell is referenced, mention Azure CLI as an alternative and provide links to relevant CLI documentation.
- Ensure that 'Next steps' and further reading sections include links to both PowerShell and Azure CLI guides.
- Explicitly state that all operations can be performed from Linux/macOS using Azure CLI or ARM/Bicep templates, and provide examples.
- Review screenshots and UI instructions to ensure they are not Windows-specific, or clarify that the steps are platform-agnostic.
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 by primarily referencing Azure PowerShell scripts and cmdlets for migration and preview registration tasks, without providing equivalent Bash or Linux-native Azure CLI examples. The use of 'Set-AzContext', 'Get-AzProviderFeature', and 'Register-AzProviderFeature' in code blocks is PowerShell-specific, and the only tutorial linked is for PowerShell. There is no mention of Linux or Bash alternatives, and the documentation does not provide parity for users on non-Windows platforms.
Recommendations
- Provide Azure CLI (bash/shell) examples alongside PowerShell commands for all operations, especially for preview registration and migration tasks.
- Explicitly mention that all features and management tasks are available cross-platform, and clarify any exceptions.
- Include links to tutorials and guides that use Azure CLI in Bash or Cloud Shell, not just PowerShell.
- When referencing scripts or tools, note their platform compatibility and provide alternatives where possible.
- Balance references to Azure PowerShell and Azure CLI in both prose and code samples to ensure Linux and macOS users are equally supported.
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 Application Gateway settings, exclusively recommending and illustrating Fiddler (a Windows-centric tool) for network capture, and referencing Windows-specific installation steps (e.g., 'Run as administrator'). There are no Linux or cross-platform alternatives mentioned for either command-line management or network debugging, and Windows tools and patterns are presented first and exclusively.
Recommendations
- Provide equivalent Azure CLI (az network application-gateway backend-http-settings list) or Azure Resource Manager REST API examples for checking Application Gateway settings, which are cross-platform.
- Include examples using Linux-compatible network debugging tools such as tcpdump, Wireshark, or mitmproxy, and provide basic usage instructions for these tools.
- When referencing downloadable tools, mention cross-platform options and clarify which tools are available on which operating systems.
- Avoid Windows-specific installation instructions (like 'Run as administrator') unless also providing Linux/Mac equivalents (e.g., 'use sudo').
- Structure sections so that cross-platform or platform-neutral approaches are presented before or alongside Windows-specific guidance.
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 policy details. There is a lack of Linux/Unix-specific examples or parity in command-line instructions, and PowerShell is mentioned before CLI or REST in several places. The 'Next steps' section links only to a PowerShell-based configuration guide, omitting equivalent Linux/CLI documentation.
Recommendations
- Provide Azure CLI examples alongside or before PowerShell examples for all configuration and inspection tasks, as Azure CLI is cross-platform and widely used on Linux.
- Include explicit Linux/Unix shell command examples (e.g., Bash) where relevant, especially for scripting or automation.
- Ensure all references to configuration guides or 'Next steps' include links to both PowerShell and CLI (and, if available, ARM template or REST API) documentation.
- Avoid language that prioritizes PowerShell or Windows tools (e.g., 'refer to the PowerShell, CLI, REST API or the Listeners blade in portal')βinstead, use a neutral or Linux-first ordering, or group tools by platform.
- Add a section or callout for Linux administrators, highlighting any platform-specific considerations or best practices.
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 a PowerShell/winget example) are presented before Linux instructions. The use of the Windows-specific 'winget' tool is highlighted, and the Windows tab is listed first. However, Linux instructions are present and functional, and most of the CLI examples use cross-platform tools (Azure CLI, Helm, kubectl) with Bash syntax.
Recommendations
- Present Linux and Windows installation instructions in parallel or with Linux first, as Linux is the more common OS for Kubernetes administrators.
- Avoid giving Windows-specific tools (like 'winget') prominence over Linux equivalents; mention both with equal weight.
- Where possible, use cross-platform installation methods (e.g., package managers like apt, yum, or Homebrew) and provide explicit commands for both platforms.
- Ensure that all examples and instructions are clearly marked for their respective platforms, and that neither platform is given preferential placement.
- Consider adding macOS-specific instructions where relevant, as many Kubernetes administrators use macOS.
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 references Azure PowerShell as the only example for creating an autoscaling, zone-redundant application gateway with a reserved virtual IP address. There are no equivalent examples or links for Linux/CLI users, and the only step-by-step tutorial provided is PowerShell-based, which is typically associated with Windows environments. This suggests a Windows-first and PowerShell-heavy bias, with a lack of parity for Linux users who would use Azure CLI or other cross-platform tools.
Recommendations
- Add equivalent Azure CLI (az) examples and tutorials for all PowerShell-based instructions.
- Ensure that links to tutorials or how-to guides include both PowerShell and CLI options, ideally side-by-side.
- When referencing tools or scripts, mention cross-platform options first or equally (e.g., 'using Azure CLI or PowerShell').
- Review all 'Next steps' and related links to ensure Linux users have clear, accessible guidance.
- Consider including Bash script examples where appropriate, especially for automation scenarios.
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 are no references to Linux tools, Bash, or CLI equivalents, and the documentation does not mention cross-platform approaches or parity for Linux users. This suggests a bias towards Windows and PowerShell usage, and a lack of Linux-first or cross-platform guidance.
Recommendations
- Include links to equivalent tutorials for Azure CLI (az), which is cross-platform and commonly used on Linux and macOS.
- Provide example commands or configuration steps using Bash or shell scripting in addition to PowerShell.
- Ensure that all referenced tutorials and guides have Linux-compatible instructions, or clearly indicate platform compatibility.
- Mention both Windows and Linux tools and workflows when describing configuration steps, to ensure parity and inclusivity.
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 examples for configuring Application Gateway with Key Vault certificates, with no equivalent Azure CLI, Bash, or Linux-native instructions. PowerShell is featured as the primary automation tool, and the 'Next steps' section links exclusively to a PowerShell guide. There is no mention or example of cross-platform tools or Linux-first workflows.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell command sequences, especially for certificate reference and managed identity configuration.
- Include Bash shell script examples for common tasks to support Linux users.
- In sections where PowerShell is referenced, mention that Azure CLI is also supported and provide links or inline examples.
- Update the 'Next steps' section to include links to Azure CLI and ARM/Bicep template guides, not just PowerShell.
- Where possible, use neutral, cross-platform language (e.g., 'use your preferred automation tool') and avoid implying PowerShell is the default or only option.
- Consider adding a table or callout comparing PowerShell and CLI commands for key tasks.
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 Linux/Unix environments, Bash, Azure CLI, or cross-platform tooling. All migration automation is described in terms of PowerShell, which is traditionally associated with Windows, and there is no guidance for users on non-Windows platforms.
Recommendations
- Provide equivalent Azure CLI (az) commands and scripts for migration tasks, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell Core is available cross-platform, if PowerShell must be used, and provide instructions for installing it on Linux/macOS.
- Include Bash script examples or references for common migration steps.
- Add a section or note clarifying support and best practices for users on Linux/macOS environments.
- Ensure that all tooling references (scripts, automation) are presented in a platform-neutral way, or provide parallel instructions for both Windows and 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 shows some Windows bias, particularly in the sections related to uploading certificates to Application Gateway and configuring web servers. Azure PowerShell (a Windows-centric tool) is featured with detailed sample code, while equivalent Azure CLI (cross-platform) instructions are missing. Windows tools and patterns (such as referencing IIS and the Windows hosts file) are mentioned first or exclusively in some places. There is also a lack of explicit Linux-oriented examples for some steps, such as uploading certificates using Azure CLI or configuring trusted root certificates on Linux systems.
Recommendations
- Provide Azure CLI examples alongside or before Azure PowerShell for certificate upload and Application Gateway configuration, as Azure CLI is cross-platform.
- Include explicit instructions or links for adding root certificates to trusted stores on Linux (e.g., update-ca-certificates on Ubuntu) as well as Windows.
- When referencing web server configuration, balance IIS (Windows) with Apache/NGINX (Linux) by giving equal prominence and detail.
- When mentioning editing the hosts file, include Linux/MacOS paths (e.g., /etc/hosts) and instructions, not just Windows.
- Review the order of tool and platform mentions to avoid always listing Windows first.
- Add notes or examples for Linux users wherever platform-specific steps are required.
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 tutorial is heavily biased toward Windows and PowerShell usage. All examples and instructions are provided exclusively using Azure PowerShell cmdlets and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate). There are no equivalent instructions or examples for Linux or cross-platform environments (such as Azure CLI or OpenSSL for certificate creation). The documentation assumes the user is running a local administrative PowerShell session, which is not the default on Linux/macOS, and does not mention or link to Linux-compatible alternatives.
Recommendations
- Provide parallel instructions and code examples using Azure CLI (az) for all resource creation and configuration steps.
- Include Linux/macOS-compatible methods for certificate creation, such as using OpenSSL, and show how to export certificates in the required format.
- Explicitly state that the tutorial is Windows/PowerShell-specific, or better, restructure it to be cross-platform by default.
- Add notes or sections for users on Linux/macOS, including how to install and use Azure CLI and how to perform each step in a non-Windows environment.
- Where Windows-specific tools or paths are mentioned (e.g., cert:\localmachine\my, c:\appgwcert.pfx), provide Linux/macOS equivalents or clarify the differences.
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 more prominently than Linux equivalents. For example, it directs users to PowerShell-based configuration guides, mentions PowerShell before CLI or REST, and omits explicit Linux/Unix shell or scripting examples. There are no Linux-specific instructions or parity in command-line examples, and the 'Next steps' section links only to a PowerShell-based configuration guide.
Recommendations
- Provide equivalent Linux/Unix shell (bash/az CLI) examples alongside or before PowerShell examples.
- Ensure that configuration steps are documented for both PowerShell and Azure CLI, with clear parity and equal prominence.
- Update 'Next steps' to include links to both PowerShell and CLI (az) configuration guides.
- Wherever PowerShell is mentioned, also mention the corresponding CLI or REST API approach, and provide direct links to those guides.
- Avoid implying that PowerShell is the primary or only supported method for configuration; clarify that both Windows and Linux users are supported equally.
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 Application Gateway settings, exclusively recommending Fiddler (a Windows-centric tool) for network debugging, and referencing Windows installation patterns (e.g., 'Run as administrator'). There are no Linux or cross-platform CLI examples, nor are Linux-friendly tools (such as tcpdump, curl, or Wireshark) mentioned. The guidance assumes a Windows environment and does not address Linux users' needs.
Recommendations
- Provide Azure CLI and/or Azure Resource Manager (ARM) template examples for checking Application Gateway settings, as these are cross-platform and work on Linux, macOS, and Windows.
- Include Linux-friendly network debugging tools such as tcpdump, Wireshark, or curl, and provide example commands for capturing and analyzing HTTP(S) traffic on Linux.
- When referencing installation steps, include Linux equivalents (e.g., using package managers or running as root/sudo).
- Explicitly state that Fiddler is just one option and suggest alternatives for non-Windows users.
- Ensure that screenshots and walkthroughs are not exclusively based on Windows UI/tools, or provide parallel Linux examples where applicable.
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 Windows bias by providing only Azure PowerShell examples for critical configuration steps, referencing PowerShell before (or instead of) cross-platform tools like Azure CLI, and omitting Linux-specific or cross-platform command-line examples. The 'Next steps' section also directs users exclusively to a PowerShell-based guide, reinforcing the Windows-centric approach. There are no CLI, Bash, or Linux-native instructions, which may hinder Linux users or those preferring cross-platform tooling.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, especially for referencing Key Vault secrets and configuring Application Gateway listeners.
- When listing tools or approaches, mention Azure CLI and ARM/Bicep templates alongside PowerShell, and avoid presenting PowerShell as the primary or sole method.
- Include Bash shell examples or notes for Linux/macOS users where applicable.
- Update the 'Next steps' section to include links to CLI-based and ARM/Bicep-based guides, not just PowerShell.
- Where screenshots or UI instructions are given, clarify that the steps are platform-agnostic or provide notes for Linux users if there are differences.
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 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 Azure CLI usage, and the documentation implicitly assumes a Windows/PowerShell workflow.
Recommendations
- Add links to equivalent tutorials using Azure CLI (az), which is cross-platform and commonly used on Linux.
- Include explicit examples or references for configuring Application Gateway redirects using Bash or Linux environments.
- Ensure that 'Next steps' sections offer both PowerShell and Azure CLI (or ARM template) options, with neither being prioritized over the other.
- Mention that Application Gateway can be managed from any OS and provide guidance for users on Linux or macOS.
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 command-line examples, but the only 'Next steps' link points to a PowerShell-based tutorial, which is Windows-centric. There are no references to Linux tools, Bash, or cross-platform CLI usage. This suggests a bias towards Windows and PowerShell, with Linux users left without clear guidance.
Recommendations
- Add links to equivalent tutorials using Azure CLI (az), which is cross-platform and commonly used on Linux.
- Include Bash or shell script examples alongside PowerShell where command-line configuration is discussed.
- Ensure that 'Next steps' and further reading sections provide parity for both Windows and Linux users.
- Explicitly mention that Application Gateway can be managed from any OS using Azure CLI or REST API, and provide documentation links.
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 Application Gateway settings, exclusively recommending Fiddler (a Windows-centric tool) for network debugging, and referencing 'Run as administrator' for setup. There are no Linux or cross-platform alternatives or examples provided for these steps.
Recommendations
- Provide equivalent Azure CLI (az) and/or Azure Resource Manager (ARM) template examples for checking and configuring Application Gateway settings, which are cross-platform.
- Include Linux-friendly network debugging tools such as tcpdump, Wireshark, or mitmproxy, with example usage for capturing and analyzing HTTP/HTTPS traffic.
- When referencing setup steps, avoid Windows-specific instructions like 'Run as administrator' unless also providing the Linux/macOS equivalent.
- Explicitly mention that Fiddler is one option and suggest alternatives for users on Linux or macOS.
- Ensure screenshots and walkthroughs are not exclusively from Windows environments; include examples from other platforms where possible.