Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates several forms of Windows bias. Windows and PowerShell examples are presented first and in greater detail, with Linux examples often following or being less emphasized. PowerShell is the primary automation tool referenced, even for Linux scenarios, and Windows-specific tools and paths are mentioned more frequently. Infrastructure-as-code examples (Bicep, ARM) and CLI samples focus on Windows VM creation and extension installation, with little to no Linux VM equivalents. Folder permissions and troubleshooting notes are Windows-centric, and Linux-specific requirements or commands are less visible or omitted.
Recommendations
- Present Linux and Windows examples side-by-side, or alternate which platform is shown first in code samples and walkthroughs.
- Provide Linux-native automation examples (e.g., Bash scripts, cloud-init, Ansible) in addition to PowerShell, especially for Linux VM onboarding and extension management.
- Expand infrastructure-as-code samples (Bicep, ARM templates) to include Linux VM creation and extension installation, not just Windows.
- Include Linux-specific troubleshooting, permissions, and configuration steps with equal detail to Windows.
- Reference Linux tools and patterns (e.g., systemd, SELinux, package managers) where relevant, not just Windows tools.
- Clarify when PowerShell Core is required or optional on Linux, and offer alternatives for users who prefer native Linux scripting.
- Ensure all folder paths, permissions, and operational notes are provided for both platforms, not just Windows.
Create Pull Request