Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation demonstrates a mild Windows bias. In the section about parameter naming conflicts, only PowerShell (specifically the New-AzResourceGroupDeployment cmdlet) is discussed, with no mention of equivalent Azure CLI or Linux-native tooling. In the resources section, links to Windows VM connection methods are listed before Linux, and two out of three links are Windows-specific. There are no Linux shell or Azure CLI examples for template deployment or parameter handling, and no mention of Linux tools or workflows.
Recommendations
- Include Azure CLI examples alongside or before PowerShell examples when discussing template deployment and parameter handling.
- Mention Linux-native tools and workflows (e.g., bash, az CLI) in sections that currently only reference PowerShell or Windows tools.
- When listing links for connecting to VMs, alternate the order or group Windows and Linux resources equally, and ensure parity in detail and prominence.
- Add explicit Linux/CLI examples for common tasks such as deploying templates, handling parameters, and resolving naming conflicts.
- Reference cross-platform editors and tools (e.g., Visual Studio Code) in a way that highlights their availability on Linux and macOS, not just Windows.
Create Pull Request