Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation consistently presents Windows-centric tools and workflows first or exclusively. Azure PowerShell is given equal prominence to Azure CLI, and Visual Studio Code is the only editor mentioned. There are no explicit Linux shell (bash) examples, and no mention of Linux-native editors or workflows. This may make Linux users feel like second-class citizens or require them to adapt Windows-oriented instructions.
Recommendations
- Present Azure CLI (which is cross-platform and often preferred on Linux/macOS) examples before PowerShell, or clarify that CLI is cross-platform while PowerShell is more common on Windows.
- Include bash/zsh shell variable syntax in CLI examples (e.g., export resourceGroupName=...) and clarify that CLI commands work on Linux/macOS terminals.
- Mention alternative editors such as Vim, Emacs, or JetBrains IDEs, or at least clarify that Visual Studio Code is available on Linux/macOS.
- Add a note or section on running Bicep deployments from Linux/macOS, including any prerequisites or differences.
- Where PowerShell is shown, explicitly state that it is primarily for Windows users, and link to Linux/macOS equivalents.
- Ensure that all instructions and scripts are tested and presented in a way that is friendly to Linux/macOS users, not just Windows.
Create Pull Request