Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates several forms of Windows bias. Windows-specific tools (e.g., PowerShell) are mentioned before or more prominently than Linux equivalents, especially for discovering image and VM SKU EOL dates and preparing data disks. Examples for Windows (such as PowerShell commands) are given in detail, while Linux examples are fewer and less detailed. In some cases, Windows patterns (directory junctions, Windows Services, autouser accounts) are discussed at length, while Linux alternatives are only briefly mentioned or omitted. This prioritization may make it harder for Linux users to find relevant guidance.
Recommendations
- Provide Linux CLI or shell script examples alongside PowerShell examples wherever Windows commands are shown.
- Mention Linux tools (e.g., bash, systemd, lsblk, fdisk) before or alongside Windows tools, not after.
- Ensure Linux-specific patterns (e.g., symlinks, systemd services, disk mounting) are described with equal detail and clarity as Windows equivalents.
- Where Windows-specific features (like directory junctions or autouser accounts) are discussed, add parallel Linux guidance (e.g., symlinks, user management).
- For API and CLI references, show both az CLI and bash usage, not just PowerShell.
- Add more Linux-focused troubleshooting and operational tips, especially for common scenarios like disk management, service setup, and log collection.
Create Pull Request