On Thursday, 12 November 2026, one of the largest cloud outages in recent years began. Exchange Online failed first, and soon much of Microsoft 365 was affected: Outlook, Teams, SharePoint, Copilot and Intune. Only on Saturday, 14 November, did Microsoft report that all services and regions were restored. The outage therefore lasted well over 24 hours.
What happened
According to Microsoft, several servers in the background had unexpectedly become unavailable. The remaining servers could not keep up with the load. A restart did not help at first, because the servers failed again as soon as traffic returned. Microsoft points to an earlier network change as the trigger, which disrupted an older capacity upgrade. The outage was fixed with a patch to an authentication and routing component.
Microsoft found no indication of an attack, and AI was not the cause. It was a technical fault in its own operations.
The scale
On the outage platform Downdetector, more than 7.4 million reports were logged worldwide. Offices were not the only ones affected:
- The UK’s National Health Service had to fall back on alternative systems.
- Airlines such as Air India, IndiGo and Akasa Air reported email support problems.
- Financial institutions were affected, and one firm in Taiwan confirmed trades by fax for a while.
For many businesses this meant: no email, no calendar, no files, and nothing to do but wait. Control lay entirely with Microsoft.
Why one vendor paralyses so many
Microsoft 365 is convenient because everything comes from one place. That is exactly the problem during an outage. Email, chat, files and sign-in all depend on the same platform. If a central part fails, everything often stops at once. And the affected business can do nothing. It sees the same status page as everyone else and waits for Microsoft to roll out the fix.
Then there is the sheer size. When millions of companies use the same cloud, every error immediately becomes a global event. This is not a one-off accident. Back in January 2026 there was already a Microsoft 365 outage lasting hours, and such incidents keep returning.
The advantage of self-operated Zimbra
Zimbra is a platform for email, calendars and contacts that runs on your own servers in Switzerland. During a worldwide outage the decisive difference shows:
- No shared global point of failure. Your mail server does not depend on Microsoft’s infrastructure. An outage in a Microsoft region does not affect you.
- In an incident, someone can act. If something goes wrong, we step in directly instead of waiting for a corporation. You have a contact who knows the system and has access.
- Manageable risk. A problem on your server affects only your business and can be fixed in a targeted way. It is not a global event with millions of victims in which your request gets lost.
- Independence. You decide on updates, maintenance windows and configuration, not a vendor rolling out a change worldwide.
Being honest: your own servers fail too
Your own mail server is no guarantee against disruption. Hardware, power or a misconfiguration can hit it as well. The difference lies elsewhere: the risk is manageable, it affects only you, and someone with access can fix it. That is why sound operations include a second line, an emergency plan and verified backups. More on this in our article on the IT emergency plan.
There is no such thing as zero outage risk. The question is whether you can act in an emergency or only wait.
What we recommend
- Review your dependency. Which parts of your business stop if Microsoft 365 fails? Often email, telephony, files and sign-in at the same time.
- Decouple email. Email and calendars in particular move well to your own server in Switzerland. That reduces the dependency the most.
- Define a fallback route. A second channel for urgent messages, and clear responsibilities for who does what during an outage.
The outage is also a data protection matter: those who run their own email keep control over content and metadata. More on this in our article on the Microsoft 365 data protection clause.
We run Zimbra in Switzerland
A BOT is a Zimbra partner and runs Zimbra environments for SMEs on servers in Switzerland, with spam filtering, archiving and backup. We review with you whether decoupling from Microsoft 365 makes sense and migrate your mailboxes outside business hours. More about the product under Zimbra and about the service under email security.
Frequently asked questions
Would Zimbra have protected us from this outage?
From this particular outage, yes, because your mail server does not depend on Microsoft’s infrastructure. Zimbra does not rule out an outage of your own for another reason, but the risk is manageable and fixable.
Do we have to leave Microsoft 365 entirely?
No. Many SMEs move only email and calendars to Zimbra and keep using Office on the desktop. That reduces the dependency without changing everything.
How quickly are you reachable in an incident?
As a fixed contact with access to your system, we act directly instead of waiting for a global vendor. That is the core of the difference.
Isn’t your own server more work?
We handle operations: updates, monitoring and backups. For you, daily work changes little, Outlook and your smartphone work as before.



