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, but the PowerShell example uses Windows-style file paths (C:\MyTemplates\...), and the PowerShell section is given equal prominence to CLI. There is also a tip referencing Visual Studio, a Windows-centric tool, and a note about PowerShell-specific parameter name conflicts. No Linux-specific examples (e.g., Bash, Linux file paths) or editor/tooling recommendations are given, and Windows patterns (such as file paths and Visual Studio usage) are mentioned without Linux equivalents.
Recommendations
- Add Linux/Bash examples for deploying with parameter files, using Linux-style file paths (e.g., /home/user/templates/storage.parameters.json).
- Clarify that Azure CLI works cross-platform and show examples with Linux file paths.
- Mention cross-platform editors (e.g., VS Code) alongside Visual Studio, or provide Linux alternatives.
- Add a note about PowerShell Core availability on Linux, or clarify any differences in usage.
- Balance the order of examples so that CLI (cross-platform) is presented before PowerShell, or explicitly state platform applicability.
- If discussing file paths, show both Windows and Linux formats.
Create Pull Request