Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation exhibits several forms of Windows bias: Windows concepts and links (e.g., Secure Boot, Hyper-V Shielded VM) are introduced first and referenced more frequently than Linux equivalents. Command examples are often provided for both Azure CLI and PowerShell, but PowerShell (a Windows-centric tool) is given equal or greater prominence, and Linux-specific shell examples are less common or absent in some sections. Troubleshooting and validation workflows reference Windows tools and documentation before Linux alternatives. Some sections lack Linux-specific examples or troubleshooting steps, and Windows terminology is used as the default.
Recommendations
- Ensure Linux shell (bash) examples are provided alongside PowerShell for all CLI commands, especially in troubleshooting and validation sections.
- When referencing Secure Boot and other security features, include links to Linux documentation (e.g., UEFI Secure Boot on Linux, Linux kernel documentation) in addition to Windows resources.
- Present Linux and Windows examples in parallel tabs or sections, with equal prominence and ordering.
- Expand troubleshooting steps to include Linux-specific workflows and tools, not just Windows-centric approaches.
- Avoid using Windows terminology as the default; clarify when instructions apply to both platforms or provide platform-specific guidance.
Create Pull Request