Microsoft Azure Azure Alerts Management Service Resource Provider

Name: Azure Alerts Management Service Resource Provider API
Brand: Azure Alerts Management Service Resource Provider
Availability: InStock

Browse all Azure APIs

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilityoauth217 Endpoints

Install Jentic One Beta

Connect the Azure Alerts Management Service Resource Provider to your agent

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

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: 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

Step 2: 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 Alerts Management Service Resource Provider API.

Query fired alerts across a subscription with filters on severity, monitorService, alertState, and time window

Change an alert's state to Acknowledged or Closed via the changestate endpoint

Retrieve the full state-change history for a specific alertId

GET STARTED

Start building with Azure Alerts Management Service Resource Provider API

Explore with Jentic

View OpenAPI Document

For Agents

Query, change state, and summarise fired alert instances across Azure Monitor, and manage action rules that filter or suppress alerts. Supports 17 endpoints over alerts, action rules, smart groups, and metadata.

Use for: I need to list all critical alerts fired in the last 24 hours, Acknowledge an alert by alertId so it stops paging, Get the state-change history of a fired alert, Summarise active alerts by severity for a dashboard

Not supported: Does not create alert rules, configure metric thresholds, or send notifications directly - use for fired alert state management, suppression rules, and smart groups only.

Use Cases

Patterns agents use Azure Alerts Management Service Resource Provider API for, with concrete tasks.

★ Operations Dashboard for Live Alerts

Power an internal status board that shows all currently firing Azure alerts grouped by severity and service. The Alerts Management API returns paginated alert instances filterable by alertState, severity, and timeRange, and the alertsSummary endpoint produces aggregated counts in a single call. Most teams ship a working dashboard against this API in under a day.

Call alertsSummary for the current subscription with groupby=severity,alertState and timeRange=1d, then list any Sev0 or Sev1 alerts via Alerts_GetAll.

Maintenance Window Suppression

Suppress alerts on a target resource during a planned maintenance window so the on-call rota is not paged for expected outages. The API's action rules support scoped suppressions with start and end times, applied to specific resource IDs or alert conditions. The rule is removed automatically when the window ends, leaving normal alerting in place.

Create an action rule scoped to /subscriptions/{subscriptionId}/resourceGroups/db-prod that suppresses all alerts between 2026-06-12T00:00 and 2026-06-12T02:00.

Automated Alert Triage

Acknowledge or close alerts automatically based on remediation outcomes, replacing manual portal clicks. The changestate endpoint accepts a new state on a specific alertId, and Alerts_GetHistory returns the audit trail of every transition. This lets remediation pipelines record their actions back into Azure Monitor so the alert lifecycle stays consistent.

Call POST /subscriptions/{subscriptionId}/providers/Microsoft.AlertsManagement/alerts/{alertId}/changestate with newState=Closed for every alert resolved by the runbook.

Agent-Driven Alert Correlation

A Jentic agent inspects smart groups and alert summaries to triage incidents at scale. It pulls active alerts via Alerts_GetAll, reads the smart group that clusters related signals, and decides whether to acknowledge, escalate, or open a ticket. The agent operates over the same 17 endpoints exposed in the spec, with no portal access required.

List all New alerts in subscription 1111-2222, group them by smartGroupId, and acknowledge every alert tagged with monitorService=Platform that belongs to a smart group with three or more members.

Key Endpoints

17 endpoints — the azure alerts management api provides a unified view of fired alert instances across azure monitor, including activity log, metric, log search, and service health alerts.

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/Microsoft.AlertsManagement/alerts

List fired alerts with filters

GET

/subscriptions/{subscriptionId}/providers/Microsoft.AlertsManagement/alerts/{alertId}

Get a single alert by ID

POST

/subscriptions/{subscriptionId}/providers/Microsoft.AlertsManagement/alerts/{alertId}/changestate

Change alert state to Acknowledged or Closed

GET

/subscriptions/{subscriptionId}/providers/Microsoft.AlertsManagement/alerts/{alertId}/history

Get state-change history for an alert

GET

/subscriptions/{subscriptionId}/providers/Microsoft.AlertsManagement/alertsSummary

Aggregated alert summary

GET

/subscriptions/{subscriptionId}/providers/Microsoft.AlertsManagement/actionRules

List action rules in a subscription

GET

/providers/Microsoft.AlertsManagement/alertsMetaData

Reference metadata about supported alert sources

GET

/subscriptions/{subscriptionId}/providers/Microsoft.AlertsManagement/alerts

List fired alerts with filters

GET

/subscriptions/{subscriptionId}/providers/Microsoft.AlertsManagement/alerts/{alertId}

Get a single alert by ID

POST

/subscriptions/{subscriptionId}/providers/Microsoft.AlertsManagement/alerts/{alertId}/changestate

Change alert state to Acknowledged or Closed

GET

/subscriptions/{subscriptionId}/providers/Microsoft.AlertsManagement/alerts/{alertId}/history

Get state-change history for an alert

GET

/subscriptions/{subscriptionId}/providers/Microsoft.AlertsManagement/alertsSummary

Aggregated alert summary

Why Jentic?

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

Credential isolation

Your Azure AD credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list active Azure alerts and acknowledge them' or 'summarise alerts by severity', and Jentic returns the matching Microsoft.AlertsManagement operation with its full schema so the agent can populate filters and state transitions without parsing ARM docs.

Time to first call

FAQs

Specific to using Azure Alerts Management Service Resource Provider API through Jentic.

What authentication does the Azure Alerts Management API use?

Azure Active Directory OAuth 2.0 via the azure_auth scheme (user_impersonation scope) on https://management.azure.com/. With Jentic, the AAD client credentials live in your Jentic One instance and the agent calls the API with a short-lived bearer token, so secrets stay out of agent context.

Can I acknowledge an alert with this API?

Yes. POST /subscriptions/{subscriptionId}/providers/Microsoft.AlertsManagement/alerts/{alertId}/changestate with newState=Acknowledged. The same endpoint accepts Closed or New, and Alerts_GetHistory will include the transition you just made.

What are the rate limits for the Azure Alerts Management API?

Subscription-level Azure Resource Manager throttling applies, typically 12,000 read and 1,200 write operations per hour per subscription, shared with other ARM calls. Heavy alert listing should use server-side filters rather than client-side pagination loops.

How do I create an alert suppression rule through Jentic?

Search Jentic for "create azure alert suppression rule", load the schema for the action rules CreateOrUpdate operation, then execute with the suppressionConfig schedule and the resource scope. Get an API key through Jentic One, the self-hosted execution layer.

Does this API let me create alert rules?

No. This API manages fired alert instances, action rules, and smart groups. To create the rules that produce alerts, use the metric alerts, log search alerts, or activity log alerts resource providers separately.

What are smart groups?

Smart groups are clusters of related alerts that Azure Monitor's correlation engine groups together to reduce noise. The smart groups endpoints in this API let you list, get, and change the state of a smart group rather than each individual alert in it.

Can I limit what my agent is allowed to do with the Azure Alerts Management API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. This API puts the subscription and alert id in the URL path, such as /subscriptions/{subscriptionId}/providers/Microsoft.AlertsManagement/alerts/{alertId}/changestate, so you can pin the agent to a specific subscription's alerts. You choose the operations it may call, so state-changing actions like closing an alert or deleting an action rule are excluded unless you add them, letting you keep the agent to read-only listing and summaries.