About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
powershell_heavy
⚠️
windows_first
⚠️
windows_tools
Summary:
The documentation provides comprehensive coverage for multiple deployment methods (Portal, PowerShell, CLI, ARM, Bicep, Terraform), but exhibits a Windows/PowerShell bias in several ways. PowerShell is given a prominent, detailed walkthrough with extensive explanations and code samples, often before CLI/Linux-native alternatives. The PowerShell sections reference Windows-specific tools and installation patterns (e.g., Azure PowerShell module, Get-Module), and the ARM template cleanup instructions reference PowerShell rather than CLI/bash. While Linux is represented (e.g., Ubuntu VM examples, CLI usage), the documentation structure and depth of PowerShell content suggest a Windows-first approach.
Recommendations:
- Ensure that CLI (az) and bash examples are as detailed and prominent as PowerShell, including explanations for environment setup and troubleshooting.
- Where PowerShell-specific instructions are given (e.g., module installation, cleanup), provide equivalent bash/CLI/Linux-native instructions alongside or before them.
- In ARM and Bicep template deployment and cleanup sections, include both PowerShell and CLI/bash commands for parity.
- Review the order of tabs and sections to avoid consistently placing PowerShell/Windows content before CLI/Linux content.
- Audit for references to Windows-specific tools or patterns (such as 'Get-Module') and ensure Linux equivalents (such as checking az CLI version) are also provided.
- Highlight that Azure Cloud Shell supports both bash and PowerShell, and provide instructions for both where relevant.
Create pull request