Bias Analysis
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Linux and Windows examples for environment variable setup, but consistently uses PowerShell for Windows and Bash for Linux. However, PowerShell-specific patterns (such as Read-Host prompts) are shown as the only secure way to input secrets, with no equivalent Bash/Linux example. Windows tools like Export-PfxCertificate are referenced exclusively for certificate export, and PowerShell is used for all secure variable input examples, even outside Windows-specific sections. The Azure CLI section uses different environment variable values for Windows and Linux, with Windows using PSCRED (PowerShell credential) and Linux using AZCLI, which may confuse cross-platform users. Overall, Windows/PowerShell patterns are presented first or exclusively in several places, and Linux equivalents for secure input and certificate handling are missing.
Recommendations
- Provide secure Bash/Linux equivalents for secret input (e.g., using 'read -s' or 'read -p' for environment variables) alongside PowerShell examples.
- Reference Linux-native tools for certificate export (e.g., 'openssl pkcs12' for .PFX creation) in addition to Windows Export-PfxCertificate.
- Clarify the difference between AZCOPY_AUTO_LOGIN_TYPE values for Windows and Linux, and explain why they differ.
- Ensure that secure input and scripting examples are shown for both platforms in all sections, not just Windows/PowerShell.
- Consider presenting Linux/Bash examples before or alongside Windows/PowerShell examples to avoid implicit prioritization.
Create Pull Request