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 826-850 of 981 flagged pages
Application Gateway Azure Application Gateway listener configuration ...rticles/application-gateway/configuration-listeners.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a code example for enabling HTTP/2 support using Azure PowerShell, which is primarily a Windows-centric tool. There are no equivalent examples for Azure CLI or Bash, which are more commonly used on Linux and cross-platform environments. This creates a bias towards Windows users by assuming PowerShell as the default automation method and omitting Linux-friendly alternatives.
Recommendations
  • Add equivalent Azure CLI and Bash examples for all configuration tasks currently shown only in PowerShell.
  • Explicitly mention that Azure CLI and Bash can be used for these operations, and provide links or inline examples.
  • Ensure that future documentation includes both Windows and Linux automation tools side-by-side, or in a platform-agnostic manner.
  • Consider a section that discusses cross-platform tooling for Azure management, highlighting parity and differences.
GitHub Create Pull Request
Application Gateway Container networking with Azure Application Gateway for Containers ...ication-gateway/for-containers/container-networking.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the 'Next steps' section, where the link to 'Deploy ALB Controller' explicitly references a Windows-specific Helm installation tab ('install-helm-windows'). There are no Linux or cross-platform installation instructions or examples provided or referenced, and no mention of Linux tools or shell commands throughout the page.
Recommendations
  • Provide parallel Linux installation instructions and examples for deploying the ALB Controller, such as 'install-helm-linux' or generic cross-platform tabs.
  • Ensure all referenced quickstart and deployment guides include both Windows and Linux shell commands and tooling.
  • Review all code snippets and command examples in related documentation to ensure Linux parity and avoid Windows-first presentation.
  • Explicitly mention supported platforms and clarify any platform-specific requirements or differences.
GitHub Create Pull Request
Application Gateway Quickstart: Create Application Gateway for Containers managed by ALB Controller ...ation-gateway-for-containers-managed-by-alb-controller.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively using Azure CLI commands and Bash scripting, which are most commonly used in Windows (via Azure CLI, PowerShell, or WSL) and do not mention or provide parity for Linux-native tools or workflows. The examples and instructions assume the use of Azure CLI, which is available cross-platform but is often associated with Windows and does not acknowledge Linux-specific networking tools or alternative methods. There are no references to Linux-specific commands, nor is there guidance for users who may be operating in a Linux-only environment.
Recommendations
  • Explicitly state that all CLI commands work on Linux, macOS, and Windows, and provide installation instructions for Azure CLI on Linux.
  • Include alternative examples using native Linux tools (e.g., ip, ifconfig, netplan) for subnet and network inspection, where appropriate.
  • Add notes or sections for Linux users, such as verifying prerequisites or troubleshooting common Linux-specific issues (e.g., permissions, environment variables).
  • Mention that Bash scripts and kubectl commands are cross-platform, and provide PowerShell equivalents for Windows users if needed.
  • Clarify that the documentation is platform-agnostic and ensure that any referenced tools (Azure CLI, kubectl) are available and supported on Linux.
GitHub Create Pull Request
Application Gateway Hosting multiple sites on Azure Application Gateway ...articles/application-gateway/multiple-site-overview.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by mentioning Azure PowerShell before Azure CLI in several places, including the important note about rule priority and the step-by-step configuration links. PowerShell is traditionally associated with Windows environments, while CLI is more cross-platform and Linux-friendly. There are no Linux-specific examples, tools, or patterns discussed, and no explicit parity guidance for Linux users. However, the CLI is referenced, and no exclusively Windows tools (like cmd.exe or Windows-only utilities) are used.
Recommendations
  • Alternate the order of Azure PowerShell and Azure CLI references, or mention Azure CLI first in some sections to avoid implicit prioritization of Windows tools.
  • Provide explicit examples or notes for Linux environments, such as shell scripting or integration with Linux-based automation tools.
  • Clarify that both Azure PowerShell and Azure CLI are cross-platform, and link to installation guides for Linux and macOS users.
  • Add a section or callout for Linux users, highlighting any differences or considerations when using Azure CLI or deploying backend pools on Linux servers.
  • Ensure parity in step-by-step guides by verifying that CLI instructions are as detailed and prominent as PowerShell instructions.
