Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
Although the documentation is focused on Linux VMs, there are several signs of Windows bias: PowerShell examples are provided extensively and often before or alongside Azure CLI examples, even though PowerShell is not the default scripting environment for most Linux users. Windows-specific tools and terminology (e.g., 'ipconfig', 'Write-Host', '.ps1' scripts, 'New-AzStorageBlobSASToken') are referenced without clear Linux alternatives or context. REST and ARM template examples use Windows-style scripts (PowerShell), and some explanations default to Windows patterns. There are missing Linux-specific examples for certain advanced scenarios (e.g., parameter passing, blob SAS token generation, script URI usage).
Recommendations
- Provide Bash shell script examples in REST and ARM template sections instead of PowerShell (.ps1) scripts.
- Clarify when a command or tool is Windows-specific and offer Linux equivalents (e.g., use 'ifconfig' or 'ip a' instead of 'ipconfig').
- Add Linux-native instructions for generating SAS tokens (e.g., using Azure CLI or azcopy) instead of only referencing PowerShell tools.
- Ensure parameter passing examples show both Windows (argument style) and Linux (environment variable style) clearly.
- Where PowerShell is used, explain its applicability to Linux (e.g., PowerShell Core) and provide Bash alternatives.
- Review all sample scripts and outputs to ensure they use Linux conventions (e.g., .sh scripts, echo, id, etc.) and avoid Windows-centric language.
Create Pull Request