Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation page focuses on using Visual Studio, a Windows-centric IDE, and lists Visual Studio as the primary tool for Bicep file creation. While it mentions Visual Studio Code as an alternative, the main instructions and screenshots are for Visual Studio. In deployment and cleanup sections, both Azure CLI (cross-platform) and Azure PowerShell (Windows-preferred) examples are provided, but PowerShell is given equal prominence. There are no Linux-specific instructions, nor is there mention of Linux-native editors or workflows beyond a brief link to Visual Studio Code.
Recommendations
- Add explicit instructions and screenshots for Visual Studio Code, which is cross-platform, or link to a Linux-specific quickstart.
- Include a note about platform compatibility for Visual Studio and Visual Studio Code, clarifying that Visual Studio is Windows-only while VS Code runs on Linux and macOS.
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more commonly used on Linux.
- Mention Linux-native editors (e.g., Vim, Emacs) and how Bicep files can be authored and deployed from Linux environments.
- Provide troubleshooting tips for Linux users, such as installing the Bicep CLI and using it with Azure CLI.
Create Pull Request