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 876-900 of 981 flagged pages
Application Gateway
Application gateway components
.../application-gateway/application-gateway-components.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides conceptual information about Application Gateway components and is largely platform-neutral. However, in the 'Next steps' section, Azure PowerShell is listed before Azure CLI, which may subtly prioritize Windows tooling. No examples or instructions are given that are Windows-specific, and Linux/macOS users are not excluded from any critical information.
Recommendations
- List Azure CLI before Azure PowerShell in the 'Next steps' section, as Azure CLI is cross-platform and more accessible to Linux/macOS users.
- Ensure parity in future procedural guides by providing both PowerShell and CLI examples, or referencing Bash scripts where relevant.
- Consider mentioning that Azure CLI works on all platforms, while PowerShell is most common on Windows, to guide users appropriately.
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 throughout, but PowerShell examples are given equal prominence and are sometimes shown before Linux-native alternatives. Azure PowerShell is primarily used on Windows, and its inclusion as a first-class option may create friction for Linux/macOS users. However, all critical steps are covered with Azure CLI (cross-platform) and kubectl (Linux-native) commands, so Linux users can complete the tasks without issue.
Recommendations
- Clearly indicate that Azure PowerShell is Windows-centric and recommend Azure CLI for Linux/macOS users.
- Where possible, show Azure CLI examples first, as it is cross-platform.
- Consider adding bash shell script examples for common tasks to further improve Linux parity.
- Ensure all PowerShell steps have equivalent Azure CLI commands.
- Add a note clarifying that Azure PowerShell is optional and not required for Linux/macOS users.
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 for Helm install) is mentioned before Linux equivalents, and Windows installation instructions are given first. While Linux/Bash is supported and examples are present, Windows tools and patterns (PowerShell, winget) are consistently prioritized or presented first.
Recommendations
- Alternate the order of Windows and Linux installation instructions so Linux is not always second.
- Provide Bash/Linux equivalents for all PowerShell/Windows-specific commands where possible.
- Mention Linux installation options for Helm before Windows-specific tools like winget.
- Clarify that Azure CLI commands are cross-platform and can be run on Linux/macOS, not just Windows.
- Consider adding a macOS tab for Helm installation.
- Where PowerShell is used, explicitly note that Bash or other shells can be used for Azure CLI steps.
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 includes both Linux and Windows examples for filtering logs. However, the Windows example (using 'findstr') is presented immediately after the Linux example (using 'grep'), and both are given equal prominence. The rest of the documentation uses cross-platform tools (kubectl, helm) and does not reference Windows-specific tools or patterns. There is minor bias in the ordering and explicit inclusion of Windows CLI examples, but Linux parity is maintained throughout.
Recommendations
- Consider presenting Linux and Windows examples in parallel tabs or sections, rather than sequentially, to reinforce equal importance.
- Ensure that Linux examples are not always listed first or last; alternate ordering or use tabbed UI for clarity.
- Explicitly state that all commands are cross-platform except where noted, to reassure non-Windows users.
- Review future documentation for unnecessary Windows CLI examples if Linux commands suffice.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page is generally platform-neutral in its conceptual explanations, but the 'Next steps' section prominently features a PowerShell-based tutorial for creating an autoscaling, zone-redundant Application Gateway. This may signal a Windows/PowerShell bias, as Linux/macOS users typically use Azure CLI or ARM templates. No Linux-specific examples or equivalent CLI guidance are provided or referenced.
Recommendations
- Add links to equivalent Azure CLI tutorials for autoscaling and zone-redundant Application Gateway creation.
- Mention that Azure CLI and ARM templates can be used on Linux/macOS for the same tasks.
- Ensure that PowerShell and CLI examples are presented side-by-side or with equal prominence in 'Next steps'.
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 given after the Linux example ('grep'). All other troubleshooting steps use cross-platform tools (kubectl, helm) and shell syntax, with no Windows-specific tools or patterns. The bias is minor, as Windows users are accommodated, but Linux examples are shown first and more prominently.
Recommendations
- Present Linux and Windows examples side-by-side, or use tabbed sections for parity.
- Explicitly mention that all commands are cross-platform unless otherwise noted.
- Ensure that Windows and Linux instructions are equally visible and accessible.
- Consider providing PowerShell-specific examples if Windows users are likely to use PowerShell rather than CMD.
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 instructions or explicit mentions of Linux/macOS environments, and PowerShell is not available natively on most Linux/macOS systems. However, the primary workflow is based on Azure CLI, which is cross-platform, and all critical tasks can be completed using CLI. The bias is mostly in the inclusion and prominence of PowerShell examples, which may create minor confusion or friction for Linux/macOS users.
Recommendations
- Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Consider moving Azure CLI examples before PowerShell examples in each section.
- Add explicit notes stating that PowerShell examples are for Windows users, and CLI is for Linux/macOS.
- Remove PowerShell examples from sections where they do not add value or are redundant.
- Add troubleshooting notes for Linux/macOS users if any step differs (e.g., SSH key generation, environment variables).
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 for all critical steps, ensuring parity for cross-platform users. However, PowerShell examples are given equal prominence to Azure CLI, and Windows-specific installation instructions for Helm (using winget) are presented before Linux instructions. There is a slight 'windows_first' bias in the ordering and explicit mention of Windows tools, but Linux users are not blocked from completing any task.
Recommendations
- Ensure Linux installation instructions for Helm are presented before or alongside Windows instructions, rather than after.
- Consider explicitly mentioning macOS installation steps for Helm, or clarify that Linux steps are applicable to macOS.
- Where possible, highlight Azure CLI as the default, since it is cross-platform, and present PowerShell as an alternative for Windows users.
- Add a brief note that Azure CLI commands are fully supported on Linux/macOS, reinforcing parity.
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
Summary
The documentation is generally cross-platform, but there are minor instances of Windows bias. In the 401 Unauthorized section, NTLM authentication (a Windows-specific protocol) is discussed before more general solutions, and the link provided is to Windows documentation. In the 504 Gateway Time-out section, IIS (a Windows web server) is discussed before Nginx (a popular Linux web server), and more detail is provided for IIS. However, Linux alternatives are mentioned, and the documentation is not Windows-exclusive.
Recommendations
- When referencing NTLM authentication, clarify that it is a Windows-specific protocol and provide equal emphasis on non-Windows authentication scenarios if relevant.
- In the 504 Gateway Time-out section, present Nginx (Linux) and IIS (Windows) examples in parallel, or alternate the order in which they are presented.
- Where possible, provide links to Linux/Unix documentation (e.g., for Nginx) with the same level of detail as for IIS.
- If referencing Windows-specific tools or protocols (like NTLM or IIS), explicitly note their platform specificity and, where possible, provide Linux/macOS equivalents or alternatives.
Application Gateway
Azure Application Gateway infrastructure configuration
...es/application-gateway/configuration-infrastructure.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally platform-neutral, focusing on Azure networking concepts and permissions. However, in the section about DNS server changes, restart instructions reference Azure PowerShell cmdlets (Stop-AzApplicationGateway and Start-AzApplicationGateway) without mentioning equivalent Azure CLI commands or portal actions. This places Windows/PowerShell tooling first and may create friction for Linux/macOS users who prefer Azure CLI or portal.
Recommendations
- Add Azure CLI examples alongside PowerShell for restarting Application Gateway after DNS changes.
- Mention that the Azure Portal can also be used for restart operations, if applicable.
- Ensure all procedural instructions reference both PowerShell and CLI (or portal) options where possible.
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 steps for Application Gateway for Containers and includes both Linux and Windows-specific log filtering commands. However, the Windows example (using 'findstr') is presented after the Linux example (using 'grep'), and both are clearly labeled. There are no exclusive Windows tools or patterns, and all critical commands are cross-platform. The overall bias is minimal, with only minor ordering preference.
Recommendations
- Ensure both Linux and Windows examples are given equal prominence, possibly by using tabbed code blocks or parallel presentation.
- Explicitly mention macOS compatibility where relevant (since macOS uses Unix-like tools).
- Add a brief note that all kubectl commands are cross-platform and clarify any OS-specific syntax differences.
- Consider listing Windows and Linux commands side-by-side for easier comparison.
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, which may favor Windows users. Helm installation instructions are given for both Windows and Linux, but Windows is listed first. There are no missing Linux examples, and Bash usage is acknowledged. The overall parity is good, but Windows examples and tools are often presented before Linux equivalents.
Recommendations
- Alternate the order of Windows and Linux examples so Linux is not always second.
- Explicitly mention Bash or Linux shell alternatives where Azure CLI is used, since Azure CLI is cross-platform.
- Consider grouping CLI and PowerShell examples together, or clarify that Azure CLI commands work on all platforms.
- Add a brief note at the start clarifying that all Azure CLI commands are cross-platform and can be run on Linux/macOS/Windows.
- For Helm installation, list Linux instructions first or equally prominent, since many Kubernetes admins use Linux/macOS.
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 is given equal prominence and is included in nearly every major step. In some sections, PowerShell examples are shown before or alongside Azure CLI, which may create friction for Linux/macOS users. However, all critical tasks can be completed using Azure CLI, and no Windows-only tools or patterns are required. There are no missing Linux examples, as Azure CLI is cross-platform and is the primary tool for most steps.
Recommendations
- Consider making Azure CLI the default or primary example in each section, with PowerShell as an optional tab for Windows users.
- Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Where PowerShell is used, ensure that equivalent Azure CLI commands are always provided and shown first.
- Explicitly note that PowerShell examples are for Windows environments, and CLI is preferred for Linux/macOS.
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 tasks, but PowerShell examples are included in nearly every section, and are often presented immediately after CLI examples. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows, and its inclusion throughout the guide may signal a Windows bias. Additionally, PowerShell examples are sometimes given equal prominence to CLI, rather than being secondary or in a dedicated Windows section.
Recommendations
- Clearly indicate that Azure CLI is the recommended, cross-platform tool for Linux/macOS users, and Azure PowerShell is primarily for Windows users.
- Consider grouping PowerShell examples in a dedicated 'Windows/PowerShell' tab or section, rather than interleaving them throughout the guide.
- For each task, ensure the Azure CLI example is shown first, and PowerShell is presented as an alternative for Windows users.
- Add explicit notes clarifying that Azure CLI commands work on Linux/macOS, and that PowerShell is optional for Windows environments.
- Review the use of PowerShell in resource group deletion and cluster updates—if CLI covers all scenarios, PowerShell can be moved to a supplemental section.
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 PowerShell examples are always shown immediately after CLI, and Windows-specific installation instructions for Helm are presented before Linux. The PowerShell examples are extensive and detailed, which may suggest a slight preference for Windows users. However, Linux parity is generally maintained, and all critical steps are achievable via CLI or Bash. The only minor bias is the ordering and emphasis of Windows tools.
Recommendations
- Alternate the order of Azure CLI and PowerShell examples, or clarify that Azure CLI is cross-platform and preferred for Linux/macOS.
- Present Linux Helm installation instructions before Windows, or group them equally.
- Explicitly mention that Azure CLI commands work on Linux/macOS and Bash, and highlight Bash as a primary shell for non-Windows users.
- Consider adding macOS-specific Helm installation instructions for completeness.
Application Gateway
Troubleshoot Application Gateway for Containers
...cation-gateway/for-containers/troubleshooting-guide.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally provides cross-platform guidance, with most examples using standard Kubernetes CLI commands. In the section for collecting logs, both Linux and Windows command examples are provided, but the Linux example is shown first, followed by the Windows example. No significant bias is present, and Linux users are fully supported.
Recommendations
- Maintain the current approach of providing both Linux and Windows command examples where platform-specific differences exist.
- Consider using tabbed code blocks or clearer headings to further emphasize parity and ease of use for both platforms.
- Continue to ensure that all critical troubleshooting steps include Linux/macOS-compatible instructions.
Application Gateway
Azure Application Gateway infrastructure configuration
...es/application-gateway/configuration-infrastructure.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally platform-neutral and focuses on Azure infrastructure concepts. However, in the section about DNS server changes, restart instructions reference Azure PowerShell cmdlets (Stop-AzApplicationGateway and Start-AzApplicationGateway) with direct links, but do not mention or provide Azure CLI equivalents. This is a minor bias, as Azure CLI is cross-platform and widely used on Linux/macOS. No other Windows-specific tools, patterns, or examples are present, and the page does not prioritize Windows tools or concepts elsewhere.
Recommendations
- Add Azure CLI examples alongside PowerShell cmdlets for restarting Application Gateway instances, e.g., az network application-gateway stop/start.
- Wherever Azure PowerShell is referenced, provide Azure CLI equivalents or clarify that both tools can be used.
- Ensure future procedural steps or examples are given in both Azure CLI and PowerShell, or reference the relevant documentation for both.
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 is given equal prominence and is presented in many sections. In some cases, PowerShell is listed before CLI, and there are no explicit Linux/macOS-specific notes or parity checks. The PowerShell examples are Windows-centric, and while Azure CLI is cross-platform, the documentation does not clarify this or provide guidance for Linux/macOS users. There are no Linux-specific tools or shell patterns (e.g., Bash, zsh) mentioned, and the documentation assumes familiarity with PowerShell in several places.
Recommendations
- Clarify that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- Add explicit notes or tabs indicating that PowerShell is Windows-only, and recommend Azure CLI for Linux/macOS.
- Consider listing Azure CLI examples first in each section to reduce Windows-first bias.
- Where PowerShell is used, provide Bash shell equivalents if there are any subtle differences (e.g., environment variable syntax).
- Add a brief section in prerequisites noting that Azure PowerShell is Windows-centric and that Linux/macOS users should use Azure CLI.
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 often presents PowerShell examples immediately after CLI, and includes Windows-specific tooling (e.g., winget for Helm installation). While Linux installation instructions for Helm are present, Windows-specific tools are mentioned first or exclusively (winget). The PowerShell examples are consistently present, which may create friction for Linux/macOS users who do not use PowerShell. However, all critical tasks are also covered with Azure CLI and Bash-compatible commands, so Linux users can complete the quickstart.
Recommendations
- When listing installation options for Helm, mention Linux/Bash methods before Windows-specific tools like winget, or present them side-by-side.
- Consider adding macOS-specific Helm installation instructions for parity.
- Clarify that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- Where PowerShell is used, explicitly state that it is primarily for Windows users, and that Azure CLI is recommended for Linux/macOS.
- Avoid presenting Windows-specific tools (e.g., winget) before Linux equivalents unless Windows is the primary audience.
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 is presented second and uses the Windows 'findstr' command. All other troubleshooting steps use cross-platform tools (kubectl, helm) and shell syntax, and there are no Windows-specific tools or patterns prioritized. The bias is minor and limited to the log filtering example.
Recommendations
- Ensure Linux and Windows examples are presented side-by-side or in tabs, with equal prominence.
- Clarify that all commands except the log filtering example are cross-platform.
- Consider providing macOS-specific notes if there are any differences.
- Explicitly state that the majority of commands are platform-agnostic and only the log filtering command differs.
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 consistently presents PowerShell examples immediately after CLI, and in some cases, Windows-specific installation instructions (e.g., Helm via winget) are given before Linux equivalents. The PowerShell examples are Windows-centric, and the CLI examples are cross-platform but shown first. There are no Linux-specific Azure CLI workarounds or Bash-specific notes beyond Helm installation. The bias is minor and does not prevent Linux/macOS users from completing the tasks.
Recommendations
- Ensure Linux installation instructions are presented with equal prominence and detail as Windows instructions.
- Add explicit Bash/Linux example tabs for Azure CLI usage, clarifying that CLI commands work on Linux/macOS and in Azure Cloud Shell.
- Consider showing Azure CLI (cross-platform) examples first, and PowerShell (Windows-only) examples second.
- Where PowerShell is mentioned, clarify its Windows focus and suggest CLI for Linux/macOS users.
- Expand Linux/macOS troubleshooting notes where relevant (e.g., permissions, package managers).
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 generally platform-neutral, focusing on Azure Application Gateway concepts and settings. However, there are two notable instances of Windows bias: (1) references to Windows-specific authentication protocols (NTLM, Kerberos) and links to Windows/IIS documentation for troubleshooting, and (2) Windows authentication guidance is provided before any mention of Linux equivalents or generic approaches. No PowerShell or Windows command-line examples are present, and most configuration is described in terms of Azure portal/API, which is cross-platform.
Recommendations
- When referencing authentication troubleshooting, include guidance for Linux-based backend servers (e.g., Apache, NGINX) and generic Kerberos/NTLM configuration.
- Provide links to platform-agnostic authentication documentation or Linux-specific resources alongside Windows/IIS links.
- Clarify that NTLM/Kerberos passthrough is relevant for Windows environments, and suggest alternatives or note limitations for Linux-based backends.
- Ensure troubleshooting steps and examples are not exclusively Windows-focused, and add parity for Linux/macOS where applicable.
Application Gateway
Azure Application Gateway infrastructure configuration
...es/application-gateway/configuration-infrastructure.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is largely platform-neutral, focusing on Azure networking concepts and permissions. However, there is a minor bias in the section describing how to restart the Application Gateway after DNS changes, where only Azure PowerShell cmdlets ([Stop-AzApplicationGateway] and [Start-AzApplicationGateway]) are mentioned, with no Azure CLI or Linux/macOS example provided. Azure PowerShell is most commonly used on Windows, so mentioning it exclusively can create friction for Linux/macOS users.
Recommendations
- Add Azure CLI examples alongside PowerShell for operations such as restarting the Application Gateway (e.g., az network application-gateway stop/start).
- When referencing Azure tools or commands, provide both PowerShell and CLI options, or explicitly state that both are supported.
- Ensure that any procedural instructions (such as changing subnets or restarting resources) include cross-platform guidance.
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 includes both Linux and Windows-specific instructions for filtering logs. However, the Windows example (using 'findstr') is presented after the Linux example (using 'grep'), and both are clearly labeled. The overall content is platform-neutral, but there is a slight bias in the explicit separation and labeling of Windows and Linux commands, with the Linux example shown first. No critical troubleshooting steps are Windows-only, and all commands are available for Linux/macOS users.
Recommendations
- Ensure parity by always providing both Linux and Windows command examples side-by-side or in tabs, as done here.
- Consider adding macOS-specific notes if there are any subtle differences (though in this case, Linux commands work on macOS).
- Maintain clear labeling for platform-specific instructions to avoid confusion.
- If possible, provide a cross-platform command (e.g., using kubectl with built-in filtering) to minimize OS-specific steps.
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 is given equal prominence and sometimes appears before Linux-native alternatives. Azure PowerShell is primarily a Windows tool, and its inclusion as a main option alongside Azure CLI (which is cross-platform) may create friction for Linux/macOS users. There are no Linux-specific examples or explicit mentions of Linux/macOS compatibility, and PowerShell examples are presented in tabs, sometimes before CLI. However, all critical tasks can be completed using Azure CLI, which is cross-platform.
Recommendations
- Make Azure CLI the default or primary example in all sections, as it is cross-platform and preferred for Linux/macOS users.
- Clearly indicate that Azure PowerShell is Windows-centric and recommend Azure CLI for Linux/macOS users.
- Add explicit notes or guidance for Linux/macOS users where PowerShell is mentioned, clarifying that Azure CLI is fully supported.
- Consider removing PowerShell examples from sections where they do not add value for non-Windows users, or move them to secondary position.
- Add a brief section in prerequisites noting that Azure CLI is recommended for Linux/macOS, and provide installation links.