Document Details
Extension Based Hybrid Runbook Worker Install
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation exhibits several signs of Windows bias. Windows and PowerShell examples are consistently presented first and in greater detail, with Linux equivalents often relegated to secondary tabs or brief mentions. The use of Windows-specific tools (e.g., Windows PowerShell 5.1, .NET Framework) is emphasized, while Linux requirements and tooling are less thoroughly explained. Infrastructure-as-code examples (Bicep, ARM templates) and REST API samples are focused on Windows VM creation and extension installation, with no parallel Linux VM examples. Folder and permission paths are Windows-centric, and troubleshooting notes often reference Windows features (UAC/LUA, registry keys) without Linux alternatives. The documentation lacks parity in Linux-specific automation, deployment, and management workflows.
Recommendations
- Provide Linux-first or side-by-side examples for all deployment, management, and troubleshooting steps, including PowerShell, CLI, Bicep, ARM, and REST API workflows.
- Expand infrastructure-as-code samples (Bicep, ARM templates) to include Linux VM creation and extension installation, with clear parameterization for OS type.
- Include Linux-specific tooling and requirements (e.g., shell commands, package managers, systemd integration) where Windows tools are referenced.
- Balance the explanation of prerequisites and permissions, detailing Linux file paths, permissions, and security contexts (e.g., SELinux, sudoers) alongside Windows equivalents.
- Add troubleshooting and operational guidance for Linux environments, such as log file locations, service management, and common issues.
- Ensure all code snippets and instructions are available for both platforms, and avoid presenting Windows examples before Linux unless contextually justified.
- Reference Linux documentation and best practices as prominently as Windows resources in the 'Next steps' and related links sections.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-12 00:00 | #243 | cancelled |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Biased
|
| 2026-01-06 18:15 | #225 | cancelled |
 Clean
|
| 2025-08-17 00:01 | #83 | cancelled |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Clean
|
| 2025-07-09 13:09 | #3 | cancelled |
Clean
|
| 2025-07-08 04:23 | #2 | cancelled |
Biased
|