Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits a Windows bias in several areas. Windows examples, tools, and terminology are presented first or exclusively in key sections, especially in the Bicep and ARM template samples, which only provision Windows VMs. PowerShell is heavily featured, with detailed cmdlets and usage, while Linux equivalents are minimal or absent. The extension installation examples and resource definitions focus on Windows-specific handlers (HybridWorkerForWindows), and Linux-specific instructions are either missing or relegated to notes or optional sections. The removal process for agent-based workers is more detailed for Windows (registry manipulation) than for Linux (simple directory removal), and permissions guidance is Windows-centric.
Recommendations
- Provide parallel Bicep and ARM template examples for Linux VMs, using the correct image references and extension types (HybridWorkerForLinux).
- Include Linux-specific CLI and PowerShell commands, such as az vm create with Linux images and Set-AzVMExtension/New-AzConnectedMachineExtension using HybridWorkerForLinux.
- Expand Linux prerequisites and troubleshooting sections to match the depth given to Windows, including permissions, identity, and hardening guidance.
- Ensure all extension installation examples clearly show both Windows and Linux type values and settings.
- Balance the order of presentation so that Linux instructions/examples are given equal prominence and detail as Windows.
- Add more Linux-specific automation and management scenarios, including common distributions and shell scripting examples.
Create Pull Request