--- title: Meet Brain, the AI that decides when Azure is officially... description: Microsoft has revealed Brain, its internal AIOps system that serves as Azure's centralized cloud health monitor. Built on top of Azure Resource Graph as a... canonical: https://daily.dev/posts/meet-brain-the-ai-that-decides-when-azure-is-officially-down-go1rusyoj twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Meet Brain, the AI that decides when Azure is officially down | daily.dev og:description: Microsoft has revealed Brain, its internal AIOps system that serves as Azure's centralized cloud health monitor. Built on top of Azure Resource Graph as a... og:url: https://daily.dev/posts/meet-brain-the-ai-that-decides-when-azure-is-officially-down-go1rusyoj og:image: https://api.daily.dev/og/posts/Go1rUSYOj.png og:image:alt: Meet Brain, the AI that decides when Azure is officially down og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Meet Brain, the AI that decides when Azure is officially down **[The New Stack](https://daily.dev/sources/newstack)** · 10 min read · 1 upvotes · 0 comments ## Summary Microsoft has revealed Brain, its internal AIOps system that serves as Azure's centralized cloud health monitor. Built on top of Azure Resource Graph as a real-time digital twin, Brain ingests three classes of signals — standardized service level indicators (SLIs), team-registered domain monitors, and third-party indicators — to produce health state, severity, impact scope, and root cause for any Azure service, region, or customer resource. Rather than asking service teams to define their own SLOs (which led to sandbagged thresholds), Brain uses ML models to derive dynamic thresholds from each service's historical behavior. The system automatically declares outages, pauses harmful rollouts, routes incidents to the right teams, and notifies affected customers. Azure CTO Mark Russinovich says auto-notification has reduced customer support tickets by 4–6x and that Brain hits a 15-minute time-to-mitigate window for 80–90% of covered services. On top of Brain, Microsoft is layering agentic systems like Triangle, an LLM-based multi-agent triage system that routes incidents to the right service team without manual handoffs. Coverage currently spans 70–80% of Azure's critical services, with the remainder in progress. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How does Microsoft's Azure decide when a service is officially having an outage? Azure uses an internal AIOps system called Brain, which layers on top of Azure Resource Graph to form a real-time digital twin of Azure's health. It combines standardized service level indicators, service-specific monitors, and third-party signals like support tickets and social media, then uses ML models to derive health thresholds per service, scale unit, and region rather than relying on manually defined SLOs. _Engineers building large-scale observability systems can follow AIOps design patterns like this on daily.dev._ ### What is Microsoft's time-to-mitigate goal for Azure incidents and how well does it meet it? Microsoft's goal is 15 minutes from problem detection to resolution, and Azure hits that window for 80 to 90 percent of services integrated with Brain, often closer to five minutes. Azure CTO Mark Russinovich attributes this partly to removing humans from the initial detection loop, since manual involvement can blow past the 15-minute target. _Teams tracking incident response benchmarks against real-world SRE goals can dig deeper on daily.dev._ ### What is Triangle in the context of Azure incident management? Triangle is a multi-agent system, described in a Microsoft Research paper, that gives each Azure service team an LLM-based agent trained on that team's historical incidents and troubleshooting guides. An orchestrator fans out incoming incidents and lets each agent 'raise its hand' if it believes the issue belongs to its service, reducing the ticket handoffs that previously slowed response times. _Developers exploring multi-agent orchestration for real ops workflows can track examples like this on daily.dev._ ## Similar posts on daily.dev - [The cloud outage that should terrify the CIO](https://daily.dev/posts/the-cloud-outage-that-should-terrify-the-cio-cmtyssior) · InfoWorld · 0 upvotes · 0 comments - [AI is coming to solve your system outages](https://daily.dev/posts/ai-is-coming-to-solve-your-system-outages-ciiwyuvu9) · The Register · 0 upvotes · 0 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#azure](https://daily.dev/tags/azure), [#observability](https://daily.dev/tags/observability), [#aiops](https://daily.dev/tags/aiops) [View this post on daily.dev](https://daily.dev/posts/meet-brain-the-ai-that-decides-when-azure-is-officially-down-go1rusyoj) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Meet Brain, the AI that decides when Azure is officially down","url":"https://daily.dev/posts/meet-brain-the-ai-that-decides-when-azure-is-officially-down-go1rusyoj","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/meet-brain-the-ai-that-decides-when-azure-is-officially-down-go1rusyoj"},"datePublished":"2026-07-12T15:00:16.689Z","dateModified":"2026-09-13T21:41:10.585Z","description":"Microsoft has revealed Brain, its internal AIOps system that serves as Azure's centralized cloud health monitor. Built on top of Azure Resource Graph as a...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/937e91b91136d6ad1d97a6c0b151861a?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/937e91b91136d6ad1d97a6c0b151861a?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"The New Stack","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"The New Stack","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/newstack","url":"https://daily.dev/sources/newstack"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/meet-brain-the-ai-that-decides-when-azure-is-officially-down-go1rusyoj","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,azure,observability,aiops","timeRequired":"PT10M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"The New Stack","item":"https://daily.dev/sources/newstack"},{"@type":"ListItem","position":3,"name":"Meet Brain, the AI that decides when Azure is officially down"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/meet-brain-the-ai-that-decides-when-azure-is-officially-down-go1rusyoj#faq","mainEntity":[{"@type":"Question","name":"How does Microsoft's Azure decide when a service is officially having an outage?","acceptedAnswer":{"@type":"Answer","text":"Azure uses an internal AIOps system called Brain, which layers on top of Azure Resource Graph to form a real-time digital twin of Azure's health. It combines standardized service level indicators, service-specific monitors, and third-party signals like support tickets and social media, then uses ML models to derive health thresholds per service, scale unit, and region rather than relying on manually defined SLOs. Engineers building large-scale observability systems can follow AIOps design patterns like this on daily.dev."}},{"@type":"Question","name":"What is Microsoft's time-to-mitigate goal for Azure incidents and how well does it meet it?","acceptedAnswer":{"@type":"Answer","text":"Microsoft's goal is 15 minutes from problem detection to resolution, and Azure hits that window for 80 to 90 percent of services integrated with Brain, often closer to five minutes. Azure CTO Mark Russinovich attributes this partly to removing humans from the initial detection loop, since manual involvement can blow past the 15-minute target. Teams tracking incident response benchmarks against real-world SRE goals can dig deeper on daily.dev."}},{"@type":"Question","name":"What is Triangle in the context of Azure incident management?","acceptedAnswer":{"@type":"Answer","text":"Triangle is a multi-agent system, described in a Microsoft Research paper, that gives each Azure service team an LLM-based agent trained on that team's historical incidents and troubleshooting guides. An orchestrator fans out incoming incidents and lets each agent 'raise its hand' if it believes the issue belongs to its service, reducing the ticket handoffs that previously slowed response times. Developers exploring multi-agent orchestration for real ops workflows can track examples like this on daily.dev."}}]} ```