Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying templates with parameter files. However, the PowerShell example uses Windows-style file paths (C:\MyTemplates\...), and PowerShell is a Windows-centric tool (despite cross-platform support, most users associate it with Windows). Additionally, the section on parameter name conflicts is specific to PowerShell, with no mention of equivalent issues in Azure CLI or Linux shells. The Visual Studio tip is also Windows-specific. Linux/macOS equivalents (e.g., Bash, VS Code) are not mentioned, and Windows examples (PowerShell, Visual Studio) appear before or instead of Linux alternatives.
Recommendations
- Add explicit Linux/macOS file path examples (e.g., /home/user/storage.parameters.json) alongside Windows paths.
- Clarify that PowerShell is available cross-platform, or provide Bash examples for Linux/macOS users.
- Include notes on parameter name conflicts for Azure CLI or other deployment tools, if applicable.
- Mention VS Code or other cross-platform editors in addition to Visual Studio for managing parameter files.
- Ensure that examples alternate or show parity between Windows and Linux/macOS usage patterns.
Create Pull Request