Automation

232
Total Pages
137
Linux-Friendly Pages
95
Pages with Bias
40.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

365 issues found
Showing 251-275 of 365 flagged pages
Automation Disable local authentication in Azure Automation ...in/articles/automation/disable-local-authentication.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively provides PowerShell examples and references PowerShell cmdlets for managing Azure Automation local authentication, without offering equivalent examples for Linux/macOS users (e.g., using curl, bash, or Azure CLI). Windows tools and patterns are mentioned first and exclusively, creating friction for non-Windows users.
Recommendations
  • Add REST API usage examples with curl or httpie for Linux/macOS users.
  • Provide Azure CLI equivalents for checking and updating the DisableLocalAuth property.
  • Include notes or sections explicitly addressing Linux/macOS workflows.
  • Reorder examples so that cross-platform methods (REST API, CLI) are shown before or alongside PowerShell.
GitHub Create Pull Request
Automation Disable system-assigned managed identity for Azure Automation account .../automation/disable-managed-identity-for-automation.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed PowerShell-based instructions for disabling a system-assigned managed identity, with no equivalent examples for Linux/macOS users (e.g., using Bash, curl, or Azure CLI). The only command-line example is Windows-centric, and PowerShell tools are referenced exclusively, creating friction for non-Windows users.
Recommendations
  • Add equivalent examples using Azure CLI and curl for REST API calls, suitable for Linux/macOS environments.
  • Include authentication steps for Azure CLI (az login) and how to acquire tokens for REST calls outside PowerShell.
  • Present cross-platform examples side-by-side or indicate which steps apply to which OS.
  • Explicitly mention that PowerShell examples are Windows-centric and provide links or guidance for Linux/macOS users.
GitHub Create Pull Request
Automation Deploy an extension-based Windows or Linux User Hybrid Runbook Worker in Azure Automation ...ation/extension-based-hybrid-runbook-worker-install.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation, while claiming to support both Windows and Linux, demonstrates several Windows-centric biases. Windows examples, tools, and patterns are consistently presented first or exclusively, especially in code samples, Bicep/ARM templates, and PowerShell cmdlets. Linux-specific instructions are minimal, sometimes absent, and often relegated to secondary tabs or notes. Windows tools (PowerShell, .NET Framework) are emphasized, with Linux requirements listed but not integrated into workflow examples. ARM/Bicep/CLI templates focus on Windows VM creation and extension installation, with no parallel Linux VM examples. Folder permissions and troubleshooting are described only for Windows paths, with Linux equivalents missing.
Recommendations
  • Provide Linux-first or side-by-side examples for all workflows, including Bicep, ARM, REST API, and CLI.
  • Include Linux VM creation and extension installation templates, not just Windows.
  • Expand PowerShell-heavy sections to include Bash/Shell or Python alternatives for Linux users.
  • Document Linux-specific folder permissions, troubleshooting steps, and proxy configuration in parity with Windows.
  • Ensure all code samples, especially those for extension installation and management, have Linux variants and are equally detailed.
  • Clarify Linux requirements and limitations in the same detail as Windows (e.g., hardening, Python version, CPU quota).
GitHub Create Pull Request
Automation Use Azure Private Link to securely connect networks to Azure Automation ...in/articles/automation/how-to/private-link-security.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a PowerShell-only example for configuring the 'publicNetworkAccess' property, with no equivalent CLI, Bash, or Linux-native instructions. The State Configuration section references PowerShell DSC, which is Windows-centric, and does not mention Linux alternatives or parity. The example scripts and configuration steps are presented with a Windows-first approach, and there are no explicit Linux/macOS command-line examples for key configuration tasks.
Recommendations
  • Add Azure CLI and Bash examples for setting 'publicNetworkAccess' and other configuration tasks, alongside PowerShell.
  • Include instructions or references for managing Desired State Configuration (DSC) on Linux, such as using the open-source DSC agent or alternatives.
  • Ensure that all automation and hybrid worker scenarios explicitly mention Linux support, and provide examples for both Windows and Linux where applicable.
  • Present examples for both platforms in parallel, or alternate which platform is shown first.
  • Clarify any platform-specific limitations or differences in feature support.
