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 851-875 of 981 flagged pages
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/private-link-configure.md
...articles/application-gateway/private-link-configure.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents configuration options in the order: Azure portal, Azure PowerShell, and then Azure CLI. The PowerShell section is more detailed, with extensive step-by-step scripts and a dedicated cmdlet reference, while the Azure CLI section is less detailed and lacks a similar command reference list. There are no Linux-specific shell (e.g., Bash) examples, and the CLI section is not as comprehensive as the PowerShell section. This ordering and depth may implicitly prioritize Windows/PowerShell users.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to avoid implying a Windows-first workflow.
- Ensure parity in detail and completeness between PowerShell and Azure CLI sections, including providing a CLI command reference list similar to the PowerShell cmdlet reference.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and consider adding Bash shell snippets where appropriate.
- Where possible, include troubleshooting or usage notes relevant to Linux environments (e.g., file path differences, shell quoting).
- Review language to ensure it does not assume a Windows environment or PowerShell familiarity.
Create Pull Request
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Azure PowerShell examples before Azure CLI examples in all relevant sections, and references to PowerShell cmdlets are repeated even in CLI sections. This ordering and emphasis can be perceived as a Windows-first and PowerShell-heavy bias, as Linux users are more likely to use Azure CLI or Bash. However, the documentation does provide Azure CLI examples and does not exclusively use Windows tools.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first in some sections to better reflect cross-platform usage.
- In CLI sections, avoid referencing PowerShell cmdlets (e.g., for viewing registration status, use 'az feature show' instead of 'Get-AzProviderFeature').
- Explicitly mention that both PowerShell and CLI are cross-platform, and provide Bash script examples where relevant.
- Add a short note or table at the beginning clarifying that all operations can be performed on Windows, Linux, or macOS, and link to platform-specific installation guides for Azure CLI and PowerShell.
- Where possible, include ARM/Bicep/Terraform examples alongside imperative commands to further increase platform neutrality.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents Azure PowerShell instructions before Azure CLI in all code tabbed sections, and references PowerShell-specific cmdlets (e.g., Get-AzProviderFeature) for status checks, even in the CLI sections. While Azure CLI is included, there is a subtle prioritization of Windows/PowerShell workflows, which may suggest a Windows-centric approach. No explicit Linux-only tools or examples are provided, and the CLI examples could be more clearly tailored for Linux environments.
Recommendations
- Alternate the order of PowerShell and CLI tabs, or present CLI first to balance platform representation.
- In CLI sections, use CLI-native commands for all steps (e.g., use 'az feature show' instead of referencing PowerShell cmdlets for status checks).
- Explicitly mention that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
- Where possible, include screenshots or terminal output from Linux environments to reinforce cross-platform applicability.
- Add a brief note or section highlighting parity between PowerShell and CLI, and direct Linux users to CLI as the preferred tool.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/redirect-overview.md
...main/articles/application-gateway/redirect-overview.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page does not provide any OS-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 cross-platform CLI usage, and no parity in example links or guidance for non-Windows users.
Recommendations
- Include links to equivalent tutorials using Azure CLI (az), which is cross-platform and commonly used on Linux and macOS.
- When referencing command-line configuration, provide both PowerShell and Bash/Azure CLI examples side-by-side.
- Ensure that 'Next steps' and other guidance sections offer parity for Linux users, not just Windows/PowerShell users.
- Explicitly mention that configuration can be performed using Azure CLI, ARM templates, or the Azure portal, and provide links to those resources.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/private-link-configure.md
...articles/application-gateway/private-link-configure.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents configuration options in the order: Azure portal, Azure PowerShell, and then Azure CLI. The PowerShell section is detailed and comes before the CLI section, which may suggest a Windows-first or PowerShell-preferred workflow. There are no Linux-specific examples, nor are cross-platform shell examples (e.g., Bash) provided. However, the CLI section does provide parity in steps, and the CLI is cross-platform, but the ordering and prominence of PowerShell may indicate a subtle Windows bias.
Recommendations
- Alternate the order of PowerShell and CLI sections, or present CLI before PowerShell to avoid implying a Windows-first workflow.
- Explicitly state that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Where possible, provide Bash shell script examples or mention Linux/macOS terminal usage for CLI commands.
- Add a note or section for Linux users, highlighting any OS-specific considerations or confirming there are none.
- Ensure that references to prerequisites and tooling do not assume a Windows environment (e.g., avoid only mentioning PowerShell installation).
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/private-link-configure.md
...articles/application-gateway/private-link-configure.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents configuration options in the order: Azure portal, Azure PowerShell, and then Azure CLI. The PowerShell section is more detailed, with extensive step-by-step scripts and a dedicated cmdlet reference list, while the Azure CLI section is less detailed and lacks equivalent depth. There are no Linux-specific shell (bash) examples or explicit mention of Linux environments, and the CLI section is presented last, after the Windows-centric PowerShell section.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform and preferred by many Linux users.
- Ensure parity in detail and explanation between PowerShell and CLI sections, including step-by-step breakdowns and command references for CLI.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and consider including bash shell scripting examples where appropriate.
- Add a note or section for Linux administrators, highlighting any OS-specific considerations or best practices.
- Avoid implying PowerShell is the primary or default automation tool by balancing the order and depth of CLI and PowerShell content.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/redirect-overview.md
...main/articles/application-gateway/redirect-overview.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page does not provide any OS-specific command-line examples, but the only 'Next steps' link points to a PowerShell-based tutorial, which is typically associated with Windows environments. There is no mention of Linux tools, Bash, or cross-platform CLI options, and no Linux-specific guidance is provided.
Recommendations
- Include links to equivalent tutorials using Azure CLI (az), which is cross-platform and commonly used on Linux and macOS.
- Add explicit mention of cross-platform configuration options, such as using Azure Portal, Azure CLI, or ARM templates, to ensure Linux users are supported.
- If PowerShell is referenced, clarify that Azure PowerShell is available on Linux and macOS, or provide Bash/Azure CLI alternatives alongside PowerShell examples.
- Ensure that future documentation and 'Next steps' sections offer parity between Windows/PowerShell and Linux/Azure CLI approaches.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/private-link-configure.md
...articles/application-gateway/private-link-configure.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents configuration options in the order: Azure portal, Azure PowerShell, and then Azure CLI. The PowerShell section is more detailed, with extensive example scripts and a dedicated cmdlet reference, while the Azure CLI section is less detailed and lacks a similar command reference. There are no Linux-specific shell examples (e.g., Bash), and the CLI examples are not explicitly shown in a Linux context. There is no mention of Linux tools or workflows, and the documentation implicitly assumes familiarity with Windows-centric tools (PowerShell) by providing them before CLI.
Recommendations
- Present Azure CLI examples before PowerShell, or provide both in parallel tabs to avoid implying a Windows-first workflow.
- Expand the Azure CLI section to include a comprehensive command reference similar to the PowerShell cmdlet reference.
- Add explicit Bash/Linux shell examples or notes clarifying that Azure CLI commands work cross-platform, including on Linux and macOS.
- Where possible, mention that Azure CLI is the recommended cross-platform tool for scripting and automation, especially for Linux users.
- Ensure parity in detail and troubleshooting notes between PowerShell and CLI sections.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/private-link-configure.md
...articles/application-gateway/private-link-configure.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents configuration options in the order: Azure portal, Azure PowerShell, and then Azure CLI. The PowerShell section is detailed and comes before the CLI section, which can be interpreted as a Windows-first and PowerShell-heavy bias. There are no explicit Linux or Bash-specific examples, and the CLI section, while cross-platform, is presented after PowerShell. No Windows-only tools are mentioned, but the ordering and depth of PowerShell coverage may suggest a preference for Windows environments.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to signal equal support for Linux and cross-platform users.
- Add explicit Bash/Linux shell example blocks where relevant, especially for scripting scenarios.
- Clarify in the introduction that Azure CLI is fully supported on Linux, macOS, and Windows.
- Ensure parity in detail and completeness between PowerShell and CLI sections.
- Consider adding a table comparing PowerShell and CLI commands for each step.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-listeners.md
...rticles/application-gateway/configuration-listeners.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a PowerShell example for enabling HTTP/2 support but does not include equivalent CLI or Linux-native examples (such as Azure CLI or ARM template snippets). There are no references to Windows-specific tools, but the exclusive use of PowerShell for code snippets and lack of Linux/CLI parity may disadvantage users on non-Windows platforms.
Recommendations
- Provide Azure CLI examples alongside PowerShell snippets for all configuration tasks, especially for enabling HTTP/2 support.
- Include ARM template or Bicep examples where applicable to ensure cross-platform automation parity.
- Explicitly mention that all configuration steps can be performed from any OS using the Azure CLI, and provide links to relevant CLI documentation.
- Review the documentation for other sections where only PowerShell is used and add Linux-friendly alternatives.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configure-alerts-with-templates.md
...application-gateway/configure-alerts-with-templates.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page references a procedure link that prioritizes CLI, PowerShell, and ARM template usage, but does not provide explicit Linux or cross-platform command-line examples. The 'Deploy to Azure' button leads to the Azure Portal, which is platform-agnostic, but the only procedural link mentions PowerShell before CLI and does not clarify Linux compatibility. There are no Linux-specific instructions or examples, and no mention of Bash or cross-platform scripting.
Recommendations
- Explicitly provide both Azure CLI (bash) and PowerShell examples for creating and managing alert rules, ensuring Linux users have clear, native instructions.
- In procedural links and references, mention Azure CLI (bash) before or alongside PowerShell to avoid the appearance of Windows-first bias.
- Add a section or note clarifying that all ARM template deployments and Azure CLI commands are fully supported on Linux, macOS, and Windows.
- Where possible, include screenshots or walkthroughs using the Azure CLI in a Linux terminal environment.
- Audit linked documentation to ensure Linux parity in all referenced procedures.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-overview.md
...articles/application-gateway/configuration-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page lists PowerShell (a Windows-centric tool) before Azure CLI in the 'Next steps' section, suggesting a preference for Windows tooling. No Linux-specific examples or tools are highlighted, and PowerShell is mentioned before the more cross-platform Azure CLI.
Recommendations
- List Azure CLI before PowerShell in the 'Next steps' section, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that both PowerShell and Azure CLI are available on Windows, Linux, and macOS, to avoid implying a Windows-only workflow.
- Where possible, provide example commands for both PowerShell and Azure CLI in relevant sections, or link to both sets of instructions equally.
- Consider adding a note or section highlighting Linux compatibility and common Linux tools for managing Azure resources.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-listeners.md
...rticles/application-gateway/configuration-listeners.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a PowerShell example for enabling HTTP/2 support but does not include equivalent Azure CLI or ARM template examples, which are more commonly used on Linux and cross-platform environments. No Linux-specific tools or command-line examples are mentioned, and the only automation example is Windows-centric.
Recommendations
- Add Azure CLI examples alongside PowerShell for all configuration steps, especially for enabling HTTP/2 support.
- Include ARM/Bicep template snippets for declarative configuration, which are platform-agnostic.
- Explicitly mention that all features are available via Azure CLI and portal, and provide links or examples.
- Where PowerShell is used, provide a note or tabbed code blocks to show equivalent commands for Linux/macOS users.
- Review for any other sections where only Windows tooling is referenced and ensure Linux parity.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-request-routing-rules.md
...ication-gateway/configuration-request-routing-rules.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation references both PowerShell and Azure CLI for configuration tasks, but PowerShell (a Windows-centric tool) is consistently mentioned before Azure CLI (cross-platform) in all relevant links. There are no Linux-specific examples or tools, and the ordering of examples and links subtly prioritizes Windows/PowerShell usage.
Recommendations
- Alternate the order of PowerShell and Azure CLI references so that CLI is sometimes mentioned first, or list them alphabetically to avoid perceived prioritization.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Wherever possible, provide example commands for both PowerShell and Azure CLI side by side.
- Consider adding a short section or note for Linux users, clarifying that all CLI instructions are fully supported on Linux.
- If relevant, include Bash shell examples or references to Linux-native tools/utilities.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configuration-overview.md
...articles/application-gateway/configuration-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page lists PowerShell (a Windows-centric tool) before Azure CLI in the 'Next steps' section, suggesting a Windows-first approach. While both PowerShell and Azure CLI are mentioned, there is an implicit prioritization of Windows tooling. No explicit Linux examples or Linux-specific tools are highlighted.
Recommendations
- List Azure CLI before PowerShell in the 'Next steps' section to avoid implying Windows-first bias, as Azure CLI is cross-platform.
- Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, and provide links to installation guides for both.
- Add a note or section highlighting cross-platform support, reassuring Linux and macOS users that all configuration steps can be performed on their systems.
- Where possible, provide example commands for both Azure CLI and PowerShell in the main body, not just in linked articles.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/configure-alerts-with-templates.md
...application-gateway/configure-alerts-with-templates.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page references the procedure to use ARM templates by linking to a guide that lists 'CLI, PowerShell, ARM' in its URL and description, but does not provide explicit Linux (Bash/Azure CLI) examples or instructions on this page. The only actionable deployment method shown is the 'Deploy to Azure' button, which opens the Azure Portal, a web-based tool, but there is no mention or example of how to deploy using cross-platform tools like Azure CLI from Linux/macOS. This may lead Linux users to feel unsupported or unclear about non-Windows deployment options.
Recommendations
- Add explicit Azure CLI (Bash) examples for deploying the ARM templates, suitable for Linux/macOS users.
- Mention that ARM templates can be deployed using cross-platform tools such as Azure CLI, and provide a sample command.
- Ensure that references to procedures or guides do not prioritize PowerShell or Windows tools in their naming or ordering.
- If linking to external guides, clarify which steps are cross-platform and which are Windows-specific.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/ingress-controller-migration.md
...es/application-gateway/ingress-controller-migration.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page primarily uses Azure CLI commands and references the Azure Portal for all examples and instructions. While Azure CLI is cross-platform, there are no explicit Linux shell or script examples, nor any mention of Linux-specific tools or workflows. The documentation assumes use of the Azure Portal (a web UI) and CLI, both of which are accessible from Windows, macOS, and Linux, but does not provide parity examples for Linux-native environments or mention Linux-specific considerations. There is also no mention of PowerShell, but the absence of Linux-specific examples or references constitutes a subtle Windows/Portal bias.
Recommendations
- Include explicit Linux shell (bash) examples where relevant, especially for scripting or automation.
- Mention that Azure CLI commands work on Linux, macOS, and Windows, and provide sample commands for common Linux shells.
- If referencing the Azure Portal, clarify that it is web-based and platform-agnostic, but also provide CLI-only workflows for users who prefer terminal-based management.
- Add troubleshooting or migration notes for users running AKS clusters on Linux-based systems, if applicable.
- Consider including Helm command examples for uninstalling AGIC, as Helm is often used in Linux environments.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/how-to-tcp-tls-proxy.md
...n/articles/application-gateway/how-to-tcp-tls-proxy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing only Windows-based examples for the SQL Server VM (specifically 'SQL Server 2022 Developer on Windows Server 2022') and by instructing users to use SQL Server Management Studio, a Windows-only tool, for connectivity testing. There are no Linux-based deployment or client examples, nor are cross-platform tools mentioned.
Recommendations
- Include instructions and screenshots for deploying a SQL Server VM on Linux (e.g., Ubuntu or Red Hat) as an alternative to Windows.
- Provide examples for connecting to the SQL Server using cross-platform tools such as Azure Data Studio, sqlcmd, or other CLI/database clients available on Linux and macOS.
- Explicitly mention that the process is similar on Linux and provide any Linux-specific configuration notes (e.g., firewall, authentication).
- Wherever client tools are referenced, list both Windows and Linux options, and avoid assuming the user is on a Windows machine.
- Consider including bash/CLI commands for relevant steps (e.g., using Azure CLI to create resources) alongside portal instructions.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/multiple-site-overview.md
...articles/application-gateway/multiple-site-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a mild Windows bias by referencing Azure PowerShell before Azure CLI in both instructional text and example links. PowerShell-specific instructions are provided with more detail, and the PowerShell tutorial is consistently mentioned before the CLI equivalent. There are no explicit Linux/Windows tool differences in Azure CLI or PowerShell, but the ordering and emphasis may suggest a preference for Windows-centric tooling.
Recommendations
- Alternate the order of Azure CLI and Azure PowerShell references throughout the documentation to avoid implying a preference.
- Provide equal detail and prominence to both Azure CLI and PowerShell instructions and examples.
- Explicitly mention that both Azure CLI and PowerShell are cross-platform, and suitable for use on Windows, Linux, and macOS.
- Consider including Bash or shell script examples where appropriate, especially for tasks that can be performed outside of Azure CLI/PowerShell.
- Add a note or section clarifying that all features described are accessible from both Windows and Linux environments.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-terraform.md
...articles/application-gateway/quick-create-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by only including the creation of an Azure Windows Virtual Machine in the checklist, with no mention or example of creating a Linux virtual machine. There are no Linux-specific instructions or parity in the resource creation steps, and the only VM example is Windows-based.
Recommendations
- Include steps and Terraform resource examples for creating an Azure Linux Virtual Machine (using azurerm_linux_virtual_machine) alongside or as an alternative to the Windows VM example.
- Update the checklist to mention both Windows and Linux VM creation, or provide a choice for the user.
- Where applicable, provide verification and troubleshooting steps that are relevant for both Windows and Linux VMs.
- Ensure that any scripts, commands, or code snippets (such as those for retrieving outputs or testing connectivity) are cross-platform or include both Windows and Linux command examples.
Application Gateway
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/redirect-overview.md
...main/articles/application-gateway/redirect-overview.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page does not provide any OS-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 alternatives, and the guidance implicitly assumes a Windows-first approach by directing users to PowerShell.
Recommendations
- Provide equivalent examples and tutorials using Azure CLI (az), which is cross-platform and works on Linux, macOS, and Windows.
- Include links to both PowerShell and Bash/Azure CLI tutorials in the 'Next steps' section.
- Explicitly mention that configuration can be performed from any OS using the Azure Portal or Azure CLI, not just PowerShell.
- Where possible, add code snippets or configuration steps for both Windows (PowerShell) and Linux (Bash/Azure CLI) environments.
Application Gateway
Azure Application Gateway Backend Settings configuration
...les/application-gateway/configuration-http-settings.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is largely platform-neutral, focusing on Azure Application Gateway backend settings. However, in the troubleshooting section for Dedicated Backend Connections, Windows-specific authentication protocols (NTLM, Kerberos) and references to Windows documentation (Kerberos, IIS Windows Authentication) are mentioned without Linux equivalents or guidance for non-Windows backends. Additionally, Windows authentication is discussed before any mention of cross-platform alternatives, creating a mild 'windows_first' bias.
Recommendations
- Add guidance for troubleshooting authentication issues with Linux-based backends, such as using SPNEGO or other Kerberos implementations.
- Include references or links to documentation for configuring Kerberos/NTLM on Linux (e.g., Samba, MIT Kerberos, mod_auth_kerb for Apache).
- Clarify that NTLM and Kerberos are Windows-centric protocols, and provide information about supported authentication methods for Linux-based backend servers.
- If possible, add troubleshooting steps for common Linux web servers (Apache, Nginx) when used as Application Gateway backends.
Application Gateway
Health monitoring overview for Azure Application Gateway
...lication-gateway/application-gateway-probe-overview.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page for Azure Application Gateway health monitoring provides detailed conceptual information applicable to all platforms. However, it demonstrates a mild Windows bias by referencing PowerShell cmdlets and examples for custom probe configuration and response matching, without offering equivalent Azure CLI or ARM template examples. Additionally, the 'MinServers' property is noted as only configurable via PowerShell, Azure CLI, or ARM templates, but only PowerShell is shown in examples. The 'Next steps' section lists PowerShell before Azure portal, and does not mention Azure CLI or ARM template guides.
Recommendations
- Add Azure CLI examples alongside PowerShell for configuring custom probes and response matching.
- Provide ARM template snippets for probe configuration and matching criteria.
- Explicitly mention Azure CLI and ARM template documentation in 'Next steps' and throughout the page where PowerShell is referenced.
- Ensure parity in example ordering, showing Azure CLI and PowerShell together or alternating their order.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller - AKS Add-on
...pplication-gateway-for-containers-alb-controller-addon.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell (a Windows-centric tool) is given equal prominence and is sometimes shown before or alongside CLI examples. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is not clearly marked as Windows-only. The use of PowerShell tabs and commands may create friction for Linux/macOS users, although all critical operations are also available via Azure CLI, which is cross-platform.
Recommendations
- Clearly indicate that Azure PowerShell examples are intended for Windows users, and Azure CLI is recommended for Linux/macOS.
- Consider showing Azure CLI examples first, as CLI is cross-platform and more widely used in Linux/macOS environments.
- Add notes or guidance for Linux/macOS users, such as confirming that Azure CLI and kubectl commands work natively on their platforms.
- Remove or de-emphasize PowerShell examples unless there is a Windows-specific requirement.
- Where possible, provide Bash shell script examples for common tasks, especially for verification steps.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller - Helm
...application-gateway-for-containers-alb-controller-helm.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell examples are always present and often shown immediately after CLI. Windows-specific tooling (winget) is mentioned for Helm installation, and Windows is referenced explicitly in Helm install instructions. However, Linux parity is generally maintained, with Bash and Azure CLI examples provided, and Linux-specific Helm install instructions included. The bias is mostly in ordering and explicit Windows tool mentions.
Recommendations
- Ensure Linux instructions are presented before or alongside Windows instructions, not after.
- For Helm installation, mention Linux package managers (apt, yum, snap) as alternatives, not just curl script.
- Add explicit macOS instructions for Helm installation (e.g., Homebrew).
- Clarify that Azure CLI and Bash commands are cross-platform, and PowerShell is optional for Windows users.
- Where possible, avoid referencing Windows-specific tools (like winget) before Linux equivalents.
- Consider grouping CLI and PowerShell examples together, or using tabs with clear OS labels.