Microsoft 365 outage: what happened and how to avoid being stuck

11 min read

Visuel Wayhost sur fond bleu nuit, avec le titre « Microsoft 365 outage: what happened and how to avoid being stuck » et un pictogramme d'enveloppe

The global Microsoft 365 outage of November 12, 2026: timeline, affected services, the cause stated by Microsoft, what happened to emails, and a practical plan to keep a working email service during the next outage.

By Mouhamed BANKOLE, CEO at ITNET Technologies · Updated November 17, 2026 · Reading time: 10 min

On Thursday, November 12, 2026, at around 5:20 p.m. Paris time, Microsoft 365 went down worldwide, cutting millions of businesses off from Outlook and Exchange Online for about 24 hours, according to Microsoft's preliminary report as reported by IT-Connect. Microsoft announced on Saturday, November 14 that all its services were restored and ruled out a cyberattack (ICTjournal). For a small business hit by the Microsoft outage, the question is no longer just "what happened?" but "how do we avoid being stuck next time?". This guide sets out the established facts, then lays out a practical plan to keep a working email service when a provider goes down.

In short

  • The facts: a global Microsoft 365 outage from November 12, 2026, led by Exchange Online and Outlook, with full recovery announced on November 14.
  • The stated cause: a faulty Windows patch on gateway servers that only showed up under heavy load; no cyberattack.
  • Emails are generally not lost: sending servers retry for several days, but messages arrive late.
  • The real risk is business disruption: no email, calendar or scheduled meetings for a whole working day.
  • You cannot prevent a provider outage, but you can soften it: local copies, a backup channel, independent backups and control of your domain name.

Contents

  1. What happened during the November 12 Microsoft 365 outage?
  2. Which Microsoft services were affected?
  3. Why did Microsoft 365 go down?
  4. Are emails sent during the outage lost?
  5. What does this outage change for your business?
  6. What should you do during an email outage?
  7. How do you avoid being stuck during the next outage?
  8. Should you leave Microsoft 365 after this outage?
  9. What should you expect from Microsoft's final report?

What happened during the November 12 Microsoft 365 outage?

Microsoft 365 suffered a global outage that began on Thursday, November 12, 2026 in the late afternoon and made Outlook and Exchange Online unreachable for most users for about a day (IT-Connect). Microsoft then announced on X, on Saturday, November 14, that all services were restored (ICTjournal).

What is established so far:

  • the start of the incident: Thursday, November 12 at 5:20 p.m. Paris time, according to the preliminary report (IT-Connect);
  • Exchange Online's return: Friday, November 13 at 5:10 p.m. Paris time, according to the same report (IT-Connect);
  • the scale: more than 7.4 million reports on Downdetector, according to Reuters as cited by ICTjournal;
  • no cyberattack: Microsoft ruled it out, as well as any involvement of AI agents (ICTjournal).

Administrators can read the preliminary report in the Microsoft 365 admin center, under references MO1550821 and EX1550543 (ICTjournal).

Which Microsoft services were affected?

Exchange Online, and therefore Outlook on the web and desktop, was the hardest hit, but the outage spread to several tools in the Microsoft 365 ecosystem (ICTjournal). Teams chats and meetings, however, worked normally for most of the incident (IT-Connect).

ServiceWhat stopped workingImpact for a small business
Exchange Online / OutlookMailbox access, delayed emailsNo email with customers or suppliers
TeamsCalendar integration, meeting schedulingMeetings impossible to set up or find
Microsoft 365 CopilotFeatures unavailableAssistants and automations stopped
SharePointSome featuresAccess to shared documents disrupted
Admin portalAccess disruptedHard for IT staff to diagnose
Defender, PurviewSafe Links, Defender XDR portal, compliance toolsWeaker protection and auditing
Graph, IntuneAPIs and device managementBusiness apps and device fleet affected

Source for the list: ICTjournal.

Why did Microsoft 365 go down?

