Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page provides deployment examples for both Azure CLI and Azure PowerShell, but the PowerShell example uses Windows-style file paths (C:\MyTemplates\...), and PowerShell is a Windows-centric tool. The PowerShell example appears after the CLI example, but there is no explicit Linux shell example (e.g., Bash), nor is there mention of Linux file path conventions. The Visual Studio tip is also Windows-specific. There is no mention of Linux editors or deployment patterns.
Recommendations
- Add explicit Bash/Linux shell examples for deploying with parameter files, using Linux-style file paths (e.g., /home/user/storage.parameters.json).
- Clarify that Azure CLI works cross-platform and provide Linux/macOS file path examples alongside Windows ones.
- Mention cross-platform editors (e.g., VS Code) in addition to Visual Studio for parameter file management.
- Where PowerShell is referenced, note that PowerShell Core is available on Linux/macOS, and provide examples with Linux file paths.
- Avoid Windows-centric file paths in generic examples, or provide both Windows and Linux/macOS variants.
Create Pull Request