About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_first
⚠️
powershell_heavy
⚠️
windows_tools
Summary:
The documentation demonstrates a moderate Windows bias. It provides detailed C#/.NET (ASP.NET Core and Web Forms) code samples first and in greater depth compared to other languages. The .NET samples are inherently Windows-centric, and the use of terms and patterns like 'HttpRequest.ClientCertificate' and 'System.Web' are specific to Windows/IIS environments. There is no mention of Linux-specific tools or command-line patterns (e.g., bash, OpenSSL, curl), and the documentation does not provide Linux shell or configuration examples for mutual TLS setup. The Azure CLI and Bicep/ARM examples are cross-platform, but the lack of Linux-focused troubleshooting, validation, or deployment steps (such as using OpenSSL to test mutual TLS) further highlights the bias.
Recommendations:
- Add Linux-specific examples for validating mutual TLS, such as using OpenSSL or curl to test client certificate authentication.
- Provide equivalent shell (bash) commands for enabling client certificates and configuring exclusion paths, in addition to Azure CLI.
- Include troubleshooting steps or validation techniques that are common in Linux environments (e.g., using tcpdump, OpenSSL s_client).
- Balance the order of language samples, perhaps starting with a cross-platform language (like Node.js or Python) before Windows-centric .NET.
- Explicitly mention that the code samples are cross-platform where applicable, and clarify any Windows-only limitations.
- Reference Linux tools and patterns (such as /etc/ssl, certificate stores, or environment variables) where relevant.
Create pull request