Bias Analysis
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation page demonstrates a mild Windows bias. PowerShell (a Windows-centric tool) is mentioned first in prerequisites and examples, with explicit references to PowerShell cmdlets for obtaining values (e.g., tenantId and objectId). The creation and update of template specs are shown with both PowerShell and Azure CLI, but PowerShell examples are consistently presented before CLI. There are no explicit Linux-only examples, nor are Linux-specific tools or shell patterns (e.g., bash, sh, or Linux file paths) mentioned. The documentation assumes familiarity with PowerShell and Windows tools, and does not provide parity for Linux users in terms of command-line environment or alternative methods for obtaining required values.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present Azure CLI first to avoid implicit Windows-first bias.
- Provide explicit instructions or examples for obtaining tenantId and objectId using Azure CLI (e.g., 'az account show', 'az ad user show'), not just PowerShell cmdlets.
- Include notes or examples for Linux/macOS users, such as using bash shell, file paths, and command syntax.
- Clarify that both Azure CLI and PowerShell are cross-platform, but highlight any differences in usage or output between Windows and Linux environments.
- Add troubleshooting or environment setup guidance for Linux users, especially regarding file handling and command-line usage.
Create Pull Request