It's Thursday afternoon. Outlook won't load at the front desk, a Teams meeting won't connect, and someone asks the question every office asks first: is it us, or is it Microsoft? On November 12, 2026, for a lot of organizations, it was Microsoft. Here's what we know about the outage, what to do while one is happening, and how to set things up so the next one is an inconvenience rather than a lost day.
What happened
Microsoft logged its first notice for Exchange Online at 16:17 UTC on Thursday, November 12. Problem reports surged in the early afternoon Eastern time. Reuters reported that Downdetector recorded more than 130,000 Outlook problem reports around 1:27 p.m. ET, along with more than 46,000 for Microsoft 365. Microsoft first described the impact as affecting the Americas, then warned it could affect users in any region. Recovery was uneven. Microsoft reported partial recovery in some regions, but some servers it brought back became unresponsive again once traffic returned. Service continued into Friday morning, November 13, with capacity gradually stabilizing.
| Item | What was reported |
|---|---|
| Incident IDs | EX1550543 (Exchange Online) and MO1550821 (broader Microsoft 365) |
| Timeline | Began Thursday, Nov 12; continued into Friday morning, Nov 13, with capacity gradually stabilizing |
| Services affected | Outlook/Exchange Online, Teams, SharePoint, OneDrive, Copilot, Defender for Office 365 and Microsoft Graph requests for mail and calendar |
| Microsoft's explanation | Servers lost capacity after a process that sets up secure connections on each server became overwhelmed |
| Cyberattack? | Microsoft said it found no indication of malicious activity |
| Final root cause | Microsoft promised a post-incident report; check Service health in your admin center for the closure summary |
Why one outage reached so many tools
Microsoft 365 is a set of connected services, not one app. Teams, SharePoint, Copilot and Microsoft Defender all depend on Exchange Online, so problems there spread to them. Reports during the incident said Copilot might not load or reach email, calendar and files. Defender for Office 365 Safe Links might be unable to verify URLs. And Microsoft Graph requests for mail, calendar and contacts could time out, which means any script, scanner or line-of-business integration that reads a mailbox would fail too. That's why some offices saw failures well beyond email: automated reports didn't send, scan-to-email stopped, and notifications from other systems never arrived.
What to do while an outage is happening
- 1
Confirm the scope
Check Health > Service health in the Microsoft 365 admin center. If you can't sign in, use Microsoft's public service status page.
- 2
Tell staff once, clearly
Use a channel that doesn't run on Microsoft 365: phone tree, text message or a posted notice.
- 3
Avoid disruptive fixes
Don't reinstall Office, reset profiles or mass-reset passwords for a problem on Microsoft's side.
- 4
Switch to downtime procedures
Use phones, printed schedules and approved paper forms for anything time-sensitive.
- 5
Watch for lures
Attackers often send fake 'service restored' or 'reset your account' messages during big outages.
- 6
Recover and reconcile
When service returns, enter paper records, check mail flow and integrations, and read Microsoft's closure summary.
Link checking may be degraded
During this incident, Safe Links in Defender for Office 365 might have been unable to verify URLs. If your email security relies on it, tell staff to be extra careful with links in Outlook and Teams while an outage is ongoing and for a while after it ends.
Don't chase unverified workarounds
Switching to Outlook on the web or another Microsoft client was not a verified workaround for this outage. When the problem is on the provider's side, time spent troubleshooting local PCs is usually better spent running your downtime plan.
Building resilience before the next one
Every cloud platform has outages sometimes. Leaving Microsoft 365 isn't the practical answer. Planning so that a few hours without it doesn't stop your core work is. Most of what helps is low-cost and procedural.
- A communication channel for staff that doesn't depend on Microsoft 365
- An offline or printed contact list for staff, key vendors and today's appointments
- Service health alerts sent to more than one person (the Microsoft 365 Admin mobile app supports push notifications)
- A list of systems that rely on Microsoft 365 email or Graph (scanners, EHR or practice-management notifications, scripts)
- Written downtime procedures for scheduling, intake and billing, with approved paper forms
- A clear owner who decides when to switch to downtime mode and when to switch back
- A separate backup of Microsoft 365 data, kept apart from your plans for keeping work running
- At least one tabletop test a year, with the plan updated afterward
An outage and a data-loss event call for different responses, and many organizations plan for one but not the other.
| Service outage | Data loss event | |
|---|---|---|
| What's wrong | You can't reach the service; your data is still there | Data is deleted, corrupted or encrypted |
| Who fixes the root problem | The provider (Microsoft) | Your organization and your IT team |
| What helps most | Downtime procedures and alternate communication | Tested, separate backups and a recovery plan |
| Would a backup help? | Rarely, since the platform itself is unavailable | Yes, it's the main recovery tool |
For healthcare and behavioral health organizations
Clinics also have a regulatory reason to plan for outages. The HIPAA Security Rule's contingency plan standard (45 CFR 164.308(a)(7)) includes a required emergency mode operation plan. HHS guidance explains that when an organization is operating in emergency mode because of a technical failure, the security processes that protect electronic protected health information must still be maintained.
In practice, that means deciding in advance how staff will communicate about clients and patients when email and Teams are down. Be explicit about what is not allowed. A quick text from a personal phone or a forward to a personal email account can create a bigger problem than the outage itself. Paper downtime forms should be stored securely and entered into the record once systems return. Every organization is different, so have a qualified compliance or legal professional review your contingency plan. A plan supports compliance but doesn't guarantee it.
Frequently asked questions
Was the November 2026 Microsoft 365 outage a cyberattack?
Microsoft said it found no indication of malicious activity. Its explanation was that servers lost capacity after a process that sets up secure connections became overwhelmed. Check Microsoft's post-incident report for the final root cause.
Where do I find Microsoft's official explanation?
In the Microsoft 365 admin center under Health > Service health. Look up EX1550543 and MO1550821. Microsoft provides incident closure summaries there, with root cause, start and end times, and next steps.
Would a Microsoft 365 backup have kept us working?
Generally not. A backup protects against data loss. It doesn't give you a working email or Teams service while the platform is down. Downtime procedures and alternate communication do that.
Do small practices really need an emergency mode plan?
The HIPAA Security Rule's contingency plan standard applies to covered entities and business associates, and the emergency mode operation plan is a required part of it. A qualified professional can help you scale it to your organization.
If you'd like help building an outage plan for your business or clinic that you can actually use, contact Charlie's Nerds through our contact page.
How Charlie's Nerds can help
Microsoft Cloud & Microsoft 365
Licensing, security, backup, and support for Microsoft 365.
Learn more โManaged IT Services
24/7 monitoring and help desk so outages become a plan, not a scramble.
Learn more โCybersecurity & HIPAA
Contingency planning and safeguards for regulated organizations.
Learn more โQuestions about your own IT setup?
Talk to a Charlie's Nerds engineer. No pressure, no jargon.