Bias Analysis
Detected Bias Types
windows_tools
powershell_heavy
windows_first
missing_linux_example
Summary
While the documentation is focused on Linux VMs and provides extensive Azure CLI examples (which are cross-platform), there is a notable bias toward Windows tooling and PowerShell. PowerShell examples are provided in great detail, often with Windows-centric terminology and tools (e.g., 'New-AzStorageBlobSASToken', 'ipconfig' as a commandId, 'myscript.ps1' in examples). REST API and ARM template examples frequently use Windows-style scripts (PowerShell, .ps1) rather than Linux shell scripts (.sh). Some explanations and notes reference Windows-specific behaviors or tools before Linux equivalents, and certain advanced scenarios (e.g., streaming output to blobs) are only illustrated with PowerShell. There are also missing Linux-specific examples for some advanced features.
Recommendations
- Provide Linux shell script (.sh) examples alongside PowerShell (.ps1) in REST API and ARM template sections.
- Clarify when PowerShell tools (e.g., New-AzStorageBlobSASToken) are Windows-only and offer Linux alternatives (e.g., Azure CLI or Python SDK for SAS token generation).
- Ensure commandId examples use Linux-relevant commands (e.g., 'ifconfig', 'ls', 'bash') instead of Windows commands like 'ipconfig'.
- Add advanced Azure CLI examples for features currently only shown in PowerShell (e.g., streaming output to blobs, parameter passing).
- Review notes and explanations to avoid referencing Windows behaviors before Linux, or to clearly distinguish OS-specific instructions.
Create Pull Request