Bias Analysis
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Visual Studio (a Windows-centric IDE) for Bicep file creation, listing Visual Studio as the primary tool in prerequisites and instructions. While it briefly mentions Visual Studio Code as an alternative, all step-by-step guidance is for Visual Studio. Additionally, deployment and cleanup instructions provide both Azure CLI and Azure PowerShell examples, but PowerShell (a Windows-native tool) is given equal prominence, and no Linux-specific shell or editor workflows are discussed. There are no Linux-specific instructions, screenshots, or troubleshooting tips.
Recommendations
- Provide parallel instructions and screenshots for Visual Studio Code, which is cross-platform, or clarify that Visual Studio is Windows-only.
- Explicitly mention platform compatibility for each tool and extension (e.g., note that Visual Studio is Windows-only, while VS Code works on Linux/Mac).
- Include Linux-specific examples, such as using Bash with Azure CLI, and troubleshooting tips for Linux environments.
- Add links or references to Linux editor workflows (e.g., Vim, Emacs, VS Code on Linux) for Bicep authoring.
- Ensure that CLI examples are shown first or equally with PowerShell, and clarify that PowerShell Core is available cross-platform if relevant.
Create Pull Request