Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates Windows bias by consistently presenting PowerShell examples and references before Linux-friendly alternatives, such as Azure CLI. PowerShell and Windows-centric tools (e.g., New-AzVM, Get-AzComputeResourceSku) are featured prominently, with more detailed scripting examples provided for PowerShell than for CLI. The REST example uses a Windows-style path ('.\sku-list.json') for output, and there is no mention of Linux-specific shell usage or file paths. No Bash or Linux shell scripting examples are provided, and the documentation does not address Linux-specific usage patterns or troubleshooting steps.
Recommendations
- Alternate the order of examples so that Azure CLI (cross-platform) is presented before PowerShell.
- Provide equivalent Bash shell scripting examples for filtering and processing output, especially for complex queries currently shown only in PowerShell.
- Use platform-neutral file paths in examples (e.g., './sku-list.json' instead of '.\sku-list.json').
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide troubleshooting notes for Linux users if relevant.
- Where PowerShell scripts are shown, offer a comparable Bash or shell script for Linux users.
- Reference Linux tools (e.g., jq for JSON parsing) alongside PowerShell tools (e.g., Where-Object) when discussing output filtering.
Create Pull Request