Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates mild Windows bias. In several instances, Windows-specific tools (PowerShell) and links are mentioned before or alongside their Linux equivalents, and sometimes Windows examples or references appear first. For example, in the 'ResourceGroupNotFound' error, both Azure CLI and PowerShell are referenced, but PowerShell is listed second. In 'AllocationFailed', troubleshooting links for Linux and Windows are provided, with Linux listed first, which is positive. However, in 'SubnetsNotInSameVnet', the Windows VM link is listed before the Linux VM link. There is also a general tendency to mention PowerShell as a management tool, which is more common on Windows, and no explicit Bash or Linux shell examples are given.
Recommendations
- Ensure that Linux and Windows troubleshooting links are presented in parallel, and alternate which is listed first to avoid implicit prioritization.
- Where management tools are referenced (e.g., PowerShell), also provide equivalent Linux/Bash/CLI commands or links, and clarify cross-platform usage.
- Add explicit Linux/Bash examples where only PowerShell or Windows tools are mentioned.
- Review all error mitigation steps to ensure Linux parity in tooling and examples, and avoid assuming PowerShell as the default management tool.
Create Pull Request