InsightsOperations and lifecycle

When Microsoft 365 went down: what businesses can learn

On November 12 and 13, email, Teams, and several other Microsoft 365 services went down for businesses around the world. No one could have prevented the incident, but there was a big difference in how well prepared businesses were. Here is what happened, how we handled it, and what you can take away from it.

A grid of dark blue cubes with one missing

What happened?

On Thursday, November 12, users began having trouble reaching their email in Exchange Online. Over the afternoon the issue spread, and Teams, SharePoint, OneDrive, Copilot, and several security services were eventually affected as well. The problems continued through the night and into Friday, and for many businesses that meant two working days without normal access to email and collaboration tools.

According to Microsoft, the incident was caused by an issue from an earlier network capacity upgrade that surfaced after a later network change. It was not a cyberattack. Services were gradually restored on Friday, and in the early hours of Saturday, November 14, Microsoft reported that everything was back to normal and that the email backlog had been delivered. In total, the incident lasted about 30 hours, and Microsoft has announced a full post-incident report.

The hour-by-hour timeline is in the article Microsoft 365 outage, November 12–13.

How we handled it

When email and Teams go down at the same time, the usual channels for informing employees and customers disappear with them. That's why we keep backup channels that don't depend on Microsoft, and they proved their worth this time.

We followed Microsoft's updates continuously from the start of the incident and sent our customers information about what was happening and what to expect. On Friday morning, we also called every one of our customers to give a status update, answer questions, and make sure no one was stuck with problems they couldn't explain.

The fault was on Microsoft's side, and there was nothing we or our customers could do to fix it. But we could make sure no one was left on their own wondering what was going on. That is an important part of our job as an IT partner, even when the problem is outside our control.

Eight lessons for businesses

1. The cloud isn't always up

Microsoft 365 is highly reliable, but no cloud service has 100% uptime. Nearly every business today depends entirely on email and Teams, yet few have thought through what they will do the day those services stop working. That belongs in your contingency planning, alongside power outages and fire.

2. Have a communication plan that doesn't depend on Microsoft

If email and Teams are down, how do you reach your employees? Keep an up-to-date phone list outside Microsoft 365, and decide in advance which channel to use, such as text messages or a dedicated group in another messaging app.

3. Give customer service a backup channel

Many businesses receive customer inquiries by email. If email goes down, customers may feel they aren't being heard. A phone number and a contact form on your website that doesn't rely on email are simple fallbacks.

4. Know where to find current status

Microsoft posted updates on its own status page, in the Microsoft 365 admin center, and on the @MSFT365Status account on X. At times, even Microsoft's own status pages were hard to reach. It helps to know several sources ahead of time, and to have an IT partner watching on your behalf.

Microsoft's public status page

How to check Microsoft 365 service health

Microsoft 365 Status on X

5. Email is rarely lost

Email sent while Exchange Online is down normally stays queued with the sender and is delivered once the service is back. In a long outage some messages can still drop out, so it's worth checking afterward that important inquiries actually arrived.

6. Local copies make it easier to keep working

Users who had Outlook set up with a local copy of their mailbox could still read older email, and files synced with OneDrive were available on the device. Also think about where your contingency plans and contact lists are stored. If they live only in the cloud, they are unavailable exactly when you need them.

7. Watch closely for scam attempts

Scammers often use major incidents as a pretext for phishing, such as emails asking you to "reactivate your account" or "confirm your sign-in" after the outage. Microsoft never asks for this by email. Remind your employees.

8. Use the incident to update your contingency plan

Review which tasks came to a halt, what worked, and what should be done differently next time. When Microsoft publishes its post-incident report, that is worth reading too.

Good preparedness is about preparation

The November incident shows that even the largest cloud providers can run into trouble. No business can prevent that, but every business can be prepared for it. With a few simple steps, a long outage becomes an annoyance instead of a crisis.

Want to review how well prepared your business is for next time? Contact us, and we'll go through it together.

How we can help

Wondering what this means for your organization? Let's talk.

Request a meeting →

Read next

All articles →