Active Incident

Updated a few seconds ago

Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methodsService Disruption

Incident Status

Service Disruption

Components

Communication & Collaboration

System

Email


November 13, 2026 7:03AM EST
IDENTIFIED

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. Next update will be by 8:30

November 13, 2026 5:06AM EST
IDENTIFIED

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 messages. 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 will be by 6:30 am eastern

November 12, 2026 11:26PM EST
INVESTIGATING

Update from 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. Given the hour, our next update will be at 5 AM Eastern.

November 12, 2026 10:37PM EST
IDENTIFIED

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.

November 12, 2026 9:22PM EST
IDENTIFIED

Update, 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.

November 12, 2026 8:16PM EST
IDENTIFIED

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 the start of impact and are monitoring to determine whether this contributes to recovery. The temporary traffic limitations we previously described are now in effect in specific locations. We're monitoring the affected servers in those locations to confirm whether they remain stable while handling a narrower set of connections, after which we'll gradually reintroduce additional traffic.

November 12, 2026 7:07PM EST
IDENTIFIED

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.

November 12, 2026 6:05PM EST
IDENTIFIED

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.

November 12, 2026 5:09PM EST
IDENTIFIED

Update from Microsoft, 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. Next update at 6:00 PM EST

November 12, 2026 4:42PM EST
IDENTIFIED

Update from Microsoft, We're continuing to work through restarting and validating the affected servers to safely return them to service, and we're exploring opportunities to expedite this process. In parallel, we're assessing whether reverting the small number of recent configuration updates we identified could help accelerate recovery.

November 12, 2026 4:10PM EST
IDENTIFIED

Update from Microsoft, 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. Next update at 5:00 PM EST

November 12, 2026 3:49PM EST
IDENTIFIED

Update from Microsoft, While validating the targeted change, we found that many of the affected servers have become unresponsive, which is preventing us from confirming whether the change is effective. We're restarting these servers so they can come back online with the change in place, and we're applying the same approach to additional affected portions of our infrastructure to validate the results more broadly.

November 12, 2026 2:50PM EST
IDENTIFIED

Update from Microsoft, We're aggressively pursuing all pathways to reduce impact. As a precaution, we've paused all deployments and configuration changes while we review recent changes for any correlation to this event. We've determined that the elevated load isn't driven by an overall increase in traffic, but by a large number of servers being unexpectedly unavailable, which is shifting load onto the remaining infrastructure. We're investigating what's causing these servers to become unavailable while we work to safely return them to service. We've identified that affected servers are failing automated health checks, which is causing them to become unavailable, and this may be related to a recent change to a component involved in processing those checks. We're testing a configuration change on a subset of affected infrastructure to address this and, if successful, will apply it more broadly. In parallel, we've initiated a restart of all affected servers and are validating whether they're successfully returning to service. Next update at 4:00 PM EST

November 12, 2026 1:41PM EST
IDENTIFIED

Users may be unable to connect to multiple Microsoft 365 services 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 Current status: We’re investigating an issue impacting multiple Microsoft 365 services and we've determined the affected infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors. We're restarting and repairing impacted portions of this infrastructure to restore capacity, and reviewing an unexpected increase in a specific type of service traffic to determine whether it's contributing to the elevated load. In parallel, we're evaluating options to redirect traffic to alternate infrastructure to expedite relief. Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.

November 12, 2026 1:01PM EST
INVESTIGATING

Microsoft has identified connectivity errors occurring on a portion of Exchange Online infrastructure which receives and processes users’ access requests. We’ve collected networking logs to review to further investigate the source of these errors and confirm our next steps.

Scheduled Maintenance

Tuesday Monthly Patch CyclePlanned Maintenance

Schedule

November 17, 2026 7:00PM - 10:00PM EST

Components

Core Infrastructure

System

Data Center

Description

In some cases short term disruptions to certain services and applications may occur but should last no longer than 10 minutes. Any servers requiring updates will be patched and rebooted per assigned schedule. Automated emails will be sent to server owners upon completion so that post-reboot verifications may be completed.
Wednesday Monthly Patch CyclePlanned Maintenance

Schedule

November 18, 2026 7:00PM - 10:00PM EST

Components

Enterprise Applications, Core Infrastructure, Data & Analytics

System

OnBase, Pulse, RightFax, The Central Line, Data Center, VDI, Analytics / PowerBI

Description

All services and applications are subject to intermittent disruptions throughout the maintenance window. These may be expected to last up to 30 minutes and can repeat. Any servers requiring updates will be patched and rebooted per assigned schedule. Automated emails will be sent to server owners upon completion so that post-reboot verifications may be completed.

Identity & Access




Operational

Communication & Collaboration




Service Disruption

Enterprise Applications




Operational

Core Infrastructure




Operational

Data & Analytics




Operational

1

Incidents Last 30 Days

0

Days Since Last Incident

2

Upcoming Maintenance

History

No incidents in the last 7 days