Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits several forms of Windows bias. Windows examples, especially those using PowerShell and Windows-specific tools (.NET Framework, Windows PowerShell 5.1), are presented first and in greater detail. Many code samples, templates (Bicep, ARM), and CLI instructions default to Windows VM creation and extension installation, with Linux equivalents either missing or less emphasized. The PowerShell cmdlets and extension installation instructions are almost exclusively shown for Windows, with Linux instructions often relegated to brief mentions or not provided at all. Folder permission and proxy configuration examples are Windows-centric, and troubleshooting notes focus on Windows-specific scenarios (UAC/LUA, registry paths).
Recommendations
- Provide Linux-first or side-by-side examples for all major steps, including extension installation, VM creation, and configuration.
- Include Linux-specific code samples for Bicep, ARM, REST API, and CLI, not just Windows VM creation.
- Expand Linux troubleshooting and operational guidance, such as folder permissions, proxy settings, and uninstall instructions.
- Balance the use of PowerShell with Bash or other Linux-native scripting examples.
- Highlight Linux package requirements and configuration steps with equal detail as Windows prerequisites.
- Ensure documentation screenshots and portal instructions are applicable to both Windows and Linux scenarios.
- Clarify when instructions are OS-specific and provide links or references to Linux documentation where appropriate.
Create Pull Request