Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Bash and Azure PowerShell examples for most CLI steps, but consistently lists Bash first and PowerShell second. However, there are several signs of Windows bias: PowerShell is presented as a primary shell alongside Bash, and some instructions (such as activating Python virtual environments) only show the Bash/Linux command, with no Windows/PowerShell equivalent. There is also an assumption that users have access to both Bash and PowerShell, which is not always the case on Linux or macOS. The cleanup section contains a typo in the PowerShell variable name, and the documentation does not provide explicit Windows command prompts or CMD examples, nor does it address differences in environment variable syntax between shells.
Recommendations
- Explicitly state which steps are for Linux/macOS (Bash) and which are for Windows (PowerShell), and clarify that Bash is available on Windows via WSL or Git Bash.
- Provide Windows CMD and/or PowerShell equivalents for all Bash commands, especially for Python virtual environment activation (e.g., `env\Scripts\activate` for Windows).
- Ensure that environment variable syntax is correct for each shell (e.g., `$env:connection_string = "..."` for PowerShell, `set connection_string=...` for CMD, `export connection_string=...` for Bash).
- Consider including a table summarizing the shell differences and how to adapt commands for each platform.
- Fix the typo in the PowerShell cleanup command (`$ResourceGroup` should match earlier variable names).
- Where possible, provide cross-platform guidance or links to official documentation on running Bash on Windows and PowerShell on Linux/macOS.
Create Pull Request