Microsoft 365 outage recovery is complete. Microsoft marked its Outlook and Exchange Online outage restored at 11:10 a.m. ET on Friday, November 13, 2026, about a day after it began. It has given a first explanation of the cause and promised a full report.
Status as of November 15: resolved. Microsoft’s final notes for incidents EX1550543 and MO1550821 give an end time of "Friday, November 13, 2026, at 4:10 PM UTC." They say a "preliminary Post-Incident Report" will follow "within two business days" and a final one "within five business days." The Microsoft 365 service health status page is where to check for anything new.
The short version: mail that was delayed should have arrived by now, so resend only what bounced. Check message trace before you chase a missing email. Re-check anything security or compliance related that ran during the outage, such as quarantine releases, DLP and Intune compliance. Microsoft says it found no evidence of an attack, so password resets are not needed. Then read the post-incident report when it lands.
We covered the first night of the outage in Microsoft 365 Outage Takes Down Outlook. This post covers what Microsoft has said since and what to finish as part of Microsoft 365 outage recovery.
What caused the Microsoft 365 outage
Microsoft’s closing notes give a short, preliminary cause. For Microsoft 365 it says, "The incident was introduced by an issue during an earlier network capacity upgrade." For Exchange Online it points to "a failure in the systems responsible for establishing secure connections to the service."
Its incident notes for EX1550543 (Exchange Online) and MO1550821 (Microsoft 365) do show how its thinking changed through the night. We read the full history through Cloud Admin Hub, which mirrors Microsoft’s service health feed, and checked the latest note against Microsoft’s own status page.
Early on, Microsoft said the load came from servers dropping out, not from more traffic. It then said the servers were failing automated health checks. By Thursday evening it had two leads:
- A process "responsible for establishing secure connections becomes overwhelmed," which stopped servers from handling requests.
- "A recent network configuration change that correlates with the start of impact," which Microsoft began reverting.
Servers it restarted kept falling over once traffic came back. Overnight, Microsoft reported "a surge in outbound call volume" from its routing services to backend servers, and some machines stuck "in a bad state."
The turn came early Friday. At 2:24 a.m. ET, Microsoft reported "positive results for server stability" after applying "an upstream authentication/routing configuration component patch." It then rolled that patch out region by region, starting where the business day was beginning.
Treat all of this as Microsoft’s preliminary account. The post-incident report will be the record.
Microsoft 365 outage recovery timeline in ET
Times are Eastern, converted from the UTC times in Microsoft’s incident notes. Microsoft 365 outage recovery started early Friday.
-
Thu 11:20 a.m. Microsoft opens the incident: possible issues "accessing mailboxes via one or more connection methods."
-
1:43 p.m. Outlook connection traffic is spread across Microsoft’s worldwide infrastructure to balance load.
-
2:06 p.m. Microsoft pauses "all deployments and configuration changes" as a precaution.
-
2:18 p.m. The load is blamed on servers "unexpectedly unavailable," not a traffic increase.
-
5:00 p.m. "A core process on the affected servers is becoming overwhelmed."
-
6:59 p.m. Restored servers "can become unresponsive again" under traffic. Some are rebuilt on a previous software configuration.
-
8:06 p.m. The secure-connection process is named, and a recent network change is being reverted.
-
9:54 p.m. A fix "is not taking as expected."
-
Fri 2:24 a.m. A routing and authentication patch shows positive results.
-
4:03 a.m. Microsoft extends "the email timeout window to 48 hours" to protect delayed mail.
-
6:01 a.m. Recovery in parts of Asia Pacific.
-
7:00 a.m. Recovery spreading in Europe.
-
8:00 a.m. "broader improvements now observed in North America."
-
9:01 a.m. Queues "approaching normal levels." No evidence of malicious activity.
-
11:10 a.m. Microsoft’s recorded end of impact. Both incidents are later marked restored.
Delayed email: what the 48-hour window means
When mail cannot be delivered, Exchange Online keeps retrying for a set time. After that the message expires and the sender gets a bounce. Microsoft stretched that window to 48 hours during this outage. That kept mail sent during the outage in the queue instead of bouncing.
That changes what you tell staff during Microsoft 365 outage recovery:
- Do not resend everything. Most delayed mail was delivered once queues cleared, and resending creates duplicates.
- Expect some messages with Thursday timestamps to have arrived late, out of order.
- Look for bounces. Those are the messages to resend.
- Ask outside partners to resend anything they sent you Thursday that bounced.
To check a specific message, use message trace. In the Exchange admin center, go to Mail flow, then Message trace. Microsoft says it shows whether the service "received, rejected, deferred, or delivered a message." A "deferred" status means it was held in the queue.
What else to check after the Microsoft 365 outage
The outage reached well past Outlook. Microsoft’s MO1550821 notes list problems in more than a dozen services. Several of them can leave quiet damage behind, so add them to your Microsoft 365 outage recovery checklist.
-
Quarantine and Safe Links (Defender for Office 365). Microsoft said quarantine releases could fail and Safe Links clicks could fail to load. Tenant allow and block list changes were delayed. Re-check any release or list change made Thursday.
-
DLP and labels (Purview). Data loss prevention, auto-labeling, audit searches and eDiscovery exports were affected. Rerun any search or export started during the outage, and do not count on DLP having caught everything.
-
Intune. Enrollment, check-in and compliance were "intermittently impacted." Devices may show as out of compliance and get blocked by sign-in rules. Check your compliance report before staff call in.
-
Teams calendars. Meetings and invites that depend on Exchange failed. Ask organizers to confirm Thursday and Friday invites went out.
-
Power Apps mobile. Sign-in could fail. Microsoft advised signed-in users not to sign out or reinstall during the outage.
-
Graph-based integrations. Calls that read mail, calendar or contacts could time out. Check sync jobs and automations that ran overnight.
What nonprofit and association IT teams should do today
Small teams do not need a big response plan for this. A short Microsoft 365 outage recovery list covers it:
- Send one all-staff note. Mail is back, delayed messages have arrived, do not resend, and report any bounces.
- Check your shared and member-facing mailboxes first. Membership, events and donations inboxes may hold time-sensitive mail from Thursday.
- Run message trace on anything urgent before anyone assumes it is lost.
- Re-check the security and compliance items above. Quarantine, DLP and Intune matter most.
- Ignore outage-themed "reset your password" emails. Microsoft says there is no sign of an attack. Our guide to phishing attacks covers what these look like.
- Write down your impact. Note when your users lost access and got it back, from Service health and your own tickets.
The post-incident report and what to learn from it
Microsoft says a preliminary post-incident report will come within two business days of the end of impact and a final one within five. During the outage it said the report would cover "root cause and defense-in-depth actions." It posts these in Service health. Microsoft’s guide to service health lists "Post-incident report published" as one of the statuses an incident can reach.
When it arrives, read it with your own notes in hand to close out your Microsoft 365 outage recovery. Look for the confirmed cause, the real start and end times, and what Microsoft says it will change.
If your agreement includes Microsoft’s service level terms, your impact notes will help. Microsoft publishes its Service Level Agreements for Online Services on its licensing site. Check the current terms there or with your reseller.
The bigger lesson is about dependence. When Exchange Online went down, it took Teams calendars, Copilot, Purview and Intune with it. If email is your main way to reach staff, plan a second channel now. A text list or a free chat workspace is enough. Keep current exports and backups of anything you cannot work without, as covered in data backup strategy basics.
Frequently Asked Questions
Is the Microsoft 365 outage over?
Yes. Microsoft recorded the end of impact at 4:10 PM UTC (11:10 a.m. ET) on Friday, November 13, 2026, and marked both incidents restored. Microsoft 365 outage recovery for most teams is now about checking what broke quietly.
What caused the Microsoft 365 outage?
Microsoft’s preliminary cause is “an issue during an earlier network capacity upgrade” and “a failure in the systems responsible for establishing secure connections to the service.” A routing and authentication patch led to recovery. The full report will confirm the details.
Was the Microsoft 365 outage a cyberattack?
Microsoft says it has “no evidence of malicious activity associated with this incident.” There is no need to reset passwords because of the outage.
Will I get the emails sent during the outage?
Most of them. Microsoft extended the email timeout window to 48 hours, so delayed messages stayed queued and delivered once service recovered. Resend only what bounced.
How do I check if a specific email was delivered?
Use message trace in the Exchange admin center under Mail flow, then Message trace. A “deferred” status means the message was held in the queue.
Which Microsoft 365 services were affected?
Exchange Online and Outlook were hit hardest. Microsoft also listed Teams, Copilot, SharePoint, Defender, Purview, Intune, Planner, To Do, Power BI, Graph, Universal Print, Windows 365 and the admin centers.
How long did the Microsoft 365 outage last?
Microsoft opened the incident at 11:20 a.m. ET on Thursday, November 12, and recorded the end of impact at 11:10 a.m. ET on Friday, November 13. That is about 24 hours.
When will Microsoft publish the post-incident report?
Microsoft says a preliminary report will come within two business days and a final one within five business days. They will appear in Service health in the Microsoft 365 admin center.