Azure Action Groups

Name: Azure Action Groups API
Brand: Azure Action Groups
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkingoauth27 EndpointsREST

For Agents

Create, list, and update Azure Monitor action groups so alerts can route to email, SMS, webhooks, Logic Apps, or Azure Functions. Confirms receiver subscriptions via the EnableReceiver operation.

Connect the Azure Action Groups to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure Action Groups, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Azure Action Groups API.

Create or update an action group with email, SMS, webhook, Logic App, Azure Function, or ITSM receivers

List every action group under a subscription or scope to a single resource group

Patch tags and receiver lists on an existing action group without recreating it

Delete an obsolete action group when the alert routing it served is retired

GET STARTED

Start building with Azure Action Groups API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Azure Action Groups, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Azure Action Groups, keeping it validated and agent-ready. Azure Action Groups lets you define a reusable set of notification and automation receivers (email, SMS, voice call, webhook, Azure Function, Logic App, ITSM, Automation Runbook) that Azure Monitor alerts trigger when conditions fire. The API exposes seven operations across the microsoft.insights/actionGroups resource type, covering create, read, update, delete, list by subscription, list by resource group, and a subscribe-receiver flow for confirming opt-in receivers. It is part of the broader Azure Monitor management surface and is intended for programmatic configuration of alert routing.

Use Cases

Patterns agents use Azure Action Groups API for, with concrete tasks.

★ Production On-Call Routing

Stand up a single Azure Monitor action group that routes critical production alerts to email, SMS, and a PagerDuty webhook so an on-call rotation always receives them. Updating the action group propagates instantly to every alert rule that references it, so alert fan-out is changed in one place rather than per rule.

Create an action group named prod-oncall in resource group monitoring with one email receiver, one SMS receiver, and one webhook pointing at the PagerDuty endpoint, and verify the action group GET returns all three receivers.

Audit and Cleanup of Alert Routing

List every action group in a subscription, identify ones with no attached alert rules or with disabled receivers, and delete or patch them. Useful for compliance reviews where stale notification paths are a finding.

List action groups across the subscription, filter for groups with the enabled flag set to false, and delete each one using the DELETE operation on the actionGroups resource.

Webhook Integration with External Incident Tooling

Attach webhook receivers on an action group so Azure Monitor alerts post to Opsgenie, PagerDuty, ServiceNow, or a custom ingestion endpoint. The action group is the single hand-off point between Azure Monitor and the external incident system.

Patch the action group named platform-incidents to append a new ITSM receiver pointing at the ServiceNow connector and confirm the patch returned 200.

Receiver Opt-In Confirmation

When a new SMS or email receiver is added, Azure sends a confirmation message that must be acknowledged. The EnableReceiver subscribe endpoint resends that confirmation so an agent can complete onboarding without manual intervention from the receiver.

Call the EnableReceiver subscribe endpoint for action group prod-oncall with the receiver name on-call-sms to resend the SMS confirmation message.

Agent-Driven Incident Response Setup

Through Jentic, an AI agent can search for the action group operation, load its input schema, and create or update routing during an incident response runbook without browsing Azure documentation. The agent receives scoped Azure AD credentials from Jentic so the raw service principal secret never enters the agent context.

Use Jentic to search for create azure action group, load the ActionGroups_CreateOrUpdate schema, and execute it with a payload that adds a webhook receiver to the existing prod-oncall group.

Key Endpoints

7 endpoints — jentic publishes the only available openapi specification for azure action groups, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/microsoft.insights/actionGroups

List action groups across a subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/microsoft.insights/actionGroups/{actionGroupName}

Get a single action group by name

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/microsoft.insights/actionGroups/{actionGroupName}

Create or update an action group with its receivers

PATCH

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/microsoft.insights/actionGroups/{actionGroupName}

Patch tags or receiver lists on an existing action group

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/microsoft.insights/actionGroups/{actionGroupName}

Delete an action group

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/microsoft.insights/actionGroups/{actionGroupName}/subscribe

Resend a receiver opt-in confirmation