GitHub Create Pull Request
Application Gateway Quickstart: Direct web traffic using Bicep ...ain/articles/application-gateway/quick-create-bicep.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, validation, and cleanup, but PowerShell is given equal prominence to CLI throughout. There are no explicit Linux shell examples (e.g., Bash), and PowerShell is a Windows-centric tool, which may disadvantage Linux users. The instructions do not mention Linux-specific considerations or alternatives, and PowerShell is presented as a primary option alongside CLI, rather than as a secondary or optional tool for Windows users.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows, while PowerShell is primarily for Windows users.
  • Consider listing Azure CLI (Bash) examples first, as CLI is the most cross-platform tool, and indicate PowerShell as an alternative for Windows users.
  • Add explicit Bash shell examples or notes for Linux users where appropriate.
  • Include a note on how to install and use Azure CLI on Linux systems.
  • If PowerShell is mentioned, clarify its platform support and recommend CLI for Linux/macOS users.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/quick-create-bicep.md ...ain/articles/application-gateway/quick-create-bicep.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment, validation, and cleanup steps. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented as a primary alternative throughout. There are no explicit Linux shell examples (e.g., Bash), nor is there mention of Linux-specific considerations or tools. The use of PowerShell may implicitly favor Windows users, as it is less commonly used on Linux platforms.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
  • Consider providing Bash shell examples or explicitly noting that CLI commands work in Bash on Linux/macOS.
  • If PowerShell is included, add a note about PowerShell Core availability on Linux/macOS, or link to installation instructions.
  • Add a brief section or tip for Linux users, such as verifying prerequisites or environment setup.
  • Ensure that any references to tools or patterns (such as script file extensions or command syntax) are not Windows-specific unless alternatives are provided.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/tutorial-multiple-sites-cli.md ...les/application-gateway/tutorial-multiple-sites-cli.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation demonstrates mild Windows bias by referencing IIS installation in the VMSS setup section, which is a Windows web server, despite the VMSS image being Ubuntu Linux. The page also mentions Azure PowerShell as an alternative before any Linux-specific tooling, and links to a PowerShell tutorial. However, all CLI examples use Azure CLI and Bash scripting, and the actual web server installed in the walkthrough is NGINX (Linux-native). No PowerShell or Windows command-line examples are shown directly, and Linux usage is present throughout.
Recommendations
  • Remove or clarify the IIS reference in the VMSS section, as the walkthrough uses Ubuntu and installs NGINX. If IIS is relevant, provide a parallel example for Windows VMSS.
  • When mentioning alternative tooling, list Linux-native options (e.g., Bash, Azure CLI in Cloud Shell) before or alongside PowerShell.
  • Ensure that all example scripts and instructions are clearly Linux-compatible, and provide explicit Windows equivalents if needed.
  • If referencing PowerShell, also mention Bash or other Linux shells as alternatives, and link to Linux-focused tutorials where appropriate.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/application-gateway-backend-health.md ...lication-gateway/application-gateway-backend-health.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides explicit PowerShell examples and mentions PowerShell as a primary method for accessing backend health, with the PowerShell section appearing before Azure CLI. There are no Linux-specific command-line examples (such as Bash or shell scripts), nor are Linux troubleshooting tools or patterns mentioned. The documentation assumes familiarity with PowerShell, which is predominantly used on Windows, and does not offer parity for Linux users beyond Azure CLI.
