What is the difference between Azure sandbox and Hybrid Runbook Worker execution?

Azure sandboxes are shared, multi-tenant environments in Azure where runbooks execute with a maximum runtime of 3 hours (fair share limit) and limited resource access (no local admin, restricted networking). Hybrid Runbook Workers are agents you install on your own VMs (on-premises or in Azure) where runbooks run without the 3-hour limit and with access to local resources. Use sandbox execution for Azure resource management tasks. Use Hybrid Workers for runbooks that need to access on-premises resources, run longer than 3 hours, or require specific software installed on the execution environment.

How do webhooks work with runbooks?

A webhook provides a URL that can be called with an HTTP POST to trigger a runbook. The POST body is passed as a parameter to the runbook. Webhooks have an expiration date (maximum 10 years) and can be enabled or disabled without regenerating the URL. Each webhook is linked to a specific runbook and can pre-fill parameter values. Webhooks are useful for integrating with external systems (ServiceNow, PagerDuty, GitHub) or Azure Monitor action groups. The webhook URL contains a security token — treat it as a secret and store it securely.

Automation Runbook Builder

ServerlessAzure

Build Azure Automation runbook configurations with schedules and webhooks.

Azure Automation Configuration

Build Automation runbook schedule configs with webhooks, variables, and advanced scheduling.

Required Fields

automationAccountNameresourceGrouprunbook.namerunbook.typeschedules

{
  "automationAccountName": "aa-ops-prod",
  "resourceGroup": "rg-automation",
  "location": "eastus2",
  "identity": {
    "type": "SystemAssigned"
  },
  "runbook": {
    "name": "Stop-IdleVMs",
    "type": "PowerShell",
    "runtimeVersion": "7.2",
    "description": "Identifies and stops VMs that have been idle for more than 2 hours during non-business hours",
    "logVerbose": true,
    "logProgress": true,
    "publishContentLink": {
      "uri": "https://strunbooks.blob.core.windows.net/runbooks/Stop-IdleVMs.ps1",
      "version": "2.1.0"
    }
  },
  "schedules": [
    {
      "name": "weeknight-cleanup",
      "description": "Run every weeknight at 10 PM EST",
      "startTime": "2026-03-15T22:00:00-05:00",
      "expiryTime": "2027-03-15T22:00:00-05:00",
      "frequency": "Week",
      "interval": 1,
      "timeZone": "Eastern Standard Time",
      "advancedSchedule": {
        "weekDays": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"]
      },
      "parameters": {
        "ResourceGroupFilter": "rg-dev-*",
        "IdleThresholdMinutes": "120",
        "DryRun": "false"
      }
    },
    {
      "name": "weekend-shutdown",
      "description": "Full shutdown of dev resources on Saturday morning",
      "startTime": "2026-03-21T06:00:00-05:00",
      "frequency": "Week",
      "interval": 1,
      "timeZone": "Eastern Standard Time",
      "advancedSchedule": {
        "weekDays": ["Saturday"]
      },
      "parameters": {
        "ResourceGroupFilter": "rg-dev-*",
        "IdleThresholdMinutes": "0",
        "DryRun": "false"
      }
    }
  ],
  "webhooks": [
    {
      "name": "wh-emergency-stop",
      "isEnabled": true,
      "expiryTime": "2027-03-14T00:00:00Z",
      "parameters": {
        "ResourceGroupFilter": "*",
        "IdleThresholdMinutes": "0",
        "DryRun": "false"
      }
    }
  ],
  "variables": [
    {
      "name": "ExcludedVMs",
      "value": "vm-jumpbox-prod,vm-dc-01",
      "isEncrypted": false
    },
    {
      "name": "SlackWebhookUrl",
      "value": "https://hooks.slack.com/services/T00/B00/xxxxx",
      "isEncrypted": true
    }
  ]
}

Generated Output

Output will appear here...

About This Tool

Azure Automation provides a managed service for process automation using PowerShell or Python runbooks that run in Azure sandbox or Hybrid Runbook Worker environments. Runbooks can automate resource management, respond to alerts, enforce compliance, and perform scheduled maintenance tasks. Configuration involves defining the runbook type (PowerShell, Python, Graph), schedule triggers, webhook endpoints for event-driven execution, and input parameters. The Automation Runbook Builder helps you configure runbook settings, schedules, webhook configurations, and connection assets for common automation scenarios.

When to Use This Tool

•Creating scheduled runbooks that stop non-production VMs at night and start them in the morning to reduce costs
•Building webhook-triggered runbooks that respond to Azure Monitor alerts and perform automated remediation
•Configuring runbooks with schedule recurrence patterns for monthly patch management or compliance reporting

Frequently Asked Questions

What is the difference between Azure sandbox and Hybrid Runbook Worker execution?: Azure sandboxes are shared, multi-tenant environments in Azure where runbooks execute with a maximum runtime of 3 hours (fair share limit) and limited resource access (no local admin, restricted networking). Hybrid Runbook Workers are agents you install on your own VMs (on-premises or in Azure) where runbooks run without the 3-hour limit and with access to local resources. Use sandbox execution for Azure resource management tasks. Use Hybrid Workers for runbooks that need to access on-premises resources, run longer than 3 hours, or require specific software installed on the execution environment.
How do webhooks work with runbooks?: A webhook provides a URL that can be called with an HTTP POST to trigger a runbook. The POST body is passed as a parameter to the runbook. Webhooks have an expiration date (maximum 10 years) and can be enabled or disabled without regenerating the URL. Each webhook is linked to a specific runbook and can pre-fill parameter values. Webhooks are useful for integrating with external systems (ServiceNow, PagerDuty, GitHub) or Azure Monitor action groups. The webhook URL contains a security token — treat it as a secret and store it securely.

Related Learning Guides

Azure DevOps Pipelines CI/CD25 min read

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.