← Back to blog
#Nube#Microsoft 365#Continuidad#Ciberseguridad#Pymes

Microsoft 365 Went Down on November 12: What Happened and How to Build a Continuity Plan

Office worker with hands on his head in front of his laptop, worried

Updated on November 17, 2026 with the cause Microsoft acknowledged afterwards; the original note described what was known on November 12.

On Thursday, November 12, 2026, Microsoft 365 suffered an outage that took Outlook, Teams and other services offline, mainly in the United States, with effects in other regions. According to France 24, Downdetector logged more than 130,000 reports for Outlook, about 46,000 for Microsoft 365 and nearly 3,000 for Teams. If your company runs email and meetings in the cloud, the useful question is not "why did it fail?" but "what do we do when it happens again?"

What happened on November 12

  • Affected services: Outlook and Exchange Online, Teams and Microsoft 365 in general; media also reported problems with Copilot, SharePoint and OneDrive.
  • Downdetector figures measure user reports, not affected users: the site itself warns that the real number may vary.
  • Knock-on effects: Anthropic and OpenAI reported problems with their Microsoft 365 connectors, showing how an outage spreads to the AI tools connected to email and documents.
  • Microsoft's response: according to France 24, it paused deployments, rerouted traffic and restarted affected servers. In its last post on X that day it said it was testing a configuration change to fix a problem that made servers fail automatic health checks and become unavailable.

Update: cause and duration, with caveats

On November 17, Expansión reported, based on a preliminary Microsoft report, that the cause was a software bug introduced in July 2026 in the servers that manage connections for its cloud services: it only showed up under certain traffic conditions and internal testing didn't catch it. Microsoft clarified it was not a general Windows vulnerability. On duration, the same preliminary report puts it at 23 hours and 50 minutes according to Microsoft's records, with active impact ending on November 13. Since the report is preliminary, that figure may be adjusted in the final version.

What this means for your SME

An outage like this is rare, but it happens even to the biggest providers. For an SME the cost is not the downed service but having no fallback plan: appointments that aren't confirmed, quotes that don't go out, teams that can't meet. What we said before about power cuts applies equally: continuity is prepared before the incident.

A continuity plan in one hour

  1. Define a backup communication channel. An emergency WhatsApp group, a phone line or a second video-call service. Everyone should know which one before they need it.
  2. Write down who notifies customers and with what message. Prepare a short template: "We're having an issue with our email provider; please reach us at this number."
  3. Where to check service status: the Microsoft 365 admin center shows service health. Assign someone to check it, and make sure the administrator has alternate access if the usual account is also down.
  4. Keep copies outside your provider's cloud. Contacts, critical calendar entries and key files should be backed up elsewhere. Ask your IT provider how your email is backed up, because a backup at the same provider doesn't protect you from a provider outage. More in immutable backups.
  5. Beware of opportunists. During an outage, fake "support" or "reset" emails and messages circulate. Nobody should give out a password or open links received through unverified channels.
  6. Write down the lesson. After the incident, record the cost in hours and what failed in your response, to decide whether you need a second provider or manual procedures.

How we approach it at SimCodec

At SimCodec we help companies design their continuity: cloud architecture with alternatives, backups outside the main provider, telephony and service channels that keep working if email fails, and a clear procedure for what to do and whom to call. If you want to review your plan, contact us.

Sources

← Back to blog Get a quote →