Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples and references (e.g., New-AzVM, Get-AzComputeResourceSku) are given equal or greater prominence compared to Azure CLI, and Windows/PowerShell tools are mentioned first in the error description and troubleshooting sections. The REST example uses a Windows-style file path ('.\sku-list.json'), and there is no explicit mention of Linux-specific shell usage or file path conventions. No Linux shell scripting examples (e.g., Bash, zsh) are provided, and the PowerShell tab includes a lengthy script, whereas the CLI tab only covers basic commands.
Recommendations
- Add Linux/Bash shell scripting examples for filtering and processing Azure CLI output, matching the complexity of the PowerShell script.
- Ensure file path examples in REST/CLI sections use cross-platform notation or provide both Windows and Linux variants (e.g., '.\sku-list.json' and './sku-list.json').
- In error descriptions and command references, mention Azure CLI before PowerShell, or present both equally.
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide usage notes for common Linux shells.
- Where advanced PowerShell scripting is shown, offer equivalent Bash or Python examples for Linux users.
Create Pull Request