Microsoft 365 Went Down. Could Your Customers Still Reach You?

What happened
Update, 15 November: Microsoft marked the incident resolved on Friday, 13 November, at about 12:10pm Eastern Caribbean time, after about 24 hours, and finished restoring remaining customers by Saturday. It published its preliminary incident report on 15 November and has promised a final one within five business days. We'll cover what it found in a follow-up.
Correction, 17 November: Microsoft's preliminary incident report puts the outage at about 24 hours, from 12:20pm Eastern Caribbean time on 12 November, when its engineers were first alerted, to 12:10pm on 13 November. We originally reported about 30 hours.
Problems began at about 12:20pm Eastern Caribbean time on Thursday, 12 November 2026, according to Microsoft's preliminary incident report, and became widespread by about 2pm, when outage reports surged. According to Microsoft's status updates and news reports:
- Exchange Online email stopped flowing for many businesses. Outlook users couldn't send, receive or, in some cases, open their inboxes.
- Teams, SharePoint, Copilot, Planner, To Do and Defender were also disrupted.
- Intune and the Microsoft 365 admin centre went down, so IT teams couldn't use Microsoft's own tools to diagnose the problem.
- Downdetector logged nearly 130,000 Outlook problem reports at the peak, according to Reuters figures.
- The impact reached beyond the US. Microsoft warned that users in any region could be affected, and Bermuda's Royal Gazette reported disruption on the island.
Microsoft said servers were failing automated health checks and dropping out of service, which pushed extra load onto the servers that were still running. It paused all deployments, began bringing servers back in stages, and saw some of them fail again as soon as traffic returned.
Overnight, Microsoft's early findings pointed to a process that sets up secure connections on its servers becoming overwhelmed. It rolled back a recent network configuration change whose timing matched the start of the outage, and said it found no sign of malicious activity. It then began rolling out a patch region by region, starting with regions entering their business day, and extended email timeouts to 48 hours so that delayed mail would still be delivered.
As of 11:52am Eastern Caribbean time on Friday, 13 November, Microsoft said it was still working on residual impact and monitoring to confirm that recovery was holding. It had not yet declared the outage resolved.
New York City's Emergency Management Department told residents that email to city agencies might be delayed, and to use other ways to get in touch.
Microsoft's own updates on X: investigating Exchange Online access · servers unavailable under elevated load · early stabilisation and 48-hour email timeout
The problem wasn't Microsoft. It was having one door.
Every provider has bad days. Microsoft runs some of the most reliable infrastructure in the world, and it still lost email for most of a day.
The businesses that felt it most were the ones where every customer conversation ran through one channel. If customers can only reach you by email, an email outage isn't an IT problem. It's a shop with the shutters down that nobody told you about.
And your customers can't see the outage. A customer who emails for a quote at 3pm and hears nothing by 6pm doesn't think "Microsoft must be down." They think you're slow, and they message the next supplier. With mail now being held for up to 48 hours, some of those enquiries will only reach your inbox after the customer has already moved on.
Five ways to keep a second door open
1. Find your single points of failure. List how customers reach you (email, phone, WhatsApp, website form) and which provider each one depends on. You may find that your email, your website form and your staff's chat all run through the same company.
2. Give customers a second channel on different infrastructure. A WhatsApp line on the official WhatsApp Business Platform runs on Meta's systems, not Microsoft's. A direct phone line works too. The point is that two channels on different providers rarely fail at the same time.
3. Don't let customer conversations live only in staff inboxes. If your team only finds out about customer messages through email notifications, an email outage hides those messages as well. In Zandolie, WhatsApp conversations live in a team inbox in the browser at app.zandolie.ai, separate from anyone's email, and the AI agent keeps answering routine questions while your team works.
4. Have a way to tell customers what's going on. Keep a short holding message ready, and somewhere to post it that doesn't depend on the system that's down: a banner on your website or a post on your social pages, pointing customers to your other channel.
5. Practise the switch. Decide in advance who checks the backup channel when the main one fails, and make sure they can sign in to it from their phone.
Two channels, not a perfect one
To be fair, WhatsApp has had outages too, and so has every other platform. No provider can promise it will never go down.
What you can control is whether one provider's bad day becomes your business's bad day. On Thursday afternoon and into Friday, the businesses with a second door open kept talking to their customers.
Coming next
Part 2, now published, looks at what kept running on our own systems during the outage, and what we're changing. Part 3 will cover Microsoft's full incident report once it's published.
See what Zandolie can do for your customers.
Get startedSources
- The Register: Microsoft struggling to fix massive cloud outage
- Al Jazeera: Microsoft outage hits tens of thousands of users
- ABC News: Microsoft Outlook outage stretches on for hours
- Digital Trends: Outlook is restoring slowly
- Cloud Admin Hub: MO1550821 incident timeline
- Windows Forum: Microsoft rolls out patch after initial fixes fail
- Windows Forum: outage reaches Bermuda and the US
- Windows Forum: network change cause and recovery checks
- Microsoft preliminary post-incident report (via 365Fanatic)
