Is Your Outlook Down? Microsoft's November 12 Outage Explained

Video reporting snapshot: November 12, 2026, 3:44 p.m. Eastern. Article updated with Microsoft’s 4:01 p.m. Eastern recovery update. This is a developing incident; consult Microsoft’s live service-health page for current information.

An email outage can turn into a work outage. Microsoft confirmed a service degradation affecting multiple Microsoft 365 services on November 12. For affected organizations, that means the tools used to exchange messages, coordinate meetings and share work may become unreliable together.

The important distinction is between a failure of a cloud service and a failure of an individual app. Outlook is the familiar interface many people see. Exchange Online is the cloud service behind business email. A connection problem behind that interface can disrupt access through more than one client.

Source: Microsoft service health: live incident updates ↗

At 4:01 p.m. Eastern, Microsoft reported that an alternative health-check method had allowed a subset of servers to return to service, and that it was applying the change more broadly. It was also preparing an automated process to detect and restart unresponsive servers and investigating configuration updates as possible contributors. This was progress toward recovery, not a declaration of full restoration. Microsoft also added multiple Purview services to its potential-impact list.

Microsoft's public service-health page listed Exchange Online, Microsoft Teams, SharePoint Online, Microsoft Copilot 365, Microsoft Defender XDR, Microsoft Planner and Microsoft To Do as potentially affected. The page also warned that administrators might have trouble reaching the admin center, one reason updates were being published publicly.

In the status update dated 8:44:51 p.m. UTC, or 3:44:51 p.m. Eastern, Microsoft said some affected servers had stopped responding while engineers were validating a targeted change. The company was restarting those machines so they could return with the change applied, and extending that approach to other affected infrastructure.

An earlier update described failed health checks, a component involved in processing them, and unusually high processor use. Microsoft said it was testing a way to bypass that component on some servers and working to keep further machines from being removed from service.

Health checks help infrastructure decide which machines can serve requests. When too many machines become unavailable, the remaining capacity can face more pressure. That explains why a behind-the-scenes infrastructure problem can surface as connection errors across different workplace tools. It does not establish the final cause of this incident.

Source: Microsoft service health: live incident updates ↗

The service list is a scope warning, not a claim that every user of each product has lost access. Experiences can vary between organizations and users. Nor does a Microsoft 365 incident establish that every Microsoft product or every Azure service is down.

The restart and targeted change were recovery steps under evaluation at this reporting snapshot. They were not a declaration of full restoration or a final root-cause report. This story does not assign an unsupported cyberattack explanation or promise a recovery time.

Use a separate channel for urgent coordination if your normal email or meeting tools are unavailable. Check Microsoft's public service-health page and your organization's own IT updates. Business administrators can consult their tenant's Service health view when accessible.

Treat timestamps as part of the story. A cached screenshot or a viral outage post can remain online long after a service begins recovering. The live update matters more than an old headline.