Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation consistently presents Windows-centric tooling (PowerShell) alongside Azure CLI, often giving PowerShell examples equal or greater prominence. There are no explicit Linux shell (bash) or macOS-specific examples, and installation instructions for Azure CLI and PowerShell do not address platform differences. The examples and command syntax assume either PowerShell or Azure CLI, but do not show Linux-native usage (e.g., bash scripting, environment variables, or package managers like apt/yum/homebrew). There is no mention of Linux-specific considerations, nor are Linux tools or shell patterns (such as piping, jq, or curl) used or referenced.
Recommendations
- Add explicit Linux (bash) examples for all CLI commands, showing usage in a Linux shell, including environment variable handling and output parsing (e.g., using jq).
- Clarify installation instructions for Azure CLI and PowerShell by specifying platform-specific steps (e.g., apt/yum/homebrew for CLI, and note that PowerShell is not native to Linux).
- When presenting command tabs, default to Azure CLI (cross-platform) first, and clarify that PowerShell is primarily a Windows tool (with limited Linux support).
- Include notes or sections on Linux/macOS compatibility, especially for scripting and automation scenarios.
- Show how to use REST API examples with curl, and SDK examples in a Linux context.
- Avoid assuming PowerShell is the default scripting environment; highlight bash/zsh/fish alternatives for Linux/macOS users.
Create Pull Request