Recommendations
  • Add Bash or shell script examples for retrieving backend health using Azure CLI, demonstrating usage in a Linux environment.
  • Explicitly mention that Azure CLI is cross-platform and provide guidance for Linux/macOS users.
  • Include troubleshooting steps or tools commonly used on Linux (e.g., curl, openssl for certificate checks) alongside Windows-centric tools.
  • Reorder examples to present Azure CLI before PowerShell, or present both methods together to avoid implicit prioritization.
  • Clarify that PowerShell Core is available on Linux, if relevant, and provide installation/use instructions for non-Windows platforms.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides a code example for enabling HTTP/2 support using Azure PowerShell, which is primarily a Windows-centric tool. There are no equivalent examples for Azure CLI or Bash, which are more commonly used on Linux and cross-platform environments. The only automation/configuration example is PowerShell, and there is no mention of Linux tools or patterns.
Recommendations
  • Add Azure CLI and/or Bash examples alongside PowerShell for all configuration snippets, especially for enabling HTTP/2 support.
  • Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and provide parity in instructions.
  • Where PowerShell is referenced, clarify that it is available cross-platform, but still provide CLI/Bash alternatives for Linux users.
  • Review other configuration sections to ensure Linux-friendly tools and workflows are represented equally.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
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. There is a specific callout to creating an application gateway using PowerShell, which is typically associated with Windows environments, while the Azure CLI (cross-platform) is mentioned after. No Linux-specific tools or examples are provided, and there is no explicit mention of Linux or Bash usage.
Recommendations
  • List Azure CLI before PowerShell in the 'Next steps' section to emphasize cross-platform parity.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows.
  • Add examples or links for configuring Application Gateway using Bash scripts or Linux-native tools where relevant.
  • Ensure that any referenced scripts or walkthroughs include both PowerShell and Bash/CLI examples.
  • Consider adding a note about platform compatibility for each tool mentioned.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing deployment via the Azure Portal and linking to procedures that prioritize CLI, PowerShell, and ARM templates, without mentioning or providing examples for Linux-specific tools or workflows (such as Azure CLI usage on Linux, Bash scripts, or cross-platform deployment methods). There are no Linux or Bash-specific instructions or examples, and the 'Deploy to Azure' button assumes use of a browser, which is more common in Windows-centric workflows.
Recommendations
  • Include explicit instructions and examples for deploying ARM templates using Azure CLI on Linux (e.g., az deployment group create).
  • Provide Bash script examples for automating alert configuration.
  • Mention cross-platform compatibility of the ARM templates and clarify that deployment can be performed from Linux, macOS, or Windows.
  • Add links to documentation or tutorials for Linux users, such as using Azure CLI in Bash or shell environments.
  • Balance references to PowerShell and CLI by presenting both side-by-side, or by using CLI-first examples where possible.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/container-networking.md ...ication-gateway/for-containers/container-networking.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the 'Next steps' section, where the link to the ALB Controller deployment quickstart defaults to the Windows installation tab ('?tabs=install-helm-windows'). There are no explicit Linux or cross-platform examples provided, and no mention of Linux-specific tools or instructions. The documentation does not provide parity for Linux users, who may use Bash or other shells for Helm installation and AKS management.
Recommendations
  • Ensure that quickstart and deployment guides provide both Windows (PowerShell) and Linux (Bash) instructions, with tabs or sections for each.
  • Default links to cross-platform or neutral tabs (e.g., '?tabs=install-helm-bash') or provide both options equally.
  • Explicitly mention Linux-compatible tools and patterns where relevant, such as Bash scripts or Linux CLI usage.
  • Review all example commands and ensure Linux equivalents are present and easy to find.
  • Add a note clarifying that instructions apply to both Windows and Linux, or specify differences where necessary.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/overview.md ...rticles/application-gateway/for-containers/overview.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page displays mild Windows bias by listing Windows-centric tools (PowerShell, Azure portal) before mentioning cross-platform or Linux-friendly alternatives (CLI, Terraform) in the deployment strategies section. There are no explicit Linux or Bash examples, and no mention of Linux-specific tooling or patterns. The documentation does not provide parity in examples or guidance for Linux users, and implicitly prioritizes Windows tools.
