Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a Windows bias in troubleshooting sections by presenting Windows (PowerShell) commands before Linux equivalents, and by providing more detailed Windows command examples. In the 'Troubleshooting' section, the Windows PowerShell command (Test-NetConnection) is listed first, with the Linux command (nc) given second and without explanation. There are no Bash or Linux CLI examples for other operations (e.g., ARM deployment, REST API usage), and the portal instructions do not mention cross-platform CLI tools (e.g., Azure CLI) as a primary method.
Recommendations
- Present Linux and Windows command examples side-by-side, or alternate which platform is shown first to avoid implicit prioritization.
- Provide equivalent Bash/Linux CLI commands (e.g., curl for REST API, az CLI for resource management) in all relevant sections, not just PowerShell.
- Expand troubleshooting steps to include Linux-native tools (e.g., dig for DNS, traceroute, etc.) with explanations.
- Instruct users on using Azure CLI and Bash for pool creation and management, not just the Azure portal or ARM templates.
- Ensure that all code snippets and screenshots are platform-agnostic or provide variants for both Windows and Linux environments.
Create Pull Request