Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. Azure PowerShell is consistently presented as a primary automation option alongside Azure CLI, and PowerShell examples are given equal prominence to CLI examples. The CLI examples are described as working in Bash or Azure PowerShell consoles, but there is no explicit mention of Linux/macOS terminals or shell environments. The documentation refers to Azure PowerShell and its cmdlets without clarifying cross-platform compatibility or providing alternative Linux/macOS shell scripting examples. Windows tools and patterns (PowerShell, `$variable` syntax) are shown before or equally with CLI, and there is no explicit assurance that all steps work identically on Linux/macOS. No Linux-specific issues, troubleshooting, or parity notes are provided.
Recommendations
- Explicitly state that Azure CLI commands work on Linux/macOS Bash shells and provide example environments.
- Clarify that Azure PowerShell is cross-platform, or provide links to installation/use on Linux/macOS.
- Add Linux/macOS-specific troubleshooting notes or callouts where relevant (e.g., authentication, environment variables, file paths).
- Where PowerShell is shown, also provide Bash scripting equivalents for resource ID extraction and variable assignment.
- In sections where both CLI and PowerShell are presented, consider listing CLI first to reflect its cross-platform nature.
- Add a brief section or note on platform compatibility for all tools discussed.
Create Pull Request