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 276-300 of 981 flagged pages
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
Summary
The documentation page demonstrates a Windows bias primarily through the exclusive use of Azure PowerShell commands and references to PowerShell scripts for migration, without providing equivalent Azure CLI (cross-platform) or Bash examples. The registration and unregistration instructions for the Basic SKU preview are shown only with PowerShell cmdlets, and migration guidance points to a PowerShell script. There are no Linux-specific or cross-platform command-line examples, and the CLI instructions shown are actually PowerShell commands, not Azure CLI/Bash, despite being labeled as 'azurecli-interactive'.
Recommendations
- Provide Azure CLI (az) command examples alongside or before PowerShell examples for all management tasks, including registration, unregistration, and migration.
- Clarify and correct code block labelsβensure 'azurecli-interactive' blocks contain actual Azure CLI commands, not PowerShell.
- Reference Bash or shell scripting alternatives for migration tasks, or provide links to cross-platform tools/scripts.
- Explicitly state that all features and management operations are available and supported on Linux/macOS as well as Windows, where applicable.
- Where PowerShell scripts are referenced (e.g., for migration), provide or link to equivalent Azure CLI or Bash scripts, or note if none exist.
Create Pull Request
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/tutorial-autoscale-ps.md
.../articles/application-gateway/tutorial-autoscale-ps.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All examples use Azure PowerShell cmdlets and Windows-specific tools (such as New-SelfSignedCertificate and Export-PfxCertificate), with no mention of Bash, Azure CLI, or Linux-compatible alternatives. The instructions assume a Windows environment (e.g., file paths like c:\appgwcert.pfx), and there are no parallel Linux or cross-platform examples provided.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside PowerShell for each step, as Azure CLI is cross-platform and widely used on Linux and macOS.
- For certificate creation, include Linux/macOS instructions using OpenSSL to generate self-signed certificates and export to .pfx format.
- Use platform-agnostic file paths (e.g., ./appgwcert.pfx) or clarify when a path is OS-specific.
- Explicitly state that the tutorial can be followed from Windows, Linux, or macOS, and provide prerequisites and setup instructions for each OS.
- Where PowerShell is required, mention PowerShell Core (pwsh), which is cross-platform, and provide guidance for installing and running it on Linux/macOS.
- Add a section or callouts for users who prefer Bash scripting or other shells, referencing relevant documentation.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/application-gateway-for-containers-metrics.md
...ntainers/application-gateway-for-containers-metrics.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (a web UI, but often associated with Windows-centric workflows), and in the 'Next steps' section, it only provides guidance for integrating with Power BI, a Microsoft Windows tool. There are no examples or references to Linux-native tools, CLI workflows, or open-source alternatives for monitoring or visualizing metrics. No Linux command-line (e.g., Azure CLI, Bash, or Kusto Query Language via CLI) examples are provided, and the documentation does not mention or prioritize Linux or cross-platform approaches.
Recommendations
- Include examples using Azure CLI and Bash scripts to retrieve and visualize metrics, ensuring parity with portal-based instructions.
- Add references and examples for open-source or cross-platform visualization tools (e.g., Grafana) that can consume Azure Monitor metrics.
- Provide Kusto Query Language (KQL) examples that can be run from the Azure Cloud Shell (which is cross-platform) or from Linux terminals.
- In the 'Next steps' section, include links to documentation on integrating Azure Monitor with non-Windows tools and environments.
- Explicitly mention that the Azure portal and Azure Monitor are accessible from any OS, and provide screenshots or instructions from a Linux perspective where relevant.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/diagnostics.md
...cles/application-gateway/for-containers/diagnostics.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides detailed instructions and a code sample for enabling diagnostic logs using PowerShell, a Windows-centric tool, but does not provide equivalent examples for Linux users (e.g., Azure CLI, Bash, or ARM templates). The only automation example is in PowerShell, and there is no mention of Linux-native tools or cross-platform alternatives. The order of presentation also places the PowerShell example before any mention of Azure CLI or Bash, which are more commonly used on Linux.
Recommendations
- Add equivalent Azure CLI (az) examples for enabling diagnostic logs, as Azure CLI is cross-platform and widely used on Linux.
- Include Bash script samples or ARM/Bicep template snippets to demonstrate automation for Linux and cross-platform users.
- Explicitly mention that PowerShell is just one way to automate configuration, and provide links or references to Linux-friendly tools.
- Reorder the automation sections to present Azure CLI or cross-platform methods before or alongside PowerShell, to avoid implying Windows-first workflows.
- Consider adding a table comparing methods (Portal, PowerShell, Azure CLI, ARM/Bicep) for enabling diagnostic logs, with links to each.
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
Summary
The documentation page demonstrates a Windows/Powershell bias by providing migration and registration/unregistration examples exclusively using Azure PowerShell commands, with no equivalent Bash or Linux-native Azure CLI examples. The only automation script referenced is a PowerShell script, and there is no mention of Linux tools or cross-platform scripting approaches. This may disadvantage Linux users or those preferring Bash scripting.
Recommendations
- Provide equivalent Azure CLI (bash/shell) command examples alongside PowerShell commands for all operations, especially for migration and feature registration/unregistration.
- Reference both PowerShell and Bash/CLI scripts where automation is discussed, or clarify if scripts are cross-platform.
- Explicitly mention cross-platform compatibility of tools and scripts, or provide links to Linux/macOS instructions where available.
- Ensure that tutorials and 'Next steps' sections include links to both PowerShell and CLI-based guides.
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 page demonstrates a Windows bias by consistently presenting Azure PowerShell instructions before Azure CLI, referencing PowerShell-specific cmdlets (e.g., Get-AzProviderFeature) even in CLI sections, and omitting explicit Linux shell examples or guidance. The step-by-step instructions and screenshots are tailored to the Azure Portal UI, which is platform-agnostic but often more familiar to Windows users. There are no bash or Linux-specific command-line examples, nor is there mention of Linux-native tooling or scripting approaches.
Recommendations
- Provide explicit bash/Linux shell examples for Azure CLI commands, including output parsing and scripting patterns.
- Ensure CLI instructions reference platform-appropriate commands for viewing feature registration status (e.g., 'az feature list' or 'az feature show'), rather than PowerShell cmdlets.
- Add notes or examples for Linux users, such as using the Azure CLI in bash, zsh, or other shells, and clarify any differences in command syntax or output formatting.
- Balance the order of examples by presenting CLI instructions before or alongside PowerShell, rather than consistently after.
- Include references to Linux-native automation tools (e.g., Ansible, shell scripts) where relevant, especially in sections discussing deployment automation.
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, with no mention of Bash, Linux, or cross-platform CLI alternatives. The only code examples provided are PowerShell-based, and the 'Next steps' section lists a PowerShell tutorial before mentioning the Azure CLI. There is no explicit guidance or examples for Linux users or Bash scripting, and Windows-centric tools and patterns are assumed throughout.
Recommendations
- Provide equivalent Azure CLI (bash-friendly) examples alongside all PowerShell commands, especially for migration and preview registration.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide Bash syntax where appropriate.
- Ensure that tutorials and 'Next steps' sections list both PowerShell and CLI options equally, or alternate their order to avoid Windows-first bias.
- Where scripts are referenced (such as migration scripts), clarify if cross-platform options exist or provide links to GitHub repositories with both PowerShell and Bash versions.
- Add a note or section for Linux users, highlighting any differences or considerations when using Application Gateway with Linux-based management tools.
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-first bias by presenting Azure PowerShell instructions and terminology before Azure CLI equivalents throughout the feature registration and unregistration sections. There is a heavy reliance on PowerShell examples, and no explicit Linux or Bash shell examples are provided. The CLI examples are present but are not contextualized for Linux users (e.g., no Bash scripting, no mention of shell environments). The documentation assumes familiarity with Windows-centric tools and patterns, and does not address Linux-specific workflows or considerations.
Recommendations
- Alternate the order of PowerShell and CLI instructions, or present CLI (cross-platform) first to avoid Windows-first bias.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide example shell environments where appropriate.
- Include Bash shell script examples for common tasks, especially for steps that are likely to be automated in Linux environments.
- Where screenshots or UI steps are provided, consider including CLI or script-based alternatives for users who prefer or require non-GUI workflows.
- Add a section or callout for Linux users, highlighting any differences or tips for using the Azure CLI or other tools on Linux.
- Ensure that references to tools (e.g., PowerShell, CLI) clarify their cross-platform availability and usage.
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 primarily through the exclusive use of Azure PowerShell commands and references, with no mention or examples of equivalent Bash or Linux-native CLI usage. The PowerShell-based workflow is presented as the default or only method for migration and preview registration tasks. There is also a lack of explicit Linux or cross-platform guidance, and the ordering of tools and tutorials often places PowerShell before Azure CLI or other platform-agnostic options.
Recommendations
- Provide Azure CLI (bash) examples alongside or before PowerShell commands for all operational tasks, such as migration and preview registration.
- Explicitly mention that Azure CLI is cross-platform and supported on Linux/macOS, and provide links to relevant installation and usage guides.
- Where PowerShell is referenced, clarify that it is available on Linux/macOS as well, or provide alternative shell-specific instructions.
- Balance the ordering of tool references (e.g., 'Azure CLI, Azure PowerShell, or Azure portal') to avoid always listing Windows-centric tools first.
- Add a section or note highlighting Linux support and any platform-specific considerations for Application Gateway v2.
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/Windows-centric command examples (e.g., Set-AzContext, Register-AzProviderFeature), referencing the PowerShell Gallery for migration scripts, and not including equivalent Azure CLI (cross-platform) or Bash examples. The 'Next steps' section also prioritizes PowerShell tutorials, and there is no mention of Linux-specific tools or workflows.
Recommendations
- Provide Azure CLI (az) command examples alongside or before PowerShell commands, especially for registration and preview management steps.
- Reference Bash or cross-platform shell usage where appropriate, and clarify that Azure CLI is available on Windows, Linux, and macOS.
- If migration scripts are available only in PowerShell, mention any alternatives for Linux users or provide guidance on running PowerShell Core on Linux.
- Balance tutorial links to include both PowerShell and Azure CLI/Bash walkthroughs.
- Review and update language to avoid implying that PowerShell is the default or only supported automation tool.
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
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting Azure PowerShell instructions and references before Azure CLI in all relevant sections. PowerShell is a Windows-centric tool, and its precedence in the documentation implies a preference for Windows environments. Additionally, there are no explicit Linux shell (bash) examples, and the CLI output examples use PowerShell cmdlets for status checks, even in the CLI section. The use of PowerShell and the ordering of examples may disadvantage Linux users or those who prefer cross-platform tooling.
Recommendations
- Alternate the order of PowerShell and CLI instructions, or present CLI (which is cross-platform) first to improve parity.
- In CLI sections, use only CLI commands for all steps, including status checks (e.g., 'az feature show' instead of 'Get-AzProviderFeature').
- Add explicit bash shell examples where relevant, especially for scripting or automation scenarios.
- Clarify in each section that both PowerShell and CLI are supported on Windows, Linux, and macOS, and provide links to installation guides for both.
- Avoid using PowerShell-specific output or terminology in CLI sections to prevent confusion for 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 primarily through the exclusive use of Azure PowerShell commands and references to the PowerShell Gallery for migration scripts. Azure CLI commands are shown, but only in the context of PowerShell (Set-AzContext, Get-AzProviderFeature, Register-AzProviderFeature), which are PowerShell cmdlets, not cross-platform Azure CLI commands. There are no explicit Linux/bash examples, and the documentation does not mention Linux tools or workflows. The 'Next steps' section also prioritizes PowerShell tutorials over CLI or portal-based workflows.
Recommendations
- Provide equivalent Azure CLI (az) command examples for all PowerShell scripts and registration/unregistration steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
- When referencing scripts or tools (such as migration scripts), clarify if they are available for both PowerShell and Bash/CLI, and provide links or instructions for both.
- In 'Next steps', include tutorials for Azure CLI and the Azure portal, not just PowerShell, and ensure parity in guidance.
- Avoid using PowerShell-specific cmdlets (Set-AzContext, Get-AzProviderFeature, etc.) in sections labeled as 'Azure CLI'; use true Azure CLI commands (az ...).
- Explicitly mention that all features and management tasks can be performed from Linux/macOS environments using Azure CLI or REST APIs, and provide examples where appropriate.
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 tools or cross-platform alternatives (such as Azure CLI or ARM templates), nor are there links to equivalent Linux-focused documentation. This suggests a bias toward Windows and PowerShell users.
Recommendations
- Include links to tutorials or guides that use Azure CLI, which is cross-platform and widely used on Linux and macOS.
- When referencing command-line configuration, provide both PowerShell and Azure CLI (or Bash) examples.
- Ensure that 'Next steps' sections offer parity by including Linux-friendly options alongside Windows/PowerShell instructions.
- Explicitly mention that Application Gateway can be managed from any platform, and provide links to documentation for ARM templates, REST API, or Terraform for infrastructure-as-code scenarios.
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 tasks, with no equivalent Bash or Linux-native CLI examples. The use of 'Set-AzContext', 'Get-AzProviderFeature', and 'Register-AzProviderFeature' in code blocks is PowerShell-specific, and there is no mention of Bash, Linux, or cross-platform CLI usage. Additionally, the tutorial link provided is PowerShell-focused, and there is no explicit guidance for Linux users.
Recommendations
- Provide Azure CLI (bash) examples alongside or before PowerShell examples for all command-line tasks, especially for registration, unregistration, and migration.
- Clarify when commands are cross-platform and when they are PowerShell-specific; if using PowerShell, also show the equivalent Bash/Azure CLI syntax.
- Include links to Linux-focused tutorials or documentation, or at least ensure parity in the 'Next steps' section.
- Avoid assuming PowerShell as the default automation tool; mention both PowerShell and Bash/CLI options in narrative text.
- Where scripts are referenced (such as migration scripts), indicate if they are cross-platform or provide Linux-compatible alternatives.
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 the CLI section), and omitting explicit Linux or Bash shell examples. The use of PowerShell is emphasized, and there are no Linux-specific or cross-platform command-line examples beyond the Azure CLI. Additionally, the documentation does not mention or illustrate Linux tools, shells, or workflows, which may hinder parity for Linux users.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to prioritize cross-platform compatibility.
- Ensure all command-line instructions (including status checks) are shown using both Azure CLI and PowerShell, with CLI output examples using 'az feature show' or 'az feature list' instead of PowerShell cmdlets.
- Add explicit Bash/Linux shell command examples where relevant, especially for scripting or automation scenarios.
- Include notes or sections on how to perform tasks in Linux environments, such as using Bash or other common Linux shells.
- Where screenshots or UI steps are shown, clarify that the Azure portal is platform-agnostic, and provide CLI/automation alternatives for headless or Linux-first environments.
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. There are no Linux or cross-platform command-line examples or references, and the only tooling mentioned is PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Add links to equivalent Azure CLI tutorials or documentation for creating and managing autoscaling, zone-redundant application gateways.
- Include ARM/Bicep template examples for infrastructure-as-code scenarios, which are platform-agnostic.
- In the 'Next steps' section, ensure that both PowerShell and CLI options are presented, ideally with CLI listed first or alongside PowerShell to emphasize cross-platform support.
- Explicitly mention that Azure CLI and ARM/Bicep templates can be used from Linux, macOS, and Windows, to reinforce platform neutrality.
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-specific examples, tools, or guidance, and the only configuration walkthrough linked is for PowerShell. The documentation does not mention Bash, Linux shell, or platform-agnostic instructions, which may disadvantage Linux users.
Recommendations
- Provide equivalent Linux/Bash command-line examples alongside PowerShell, especially for configuration tasks.
- When referencing configuration tools, mention Azure CLI before or alongside PowerShell, as CLI is cross-platform.
- Add links to Linux-focused configuration guides or ensure that the main configuration guide covers both Windows (PowerShell) and Linux (Bash/CLI) workflows.
- Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide sample commands in Bash syntax.
- Avoid referencing only PowerShell in notes and instructions; always include CLI or REST API alternatives where possible.
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 installation instructions (including a PowerShell/winget example) are presented before Linux instructions. The use of 'winget' (a Windows-specific package manager) is highlighted, and the PowerShell example is given more prominence. However, Linux instructions are present and functional, and most CLI examples use cross-platform tools (Azure CLI, Helm, kubectl) in Bash syntax.
Recommendations
- Present Linux and Windows installation instructions in parallel tabs or in the same order (Linux first or alphabetically) to avoid prioritizing Windows.
- Provide equal detail and prominence to both Windows and Linux installation methods for Helm and other tools.
- Include explicit Bash and PowerShell examples for all relevant commands, or clarify that all examples work on both platforms unless otherwise noted.
- Avoid highlighting Windows-specific tools (like winget) before cross-platform or Linux-native alternatives.
- Add a note clarifying that Azure CLI, Helm, and kubectl commands are cross-platform and can be run on Windows, Linux, or MacOS.
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' and .NET requirements. There are no Linux or cross-platform CLI examples (such as Azure CLI or Bash), nor are Linux-friendly tools (like tcpdump, Wireshark, or curl) mentioned. The order of presentation also puts Windows tools and patterns first, with no Linux parity.
Recommendations
- Provide equivalent Azure CLI (az) and/or Bash commands for checking Application Gateway settings alongside PowerShell examples.
- Include Linux-friendly network debugging tools (e.g., tcpdump, Wireshark, curl, or mitmproxy) as alternatives to Fiddler, with basic usage instructions.
- Avoid instructions that are specific to Windows environments (e.g., 'Run as administrator', .NET requirements) or provide Linux/macOS alternatives where applicable.
- Explicitly state that the troubleshooting steps can be performed on any OS, and ensure screenshots or instructions are not exclusively Windows-centric.
- Present cross-platform or Linux examples before or alongside Windows examples to ensure parity.
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, without mentioning or providing examples for cross-platform tools such as Azure CLI or REST API. There are no Linux or Bash examples, and the only automation path described is via PowerShell, which is traditionally associated with Windows environments.
Recommendations
- Include equivalent Azure CLI examples for all migration steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Mention REST API options for migration where applicable, to support automation from any OS.
- Provide Bash script examples alongside PowerShell, or clarify that PowerShell Core is cross-platform if that is the intended usage.
- Explicitly state platform compatibility for all scripts and tools, and offer guidance for Linux/macOS users.
- Add a section or FAQ addressing migration for users on non-Windows platforms, including tool recommendations and sample commands.
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, with no equivalent Azure CLI, Bash, or Linux-oriented instructions. PowerShell is mentioned and used as the primary automation tool, and the 'Next steps' section links exclusively to a PowerShell guide. There are no Linux/Unix shell or cross-platform scripting examples, and the documentation assumes familiarity with Windows-centric tools and workflows.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside PowerShell for all configuration steps, especially for referencing Key Vault secrets and configuring Application Gateway.
- Include Bash shell script examples for Linux users where automation is demonstrated.
- In the 'Next steps' section, add links to guides for Azure CLI and ARM/Bicep templates, not just PowerShell.
- When mentioning tools or automation approaches, present cross-platform options first or in parallel, rather than defaulting to PowerShell.
- Explicitly state that all steps can be performed on Linux/macOS using Azure CLI, and provide references or links to relevant documentation.
- Where screenshots or UI steps are shown, clarify that the Azure portal is cross-platform, and note any OS-specific considerations if relevant.
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
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows tools and patterns (such as IIS and PowerShell) are mentioned before or more prominently than their Linux equivalents. The Azure PowerShell example is provided in detail, while no equivalent Azure CLI (cross-platform) example is given. The instructions for adding the certificate to a web server list IIS first, and the PowerShell section is extensive, reinforcing a Windows-centric approach.
Recommendations
- Provide Azure CLI examples alongside or before Azure PowerShell examples for certificate upload and Application Gateway configuration, as Azure CLI is cross-platform.
- When listing web server configuration instructions, alternate the order (e.g., list Apache or NGINX before IIS, or group them together without preference).
- Include explicit Linux/macOS instructions for tasks like adding the root certificate to the trusted store (e.g., update-ca-certificates on Linux, Keychain Access on macOS).
- Where file paths are shown (e.g., C:\Users\...), include Linux-style paths as well (/home/user/...).
- If referencing Windows-specific tools or articles (like the IIS certificate import guide), provide equivalent Linux resources (e.g., for Apache or NGINX certificate installation).
- Consider a dedicated section or callout for Linux/macOS users where platform-specific steps differ.
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 First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively linking to a PowerShell-based tutorial for creating an autoscaling, zone-redundant Application Gateway. There are no references to Linux CLI (az CLI), Bash, or ARM template examples, and the only automation tool mentioned is Azure PowerShell, which is most commonly used on Windows platforms. This prioritizes Windows tooling and patterns, potentially excluding Linux users or those who prefer cross-platform command-line interfaces.
Recommendations
- Add equivalent examples and tutorials using Azure CLI (az cli), which is cross-platform and widely used on Linux and macOS.
- Provide ARM/Bicep template examples for infrastructure-as-code scenarios, ensuring parity for users who prefer declarative provisioning.
- When listing 'Next steps' or automation options, mention both PowerShell and CLI/Bash options, or provide a neutral, platform-agnostic example first.
- Explicitly state that Azure PowerShell can be used on Linux/macOS, or clarify that other tools are available for non-Windows environments.
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 as the primary method for configuring and retrieving TLS policy details, both in the main text and in the 'Next steps' section. There are no explicit Linux or Bash examples, and the CLI is only mentioned in passing, always after PowerShell. The documentation does not provide parity for Linux users in terms of command-line instructions or tool references.
Recommendations
- Provide explicit Azure CLI (az) command examples alongside or before PowerShell examples for all configuration and retrieval tasks.
- Include Bash/Linux shell command examples where relevant, especially for common administrative operations.
- When referencing documentation for configuration steps, link to both PowerShell and CLI/Bash guides, or create unified guides that show both approaches.
- Avoid mentioning PowerShell first or exclusively; use neutral phrasing such as 'using Azure CLI or PowerShell' and ensure both are equally represented.
- Add a section or callout for Linux/macOS administrators, highlighting any differences or additional steps required.
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 OS-specific command-line examples, but the only 'Next steps' link directs users to a PowerShell-based tutorial, which is Windows-centric. There is no mention of Linux tools, Bash, or cross-platform CLI alternatives, 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 works natively 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.
- Ensure that 'Next steps' and further reading sections offer parity between Windows and Linux users by linking to both PowerShell and CLI/REST documentation.