Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation generally presents both Azure PowerShell and Azure CLI options for resource creation, but in several instances, PowerShell is mentioned or linked before Azure CLI. In the 'Alternate way to get the Azure Container Instance ID' section, the PowerShell example is given before the Azure CLI example. Additionally, in the 'Create a virtual network' section, the PowerShell link precedes the CLI link. This ordering may subtly prioritize Windows/PowerShell users over Linux/CLI users, though both options are present. No exclusive use of Windows tools or missing Linux examples were found.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples and links throughout the documentation to avoid implicit prioritization.
- Where possible, provide both PowerShell and CLI examples side-by-side, or in a tabbed format, to make parity explicit.
- In sections where command-line examples are given, ensure that Azure CLI (cross-platform) is presented first or equally with PowerShell.
- Review screenshots and UI instructions to ensure they are not Windows-specific unless necessary.
- Explicitly state that both PowerShell and Azure CLI are supported and cross-platform, and clarify that users can choose either based on their environment.
Create Pull Request