Bias Analysis
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by consistently using Windows-style file paths (e.g., C:\templates\main.bicep) in all CLI and PowerShell examples, and by not providing Linux/macOS equivalents. All examples assume a Windows environment, and there is no mention of Linux-specific considerations or examples (such as using ~/templates/main.bicep or /home/user/templates/main.bicep). Additionally, the documentation references PowerShell and Azure PowerShell heavily, which are more native to Windows, and the only editor mentioned is Visual Studio Code, which, while cross-platform, is often associated with Windows in Microsoft documentation.
Recommendations
- Provide Linux/macOS equivalents for all file paths in CLI and PowerShell examples (e.g., ~/templates/main.bicep or /home/user/templates/main.bicep).
- Explicitly mention that the CLI and PowerShell commands work on Linux/macOS, and note any differences in syntax or environment setup.
- When referencing file paths in code samples, use environment-agnostic variables or provide both Windows and Linux/macOS path formats.
- Include a note or section on running Azure CLI and PowerShell on Linux/macOS, including any prerequisites or differences.
- Consider mentioning other editors that are popular on Linux/macOS, or clarify that Visual Studio Code is available cross-platform.
Create Pull Request