Bias Analysis
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page demonstrates a moderate Windows bias. While Azure CLI examples are provided (which are cross-platform), all PowerShell examples use Azure PowerShell cmdlets with Windows-style paths (e.g., C:\MyTemplates\...), and there is no mention of Linux-specific shell environments or examples using Bash or other Linux-native tools. Visual Studio Code is referenced as the primary editor, which is cross-platform, but no mention is made of Linux-specific editors or shell usage. Windows-style paths and PowerShell are presented before any Linux alternatives, and there are no explicit Linux/Bash examples for deployment commands.
Recommendations
- Add Linux/Bash shell examples for deployment commands, using typical Linux path formats (e.g., /home/user/templates/storage.bicep).
- Include notes or examples for using Azure CLI and Bicep CLI in Linux environments, such as running commands in Bash or zsh.
- Provide guidance for Linux users on installing and using the Bicep CLI and Azure CLI, including any differences in environment variables or file paths.
- Mention Linux-native editors (such as Vim or VS Code on Linux) where appropriate.
- Ensure that all examples using file paths show both Windows and Linux formats, or use environment-agnostic paths.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide explicit cross-platform instructions where relevant.
Create Pull Request