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 926-950 of 981 flagged pages
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
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but the PowerShell examples are prominent and detailed, and Windows-specific installation instructions (e.g., Helm via winget) are given before Linux equivalents. The Helm installation section gives Windows instructions first and highlights Windows tools like winget, while Linux instructions are present but less emphasized. There are no missing Linux examples for critical steps, but Windows tools and patterns are sometimes mentioned before Linux equivalents.
Recommendations
- Present Linux and Windows instructions in parallel or alternate their order to avoid Windows-first bias.
- Expand Linux installation instructions for tools (e.g., mention package managers like apt, yum, or snap for Helm, not just the curl script).
- Explicitly state that all Azure CLI commands are cross-platform and can be run on Linux/macOS/Windows.
- Where PowerShell is used, clarify that Azure CLI is the preferred cross-platform option, and PowerShell is optional for Windows users.
- Add macOS-specific instructions where relevant, especially for Helm installation.
Create Pull Request
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 for most steps, but PowerShell (a Windows-centric tool) is given equal prominence and sometimes appears before Linux-native alternatives. The use of PowerShell is unnecessary for most Linux/macOS users, and the documentation does not explicitly clarify that Azure CLI is cross-platform while PowerShell is primarily Windows-focused. There are no missing Linux examples, but the inclusion of PowerShell may create confusion or friction for non-Windows users.
Recommendations
- Clarify in the prerequisites and code tabs that Azure CLI is cross-platform and recommended for Linux/macOS users, while PowerShell is primarily for Windows.
- Present Azure CLI examples first in all code tab sections, as it is the default for Linux/macOS and Windows.
- Consider removing PowerShell examples or placing them in a secondary section for Windows users, to avoid implying parity.
- Add brief notes indicating that PowerShell is optional and not required for Linux/macOS users.
- Ensure all instructions and tooling references are equally accessible from Linux/macOS (e.g., avoid referencing Windows-only tools unless necessary).
Application Gateway
Troubleshoot Application Gateway for Containers
...cation-gateway/for-containers/troubleshooting-guide.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux and Windows examples for filtering logs, but the Windows example (using findstr) is presented immediately after the Linux example (using grep), and both are clearly labeled. The rest of the troubleshooting steps use standard Kubernetes CLI commands that are cross-platform. There is no exclusive use of Windows tools, nor are Windows patterns mentioned before Linux equivalents elsewhere. The bias is minor and limited to the order and labeling of log filtering examples.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence, perhaps using tabbed code blocks or side-by-side formatting.
- Consider showing Linux and Windows examples together, or defaulting to Linux first given the Kubernetes ecosystem's Linux-centric nature.
- Add a note clarifying that all kubectl commands work on both platforms, and only the log filtering command differs.
- If possible, provide macOS-specific notes (though macOS is typically similar to Linux).
Application Gateway
Troubleshoot Application Gateway for Containers
...cation-gateway/for-containers/troubleshooting-guide.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides troubleshooting guidance for Application Gateway for Containers and generally uses cross-platform Kubernetes tools (kubectl, helm). However, in the section on collecting logs, Windows-specific command-line patterns (findstr) are presented alongside Linux (grep), but the Windows example is shown after the Linux one. The documentation does not exclusively favor Windows, but it does provide explicit Windows command examples, which is positive for parity. There are no missing Linux/macOS examples, and all critical tasks can be completed on any platform.
Recommendations
- Ensure that Linux/macOS and Windows examples are always presented together, preferably in tabbed format, to avoid any perception of bias.
- Consider adding macOS-specific notes if there are any differences (though none are apparent here).
- Maintain parity by continuing to provide both grep (Linux/macOS) and findstr (Windows) examples for log filtering.
- If possible, clarify that all commands are cross-platform except where noted, to reassure users.
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 for most steps, but PowerShell is featured as a first-class option throughout, including module installation and resource management. Azure CLI is cross-platform, but PowerShell is primarily used on Windows, and its inclusion as a main tab may create friction for Linux/macOS users. In several sections, PowerShell examples are shown before or alongside CLI, and there are no Linux/macOS-specific notes or parity checks. However, all critical tasks can be completed with Azure CLI, which is cross-platform.
Recommendations
- Consider making Azure CLI the default or primary example, as it is cross-platform and more widely used by Linux/macOS users.
- Add explicit notes clarifying that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
- Ensure that all PowerShell instructions are matched with Azure CLI equivalents, and avoid presenting PowerShell as the first or preferred option.
- If possible, add a 'bash' or 'Linux/macOS' tab for any steps where CLI usage may differ (e.g., environment variable syntax).
- Review for any subtle assumptions (e.g., use of Windows-style variables or paths) and clarify for cross-platform compatibility.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller
...ploy-application-gateway-for-containers-alb-controller.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides both Windows and Linux instructions for installing Helm, but the Windows example (using winget) is presented first and references Windows-specific tooling. The rest of the guide uses Azure CLI and Bash-compatible commands, which are cross-platform, and explicitly states that Helm commands can be run using Bash. No PowerShell-specific examples are given for core tasks, and Linux parity is generally maintained.
Recommendations
- Present Linux and Windows installation instructions for Helm in parallel, or default to Linux first, as Linux is the primary OS for most Kubernetes workloads.
- Explicitly mention macOS installation steps or clarify that Linux instructions also apply to macOS where relevant.
- Where Windows tools (like winget) are referenced, ensure equivalent Linux/macOS package manager options are also mentioned (e.g., apt, yum, brew).
- Consider adding a note that Azure CLI and Helm commands are cross-platform and can be run in Bash or PowerShell on any OS.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller
...ploy-application-gateway-for-containers-alb-controller.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides both Windows and Linux instructions for installing Helm, but the Windows section is presented first and includes a Windows-specific tool (winget) for installation. The Linux section is present and offers a standard installation command. All other examples and instructions use cross-platform tools (Azure CLI, Helm, kubectl) and are shown in Bash syntax, which is compatible with Linux/macOS and Windows (via Azure Cloud Shell or WSL). No critical steps are Windows-only, and Linux/macOS users can complete the quickstart without friction.
Recommendations
- Present Linux and Windows installation instructions for Helm in parallel or with Linux first, to avoid implicit prioritization.
- Explicitly mention macOS in the Helm installation section, as the Helm install instructions are also applicable to macOS.
- Clarify that Azure CLI, Helm, and kubectl commands are cross-platform and can be run in Bash, PowerShell, or Azure Cloud Shell.
- Consider linking to official Helm installation docs for all platforms, not just Windows.
- Where possible, use neutral language (e.g., 'On your local machine (Windows, Linux, or macOS)...') rather than 'local device running Windows or Linux'.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller
...ploy-application-gateway-for-containers-alb-controller.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Linux instructions for installing Helm, but the Windows instructions are presented first. All other commands and examples use Azure CLI, Helm, and kubectl, which are cross-platform tools and do not show a Windows bias. No PowerShell-heavy or Windows-only tooling is present, and Linux parity is maintained throughout.
Recommendations
- Present Linux and Windows installation instructions for Helm in parallel tabs or list Linux first, as Linux is the most common platform for Kubernetes workloads.
- Explicitly mention that Azure CLI, Helm, and kubectl commands work on Linux, macOS, and Windows, and provide troubleshooting notes for each OS if relevant.
- Ensure future updates continue to provide parity for Linux/macOS users, especially for installation and environment setup steps.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller
...ploy-application-gateway-for-containers-alb-controller.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides installation instructions for Helm on both Windows and Linux, but the Windows example (using PowerShell and winget) is presented first, followed by the Linux example. The Windows installation method is highlighted before Linux, which may subtly prioritize Windows users. However, the majority of commands throughout the guide use Azure CLI and Bash syntax, which are cross-platform and suitable for both Linux and Windows environments. There are no sections that are Windows-only or that omit Linux equivalents.
Recommendations
- Present Linux and Windows installation instructions for Helm in parallel tabs or sections, or alternate which OS is shown first to avoid implicit prioritization.
- Explicitly state that all Azure CLI and Helm commands can be run on Linux, macOS, and Windows (with Bash or PowerShell as appropriate).
- Consider adding a macOS-specific Helm installation example for completeness.
- Clarify that Azure Cloud Shell is cross-platform and available to all users, reducing OS-specific friction.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller
...ploy-application-gateway-for-containers-alb-controller.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Linux instructions for installing Helm, but the Windows instructions are presented first. All other examples and commands use Azure CLI, Bash, and Kubernetes tools, which are cross-platform and do not show a Windows bias. No PowerShell-heavy or Windows-only tooling is present.
Recommendations
- Present Linux and Windows installation instructions for Helm in parallel tabs or list Linux first, as Linux is the more common OS for Kubernetes workloads.
- Explicitly state that all Azure CLI and Kubernetes commands work on Linux, macOS, and Windows (with WSL or Bash).
- Consider adding a note for macOS users in the Helm installation section.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller
...ploy-application-gateway-for-containers-alb-controller.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Linux instructions for installing Helm, but the Windows example (using PowerShell and winget) is presented before the Linux example. All other commands and examples use Azure CLI, Bash, or Kubernetes tools, which are cross-platform and do not show bias toward Windows.
Recommendations
- Present Linux and Windows installation instructions for Helm in parallel tabs or sections, or list Linux first to avoid implicit prioritization.
- Ensure that any future examples or troubleshooting steps include both Linux and Windows variants if platform-specific commands are needed.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller
...ploy-application-gateway-for-containers-alb-controller.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows and Linux instructions for installing Helm, but the Windows example (using PowerShell and winget) is presented first, and the Linux example second. The only explicit OS-specific example is for Helm installation, and the Windows instructions use PowerShell syntax and Windows tooling (winget). All other commands are cross-platform (Azure CLI, Helm, kubectl, Bash-style variables), and the documentation generally assumes a CLI/Bash environment, which is compatible with Linux/macOS and Windows (with WSL or PowerShell).
Recommendations
- Present Linux and Windows installation instructions for Helm in parallel tabs or sections, or list Linux first to match the majority of AKS users.
- Clarify that Azure CLI, Helm, and kubectl commands are cross-platform and provide notes for Windows users about using PowerShell or WSL where appropriate.
- For Windows instructions, mention that Bash-style variable syntax may need adjustment in PowerShell (e.g., $VAR vs $env:VAR).
- Ensure parity in troubleshooting notes for both platforms if issues arise during installation.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller
...ploy-application-gateway-for-containers-alb-controller.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows and Linux instructions for installing Helm, but the Windows example (using PowerShell and winget) is presented first, and the Linux example follows. The use of PowerShell and winget for Windows is highlighted, while the Linux installation uses a generic bash/curl command. All other commands throughout the guide are cross-platform (Azure CLI, Helm, kubectl) and do not exhibit OS-specific bias.
Recommendations
- Present Windows and Linux installation instructions for Helm side-by-side or in parallel tabs, rather than listing Windows first.
- Explicitly mention that Azure CLI, Helm, and kubectl commands are cross-platform and can be run on Windows, Linux, or macOS.
- Consider adding a macOS-specific Helm installation example for completeness.
- Clarify that Azure Cloud Shell is OS-agnostic and available to all users.
Application Gateway
Application gateway components
.../application-gateway/application-gateway-components.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page lists Azure PowerShell as the first option for creating an application gateway, ahead of the Azure CLI. This ordering may subtly prioritize Windows tooling, as PowerShell is most commonly associated with Windows environments, while the Azure CLI is cross-platform and widely used on Linux/macOS. No examples or instructions are given in the main body, and no Windows-specific tools or patterns are mentioned elsewhere.
Recommendations
- List Azure CLI before Azure PowerShell in the 'Next steps' section to better reflect cross-platform parity.
- Explicitly mention that both Azure PowerShell and Azure CLI are available on Windows, Linux, and macOS.
- If examples or walkthroughs are added in the future, ensure both PowerShell and CLI examples are provided, or default to CLI for cross-platform accessibility.
Application Gateway
Azure Application Gateway infrastructure configuration
...es/application-gateway/configuration-infrastructure.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page exhibits mild Windows bias by referencing Azure PowerShell cmdlets for Application Gateway management (restart operations) and mentioning PowerShell before Azure CLI. No explicit Linux/macOS examples or tools are provided, and the only command-line references are PowerShell-centric. However, most of the content is platform-neutral, focusing on Azure resource configuration, permissions, and networking concepts.
Recommendations
- Provide Azure CLI examples alongside or before PowerShell examples, especially for restart/start/stop operations.
- Explicitly mention that all operations can be performed from Linux/macOS using Azure CLI.
- Add links to Azure CLI documentation for Application Gateway management.
- Where possible, include cross-platform command snippets (CLI, PowerShell, Portal) for key tasks.
Application Gateway
Quickstart: Direct web traffic using Bicep
...ain/articles/application-gateway/quick-create-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, validation, and cleanup tasks. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented as a primary option throughout. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux/macOS platform nuances. The order of presentation sometimes puts PowerShell before or alongside CLI, rather than clearly prioritizing cross-platform CLI usage.
Recommendations
- Explicitly state that Azure CLI works on Windows, Linux, and macOS, and is the recommended cross-platform tool.
- Present Azure CLI examples first in all sections, with PowerShell as an alternative for Windows users.
- Add brief notes for Linux/macOS users about running Azure CLI commands in Bash or other shells.
- Consider removing PowerShell examples from the main flow, or move them to a dedicated 'Windows users' section.
- Clarify that PowerShell examples are for Windows users, and that Linux users should use Azure CLI.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias by listing Azure PowerShell (a Windows-centric tool) as the only example for creating an autoscaling, zone redundant application gateway with a reserved virtual IP address. No equivalent Linux/macOS CLI or ARM template example is provided or referenced. Additionally, the PowerShell tutorial is listed first and exclusively in the 'Next steps' section.
Recommendations
- Add equivalent instructions and links for Azure CLI (cross-platform) and ARM/Bicep templates for creating autoscaling, zone redundant application gateways.
- List cross-platform tools (Azure CLI, ARM templates) before or alongside PowerShell in 'Next steps'.
- Explicitly mention that PowerShell is available on Linux/macOS, or clarify platform requirements for each tool.
Application Gateway
Azure Monitor metrics for Application Gateway
...les/application-gateway/application-gateway-metrics.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias by highlighting Power BI (a Windows-centric tool) for log visualization in the 'Next steps' section and referencing it before mentioning other cross-platform or Linux-native alternatives. No Linux/macOS-specific tools or examples are provided, and the documentation does not mention command-line or open-source visualization options that are popular among Linux users. However, the core instructions for monitoring and alerting within the Azure portal are platform-agnostic.
Recommendations
- Include examples or references to cross-platform log visualization tools such as Grafana, Kibana, or open-source alternatives alongside Power BI.
- Explicitly mention that Azure Monitor and portal-based workflows are accessible from any OS with a browser.
- Provide CLI (Azure CLI, Bash) or REST API examples for metric access and alert configuration to support Linux/macOS users.
- Add links to documentation or tutorials for integrating Azure Monitor metrics with open-source monitoring stacks.
Application Gateway
Container networking with Azure Application Gateway for Containers
...ication-gateway/for-containers/container-networking.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page generally avoids OS-specific instructions, but in the 'Next steps' section, the link to 'Deploy ALB Controller' includes a query parameter '?tabs=install-helm-windows', suggesting that Windows installation instructions are prioritized or shown by default. There are no explicit Linux/macOS examples or tabs referenced, and no mention of Linux-specific tools or commands.
Recommendations
- Ensure that the 'Deploy ALB Controller' quickstart page defaults to a neutral or OS-detection-based tab, or at least provides both Windows and Linux/macOS installation tabs equally.
- Explicitly mention that the instructions apply to all platforms, or provide clear links/tabs for Linux/macOS users.
- Review linked quickstarts and ensure Linux/macOS parity in examples and instructions.
Application Gateway
Azure Application Gateway configuration overview
...articles/application-gateway/configuration-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists Windows-centric tools (PowerShell) before cross-platform alternatives (Azure CLI) in the 'Next steps' section. No explicit Linux/macOS bias is present in the main content, but the ordering subtly prioritizes Windows users.
Recommendations
- List Azure CLI before PowerShell in 'Next steps', as CLI is cross-platform and more inclusive.
- Explicitly mention that Azure CLI works on Linux/macOS and provide links to installation guides for non-Windows platforms.
- Consider adding examples or links for ARM templates or Terraform, which are platform-agnostic.
- Ensure future documentation sections provide equal coverage for Linux/macOS tools and workflows.
Application Gateway
Troubleshoot Application Gateway for Containers
...cation-gateway/for-containers/troubleshooting-guide.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux and Windows examples for filtering logs, but the Windows example (using findstr) is presented after the Linux example (using grep). There is no exclusive use of Windows tools, and most commands are cross-platform (kubectl, helm). However, the presence of a dedicated Windows tab and explicit CLI example for Windows users indicates some Windows bias, though Linux is presented first and with parity.
Recommendations
- Ensure both Linux and Windows examples are presented with equal prominence, possibly side-by-side or in a unified format.
- Consider mentioning macOS explicitly where Linux commands apply, to clarify compatibility.
- If possible, provide a table or note indicating which commands work across platforms and highlight any platform-specific caveats.
- Avoid labeling sections as '[Linux]' and '[Windows]' unless there are substantial differences; otherwise, use '[Linux/macOS]' for broader coverage.
Application Gateway
Quickstart: Deploy Application Gateway for Containers ALB Controller
...ploy-application-gateway-for-containers-alb-controller.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides both Windows and Linux instructions for installing Helm, but Windows-specific tooling (winget) is mentioned and shown first. The installation section for Helm lists Windows before Linux, and highlights Windows Package Manager (winget) as an option, which is a Windows-only tool. However, Linux instructions are present and clear, and all core deployment steps use cross-platform tools (Azure CLI, Helm, kubectl) with Bash syntax, which works on Linux/macOS and Windows (with WSL or PowerShell). No critical steps are Windows-only.
Recommendations
- Present Linux and Windows installation instructions for Helm in parallel, or list Linux first to avoid implicit prioritization.
- Mention cross-platform package managers (e.g., Homebrew for macOS) alongside winget for Windows.
- Clarify that all Azure CLI, Helm, and kubectl commands are cross-platform and provide notes for running them on macOS.
- Add explicit macOS installation instructions for Helm.
- Avoid highlighting Windows-specific tools (like winget) before Linux equivalents.
Application Gateway
HTTP response codes - Azure Application Gateway
...in/articles/application-gateway/http-response-codes.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias, notably in the troubleshooting section for HTTP 504 Gateway Time-out, where IIS (a Windows web server) is discussed first and in greater detail, with a direct link to Microsoft's IIS documentation. The Nginx (Linux) example is mentioned second, with less detail and no direct link to upstream documentation. NTLM authentication is referenced in the 401 section, which is a Windows-specific protocol. No Linux/macOS-specific troubleshooting tools, logs, or patterns are mentioned, and examples are generally platform-neutral but Windows technologies are referenced first or exclusively where relevant.
Recommendations
- Provide equal detail and direct documentation links for Linux web servers (e.g., Apache, Nginx) when discussing time-out settings.
- Include troubleshooting steps or examples for Linux/macOS users, such as using systemd, journalctl, or Linux-native log locations.
- Mention Linux authentication patterns (e.g., Kerberos, LDAP) alongside NTLM when discussing backend authentication.
- Ensure examples and references are balanced between Windows and Linux platforms, or presented in parallel.
- Add explicit notes or examples for Linux/macOS users where platform-specific configuration or troubleshooting is relevant.
Application Gateway
Configure Azure Application Gateway Private Link
...articles/application-gateway/private-link-configure.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents configuration options for Azure Application Gateway Private Link via the Azure portal, PowerShell, and Azure CLI. However, the PowerShell section is given before the CLI section, and the PowerShell example is extensive and detailed, reflecting a slight Windows-first and PowerShell-heavy bias. Both PowerShell and CLI examples are present, but there are no Linux-specific notes, nor are Linux/macOS shell patterns or troubleshooting tips mentioned. The CLI section is present and reasonably complete, but the ordering and depth of PowerShell coverage may create friction for Linux/macOS users.
Recommendations
- Present Azure CLI instructions before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
- Add explicit notes clarifying that Azure CLI works natively on Linux/macOS, while PowerShell may require installation or may not be preferred on those platforms.
- Ensure parity in example depth and troubleshooting between PowerShell and CLI sections.
- Consider adding bash shell scripting examples for automation on Linux/macOS.
- Add a short section on platform compatibility for each method.
Application Gateway
What is Azure Application Gateway
...ocs/blob/main/articles/application-gateway/overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists Azure PowerShell (Windows-centric) as a primary method for creating an Application Gateway before mentioning Azure CLI, which is cross-platform. No explicit Linux/macOS bias is present, but the ordering may subtly prioritize Windows tools.
Recommendations
- List Azure CLI before Azure PowerShell in 'Next steps', as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly mention that Azure CLI works on Windows, Linux, and macOS.
- Ensure that all examples and quickstarts include both PowerShell and CLI options, with equal prominence.
- Add a note clarifying platform compatibility for each tool.