Bias Analysis
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for all major workflows, but PowerShell (a Windows-centric tool) is given equal prominence as CLI, and some ARM template and REST examples reference PowerShell deployment commands. The section on accessing config maps in containers gives a Linux example (mount path) and a Windows example (PowerShell command), but the Windows method is less clear and relies on Windows tooling. There is no explicit Linux shell example for accessing config map values inside the container, and PowerShell is mentioned before Linux shell alternatives in several places.
Recommendations
- Add explicit Linux shell examples for accessing config map values inside containers (e.g., using 'cat' or 'ls' on the mount path).
- Clarify the Windows container config map access method, and provide a more concrete example (e.g., using 'type' or other Windows shell commands, not just PowerShell).
- Consider listing CLI (cross-platform) examples before PowerShell in each tab group to reduce Windows-first perception.
- Where ARM template and REST examples mention deployment tools, highlight cross-platform options (e.g., Azure CLI, Bicep) before PowerShell.
- Add notes about which commands are cross-platform and which are Windows-only, especially for PowerShell scripts.
Create Pull Request