Scan Details - Linux-first Docs for Azure

1012

Pages Scanned

Pages Flagged

1012

Changed Pages

0.4%

% Pages Flagged

Scan Information

Started At: 2025-07-23 00:00:11

Finished At: 2025-07-23 00:04:42

Status: completed

Target URL: https://github.com/MicrosoftDocs/azure-docs/tree/main/articles

Current Phase: discovery

Problematic Pages

Bias Types:

⚠️ powershell_heavy

⚠️ windows_tools

⚠️ missing_linux_example

⚠️ windows_first

Summary:

The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for command-line operations, referencing the installation of Azure PowerShell (which is most commonly used on Windows), and omitting equivalent Azure CLI (cross-platform) or Bash examples. There are no Linux- or macOS-specific instructions, and PowerShell is presented as the default scripting tool for automation, with no mention of alternatives. This may disadvantage users on Linux or macOS, or those who prefer Azure CLI.

Recommendations:

Add Azure CLI examples alongside all PowerShell examples for creating and managing managed identities, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that Azure PowerShell can be used cross-platform, but also provide Bash or shell script equivalents where appropriate.
When listing automation options, present Azure CLI and PowerShell together, or list Azure CLI first to avoid the impression of Windows-first bias.
Include notes or links for Linux/macOS users on how to install and use the Azure CLI and/or PowerShell Core on their platforms.
Where possible, provide sample ARM/Bicep templates with deployment instructions using both Azure CLI and PowerShell.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias by providing a PowerShell script for automation but omitting equivalent Bash or Linux shell examples. The automation section lists Azure CLI and PowerShell, but only the PowerShell script is shown inline, with no Bash/Linux script or example. There are no explicit Linux-specific instructions or screenshots, and the general workflow assumes portal-based (GUI) steps, which are platform-agnostic but often more familiar to Windows users. The only mention of Linux is a reference to a separate Node.js guide, not present in this document.

Recommendations:

Add Bash or Linux shell script examples for automating certificate binding, alongside PowerShell.
Provide explicit Azure CLI command examples inline, not just as links.
Include Linux-specific notes or screenshots where relevant, such as uploading certificates from Linux systems.
Ensure parity in automation instructions by treating CLI and PowerShell equally, and avoid presenting PowerShell first or exclusively.
Reference Linux and cross-platform tools or workflows where appropriate, not just Windows-centric ones.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by prioritizing ASP.NET (Core and Web Forms) code samples, which are primarily Windows-centric technologies, and by referencing Windows-specific request properties (e.g., HttpRequest.ClientCertificate). There are no explicit Linux command-line examples (such as Bash or shell commands), and the documentation does not discuss Linux-specific certificate handling or tools. The Azure CLI and Bicep/ARM sections are cross-platform, but the application code samples and explanations are heavily skewed toward Windows development patterns and frameworks.

Recommendations:

Add Linux-specific examples, such as using Bash or OpenSSL commands to test mutual TLS connections or to inspect client certificates.
Include code samples for popular Linux web frameworks (e.g., Nginx, Apache, or Kestrel on Linux) showing how to access and validate client certificates.
Clarify that the .NET code samples are cross-platform when run on .NET Core, and provide guidance for running them on Linux-based App Service plans.
Mention and provide examples of Linux-native tools (such as curl with client certificates, or OpenSSL s_client) for testing mutual TLS.
Balance the order of examples so that Linux and cross-platform approaches are presented alongside or before Windows-centric ones.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page provides a troubleshooting step for clearing the DNS cache that only references the Windows-specific ipconfig /flushdns command, without mentioning the equivalent commands for Linux or macOS. No Linux or cross-platform command-line examples are given, and the only OS-specific tool mentioned is for Windows.

Recommendations:

When providing troubleshooting steps involving command-line tools, include 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`) alongside the Windows example.
Wherever possible, use cross-platform language or provide parallel instructions for all major operating systems.
Review the documentation for other implicit Windows-first assumptions and ensure parity in guidance for Linux and macOS users.

Create pull request

No problematic pages found in this scan. All pages appear to be Linux-friendly! 🐧