Bias Analysis
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exhibits a Windows bias by consistently using Windows-style file paths (e.g., C:\templates\main.bicep) in all command examples, regardless of whether Azure CLI or PowerShell is being used. There are no explicit Linux/macOS examples or notes on path differences. Additionally, PowerShell is presented as a primary tool alongside Azure CLI, and the only editor recommended is Visual Studio Code. There is also a reference to a PowerShell-specific tutorial for role assignments. No Linux-specific tools, shell commands, or considerations are mentioned.
Recommendations
- Provide both Windows and Linux/macOS path examples for file locations in all CLI and PowerShell commands (e.g., C:\templates\main.bicep and ~/templates/main.bicep).
- Add notes or tabs to clarify differences in command syntax or file paths between Windows and Linux/macOS environments.
- Include bash/zsh shell examples where appropriate, especially for Azure CLI usage.
- Reference cross-platform editors (such as VS Code, Sublime Text, Atom) and clarify that the Bicep extension is available on all platforms.
- When linking to tutorials or further reading, provide both PowerShell and CLI (bash) options, or ensure parity in Linux/macOS guidance.
- Explicitly state that all commands are cross-platform unless otherwise noted, and highlight any known issues or differences for Linux/macOS users.
Create Pull Request