Scan Details - Linux-first Docs for Azure

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page exhibits a Windows bias by providing command-line examples exclusively in Azure PowerShell, referencing installation of Azure PowerShell (which is most commonly associated with Windows environments), and omitting any examples using Azure CLI (which is cross-platform and more common on Linux/macOS). There are no Bash or Linux-native shell examples, and PowerShell is always presented as the primary or only scripting interface. No mention is made of Linux-specific tooling or workflows.

Recommendations:

Add equivalent Azure CLI (az) command examples alongside all Azure PowerShell examples, especially for resource creation and identity assignment.
Explicitly mention that Azure CLI is cross-platform and can be used from Linux, macOS, and Windows.
Where PowerShell installation is referenced, provide a parallel reference for installing Azure CLI.
Consider including Bash script examples or at least showing CLI commands in a Bash context.
Review and update language to avoid implying PowerShell is the only or default automation tool.
Add a section or note clarifying that all operations can be performed from Linux environments using Azure CLI and ARM templates.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by prioritizing PowerShell scripting in the 'Automate with scripts' section, referencing Azure CLI only as a link (without inline examples), and omitting explicit Linux or Bash scripting examples. The only code sample shown is PowerShell, which is more familiar to Windows users. While there is a brief mention of a Linux Node.js configuration guide, the main automation and scripting guidance is Windows-centric.

Recommendations:

Provide inline Azure CLI examples alongside PowerShell, not just as links, to ensure parity for Linux and cross-platform users.
Include Bash scripting examples for certificate upload and binding, especially for common Linux workflows.
When referencing automation, present CLI and PowerShell examples side-by-side or in parallel sections, rather than PowerShell-only.
Expand the 'Automate with scripts' section to explicitly mention and demonstrate Linux-compatible tools and commands.
Review screenshots and UI instructions to ensure they are not overly tailored to Windows environments (e.g., file dialogs, path formats).

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a Windows bias primarily by focusing on .NET/ASP.NET (Windows-centric frameworks) in code samples, providing detailed Windows/ASP.NET examples before other platforms, and referencing Windows-specific concepts (such as the HttpRequest.ClientCertificate property and .NET middleware) without equivalent Linux/Unix-native patterns. There is no mention of Linux command-line tools (e.g., OpenSSL) for certificate handling, and the overall structure assumes familiarity with Windows development environments.

Recommendations:

Add Linux/Unix-native command-line examples (e.g., using OpenSSL) for generating and inspecting client certificates.
Include examples or references for configuring mutual TLS in popular Linux web servers (e.g., Nginx, Apache) when running App Service on Linux.
Balance the order of code samples so that non-Windows stacks (Node.js, Python, Java) are presented before or alongside Windows/.NET examples.
Explicitly mention any platform differences in how client certificates are handled in App Service on Linux vs. Windows.
Provide guidance for validating client certificates using common Linux tools or scripting languages (e.g., Bash, OpenSSL, curl) in addition to .NET/Windows approaches.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias in several ways: PowerShell examples are provided alongside Azure CLI, but there are no Bash or Linux shell equivalents for PowerShell commands. Outbound IPv6 support is noted as available only for Windows apps, with no Linux parity. In command examples, PowerShell is presented as an alternative to Azure CLI, but no Linux-native scripting or command-line examples are given. The documentation references Windows-specific features and limitations before mentioning Linux, and Linux-specific guidance is minimal or missing.

Recommendations:

For every PowerShell example, provide an equivalent Bash/Linux shell example, especially for commands that retrieve app properties.
Explicitly state Linux support or limitations in all relevant sections, not just in IPv6 outbound support.
When listing command-line options, present Azure CLI (cross-platform) examples first, followed by PowerShell, and include Bash where appropriate.
Clarify in all relevant sections whether features or commands apply to both Windows and Linux App Service plans.
Add troubleshooting and verification steps for Linux environments, such as using dig or host commands in addition to nslookup.
Where outbound IPv6 is not supported for Linux, provide a roadmap or workaround, or link to relevant tracking issues.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by referencing PowerShell and Windows-centric tools and patterns more prominently than Linux equivalents. For example, it directs users to PowerShell-based configuration guides, mentions PowerShell before CLI or REST, and omits explicit Linux/Unix shell or scripting examples. There are no Linux-specific instructions or parity in command-line examples, and the 'Next steps' section links only to a PowerShell-based configuration guide.

Recommendations:

Provide equivalent Linux/Unix shell (bash/az CLI) examples alongside or before PowerShell examples.
Ensure that configuration steps are documented for both PowerShell and Azure CLI, with clear parity and equal prominence.
Update 'Next steps' to include links to both PowerShell and CLI (az) configuration guides.
Wherever PowerShell is mentioned, also mention the corresponding CLI or REST API approach, and provide direct links to those guides.
Avoid implying that PowerShell is the primary or only supported method for configuration; clarify that both Windows and Linux users are supported equally.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page generally avoids platform-specific instructions, but in the troubleshooting section, it provides a Windows-specific command ('ipconfig /flushdns') for clearing the DNS cache without mentioning the equivalent command for Linux or macOS. No Linux or cross-platform alternatives are provided, and the Windows command is presented as the only example.

Recommendations:

When mentioning platform-specific commands (such as clearing DNS cache), provide equivalent instructions for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo /etc/init.d/nscd restart') and macOS (e.g., 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder').
Use language that is inclusive of all major platforms, such as 'On Windows, use ...; on Linux, use ...; on macOS, use ...'.
Review the documentation for any other subtle Windows-first assumptions and ensure parity by including Linux/macOS equivalents wherever relevant.
Consider adding a short section or callout box for common troubleshooting steps across different operating systems.

Create pull request

Bias Types:

⚠️ windows_tools

⚠️ missing_linux_example

Summary:

The documentation is generally platform-neutral, focusing on Azure Portal UI steps. However, in the troubleshooting section, it specifically mentions the Windows command 'ipconfig /flushdns' for clearing DNS cache, without providing an equivalent command for Linux or macOS users. No Linux or cross-platform alternatives are mentioned, and no Linux command-line examples are given.

Recommendations:

When suggesting command-line tools (such as for clearing DNS cache), provide equivalent commands for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo resolvectl flush-caches') and macOS (e.g., 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder').
Explicitly mention that the instructions apply to all platforms, or provide platform-specific notes where relevant.
Review other troubleshooting or command-line steps to ensure parity between Windows, Linux, and macOS.
Consider adding a short section or callout box for cross-platform DNS cache clearing instructions.

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 provide explicit instructions or examples for Linux users. The use of GitHub Codespaces and Azure Developer CLI (azd) is cross-platform, but there are no Linux-specific terminal commands, deployment notes, or troubleshooting tips. The documentation also references 'Open in Browser' and Swagger UI navigation in a way that may be more familiar to Windows users. There are no references to Windows-only tools, but the lack of explicit Linux parity is a subtle form of bias.

Recommendations:

Explicitly state that all commands and steps work on Linux, macOS, and Windows, and mention any OS-specific prerequisites if needed.
Provide example terminal commands for both Windows (PowerShell/CMD) and Linux/macOS (bash/zsh) when relevant, especially for deployment, file navigation, or environment variable management.
Include troubleshooting tips for common Linux issues (e.g., permissions, case sensitivity, .NET SDK installation).
Clarify that GitHub Codespaces and Azure Developer CLI are cross-platform, and provide links to installation guides for Linux users.
If referencing UI actions like 'Open in Browser', note how to do this from a Linux terminal (e.g., using xdg-open or open commands).

Create pull request

Scan Information

Problematic Pages