Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication and resource listing, but PowerShell examples are given equal prominence and detail, despite PowerShell being primarily a Windows tool. There are references to Visual Studio Code and PowerShell for template deployment, but no mention of Linux-native editors or tools. The documentation does not provide explicit Linux shell (bash) examples beyond Azure CLI, nor does it reference Linux-specific patterns or alternatives to Windows-centric tools. The order of examples sometimes places PowerShell before or alongside CLI, which may suggest Windows-first thinking. There are no explicit Linux or macOS-specific instructions or troubleshooting notes.
Recommendations
- Add explicit bash shell examples for REST calls and authentication, especially for steps that use PowerShell.
- Reference Linux-native editors (e.g., Vim, Nano) or cross-platform alternatives alongside Visual Studio Code.
- Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Provide troubleshooting notes or tips for Linux/macOS users where file paths, environment variables, or authentication flows may differ.
- Avoid referencing PowerShell as the default or primary method; present Azure CLI or bash examples first when possible.
- Include links to Linux/macOS installation guides for Azure CLI and other required tools.
Create Pull Request