Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell (a Windows-centric tool) is consistently presented first in examples, sample templates, and usage scenarios. Most code samples and walkthroughs use PowerShell, with only a few CLI/bash examples provided later. Windows-specific tools and APIs (e.g., CommandLineToArgvW) are referenced without Linux equivalents. There is a lack of parity in example depth and troubleshooting guidance for Linux/bash users, and some instructions (such as using the Cloud Shell 'Try it' button) default to PowerShell. The documentation does not provide balanced, parallel examples for Linux/bash users, and troubleshooting/development sections are PowerShell-centric.
Recommendations
- Alternate the order of PowerShell and Azure CLI/bash examples throughout the documentation, or present both side-by-side.
- Provide equally detailed sample templates and walkthroughs for Azure CLI/bash, including inline and external script usage.
- Include troubleshooting and development environment guidance specifically for Linux/bash users, not just PowerShell.
- Reference Linux-native tools and APIs where appropriate, or provide Linux equivalents when mentioning Windows-specific tools (e.g., mention how argument parsing works in bash).
- Ensure that all instructions (such as 'Try it' in Cloud Shell) offer both PowerShell and Bash options, with clear guidance for each.
- Expand the 'Work with outputs' and 'Monitor and troubleshoot' sections to include bash/CLI-specific details and examples.
- Review all sample links and ensure there are as many CLI/bash samples as PowerShell samples, with similar complexity.
Create Pull Request