Microsoft's Current Status: We're seeing continued recovery progress across affected regions, with broader improvements now observed in North America and sustained improvements across much of Europe. We're also seeing encouraging recovery signals in Asia Pacific, although some users may continue to experience intermittent access issues or delayed email delivery as mitigation progresses across the remaining affected infrastructure.
Our focus remains on stabilizing recovered infrastructure, completing mitigation in the remaining impacted areas, and reducing delayed email queues and backlogs. We're closely monitoring service consistency and validating recovery across different connection methods as we work toward full mitigation.
At this time, we have no evidence of malicious activity associated with this incident. We will continue to treat this with urgency until full mitigation, and we will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation is complete.
Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.
Next update by: Friday, November 13, 2026, at 2:00 PM UTC
Posted Nov 13, 2026 - 08:31 EST
Update
Another Microsoft Update:
Current status: We’re seeing encouraging recovery progress in Europe, with service availability and email delivery performance improving across a growing portion of affected Microsoft 365 infrastructure. Japan remains comparatively more stable, while North America is also improving; however, some users may still experience intermittent issues as recovery actions continue.
We're focused on addressing the remaining areas of disruption and improving service consistency across affected regions. Reducing email queues and backlogs remains a priority, and the extended 48-hour email timeout window remains in place to help protect delayed messages as delivery catches up.
At this time, we have no evidence of malicious activity associated with this incident. We will continue to treat this with urgency until full mitigation, and we will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation is complete.
Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.
Next update by: Friday, November 13, 2026, at 1:00 PM UTC
Posted Nov 13, 2026 - 07:05 EST
Update
Microsoft's Current status: We've made additional progress toward service recovery, with recovery actions completed across portions of the affected infrastructure in the Asia Pacific region. Traffic is being gradually restored, and we're seeing improvements in key customer scenarios, including mailbox access and delayed email processing. However, some users may continue to experience intermittent issues.
Our focus is now on extending these recovery actions across affected infrastructure in other regions, while continuing stabilization efforts and adding supporting capacity to improve service consistency.
Reducing email queues and backlogs remains a priority, and the extended 48-hour email timeout window remains in place to help protect delayed messages as delivery catches up.
At this time, we have no evidence of malicious activity associated with this incident. We will continue to treat this with urgency until full mitigation, and we will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation is complete.
Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.
Next update by: Friday, November 13, 2026, at 12:00 PM UTC
User impact: Users may be unable to connect to multiple Microsoft 365 services.
More info: Features of the Microsoft 365 services below that interact with Exchange Online and email services are impacted. Elements of those services that do not depend on interaction with Exchange Online remain functional.
- Exchange Online: Users may be unable to access their mailbox using Outlook on the web, Outlook desktop (MAPI), Exchange ActiveSync (EAS), or REST-based connections, and email delivery may be delayed. - Microsoft 365 admin center: Admins may be unable to load some admin center pages. - Microsoft 365 apps: Users may be unable to view their recently used files. - Microsoft 365 Apps Admin Center: Multiple services including Cloud Update, Cloud Policy, and Inventory are affected. - Microsoft 365 Education: Features including Assignments, Reading Progress, and Speaker Progress may be impacted. - Microsoft Copilot 365: Users may be unable to load Copilot Chat or receive responses in the web and desktop apps, and Copilot experiences may be unable to access work data such as email, calendar, and files. - Microsoft Defender for Office 365: Safe Links may be unable to verify URLs, which may impact users clicking links in Outlook and Teams. - Microsoft Defender XDR: Users may be unable to load Microsoft Defender portal pages or solution tabs. - Microsoft Fabric: Users may encounter failures when exporting reports with sensitivity labels to PDF or PowerPoint, when updating artifacts with sensitivity labels, or opening pbix with sensitivity label in Power BI Desktop. As a workaround, users can remove the sensitivity label from the affected item to complete the operation, if their organization's data protection policies allow it. - Microsoft Graph: API requests that access Exchange Online data, such as mail, calendar, and contacts, may time out. - Microsoft Intune - Microsoft Planner: Users are experiencing Plan and Task operation reliability issues. - Microsoft Purview: Multiple Purview services including Authorization, auto-labeling, Data Loss Prevention (DLP), Communication Compliance, and Data Classification are impacted, and users may be unable to load Microsoft Purview portal pages. - Microsoft Teams: Scenarios that depend on Exchange Online, including calendar, meeting scheduling, and creating chats for organizations using Information Barriers, may fail. Core messaging and online meetings remain largely functional. - Microsoft To Do: The app may not load, and users may see operation failures. - Power BI: All users may intermittently be unable to export reports with MIP sensitivity labels to PDF in Power BI. - SharePoint Online: Features that depend on Exchange Online may be impacted. Accessing files stored directly in SharePoint Online remains functional. - Universal Print: Users may encounter errors submitting print jobs or using admin features. - Windows 365: Customers who have configured their tenant and Cloud PCs to use Microsoft Purview Customer Key for Windows 365 Cloud PCs may have users who are unable to connect to their Cloud PCs.
Current status: We’re applying infrastructure capacity improvements where possible in an effort to help support traffic in regions coming online. We’re continuing to monitor the results of changes applied so we can identify strategic actions that can help to improve service health across all affected regions.
Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.
Next update by: Friday, November 13, 2026, at 3:00 AM UTC
Posted Nov 12, 2026 - 22:00 EST
Update
Microsoft's Current status: We've validated an alternative health check method on a subset of affected infrastructure, which allowed the servers in that subset to successfully return to service, and we're now applying this change more broadly. We're also preparing an automated recovery process to continually detect and restart unresponsive servers, to help keep them in service while this change progresses. Additionally, our review of recent changes has identified a small number of configuration updates that we're investigating as potential contributors to the issue.
Posted Nov 12, 2026 - 16:25 EST
Update
Latest update from Microsoft:
User impact: Users may be unable to connect to multiple Microsoft 365 services.
More info: Potentially impacted services include: - Exchange Online - Microsoft Teams - SharePoint Online - Microsoft Copilot 365 - Microsoft Defender XDR - Microsoft Planner - Microsoft To Do
Current status: While we haven't identified any recent changes that correlate with the start of impact, our investigation indicates the failed health checks may originate from a specific component on the affected servers that's responsible for processing them. We're deploying a targeted change to bypass this component on a subset of servers to validate whether this restores availability, and we've taken steps to prevent additional servers from being removed from service while we work to return the affected servers to service. We're also investigating why affected servers are experiencing elevated processor usage while handling requests.
Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.
Next update by: Thursday, November 12, 2026, at 9:30 PM UTC
Posted Nov 12, 2026 - 15:39 EST
Investigating
Microsoft is currently experiencing a severe outage. At present, we do not have any status updates since Microsoft's own status page is not responding: https://status.cloud.microsoft
Posted Nov 12, 2026 - 13:44 EST
This incident affected: 3rd Party Solutions (Office365 Services).