Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are provided for nearly every major operation, and Windows-specific extension types (ApplicationHealthWindows) are shown before or alongside Linux equivalents. In several places, Windows tools and patterns (PowerShell scripts, Windows extension types) are presented before Linux alternatives, and the PowerShell example for the health endpoint response is more elaborate than the Bash/Python example. However, Linux/CLI examples are present throughout, and REST API examples are provided, mitigating the impact.
Recommendations
- Ensure Linux and Windows extension types are presented equally, with clear guidance for both (e.g., ApplicationHealthLinux and ApplicationHealthWindows).
- Present CLI/Bash examples before PowerShell examples to avoid implicit prioritization of Windows workflows.
- Expand Linux/macOS scripting examples (e.g., provide a shell-only or Python-only example for endpoint response, not requiring iptables or Python).
- Clarify in each example which OS/platform it applies to, and provide parity for both where possible.
- Where PowerShell is used, offer an equivalent Bash or shell script for Linux/macOS users.
- Explicitly mention that all features are available on both Linux and Windows VMSS, and link to OS-specific extension documentation.
Create Pull Request