GitHub Create Pull Request
Automation Manage databases in Azure SQL databases using Azure Automation ...articles/automation/manage-sql-server-in-automation.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page is heavily focused on PowerShell and Windows-centric tools and patterns. All code samples use PowerShell cmdlets, with no mention of Bash, Azure CLI, or Linux/macOS scripting alternatives. Instructions for installing modules and running commands are given only for PowerShell, and the concept of Hybrid Runbook Worker is described in terms of Windows environments. There are no Linux/macOS-specific examples or guidance, and Windows/PowerShell terminology is used throughout.
Recommendations
  • Add equivalent examples using Azure CLI and Bash for connecting to Azure SQL and managing identities.
  • Include instructions for installing required modules and running scripts on Linux/macOS Hybrid Runbook Workers.
  • Clarify whether Hybrid Runbook Worker supports Linux, and provide setup steps if so.
  • Present examples for both Windows and Linux/macOS environments, or note any platform limitations explicitly.
  • Reference cross-platform tools and scripting languages where possible, not just PowerShell.
GitHub Create Pull Request
Automation Migrate an existing agent-based hybrid workers to extension-based-workers in Azure Automation ...g-agent-based-hybrid-worker-to-extension-based-workers.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. Windows examples, tools, and terminology are presented first and in greater detail, especially in code samples (Bicep, ARM template, PowerShell). The Bicep and ARM template sections only show Windows VM creation and extension installation, omitting Linux VM equivalents. PowerShell cmdlets and instructions are Windows-centric, with Linux-specific steps or commands either missing or relegated to notes. Folder permissions and requirements are described only for Windows paths, with no Linux equivalents. The Azure CLI and REST API sections mention both Windows and Linux extension types, but do not provide concrete Linux-focused examples.
Recommendations
  • Add parallel Linux VM creation and extension installation examples in Bicep and ARM template sections.
  • Provide explicit Linux PowerShell/CLI commands for installing and managing the Hybrid Worker extension.
  • List Linux folder permission requirements and management steps alongside Windows equivalents.
  • Ensure that all code samples and walkthroughs include both Windows and Linux paths/types, or use tabs to separate OS-specific instructions.
  • Present Windows and Linux options with equal prominence, avoiding Windows-first ordering.
GitHub Create Pull Request
Automation Azure Automation overview ...s/azure-docs/blob/main/articles/automation/overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for Azure Automation demonstrates a moderate Windows bias. PowerShell is mentioned repeatedly as the primary language for runbooks and configuration management (DSC), with only brief mention of Python. The Configuration Management section focuses exclusively on PowerShell Desired State Configuration (DSC), which is Windows-centric, without discussing Linux-native equivalents (e.g., Ansible, Chef, or native Linux DSC support). Shared resources and modules emphasize PowerShell Gallery integration and Microsoft Script Center, both Windows-oriented tools. While Linux support is acknowledged in several places, examples, tooling, and patterns are generally presented from a Windows-first perspective.
Recommendations
  • Include Linux-specific examples and workflows, such as Bash or Python runbooks, alongside PowerShell.
  • Discuss configuration management options for Linux, such as Ansible, Chef, or native Linux DSC (if supported), and clarify how Azure Automation interacts with them.
  • Highlight Linux module sources (e.g., PyPI for Python, or other Linux package repositories) in addition to PowerShell Gallery.
  • Provide parity in documentation for onboarding, managing, and automating Linux servers, including troubleshooting and best practices.
  • Ensure that all features and capabilities are described with both Windows and Linux use cases, not just Windows-centric ones.
GitHub Create Pull Request
Automation Manage Python 2 packages in Azure Automation ...-docs/blob/main/articles/automation/python-packages.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides explicit instructions for downloading Python packages and their dependencies using pip on a Windows 64-bit machine, but does not offer equivalent guidance or examples for Linux or macOS users. The only concrete command-line example is Windows-specific, and there is no mention of how to perform the same task on other platforms.
Recommendations
  • Add equivalent instructions and command-line examples for Linux/macOS users, such as using pip on those platforms.
  • Clarify that the process can be performed on any OS with Python and pip installed, not just Windows.
  • Provide sample commands for Linux/macOS (e.g., 'pip2 download -d <output dir> <package name>') and note any platform-specific considerations.
  • Consider presenting cross-platform instructions first, or in parallel, rather than Windows-only.
