Document Details
Automation Runbook Types
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 page demonstrates a strong Windows and PowerShell bias. PowerShell (including Windows PowerShell and PowerShell Workflow) is presented first and in the most detail, with extensive examples and troubleshooting focused on Windows paths, tools, and cmdlets. Many examples and limitations reference Windows-specific file paths (e.g., C:\modules), environment variables, and behaviors. There is little to no Linux-specific guidance, examples, or troubleshooting, and Linux is only mentioned in passing (e.g., 'can run on Linux Hybrid Worker'), without concrete examples or parity in troubleshooting. Python runbooks receive less coverage, and Linux-specific details are minimal.
Recommendations
- Provide Linux-specific examples for PowerShell runbooks, especially for Hybrid Runbook Workers running on Linux (e.g., file paths, environment variables, module locations).
- Include troubleshooting steps and known issues relevant to Linux environments, not just Windows (e.g., what to do if a module path is /usr/local/share/powershell/Modules).
- Balance the order and prominence of runbook types: consider presenting Python and PowerShell equally, or at least avoid always listing Windows/PowerShell first.
- Where Windows-specific tools or patterns are mentioned (e.g., C:\modules, .ps1 script execution), provide Linux equivalents (e.g., /opt/automation/modules, ./child-runbook.ps1 with Linux path syntax).
- Expand the Python runbook section to include more parity with PowerShell, such as common troubleshooting, best practices, and examples for both Windows and Linux Hybrid Workers.
- Explicitly call out any differences or additional steps required for Linux Hybrid Runbook Workers throughout the documentation, not just in limitations.
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 |
 Clean
|
| 2026-01-06 18:15 | #225 | cancelled |
Clean
|
| 2025-09-12 00:00 | #109 | completed |
Clean
|
| 2025-08-12 00:00 | #78 | cancelled |
Biased
|
| 2025-08-11 00:00 | #77 | completed |
Biased
|
| 2025-08-10 00:00 | #76 | completed |
Biased
|
| 2025-08-09 00:00 | #75 | completed |
Biased
|
| 2025-08-08 00:00 | #74 | completed |
Biased
|
| 2025-08-07 00:00 | #73 | completed |
Biased
|
| 2025-08-06 00:00 | #72 | completed |
Biased
|
| 2025-08-05 00:00 | #71 | completed |
Biased
|
| 2025-08-04 00:00 | #70 | cancelled |
Biased
|
| 2025-08-03 00:00 | #69 | completed |
Biased
|
| 2025-08-02 00:00 | #68 | cancelled |
Clean
|
| 2025-08-01 00:00 | #67 | completed |
Biased
|
| 2025-07-31 00:00 | #66 | completed |
Clean
|
| 2025-07-30 00:00 | #65 | completed |
Clean
|
| 2025-07-29 00:01 | #64 | completed |
Clean
|
| 2025-07-28 00:00 | #63 | completed |
Clean
|
| 2025-07-27 00:00 | #62 | completed |
Clean
|
| 2025-07-26 00:01 | #61 | completed |
Clean
|
| 2025-07-25 00:00 | #60 | completed |
Clean
|
| 2025-07-24 00:00 | #59 | completed |
Clean
|
| 2025-07-23 00:00 | #58 | completed |
Clean
|
| 2025-07-22 00:01 | #57 | completed |
Clean
|
| 2025-07-21 00:00 | #56 | completed |
Clean
|
| 2025-07-19 13:51 | #54 | completed |
Clean
|
| 2025-07-17 00:00 | #53 | completed |
Biased
|
| 2025-07-16 00:00 | #52 | completed |
Biased
|
| 2025-07-13 21:37 | #48 | completed |
Biased
|
| 2025-07-09 13:09 | #3 | cancelled |
Clean
|
| 2025-07-08 04:23 | #2 | cancelled |
Biased
|