What To Do When Microsoft 365 Is Down: A Business Playbook For 2027

Last updated: November 14, 2026

When Microsoft 365 is down, first confirm it is Microsoft and not you, then move urgent communication to a channel that does not depend on Microsoft, tell staff and customers what is happening, and avoid making changes to your tenant while Microsoft fixes it. Mail sent to you is usually queued and delivered later. If you cannot afford a day without email, the long-term fix is an email continuity service plus an independent backup.

This playbook was written after the Microsoft 365 outage that began on November 12, 2026, when Exchange Online servers failed automated health checks and Outlook, Teams, SharePoint, Copilot and other services were disrupted worldwide into November 14. Microsoft said it was not a cyberattack. It was a reminder that even the biggest cloud can fail for a day.

Quick Checklist

• Confirm the outage on Microsoft’s public status page and social channels, not only in the admin center.
• Stop troubleshooting your own devices once Microsoft confirms an incident. Do not reset passwords or reinstall Outlook.
• Switch urgent communication to phone, SMS, a non-Microsoft chat tool or an email continuity inbox.
• Tell people: post an internal notice and, if customers are affected, a short public update.
• Freeze tenant changes until Microsoft declares the incident resolved.
• Track the incident ID and timestamps for your records and any contractual claims.
• After recovery, check delayed mail, confirm sync, read Microsoft’s post-incident report and update your plan.

Step 1: Confirm It Is Microsoft, Not You

Check the Microsoft 365 public status page at status.cloud.microsoft and the Microsoft 365 Status account on X. Administrators should also look at Service health in the Microsoft 365 admin center, but during large incidents the admin center itself can be slow or unreachable, which is why Microsoft posts updates on its public channels too. Note the incident IDs. In November 2026 they were EX1550543 for Exchange Online and MO1550821 for the wider Microsoft 365 suite.

Outage trackers such as Downdetector are useful for a quick read on whether others see the same thing, but treat them as signals, not confirmation. If only one office or one user is affected, look at your own network, identity provider or device first.

Step 2: Keep The Business Talking

The most painful part of a Microsoft 365 outage is that email and Teams fail together, so the channel you would normally use to explain the outage is the one that is down. Decide now which channels you will use instead:

• Phone and SMS for urgent internal and customer contact. Keep an up-to-date phone list somewhere outside Microsoft 365.
• A second chat tool such as Slack, Google Chat or WhatsApp for a small crisis group.
• An email continuity inbox if you have one. Services such as Mimecast, Proofpoint Essentials and Hornetsecurity give users a temporary inbox while Microsoft is down. See our list of email continuity services for Microsoft 365.
• A status page hosted outside Microsoft for staff and customers. See our list of status page tools.

Step 3: What Happens To Email Sent To You?

During most Exchange Online incidents, inbound email is not lost. Microsoft’s own systems and the sending mail servers queue messages and keep retrying, so mail usually arrives late rather than never. In November 2026, Microsoft reported that delayed mail was being delivered as queues returned to normal. Very long outages can push some senders past their retry limits, and those senders receive a bounce notice, so after a long incident it is worth asking key partners whether anything bounced.

Outbound mail is different. If Outlook cannot connect, nothing leaves until service returns, unless you have a continuity service that sends on your behalf.

Step 4: What IT Admins Should And Should Not Do

Do

• Post a short internal notice with what is down, what still works and when the next update will come.
• Follow the Microsoft incident and record timestamps, symptoms and business impact.
• Activate email continuity if you have it, and tell users how to reach it.
• Open a support case if you see symptoms Microsoft has not listed, so your tenant is linked to the incident.

Don’t

• Do not mass-reset passwords, re-provision mailboxes or change mail flow rules while Microsoft is still fixing the problem. Changes made mid-incident are hard to unwind.
• Do not tell users to delete and re-add Outlook profiles unless Microsoft recommends it.
• Do not move your MX records to an untested provider in a hurry. Unplanned DNS changes can cause more lost mail than the outage itself.

Step 5: Tell Customers What They Need To Know

If customers email you for orders, support or legal deadlines, post a short notice on your website and social channels: email may be delayed, here is a phone number or alternative address, and we will confirm receipt once service returns. Keep it factual and avoid blaming the vendor. Customers care about what you will do, not whose fault it was.

Timeline Of The November 2026 Microsoft 365 Outage

When (UTC)	What Happened
Nov 12, 16:17	Exchange Online incident EX1550543 begins; users cannot connect to mailboxes
Nov 12, 18:26	Broader Microsoft 365 incident MO1550821 opens as Teams, SharePoint, Copilot and others are affected
Nov 12, 19:18	Microsoft says load is shifting because many servers are unexpectedly unavailable, not because of extra traffic
Nov 13	Microsoft says a process that sets up secure connections is overwhelmed, reverts a recent network change, and reports no evidence of malicious activity
Nov 14	Most users can reach mailboxes again and delayed mail is being delivered; a post-incident report is promised

How To Prepare For The Next Outage

You cannot stop Microsoft from going down, but you can decide how much it hurts. These are the four layers we recommend:

• Email continuity so mail keeps flowing during an outage. See email continuity services.
• Independent backup stored outside Microsoft so you can read and restore data. See Microsoft 365 backup solutions.
• A written communication plan with phone lists and a backup chat channel kept outside Microsoft 365.
• Someone accountable: an internal owner or a managed IT provider who has rehearsed the plan. See our lists of Microsoft 365 consultants in the US, business continuity consulting firms and, for local help, managed IT services companies in Kansas City.

How We Researched This Guide

We built this playbook from Microsoft’s public incident updates for EX1550543 and MO1550821, coverage of the outage by security and IT publications, and vendor status pages from continuity providers during the event, checked on November 13 and 14, 2026. See our research and ranking method.

Frequently Asked Questions

How do I check if Microsoft 365 is down?

Check the Microsoft 365 public status page at status.cloud.microsoft, the Microsoft 365 Status account on X, and Service health in the Microsoft 365 admin center. Outage trackers like Downdetector can confirm others are affected.

Will I lose emails when Outlook is down?

Usually not. Inbound mail is queued and retried, so it arrives late. Very long outages can cause some senders to give up and send a bounce notice, so check with key contacts afterward.

What caused the November 2026 Microsoft 365 outage?

Microsoft said Exchange Online servers failed automated health checks, a process that sets up secure connections became overwhelmed, and it reverted a recent network change. It said there was no evidence of a cyberattack and promised a full post-incident report.

Can I keep sending email when Microsoft 365 is down?

Only if you have an email continuity service in front of Microsoft 365, which gives users a temporary inbox to send and receive until Microsoft recovers.

Does Microsoft give credits for outages?

Microsoft 365 business plans carry a financially backed uptime service level agreement. If monthly uptime falls below the commitment, eligible customers can submit a claim for service credits through the admin center within the time limit set in the agreement.

Conclusion

When Microsoft 365 goes down, confirm it, move urgent conversations to another channel, communicate early, and leave your tenant alone until Microsoft finishes. Then use the experience to put continuity, backup and a written plan in place before the next one. For more, see the Microsoft Azure hub and the Cybersecurity And IT Services hub.