Bias Analysis
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Linux and Windows examples for setting environment variables, but consistently uses PowerShell syntax for Windows and Bash for Linux. However, prompts for sensitive input (such as client secrets and certificate passwords) are only shown using PowerShell's Read-Host, with no Linux equivalent (e.g., read -s). Additionally, references to Windows-specific tools (like Export-PfxCertificate) are present, and PowerShell is used as the default for interactive examples, even in generic 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 cause confusion. Overall, there is a slight preference for Windows/PowerShell patterns and tools, with Linux equivalents sometimes missing or less emphasized.
Recommendations
- Provide Linux equivalents for all PowerShell-specific examples, especially for secure input prompts (e.g., use 'read -s' in Bash for secrets/passwords).
- When referencing Windows tools (e.g., Export-PfxCertificate), also mention or link to Linux/macOS alternatives for certificate export and management.
- Ensure that generic examples (such as setting environment variables or running AzCopy commands) are shown in both Bash and PowerShell, or use a neutral syntax where possible.
- Clarify the difference in environment variable values for Azure CLI integration between Windows and Linux, and explain why they differ.
- Consider presenting Linux examples first or side-by-side with Windows examples to avoid implicit prioritization of Windows.
Create Pull Request