According to Microsoft's preliminary report, the cause was a faulty Windows patch, deployed since July on Microsoft 365 gateway servers, whose defect only appeared under heavy load (IT-Connect). Three factors combined on the same day.

The sequence described by Microsoft:

  1. Teams traffic was shifted to the main gateway on Thursday at 2:07 a.m.;
  2. load increased over the working day;
  3. about 14% of capacity was already out of service because of a separate issue the day before (IT-Connect);
  4. servers saturated one after another, until more than 80% of them stopped responding in under two hours (IT-Connect).

Microsoft states that this defect does not affect other Windows deployments: its customers' computers and servers are not involved (IT-Connect).

Analysis: this is a classic cascading failure. Each element on its own was harmless; their combination, on infrastructure shared by hundreds of millions of users, caused the outage. The lesson applies to every business: a single provider, however robust, remains a single point of failure.

Are emails sent during the outage lost?

As a rule, no: when a receiving mail server does not respond, the sending server keeps the message and retries, often for several days, before giving up. The SMTP standard recommends not giving up for at least four to five days (RFC 5321, IETF).

In practice:

  • incoming emails were delayed, then delivered once Exchange Online was back;
  • outgoing emails written in Outlook stayed in the outbox and were sent when the service returned;
  • a sender may have received a delay notice, or even a rejection if their server gives up sooner than the standard;
  • messages sent from a phone depend on the app: check that they appear in your sent items.

Pro tip: after an outage, ask your key contacts whether they received a non-delivery report. A lost quote or follow-up often costs more than the outage itself.

What does this outage change for your business?

It is a reminder that email hosted with a single provider can stop for a whole day, and that no contract replaces a backup plan. For a small business, a day without email or calendar means unsent quotes, missed appointments and unanswered customers.

Key points:

  • availability is never total, even with the largest providers;
  • dependency is often broader than you think: email, calendar, documents, video calls and sign-in rely on the same ecosystem;
  • administrators are helpless when the admin portal itself is disrupted;
  • contractual compensation stays small compared with the real loss of business.

Analysis: the question is not whether a provider will fail again, but when, and what your team will be able to do in the meantime.

What should you do during an email outage?

During the outage, first confirm that it comes from the provider, alert your teams and customers through another channel, and work from local copies until the service returns. A procedure written in advance saves precious hours.

The steps:

  1. confirm the outage on your provider's status page and on an outage-reporting service before touching your settings;
  2. do not change your MX records or passwords in a rush: you could make things worse;
  3. alert your teams through an independent channel (text message, a messaging app from another vendor, phone);
  4. inform key customers, for example with a notice on your website or a backup address;
  5. work from Outlook's local cache: messages already synced remain readable offline;
  6. list urgent messages to send, so you can handle them as soon as the service is back;
  7. check what was sent once the service is restored: outbox, non-delivery reports, appointments.

How do you avoid being stuck during the next outage?

You cannot prevent a provider outage, but you can limit its impact with four measures: keep control of your domain name, have a backup channel, keep independent copies and write a procedure. It is business continuity scaled to a small company.

MeasureWhat it protectsEffort
Domain name and DNS zone with a separate providerYour ability to redirect email to another serviceLow
Backup mailboxes with another providerAn address that stays reachable during the outageLow to medium
Outlook local cache enabled on computersReading emails already receivedLow
Backup of mailboxes and calendars outside MicrosoftData recovery after a serious incidentMedium
Independent team channel (text, other messaging app)Coordination during the outageLow
Written and tested procedureA fast reaction, without improvisingLow

Good practices to set up now:

  • keep your domain name and its DNS zone outside the Microsoft ecosystem: in a long outage, the DNS zone, through MX records, is what lets you redirect mail;
  • choose reasonable TTLs on MX records, so a planned switch propagates in hours rather than days;
  • prepare a backup mailbox for critical addresses (management, support, accounting) with another provider;
  • back up your Microsoft 365 data with a third-party tool: the provider ensures the availability of its service, not the long-term retention of your data;
  • document who does what during an outage and test the procedure once a year.

