Microsoft Azure Microsoft.ResourceHealth
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilityoauth210 EndpointsREST
For Agents
Query the Azure platform health of any resource and surface emerging service issues. Covers 10 endpoints for availability statuses on individual resources, child resources, subscriptions, and resource groups, plus tenant-wide emerging issue feeds.
Use for: Get the current availability status of a virtual machine, List all unhealthy resources in a subscription, Check whether an Azure region is currently experiencing an emerging issue, Retrieve the availability history of an App Service over the last week
Not supported: Does not handle metric collection, log queries, or remediation actions — use for reading Azure platform availability state and emerging issues only.
Jentic publishes the only available OpenAPI specification for Microsoft.ResourceHealth, keeping it validated and agent-ready. The Resource Health API exposes the current and historical availability state of every Azure resource in a subscription, alongside platform-emerging issues that affect entire services or regions. Operators and AI agents can query availability statuses for individual resource URIs, list child availability statuses for parent resources like virtual machine scale sets, and surface emerging issues directly into incident response workflows. Status values include Available, Unavailable, Degraded, and Unknown, with reason codes that explain platform-initiated outages versus user-initiated downtime.
Install Jentic One Beta
Connect the Microsoft.ResourceHealth to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Microsoft.ResourceHealth, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 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 Microsoft.ResourceHealth API.
Retrieve the current availability status of any Azure resource by resource URI
List historical availability status transitions for a resource over time
Surface child availability statuses for parent resources such as VM scale sets
List availability statuses scoped to a subscription or resource group
Query Azure-wide emerging issues affecting one or more services or regions
Distinguish platform-initiated downtime from customer-initiated downtime via reason codes
Expose Resource Health operations metadata for self-describing tooling
Use Cases
Patterns agents use Microsoft.ResourceHealth API for, with concrete tasks.
★ Automated incident triage for Azure workloads
When an alert fires on a production workload, an SRE agent calls the Resource Health API to determine whether the cause is platform-initiated or customer-initiated. The current availability status returns a reason code such as PlatformInitiated or Unplanned, allowing the on-call workflow to route platform issues to Azure support and customer issues to the application team. This typically cuts mean time to triage from 15 minutes to under one minute.
Get the current availability status for the virtual machine at /subscriptions/abc/resourceGroups/prod/providers/Microsoft.Compute/virtualMachines/web01 and return the reason code if the status is not Available.
Subscription-wide health dashboards
Platform teams build live health dashboards by polling the availability statuses endpoint scoped to a subscription. The API returns the latest known status for every resource in the subscription, which a dashboard groups by resource type, region, and reason code. Combined with emerging issues, this produces a single pane of glass that shows both customer impact and Microsoft-acknowledged service incidents.
List availability statuses for subscription abc and return the count of resources in each status bucket grouped by reason code.
Emerging issue surfacing for status pages
Public-facing status pages and internal communications channels can pull from /providers/Microsoft.ResourceHealth/emergingIssues to surface acknowledged Azure platform issues before customers notice impact. The endpoint returns issue titles, impacted services, regions, and recommended actions, which a content agent can summarize into a customer-facing post within seconds of Microsoft publishing the issue.
List all emerging issues, filter to those impacting the East US region, and produce a one-paragraph summary for each issue.
Agent-driven Azure platform health checks
AI agents can use Jentic to discover Resource Health operations by intent, load the structured input schema, and execute calls against management.azure.com without browsing the Azure REST docs. Agents can answer is my Azure environment healthy with a single intent search, fetch availability statuses across the subscription, and summarize unhealthy resources in plain English for an on-call engineer.
Search Jentic for list azure availability statuses, load the input schema, and execute it for subscriptionId abc, returning a markdown table of unhealthy resources.
Key Endpoints
10 endpoints — jentic publishes the only available openapi specification for microsoft.
METHOD
PATH
DESCRIPTION
GET
/{resourceUri}/providers/Microsoft.ResourceHealth/availabilityStatuses/current
Get the current availability status for a resource
GET
/{resourceUri}/providers/Microsoft.ResourceHealth/availabilityStatuses
List historical availability statuses for a resource
GET
/{resourceUri}/providers/Microsoft.ResourceHealth/childAvailabilityStatuses
List child availability statuses for a parent resource
GET
/subscriptions/{subscriptionId}/providers/Microsoft.ResourceHealth/availabilityStatuses
List availability statuses across a subscription
GET
/providers/Microsoft.ResourceHealth/emergingIssues
List Azure-wide emerging platform issues
GET
/{resourceUri}/providers/Microsoft.ResourceHealth/availabilityStatuses/current
Get the current availability status for a resource
GET
/{resourceUri}/providers/Microsoft.ResourceHealth/availabilityStatuses
List historical availability statuses for a resource
GET
/{resourceUri}/providers/Microsoft.ResourceHealth/childAvailabilityStatuses
List child availability statuses for a parent resource
GET
/subscriptions/{subscriptionId}/providers/Microsoft.ResourceHealth/availabilityStatuses
List availability statuses across a subscription
GET
/providers/Microsoft.ResourceHealth/emergingIssues
List Azure-wide emerging platform issues
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD OAuth credentials and service principals are stored encrypted in the Jentic vault. Agents receive scoped bearer tokens for management.azure.com at execution time; client secrets and certificates never enter the agent context.
Intent-based discovery
Agents search by intent (for example check azure resource health or list emerging azure issues) and Jentic returns the matching ARM operation with its full input schema, so the agent can call the correct path without browsing Microsoft Learn docs.
Time to first call
Direct integration with the Resource Health REST API: 1-2 days for AAD auth, ARM throttling handling, and resourceUri encoding. Through Jentic: under 1 hour to search, load, and execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Microsoft.ResourceHealth API through Jentic.
Why is there no official OpenAPI spec for Microsoft.ResourceHealth?
Microsoft Azure does not publish an OpenAPI specification for the Microsoft.ResourceHealth Resource Provider. Jentic generates and maintains this spec from the Azure Resource Manager contracts so that AI agents and developers can call Microsoft.ResourceHealth 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 Microsoft Resource Health API use?
The API uses Azure Active Directory OAuth 2.0 with the user_impersonation scope against https://login.microsoftonline.com/common/oauth2/authorize. Jentic stores the AAD client secret or service principal credentials encrypted in its vault and issues scoped bearer tokens to agents at execution time without revealing the underlying credential.
Can I get the availability status of a single resource through the Resource Health API?
Yes. Call GET /{resourceUri}/providers/Microsoft.ResourceHealth/availabilityStatuses/current with the URI-encoded resource path as resourceUri. The response includes the status (Available, Unavailable, Degraded, Unknown), a reason type (PlatformInitiated, UserInitiated, Unplanned), and a reasonChronicity that distinguishes transient from persistent issues.
What are the rate limits for the Microsoft Resource Health API?
Resource Health follows the standard Azure Resource Manager throttling limits, which apply per subscription and per region. Read operations are limited to 1200 requests per hour per subscription. The emerging issues endpoint is global and shares the tenant read budget, so dashboards should cache responses for at least 60 seconds rather than poll continuously.
How do I list emerging Azure platform issues through Jentic?
Search Jentic for list azure emerging issues, load the schema for GET /providers/Microsoft.ResourceHealth/emergingIssues, and execute the call. Jentic handles AAD token exchange and returns the active issue list, which an agent can then filter by impacted service or region.
Does the Resource Health API trigger remediation actions?
No. Resource Health is read-only and reports state rather than acting on it. Pair it with the Azure Automation, Logic Apps, or compute resource APIs when an agent needs to restart, redeploy, or failover an unhealthy resource based on the status returned here.
GET STARTED