Microsoft 365: Users may be unable to connect to multiple Microsoft 365 services.

Microsoft: Current status: We remain focused on addressing residual impact and ensuring reliable service restoration. We continue to assess recovery across various connection methods and are closely monitoring service health to verify sustained stability. 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. Next update by: Friday, November 13, 2026, at 6:00 PM UTC

Microsoft: Current status: Current status: We remain focused on addressing residual impact and ensuring reliable service restoration. We continue to assess recovery across various connection methods and are closely monitoring service health to verify sustained stability. 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. Next update by: Friday, November 13, 2026, at 6:00 PM UTC

Microsoft: Current status: We're observing sustained improvements in service availability as recovery progresses across affected Microsoft 365 services. While service functionality continues to improve, some users may still experience intermittent connectivity issues or delayed email delivery. Our efforts are increasingly focused on resolving the remaining issues and restoring consistent service for all affected users. We're validating recovery across different connection methods and monitoring service stability to confirm that improvements are… Next update by: Friday, November 13, 2026, at 4:00 PM UTC

Microsoft: Current status: We're continuing to see improvements in service availability, with email queues significantly reduced and approaching normal levels. Some users may still experience intermittent access issues or delayed email delivery as recovery continues. We've implemented additional mitigation measures and are restoring the remaining affected infrastructure while investigating residual service issues. We're closely monitoring service health and validating recovery across affected connection methods to ensure sustained service… Next update by: Friday, November 13, 2026, at 3:00 PM UTC

Microsoft: 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… Next update by: Friday, November 13, 2026, at 2:00 PM UTC

Microsoft: 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… Next update by: Friday, November 13, 2026, at 1:00 PM UTC

Microsoft: 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… Next update by: Friday, November 13, 2026, at 12:00 PM UTC

Microsoft: Current status: Recovery actions are ongoing and have progressed in phases across affected Microsoft 365 infrastructure. Global telemetry and customer reports show incremental improvement in several workloads; however, service health remains variable and capacity has not yet fully returned to baseline. Network and traffic-management actions remain active. To protect email during recovery, we’re continuing to prioritize queue and backlog processing, and the email timeout window has been extended to 48 hours to preserve delayed… Next update by: Friday, November 13, 2026, at 11:00 AM UTC

Microsoft: Current status: Users may be unable to connect to multiple Microsoft 365 services. Next update by: Friday, November 13, 2026, at 10:00 AM UTC

Microsoft: Current status: Users may be unable to connect to multiple Microsoft 365 services.

Microsoft: Current status: We’re seeing positive results for server stability after applying an upstream authentication/routing configuration component patch to a portion of our infrastructure. We’ll continue to monitor its progress and are working to expand it to servers supporting active regions coming online. As of now, we are not aware of any malicious activity that is causing this incident. We will continue to treat this incident with urgency and priority until full resolution. Once mitigated, we will provide full details of the root cause… Next update by: Friday, November 13, 2026, at 8:30 AM UTC

Microsoft: Current status: We’re continuing to monitor activity across regions to evaluate server status and determine actions that can be taken to improve capacity. This includes reviewing server performance and confirming that developed patches have been applied and working as intended after infrastructure reboots are completed. At this point, we have observed marginal success. In parallel, we’re taking action to expand capacity through the utilization of Virtual Machines. As of now, we are not aware of any malicious activity that is causing… Next update by: Friday, November 13, 2026, at 7:30 AM UTC

Microsoft: Current status: As part of our ongoing efforts to advance the recoverability of our frontend servers, we’re evaluating traffic controls that can be applied to increase capacity and stability. This includes traffic optimization actions such as traffic throttling, protocol adjustments, and failover routing intended to improve stability in active regions. In parallel, were expanding internal testing to track activity within a contained environment to improve traffic monitoring and issue detection capabilities. As of now, we are not aware… Next update by: Friday, November 13, 2026, at 7:00 AM UTC

Microsoft: Current status: We’re continuing to pursue multiple workstreams to pinpoint the underlying cause of the traffic influx and advance the recoverability of the backend servers. We’re taking a measured approach to identify and repair affected infrastructure to improve the ability to confirm the developed changes were applied. We’re tracking the results of this approach to verify the servers are showing the anticipated recovery and performance intended. As of now, we are not aware of any malicious activity that is causing this incident. We… Next update by: Friday, November 13, 2026, at 7:00 AM UTC