GitHub Create Pull Request
Automation Manage Runtime Environment and Associated Runbooks in Azure Automation ...main/articles/automation/manage-runtime-environment.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows/PowerShell bias. Most examples and instructions focus on PowerShell, with repeated references to PowerShell modules, cmdlets, and the PowerShell Gallery. Windows-centric terminology and tooling (e.g., Az PowerShell package, Get-Module) are used throughout, and examples for Linux/macOS users (such as Python runbooks or Linux package formats) are minimal, often mentioned only in passing or as notes. Windows/PowerShell examples are consistently presented first, and there is a lack of parity in detailed examples for Python/Linux environments.
Recommendations
  • Provide equally detailed examples for Python runbooks, including package management and execution, not just brief mentions.
  • Include explicit instructions and screenshots for managing Python/Linux runtime environments, such as uploading .whl files and troubleshooting Linux-specific issues.
  • Balance the order of examples so that Python/Linux options are presented alongside or before PowerShell/Windows options where appropriate.
  • Reference Linux/macOS tools and commands (e.g., pip, bash) where relevant, and clarify OS compatibility for each step.
  • Add troubleshooting and best practices sections for Linux/macOS users, similar to those provided for PowerShell.
GitHub Create Pull Request
Automation Quickstart - Enable managed identities for your Automation account using the Azure portal ...cles/automation/quickstarts/enable-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page is primarily focused on using the Azure portal UI, which is cross-platform. However, the only 'Next steps' link provided is to a PowerShell runbook tutorial, implicitly prioritizing Windows/PowerShell workflows. There are no references to Linux-native automation tools (such as Bash or Python runbooks), nor are Linux/macOS command-line alternatives mentioned. This creates a subtle bias toward Windows users and PowerShell-centric automation.
Recommendations
  • Include links or references to tutorials for Bash or Python runbooks using managed identities.
  • Add examples or documentation for enabling managed identities via Azure CLI or REST API, which are platform-agnostic.
  • Ensure parity in 'Next steps' by providing both PowerShell and non-Windows automation options.
  • Explicitly mention that the Azure portal UI is accessible from any OS/browser.
GitHub Create Pull Request
Automation Remove user-assigned managed identity for Azure Automation account ...n/articles/automation/remove-user-assigned-identity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell examples for command-line and REST API operations, referencing Windows-centric tools (PowerShell cmdlets) throughout, and omitting equivalent Linux/macOS shell examples (such as Azure CLI or curl). The PowerShell approach is presented first and as the default for scripting, with no mention of cross-platform alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add Azure CLI examples for all operations, especially for removing managed identities and verifying results.
  • Provide REST API invocation examples using curl or httpie, which are standard on Linux/macOS.
  • Explicitly mention that PowerShell is available cross-platform, but also offer native shell alternatives.
  • Reorder examples so that cross-platform or platform-neutral methods (Azure CLI, REST API with curl) are presented before or alongside PowerShell.
  • Include verification steps using Azure CLI (e.g., az automation account show) in addition to PowerShell.
GitHub Create Pull Request
Automation Azure Quickstart - Install Hybrid Worker extension on Azure portal. ...omation/quickstarts/install-hybrid-worker-extension.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on installing the Hybrid Worker extension on Windows Azure Virtual Machines. All step-by-step instructions, screenshots, and extension selection are for Windows, with no Linux-specific examples or guidance. The extension referenced is 'Azure Automation Windows Hybrid Worker', and there is no mention of the Linux equivalent or its installation process. Linux users are left without clear instructions, creating friction for non-Windows environments.
Recommendations
  • Add explicit instructions and screenshots for installing the Hybrid Worker extension on Linux Azure Virtual Machines.
  • Mention and show the selection of the 'Azure Automation Linux Hybrid Worker' extension where appropriate.
  • Clarify any differences in configuration or prerequisites for Linux VMs.
  • Present Windows and Linux instructions in parallel or clearly labeled sections.
  • Ensure that prerequisites and next steps reference both Windows and Linux scenarios.
GitHub Create Pull Request
Automation Runtime Environment in Azure Automation ...in/articles/automation/runtime-environment-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a notable Windows bias by prioritizing PowerShell as the primary scripting language, referencing Windows-centric tools (PowerShell, Az PowerShell), and providing examples and package details for PowerShell before Python. The Azure CLI is discussed only in the context of PowerShell, with no mention of its use in Python runbooks or Linux/macOS environments. There are no Linux-specific examples, tools, or patterns referenced, and PowerShell versions and features are described in greater detail than Python equivalents.
Recommendations
  • Add explicit examples and package details for Python runbooks, including how to use Azure CLI and custom packages in Python environments.
  • Clarify cross-platform support for Azure CLI and other packages, including any differences in usage or limitations on Linux/macOS.
  • Provide Linux/macOS-specific guidance or notes where relevant, such as file paths, environment variables, or shell usage.
  • Ensure parity in documentation depth for Python and other non-Windows scripting languages.
  • Include links to Python documentation and best practices for automation alongside PowerShell references.
