Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation exhibits a moderate Windows bias. In multi-platform code tabs, Windows/PowerShell examples are consistently presented first, and REST API examples use Windows-based scale sets by default. PowerShell (a Windows-centric tool) is given prominent coverage, with Linux/CLI examples appearing later. REST and PowerShell examples default to 'ApplicationHealthWindows' and Windows resource names, while Linux examples are only provided under Azure CLI sections. Troubleshooting commands are PowerShell-focused, and Windows log file paths are listed before Linux equivalents.
Recommendations
- Present Linux and Windows examples with equal prominence, alternating which appears first or grouping by OS rather than tool.
- In REST API and JSON schema examples, provide both 'ApplicationHealthLinux' and 'ApplicationHealthWindows' variants, or use a neutral placeholder.
- Include Azure CLI and PowerShell examples for both Linux and Windows scale sets in all relevant sections.
- In troubleshooting, provide equivalent Linux commands (e.g., using Azure CLI or Bash) alongside PowerShell.
- List Linux and Windows log file paths together or alternate their order.
- Use neutral resource names (e.g., 'myVMScaleSet' instead of 'myVMScaleSet' for Windows and 'myLinuxVMScaleSet' for Linux) in examples.
Create Pull Request