Live / Moveworks / Incident
Moveworks: Moveworks Assistant Impacted by Ongoing Microsoft Outage
Moveworks · moveworks.comMinor incidentResolved2026-11-13 23:36 UTC
Public — what happened
Summary
Moveworks said a Microsoft outage beginning 2026-11-12 at 20:51 UTC hurt some users of its AI Assistant, mainly in Microsoft Teams, where replies were slow and notifications and Employee Communications campaigns were delayed or not delivered. The company said the problem was on Microsoft's side, that other chat platforms kept working, and that a sync of identity data from Exchange Online sources was also interrupted before resuming. Moveworks said it increased its notification capacity, and by 2026-11-13 19:29 UTC it reported its services had recovered, with only campaign progress counts still catching up. The incident was marked resolved at 23:36 on 2026-11-13, and Moveworks relayed Microsoft's statement that the outage came from a technical issue during a network capacity upgrade and was not a cyber attack.
Affected
Microsoft Teams, Employee Communications
Timeline
- Started — 2026-11-12 20:51 UTC
- Identified — 2026-11-12 20:51 UTC (3 updates)
- Monitoring — 2026-11-13 14:15 UTC (3 updates)
- Resolved — 2026-11-13 23:36 UTC · 26h 45m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Moveworks against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Moveworks: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Moveworks report →
More from Moveworks
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.