Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides deployment examples for both Azure CLI and Azure PowerShell, but the PowerShell example uses Windows-style file paths (C:\MyTemplates\...), and PowerShell is a Windows-centric tool (despite cross-platform support, it's still most commonly associated with Windows). The PowerShell example is given after the CLI example, which is cross-platform, but references to Visual Studio (Windows-only) and PowerShell parameter name conflicts further reinforce a Windows bias. There are no explicit Linux shell examples (e.g., Bash), and no mention of Linux-specific patterns or tools.
Recommendations
- Include Linux/Bash shell examples for deploying templates, such as using az CLI from Bash with Linux-style file paths (e.g., /home/user/storage.parameters.json).
- Clarify that PowerShell is available cross-platform, and provide examples with Linux/Mac file paths.
- Add notes or examples for using VS Code (cross-platform) instead of Visual Studio for ARM template projects.
- Ensure that references to file paths use both Windows and Linux/Mac conventions.
- Mention that Azure CLI is fully supported on Linux and Mac, and highlight any differences in usage if relevant.
Create Pull Request