Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools (Visual Studio Code, Azure PowerShell) are mentioned before or alongside cross-platform alternatives, and PowerShell examples are given equal prominence to Azure CLI. The workflow assumes familiarity with right-click context menus and UI patterns typical of Windows environments. There are no explicit Linux-specific instructions or examples, and the documentation does not address platform differences in setup or usage.
Recommendations
- Add explicit notes clarifying that Visual Studio Code and the Bicep extension are fully supported on Linux and macOS, not just Windows.
- Include Linux/macOS-specific instructions for launching Visual Studio Code and interacting with files (e.g., using terminal commands rather than right-click context menus).
- Provide CLI-only workflows for deployment and resource management, emphasizing that Azure CLI is cross-platform and can be used on Linux/macOS.
- Mention alternative editors (e.g., Vim, VS Codium) that support Bicep via extensions, for users who do not use Visual Studio Code.
- Clarify that Azure PowerShell is available on Linux/macOS, but highlight Azure CLI as the default cross-platform tool.
- Add screenshots or examples from Linux/macOS environments to visually reinforce cross-platform support.
Create Pull Request