Microsoft 365 Outage: When Outlook Goes Down, What's Your Plan?
At 12:54 PM ET on Thursday, November 12th, 2026, Microsoft began investigating reports that users could not reach their Exchange Online mailboxes, first in the Americas. Thirteen minutes later it warned that the issue could affect Microsoft 365 connectivity "for users in any region." Microsoft is tracking it as EX1550543 and MO1550821 in the Microsoft 365 admin center. (Microsoft 365 Status) Users could not open mail in Outlook on the web, Outlook desktop, or phone mail apps, and email delivery was delayed. On Friday, November 13th at 1:05 PM ET, Microsoft confirmed the cause: "The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change." It said this was "a technical issue not related to cyber," that it had "addressed the underlying issue," and that it was seeing "broad recovery and stability across our services." (Microsoft 365 Status) As of Microsoft's 3:02 PM ET update, it was "still draining queued messages and rebalancing traffic," so sign-in can recover before mail delivery fully catches up. (Microsoft 365 Service Health Status)
This is a field note from how we work. When we run a Phase 1 Regulatory Discovery for a medical group, a CPA firm, or a defense contractor, one of the first questions we ask is simple: what stops when email stops? The answer is almost always longer than people expect, and the risk usually isn't the outage itself. It's what people do to get around it.
Watch the 60-Second Briefing: Watch our narrated YouTube Short on the Microsoft 365 outage and what your email backup plan should cover, on YouTube (@emrynetworks).
What should regulated businesses take away from the Microsoft 365 outage?
A cloud provider outage is an operations event that can turn into a compliance event. Microsoft says this one was a technical issue, not a cyberattack. But the hours without email are when staff send patient files from personal accounts, approve payments without a call-back, and skip the steps your policies depend on.
- Who is affected: any business on Microsoft 365 or Outlook.com whose mailboxes run on Exchange Online, plus features in Teams, Copilot, SharePoint, Intune, Purview, and Defender that depend on Exchange Online.
- What happened: Microsoft says an issue from an earlier network capacity upgrade surfaced after a recent network change, leaving a number of servers "unexpectedly unavailable" and straining the rest of its infrastructure.
- What to verify now: that delayed mail is arriving, that nobody moved client or patient data to personal accounts, and that every payment or bank-detail change made during the outage was confirmed by phone.
- Why it matters for compliance: HIPAA requires a contingency plan with an emergency mode operation plan, and auditors and cyber insurers ask how you keep working, and keep data protected, when a key system is down.
What happened to Microsoft 365 on November 12th, 2026?
Microsoft first reported mailbox access problems "through multiple connection methods in the Americas" at 12:54 PM ET and widened the warning to any region at 1:07 PM ET. By 2:31 PM ET it said the strain "isn't driven by an increase in traffic, but by a number of servers being unexpectedly unavailable." Through Thursday afternoon and evening, Microsoft paused all deployments, restarted servers, moved traffic, tested a different health-check method, and said at 5:09 PM ET that its actions "have not provided the anticipated relief" because "a core process on affected servers is becoming overwhelmed." (@MSFT365Status)
Was the Microsoft 365 outage a cyberattack?
No. On Friday at 1:05 PM ET Microsoft said: "This was a technical issue not related to cyber or AI / agents." It traced the incident to an issue during an earlier network capacity upgrade that surfaced after a recent network change, and said it will publish a full post-incident report once its review is complete. (Microsoft 365 Status)
What stopped working, and what kept working?
Microsoft's incident notes say Exchange Online users may be unable to reach their mailbox through Outlook on the web, Outlook desktop (MAPI), Exchange ActiveSync (most phone mail apps), or REST connections, and that mail may be delayed. Features of other Microsoft 365 services that depend on Exchange Online were also affected, including Teams calendar and meeting scheduling, Copilot access to email and files, and parts of Purview, Defender, and Intune. Microsoft also notes that most core Teams functions, including chat, calls, and meetings, were not impacted, and that files stored directly in SharePoint Online remained accessible. (Microsoft 365 Service Health Status)
What has Microsoft done so far?
On Friday at 4:24 AM ET, Microsoft said it was "seeing early stabilization and capacity improvements" and had extended the email timeout window to 48 hours "to help preserve delayed mail." (Microsoft 365 Status) By 9:17 AM ET it said email queues were "significantly reduced and approaching normal levels." At 1:05 PM ET it said it had "addressed the underlying issue" and was continuing "to restore service to remaining customers and regions." At 3:02 PM ET it said it was still draining queued messages and rebalancing traffic, and did not yet have an ETA for full recovery. (Microsoft 365 Service Health Status)
Why does an email outage become a compliance problem?
Email is rarely just email in a regulated office. It carries the codes, faxes, approvals, and alerts that other systems depend on. When it goes down, four risks show up quickly.
- Hidden dependencies. Sign-in codes sent by email, scan-to-email copiers, e-fax services that deliver to an inbox, patient or client portal notices, and security alerts can all stop or queue when the mailbox does.
- Risky workarounds. Staff with deadlines improvise. Records sent from a personal Gmail account or a text message can create a privacy problem that outlasts the outage.
- A fraud window. Confusion is good cover. Expect fake "Microsoft support" messages offering to fix your account, and payment or bank-detail changes that arrive while nobody can check the normal thread.
- Evidence. Under the HIPAA Security Rule, 45 CFR 164.308(a)(7), covered entities and business associates must have a contingency plan for an emergency or other occurrence, including "system failure," that damages systems containing electronic protected health information. The plan requires a data backup plan, a disaster recovery plan, and an emergency mode operation plan, with testing and revision as an addressable specification. (eCFR, 45 CFR 164.308) An outage like this one is a live test of that plan, and the notes you keep are your evidence.
What should you do while Microsoft 365 recovers?
This is the short checklist we walk clients through during a provider outage. None of it requires waiting on Microsoft.
- Check the right source. Use the Microsoft 365 admin center's Service health page for EX1550543 and MO1550821, or the public page at status.cloud.microsoft if the admin center won't load. Don't reinstall Outlook or reset passwords to "fix" a provider outage.
- Switch to your approved backup channel. Use the phone tree, a text alert, or a messaging tool your policy already approves. If Teams chat is working for you, Microsoft lists it as not impacted, but don't assume, and don't move protected data into a channel that isn't approved for it.
- Keep protected data in approved systems. No patient, client, or tax records go to personal email or personal phones, even "just this once."
- Call back before you pay. Confirm any new payment request or bank-detail change by calling a number you already have on file, not one in the message.
- Tell the people who depend on you. Post a short note on your website, phone greeting, or portal so patients and clients know email replies may be delayed and how to reach you.
- Keep a timeline. Write down when the outage hit you, what stopped, which workarounds you approved, and who decided. It takes ten minutes and becomes your contingency-plan evidence.
What should you check after email comes back?
Microsoft says it extended its email timeout to 48 hours to help preserve delayed mail. Once mailboxes recover, watch for messages that arrive late or out of order, check with senders about anything time-sensitive that never arrived, and review sign-in alerts for anyone who "helpfully" changed account settings during the outage. Then hold a short after-action review and update the plan while the details are fresh.
How does Standard IT differ from Defensible IT for email outages?
Standard IT waits for the status page to turn green. Defensible IT has already decided how the office keeps working, and keeps data protected, while it waits.
Standard IT says "Microsoft is down, nothing we can do." Defensible IT can show the written backup channel, the call list, the decisions made during the outage, and the date the plan was last tested.
Standard IT looks like this:
- No list of which business processes depend on email.
- Staff find their own workarounds, including personal accounts.
- No call-back rule for payment or bank-detail changes.
- No record of what happened, so nothing to show an auditor or insurer.
Defensible IT looks like this:
- An email-dependency list and an approved backup channel, kept current through compliance-first managed IT services.
- A written emergency mode plan that says what staff may and may not do while email is down.
- A call-back rule for every payment change, plus 24x7 managed detection and response watching for account takeovers dressed up as "outage fixes."
- A dated outage log and after-action review saved to your evidence folder, mapped to your IT compliance program.
How does Emry Networks help regulated businesses in Jacksonville FL, Manchester NH, and nationwide?
Emry Networks provides managed IT, cybersecurity, and IT compliance program support for medical and dental groups, CPA firms, financial advisors, defense contractors, and other regulated industries. We serve regulated SMBs nationwide from hubs in the Jacksonville, FL and Manchester, NH areas. Pricing is all-inclusive and flat monthly, so an overnight outage response does not bring a surprise invoice. Every engagement follows the 3-phase Emry Assurance Roadmap (often delivered as a 90-day blueprint):
- Phase 1 - Red Zone (Regulatory Discovery): Map every process that depends on email and Microsoft 365, find single points of failure, and document who decides what during an outage.
- Phase 2 - Transition (Security Hardening Sprint): Set up an approved backup channel, a call-back rule for payments, and an emergency mode plan your staff can actually follow.
- Phase 3 - Green Zone (Continuous Management & Drift Control): Test the plan on a schedule, update it after every real outage, and hand you dated evidence for your auditor and insurer.
Not sure what stops when your email stops? Book a 30-Minute Risk Assessment. In thirty minutes we review your email dependencies, backup channels, and contingency plan, then tell you plainly what we find. Prefer the phone? Call (603) 202-3200.
What are the next steps for your team?
Book a 30-Minute Risk Assessment to review your email continuity and contingency plan. Before that call, write down every task your office couldn't do on Thursday and every workaround someone used.
- Book a 30-Minute Risk Assessment with our team. Prefer the phone? Call (603) 202-3200.
- Take the free Compliance Readiness Assessment to see where you stand.
- Read our earlier brief on Microsoft 365 vendor access and cloud backup risk.
Frequently asked questions
What happened with the Microsoft 365 outage on November 12th, 2026?
Starting at 12:54 PM ET on November 12th, 2026, Microsoft reported that users could not reach Exchange Online mailboxes through Outlook on the web, Outlook desktop, and mobile mail apps, and that email was delayed. Microsoft warned the issue, tracked as EX1550543 and MO1550821, could affect users in any region, and it also affected Microsoft 365 features that depend on Exchange Online. On November 13th Microsoft traced it to an issue from an earlier network capacity upgrade that surfaced after a recent network change and said it had addressed the underlying issue. As of 3:02 PM ET it was still draining the remaining queued mail.
Was the Microsoft 365 outage caused by a cyberattack?
No. Microsoft says it was "a technical issue not related to cyber," introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change. It says a full post-incident report will follow once its review is complete.
Is email lost during a Microsoft 365 outage?
Not necessarily. During this incident Microsoft extended its email timeout window to 48 hours to help preserve delayed mail while queues clear. Messages may arrive late, so confirm anything time-sensitive with the sender.
Does HIPAA require a plan for email outages?
HIPAA's Security Rule (45 CFR 164.308(a)(7)) requires a contingency plan for emergencies and other occurrences, including system failure, that damage systems containing electronic protected health information. That plan includes a required emergency mode operation plan for keeping critical processes running while protecting that information. If email carries patient information, your plan should cover how you operate when email is down.
What should a small business do during an email outage?
Check Microsoft's official status page, switch to an approved backup channel, keep protected data out of personal accounts, confirm any payment change by calling a known number, tell clients how to reach you, and keep a dated timeline you can review afterward.
Next steps
See how we help businesses in your industry, or book a short call to talk through where you stand today.
Read more from our team
Explore insights on compliance and security.
Ready to strengthen your compliance?
Get hands-on assessment and guidance from our compliance experts.


