Bias Analysis
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page demonstrates a moderate Windows bias. While Azure CLI (cross-platform) is covered, Windows-specific tools and workflows are mentioned more prominently. PowerShell examples are given, and file paths in PowerShell use Windows conventions (C:\MyTemplates\...). Visual Studio (Windows-centric) is referenced, and parameter name conflict guidance is focused on PowerShell. There are no explicit Linux shell examples (e.g., Bash), nor is there mention of Linux-native editors or workflows.
Recommendations
- Add Linux/Bash shell examples for deploying templates with parameter files, using Linux-style file paths (e.g., /home/user/storage.parameters.json).
- Include guidance for using parameter files with Linux-native editors (e.g., vim, nano) and workflows.
- When referencing PowerShell, clarify that Azure CLI is cross-platform and provide parity in examples.
- If mentioning Visual Studio, also mention cross-platform alternatives (e.g., VS Code) and their parameter file handling.
- Add a note that the Azure CLI commands work identically on Linux, macOS, and Windows, and show sample file paths for each.
Create Pull Request