Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is given equal or sometimes slightly more detailed coverage. PowerShell examples and explanations are consistently presented alongside Azure CLI, but CLI is not always prioritized or explained first. There are no Linux/macOS-specific shell examples (e.g., Bash), nor are there explicit mentions of Linux environments or tooling. The documentation assumes users are familiar with PowerShell, which is primarily a Windows tool, and does not offer parity for Linux-native scripting or package management. REST API and SDK options are mentioned, but not with platform-specific guidance.
Recommendations
- Prioritize Azure CLI examples before PowerShell, as CLI is cross-platform and native to Linux/macOS.
- Explicitly mention that Azure CLI commands work on Linux/macOS and provide Bash-specific usage notes where relevant.
- Include references to Linux/macOS environments in installation and usage instructions (e.g., package managers like apt, yum, or Homebrew for Azure CLI).
- Add a note clarifying PowerShell Core is available cross-platform, but CLI is the default/preferred option for Linux/macOS.
- Provide troubleshooting or environment setup tips for Linux/macOS users, especially for file paths and shell differences.
- Where programmatic examples are given, show how to parse JSON output in Bash (e.g., using jq) in addition to PowerShell object handling.
Create Pull Request