Bias Analysis
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page provides both Azure CLI and Azure PowerShell examples for deploying Bicep files with parameters. However, the PowerShell examples use Windows-style file paths (e.g., C:\MyTemplates\...), and PowerShell is a Windows-centric tool, with no mention of Bash or Linux-native alternatives. The CLI examples are cross-platform, but PowerShell is presented as an equal deployment method without clarifying its limited use on Linux/macOS. Additionally, file path examples and tool references (Visual Studio Code, PowerShell) are Windows-first or Windows-only, which may cause confusion or friction for Linux/macOS users.
Recommendations
- Add explicit Bash shell examples for Linux/macOS users alongside PowerShell examples.
- Use cross-platform file path examples (e.g., ./MyTemplates/storage.bicep) or clarify path differences for each OS.
- Clarify that Azure PowerShell is available on Linux/macOS, but usage and installation may differ.
- Mention Linux/macOS alternatives for Visual Studio Code, or reference other editors where applicable.
- Ensure that CLI examples are shown before PowerShell, or at least clarify cross-platform applicability.
Create Pull Request