Bias Analysis
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The documentation page exhibits a strong Windows bias, primarily through the exclusive use of PowerShell for all command-line examples and automation steps. PowerShell cmdlets are used for REST API calls, ARM template deployments, role assignments, and authentication, with no mention of Bash, Azure CLI, or Linux-native tools. Even generic HTTP requests are demonstrated using PowerShell, and file paths use Windows conventions. The only non-PowerShell example is a Python snippet, but it does not address shell or CLI parity. There are no Linux/macOS-specific instructions or examples, and PowerShell is presented as the default and only scripting environment.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell cmdlets, especially for resource creation, role assignment, and authentication.
- Provide Bash shell examples for REST API calls using curl or wget, including access token retrieval.
- Use platform-neutral file path conventions (e.g., forward slashes) or clarify path usage for different OSes.
- Explicitly mention that PowerShell Core is cross-platform, but also provide instructions for Linux/macOS users who may prefer Bash or Azure CLI.
- Include troubleshooting notes or links for Linux/macOS users regarding environment setup and authentication differences.
- Reorder examples so that platform-neutral or cross-platform methods (portal, REST API, ARM template) are presented before platform-specific scripting.
Create Pull Request