Bias Analysis
Detected Bias Types
windows_tools
powershell_heavy
windows_first
Summary
The documentation page demonstrates a Windows bias in several areas: deployment examples for Azure PowerShell use only Windows-style paths (e.g., C:\MyTemplates\...), and all PowerShell examples use the Windows-centric Azure PowerShell module. There is no mention of Linux equivalents (such as Bash or pwsh on Linux), nor are Linux file path formats (e.g., /home/user/...) provided. Visual Studio Code is referenced as the editor, which is cross-platform, but no explicit Linux-specific instructions or examples are given. Windows tools and patterns (PowerShell, Windows file paths) are mentioned exclusively and before any Linux alternatives.
Recommendations
- Include Linux/Bash examples alongside PowerShell, especially for deployment commands (e.g., az deployment group create in Bash, pwsh, or sh).
- Show file paths in both Windows (C:\...) and Linux (/home/user/...) formats for clarity.
- Mention that Azure PowerShell and Bicep CLI are available cross-platform, and provide instructions/examples for installing and running them on Linux/macOS.
- Add notes or examples for using pwsh (PowerShell Core) on Linux/macOS, not just Windows PowerShell.
- Where Visual Studio Code is referenced, clarify cross-platform support and provide any Linux/macOS-specific setup notes if relevant.
Create Pull Request