GitHub Create Pull Request
Automation Use Source Control Integration in Azure Automation ...main/articles/automation/source-control-integration.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell-based examples and instructions for configuring source control integration in Azure Automation. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform scripting. The only command-line instructions use PowerShell cmdlets, and prerequisites and troubleshooting refer to Windows-centric tools and patterns. This creates friction for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI and/or REST API examples for all PowerShell instructions, especially for role assignment and source control configuration.
  • Provide Bash or shell script examples for common tasks, or clarify cross-platform alternatives.
  • Explicitly state platform requirements for PowerShell cmdlets and offer guidance for installing PowerShell Core on Linux/macOS if necessary.
  • Reorder examples so that platform-neutral or cross-platform methods (e.g., Azure portal, REST API, Azure CLI) are presented before or alongside PowerShell.
  • Include troubleshooting and encoding guidance relevant to Linux/macOS editors and environments.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation State Configuration issues ...automation/troubleshoot/desired-state-configuration.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows and PowerShell, with most troubleshooting steps, examples, and cmdlets focused on Windows environments. PowerShell DSC and related modules are referenced throughout, with explicit commands and error messages shown only for Windows. Linux troubleshooting is limited to a single scenario, and Linux-specific guidance is sparse or absent in most sections.
Recommendations
  • Provide equivalent Linux troubleshooting steps and examples for each scenario, especially where PowerShell or Windows-specific tools are referenced.
  • Include Linux shell commands and log locations for DSC troubleshooting alongside PowerShell examples.
  • Mention Linux DSC extension management and certificate handling, not just Windows PowerShell commands.
  • Ensure Linux onboarding, registration, and error resolution steps are as detailed as Windows steps.
  • Add links to Linux DSC documentation and community resources.
GitHub Create Pull Request
Automation Configure runbook input parameters in Azure Automation ...b/main/articles/automation/runbook-input-parameters.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias, primarily through its heavy reliance on PowerShell examples and Windows-centric tooling. Most code samples, parameter configuration, and automation instructions are provided for PowerShell and PowerShell Workflow runbooks, with only minimal coverage for Python (the only non-Windows-centric option). There are no examples or guidance for using Linux/macOS shells or CLI tools (such as Bash or Azure CLI), nor are there instructions for starting runbooks from non-Windows platforms. Windows tools and patterns (PowerShell cmdlets, C# SDK, etc.) are mentioned exclusively and often before any alternatives. Linux/macOS users are left without direct examples or parity in workflow.
Recommendations
  • Add equivalent examples using Azure CLI (az automation runbook start ...) for Linux/macOS users.
  • Provide Bash shell scripts for starting runbooks and passing parameters.
  • Clarify cross-platform compatibility of PowerShell Core (pwsh) and provide examples for Linux/macOS environments.
  • Include Python SDK examples for starting runbooks, not just C#.
  • Explicitly note any platform limitations or differences in parameter handling.
  • Reorder sections to present cross-platform options (Azure CLI, REST API, SDKs) before Windows-specific tools.
GitHub Create Pull Request
Automation Manage schedules in Azure Automation ...main/articles/automation/shared-resources/schedules.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong bias toward Windows and PowerShell tooling. All CLI examples use PowerShell cmdlets, and there is no mention of Bash, Azure CLI, or Linux/macOS-specific workflows. The only automation scripting language covered is PowerShell, and even ARM template deployment is shown via PowerShell. No Linux or cross-platform command-line examples are provided, and PowerShell is presented as the default/primary automation method.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets, showing how to create, link, disable, and remove schedules using az commands.
  • Explicitly mention that PowerShell cmdlets can be run on Linux/macOS using PowerShell Core, but also provide native Bash/Azure CLI alternatives.
  • Reorder sections so that Azure portal and cross-platform methods (ARM templates, Azure CLI) are presented before or alongside PowerShell examples.
  • Include notes or links to Linux/macOS setup guides for Azure Automation tasks.
  • Clarify which steps are platform-agnostic and which require Windows-specific tooling.
GitHub Create Pull Request
Automation Manage variables in Azure Automation ...main/articles/automation/shared-resources/variables.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell and Windows-centric tools (Az PowerShell cmdlets, internal cmdlets) are emphasized throughout, with examples and instructions almost exclusively for Windows PowerShell. There are no Bash, CLI, or Linux-native scripting examples. The only alternatives shown are Python runbooks, but these are not positioned as Linux-specific solutions. The documentation does not mention Linux or macOS environments, nor does it provide parity for users who may want to manage Azure Automation variables using Bash, Azure CLI, or other cross-platform tools.
Recommendations
  • Add examples for managing variables using Azure CLI (az automation variable ...), which is cross-platform.
  • Include Bash or shell script examples for Linux/macOS users, especially for common tasks like creating, retrieving, and updating variables.
  • Explicitly mention Linux/macOS compatibility in relevant sections, clarifying which tools and approaches work across platforms.
  • Reorder sections so that cross-platform or platform-neutral approaches (e.g., Azure portal, Azure CLI, Python) are presented before or alongside Windows PowerShell examples.
  • Provide guidance for users running runbooks or scripts on Linux Hybrid Runbook Workers, including any limitations or differences.
GitHub Create Pull Request
Automation Start a runbook in Azure Automation ...e-docs/blob/main/articles/automation/start-runbooks.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell-based examples and instructions for starting runbooks via the command line. There are no equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash, or REST API usage), and Windows tools and workflows are mentioned before cross-platform or Linux-native alternatives. This creates friction for non-Windows users, who must seek out other documentation or adapt Windows-centric instructions.
Recommendations
  • Add Azure CLI examples for starting runbooks, including parameter passing and job tracking.
  • Include REST API sample requests and responses for starting runbooks, with clear authentication steps.
  • Provide Bash or shell script equivalents where possible.
  • Clearly indicate which methods are cross-platform and which are Windows-only.
  • Reorder sections to present cross-platform options (portal, API, CLI) before Windows-specific tools.
  • Link directly to Linux/macOS relevant documentation where appropriate.
