Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
minor_linux_segregation
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all queries, with the Portal as a third option. However, PowerShell (a Windows-centric tool) is always given equal prominence to Azure CLI, and in some cases, the PowerShell tab appears before CLI in the tab order. There are also separate queries for Windows and Linux OS update installations, but the Windows example appears before the Linux one, and the Linux example is segregated rather than integrated. There are no Linux/macOS-specific command-line examples (e.g., bash scripts), and no mention of Linux-native tools or shell environments. The documentation assumes parity between CLI and PowerShell, but the prominence of PowerShell and the ordering of Windows/Windows Server examples before Linux ones indicate a subtle Windows bias.
Recommendations
- Ensure Azure CLI examples are always listed before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Where possible, add bash or shell script examples for Linux/macOS users, especially for common automation scenarios.
- When presenting OS-specific queries (e.g., update installation), present Linux and Windows examples together, or alternate their order to avoid always prioritizing Windows.
- Explicitly mention that Azure CLI works on all platforms and highlight its use for Linux/macOS users.
- Consider adding a 'Linux/macOS' tab for any platform-specific guidance or troubleshooting.
- Review tab order and documentation structure to avoid implicit prioritization of Windows tools or workflows.
Create Pull Request