Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation exhibits a moderate Windows bias. PowerShell examples and references (e.g., New-AzVM, Get-AzComputeResourceSku) are given equal prominence to Azure CLI, but Windows-specific tools and patterns (PowerShell scripting, Windows file paths in az rest output) are used without Linux equivalents. The REST example uses a Windows-style path (.\sku-list.json) for output, and PowerShell scripting is detailed extensively, while Bash or Linux shell scripting is absent. The ordering of tabs often places PowerShell before Portal or REST, and the initial error example uses New-AzVM before az vm create.
Recommendations
- Add Bash/Linux shell scripting examples for filtering and processing az vm list-skus output, similar to the PowerShell script provided.
- In REST examples, use cross-platform file paths (e.g., ./sku-list.json) or show both Windows and Linux variants.
- Ensure that CLI examples (az vm create, az vm list-skus) are presented before or alongside PowerShell examples, not after.
- Include notes or examples for Linux users, such as using jq for JSON processing, or grep/awk for filtering output.
- Balance the depth of scripting examples: if PowerShell scripts are shown, provide equivalent Bash scripts for Linux users.
Create Pull Request