GET

/subscriptions/{subscriptionId}/providers/microsoft.insights/actionGroups

List action groups across a subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/microsoft.insights/actionGroups/{actionGroupName}

Get a single action group by name

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/microsoft.insights/actionGroups/{actionGroupName}

Create or update an action group with its receivers

PATCH

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/microsoft.insights/actionGroups/{actionGroupName}

Patch tags or receiver lists on an existing action group

DELETE

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/microsoft.insights/actionGroups/{actionGroupName}

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Azure AD service principal credentials (client ID, tenant ID, client secret) are stored encrypted in the Jentic vault. Agents receive a scoped bearer token for management.azure.com — the raw client secret never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g., create azure action group) and Jentic returns the matching ActionGroups_CreateOrUpdate operation with its full input schema, so the agent calls the right endpoint without browsing Azure docs.

Time to first call

Direct integration: 1-2 days for ARM auth, retry logic, and ARM polling on long-running operations. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure Activity Log Alerts

Define alert rules over the Azure Activity Log that route through action groups

Use Activity Log Alerts to fire on subscription-level events (resource created, role assignment changed) and reference an Action Group as the notification target.

Complementary

Azure Alerts Management Service Resource Provider

Manage Smart Detector alert rules that consume action groups

Pair with Action Groups when you need anomaly detection on Application Insights data and want the resulting alert to fire to the same receivers.

Complementary

Azure Monitor Management Client

Broader Azure Monitor surface — metric alerts, autoscale, diagnostic settings

Use when the agent needs to create the metric or log alert that will fan out through an action group, not just configure the receivers.

Alternative

Microsoft Insights

Older consolidated insights API that includes action group operations alongside metrics and alerts

Choose this if you need action group management plus metric definitions and diagnostic settings in a single client; otherwise prefer the dedicated action groups spec.

FAQs

Specific to using Azure Action Groups API through Jentic.

Why is there no official OpenAPI spec for Azure Action Groups?

Microsoft Azure does not publish a single consolidated OpenAPI specification for Azure Action Groups. Jentic generates and maintains this spec so that AI agents and developers can call Azure Action Groups via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Azure Action Groups API use?

The API uses Azure Active Directory OAuth 2.0 with the implicit flow defined in the spec under the azure_auth scheme, scoped to user_impersonation against https://management.azure.com. Jentic stores the service principal client secret in its encrypted vault and gives the agent a scoped token, so the raw secret never reaches the agent context.

Can I add a webhook receiver to an action group via this API?

Yes. Send a PUT or PATCH to /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/microsoft.insights/actionGroups/{actionGroupName} with a webhookReceivers array element containing the name and serviceUri. The same call accepts emailReceivers, smsReceivers, azureFunctionReceivers, logicAppReceivers, automationRunbookReceivers, and itsmReceivers.

What are the rate limits for the Azure Action Groups API?

Azure Resource Manager applies the standard ARM throttling limits — roughly 12,000 read and 1,200 write operations per hour per subscription per region. Action Groups inherits those limits since it is an ARM resource provider under microsoft.insights. Specific per-second ceilings are not exposed in the spec.

How do I create an action group with a webhook through Jentic?

Run pip install jentic, search Jentic for create azure action group, load the ActionGroups_CreateOrUpdate schema, then execute with a request body that includes groupShortName and a webhookReceivers entry pointing at your incident endpoint. Jentic handles the Azure AD token exchange so you do not embed the service principal secret in agent code.

Is the Azure Action Groups API free?

Calling the API itself is free, but each notification delivered through an action group is billed per Azure Monitor pricing — SMS, voice call, ITSM, and webhook deliveries each have their own per-message rates. Email notifications and Azure Function invocations have no per-message charge from Action Groups.

Can I use the EnableReceiver endpoint to confirm an SMS receiver?

Yes. POST to /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/microsoft.insights/actionGroups/{actionGroupName}/subscribe with the receiver name in the request body. Azure resends the confirmation SMS or email to that receiver so the opt-in can be completed.