Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page exhibits a Windows bias in several ways: PowerShell is frequently used as the primary or sole scripting example for verifying template functions, resource providers, VM images, VM sizes, and VM extensions. Windows-centric tools and patterns (such as PowerShell DSC and Windows VM images) are referenced and shown in code samples, while Linux equivalents are either omitted or mentioned only in passing. Examples and default values often reference Windows-specific resources (e.g., 'dotnet-core-music-windows', 'MicrosoftWindowsServer'), and there is a lack of Linux-focused examples for VM images, extensions, and scripts.
Recommendations
- Provide Linux-focused examples alongside Windows ones, such as using Bash scripts, Linux VM images, and Linux-specific VM extensions.
- Include Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more commonly used on Linux/macOS.
- Use neutral or Linux-inclusive default values in code samples (e.g., reference both Windows and Linux script repositories, VM images, and artifacts).
- Mention and demonstrate Linux-compatible tools and extensions (e.g., Custom Script Extension for Linux, OMS Agent for Linux) where relevant.
- Balance references to Windows-specific technologies (like PowerShell DSC) with Linux equivalents (such as cloud-init or Ansible).
- Ensure documentation language and examples do not assume a Windows environment by default.
Create Pull Request