GitHub Create Pull Request
Automation Troubleshoot extension-based Hybrid Runbook Worker issues in Azure Automation .../troubleshoot/extension-based-hybrid-runbook-worker.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation generally provides parity between Windows and Linux troubleshooting steps for Hybrid Runbook Workers, with dedicated sections and commands for both platforms. However, there is a notable Windows bias: Windows examples and instructions are often presented before Linux equivalents, especially in general troubleshooting checklists and scenario resolutions. Windows-specific tools (PowerShell scripts, registry edits, event logs) are described in detail, sometimes with more context than Linux alternatives. Some troubleshooting scenarios (e.g., registry permissions, event logs, .NET errors) are Windows-only, with no Linux equivalent or guidance. The documentation also references Windows tools and patterns (e.g., PowerShell, registry editing) more frequently and with greater detail.
Recommendations
  • Alternate the order of Windows and Linux instructions to avoid always listing Windows first.
  • Ensure Linux troubleshooting steps are as detailed as Windows steps, including explanations for log locations, permissions, and service management.
  • Where Windows-specific tools (e.g., PowerShell scripts, registry edits) are mentioned, provide Linux equivalents or clarify if not applicable.
  • Add Linux-specific troubleshooting scenarios where relevant (e.g., authentication, certificate management, service failures).
  • Reference Linux logs and diagnostic commands (e.g., journalctl, systemctl, grep) where appropriate.
  • Clarify which scenarios are Windows-only and provide Linux alternatives or explicitly state if not applicable.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation managed identity issues ...n/articles/automation/troubleshoot/managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased toward Windows and PowerShell environments. All troubleshooting examples and code snippets use PowerShell cmdlets (e.g., Connect-AzAccount, Get-AzVM, Invoke-RestMethod), which are native to Windows and require PowerShell. There are no equivalent examples for Linux or macOS environments, such as using Azure CLI or Bash scripts. The documentation assumes the user is operating in a Windows-centric context, which may create friction for Linux/macOS users.
Recommendations
  • Provide equivalent troubleshooting steps and code examples using Azure CLI (az) and Bash scripts for Linux/macOS users.
  • Explicitly mention cross-platform alternatives where PowerShell is referenced, and clarify which steps are OS-agnostic.
  • Add notes or sections indicating how Linux/macOS users can perform the same actions, including authentication and error handling.
  • Where screenshots or UI instructions are given, clarify if they apply to all platforms or provide platform-specific guidance.