Recommendations
  • Ensure that command-line examples are provided for both PowerShell and Bash/Azure CLI, with equal prominence.
  • List cross-platform tools (CLI, Terraform) before or alongside Windows-specific tools (PowerShell, Azure portal) when describing deployment options.
  • Include explicit guidance or examples for Linux users, such as Bash scripts or references to Linux-native workflows.
  • Review other documentation pages linked from this overview to ensure Linux parity in walkthroughs and quickstarts.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller.md ...ploy-application-gateway-for-containers-alb-controller.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias in the Helm installation section, where Windows installation instructions (including use of the Windows Package Manager 'winget') are presented before Linux instructions. The use of 'winget' is a Windows-specific tool, and the section explicitly calls out Windows as a separate tab. However, the rest of the documentation uses cross-platform tools (Azure CLI, Helm, kubectl) and provides Linux installation steps for Helm. There are no PowerShell-heavy examples, and Linux parity is generally maintained outside the Helm installation section.
Recommendations
  • Present Linux and Windows installation instructions for Helm in parallel or in a neutral order, rather than listing Windows first.
  • Where possible, use generic installation instructions or link to the official Helm documentation for both platforms equally.
  • Avoid highlighting Windows-specific tools (like 'winget') before mentioning Linux equivalents (such as apt, yum, or direct script installation).
  • Consider adding macOS installation instructions for Helm to further improve cross-platform parity.
  • Ensure that any platform-specific instructions are grouped together and clearly labeled, rather than giving precedence to one platform.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/quickstart-create-application-gateway-for-containers-managed-by-alb-controller.md ...ation-gateway-for-containers-managed-by-alb-controller.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation demonstrates a moderate Windows bias by exclusively using Azure CLI commands and shell scripting patterns that are most commonly used and supported on Windows (and WSL), with no mention of Linux-specific nuances or alternatives. All examples use Azure CLI (az), which is available cross-platform but is often associated with Windows environments. There is no explicit mention of Linux shell environments, nor are there examples or notes about running these commands on Linux or macOS. The documentation does not address potential differences in command syntax, environment variables, or prerequisites for Linux users.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide installation instructions for each platform.
  • Include notes or examples for Linux users, such as using bash/zsh and handling environment variables.
  • Mention potential issues with command-line tools on Linux (e.g., differences in quoting, line endings, or required dependencies).
  • Provide troubleshooting tips for common Linux-specific errors (e.g., permission issues, missing dependencies).
  • Where appropriate, include alternative commands or instructions for Linux-native tools (e.g., using curl, jq, or native package managers).
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by consistently mentioning Azure PowerShell before Azure CLI when describing configuration steps and examples. The PowerShell example is given first in the 'Wildcard host names in listener' section, and the 'Next steps' section lists PowerShell before CLI. There is a slight emphasis on PowerShell, which is more commonly used on Windows, while CLI is cross-platform. No exclusive use of Windows tools or missing Linux examples is observed, as Azure CLI is referenced and supported throughout.
Recommendations
  • Alternate the order of Azure PowerShell and Azure CLI references/examples to avoid implicit prioritization.
  • Provide equal depth and clarity in both PowerShell and CLI instructions, ensuring CLI examples are as prominent and detailed as PowerShell ones.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Consider adding a short note or section for Linux/macOS users to clarify tool parity and usage.
  • Where possible, provide bash script examples alongside PowerShell snippets for configuration tasks.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/overview.md ...ocs/blob/main/articles/application-gateway/overview.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page lists Azure PowerShell as a primary method for creating and managing Application Gateway resources, and PowerShell is mentioned before Azure CLI in the 'Next steps' section. This ordering and emphasis can be interpreted as a subtle Windows bias, as PowerShell is most commonly associated with Windows environments. There are no explicit Linux-only examples or tools highlighted, and the documentation does not provide parity in showcasing Linux-native workflows or tools.
