Azure DevOps Health vs Buddy

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.

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.