Bias Analysis
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation page exhibits a Windows bias in several ways: troubleshooting commands and scripts are primarily shown in PowerShell, with no Linux shell equivalents; Windows-centric workflows and tools (e.g., PowerShell, Test-NetConnection, Hyper-V terminology) are mentioned first or exclusively; Linux troubleshooting is covered in dedicated sections but lacks parity in example commands and scripting for common tasks (e.g., checking IP conflicts, deleting resources). There are no bash or Linux CLI examples for tasks like network diagnostics or resource management, and Windows tools/scripts are presented before or instead of Linux alternatives.
Recommendations
- Provide equivalent Linux shell (bash) commands for network diagnostics (e.g., use 'ip', 'ss', 'netstat', 'curl', etc.) alongside PowerShell examples.
- Include Linux CLI examples for resource management tasks, such as deleting images or checking ingestion jobs, using Azure CLI or REST API via curl.
- When listing troubleshooting steps, present both Windows and Linux approaches in parallel, rather than focusing on Windows tools/scripts first.
- Clarify which steps are OS-agnostic and which require OS-specific commands, and ensure Linux users are not required to interpret Windows-centric instructions.
- Add troubleshooting examples for Linux VMs beyond cloud-init and waagent.conf, such as common Linux networking issues, log locations, and diagnostic commands.
Create Pull Request