Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation lists methods for discovering Azure Policy aliases, presenting the Visual Studio Code extension (cross-platform) first, but then gives Azure PowerShell examples before Azure CLI and REST API. The PowerShell section is more detailed, including advanced usage notes and examples, while the Azure CLI section is shorter and less emphasized. This ordering and depth may create friction for Linux/macOS users, as PowerShell is traditionally Windows-centric and CLI is more common on Linux/macOS.
Recommendations
- Provide equally detailed examples and notes for Azure CLI, matching the PowerShell section (e.g., how to filter for modifiable aliases).
- Consider listing Azure CLI before PowerShell, as CLI is more universally available across platforms.
- Explicitly mention cross-platform compatibility for each tool, clarifying that PowerShell Core and VS Code are available on Linux/macOS.
- Add links or notes for installing Azure CLI and PowerShell on Linux/macOS.
- Ensure advanced usage scenarios (such as filtering for modifiable aliases) are shown for both CLI and PowerShell.
Create Pull Request