Current status: Microsoft has confirmed that the underlying infrastructure issue has been mitigated, and all affected Microsoft 365 services—including Outlook, Teams, SharePoint, and Copilot—have been fully restored globally. Following the successful application of the routing and authentication configuration component patches, server stability has fully normalized across all active regions. We have verified that traffic flows and service access have returned to baseline operations. We will continue to monitor our own integrations and client connectivity closely to ensure sustained stability. A detailed internal Post-Incident Report covering the root cause will be reviewed as Microsoft publishes their formal breakdown. Scope of impact: Resolved. All services are operating normally. - Microsoft
Posted Nov 15, 2026 - 19:01 AEDT
Update
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, defense-in-depth repair items, and more within a Post-Incident Report.
Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services. - Microsoft
Posted Nov 13, 2026 - 18:41 AEDT
Update
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 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, defense-in-depth repair items, and more within a Post-Incident Report. - Microsoft
Posted Nov 13, 2026 - 17:33 AEDT
Update
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 workstreams to pinpoint the underlying cause of this traffic influx and address it.
Current actions we are taking include scaling up virtual machines to increase capacity and reduce load. Additionally, we’re querying for machines in a bad state to perform a force sync for our recent network change, which may improve service availability. However, we are encountering issues with the machines being stuck in a bad state, preventing our changes from syncing as expected. We’ll continue to monitor the effectiveness of changes applied so we can determine what refinements are necessary. - Microsoft
Posted Nov 13, 2026 - 16:37 AEDT
Update
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. - Microsoft
Posted Nov 13, 2026 - 15:56 AEDT
Update
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. - Microsoft
Posted Nov 13, 2026 - 14:43 AEDT
Monitoring
Microsoft Update:
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 a particular type of request is contributing to the impact and allow us to restore service incrementally. Additionally, we're rebuilding a subset of affected servers using a previous software configuration to validate whether this prevents them from becoming unresponsive, and we'll expand this approach to additional servers if we observe positive results. - Microsoft
Posted Nov 13, 2026 - 11:22 AEDT
Investigating
Latest from Microsoft: Current status: We've begun returning a portion of the affected servers to service, and they're remaining stable so far. We’ve also shifted traffic and connections to alternative pathways wherever possible and have observed limited recovery in some regions.
We've streamlined our recovery process to expedite returning the remaining affected servers to service. To further support recovery, we're implementing protective traffic management measures in a specific location to reduce load on the affected infrastructure, and we'll expand these measures to additional locations if we observe positive results. As capacity is restored, users may experience a gradual recovery as their clients reconnect to the service. - Microsoft
Posted Nov 13, 2026 - 10:18 AEDT
Monitoring
Microsoft Update: 09:30AM: We’re continuing to pursue all available pathways to restore service, as our actions taken thus far have not provided the anticipated relief. Our investigation has found that a core process on the affected servers is becoming overwhelmed, which causes the servers to stop responding and contributes to the capacity loss.
To validate a potential recovery approach, we're fully isolating a portion of our service infrastructure, restarting the affected components, and gradually reintroducing traffic to confirm our services remain stable before applying this approach more broadly. We're also analyzing traffic patterns across our entire service infrastructure and evaluating whether isolating traffic within each region may allow affected regions to recover independently.
We're aware of a widespread Microsoft 365 outage that started early this morning. Users may have trouble sending or receiving email, or connecting to other Microsoft 365 services.
Services that may be affected:
Exchange Online / Outlook Microsoft Teams SharePoint Online Microsoft 365 Copilot Microsoft Defender XDR Third-party apps connected to Microsoft 365
Microsoft has confirmed the problem is on their side and is working to restore service. We're monitoring the situation and will update this page as more details come from Microsoft.