Azure Monitor Action Group Builder

MonitoringAzure

Build action group notification configs with email, SMS, voice, webhooks, PagerDuty, Azure Functions, and Automation Runbooks.

Azure Monitor Configuration

Build action group notification configs with email, SMS, voice, webhooks, PagerDuty, Slack, Azure Functions, Logic Apps, and Automation Runbooks.

Required Fields

actionGroupNameresourceGroupshortNameenabled

{
  "actionGroupName": "ag-critical-alerts",
  "resourceGroup": "rg-monitoring",
  "location": "global",
  "shortName": "CritAlert",
  "enabled": true,
  "emailReceivers": [
    {
      "name": "SOC Team Email",
      "emailAddress": "soc-team@contoso.com",
      "useCommonAlertSchema": true
    },
    {
      "name": "On-Call Engineer",
      "emailAddress": "oncall@contoso.com",
      "useCommonAlertSchema": true
    }
  ],
  "smsReceivers": [
    {
      "name": "On-Call SMS",
      "countryCode": "1",
      "phoneNumber": "5550199"
    }
  ],
  "voiceReceivers": [
    {
      "name": "Escalation Voice",
      "countryCode": "1",
      "phoneNumber": "5550200"
    }
  ],
  "webhookReceivers": [
    {
      "name": "PagerDuty",
      "serviceUri": "https://events.pagerduty.com/integration/<integration-key>/enqueue",
      "useCommonAlertSchema": true,
      "useAadAuth": false
    },
    {
      "name": "Slack Webhook",
      "serviceUri": "https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX",
      "useCommonAlertSchema": false
    }
  ],
  "azureAppPushReceivers": [
    {
      "name": "Azure App Push",
      "emailAddress": "admin@contoso.com"
    }
  ],
  "azureFunctionReceivers": [
    {
      "name": "Auto-Remediation Function",
      "functionAppResourceId": "/subscriptions/a1b2c3d4/resourceGroups/rg-automation/providers/Microsoft.Web/sites/func-auto-remediate",
      "functionName": "HandleCriticalAlert",
      "httpTriggerUrl": "https://func-auto-remediate.azurewebsites.net/api/HandleCriticalAlert",
      "useCommonAlertSchema": true
    }
  ],
  "logicAppReceivers": [
    {
      "name": "Incident Creator",
      "resourceId": "/subscriptions/a1b2c3d4/resourceGroups/rg-automation/providers/Microsoft.Logic/workflows/la-create-incident",
      "callbackUrl": "https://prod-00.eastus2.logic.azure.com:443/workflows/<id>/triggers/manual/paths/invoke",
      "useCommonAlertSchema": true
    }
  ],
  "automationRunbookReceivers": [
    {
      "name": "VM Restart Runbook",
      "automationAccountId": "/subscriptions/a1b2c3d4/resourceGroups/rg-automation/providers/Microsoft.Automation/automationAccounts/aa-contoso-prod",
      "runbookName": "Restart-UnhealthyVM",
      "webhookResourceId": "/subscriptions/a1b2c3d4/resourceGroups/rg-automation/providers/Microsoft.Automation/automationAccounts/aa-contoso-prod/webhooks/wh-restart-vm",
      "isGlobalRunbook": false,
      "useCommonAlertSchema": true
    }
  ],
  "tags": {
    "environment": "production",
    "team": "platform-engineering"
  }
}

Generated Output

Output will appear here...

How It Helps

Build action group notification configs with email, SMS, voice, webhooks, PagerDuty, Azure Functions, and Automation Runbooks. This tool helps Azure engineers generate valid configurations quickly without consulting documentation, reducing errors and accelerating infrastructure deployment. All processing runs in your browser with no data sent to external servers.

Things Engineers Ask

Will the output of this Monitor Action Group builder pass `az deployment validate` or `terraform validate`?

It produces structurally valid output for the Azure schemas it supports. We still recommend running provider validation locally before applying — schemas evolve and a recently-released property may not yet be reflected. When validation does fail, the error message points at the exact attribute the schema rejected.

Can the output of this Monitor Action Group builder be checked into source control safely?

Yes. The output is plain text containing only configuration — no Azure credentials, subscription IDs (unless you typed them), or secrets are included. Treat it like any other infrastructure-as-code artifact: review in pull requests, gate on validation, apply via your change process.

Practical Applications

1Producing a Monitor Action Group starting point for a new service that follows the Azure reference architecture rather than copy-paste from another team's repo.
2Sketching a Monitor Action Group migration from one Azure subscription to another with subscription and resource-group differences called out.
3Documenting an existing production Monitor Action Group configuration in source control after a portal-side hotfix that bypassed IaC.
4Drafting a Monitor Action Group change for an Azure Bicep or Terraform module before raising the pull request, so reviewers can see intent in plain text.

Related Learning Guides

Cost Management Guide24 min read
Azure Monitor & Application Insights26 min read

Was this tool helpful?

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.