Bias Analysis
Detected Bias Types
windows_first
missing_linux_example
windows_tools
Summary
The documentation exhibits a Windows bias by consistently using Windows-style file paths (e.g., C:\templates\main.bicep) in all command examples, regardless of whether the tool is cross-platform. There are no explicit Linux/macOS path examples or notes on path differences. Additionally, the documentation references Visual Studio Code (cross-platform) but does not mention any Linux/macOS-specific considerations or alternatives. The PowerShell examples are presented before CLI examples, and the CLI examples also use Windows paths, which may confuse Linux/macOS users. There is also a reference to a PowerShell-specific tutorial for role assignment, with no mention of CLI or portal alternatives.
Recommendations
- Provide both Windows and Linux/macOS path examples for all file operations (e.g., use C:\templates\main.bicep and ~/templates/main.bicep or ./templates/main.bicep).
- Add notes or tabs clarifying file path differences between Windows and Linux/macOS.
- When referencing tools, ensure parity by mentioning cross-platform alternatives (e.g., Azure CLI, Bash) alongside PowerShell.
- In sections where PowerShell and CLI are presented, alternate the order or clarify that both are cross-platform, and highlight any OS-specific issues.
- For role assignment and other tasks, provide CLI and portal links in addition to PowerShell tutorials.
- Explicitly state that the Azure CLI and Bicep tools are cross-platform, and provide guidance for Linux/macOS users where behaviors or commands differ.
Create Pull Request