Microsoft 365 Outage Resolved: Outlook and Teams Restored

this article contains no affiliate links. All links are plain links, and we earn nothing if you click them. See our affiliate disclosure. How this article was prepared: AI helped gather and draft this research; a person checked the facts against the cited sources.

Quick answer: A Microsoft 365 outage that Microsoft first flagged at 17:54 UTC on Thursday, November 12, 2026 (01:54 MYT on Friday, November 13) left users unable to reach Outlook email, Teams and other Microsoft 365 services. Microsoft said at 06:09 UTC on Saturday, November 14 (14:09 MYT) that it had "restored service to the remaining impacted customers and regions". It blames "an issue during an earlier network capacity upgrade that surfaced following a recent network change", and says the incident was "not related to cyber or AI / agents". Microsoft has since published its preliminary post-incident report, tracing the failure to a software bug from July 2026; the final report is due within five business days.

Update (November 16, 2026): Microsoft said in its preliminary post-incident report that the outage came from a software defect introduced in July 2026 as part of a fix in Microsoft 365 networking gateway servers. The defect caused lock contention inside an internal process, making servers unresponsive under certain workloads. Microsoft executive Charles Lamanna shared an abridged version of the report's root-cause details on X on November 16. Two other factors combined with the bug: about fifteen hours before the outage, Teams traffic moved from an alternative gateway to the primary gateway shared with Exchange Online; and nearly 14% of network gateway server capacity was taken offline the previous day because of an unrelated issue. When all three combined, the bug was triggered, and automatic redirection of traffic to healthy servers spread the failure — a cascading failure that left more than 80% of servers unresponsive within less than two hours. Exchange Online could not use the same failover at its operating scale. Microsoft built an update that returned Windows connection handling to its earlier working state. Microsoft will publish the final post-incident report within five business days. In Microsoft's own wording, traffic shifts during standard network maintenance and upgrades exposed a latent bug causing a rapidly increasing number of requests to queue for processing.

Latest update (checked 00:09 MYT, Sunday, November 15, 2026): the outage is over. At 06:09 UTC on Saturday, November 14 (14:09 MYT), Microsoft said: "We have completed our efforts to address the underlying issue of the incident and restored service to the remaining impacted customers and regions." At our check, Microsoft's status page read: "All products are operational." The Associated Press reported that Microsoft said services were fully restored.

Microsoft has also given a first explanation. In a post at 18:05 UTC on November 13 (02:05 MYT on November 14), it said: "This was a technical issue not related to cyber or AI / agents. The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change." It added: "Given the scale of demand, we restored services gradually, validating stability at each stage." The same post opened with an apology: "We are deeply sorry for the disruption this incident has caused our customers and partners."

Delayed email was part of the recovery. On November 13 Microsoft said it had "extended email timeout to 48 hours" (09:24 UTC), and later that it was monitoring the email backlog "to ensure all process successfully before considering the issue resolved" (21:55 UTC).

