Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation shows a notable Windows bias in deployment examples and tooling. In multi-tabbed deployment sections, Windows/PowerShell examples are consistently presented first, with Linux/Azure CLI examples following. PowerShell is the only scripting language shown for imperative scripting, and all PowerShell examples target Windows-based scale sets. REST API examples also default to Windows. Linux-specific examples are only present in the Azure CLI sections, and there are no Linux PowerShell or Bash scripting examples. Troubleshooting commands are PowerShell-centric, and Windows log paths are listed before Linux equivalents. This ordering and tooling focus create friction for Linux/macOS users.
Recommendations
- Present Linux and Windows examples in parallel, or alternate which is shown first to avoid implicit prioritization.
- Provide imperative scripting examples for Linux users (e.g., Bash scripts using Azure CLI, or cross-platform PowerShell with ApplicationHealthLinux).
- Ensure REST API examples alternate or include both ApplicationHealthLinux and ApplicationHealthWindows in the 'type' property.
- In troubleshooting, show Linux log paths before or alongside Windows paths, and provide Azure CLI commands for health state retrieval.
- Explicitly state that all extension operations are supported on both Linux and Windows, and clarify any differences in behavior or support.
Create Pull Request