Cases › operational mistake › LR-2026-0347
Microsoft Copilot outage affects users in Europe
Preliminary Why: 1 report: BleepingComputer · subject to change · 1 independent report
Status: no action reported
No source states: loss or records, agent tool, could do, deployer, industry.
Microsoft's AI-powered Copilot digital assistant became inaccessible or degraded for some users in the United Kingdom and Europe, reaching them through copilot.cloud.microsoft, m365.cloud.microsoft, the Edge Copilot button and Microsoft Copilot for Microsoft 365 apps. Affected users saw an error reply. Microsoft attributed the outage to a capacity scaling issue and reported an unexpected increase in traffic in its monitoring telemetry. It manually scaled capacity while also identifying a separate load-balancing issue and changing its load-balancing rules. Microsoft later reported that it had resolved the incident by reverting a recent policy change affecting service traffic balancing, and that telemetry confirmed the impact was fully resolved. No AI agent was involved; the record concerns service availability rather than model behaviour.
What happened
No source tells the story step by step yet.
What was done
No source states an action or fix.
Risks
Primary63 incidents
Rising: 5 vs 2.2 a week
Sorted by rule from the case's fields; not yet read from the sources.
Controls
Not yet read for controls. Controls that mitigate the primary risk:
HarnessTool allow-list · Fail-closed defaults · Stop control
ApplicationHuman approval for high-impact actions · Change review and separation of duties · Least-privilege access for the agent · Production kept apart from test · Activity logs · Adversarial testing before deployment
Infrastructure / targetSimilar incidents
Evidence
No source states: a step-by-step account, when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, the cause, what set it off, what was done.
Show the full account: 1 items from the primary sources
What happened, in order
Not dated in the sources:
- Service monitoring telemetry indicated an unexpected increase in traffic had caused impact.
Show every field, with its source and grade
The AI system
What happened
Impact
Notes on gaps
Risks and controls are empty because no listed risk or control fits a capacity and load-balancing outage. The separate Defender incident (DZ1193516) and the earlier Defender XDR outage are different incidents and were excluded.
LR-2026-0347 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON