
If your inbox went strangely quiet on Thursday evening, 12 November and stayed that way into Friday, you weren’t alone. Millions of users around the world lost access to Outlook email, Teams meeting tools and other everyday office essentials as the disruption spread.
It was a frustrating day for all businesses, including some of our own clients. Now that Microsoft has published its full post-incident report, here’s a clear look at what happened, what worked and what you can do to keep your business running if something like this happens again.
What actually happened
First, the most important point: this was not a cyberattack. Microsoft confirmed it was a technical issue, unrelated to cyber activity or AI agents.
The post-incident report shows there was no single point of failure. Instead, three separate issues lined up at the same time:
-
A previously undetected software defect in the servers behind Microsoft’s networking gateway.
-
About 14% of that gateway’s server capacity was already offline because of an unrelated incident the day before.
-
Around 15 hours before the outage, Teams traffic was moved onto the same primary gateway that also handles Exchange Online, adding extra load.
None of these would have caused a global outage alone. Together they did. That’s useful for any IT leader to understand: modern resilience planning is about how several small issues can line up, not only about single failures.
What held up
The headlines focused on email, but several things worked as designed.
Redundancy kicked in where it could. Services that were able to, including Teams, OneDrive, SharePoint and the Office apps, moved away from the faulty gateway infrastructure. That’s why they came back sooner, and Microsoft says Teams chats and meetings kept working for most users throughout the outage.
Microsoft owned up quickly and kept customers informed. In any outage, the worst thing a provider can do is leave customers in the dark. Microsoft didn’t. Outlook complaints began rising at about 12:25 p.m. US Eastern time, and Microsoft posted its first public alert at 12:54 p.m., acknowledging the problem within about half an hour. From there, it kept customers updated through the Microsoft 365 Status account and the admin centre, sharing what its engineers were doing as they worked to restore capacity and stabilise the service. Once services recovered, Microsoft publicly apologised to its customers and partners, promised a full review and delivered a detailed post-incident report within days.
Owning up and communicating openly builds trust, even when things go wrong.
What is positive about this: The fix applies to everyone at once. This is one of the less obvious benefits of a cloud platform like Microsoft 365. When Microsoft’s engineers find and fix a defect like this, every customer benefits immediately, without each business patching its own servers.
Five practical steps to take now
An outage like this is a good prompt to review your own setup. Here’s what we recommend:
-
Know where to check. When something seems wrong, it helps to know whether the problem is on your side or Microsoft’s. Microsoft posts live updates on its official status page (called Service Health) and on its Microsoft 365 Status account on X (formerly Twitter). Make sure someone in your business knows where to find these updates or simply give us a call and we’ll check for you.
-
Agree on a backup communication channel. During this outage, Teams chat kept working while email was down. Decide in advance where your team should go when one channel fails, whether that’s Teams, a phone tree or something else, so nobody must improvise.
-
Use the desktop apps, not only the browser. Outlook’s desktop app keeps a local copy of your recent mail and calendar, so you can still look up an important email or meeting detail while the service is unavailable.
-
Review your Microsoft 365 backup. Microsoft keeps the platform running, but your business is responsible for protecting its own data. A dedicated Microsoft 365 backup solution adds an extra layer of protection.
-
Revisit your business continuity plan. If your team couldn’t send email for a day, what would stop? Who would you need to contact, and how? Last week made the answers clearer for many businesses, so write them down while they’re fresh.
We’re here to help
As a Microsoft Partner, we keep a close eye on service health, so you don’t have to, and we’ll always keep you informed when something affects your business. If last week’s outage raised questions about your setup, your backups or your continuity plan, get in touch with us. We’ll help you review where you stand and make sure you’re ready if it happens again.


