Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation generally maintains cross-platform neutrality by focusing on Visual Studio Code and Azure CLI. However, in several places, Azure PowerShell is mentioned alongside Azure CLI, and in all such cases, PowerShell is always listed after Azure CLI (never exclusively or first). There are no explicit Windows-only tools or patterns, but the presence of PowerShell examples and references may be perceived as Windows-centric, especially since Linux-native shell examples (e.g., Bash) are not provided. All keyboard shortcuts are given in a cross-platform way (Ctrl/Cmd), and no Windows-only tools are promoted. There are no missing Linux examples, but the parity could be improved by explicitly mentioning Linux/macOS environments and shell usage.
Recommendations
- Where Azure CLI and PowerShell are both mentioned, consider explicitly stating that Azure CLI works natively on Linux/macOS/Windows, and PowerShell Core is cross-platform, to avoid the impression of Windows bias.
- Add explicit references to Linux/macOS environments where relevant, such as mentioning that all commands work in Bash or zsh.
- Provide example commands in Bash or zsh where appropriate, especially for common developer workflows.
- In sections that mention keyboard shortcuts, clarify any differences for macOS users (e.g., Cmd vs Ctrl) if not already done.
- Consider including a brief note or link about using the Azure CLI in Linux/macOS terminals to reinforce cross-platform support.
Create Pull Request