Bias Analysis
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for all key operations, ensuring cross-platform support. However, PowerShell examples are consistently presented first, and the narrative often refers to 'PowerShell or CLI' as the main automation tools, which subtly prioritizes Windows-centric workflows. There are no Linux/macOS-specific shell examples (e.g., Bash), nor are there explicit mentions of platform differences or parity. No Windows-only tools or patterns are used, and all CLI commands are cross-platform.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first to avoid implicit Windows prioritization.
- Explicitly state that Azure CLI works natively on Linux and macOS, and that all shown CLI commands are cross-platform.
- Add a brief note or section clarifying platform compatibility for both PowerShell and CLI, including links to installation guides for Linux/macOS.
- Consider including Bash script examples for common tasks, or referencing Bash usage in automation contexts.
- Avoid language that implies PowerShell is the default or preferred automation tool; use neutral phrasing such as 'You can use Azure CLI or PowerShell...'
Create Pull Request