Outlook and Microsoft 365 disruption: November 12 and 13, 2026
At our 06:47:54 UTC check on November 14, 2026, Microsoft’s public consumer advisory reported Service restored. Its final notice, updated at 03:51:29 UTC on November 14, confirms full recovery of the affected consumer services and completion of the email backlog. Earlier notices identified Outlook.com, OneDrive, OneNote, Microsoft To Do, Teams, and Microsoft 365 for the web as affected services.
The final consumer notice retrospectively gives a start of November 12 at 10:05 UTC and an end of November 13 at 16:10 UTC. Those are Microsoft’s reported event times, not the time it published the final notice or when we confirmed recovery. They apply to this consumer incident; the public business fallback page now shows Available but does not provide an incident-specific closure notice.
Work and school accounts
Microsoft’s public business fallback page now reports Available. The generic notice was authored at 05:42:35 UTC on November 14 and last updated at 06:30:00 UTC. It replaces the outage narrative and explains that the page is updated when service issues prevent administrators from accessing Service health in the Microsoft 365 admin center.
That change does not itself confirm closure of the business incident. Administrators should check their tenant’s Service health for the incident-specific status. We have not verified a final Microsoft business incident notice or business end time.
The last substantive business update we verified was 22:00:36 UTC on November 13. It reported sustained recovery, extended monitoring and email backlog checks before resolution. Microsoft believed most dependent-service impact scenarios had been addressed.
That notice listed possible Exchange Online mailbox access failures through Outlook on the web, desktop MAPI, Exchange ActiveSync or REST connections, and delayed email. It also listed Exchange-dependent features such as calendars as affected, while most Teams calls, meetings, group chats and channel messages remained unaffected and files stored directly in SharePoint remained accessible. These are historical impact descriptions, not a fresh assessment of current failures.
Earlier business advisories reported a 48-hour email timeout window to preserve delayed messages. It was not a delivery guarantee or a confirmed setting for consumer Outlook.com accounts. The generic fallback notice does not confirm whether that extension remains in effect. Earlier notices also said Microsoft had no evidence of malicious activity and planned a post-incident report after mitigation; the generic notice adds no final root cause or recovery details.
Event timeline
These are Microsoft advisory or status-page update dates and times in UTC, in 2026, not necessarily when the events occurred. The consumer start and end times above were supplied retrospectively in the final notice; earlier rows preserve what the advisories reported at the time. These notices do not establish the business incident’s exact start or end. Microsoft’s live business and consumer advisories can replace earlier notices as the incident develops.
| Advisory date and time (UTC) | Microsoft’s reported status |
|---|---|
| Nov 13, 06:24:32 | Consumer services remain degraded; Microsoft is pursuing several investigation and recovery workstreams. |
| Nov 13, 06:57:32 | Business recovery efforts show only marginal success after infrastructure reboots and patch checks; Microsoft is adding virtual-machine capacity. |
| Nov 13, 07:29:09 | Business server stability improves after an authentication/routing component patch reaches part of the infrastructure. Microsoft plans to expand it. |
| Nov 13, 10:01:07 | Business recovery proceeds in phases, with variable service health and capacity below normal. Email backlog processing is a priority, and the timeout window is extended to 48 hours. |
| Nov 13, 11:04:50 | Recovery actions finish in portions of affected Asia Pacific infrastructure. Mailbox access and delayed email processing improve, but intermittent issues remain; recovery work is expanding to other regions. |
| Nov 13, 11:55:31 | Consumer recovery is progressing while investigation into the source continues. The advisory still reports service degradation. |
| Nov 13, 12:00:37 | Business services and email delivery improve across more affected infrastructure in Europe. Japan is comparatively more stable and North America is improving, but some users still face intermittent issues. |
| Nov 13, 12:58:36 | Broader improvements in North America and sustained improvements across much of Europe accompany recovery signals in Asia Pacific. Some access issues and delayed email persist; Microsoft is checking recovery across connection methods. |
| Nov 13, 20:03:12 | Consumer infrastructure is stabilizing, but queued messages and traffic rebalancing remain. Access may improve before mail flow normalizes; Microsoft has no full-recovery ETA. |
| Nov 13, 22:00:36 | Business services show sustained recovery. Microsoft continues extended monitoring and email backlog checks before declaring resolution, and believes most dependent-service impact scenarios have been addressed. |
| Nov 14, 00:39:14 | Consumer services show sustained recovery. Microsoft continues extended health monitoring and checks the email backlog before considering the issue remediated; the advisory remains degraded. |
| Nov 14, 03:51:29 | Final consumer notice confirms full recovery and processed email backlog. It retrospectively dates the consumer event from Nov 12, 10:05 UTC to Nov 13, 16:10 UTC. Business resolution is not confirmed. |
| Nov 14, 06:30:00 | The public business fallback page shows Available and a generic notice in place of the outage narrative. This page update does not itself confirm incident-specific business closure. |
Personal accounts
Outlook.com is Microsoft’s consumer email service; Exchange Online hosts organizational mailboxes. Check which account is failing and follow the corresponding advisory.
Consumer recovery is confirmed by the umbrella advisory’s final notice, not merely by individual service rows marked operational. That consumer notice does not resolve the separate business incident.
What to do while service recovers
Check Microsoft’s public status page before making local changes. For work or school accounts, ask an administrator to open Health > Service health in the Microsoft 365 admin center and read the current impact statement for your tenant. Microsoft’s service-health instructions also point to the public status page when the admin center cannot be reached.
Keep unsent work in a location permitted by your organization. If an email’s delivery is uncertain, check its status before sending another copy; use an approved alternative channel for urgent coordination. Avoid deleting Outlook profiles, clearing locally stored mail, or changing tenant authentication settings solely in response to a shared service incident.
After recovery, verify the tasks you actually use: mailbox access, sending and receiving a test message, and any affected calendar or file workflow. Record continuing failures with their UTC timestamps and error messages for support. A successful sign-in by itself does not confirm that every dependent feature has recovered.
Acknowledgements
This post was created with assistance from AI.