Scan Details - Linux-first Docs for Azure

1139

Pages Scanned

Pages Flagged

1139

Changed Pages

0.4%

% Pages Flagged

Scan Information

Started At: 2025-07-28 00:00:54

Finished At: 2025-07-28 00:04:49

Status: completed

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

Current Phase: discovery

Problematic Pages

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

⚠️ windows_tools

Summary:

The documentation page demonstrates a Windows bias by providing command-line examples exclusively in Azure PowerShell, a tool most commonly associated with Windows environments. There are no examples using Azure CLI (which is cross-platform and preferred by many Linux users), nor are there any Bash or Linux shell script examples. The PowerShell approach is presented before ARM templates, and there is no mention of Linux-specific workflows or tools. Installation instructions and references are all for Azure PowerShell, with no equivalent guidance for Linux users.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell command sequences, as Azure CLI is cross-platform and widely used on Linux.
Include Bash shell script examples where appropriate, especially for automation scenarios.
When listing command-line options, present Azure CLI and PowerShell in parallel, or at least mention both, rather than only PowerShell.
Provide installation and setup instructions for Azure CLI alongside PowerShell, with links to Linux-specific documentation.
Review references and links to ensure Linux users are not excluded (e.g., avoid only linking to PowerShell samples).
Consider adding a section or note explicitly stating that all operations can be performed from Linux environments using Azure CLI or ARM templates.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation shows a moderate Windows bias. The only platform-specific examples for accessing the client certificate in application code are for ASP.NET Core and ASP.NET Web Forms, both of which are traditionally Windows-centric frameworks. The initial mention of how to access the client certificate property is for ASP.NET, with Linux/Unix-agnostic stacks (Node.js, Java, Python) following. There are no explicit Linux shell or configuration examples, and the document does not mention Linux-specific tools or patterns for certificate handling. The Azure CLI and Bicep/ARM examples are cross-platform, but the application code samples and the ordering of explanations favor Windows-first technologies.

Recommendations:

Add explicit Linux/Unix shell (bash) examples for enabling client certificates using Azure CLI, including usage from a Linux terminal.
Include examples for popular Linux web servers (e.g., Nginx, Apache) on how to forward client certificates to the application, especially for self-hosted scenarios.
Provide parity in application code samples by including examples for popular Linux-first frameworks (e.g., FastAPI for Python, Spring Boot for Java, Express for Node.js) and clarify any OS-specific differences.
Reorder the 'Access the client certificate' section to mention cross-platform approaches (e.g., via HTTP headers) before Windows-specific frameworks.
Explicitly state that the Azure CLI and Bicep/ARM approaches are cross-platform and can be used from Linux, macOS, and Windows.

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 and referencing Azure CLI only as a link, without providing direct Linux/Unix shell examples or parity in scripting walkthroughs. The page also lacks explicit Linux or cross-platform command-line instructions, and the scripting focus is on Windows tools and patterns.

Recommendations:

Provide direct Azure CLI command examples inline, not just as links, to ensure parity with PowerShell examples.
Include Linux/Unix shell (bash) scripting examples for certificate upload and binding operations.
Explicitly mention that the steps can be performed on both Windows and Linux, and clarify any platform-specific differences.
Add references or links to Linux-specific documentation where relevant, such as using OpenSSL to generate .pfx files.
Ensure that automation and scripting sections always include both PowerShell and CLI/bash examples side by side.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation provides a troubleshooting step for clearing the DNS cache that only references the Windows-specific command 'ipconfig /flushdns', without mentioning the equivalent commands for Linux or macOS. No PowerShell or Windows tool bias is present elsewhere, but this omission results in a subtle Windows-first and missing Linux example bias.

Recommendations:

When suggesting DNS cache clearing, include equivalent commands 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').
Wherever platform-specific troubleshooting is mentioned, provide parity for Linux and macOS users, or link to official documentation for those platforms.
Consider a short note or table listing common DNS cache flush commands for all major platforms to ensure inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page exhibits a subtle 'windows_first' bias by referencing Windows-specific SKUs (such as 'Windows Isolated v2') as the default or minimum charge in the App Service plan, without mentioning Linux equivalents or clarifying Linux support. There are no explicit PowerShell examples or Windows-only tools, but the language and examples assume Windows as the primary platform, with no mention of Linux options or parity.

Recommendations:

Explicitly mention Linux support and available SKUs (e.g., 'Linux Isolated v2') where Windows SKUs are referenced.
Clarify whether the minimum charge applies to both Windows and Linux App Service plans, or provide details for both.
Add examples or notes for Linux-based deployments if there are differences or additional considerations.
Ensure that screenshots, instructions, and terminology are platform-neutral or provide both Windows and Linux perspectives where relevant.

Create pull request

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