Recommendations
  • List Azure CLI before PowerShell in example and quickstart links, as CLI is cross-platform and widely used on Linux.
  • Explicitly mention that Azure CLI is available on Linux and macOS, and provide links to installation guides for those platforms.
  • Include examples or references to Linux-native tools or workflows (e.g., bash scripts, cloud-init) where relevant.
  • Add a note clarifying that all management tasks can be performed from Linux, macOS, and Windows equally, and highlight any platform-specific considerations.
  • Ensure future documentation sections provide equal coverage and ordering for cross-platform tools, avoiding implicit prioritization of Windows-centric solutions.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell as a primary configuration method alongside the Azure portal and CLI, and by providing extensive PowerShell examples and cmdlet references before Azure CLI equivalents. The PowerShell section is more detailed and comes before the CLI section, which may disadvantage Linux users who typically use Bash and Azure CLI. There are no explicit Linux-specific examples (e.g., Bash scripts, Linux shell environment notes), and no mention of Linux tools or patterns.
Recommendations
  • Add explicit Bash/Linux shell examples for CLI commands, including environment setup notes for Linux users.
  • Ensure CLI examples are as detailed as PowerShell examples, including step-by-step explanations and troubleshooting tips.
  • Consider listing Azure CLI before PowerShell in configuration options and examples to avoid implicit Windows-first ordering.
  • Include a note clarifying that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Provide links or references to Linux-specific documentation or troubleshooting guides where relevant.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page lists Windows-centric tools (PowerShell) before cross-platform tools (Azure CLI) in the 'Next steps' section, suggesting a Windows-first approach. There is an explicit mention of PowerShell, which is primarily associated with Windows, and no Linux-specific examples or tools are highlighted. The ordering and tool selection may subtly prioritize Windows users over Linux users.
Recommendations
  • List Azure CLI before PowerShell in the 'Next steps' section, as Azure CLI is cross-platform and more inclusive for Linux users.
  • Add explicit mention of Linux compatibility and usage throughout the documentation, especially in sections discussing command-line configuration.
  • Provide examples or links for configuring Application Gateway using Linux-native tools or scripts where relevant.
  • Ensure parity in documentation by including screenshots or walkthroughs for both Windows and Linux environments if applicable.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/container-networking.md ...ication-gateway/for-containers/container-networking.md
Medium Priority View Details →
Scanned: 2025-08-27 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by providing a 'Next steps' deployment link that defaults to a Windows-specific installation tab (install-helm-windows), without mentioning or linking to Linux/macOS equivalents. There are no explicit PowerShell or Windows command examples in the main content, but the navigation flow prioritizes Windows users and omits Linux-first guidance.
Recommendations
  • Ensure that all deployment and installation guides linked from this page offer clear parity between Windows and Linux/macOS instructions, ideally defaulting to a neutral or most common platform (such as Linux) or providing platform selection tabs up front.
  • Explicitly mention that instructions are available for both Windows and Linux/macOS, and provide direct links or navigation cues for each.
  • Review all linked quickstarts and ensure that Linux/macOS installation steps are as prominent and complete as Windows steps.
  • Consider adding a short section or note in this page clarifying that Application Gateway for Containers is platform-agnostic and that all major OSes are supported for management and deployment tasks.
GitHub 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 →
Scanned: 2025-08-22 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for feature registration and unregistration, but consistently lists PowerShell (a Windows-centric tool) before CLI. The CLI examples are present and correct, but there is a subtle 'Windows-first' ordering bias. No Linux-specific tools or shell examples (such as Bash scripts) are provided, and there is no mention of Linux environments or considerations. The documentation does not provide any examples that are exclusive to Windows, but the ordering and emphasis may suggest a preference.
Recommendations
  • Alternate the order of PowerShell and CLI examples in different sections, or explicitly state that both are cross-platform and equally supported.
  • Add explicit mention that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Where possible, include Bash or shell script snippets for common tasks, especially in sections likely to be automated by Linux users.
  • Consider including a short section or note on using these commands in Linux environments (e.g., running Azure CLI in Bash).
  • Ensure parity in screenshots and walkthroughs by including CLI/terminal examples, not just portal or PowerShell interfaces.
