Scan Details - Linux-first Docs for Azure

Bias Types:

⚠️ powershell_heavy

⚠️ missing_linux_example

⚠️ windows_tools

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by providing only Azure PowerShell examples for command-line operations, with no mention or examples of Azure CLI (which is cross-platform and commonly used on Linux/macOS). Instructions for installing and using PowerShell are included, but there are no equivalent steps or code snippets for Linux users. The documentation refers to 'PowerShell samples' and does not mention Bash, shell scripting, or Linux-specific tools. This may make it less accessible or intuitive for Linux users.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell code snippets, including resource creation, identity assignment, and updates.
Include installation and usage instructions for Azure CLI, especially for Linux/macOS environments.
Where referencing 'PowerShell samples', also link to or mention Azure CLI samples if available.
In step-by-step instructions, present both PowerShell and CLI options, or indicate which are cross-platform.
Review terminology to ensure it is inclusive of non-Windows environments (e.g., avoid assuming PowerShell is the default shell).

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation demonstrates a Windows bias by providing PowerShell as the only CLI example for checking Application Gateway settings, exclusively recommending Fiddler (a Windows-centric tool) for network debugging, and referencing Windows installation patterns (e.g., 'Run as administrator'). There are no Linux or cross-platform CLI examples, nor are Linux-friendly tools (such as tcpdump, curl, or Wireshark) mentioned. The guidance assumes a Windows environment and does not address Linux users' needs.

Recommendations:

Provide Azure CLI and/or Azure Resource Manager (ARM) template examples for checking Application Gateway settings, as these are cross-platform and work on Linux, macOS, and Windows.
Include Linux-friendly network debugging tools such as tcpdump, Wireshark, or curl, and provide example commands for capturing and analyzing HTTP(S) traffic on Linux.
When referencing installation steps, include Linux equivalents (e.g., using package managers or running as root/sudo).
Explicitly state that Fiddler is just one option and suggest alternatives for non-Windows users.
Ensure that screenshots and walkthroughs are not exclusively based on Windows UI/tools, or provide parallel Linux examples where applicable.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page exhibits a Windows bias by providing only Azure PowerShell examples for critical configuration steps, referencing PowerShell before (or instead of) cross-platform tools like Azure CLI, and omitting Linux-specific or cross-platform command-line examples. The 'Next steps' section also directs users exclusively to a PowerShell-based guide, reinforcing the Windows-centric approach. There are no CLI, Bash, or Linux-native instructions, which may hinder Linux users or those preferring cross-platform tooling.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell commands, especially for referencing Key Vault secrets and configuring Application Gateway listeners.
When listing tools or approaches, mention Azure CLI and ARM/Bicep templates alongside PowerShell, and avoid presenting PowerShell as the primary or sole method.
Include Bash shell examples or notes for Linux/macOS users where applicable.
Update the 'Next steps' section to include links to CLI-based and ARM/Bicep-based guides, not just PowerShell.
Where screenshots or UI instructions are given, clarify that the steps are platform-agnostic or provide notes for Linux users if there are differences.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

⚠️ powershell_heavy

Summary:

The documentation page does not provide any command-line examples, but the only 'Next steps' link points to a PowerShell-based tutorial, which is Windows-centric. There is no mention of Linux tools, Bash, or cross-platform Azure CLI usage, and the documentation implicitly assumes a Windows/PowerShell workflow.

Recommendations:

Add links to equivalent tutorials using Azure CLI (az), which is cross-platform and commonly used on Linux.
Include explicit examples or references for configuring Application Gateway redirects using Bash or Linux environments.
Ensure that 'Next steps' sections offer both PowerShell and Azure CLI (or ARM template) options, with neither being prioritized over the other.
Mention that Application Gateway can be managed from any OS and provide guidance for users on Linux or macOS.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias by providing Azure PowerShell examples alongside Azure CLI, but does not offer equivalent Linux shell or Bash scripting examples. PowerShell commands are presented as a primary method for retrieving outbound IP addresses, and outbound IPv6 support is noted as available only for Windows apps, with no Linux parity. There is also a lack of explicit Linux-focused guidance or troubleshooting, and the documentation does not mention Linux-specific tools or patterns.

Recommendations:

Provide Bash or Linux shell script examples for all command-line operations, especially where PowerShell is shown.
Clarify the availability and limitations of features (such as outbound IPv6) for both Windows and Linux App Service apps, and provide guidance or workarounds for Linux users.
When listing command-line examples, present Azure CLI (cross-platform) examples before PowerShell, and clearly indicate which platforms each example is intended for.
Include troubleshooting steps or notes relevant to Linux users, such as differences in DNS tools or network stack behavior.
Where PowerShell is referenced, offer equivalent Linux-native alternatives (e.g., Bash, curl, dig, jq) for common tasks.

Create pull request

Bias Types:

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation assumes a development environment that is compatible with .NET and Azure App Service, but it does not explicitly mention or provide examples for Linux-based development environments or deployment scenarios. The instructions reference GitHub Codespaces (which is Linux-based) and the Azure Developer CLI (which is cross-platform), but there are no explicit Linux shell commands, nor is there any mention of Linux-specific considerations. All code and deployment steps are shown in a way that is neutral but implicitly assumes familiarity with Windows/.NET workflows. There are no PowerShell-specific commands, but the lack of Linux/Bash-specific examples or troubleshooting tips may disadvantage Linux users.

Recommendations:

Explicitly mention that the tutorial works on both Windows and Linux environments, and clarify any OS-specific prerequisites.
Provide Bash shell equivalents for any terminal commands, especially for deployment and running the app.
Include notes or troubleshooting tips for common Linux development environments (e.g., WSL, Ubuntu, Docker containers).
If any steps differ for Linux (such as file paths, environment variable syntax, or permissions), call these out in side notes or callouts.
Add a section or appendix with Linux-specific setup instructions for .NET and Azure CLI if not already covered elsewhere.

Create pull request

Scan Information

Problematic Pages