Skip to content
ramira

13 November 2026 · 6 min · Web and mobile apps

The global Outlook outage of 12–13 November 2026: what happened

On Thursday 12 November 2026, in the late afternoon UTC, Microsoft’s Outlook email stopped working for a very large number of businesses around the world. Mailboxes would not open. Emails would not send. Teams, SharePoint and other Microsoft 365 tools followed. The next morning, Microsoft was still working to restore the service. Here is what we know, hour by hour, and what a small business can take from it.

Written on the morning of 13 November 2026, with the information published at that time. It will be updated when Microsoft publishes its report.

Hands typing on a laptop keyboard, surrounded by dozens of drawn envelopes representing emails.
Illustration. Photo: geralt, Pixabay licence, via Pixabay.

What happened, in short

Exchange Online is the Microsoft service that runs business Outlook mailboxes. On 12 November, part of its servers became unavailable. The remaining servers received all the load. They could not cope.

Microsoft first described a problem in the Americas. It then confirmed that sign-in to Microsoft 365 could be affected for all users, in any region.

According to Downdetector, quoted by franceinfo, the outage hit Microsoft products in 74 countries and territories.

The timeline, hour by hour

Times are in UTC. Add one hour for Paris; subtract five hours for New York.

Date and time (UTC) What happens
Thursday 12 November, 16:17 Start of incident EX1550543, according to Microsoft’s record (as mirrored by the University of Pennsylvania, whose other times are in UTC).
Thursday 12 November, around 17:50 Microsoft says it is investigating problems reaching Exchange Online mailboxes, first in the Americas.
Thursday 12 November, just after 18:00 Downdetector shows nearly 130,000 reports for Outlook, and thousands for Teams and Copilot.
Thursday 12 November, 18:26 Microsoft opens a second incident, MO1550821, for the other Microsoft 365 services.
Thursday 12 November, around 19:50 Microsoft tests a configuration change on its servers.
Thursday 12 November, around 21:00 Microsoft validates another way to check server health. Some servers come back online.
Thursday 12 November, around 21:40 Microsoft restarts the affected servers.
Thursday 12 November, around 23:00 Microsoft returns some servers to service. It later warns they can become unresponsive again once they receive traffic.
Friday 13 November, 02:54 Microsoft writes that the change is “not performing as expected”. It looks for other ways to add capacity.
Friday 13 November, 04:10 Partial recovery in some regions, but not sustained. Microsoft redistributes traffic and blocks some of it.
Friday 13 November, 04:59 Microsoft sees a surge in calls from its routing services to the mail servers.
Friday 13 November, 07:25 Microsoft reports “positive results” for server stability where a patch was applied.
Friday 13 November, 08:06 Microsoft extends the patch to regions entering business hours. The incident is not closed. Next update promised at 09:00.

The cause, according to Microsoft

Microsoft has not yet published its full report. It promised a post-incident report once the outage is fixed. Here is what it said during the outage.

  • A number of servers became unexpectedly unavailable. The others had to absorb all connections.
  • It was not a rise in the number of users. It was a loss of capacity.
  • A core process on these servers was overwhelmed.
  • Some servers were failing automated health checks. These failures made recovery harder.
  • The patch that worked targets an authentication and routing component, upstream of the mail servers.

Microsoft repeated that it was not aware of any malicious activity causing the incident. One of its executives also wrote this on X, according to AFP.

An aisle between two rows of black server cabinets in a data centre, with a perforated tile floor.
Illustration: a server room. Photo: Apke, Pixabay licence, via Pixabay, cropped.

Who was hit

Email was hit hardest. Many users could not send or receive messages. Some could not even load their inbox.

Microsoft listed these services in its notice: Outlook.com, OneDrive, OneNote, To Do, Teams and Microsoft 365 for the web. Its MO1550821 record also names SharePoint, Copilot, Planner, Intune, Power BI, Power Apps, Defender, Purview, Windows 365 and Universal Print.

A few examples from the press:

  • Health. The University of Iowa hospital network lost email and voicemail. It asked patients to use its online portal.
  • Air travel. IndiGo (India) and CemAir (South Africa) reported email problems. None had reported flight disruptions.
  • Government. Japan’s government said its IT was affected. In New York, the city’s Emergency Management warned of delays in email and some online services.
  • AI assistants. Assistants that read the email or calendar of a Microsoft account were also disrupted.

Microsoft said it had restored Teams in North America, according to AP. But some users still reported connection problems.

What a small business can do when its email goes down

This outage did not come from a crashed computer, unlike the CrowdStrike outage of 19 July 2024. Your computers worked. The online service stopped answering. So the right moves are different.

  1. Keep your key contacts outside your email. Current clients, suppliers, your accountant: name and phone number, on paper or in your phone. When email goes down, you call or text.
  2. Keep a local copy of your mail. The desktop Outlook app keeps a copy of messages already received. Check that this mode is on. You can still read a quote or an address without the service.
  3. Have a backup address. A mailbox with another provider, known to your main clients, is enough for a day. Put it in your email signature, not just in your head.
  4. Do not put everything behind one account. Here, sign-in to Microsoft 365 itself was affected. If your files, calendar and email all go through one account, they all stop at once. Keep at least your vital documents reachable another way.
  5. Subscribe to your provider’s alerts. Microsoft posts service status in the Microsoft 365 admin center and on its “Microsoft 365 Status” account on X. You quickly know whether the problem is on your side or theirs.
  6. Warn your clients through another channel. A message on your website or your Google business profile saves dozens of worried calls.
  7. Back up what matters, and test it. The more your data sits with one provider, the harder an outage hits. Our method to back up Odoo automatically works for any business software.

In short

On 12 November 2026, around 17:50 UTC, Microsoft reported an Exchange Online outage. Outlook, Teams and much of Microsoft 365 were hit worldwide. According to Microsoft, servers dropped out suddenly and the others could not carry the load. On the morning of the 13th, a patch was showing good results, but the outage had already lasted more than 14 hours.

A small business cannot fix Microsoft. It can keep its key contacts outside email, a local copy of its messages and a backup address.

Want tools that do not depend on a single provider? We build web and mobile apps hosted in France, and we publish our own apps. For Odoo users, see our custom Odoo modules or contact us.

FAQ

Was it a cyberattack?

Microsoft says no, so far. It wrote several times that it was not aware of any malicious activity causing the incident. The exact cause will be in its post-incident report, once the outage is fixed.

Which services were affected?

Mostly Outlook and Exchange Online, the email service. Microsoft also named Outlook.com, OneDrive, OneNote, To Do, Teams and Microsoft 365 for the web. Its incident record also lists SharePoint, Copilot, Planner, Intune, Power BI, Windows 365 and others.

Are emails sent during the outage lost?

Microsoft has not said so far. If in doubt, resend important emails once the service is back, and warn your contacts another way.

What is Microsoft’s incident number?

EX1550543 for Exchange Online email, and MO1550821 for the other Microsoft 365 services. An administrator can find them in the Microsoft 365 admin center, under Service health.

Sources

Mohamed Rahmouni — founder of Ramira, app developer and Odoo consultant in Niort, France. More

Read next

An app, website or Odoo module project?

Describe it in a few lines: reply within 2 business days, with a first estimate.