Bias Analysis
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell for all major operations. However, PowerShell is given equal prominence to CLI, despite being primarily a Windows tool, and PowerShell examples are detailed and referenced with links to specific cmdlets. There is a slight Windows bias in the inclusion and emphasis of PowerShell, which is not natively available on Linux/macOS (though it can be installed). The CLI examples are cross-platform, but PowerShell is often presented as a first-class option, which may create friction for Linux/macOS users. No Linux/macOS-specific tools or shell examples (e.g., Bash scripts) are provided, and PowerShell is mentioned before CLI in some sections.
Recommendations
- Clarify that Azure CLI is the recommended cross-platform tool for scripting and automation, and mention that PowerShell is primarily for Windows users (with installation instructions for Linux/macOS if referenced).
- Ensure CLI examples are shown before PowerShell in tabbed sections to reinforce CLI as the default for non-Windows platforms.
- Add Bash script equivalents for common operations, or provide notes for Linux/macOS users on how to adapt CLI commands in shell scripts.
- Explicitly state the cross-platform nature of Azure CLI and ARM templates, and provide links to installation guides for Linux/macOS.
- Consider reducing the prominence of PowerShell unless there are Windows-specific steps.
Create Pull Request