Bias Analysis
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation page exhibits a strong Windows bias, primarily through exclusive use of PowerShell examples, Windows-centric file paths, and references to Windows tools and patterns. There are no CLI/bash examples, nor any mention of Linux/macOS-specific workflows or tools. All code samples and automation instructions rely on PowerShell cmdlets, which are native to Windows and only available on Linux/macOS via PowerShell Core, which is not referenced. Windows file paths (e.g., C:\Runbooks\...) are used, and there is no guidance for Linux/macOS users regarding file locations, shell usage, or alternative approaches. The documentation assumes familiarity with Windows conventions and does not provide parity for Linux/macOS users.
Recommendations
- Add Azure CLI/bash examples alongside PowerShell for all major tasks (creating, importing, publishing, retrieving runbook/job status).
- Include Linux/macOS file path examples and clarify cross-platform compatibility for scripts and automation.
- Mention PowerShell Core and its installation/usage on Linux/macOS where PowerShell is required.
- Explicitly state platform requirements and provide guidance for Linux/macOS users on how to adapt instructions.
- Where possible, provide REST API or SDK-based examples that are platform-agnostic.
- Ensure that references to tools (e.g., file browsers, script editors) include Linux/macOS equivalents.
Create Pull Request