Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for all operations, but PowerShell (a Windows-centric tool) is consistently presented alongside CLI, sometimes with more detail (e.g., accepting Marketplace terms). There is no explicit mention of Linux-specific tools or shell patterns (such as Bash scripting), and PowerShell is referenced as a primary automation method, which may implicitly favor Windows users. Additionally, the naming conventions and resource group patterns use Windows-style casing (PascalCase), and there is no discussion of Linux-specific considerations or alternative workflows.
Recommendations
- Add explicit Bash shell script examples for all CLI commands to demonstrate Linux-native automation.
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Include notes or sections on Linux-specific considerations, such as file permissions, environment variables, or shell differences when moving VMs.
- Avoid presenting PowerShell as the default or primary automation method; alternate CLI and PowerShell examples, or lead with CLI (which is more cross-platform).
- Mention that PowerShell Core is available on Linux, but provide guidance for users who prefer native Linux tools.
- Review resource naming conventions to ensure they are not implicitly Windows-centric.
Create Pull Request