Scan Details - Linux-first Docs for Azure

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, which is primarily a Windows-centric tool, and by referencing PowerShell installation and usage instructions without mentioning cross-platform alternatives like Azure CLI or Bash. There are no Linux- or macOS-specific instructions or examples, and the PowerShell approach is presented before any mention of ARM templates, with no Azure CLI parity. This may hinder Linux or macOS users who prefer or require non-Windows tooling.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell command snippets, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that Azure PowerShell is available cross-platform, but also provide Bash or shell script examples where appropriate.
In sections where PowerShell is referenced, add a parallel section or tab for Azure CLI, and consider presenting both options side-by-side.
Include installation and usage instructions for Azure CLI alongside PowerShell, and link to relevant documentation for both.
Review all references to Windows-specific tools or patterns and ensure Linux/macOS users are equally supported in instructions and troubleshooting.
Consider adding a note at the top of the page clarifying that all examples are available in both PowerShell and Azure CLI, with links to both.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing a PowerShell automation example but omitting equivalent Linux shell (Bash) examples. The scripting section lists Azure CLI and PowerShell, but only the PowerShell script is shown inline, with no Bash or Linux-specific automation guidance. Additionally, there is no mention of Linux tools or workflows for certificate management, and the documentation does not provide parity in step-by-step examples for Linux users.

Recommendations:

Add Bash/Linux shell script examples for automating certificate binding, alongside PowerShell.
Provide explicit guidance or links for Linux users on how to generate and upload certificates (e.g., using OpenSSL).
Ensure that automation and scripting sections always include both Windows (PowerShell) and Linux (Bash/CLI) examples, or clearly indicate parity.
Reference Linux-specific documentation or workflows where relevant, especially in sections discussing application code or certificate management.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ missing_linux_example

Summary:

The documentation provides both Azure CLI and Azure PowerShell examples for retrieving outbound IP addresses, but PowerShell examples are given equal prominence to CLI, and there are no explicit Linux shell or Bash script examples beyond the use of Azure CLI. The documentation references 'Cloud Shell' without clarifying that it supports both Bash and PowerShell, and does not provide Linux-native alternatives for PowerShell commands. Additionally, outbound IPv6 support is noted as being available only for Windows apps, with no Linux parity.

Recommendations:

Clearly indicate when examples are cross-platform (e.g., Azure CLI) and when they are Windows-specific (e.g., PowerShell).
Provide explicit Bash or Linux-native command examples where possible, especially for common tasks like retrieving IP addresses.
When referencing 'Cloud Shell', clarify that both Bash and PowerShell environments are available and show equivalent commands for each.
If a feature (such as outbound IPv6 support) is Windows-only, explicitly mention the lack of Linux support and provide a roadmap or workaround if possible.
Avoid giving PowerShell examples equal prominence to CLI unless there is a clear need; prioritize cross-platform tools like Azure CLI.
Add a table or section summarizing command-line options for Windows (PowerShell), Linux (Bash), and cross-platform (Azure CLI) to improve parity and clarity.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

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

Recommendations:

Provide equivalent DNS cache clearing instructions for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo service nscd restart') and macOS (e.g., 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder').
When giving OS-specific commands, present them in a cross-platform table or list, or explicitly mention alternatives for Linux and macOS.
Review other troubleshooting and automation sections to ensure parity and inclusion of Linux/macOS where relevant.
Consider adding a note that the instructions apply to all major platforms, and clarify any platform-specific steps.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation demonstrates a Windows bias primarily by presenting .NET/ASP.NET (Windows-centric) code samples first and in greater detail, while not providing any explicit Linux-specific configuration or troubleshooting guidance. There are no examples or instructions for Linux command-line tools (such as Bash, OpenSSL, or curl) for certificate handling, nor is there any mention of Linux-specific behaviors or caveats. The focus on the X-ARR-ClientCert header and .NET-centric validation patterns further reinforces a Windows-oriented approach, even though App Service supports Linux hosting.

Recommendations:

Add Linux-specific command-line examples (e.g., using Bash, OpenSSL, or curl) for uploading, validating, or troubleshooting client certificates.
Include guidance or notes on differences in certificate handling between Windows and Linux App Service plans, if any.
Provide parity in code samples by including examples for popular Linux-first frameworks (e.g., Nginx, Apache, or Kestrel on Linux) and how to access/validate client certificates in those environments.
Explicitly mention that the provided instructions and code samples are cross-platform where applicable, or clarify any platform-specific limitations.
Consider reordering or balancing the presentation of code samples so that Windows and Linux (or cross-platform) approaches are given equal prominence.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page demonstrates a subtle Windows bias by referencing 'Windows Isolated v2' as the default/minimum charge in the 'regional deployment' section, without mentioning Linux equivalents or clarifying Linux support. There are no explicit Linux examples, nor is there mention of Linux-specific deployment considerations. However, the page does not provide any command-line examples (PowerShell, CLI, or otherwise), so it is not 'powershell_heavy' or missing Linux CLI examples. The bias is primarily in the ordering and defaulting to Windows terminology.

Recommendations:

Explicitly mention Linux support and pricing in the 'regional deployment' section, or clarify if the minimum charge applies to both Windows and Linux Isolated v2 plans.
Where Windows-specific SKUs or terminology are used (e.g., 'Windows Isolated v2'), provide the Linux equivalent or state if there is none.
Add a section or note about Linux compatibility and any differences in deployment or pricing.
Ensure that any future examples (scripts, CLI, etc.) include both Windows (PowerShell) and Linux (Bash/Azure CLI) variants.

Create pull request

Scan Information

Problematic Pages