A nearly 24-hour Microsoft 365 outage: lessons for small and medium-sized companies

From Thursday 12 November at 17:20 Belgrade time until around 17:10 on Friday 13 November, Microsoft 365 suffered one of its longest outages in years. For almost 24 hours users worldwide could not open their Outlook mailboxes, and mail was delayed. Teams, SharePoint and OneDrive recovered earlier because they could switch to alternative infrastructure, but Exchange Online could not.
What caused it
- According to the preliminary report Microsoft shared with administrators, a bug was introduced in July through an update to the Microsoft 365 networking gateway servers and stayed dormant for more than three months.
- The trigger was extra traffic after Teams automatically failed over to the networking infrastructure used by Exchange Online about 15 hours earlier, while about 14% of capacity was already offline because of an unrelated issue.
- In less than two hours the defect spread across the fleet, and at its worst more than 80% of servers were unresponsive.
- Microsoft says its lab testing did not catch the bug because it uses a different traffic mix and less powerful hardware than production. A final report is expected this week.
Why it matters
Most small and medium-sized companies in Serbia spend the whole day in one suite: email, meetings, documents and calendars all live in the same place. When that suite stops, it is not just email that stops but client communication, quotes and deadlines. This outage was not an attack but a supplier-side bug, exactly the kind of failure no company can prevent on its own. It can only prepare.
What to do now
- agree on a backup channel for the team (phone, SMS or a group in another app) and keep a client contact list that does not live only in Outlook;
- turn on Outlook cached mode and sync key OneDrive folders so the most important documents are available offline;
- make sure at least one person knows where the Service health page in the Microsoft 365 admin center is and checks it before the whole company starts restarting computers;
- check that you have a backup of email and documents outside Microsoft 365 itself;
- write a one-page plan: who informs clients, through which channel, and what happens with urgent deadlines.
We help companies set up their tools and processes so work does not stop when one service goes down. See AI integration and business process optimisation or get in touch.
Sources
- BleepingComputer: Microsoft says months-old bug caused global Microsoft 365 outage (16 Nov 2026)
- Petri: Microsoft Explains Causes of Microsoft 365 Outage (16 Nov 2026)
- Microsoft Learn: How to check Microsoft 365 service health
Cover photo: Crew, Wikimedia Commons, CC0.