Microsoft 365 and Exchange Online widespread service disruption
A connection-establishment failure made Exchange Online mailboxes inaccessible or intermittently available for many users, with delayed mail delivery and secondary effects in Microsoft 365 products that depend on Exchange.
Microsoft’s public service-health mirror records the Exchange Online incident from 16:17 UTC on Nov 12 to 16:10 UTC on Nov 13. Related Microsoft 365 service impacts were tracked under MO1550821.
Incident summary
A connection-establishment failure made Exchange Online mailboxes inaccessible or intermittently available for many users, with delayed mail delivery and secondary effects in Microsoft 365 products that depend on Exchange.
The main impact affected Exchange Online access through Outlook on the web, MAPI, ActiveSync, and REST. Related Microsoft 365 features were affected to varying degrees. Service recovery was gradual, and queued email continued processing after mailbox access improved.
What the provider reported
Microsoft said traffic shifts during standard network maintenance and upgrades exposed a latent bug in systems establishing Exchange Online connections. Requests accumulated in queues until affected servers exhausted processing capacity. Microsoft described the event as a technical issue and said it found no evidence of malicious activity.
Editorial note: This is a concise summary of the provider’s public explanation, not an independent technical investigation.
Services and systems
Reported scope: Multiple regions · global Microsoft 365 tenant impact
Latest source updates
Showing up to the 3 latest updates available in the source record. UTC is fixed; local time is converted in this browser (your local timezone).
-
Incident marked ended
Microsoft’s incident record lists 16:10 UTC on Friday, Nov 13 as the end of the Exchange Online impact window.
-
Recovery update
Microsoft reported the underlying issue addressed and continued restoring remaining customers and regions while monitoring queued email and service stability.
-
Post-incident report published
Microsoft’s service-health extract recorded publication of the post-incident report.
Latest source record: ·
What did this incident feel like?
React anonymously. Counts are shared across visitors and are not a measure of the number of customers affected.