Bias Analysis
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page demonstrates a moderate Windows bias. Examples for deploying Bicep files with parameters are provided for both Azure CLI and Azure PowerShell, but PowerShell is a Windows-centric tool and its usage is shown extensively. File paths in PowerShell examples use Windows-style (C:\MyTemplates\...), and no Linux/macOS equivalents are provided. Visual Studio Code is referenced as the primary editor, which is cross-platform, but no mention is made of alternative editors or shell environments. The documentation does not provide Bash or Linux shell examples for deployment commands, nor does it show Linux-style file paths. The order of presentation puts PowerShell after CLI, but the PowerShell section is detailed and uses Windows conventions throughout.
Recommendations
- Add Linux/macOS shell examples for deployment commands, using Bash syntax and Linux-style file paths (e.g., /home/user/templates/storage.bicep).
- Include notes or examples for using Azure CLI and Bicep CLI in Linux/macOS environments, including file path conventions.
- When showing PowerShell examples, clarify that these are for Windows and provide equivalent Bash examples for Linux/macOS users.
- Mention cross-platform editors and shell environments where appropriate, not just Visual Studio Code.
- Ensure that references to file paths and tooling are not exclusively Windows-centric; provide parity for Linux/macOS users.
Create Pull Request