GitHub Create Pull Request
Automation Troubleshoot Azure Automation runbook issues ...blob/main/articles/automation/troubleshoot/runbooks.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell-based troubleshooting and examples, with nearly all code samples, cmdlet references, and module instructions centered around PowerShell and Windows-centric tools (e.g., PowerShell ISE, Az.Automation, AzureRM). There is little to no mention of Linux/macOS-specific workflows, shell environments, or cross-platform scripting approaches. Linux/macOS users are left to infer how to adapt the guidance, and there are no Bash, Python, or CLI examples for common troubleshooting scenarios.
Recommendations
  • Add equivalent troubleshooting steps and code samples for Bash, Azure CLI, and Python runbooks where applicable.
  • Explicitly mention cross-platform compatibility for PowerShell Core (pwsh) and clarify any Windows-only limitations.
  • Provide guidance for Linux/macOS users on how to author, test, and debug runbooks locally (e.g., using VS Code on Linux, running scripts with pwsh).
  • Include links to Azure CLI and REST API documentation for tasks that can be performed outside PowerShell.
  • Reorder examples so that cross-platform or neutral approaches (e.g., Azure CLI, REST API) are presented before or alongside Windows/PowerShell-specific methods.
GitHub Create Pull Request
Automation What's New in Azure Automation .../azure-docs/blob/main/articles/automation/whats-new.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page for Azure Automation updates shows a notable bias toward Windows and PowerShell. Most scripting and automation examples, features, and announcements focus on PowerShell (a Windows-centric tool), with frequent references to PowerShell versions and modules (AzureRM, Az). Windows is often mentioned first when discussing hybrid worker support, and Windows tools/patterns (PowerShell, VS Code extension for PowerShell) are emphasized. Linux support is present but typically mentioned as an add-on or secondary, and there are few explicit Linux-specific examples or tools highlighted.
Recommendations
  • Include Linux/bash examples and workflows alongside PowerShell in feature announcements and documentation.
  • Highlight Linux support equally when discussing hybrid worker features, not just as a secondary mention.
  • Provide parity in tooling recommendations (e.g., VS Code extensions for Python/bash, Linux shell scripting guidance).
  • Add explicit references and links to Linux documentation and migration guides where relevant.
  • Ensure that new features and retirements affecting both Windows and Linux are described with equal detail.
GitHub Create Pull Request
Automation Troubleshoot agent-based Hybrid Runbook Worker issues in Azure Automation ...icles/automation/troubleshoot/hybrid-runbook-worker.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. Many troubleshooting scenarios and examples are presented first or exclusively for Windows, using Windows-specific tools (PowerShell, registry edits, event logs, .exe config files, etc.). Linux troubleshooting is covered in a separate section, but Windows scenarios are more detailed and numerous, and some workarounds (e.g., editing Orchestrator.Sandbox.exe.config) are only described for Windows. Several sections provide only PowerShell or Windows command examples, with Linux equivalents either missing or relegated to later sections.
Recommendations
  • Ensure all troubleshooting steps and workarounds have Linux/macOS equivalents, or explicitly state if not applicable.
  • Provide Linux examples alongside Windows ones, not only in a separate section but also within each scenario where relevant.
  • Include Linux-specific commands, file paths, and log locations for each troubleshooting step.
  • Balance the number and detail of Linux scenarios to match Windows coverage.
  • Avoid presenting Windows examples first by default; alternate or present both platforms together.
GitHub Create Pull Request
Automation Runbook execution in Azure Automation ...in/articles/automation/automation-runbook-execution.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell and Windows-centric tools and patterns. All code examples are PowerShell, and references to modules, error handling, and job management are exclusively in the context of PowerShell. Windows-specific tools (e.g., WinSCP.exe, IIS, .NET Framework 4.7.2, UAC) are mentioned without Linux equivalents. There are no Bash, Python, or Linux shell examples, and Linux-specific scenarios are not addressed. Windows terminology and paths (e.g., C:\temp, .exe files) are used without mention of Linux alternatives.
Recommendations
  • Add equivalent examples for Bash, Python, or other supported Linux scripting languages.
  • Explicitly mention Linux support for Hybrid Runbook Workers, including any OS-specific requirements or limitations.
  • Include Linux-specific tools and patterns (e.g., SCP, Apache/Nginx administration, Linux file paths like /tmp).
  • Clarify which features and modules are available or limited on Linux Hybrid Runbook Workers.
  • Provide guidance on error handling and process management for Linux-based runbooks.
  • Balance references to Windows and Linux tools, listing both where applicable.
GitHub Create Pull Request
← Previous Page 11 of 15 Next →