Bias Analysis
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for most scenarios, but the PowerShell sections are significantly more detailed, with full resource creation flows and advanced configuration. The PowerShell examples are inherently Windows-centric, and the VM creation steps in PowerShell default to Windows VMs (using Set-AzVMOperatingSystem -Windows), with no equivalent Linux PowerShell example. Network security rules in PowerShell focus on RDP (port 3389), which is Windows-specific, and the password requirements link points to a Windows FAQ. In REST examples, both Linux and Windows VM creation are shown, but the PowerShell bias remains strong throughout. The CLI examples do show Linux VM creation with SSH keys, but the PowerShell sections are more comprehensive and default to Windows patterns.
Recommendations
- Add PowerShell examples for Linux VM creation, including Set-AzVMOperatingSystem -Linux and SSH key authentication.
- Balance the detail level between CLI and PowerShell sections, ensuring Linux scenarios are equally covered in PowerShell.
- When showing network security rules, include examples for SSH (port 22) alongside RDP (port 3389) in PowerShell.
- Reference Linux password/SSH requirements, not just Windows password complexity.
- Where possible, avoid defaulting to Windows-centric resource names, patterns, or tools in examples.
Create Pull Request