Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation generally presents authentication options and examples in a cross-platform manner, but there is a mild Windows bias in the authentication section. The 'Interactive browser login' is labeled as 'Windows only' and described first, while the Linux default ('Device code login') is described second. The access token section references the PowerShell cmdlet 'Get-AzAccessToken' as the only example for obtaining a token, with no Linux/CLI equivalent. Additionally, certificate authentication from the Windows certificate store is described in detail, but there is no equivalent Linux-specific guidance for certificate storage.
Recommendations
- Reorder authentication options to present cross-platform or Linux-default methods (such as device code login) before Windows-only options.
- When referencing PowerShell cmdlets (e.g., Get-AzAccessToken), also provide equivalent Azure CLI commands (e.g., 'az account get-access-token') for Linux/macOS users.
- For certificate-based authentication, add Linux-specific instructions for storing and referencing certificates (e.g., using PEM files in the filesystem) and clarify any platform-specific differences.
- Where features are Windows-only (such as using the Windows certificate store), clearly label them as such and, where possible, provide Linux/macOS alternatives or explicitly state if none exist.
Create Pull Request