GitHub Create Pull Request
Application Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/application-gateway/for-containers/troubleshooting-guide.md ...cation-gateway/for-containers/troubleshooting-guide.md
Medium Priority View Details →
Scanned: 2025-08-22 00:01
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Linux and Windows examples for filtering logs, but the Windows example is given immediately after the Linux one, and uses Windows-specific CLI patterns (findstr). There is a slight Windows bias in the ordering and explicit inclusion of Windows CLI syntax, while Linux is presented first. No PowerShell-only or Windows-only tools are used, and most commands are cross-platform (kubectl, helm). However, the documentation could improve Linux parity by ensuring equal prominence and clarity for Linux commands and avoiding Windows-first ordering or unnecessary Windows-specific syntax.
Recommendations
  • Present Linux and Windows examples in parallel tabs or sections with equal prominence.
  • Clarify that most commands are cross-platform and only the filtering syntax differs.
  • Consider providing a table or side-by-side comparison for log filtering commands.
  • Avoid unnecessary repetition of Windows CLI syntax unless required for a specific use case.
  • Ensure Linux examples are not overshadowed by Windows-specific instructions.
GitHub 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 →
Scanned: 2025-08-18 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents command-line instructions for both Azure PowerShell and Azure CLI, but consistently lists PowerShell (a Windows-centric tool) before CLI in all tabbed examples. There are no explicit Linux-only instructions or examples, and the use of PowerShell as the first example may suggest a Windows-first approach. However, Azure CLI (which is cross-platform and preferred by many Linux users) is included in all relevant sections, and no steps are exclusive to Windows or PowerShell. No Windows-only tools or patterns are mentioned, and the CLI examples are present and correct.
Recommendations
  • Alternate the order of PowerShell and CLI tabs, or list Azure CLI first to better reflect cross-platform parity.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and consider providing Bash shell snippets or Linux terminal screenshots where appropriate.
  • Add a short note or section on using the Azure Cloud Shell, which is accessible from any OS and supports both PowerShell and Bash.
  • Ensure that any future examples or troubleshooting steps do not assume a Windows environment (e.g., avoid referencing Windows file paths or PowerShell-specific output parsing).
GitHub 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 →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by listing Azure PowerShell instructions before Azure CLI in both the feature registration and unregistration sections. PowerShell is a Windows-centric tool, while Azure CLI is cross-platform and more commonly used on Linux. However, both PowerShell and CLI examples are provided, and there are no exclusive references to Windows-only tools or patterns elsewhere. There are no missing Linux examples, but the ordering and emphasis subtly prioritize Windows/PowerShell.
Recommendations
  • Alternate the order of PowerShell and CLI instructions in different sections, or list Azure CLI first to reflect its cross-platform nature.
  • Explicitly mention that both Azure CLI and PowerShell are supported on Windows, Linux, and macOS, and provide installation links for each.
  • Where possible, include Bash shell script snippets or references to Linux-native tooling (e.g., curl for REST API calls) to further demonstrate Linux parity.
  • Clarify that all portal and CLI steps are fully supported on Linux, and avoid implying PowerShell is the primary or preferred method.
  • Consider adding a short section or note highlighting cross-platform support and recommending tools for Linux users.
GitHub Create Pull Request
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 →
Scanned: 2025-08-11 00:00
Reviewed by: Unknown
Issues: 2 bias types
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 appears before the Azure CLI section, which may signal a preference for Windows-centric tooling. There are no Linux-specific examples, nor is there mention of Linux shell scripting or tooling. The CLI section is present and complete, but PowerShell is given prominence by being listed and described before CLI, which is more cross-platform. No Linux-specific guidance or troubleshooting is provided.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more familiar to Linux users.
  • Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any Linux-specific notes if needed (e.g., shell differences, permissions).
  • Add a short section or note for Linux users, highlighting any OS-specific considerations or best practices.
  • If possible, provide bash script examples or references for automation on Linux.
  • Ensure that documentation language and ordering do not imply PowerShell is the default or preferred method, especially for cross-platform scenarios.
GitHub Create Pull Request
← Previous Page 34 of 40 Next →