Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell examples are consistently presented before Azure CLI (which is more cross-platform), and instructions for opening terminals reference PowerShell and Visual Studio Code, which are more commonly used on Windows. The use of PowerShell-specific features (like splatting) and terminology (e.g., 'PowerShell terminal') further reinforces a Windows-centric approach. There is no mention of Linux-specific editors, shells (other than Bash), or alternative workflows for Linux users. Visual Studio Code is recommended as the editor, which is cross-platform but often associated with Windows. No explicit Linux examples or troubleshooting notes are provided.
Recommendations
- Alternate the order of Azure PowerShell and Azure CLI examples so CLI is presented first in some sections, or default to CLI where possible.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide guidance for opening terminals on Linux (e.g., GNOME Terminal, Konsole) and macOS (Terminal.app).
- Add notes or links for installing and using Bicep and Azure CLI on Linux and macOS, including editor recommendations (e.g., Vim, Emacs, or VS Code on Linux).
- Avoid PowerShell-specific terminology (like 'PowerShell terminal') in general instructions; use neutral terms such as 'terminal' or 'command prompt'.
- Where PowerShell splatting or other Windows-centric features are used, provide equivalent CLI or Bash scripting examples for Linux users.
- Add troubleshooting or environment setup notes for Linux and macOS users, especially for file paths, permissions, and shell differences.
Create Pull Request