Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and cleaning up resources. However, PowerShell examples are given equal prominence to CLI, and the prerequisites section lists Visual Studio Code and the Bicep extension as required tools, which are cross-platform, but does not mention any Linux-specific editors or workflows. There is no explicit mention of Linux shell usage (e.g., Bash), nor are there any examples tailored for Linux environments (such as shell script snippets or Linux-specific instructions). The documentation implicitly assumes familiarity with Windows/PowerShell patterns by listing PowerShell as a primary deployment method.
Recommendations
- Add explicit Bash shell examples for deployment and cleanup, demonstrating usage on Linux/macOS.
- Clarify that Azure CLI commands work cross-platform and provide sample commands using Bash syntax (e.g., export variables, use $VAR notation).
- Mention Linux-native editors (such as Vim, Nano) as alternatives to Visual Studio Code for editing Bicep files.
- Include a note or section on setting up Bicep tools in Linux environments, including package manager installation instructions (apt, yum, etc.).
- Ensure that CLI examples precede PowerShell examples to avoid implicit Windows-first bias.
Create Pull Request