Bias Analysis
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides both Bash and Azure PowerShell examples for all CLI steps, but PowerShell is given equal prominence to Bash, and is explicitly called out as a required shell in prerequisites. There is a slight Windows bias in the consistent inclusion of Azure PowerShell examples, even for steps that are natively cross-platform (Azure CLI), and in the assumption that users may use PowerShell locally. There are no explicit Linux-only examples or mentions of Linux-specific tools or patterns. The language SDK examples (Python, JavaScript, Java, C#) are Bash-centric, but the overall parity between Windows and Linux is not fully clear, and PowerShell is sometimes presented before Bash in variable naming conventions and explanations.
Recommendations
- Clarify that Azure CLI commands work equally well on Linux, macOS, and Windows, and that Bash is available on all platforms.
- Make Bash the default/primary example, with PowerShell as an optional tab for Windows users.
- Add explicit notes for Linux/macOS users, including shell environment setup and common editors (e.g., mention nano/vim in addition to VS Code).
- Where PowerShell is used, explain its cross-platform availability, or clarify when it is Windows-specific.
- Consider including Linux-specific troubleshooting or environment setup steps, such as package manager commands for dependencies.
- Avoid listing PowerShell as a prerequisite unless it is strictly required; emphasize Bash or sh for cross-platform compatibility.
Create Pull Request