Bias Analysis
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for most operations, but there is a notable emphasis on PowerShell, which is traditionally a Windows-centric tool. In several places, PowerShell is listed before CLI, and there are no explicit Linux/Bash-specific examples or notes about running commands in a Linux environment. The CLI examples are generic and do not clarify Linux-specific nuances (e.g., quoting, environment variables). There are also no references to Linux-native tools or shell scripting, and the PowerShell tab is sometimes shown before the CLI tab. This could make the documentation feel Windows-biased and less approachable for Linux users.
Recommendations
- Ensure that Azure CLI examples are always presented before PowerShell examples, as CLI is cross-platform and more familiar to Linux users.
- Add explicit notes or sections about running Azure CLI commands in Linux/Bash environments, including any differences in quoting, environment variables, or output parsing.
- Where PowerShell is referenced, clarify that Azure PowerShell is available cross-platform, but also provide Bash shell alternatives for scripting scenarios.
- Include Linux/Bash-specific examples for common tasks, such as using environment variables, piping, and parsing output with jq.
- Avoid using PowerShell syntax (e.g., $variable = ...) in CLI sections, as this can confuse Linux users who expect Bash syntax.
- Where possible, mention Linux tools or patterns (e.g., using export for environment variables, using grep/jq for output processing) alongside Windows/PowerShell equivalents.
- Add a short section or callout at the top clarifying that all CLI examples are cross-platform and tested on both Windows and Linux.
Create Pull Request