At Wayhost, domain DNS management lets you edit your MX, CNAME and TXT records yourself, with DNSSEC included (checked on November 16, 2026). Wayhost professional email, with anti-spam protection, can serve as your main email or as a backup on your own domain (checked on November 16, 2026). To set up email on your domain properly, our professional email guide walks through the steps.

Pro tip: an MX switch cannot be improvised during an outage. Prepare it in advance, with the backup provider's SPF and DKIM records already published, so your emails do not land in spam on the day you need it.

Should you leave Microsoft 365 after this outage?

Not necessarily: a single outage does not justify a migration, but it should push you to reduce your dependence on a single provider. The right decision depends on your usage, your costs and your data constraints.

Three realistic options:

  • stay on Microsoft 365 with a backup plan: independent domain and DNS, third-party backups, backup mailboxes;
  • spread services: email with one provider, documents and video calls with another;
  • migrate to an alternative, if data sovereignty or cost also weigh in.

Our article Microsoft 365 alternative compares the possible solutions and what to check before switching. To self-host some tools, such as a file server or video conferencing, a Wayhost VPS offers full root access and snapshots (checked on November 16, 2026).

What should you expect from Microsoft's final report?

Microsoft has announced a final report for November 20, 2026, which is expected to detail the cause, the timeline and the corrective measures (IT-Connect). What follows is about an announcement: its exact content is not yet known.

What to look for:

  • corrective measures on gateway servers and on patch management;
  • changes in load balancing between gateways, which triggered the cascade;
  • any service credits provided for in contracts;
  • recommendations for administrators, if any.

We will update this article once the final report is published.

Frequently asked questions

When did the Microsoft 365 outage happen?

It started on Thursday, November 12, 2026 at around 5:20 p.m. Paris time. Exchange Online came back on Friday, November 13 in the late afternoon, according to the preliminary report. Microsoft announced that all services were restored on Saturday, November 14.

Was the Microsoft outage a cyberattack?

No, Microsoft ruled out a cyberattack. The preliminary report points to a faulty Windows patch on its gateway servers. The defect only appeared under heavy load.

Did I lose emails during the Outlook outage?

Generally not, because sending servers retry for several days. Messages arrived late after the recovery. Still, check your outbox and any non-delivery reports.

How can I tell whether Outlook is down or my computer is at fault?

Check the Microsoft 365 status page or an outage-reporting service. If other users report the same problem at the same time, the fault lies with the service. Otherwise, check your connection, your password and whether Outlook is up to date.

How can I keep receiving email during an outage?

Prepare a backup mailbox in advance with another provider, on your own domain name. Keep the DNS zone outside your main provider's ecosystem. You can then redirect mail if the outage drags on.

Should you back up Microsoft 365 data?

Yes, an independent backup is recommended. The provider ensures the availability of its service, not necessarily the long-term restoration of your data. A third-party backup tool also protects against accidental deletion or account compromise.

Will Microsoft compensate businesses?

Microsoft 365 contracts provide service credits when the promised availability is not met. They usually have to be requested by the administrator. The final report, expected on November 20, should clarify what comes next.

Key takeaways

  • Microsoft 365 suffered a global outage from November 12, 2026, led by Exchange Online and Outlook.
  • The stated cause is a faulty Windows patch on gateway servers, with no cyberattack.
  • Emails were delayed, rarely lost, thanks to retries by sending servers.
  • Keeping control of your domain and DNS zone is the first continuity measure.
  • A backup mailbox, third-party backups and a written procedure limit the impact of the next outage.

To keep control of your domain and have a backup mailbox, discover Wayhost professional email.

Article written by Mouhamed BANKOLE, CEO at ITNET Technologies.

Have a specific question?

Our step-by-step articles answer the most common questions.

Knowledge base