Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page exhibits a Windows bias in several ways: PowerShell is consistently presented first and most examples use PowerShell, with CLI/bash examples appearing later and less frequently. Windows-specific tools and APIs (e.g., CommandLineToArgvW, ARMClient in PowerShell) are referenced without Linux alternatives. The 'Try it' instructions and troubleshooting sections focus on PowerShell, and there is limited coverage of bash scripting patterns or Linux-native troubleshooting. There are few, if any, examples using Linux shell scripting idioms, and the external script section prioritizes PowerShell (.ps1) files over bash scripts.
Recommendations
- Alternate the order of PowerShell and Azure CLI/bash examples so that Linux users see parity in guidance.
- Provide equivalent bash script examples for every PowerShell example, including inline and external script scenarios.
- Include Linux-native troubleshooting steps and tools (e.g., using tail, grep, jq) alongside PowerShell-centric guidance.
- Reference Linux system calls or APIs (e.g., exec, getopt) where CommandLineToArgvW is mentioned, or clarify cross-platform behavior.
- Expand the 'Try it' and quickstart sections to include Azure CLI/bash instructions and outputs.
- Ensure external script examples and sample URIs include both .ps1 and .sh files, and clarify extension requirements for bash scripts.
- Highlight that all deployment scripts run in Linux containers, and provide best practices for bash scripting in that environment.
Create Pull Request