13 November 2026 — Microsoft is still working to restore Microsoft 365 services after an incident that left users unable to reach their Exchange Online mailboxes, with the company saying early on Friday India time that its recovery changes were "not taking as expected". As of 09:52 IST, the incident was still open.
The incident, tracked as EX1550543 in the Microsoft 365 admin center, began at 16:17 UTC on 12 November (21:47 IST), according to the incident record in Microsoft's admin center, and was first acknowledged by Microsoft's official Microsoft 365 Status account at 17:54 UTC (23:24 IST). Microsoft said it was investigating reports of users having trouble accessing Exchange Online mailboxes "through multiple connection methods in the Americas". Thirteen minutes later it said the issue "may affect Microsoft 365 service connectivity for users in any region". When I checked Microsoft's public service health page on the morning of 13 November, it still showed a service degradation for Microsoft 365 business and enterprise customers, stating that users "may be unable to connect to multiple Microsoft 365 services", and a degradation for Microsoft consumer products.
What Microsoft has said so far
At 18:35 UTC, Microsoft said part of its infrastructure was under elevated load across multiple regions, and it began publishing details under a second reference, MO1550821, alongside EX1550543. It then said it had begun redistributing connection traffic across its wider worldwide infrastructure.
“We've paused all deployments, we're moving additional traffic off the affected infrastructure, and we're restarting affected servers to return them to service.”
Microsoft 365 Status, 12 November 2026, 19:12 UTC
About 20 minutes later, the company narrowed down where the load was coming from. "We determined the elevated load isn't driven by an increase in traffic, but by a number of servers being unexpectedly unavailable; straining the remaining infrastructure," it said.
At 20:19 UTC (01:49 IST on 13 November), Microsoft said it had not identified any recent change that correlated with the start of the impact, but that the failed health checks "may originate from a specific component that's responsible for processing server health". It later said an alternative health check method had allowed a subset of servers to return to service, and at 21:40 UTC said it was assessing whether reverting "a small number of recent configuration updates" could help speed recovery.
By 22:09 UTC, the company said its actions had "not provided the anticipated relief". It added: "We found a core process on affected servers is becoming overwhelmed, causing capacity loss."
Partial recovery, then a setback
At 23:04 UTC, Microsoft reported returning a portion of affected servers to service, said they were stable so far, and described "limited recovery" as it shifted traffic to alternative routes. About an hour later it reported a new problem.
“The servers we returned to service can become unresponsive again once they receive traffic; we're analyzing diagnostic data to determine what's triggering the behavior.”
Microsoft 365 Status, 13 November 2026, 00:06 UTC
Microsoft said it was temporarily limiting which types of traffic could reach the affected infrastructure in some locations. At 01:01 UTC it said it had revised the list of affected services and features, published in the "more info" section of MO1550821. At 01:59 UTC it reported "positive results" from restarting infrastructure in an isolated manner, and at 02:29 UTC said it was adding capacity to support regions coming back online.
In a message to administrators at 01:06 UTC (06:36 IST), Microsoft said a process on the affected servers "responsible for establishing secure connections becomes overwhelmed, causing the servers to stop processing requests". It said it had also "begun reverting a recent network configuration change that correlates with the start of impact", and was monitoring whether that helped.
An update at 03:13 UTC (08:43 IST) on 13 November was less positive: "We’ve monitored the status of the changes applied to improve serviceability and confirmed they're not taking as expected." Microsoft said it was looking for alternative ways to increase capacity in the face of "sustained traffic management imbalances". At 03:48 UTC (09:18 IST) it said it was reviewing traffic flows and affected infrastructure "to identify opportunities to optimize routing". Its public status page, updated at 04:11 UTC (09:41 IST), still showed a service degradation and added: "for now we can confirm that there is no indication this is the result of malicious activity." In its next status update, at 04:22 UTC (09:52 IST), Microsoft said it was "observing partial recovery across regions in which we've applied these adjustments; however, these actions aren't resulting in sustained recovery". It said it was adjusting traffic protocols, redistributing traffic and "applying strategic traffic blocking measures". Microsoft has not published a root cause or an estimated time for full recovery, and said its next update would come by 05:00 UTC (10:30 IST).
Background
Exchange Online is the hosted email and calendar service behind Outlook for Microsoft 365 business and enterprise customers. Microsoft directs administrators to the Service health section of the Microsoft 365 admin center for incident details, and points to its public status page for those who cannot reach the admin center.
Earlier on 12 November, at 15:40 UTC, the same status account reported a separate issue affecting Microsoft Teams in North America under TM1550488, which it said was fully resolved at 17:09 UTC. Microsoft has not said whether the two incidents are connected.
Analysis
In my view, the most telling detail is Microsoft's statement that the load was not caused by more traffic but by servers dropping out and pushing their work on to the rest. That is a classic cascading failure: each server that fails a health check makes the next one more likely to fail, and simply restarting servers can bring them back into the same overload. Microsoft's moves to pause deployments, change how health checks work and limit traffic types all fit that picture.
For businesses, the practical lesson is about dependencies. Email is often also the route for password resets, sign-in codes and alerts, so an email outage can lock people out of other systems. It is worth keeping at least one out-of-band contact method for staff and clients, and making sure administrators know where to read incident updates when the admin center itself is slow. I will update this report if Microsoft confirms recovery or publishes a root cause.
About this report
Based on updates posted by Microsoft's official Microsoft 365 Status account on X between 12 and 13 November 2026 and the Microsoft service health status page. Facts and quotes are taken from the sources credited below, which I read on 13 November 2026 up to 10:05 IST, and checked against the further reporting listed. Sections marked "Analysis" are my own view. I am an independent developer and am not affiliated with the organisations named here.
Credits and sources
- Source: Microsoft 365 Status (X), 12 Nov 2026, 17:54 UTC: Investigating Exchange Online mailbox access issues in the Americas (EX1550543)
- Source: Microsoft 365 Status (X), 12 Nov 2026, 18:07 UTC: Issue may affect Microsoft 365 connectivity in any region
- Source: Microsoft 365 Status (X), 12 Nov 2026, 19:12 UTC: Deployments paused and servers restarted
- Source: Microsoft 365 Status (X), 12 Nov 2026, 19:31 UTC: Elevated load caused by unavailable servers
- Source: Microsoft 365 Status (X), 12 Nov 2026, 20:19 UTC: Failed health checks traced to a server-health component
- Source: Microsoft 365 Status (X), 12 Nov 2026, 22:09 UTC: Core process on affected servers becoming overwhelmed
- Source: Microsoft 365 Status (X), 13 Nov 2026, 00:06 UTC: Restored servers can become unresponsive again
- Source: Microsoft 365 Status (X), 13 Nov 2026, 01:59 UTC: Positive results from restarting infrastructure
- Source: Microsoft 365 Status (X), 13 Nov 2026, 03:13 UTC: Changes not taking as expected
- Source: Microsoft 365 Status (X), 13 Nov 2026, 03:48 UTC: Reviewing traffic flows to optimise routing
- Source: Microsoft 365 admin center messages for EX1550543 and MO1550821, as republished by the University of Pennsylvania: Microsoft's Incident Reports for PennO365
- Source: Microsoft (status page, updated 13 Nov 2026, 04:22 UTC): Microsoft service health status page
- Further reporting: Josh Taylor and Emma Elsworthy, The Guardian, 12–13 Nov 2026: Microsoft begins restoring services as global outage affects Outlook and Teams
- Further reporting: Richard Lawler, The Verge, 12 Nov 2026: Microsoft Outlook is still down
- Further reporting: ABC News (Australia), 13 Nov 2026: Microsoft platforms including Outlook suffer widespread outages
- Lead image: Illustration created for this article: computer-generated graphic with headline text, made by Depakar B.
Corrections
Spotted an error? Please contact me. Corrections are noted on this page with the date.