Microsoft: Current status: We appreciate your organization’s patience and understanding while we work with urgency to resolve this incident. As we’ve applied our current ongoing mitigation actions, we’ve observed a surge in outbound call volume from our routing services to our backend servers. This occurs when the backend servers outbound service cannot properly route to the backend machines. We’re continuing to observe heightened volume due to traffic rebalancing actions that we have taken throughout this event. We’re working on multiple… Next update by: Friday, November 13, 2026, at 6:00 AM UTC

Microsoft: Current status: We’re continuing our efforts to improve server stability to improve traffic flow. This includes adjusting traffic protocols, redistributing traffic, and applying strategic traffic blocking measures. We're observing partial recovery across regions in which we've applied these adjustments; however, these actions aren't resulting in sustained recovery, so we're reviewing what additional actions we can take to improve overall infrastructure stability. Next update by: Friday, November 13, 2026, at 5:00 AM UTC

Microsoft: Current status: As part of our investigation into the sustained traffic management imbalances, we’re reviewing traffic flows and affected infrastructure to identify opportunities to optimize routing. This includes verifying the reasons for service failures so we can develop specific actions to improve stability. We will continue to share more information as soon as we have it, and for now we can confirm that there is no indication this is the result of malicious activity. We’ll continue to apply learnings towards remediation actions… Next update by: Friday, November 13, 2026, at 4:30 AM UTC

Microsoft: Current status: As part of our investigation into the sustained traffic management imbalances, we’re reviewing traffic flows and affected infrastructure to identify opportunities to optimize routing. This includes verifying the reasons for service failures so we can develop specific actions to improve stability. Next update by: Friday, November 13, 2026, at 4:30 AM UTC

Microsoft: Current status: We’ve monitored the status of the changes applied to improve serviceability and confirmed that change is not taking as expected. We’re identifying alternate workstreams that can be applied to increase capacity in the face of sustained traffic management imbalances. Next update by: Friday, November 13, 2026, at 3:30 AM UTC

Microsoft: 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. Next update by: Friday, November 13, 2026, at 3:00 AM UTC

Microsoft: Current status: We’re seeing positive results with our efforts to restart affected infrastructure. We’re actively monitoring the performance of these to verify stability which will support improved availability. Remediation actions will be expanded as we confirm stability with the changes applied. Next update by: Friday, November 13, 2026, at 3:00 AM UTC

Microsoft: Current status: Our investigation has found that a process on the affected servers responsible for establishing secure connections becomes overwhelmed, causing the servers to stop processing requests. We're preparing a configuration change to address this behavior that can be applied across all affected servers, and we're validating it on a subset of servers before applying it more broadly alongside restarts of the affected infrastructure. In parallel, we've begun reverting a recent network configuration change that correlates with… Next update by: Friday, November 13, 2026, at 2:00 AM UTC

Microsoft: Current status: We've reviewed known impact scenarios and have revised the list of impact services and features, which can be viewed in the "more info" section of this communication. We're continuing our work to isolate the issue affecting server availability, as well as other workstreams. Next update by: Friday, November 13, 2026, at 1:30 AM UTC

Microsoft: Current status: While the servers we've returned to service initially remain healthy, we've observed that they can become unresponsive again once they begin receiving traffic. We're analyzing diagnostic data from these servers with our networking and platform experts to determine what's triggering this behavior. Building on the protective traffic management measures we've implemented, we're also temporarily limiting which types of traffic can reach the affected infrastructure in specific locations. This will help us determine whether… Next update by: Friday, November 13, 2026, at 1:30 AM UTC

Reported by Microsoft on its status page: Users may be unable to connect to multiple Microsoft 365 services. Potentially impacted: Exchange Online, Microsoft Teams, SharePoint Online, Microsoft Copilot 365, Microsoft Defender XDR, Microsoft Planner, Microsoft To Do, Microsoft Intune, Microsoft Defender for Office 365, Microsoft Purview, Power BI, Microsoft 365 Apps Admin Center, Universal Print, Windows 365.