Scan Details - Linux-first Docs for Azure

1246

Pages Scanned

Pages Flagged

1246

Changed Pages

0.4%

% Pages Flagged

Scan Information

Started At: 2025-07-30 00:00:55

Finished At: 2025-07-30 00:05:24

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 used on Windows. There are no examples using cross-platform tools such as Azure CLI or Bash scripts, and no mention of Linux or macOS workflows. PowerShell is presented as the primary automation method, with no parity for Linux users. The structure also places PowerShell instructions before ARM template examples, and there is no guidance for using these features from a Linux or macOS environment.

Recommendations:

Add equivalent Azure CLI examples for all PowerShell command sequences, as Azure CLI is cross-platform and widely used on Linux and macOS.
Explicitly mention that both Azure PowerShell and Azure CLI can be used, and provide links to installation guides for both.
Include Bash shell script examples where appropriate, especially for automation scenarios.
Reorder sections or provide parallel sections so that PowerShell and CLI examples are presented together, or alternate which comes first.
Add a note or section on using these features from Linux/macOS environments, including any prerequisites or differences.
Ensure that references to 'installing tools' include both PowerShell and CLI, not just PowerShell.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ powershell_heavy

⚠️ windows_tools

Summary:

The documentation demonstrates a moderate Windows bias, particularly in the application code samples and terminology. The .NET/ASP.NET (Windows-centric) examples are presented first and in greater detail, with explicit references to Windows-specific properties and patterns. There is a lack of Linux shell or OpenSSL command-line examples for certificate management, and the documentation assumes the use of Azure Cloud Shell (which is cross-platform but often defaults to PowerShell). The focus on .NET and Windows-native certificate handling precedes or outweighs coverage of Linux-native approaches.

Recommendations:

Add explicit Linux command-line examples (e.g., using bash and OpenSSL) for generating, inspecting, and handling client certificates.
Include examples for configuring mutual TLS in popular Linux web servers (such as Nginx and Apache) in addition to .NET/ASP.NET.
Clarify that the Azure CLI can be used from any platform, and provide bash/zsh syntax where appropriate.
Balance the order of code samples so that Linux-friendly stacks (Node.js, Python, Java) are not always after Windows/.NET examples.
Mention Linux-native certificate stores and tools (such as update-ca-certificates, certutil, or OpenSSL) where relevant.
Where possible, provide parity in troubleshooting and validation steps for both Windows and Linux environments.

Create pull request

Bias Types:

⚠️ powershell_heavy

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page demonstrates a Windows bias primarily in the automation section, where both Azure CLI and PowerShell are mentioned, but only a PowerShell script is directly embedded and shown. There are no explicit Linux shell (bash) examples or references to Linux-native tools. The documentation does not provide parity in scripting examples for Linux users, and the PowerShell script is highlighted more prominently than the Azure CLI link. Additionally, the use of .pfx files (a Windows-centric certificate format) is mentioned without referencing Linux-friendly alternatives or conversion steps.

Recommendations:

Add explicit bash or shell script examples for Linux users in the automation section, alongside PowerShell.
Embed or link to Azure CLI scripts as prominently as PowerShell scripts.
Mention Linux-native certificate formats (such as .pem) and provide guidance or links on converting between .pfx and .pem.
Ensure that any references to tools or workflows (such as uploading certificates) include Linux command-line equivalents or instructions.
Review screenshots and UI instructions to ensure they are not overly Windows-centric, and add notes for Linux/macOS users where appropriate.

Create pull request

Bias Types:

⚠️ windows_first

⚠️ missing_linux_example

Summary:

The documentation page is generally cross-platform and avoids explicit Windows or PowerShell bias in its main instructions. However, in the troubleshooting section, when suggesting how to clear the DNS cache, only the Windows-specific command ('ipconfig /flushdns') is mentioned, with no equivalent Linux or macOS instructions. This is an example of 'windows_first' and 'missing_linux_example' bias.

Recommendations:

When providing troubleshooting steps that involve OS-specific commands (such as clearing the DNS cache), include 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').
Wherever possible, avoid assuming the user is on Windows. If a command is OS-specific, present alternatives for all major platforms, or link to platform-specific instructions.
Consider adding a short note or a tabbed section for clearing DNS cache on Windows, Linux, and macOS to ensure parity and inclusivity.

Create pull request

Bias Types:

⚠️ windows_first

Summary:

The documentation page exhibits a 'windows_first' bias by referencing Windows-specific SKUs (e.g., 'Windows Isolated v2') as the default or minimum charge in the regional deployment section, without mentioning Linux equivalents or clarifying Linux support. There are no explicit PowerShell or Windows-only tool examples, but the mention of Windows pricing and SKUs before any Linux context may suggest to readers that Windows is the primary or default platform.

Recommendations:

Explicitly mention Linux support and pricing/SKU details alongside Windows wherever applicable, especially in deployment and billing sections.
Clarify whether the minimum instance charge applies to both Windows and Linux App Service plans, or provide Linux-specific details if different.
Add examples or notes for Linux-based App Service Environments where relevant, to ensure parity and inclusivity.
Review all references to platform-specific features or pricing to ensure both Windows and Linux users are equally informed.

Create pull request

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