LO
DeploymentCognitive automation2023-11-13
Microsoft says an LLM-based incident tool's data-collection part has been used by over 30 of its teams for four years, and its root-cause prediction by one incident team
Backend developeroccupation page →
Event date / reported
2023-11-13
Evidence stage
DeploymentAn employer has put it into production. Can move the baseline — weighted by scale and how similar the setting is.
Tasks this bears on
Being the one the pager wakes
On-call: deciding under time pressure what to roll back, what to degrade, and what to tell people while it is still broken.
Still human-led✓ Evidence-backed
Where this applies
A peer-reviewed paper, mostly by Microsoft authors, on a tool for on-call engineers handling cloud incidents. Its diagnostic information collection component has been deployed across over 30 teams within Microsoft for over four years; a root-cause prediction component using a language model, after a successful preliminary phase, has been actively deployed by one incident management team for several months. It helps with diagnosis; it does not decide what to roll back or accept, and Microsoft sells the models involved.
What this means
Diagnosis during an incident is increasingly assisted: at one large cloud provider, collecting what the on-call engineer needs is long automated and root-cause suggestions are in use. The decision about what to sacrifice to restore service is not what the tool does.
What it does not yet show
One company's tooling, reported by its own researchers; it does not show whether on-call load is rising or falling.
What you can check
Open arXiv:2305.15778 (RCACopilot) and find "has been deployed across 30 teams within Microsoft for over four years".
Does it change the assessment?
No. The impact index is never moved by a single event. What this record did: the 1 linked task judgement above now rest on evidence instead of inference.
Source
Chen et al. (Microsoft and others) — "Automatic Root Cause Analysis via Large Language Models for Cloud Incidents" (RCACopilot), arXiv:2305.15778v4 (13 November 2023; EuroSys 2024) · verified 2026-09-27 · Claude (VOLO agent) · interpreted 2026-09-27 · Claude (VOLO agent)
Primary source — published by the party that did this, or the authority of record. No co-signature needed.