Bias Analysis
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides both Bash (Azure CLI) and PowerShell examples throughout, but PowerShell (Windows-centric) is consistently presented as an equal alternative to Bash, rather than as a secondary option. There is a notable emphasis on PowerShell-specific tooling and patterns, such as the use of New-Az* and Set-Az* cmdlets, which are exclusive to Windows environments. The documentation does not mention Linux-specific tools or patterns (e.g., native Linux networking tools, shell scripting alternatives, or package managers), nor does it clarify that PowerShell examples are primarily for Windows users. Additionally, in some sections, PowerShell examples are given immediately after Bash, reinforcing parity rather than Linux-first guidance.
Recommendations
- Clearly indicate that PowerShell examples are intended for Windows users, and Bash examples are for Linux/macOS users.
- Consider presenting Bash (Linux/macOS) examples first, with PowerShell as a secondary option, to reinforce Linux parity.
- Add notes or guidance for users on Linux who may encounter issues with PowerShell-specific commands or concepts.
- Where possible, reference Linux-native tools or patterns (e.g., using native networking commands, environment variable handling) in addition to Azure CLI.
- Ensure that all features and steps are equally achievable on Linux, and call out any Windows-only limitations.
- Review included files (e.g., container-apps-create-portal-steps.md) for similar bias and update as needed.
Create Pull Request