Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation presents both PowerShell and Azure CLI examples for deploying ARM templates, but PowerShell (a Windows-centric tool) is consistently listed first in each example section. The prerequisites recommend Visual Studio Code and the Resource Manager Tools extension, which are cross-platform, but there is no mention of Linux-native editors or workflows. The troubleshooting note refers to 'verbose' and 'debug' switches without clarifying their usage in both CLI and PowerShell contexts. There are no explicit Linux shell (bash) examples or references to Linux-specific tools or workflows.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or default to Azure CLI first, as it is cross-platform and more common on Linux.
- Explicitly mention that all CLI commands work on Linux, macOS, and Windows, and provide bash/zsh syntax where appropriate.
- Include Linux-native editor options (e.g., vim, nano) in the prerequisites, or clarify that Visual Studio Code is available on Linux.
- Add a note or section on running these commands in a Linux environment, including any differences in file paths or environment setup.
- Clarify the use of 'verbose' and 'debug' switches in both PowerShell and Azure CLI contexts.
Create Pull Request