Microsoft said it would provide a full post-incident report once its review was complete. The preliminary report, dated November 15, was published on November 16; the final report is due within five business days. Microsoft first flagged the outage at 17:54 UTC on November 12, so the restoration post came about 36 hours later (our calculation from Microsoft's posts).

Earlier update (checked 16:12 MYT, Friday, November 13, 2026): The outage is still not resolved more than 14 hours after Microsoft first flagged it. Microsoft's status page still shows "Service degradation" for Microsoft 365 (Business or Enterprise). Its latest entry, posted at 07:29 UTC (15:29 MYT), says: "We're seeing positive results for server stability after applying an upstream authentication/routing configuration component patch to a portion of our infrastructure." Microsoft says it is working to expand that fix, and adds: "As of now, we are not aware of any malicious activity that is causing this incident."

Microsoft also promises a fuller explanation once the outage ends: "Once mitigated, we will provide full details of the root cause, defense-in-depth repair items, and more within a Post-Incident Report." Its next update is due by 8:30 AM UTC (16:30 MYT) on November 13.

Consumers are affected too. The status page's Microsoft 365 (Consumer) card, updated at 06:24 UTC (14:24 MYT), says: "This issue impacts Outlook.com, OneDrive, OneNote, Microsoft To Do, Teams, and Microsoft 365 for the web although you may also see issues in other Microsoft 365 services."

Recovery has been slow. Overnight, Microsoft said at 22:09 UTC that "a core process on affected servers is becoming overwhelmed, causing capacity loss", and at 00:06 UTC that "the servers we returned to service can become unresponsive again once they receive traffic". At 03:13 UTC it said earlier changes were "not taking as expected". Its latest X post, at 07:44 UTC (15:44 MYT), reports "positive results for service stability and increased capacity as a result of our latest traffic optimization actions".

What Microsoft says is happening

At 17:54 UTC on November 12 (01:54 MYT on November 13), the Microsoft 365 Status account on X said: "We're investigating reports of users experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas." The incident is tracked as EX1550543 in the Microsoft 365 admin center.

!Screenshot of Microsoft's Service Health Status page: Microsoft 365 (Business or Enterprise), Service degradation. Users may be unable to connect to multiple Microsoft 365 services; potentially impacted: Exchange Online, Microsoft Teams, SharePoint Online, Microsoft Copilot 365, Microsoft Defender XDR. Next update by 10:00 PM UTC, last updated 7:30:36 PM UTC, November 12, 2026.

Source: Microsoft Service Health Status page, captured Nov 13, 2026, about 04:03 MYT. Credit: Microsoft. Shows the Microsoft 365 (Business or Enterprise) card, last updated 7:30:36 PM UTC on Nov 12. Not a TechKit graphic.

At 18:07 UTC, Microsoft said it had "confirmed the issue may affect Microsoft 365 service connectivity for users in any region". At 18:35 UTC it added that "a portion of infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors", and began pointing to a second incident ID, MO1550821.

At 19:31 UTC (03:31 MYT), Microsoft wrote: "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." The public status page, last updated at 19:30:36 UTC when we checked, phrases it as "a large number of servers being unexpectedly unavailable" and says Microsoft is "investigating what's causing these servers to become unavailable".

Which services were affected

During the outage, under "Microsoft 365 (Business or Enterprise)", the status page said: "Users may be unable to connect to multiple Microsoft 365 services." It listed Exchange Online, Microsoft Teams, SharePoint Online, Microsoft Copilot 365 and Microsoft Defender XDR as potentially impacted services.

TechCrunch reported that the outage was preventing both business and consumer users from accessing their inboxes, and that consumers were also unable to access their OneDrive storage, Office (for the web) and several other Microsoft services. Engadget reported that while the status report points to Business and Enterprise tiers, individual users also appear to be impacted.

The Associated Press reported that nearly 130,000 users on outage tracker Downdetector reported problems accessing Outlook just after 1 p.m. ET (18:00 UTC, 02:00 MYT), and that reports have since fallen some. Many said they couldn't send and receive emails or had trouble loading their inboxes, and thousands also reported issues with Teams and Copilot, AP said.

What Microsoft did to fix it

[Bloomberg reported]() that Microsoft said it was working to restore access to its bundle of workplace software. At 18:48 UTC Microsoft said: "We've begun redistributing connection traffic across our broader worldwide infrastructure to help balance the load." At 19:12 UTC it posted: "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." The status page adds that deployments and configuration changes were paused "while we review recent changes for any correlation to this event".

At the time of our first check, Microsoft's latest update had come at 19:50 UTC (03:50 MYT). It said: "We're testing a configuration change to address a problem that's causing servers to fail automated health checks and become unavailable. In parallel, we've initiated a restart of all affected servers and are monitoring health as they return to service." The status page then listed its next update by 10:00 PM UTC on November 12 (06:00 MYT on November 13). For what has happened since, see the latest update at the top of this article.

!TechKit table card, what Microsoft said and when (UTC / MYT): 17:54 / 01:54 investigating Exchange Online mailbox access issues in the Americas (EX1550543); 18:07 / 02:07 may affect users in any region; 18:35 / 02:35 elevated load across multiple regions, details also under MO1550821; 19:12 / 03:12 all deployments paused, restarting affected servers; 19:31 / 03:31 load not from more traffic but servers unexpectedly unavailable; 19:50 / 03:50 testing a configuration change, restart of all affected servers.

TechKit text card. Based on Microsoft 365 Status posts on X, checked Nov 13, 2026 MYT. Not an official screenshot.

Microsoft has now published its preliminary root cause in its preliminary post-incident report; see the November 16 update at the top of this article. TechCrunch noted Microsoft cited unavailable servers "for reasons it did not explain".

What admins and users can check

Microsoft points admins to incidents EX1550543 and MO1550821 in the Microsoft 365 admin center, and to status.cloud.microsoft "if the admin center is not available to you". The status page says the details are posted there "because Microsoft 365 administrators may be unable to access the admin center to get Service health information."

This is separate from an earlier Teams incident. Microsoft began investigating Teams problems in North America under TM1550488 at 15:40 UTC, and at 17:09 UTC said: "Customer impact is now fully resolved." The wider outage was tracked under different IDs.

FAQ

Is Microsoft 365 down right now?

No, according to Microsoft. At 06:09 UTC on November 14, 2026 (14:09 MYT), Microsoft said it had "restored service to the remaining impacted customers and regions". At our check at 00:09 MYT on November 15, its status page read "All products are operational."

What caused the Microsoft 365 outage?

Microsoft said in its preliminary post-incident report that a software defect introduced in July 2026 as part of a fix in Microsoft 365 networking gateway servers caused lock contention inside an internal process, making servers unresponsive under certain workloads. Two other factors combined with it: Teams traffic moved from an alternative gateway to the primary gateway shared with Exchange Online about fifteen hours before the outage, and nearly 14% of gateway server capacity was taken offline the previous day because of an unrelated issue. The combined load triggered the bug, and automatic redirection spread the failure until more than 80% of servers were unresponsive. Microsoft says it was a technical issue "not related to cyber or AI / agents".

When will Microsoft publish the final report?

Microsoft will publish the final post-incident report within five business days.

Which Microsoft services were affected?

Microsoft listed Exchange Online (Outlook email), Microsoft Teams, SharePoint Online, Microsoft Copilot 365 and Microsoft Defender XDR as potentially impacted. TechCrunch reported consumers also could not access OneDrive storage and Office (for the web).

Where can I check Microsoft 365 service status?

Admins can look up EX1550543 and MO1550821 in the Microsoft 365 admin center. If the admin center is not available, Microsoft points to status.cloud.microsoft. It also posts updates on its @MSFT365Status account on X.

Is this the same as the earlier Teams outage?

No. The earlier Teams incident, TM1550488, affected North America and was declared resolved at 17:09 UTC on November 12. The wider outage was tracked as EX1550543 and MO1550821.

Sources

Microsoft 365 Status (@MSFT365Status) on X, November 12, 2026: 17:54 UTC, 18:07 UTC, 18:35 UTC, 18:48 UTC, 19:12 UTC, 19:31 UTC, 19:50 UTC; earlier Teams incident 15:40 UTC and 17:09 UTC

Microsoft, Service Health Status page (last updated 7:30:36 PM UTC, November 12, 2026; checked 04:07 MYT November 13): https://status.cloud.microsoft/

TechCrunch, Zack Whittaker, "Microsoft's Outlook email hit by new outage" (November 12, 2026, 19:03 UTC, updated 19:48 UTC): https://techcrunch.com/2026/11/12/microsofts-outlook-email-hit-by-new-outage/

Engadget, Anna Washenko, "Multiple Microsoft 365 services are experiencing an outage" (November 12, 2026, 19:17 UTC): https://www.engadget.com/2315259/multiple-microsoft-365-services-are-experiencing-an-outage/

The Associated Press, "Is Outlook down? Widespread outage hits Microsoft email and other apps" (updated November 12, 2026, 19:33 UTC): https://apnews.com/article/microsoft-outlook-outage-email-teams-6376045281feb430c0b923e3a4b251c2

Bloomberg, Matt Day, "Microsoft Says It's Working to Fix Outlook, Copilot Outage" (November 12, 2026, 19:14 UTC) — URL not recovered, see self-check.

Microsoft 365 Status (@MSFT365Status) on X, November 12–13, 2026 (follow-up): 22:09 UTC, 00:06 UTC, 03:13 UTC, 07:44 UTC

Microsoft, Service Health Status page, follow-up check (Business or Enterprise card updated 07:29 UTC and Consumer card updated 06:24 UTC, November 13, 2026; checked 16:12 MYT): https://status.cloud.microsoft/

Microsoft 365 Status (@MSFT365Status) on X, November 13–14, 2026 (resolution): 09:24 UTC, 18:05 UTC, 21:55 UTC, 06:09 UTC November 14

Microsoft, Service Health Status page (checked 00:09 MYT, Sunday, November 15, 2026): https://status.cloud.microsoft/

The Associated Press, "Microsoft says services fully restored after hourslong global outage" (updated November 14, 2026, 4:21 a.m. EST): https://apnews.com/article/microsoft-outage-outlook-email-365-recover-ca395c0f1e51af784b6d70afb6554f6a

Cryptika, "Microsoft Reveals How a Hidden Windows Bug Took Down Microsoft 365 Services Worldwide" (November 16, 2026; republishes the Cyber Security News report in full): https://www.cryptika.com/microsoft-reveals-how-a-hidden-windows-bug-took-down-microsoft-365-services-worldwide/

KuCoin, "Microsoft 365 outage on November 12 caused by three combined factors" (November 16, 2026; summarizes Huo Xing Cai Jing's report of Lamanna's X post): https://www.kucoin.com/news/flash/microsoft-365-outage-on-nov-12-caused-by-three-combined-factors

University of Pennsylvania, PennO365 Microsoft 365 incident mirror (Microsoft's own admin-center incident text; EX1550543 status postIncidentReviewPublished; checked November 16, 2026): https://mailservices.isc.upenn.edu/computing/email/penno365/alerts/ms-incidents.html

AAP, "Microsoft services fully recover after global outage" (November 14, 2026): https://aapnews.aap.com.au/news/hours-long-microsoft-outage-hits-companies-governments

Charles Lamanna (@clamanna) on X, November 16, 2026: https://x.com/clamanna/status/2122209697226948729

Last checked: November 16, 2026 (MYT).*

Get new free-deal guides & reviews by email

2 thoughts on “Microsoft 365 Outage Resolved: Outlook and Teams Restored”

Leave a Comment