Build action group notification configs with email, SMS, voice, webhooks, PagerDuty, Azure Functions, and Automation Runbooks.
Build action group notification configs with email, SMS, voice, webhooks, PagerDuty, Slack, Azure Functions, Logic Apps, and Automation Runbooks.
Required Fields
actionGroupNameresourceGroupshortNameenabledOutput will appear here...Build an Azure Monitor action group fanning one alert out to multiple heterogeneous receiver types simultaneously (email, SMS, voice, webhook, Azure Function, Logic App, Automation Runbook), each configured independently with its own useCommonAlertSchema setting, since the common alert schema and each service's legacy alert payload format have genuinely different JSON shapes, a webhook or Function expecting one format that actually receives the other fails to parse the payload correctly, a subtle integration bug that only shows up once a real alert fires. The automationRunbookReceivers entry pointing at a webhook (webhookResourceId) plus the runbook name means the actual auto-remediation logic lives in the runbook itself, the action group's job is only to reliably trigger it with the alert context, not to contain any remediation logic.
Each receiver gets whichever format its own useCommonAlertSchema setting specifies, they're independent per-receiver settings, not a single action-group-wide toggle. A webhook receiver expecting the common schema but with useCommonAlertSchema left false receives the legacy format instead, and if the webhook's parsing code only handles the common schema, it fails to correctly extract alert details, this is a common, easy-to-miss integration bug worth checking explicitly per receiver.
No, the action group's automationRunbookReceivers entry just triggers the named runbook (via its webhook) with the alert's context when the alert fires, all the actual remediation logic (what 'restart the VM' actually does, any safety checks) lives in the Automation Runbook itself, the action group is purely the trigger mechanism, not where remediation behavior is defined or reviewed.
Yes, this is the standard and recommended pattern, an action group is a reusable notification/remediation target, and many different alert rules (CPU alerts, availability alerts, custom log alerts) can all reference the same action group, updating the action group's receivers once then applies to every alert rule using it, rather than needing to update notification settings on each alert rule individually.
The builder validates that actionGroupName, resourceGroup, shortName, and enabled all resolve before accepting the JSON as a valid combined action group definition spanning every configured receiver type; it can't verify webhook URLs are reachable, that referenced Function/Logic App/Automation resource IDs exist, or that phone numbers and email addresses are valid and monitored, those are only confirmed when a real alert actually fires and attempts delivery.
Verify useCommonAlertSchema is set correctly per receiver based on what that specific integration's parsing code actually expects, don't assume one setting applies uniformly across every receiver in the action group, this is a genuinely common source of a webhook or Function silently failing to parse alert payloads correctly.
Keep shortName genuinely short and recognizable, it's used in space-constrained channels like SMS where a long name gets truncated to something unrecognizable.
Treat an automationRunbookReceiver as just the trigger wiring, review and test the actual runbook's remediation logic and safety checks separately, the action group configuration itself gives no visibility into what the runbook actually does when triggered.
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.