Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Bash and PowerShell examples for querying logs via Azure CLI, but PowerShell examples are consistently shown after Bash. However, there are subtle signs of Windows bias: the Bash examples use 'SET' (a Windows CMD command) instead of 'export' (the standard for Bash on Linux/macOS), and the PowerShell examples use Windows-specific cmdlets (Invoke-AzOperationalInsightsQuery). There is no explicit mention of Linux/macOS tools or shell environments, and the use of 'SET' in Bash examples may confuse Linux users. No Linux/macOS-specific troubleshooting or parity notes are present.
Recommendations
- Replace 'SET' with 'export' in Bash examples to match standard Linux/macOS usage.
- Add explicit notes clarifying that Bash examples are intended for Linux/macOS and CMD examples for Windows.
- Provide troubleshooting tips or environment notes for Linux/macOS users (e.g., Azure CLI installation, shell compatibility).
- Ensure parity in example order (sometimes show Bash first, sometimes PowerShell) or clarify that both are equally supported.
- Include a brief section on running Azure CLI commands in Linux/macOS terminals.
Create Pull Request