Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. While both Azure CLI and Azure PowerShell examples are provided for deployment and cleanup, PowerShell is mentioned as an equal alternative to CLI in prerequisites and examples. The use of Visual Studio Code is platform-neutral, but the documentation refers to Visual Studio (Windows-only) as a similar experience and links to a separate quickstart for it. The order of presentation often lists PowerShell alongside or before CLI, and no explicit Linux-specific instructions, troubleshooting, or screenshots are provided. There is no mention of Linux-specific considerations, such as shell differences, nor are there examples using Bash or other Linux-native tools.
Recommendations
- Explicitly mention that Visual Studio Code and the Bicep extension are cross-platform and supported on Linux and macOS, not just Windows.
- Provide Linux/Bash-specific examples for deploying Bicep files, including command-line usage and troubleshooting tips (e.g., file path formats, permissions).
- Include screenshots taken from Linux environments (e.g., Ubuntu desktop) to demonstrate parity.
- Clarify that Azure CLI is cross-platform and highlight its usage for Linux users, possibly listing CLI examples before PowerShell.
- Add a note or section for Linux/macOS users, addressing any differences in setup, keyboard shortcuts, or environment variables.
- Avoid referring to Visual Studio (Windows-only) as a primary alternative; instead, mention cross-platform editors first.
Create Pull Request