Azure DevOps Health API

Varies by plan (check documentation)

Overview

The Azure Resource Health API lets you query the current and historical health status of individual Azure resources, such as virtual machines, SQL databases, and App Services. It surfaces incident impact details and recommended actions when an Azure outage or degradation affects your subscriptions. Developers use it to build custom dashboards and alerting systems that reflect real Azure platform health rather than relying solely on third-party monitors.

💡

Beginner Tip

This API requires an Azure Active Directory (AAD) Bearer token, not a simple API key. Use the Azure CLI command `az account get-access-token --resource https://management.azure.com/` to quickly generate a token for testing.

Available Data

case counts and statistics
vaccination data
geographic breakdown
historical trend data

Example Response

JSON Response
{
  "status": "success",
  "data": {
    "result": "Data from Azure DevOps Health",
    "description": "Resource health helps you diagnose and get support when an Azure issue impacts your resources",
    "timestamp": "2025-01-15T10:00:00Z"
  }
}

Field Reference

id Full Azure Resource Manager path for this health record.
properties.availabilityState Current health status: "Available", "Unavailable", or "Unknown".
properties.summary Human-readable description of the current health event or degradation.
properties.reasonType Root cause category — "Unplanned", "Planned", or "UserInitiated".
properties.occuredTime When the health event started.
location Azure region where the affected resource is deployed.

Implementation Example

const url = "https://docs.microsoft.com/en-us/rest/api/resourcehealth";
// Replace headers or query params with the values required by this API.
const response = await fetch(url, {
  headers: {
  "X-API-Key": "YOUR_API_KEY"
  }
});
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

401 Unauthorized The Bearer token is expired or was generated for the wrong resource scope.
Regenerate your token with `az account get-access-token --resource https://management.azure.com/` and ensure your Azure account has Reader access on the subscription.
403 Forbidden The service principal or user does not have the required RBAC role on the resource.
Assign at minimum the "Reader" role on the target subscription or resource group in Azure IAM.
404 Not Found The subscription ID, resource group name, or resource name in the URL path is incorrect.
Verify IDs with `az account show` and `az resource list` and double-check the URL path segments match exactly.

Matrix Score Breakdown

🌐 Reachability 30/30
⚡ Speed 10/20
🔒 Security 5/15
🛠 Developer XP 9/20
✓ Reliability 10/15

Partially tested on Apr 5, 2026

Technical Specifications

Auth API Key
HTTPS NO
CORS NO
Difficulty Intermediate
Verified: 2026-04-07

Similar APIs

View All →