Summary
- Microsoft 365 experienced widespread disruptions on November 12.
- Outlook and other services were affected.
- Microsoft investigated servers unexpectedly becoming unavailable.
- Recovery proceeded gradually.
Disruptions affecting Outlook, Teams and other Microsoft 365 services beginning on November 12, 2026 showed how quickly everyday work can grind to a halt when a major cloud platform has trouble.
Microsoft confirmed Exchange Online connection issues that could affect users in any region. Problems also extended to other Microsoft 365 services, while the company issued a series of updates on its recovery efforts.
Which services were affected
The initial incident, EX1550543, concerned access to Exchange Online mailboxes. Users could encounter errors in Outlook on the web and when connecting through MAPI, Exchange ActiveSync or REST APIs. These are different methods of accessing the same email platform.
The broader incident, MO1550821, covered connectivity problems across more services. Provider reports listed Microsoft Teams, SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR, with later updates also mentioning Planner, To Do and Purview. Not every user necessarily experienced the same impact.
What happened inside Microsoft’s infrastructure
Microsoft determined that a large number of servers had unexpectedly become unavailable. Requests were then pushed onto the remaining servers, sharply increasing their workload. The company clarified that this was not simply caused by an overall rise in traffic.
Investigators focused on failed automated server health checks and a core process that was becoming overwhelmed. Microsoft tested an alternative health-check mechanism, server restarts, traffic rerouting and rebuilding part of the infrastructure using a previous configuration. Recent configuration changes were also under investigation, but a definitive root cause had not been established publicly.
The recovery effort
In its November 13 updates, Microsoft described limited recovery but also servers that became unresponsive again when traffic returned. Restoration was therefore gradual, and there was no sound basis for saying that all services were fully back to normal.
Business administrators can track incidents EX1550543 and MO1550821 through the Microsoft 365 admin center or the company’s service-status page. For this type of infrastructure incident, reinstalling Outlook or changing a password will not, on its own, fix the underlying problem.
Why this matters to photographers and production teams
A photography production or film crew may depend on Outlook for client communications, Teams for approvals and SharePoint for shared documents. When these services fail at the same time, the issue goes well beyond unread emails: call sheets, quotations, deliverable feedback and team coordination can all be delayed.
The practical response is to maintain an alternative communication channel for urgent decisions and locally available copies of essential production documents. That does not mean giving up on cloud services; it means avoiding a workflow where a single service is the only path forward.
What we think
When Outlook goes down, it initially looks like a day of missed emails. For a photographer waiting for an approval or a crew organizing a shoot, the real cost is often the decisions that cannot be made on time.
What concerns us most is how unavailable servers shifted extra demand onto the remaining infrastructure. It is a concrete reminder that even enormous platforms have dependencies. A basic fallback plan — team phone numbers, an offline call sheet and a second way to send files — can save considerable time when the primary platform stops responding.
