Microsoft Azure Azure Alerts Management Service Resource Provider
Browse all Azure APIs46
AI ReadinessFoundational (D)46/100
Community OpenAPI document · agent-readyDeveloper ToolsMonitoring Observabilityoauth217 EndpointsREST
Know of an official OpenAPI document? Contribute it →
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.
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. It exposes endpoints to list alerts with filtering by severity, monitor service, and time range, change alert state to acknowledged or closed, retrieve alert history, and manage action rules that suppress or route alerts. It also returns aggregated alert summaries and metadata that drive dashboards.
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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-alerts-management-service-resource-provider" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-alerts-management-service-resource-provider" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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
Aggregate alert counts by severity, alert state, or monitor condition through the alertsSummary endpoint
Create, update, and delete action rules that suppress or route alerts based on scope and conditions
Inspect smart groups that cluster related fired alerts to reduce notification noise
Read alert metadata such as monitor service catalogues for client-side filtering
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
GET
/subscriptions/{subscriptionId}/providers/Microsoft.AlertsManagement/actionRules
List action rules in a subscription
GET
/providers/Microsoft.AlertsManagement/alertsMetaData
Reference metadata about supported alert sources
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
Azure Alerts Management Service Resource Provider
- Foundational (D)46/100
80
Foundational Compliance60
Developer Experience & Jentic Compatibility24
AI-Readiness & Agent Experience94
Agent Usability35
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
80
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
96%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
25%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
60
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
47%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
93%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
24
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
67%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
29%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
35
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
35%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Azure Alerts Management Service Resource Provider by hand means registering an Azure AD app, exchanging OAuth 2.0 tokens for management.azure.com, and building the Azure Resource Manager plumbing that server-side filters paginated alert queries and retries changestate calls on throttling. Through Jentic you install once, import the Azure Alerts Management Service Resource Provider from the API Directory, store the Azure AD credential once, and your agent calls it.
Permission scoping
This API puts the subscription and alert id in the URL path (for example /subscriptions/{subscriptionId}/providers/Microsoft.AlertsManagement/alerts/{alertId}/changestate), so a rule can pin your agent to a specific subscription's alerts. You choose the operations it may call, so ones like changing alert state to Closed or deleting an action rule are not included unless you add them.
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.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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.
GET STARTED