Microsoft restores Outlook after a global Microsoft 365 outage
Microsoft is making progress in restoring Outlook and Microsoft 365 after the global outage that began on November 12. Email and other services are showing improvement, but intermittent connections, delayed messages, and questions about the definitive cause persist.
Microsoft began restoring access to Outlook and other Microsoft 365 services this Friday, November 13, 2026, after an international outage that started on Thursday the 12th. The failure affected email, Exchange Online connections, and various business tools that depend on the same infrastructure.
Recovery has been gradual. In its updates on Friday, Microsoft reported that the queues of pending emails had been reduced considerably and that there were sustained improvements in availability, although intermittent failures and delayed messages were still occurring.
How the Outlook outage began
The incident identified as EX1550543 officially began at 16:17 UTC on Thursday, November 12, equivalent to 10:17 in the morning in central Mexico. Microsoft later opened incident MO1550821, related to the effects that spread to other Microsoft 365 products.
The first problems were concentrated in connections to Exchange Online mailboxes, the service that manages Microsoft's business email. Users reported difficulties opening their inboxes, sending and receiving messages, checking calendars, and keeping their applications connected.
The scale was considerable. According to Associated Press, Downdetector logged nearly 130,000 reports of Outlook problems shortly after 1 p.m. Eastern Time in the United States, though that figure reflects user reports rather than the total number of people affected.
What caused the outage
Microsoft identified an overload issue in its infrastructure. Numerous servers stopped responding to automated health checks and were taken out of service, so requests concentrated on the remaining machines.
The investigation also found that a process responsible for establishing secure connections was becoming saturated and causing some servers to stop processing requests. Microsoft examined recent network configuration changes that temporarily coincided with the incident, without yet establishing a definitive causal link.
To restore capacity, the company redistributed connections, restarted servers, limited certain types of traffic, and tested configuration changes. Several of the early measures produced insufficient or temporary results, because some servers failed again once they began receiving requests.
Microsoft also reported that it found no evidence of malicious activity associated with the incident. The follow-up report will need to establish the root cause and explain what measures it will take to reduce the possibility of a similar disruption.
Which Microsoft services were affected
The list was much broader than Outlook. Microsoft identified issues in Exchange Online-related functions across different tools.
| Service | Reported impact |
|---|---|
| Outlook and Exchange Online | Email access, connections, and delayed delivery |
| Microsoft Teams | Calendars, invitations, and meeting scheduling |
| Microsoft 365 Copilot | Access to conversations and work data |
| SharePoint Online | Some external sharing features |
| Microsoft Planner and To Do | Plan and task operations, and app loading |
| Microsoft Defender and Purview | Access to portals and certain protection features |
| Microsoft Graph | Requests related to email, contacts, and calendars |
| Power BI and Fabric | Certain exports with sensitivity labels |
The scope varies depending on the function. Microsoft clarified that core Teams meetings, calls, and messages were largely still working, while certain calendar-related operations could fail.
Issues were also reported in admin centers, Microsoft Intune, and some Power Platform apps. Organizations using automations or integrations based on the affected services may have experienced additional errors.
November 13 updates
The official information allows us to reconstruct the most relevant developments from Friday, using Mexico City time.
| Time | Update |
|---|---|
| 6:00 a.m. | Microsoft reported improvements in Europe and North America. |
| 7:00 a.m. | Confirmed progress in various regions and a reduction in queued messages. |
| 8:01 a.m. | Backlogs of pending emails were approaching normal levels. |
| 8:57 a.m. | Reported sustained improvements, though intermittent errors persisted. |
| 9:52 a.m. | Stability checks and measures to address residual impact continued. |
| 10:53 a.m. | Continued working to achieve stable restoration across all connection methods. |
In its Exchange Online updates, Microsoft also confirmed that it temporarily extended the mail delivery retry window to 48 hours to help process delayed messages.
The next official update was scheduled for 18:00 UTC on Friday, equivalent to 12:00 noon Central Mexico time.
What to do if Outlook is still showing errors
The first step is to check the official Microsoft 365 status. Organization administrators can review incidents EX1550543 and MO1550821 in the admin center to learn how their services are affected.
If a message is still pending delivery, it's best to check its status before sending it again. During recovery, some emails may be delivered after several attempts, so resending them without checking their status can create duplicates.
It's also advisable to avoid reinstalling, making unnecessary configuration changes, or deleting local data as an initial response to this outage. A localized failure in Microsoft's infrastructure generally isn't fixed by modifying each device.
Recovery still needs final confirmation
Outlook and Microsoft 365 show significant recovery compared with the first hours of the outage. However, full normalization depends on Microsoft confirming connection stability, finishing processing pending messages, and closing the official incidents.
For companies that rely on Microsoft email and calendars, the immediate consequence is clear: regaining access to an application does not necessarily mean that all related messages and services are back to normal.
Terms in this note
- Exchange Online: cloud service that manages Microsoft enterprise email and calendars.
- Microsoft 365: suite of Microsoft productivity applications and services.
- Downdetector: platform that collects user reports about digital service outages.
- Microsoft Graph: interface that allows other applications to query information and perform operations on Microsoft services.
- Root cause: the original problem that triggers an outage and must be identified to prevent it from recurring.
References
- Microsoft Service Health, official status of its services
- Official Microsoft 365 incident records published by the University of Pennsylvania