Bias Analysis
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash (Azure CLI) and PowerShell examples for all commands, ensuring cross-platform coverage. However, PowerShell examples are present for every command, and in some cases, PowerShell-specific cmdlets are used (e.g., Update-AzContainerApp), which are only available on Windows or require PowerShell Core on other platforms. Additionally, PowerShell tabs are always present, and in some sections, PowerShell examples use native cmdlets rather than the CLI, which may not be as accessible to Linux/macOS users. The order of tabs is Bash first, then PowerShell, which is good, but the heavy presence of PowerShell may create a perception of Windows bias.
Recommendations
- Clearly indicate that PowerShell examples using Az cmdlets require PowerShell Core and the Az module, and note their cross-platform compatibility.
- Where PowerShell examples use Azure CLI commands, clarify that these can be run in any shell, not just PowerShell.
- Consider adding explicit Linux/macOS notes or examples where PowerShell cmdlets are not available or not cross-platform.
- If possible, provide Bash-only or POSIX shell examples for all tasks, especially where PowerShell cmdlets are used.
- Add a brief section at the top explaining the cross-platform nature of Azure CLI and PowerShell, and any limitations.
Create Pull Request