Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment and deletion tasks, but PowerShell (a Windows-centric tool) is given equal prominence and is presented immediately after CLI examples. There is no explicit Linux shell example (e.g., bash), and PowerShell is not marked as Windows-only, potentially implying parity or preference. Visual Studio Code is recommended as the editor, which is cross-platform, but no mention is made of alternative Linux-native editors. The SSH key generation instructions do include both Azure CLI and ssh-keygen (Linux/Unix tool), which is positive for parity.
Recommendations
- Clearly label PowerShell examples as Windows-specific, and Azure CLI examples as cross-platform.
- Present Azure CLI (cross-platform) examples first in every section, with PowerShell as an alternative.
- Add explicit bash shell examples for Linux/macOS users where relevant, especially for file operations and environment setup.
- Mention Linux-native editors (e.g., Vim, Nano) as alternatives to Visual Studio Code for editing Bicep files.
- Add a note clarifying that Azure CLI works on Linux/macOS/Windows, while PowerShell is primarily for Windows users.
Create Pull Request