Microsoft 365 Outage Ends as Services Return Worldwide

The Microsoft 365 outage that disrupted offices and public services around the world has ended. Microsoft confirmed recovery across its services early on Saturday. The failure had lasted for roughly a day and a half.

The failure began at 16:17 UTC on Thursday 12 November. For many workers, the Microsoft 365 outage began with a simple sign: an inbox that would not open. It then ran into Friday's working day across Asia, Europe and the Americas.

For many organisations, Microsoft 365 is the office itself. Mail, meetings, documents and security tools sit inside one subscription. When it fails, work slows everywhere at once.

How the Microsoft 365 outage unfolded

Microsoft tracked the failure under two incident codes. Exchange Online was logged as EX1550543. The wider Microsoft 365 outage was logged as MO1550821, covering multiple services.

Users found they could not open their Outlook mailboxes. Email that did move was often delayed for hours. Teams meetings, files and calls were disrupted alongside the mail failure.

The affected list was long. It included Teams, Copilot, SharePoint, OneDrive, Defender, Purview, Planner, To Do and Intune. Microsoft said the impact reached every region.

Businesses and government agencies were hit together. CNN reported disruption to government services in US cities including Jacksonville, Austin and Dallas. The same cities later reported gradual recovery as systems came back.

At the peak, about 130,000 users reported Outlook problems on the tracker Downdetector. Such trackers rely on public reports, so the true number affected was far higher. Few large employers were untouched by the failure.

The failure reached beyond Microsoft's own products. Industry trackers noted that the email and calendar connectors used by AI assistants stopped working too. That included connectors used by ChatGPT and Claude.

Microsoft also clarified a separate question. It said there was no indication that the FAA's nationwide ground stop in the United States was related to Microsoft services. The two failures simply happened in the same window.

What caused the Microsoft 365 outage

Microsoft gave a preliminary cause once recovery was under way. It linked the failure to an earlier network capacity upgrade. The problem surfaced following a recent network change, and part of the infrastructure saw elevated load.

The company was firm about what the failure was not. Microsoft said the Microsoft 365 outage was not related to cyber activity. It also said it was not related to AI or to agents.

Early on Saturday, Microsoft said it had no time estimate for full recovery. It then reported sustained service recovery across the affected environments. Its final update, at 04:17 UTC on Saturday, marked the incident as serviceRestored.

Microsoft apologised publicly for the disruption. In a social media post, the company said it was deeply sorry. Executive Vice President Charles Lamanna said Microsoft was reviewing the incident and working to prevent a repeat.

A full post incident report is still to come. Microsoft promised to publish it once its review is complete. That document should explain how a routine change spread so widely.

Why some emails arrived late

Email was delayed rather than destroyed. Messages sat in queues while Exchange Online was down. Microsoft extended the email retry window to 48 hours, so queued mail kept retrying instead of bouncing back to senders.

As recovery spread, those queues began to drain. Some users received batches of older messages at once. That pattern is normal after a long mail failure of this kind. Colleagues in other time zones often saw the same delayed batches arrive hours later.

What to do if the Microsoft 365 outage still affects you

Start with the official status pages. Microsoft publishes service health at status.cloud.microsoft. Business administrators can read the full incident record in the Microsoft 365 admin centre.

If Outlook still fails, restart the app and sign in again. Then check the service health page before changing any settings. Most remaining problems clear as the last queues drain.

If the Microsoft 365 outage still affects your mailbox on Monday, contact your IT team. Administrators can check whether your organisation is fully recovered. They can also confirm that queued mail has finished delivering.

Do not delete and recreate accounts during a backlog. That step can damage mailbox data and make recovery harder. Patience, and the official status page, are the safer tools here.

Microsoft 365 outage: common questions

What caused the Microsoft 365 outage?

Microsoft linked it to an earlier network capacity upgrade and a recent network change. Part of the infrastructure saw elevated load during the failure. The company promised a full report after its review is complete.

Is the Microsoft 365 outage over now?

Yes. Microsoft marked the incident serviceRestored at 04:17 UTC on Saturday 14 November. Recovery was confirmed across the affected environments. Some queued email took longer to finish delivering to inboxes.

Was the Microsoft 365 outage a cyberattack?

No, according to Microsoft. The company said the failure was not related to cyber activity. It also ruled out any link to AI systems or agents.

Which services were affected by the outage?

Outlook and Exchange Online were hit first. Teams, Copilot, SharePoint, OneDrive, Defender, Purview, Planner, To Do and Intune were also affected. Microsoft said the impact reached every region of the world.

Were emails lost during the outage?

Microsoft treated mail delayed during the Microsoft 365 outage as queued, not lost. It extended the retry window to 48 hours so messages kept trying to deliver. Most late mail arrived once the queues drained.

How can I check the Microsoft 365 outage status myself?

Visit status.cloud.microsoft for the public service health page. Administrators can open the Microsoft 365 admin centre and read incident MO1550821. The final update there confirms that recovery is complete.