greatapis

Continuous Integration — entry 001 of 5

Azure DevOps Health

Verified Jul 2026

Despite its name, this is the Azure Resource Health control-plane API (part of Azure Resource Manager), which reports the real-time and historical availability status of individual Azure resources rather than anything DevOps-pipeline-specific. Every call goes through management.azure.com and is authenticated like any other ARM provider — a Microsoft Entra ID (Azure AD) OAuth2 bearer token in the Authorization header, not a plain API key. A live unauthenticated GET against its availabilityStatuses endpoint returned a structured JSON error with access-control-allow-origin: * rather than a raw connection failure, confirming the service and its CORS support are live.

azuremonitoringcloudresource-healthdevops
Visit learn.microsoft.com ↗More Continuous Integration
AuthenticationOAuthRequires an OAuth flow; expect app registration.
HTTPSSupportedTraffic is encrypted in transit.
CORSEnabledCallable directly from browser JavaScript.
PricingFreeNo paid tier — free for the documented use case.
FormatsJSONResponses can be requested as JSON.

GreatAPIs Score

Score57out of 100
Authentication8/25OAuth flow required
Pricing20/20Free to use
Docs0/20No docs or spec available
Formats9/15Single response format
Freshness20/20Verified within 6 months

Embed this badge

Scored 57 on greatapis.com
<a href="https://greatapis.com/api/azure-devops-health/"><img src="https://greatapis.com/badge/azure-devops-health.svg" alt="Scored 57 on greatapis.com"></a>

Auth quickstart

  1. Register an app / run the OAuth flow to obtain a bearer token.
  2. Send it as an Authorization headerAuthorization: Bearer <token>
Stored keyNo key stored

Your key is stored only in this browser (localStorage) and sent directly to the API — never to greatapis.

People comparing Azure DevOps Health also look at…

All 5 →

Azure DevOps Health vs Bitrise

Bitrise's REST API drives its mobile-focused CI/CD platform: triggering builds, reading build and workflow logs, and managing apps, webhooks, and cache across a project's pipelines. A live unauthenticated GET against api.bitrise.io/v0.1/me returned a clean 401 Unauthorized JSON body while still carrying access-control-allow-origin: * on both the request and an OPTIONS preflight, confirming the personal-access-token auth model and resolving its previously unknown CORS support to open. Its own pricing page offers a free Hobby tier for individual developers alongside paid team plans, so this is a freemium product, not a flat-fee one.

Compare →

Azure DevOps Health vs Buddy

Buddy's REST API manages its visual CI/CD pipelines end to end — projects, actions, environments, runs, sandboxes, and Git operations — and is described as covering the same permission model as the web app itself. Its docs state plainly that authentication is performed with OAuth2, sending requests with a Bearer access_token, which this run reconfirmed live: an unauthenticated call to api.buddy.works/user returned a 401 "Wrong authentication data" response while still carrying access-control-allow-origin: * on both the request and its OPTIONS preflight, resolving the previously unknown CORS support to open. Buddy's own pricing page lists a free plan (limited pipeline minutes and one seat) alongside paid Pro and Hyper tiers, making it freemium rather than a flat fee.

Compare →

Azure DevOps Health vs Travis CI

Travis CI's REST API reads and manages builds, repositories, branches, and jobs, and its docs specify a token-based Authorization: token "<token>" header rather than an OAuth redirect flow, reconfirming the stored API Key auth model. A live GET against api.travis-ci.com returned a structured JSON response (not a raw connection error), and the same request sent with an Origin header carried access-control-allow-origin: * on both the GET and its OPTIONS preflight, resolving the previously unknown CORS support to open. Travis CI's own pricing page still lists an "Open Source Only" free tier alongside paid Linux/FreeBSD plans, so it remains freemium rather than fully paid.

Compare →

Azure DevOps Health vs CircleCI

Azure DevOps Health supports CORS, while CircleCI doesn't — pick Azure DevOps Health for direct browser calls.

Compare →