Bias Analysis
Detected Bias Types
windows_first
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation provides both Linux and Windows examples for creating Batch pools with extensions, and lists supported extensions for both platforms. However, there is a slight Windows bias: Windows-specific extensions (e.g., Antimalware, Diagnostics, HPC GPU for AMD) are more numerous and detailed, and Windows tools/patterns (such as certificateStoreLocation: 'LocalMachine') are referenced. The troubleshooting section refers to logging into the node and checking logs, but does not specify Linux log locations or commands. The Application Health extension section is platform-neutral, but overall, Windows examples and tools are slightly more prominent.
Recommendations
- Ensure equal detail for Linux and Windows extension examples, including troubleshooting steps and log locations for Linux.
- Add explicit Linux command-line or log file references for troubleshooting (e.g., where to find Key Vault extension logs on Linux).
- Where Windows tools or concepts are mentioned (e.g., 'LocalMachine' certificate store), provide Linux equivalents or explanations.
- Balance the order of extension listings and examples so Linux is not always second.
- If possible, add more Linux-specific extension examples or highlight parity in supported features.
Create Pull Request