Bias Analysis
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation exhibits several Windows biases: PowerShell is used as the primary automation tool for both Windows and Linux examples, even when Linux users would typically use Bash or native Linux CLI tools. All command-line examples (deployment, tracking, removal) are shown in PowerShell, often from a Windows prompt (PS C:\WINDOWS\system32>), even for Linux VMs. Windows-specific tools and paths are referenced first and in more detail. There are no Bash or Linux-native command examples for deploying or managing extensions, and Linux verification steps use PowerShell to SSH into the VM, rather than native Linux SSH usage.
Recommendations
- Provide Bash or Azure CLI examples for Linux users, including deployment, tracking, and removal of GPU extensions.
- Show Linux command-line usage from a Linux shell (e.g., $ or # prompt), not from PowerShell on Windows.
- Reference Linux tools and patterns (e.g., SSH from Linux, file paths, environment variables) before or alongside Windows equivalents.
- Include instructions for connecting to Azure Resource Manager using Azure CLI or Bash, not just PowerShell.
- Ensure parity in troubleshooting and verification steps, using native Linux commands and file locations.
- Clarify which commands are cross-platform and which are Windows-specific, and provide alternatives where appropriate.
Create Pull Request