Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples and tooling are presented alongside Azure CLI, but PowerShell is often given equal or greater prominence, and Windows-centric tools (e.g., Azure PowerShell, ARMClient in PowerShell context) are used for deployment and management tasks. Script deployment instructions are provided only for Azure PowerShell, with no Linux-native shell or cross-platform alternatives (e.g., Bash, Bash+az CLI, or Linux scripting). There is no explicit example of deploying Bicep files using Bash or Linux-native commands, and PowerShell is referenced for authentication and management tasks before CLI equivalents. The documentation does not provide parity for Linux-first or cross-platform workflows.
Recommendations
- Add explicit Bash/Linux shell examples for deploying Bicep files, using az CLI commands (e.g., az group create, az deployment group create).
- Present CLI and PowerShell examples in parallel, rather than PowerShell-first or exclusively.
- Include instructions for script deployment and management using Linux-native tools and workflows.
- Reference cross-platform tools and patterns before or alongside Windows-specific ones.
- Clarify that both Azure CLI and PowerShell are supported and provide guidance for users on both platforms.
- Where ARMClient is referenced, provide CLI usage examples or alternatives.
- Ensure that all code samples and management instructions are available for both Windows and Linux environments.
Create Pull Request