Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a mild Windows bias. Visual Studio Code is recommended as the editor, with installation instructions linked for Windows first. The Azure CLI installation instructions list Windows before Linux and macOS. PowerShell is presented as an equal alternative to Azure CLI, but PowerShell is primarily a Windows-centric tool (though cross-platform now). The examples for Azure CLI are written for Bash, but there are no explicit Linux shell examples or mentions of Linux-native editors or tooling. The documentation does not provide Linux-specific guidance or highlight Linux workflows, and Windows tools/patterns (PowerShell, Visual Studio Code) are mentioned before or instead of Linux equivalents.
Recommendations
- Add explicit Linux shell examples (e.g., bash, zsh) and clarify that Azure CLI commands work on Linux and macOS.
- Mention Linux-native editors (e.g., Vim, Emacs, nano) as alternatives to Visual Studio Code, or at least acknowledge their use.
- Reorder installation instructions to present all platforms equally, or start with Linux to balance historical bias.
- Clarify that PowerShell is available cross-platform, but also suggest Bash or other Linux-native shells for Linux users.
- Include screenshots or instructions for resource group management using Azure CLI on Linux/macOS, not just the Azure portal.
- Add notes or sections specifically for Linux users to ensure parity and inclusivity.
Create Pull Request