Outlook Down? The Nov. 12 Microsoft 365 Outage Explained

Outlook Down? The Nov. 12 Microsoft 365 Outage Explained

On Thursday, November 12, 2026, Outlook stopped working for a large share of Microsoft 365 users. Starting shortly before 1 p.m. Eastern, people across the Americas could not reach their Exchange Online mailboxes, and many also reported trouble with Teams. Microsoft says the cause was servers in its own email service failing automated health checks and dropping out of service, not a surge in traffic, and it has reported no sign of a cyberattack. By about 4 p.m. Eastern, Microsoft said a fix had brought some servers back and was being applied more broadly. Nothing Microsoft has published suggests mailboxes were breached or mail was lost: this was an access problem on Microsoft’s side.

What happened

Microsoft’s first posts on its Microsoft 365 Status account said it was investigating reports of users having trouble accessing Exchange Online mailboxes through multiple connection methods in the Americas, and that part of its infrastructure was under “elevated load across multiple regions.” It tracked the problem as incident EX1550543 for Exchange Online and MO1550821 for the wider Microsoft 365 impact. Users also reported problems with Teams, SharePoint Online, and Microsoft 365 Copilot.

Over the afternoon, Microsoft narrowed it down:

• “We determined the elevated load isn’t driven by an increase in traffic, but by a number of servers being unexpectedly unavailable; straining the remaining infrastructure.”
• It paused all deployments, moved traffic off the affected infrastructure, and began restarting affected servers to return them to service.
• It found no recent change that lined up with the start of the problem, and said the failed health checks “may originate from a specific component that’s responsible for processing server health.”
• Around 4 p.m. Eastern, it said an alternative health check method had allowed a subset of affected servers to return to service: “We’re now applying this change more broadly.” It also said it was preparing automated systems to detect and restart unresponsive servers.

In plain terms: a large number of Microsoft’s email servers failed their automated health checks and were taken out of service. The servers that remained could not carry all the work, so connections failed, and Microsoft’s investigation points at the component that runs those health checks. As of Thursday evening, Microsoft had not published a root cause. Admins can follow the final updates and the post-incident report under EX1550543 in the Microsoft 365 admin center.

Was it a cyberattack?

Nothing Microsoft has published points to one. It has described servers failing health checks inside its own infrastructure and has reported no malicious activity. That matters for your next steps: there is no reason to reset every password or treat the outage as a breach. If you do see real warning signs, such as inbox rules you did not create or sent mail you did not write, follow our guide on how to tell if your email is hacked.

What to do while Microsoft 365 is down

1. Check Microsoft before troubleshooting. Admins should look at Health > Service health in the Microsoft 365 admin center. If the admin center itself is unreachable, Microsoft posts updates at status.cloud.microsoft and on its Microsoft 365 Status account on X. If an incident is listed, the problem is not your computer or your network.
2. Don’t try to fix it on your own PC. Reinstalling Office, deleting the Outlook profile, or resetting passwords will not fix a problem on Microsoft’s servers. A new Outlook profile also has to download the whole mailbox again once service returns, which can keep you offline longer.
3. Work from what Outlook already has. Outlook on your desktop normally keeps a local copy of recent mail, your calendar, and your contacts, so you can usually still read messages and check today’s appointments. Messages you send wait in the Outbox and go out when the connection returns.
4. Don’t assume mail is lost. When a mail server cannot deliver a message, it normally queues it and keeps retrying, so email sent to you during an outage usually arrives late rather than vanishing. Once service is back, give it time to catch up before chasing missing messages.
5. Use a channel outside Microsoft 365. Teams was affected too, so move urgent conversations to phone calls or text messages. If customers email you for orders or appointments, post a short notice with your phone number on your website or social media.

Watch for outage-themed phishing

Scammers follow the headlines. In the days after a big outage, expect emails claiming your mailbox was “suspended during the outage” or asking you to sign in to “restore” messages, along with calls from fake Microsoft support. Microsoft says it does not make unsolicited calls offering technical support, and a link asking for your password to recover a mailbox is a phishing attempt. Check any message like that with the SLAM method before you click anything.

What this outage should change for your business

Know what Microsoft actually guarantees. Microsoft’s financially backed service level agreement for Exchange Online promises 99.9% uptime each month, which still allows about 43 minutes of downtime in a 30-day month. If an outage pushes a month below that, service credits are not automatic: your Microsoft 365 admin or IT provider has to file a claim. Write down when your staff lost access and when it came back while the details are fresh.

Plan for email and Teams going down together. Many businesses run everything through Microsoft 365, so one incident can take out email, chat, and shared files at the same time. Decide ahead of time how staff will reach each other, who tells customers what, and how customers can reach you, the same way you would plan for losing your internet connection. Admins can also have the Microsoft 365 admin center email them about service incidents; send those alerts to an address outside your Microsoft 365 email so they arrive even when your email is the thing that is down. Our guide to the first hour of an incident covers the roles and contact lists to set up before you need them.

Know what a backup does and doesn’t do. A third-party Microsoft 365 backup protects you against deleted or encrypted data, but it does not keep mail flowing during an outage like this one. Staying productive through an outage takes a plan, not just a backup.

Don’t switch platforms over one bad afternoon. Every large cloud provider has outages, as the AWS outage of October 2025 showed. Moving to another provider trades one set of risks for another. The better fix is a plan that assumes any provider will occasionally go down.

Get ready for the next one

Equal Tech Solutions supports Microsoft 365 for businesses across Cleveland, Chattanooga, and the Southeast as part of our managed IT and cloud services. We can set up service health alerts, write an outage plan your staff can follow, and file SLA claims when Microsoft falls short. Contact us if this outage exposed gaps in your plan.