Microsoft 365 Outage: Outlook and Teams Down Worldwide for a Day
![]()
Photo: JESHOOTS.COM, CC0 — via Wikimedia Commons
On Thursday 12 November 2026, email stopped working for millions of people. Outlook would not load, messages would not send, Teams calendars would not open, and Copilot went dark. The outage began late in the morning and spread across the world, with reports logged in 74 countries. Access took more than a day to largely recover — and even on Saturday morning, 14 November, Microsoft had still not declared the incident resolved.
How the outage unfolded
The first problems appeared in Exchange Online, the service behind Outlook mail. Microsoft logged the incident as EX1550543, with problems beginning at 11:17 a.m. ET on Thursday 12 November. Within hours it had widened into a broader Microsoft 365 degradation, logged as MO1550821 at 1:26 p.m. ET.
Downdetector logged roughly 130,000 Outlook problem reports at the peak, from 74 countries — a worldwide outage, hitting the United States, Europe and Asia at the same time, in the middle of a working week.
Outlook was hit on web, desktop and mobile, and mail delivery itself was disrupted. Teams calendars and scheduling stopped working, and SharePoint, Copilot, Graph, Planner, To Do, Intune, Purview and Power BI were affected too. The whole Microsoft 365 workplace — email, meetings, documents, tasks and the AI assistant — was degraded at once, with no workaround inside the Microsoft system.
What caused it
Microsoft said part of its infrastructure was under elevated load across multiple regions, later blaming an issue during an earlier network capacity upgrade that surfaced after a recent network change. A change meant to add capacity created a problem that only appeared once it was live — and the load spread across regions rather than staying in one place.
Microsoft apologised, said it was "deeply sorry", and ruled out a cyberattack and any link to AI or its AI agents. That matters because the outage came in the same week as the end of the US government shutdown and the FAA's nationwide ground stop on 13 November, and speculation about a common cause was already circulating. Microsoft also confirmed there was no indication the FAA ground stop was related to any Microsoft services.
The recovery — and the email backlog
Access had largely recovered by 3:02 p.m. ET on Friday 13 November, more than a day after the outage began. But by the morning of Saturday 14 November, Microsoft reported "broad recovery and stability" yet had still not declared the incident resolved, and gave no ETA for full recovery while it cleared the email backlog.
The backlog affects users most directly: Microsoft extended the mail timeout to 48 hours, so delayed mail kept retrying instead of bouncing back to the sender. Messages were delayed rather than lost — but inboxes filled in waves as the backlog cleared, and some mail arrived a day late.
If you are still waiting for an important message, check your inbox and spam folders before assuming it never arrived. Mail sent during the outage with no bounce is likely delayed, not lost. If you did receive a bounce, resend it now. For anyone waiting on a job offer, a visa decision or a university reply, late mail is better than mail never sent.
![]()
Photo: Crew, CC0 — via Wikimedia Commons
Who was hit hardest
The outage hit hardest where Microsoft 365 is the whole workplace. Large employers, universities and government offices run email, calendars, documents and meetings through the platform, and when all of those stop at once there is no fallback. Workers could not read mail, check calendars, or join Teams meetings — for remote and hybrid teams, a shutdown of the office itself.
Small businesses and individuals were affected too. A freelancer waiting on a client reply, a jobseeker waiting on an interview invitation, or a migrant waiting on a document all depend on email arriving on time — a day's delay can mean a missed deadline, and the outage gave no warning. Our report on the Nvidia leadership shake-up covers another of the week's big technology stories, and the Hormuz tanker explosions show how the same week moved energy markets.
What to do if your mail is still affected
- Mail sent between 12 and 13 November with no bounce was likely delayed, not lost — confirm with the recipient if it was urgent.
- If you received a bounce message, resend now that the service has largely recovered.
- If Teams still shows wrong or missing meetings, refresh the app and check Outlook on the web.
- If you run a business on Microsoft 365, check that scheduled mail, invoices and automated messages went out.
The October CPI report shows how the same week that broke email also moved expectations about US interest rates.
What happens next
Microsoft has not yet given a full account, or said when the incident will close. It will need to explain what went wrong in the network capacity upgrade, why the load spread across regions, and what changes it will make to testing and rollback. Enterprise customers will want answers in writing, and some will ask for service credits. For users, the lesson is practical: email is not instant or guaranteed — keep copies of important messages, confirm receipt of anything time-critical, and have a second way to reach the people who matter.
![]()
Photo: Shixart1985, CC BY 2.0 — via Wikimedia Commons
Official links and sources
- Microsoft 365 Status — incidents EX1550543 and MO1550821, November 2026; The Hindu — live coverage, 13–14 November 2026
- BleepingComputer, via Acorn Technology — the outage, its cause and the recovery
- Downdetector — user problem reports for Outlook during the outage
Frequently asked questions
When did the Microsoft 365 outage start, and what was affected? The Exchange Online incident began at 11:17 a.m. ET on Thursday 12 November 2026 (EX1550543), widening into broader Microsoft 365 degradation at 1:26 p.m. ET (MO1550821). Outlook, mail delivery, Teams calendars, SharePoint, Copilot, Graph, Planner, To Do, Intune, Purview and Power BI were affected. Downdetector logged about 130,000 Outlook problem reports at the peak, from 74 countries.
Was the outage caused by a cyberattack? No. Microsoft ruled out a cyberattack and any link to AI, and apologised, saying it was "deeply sorry". The company blamed an issue during an earlier network capacity upgrade that surfaced after a recent network change.
Is the outage over, and what about my missing email? Access had largely recovered by 3:02 p.m. ET on 13 November, and by Saturday morning Microsoft reported "broad recovery and stability" — but the incident was not declared resolved and no ETA was given. The mail timeout was extended to 48 hours so delayed mail kept retrying. Check your inbox and spam, and resend any message that bounced.
Comments
Post a Comment