Microsoft Outage Enters Second Day as Recovery Patch Improves Stability

Microsoft’s global Microsoft 365 outage entered its second day on November 13, 2026, with server stability improving after a configuration patch, but full recovery still unconfirmed. The company says it is not aware of malicious activity causing the disruption.

The latest verified Microsoft update, issued at approximately 3:09 a.m. EST on November 13 and reproduced by the University of Pennsylvania’s IT service , continued to classify the incident as service degradation. Microsoft was expanding the authentication and routing patch, prioritizing regions in or approaching business hours. No firm restoration deadline had been announced.

Outlook and Exchange Remain Central to Disruption

Exchange Online is the central affected service, with users experiencing mailbox access failures and potentially delayed email delivery. The disruption also affects Microsoft 365 features that depend on Exchange, according to Microsoft’s incident notices.

Teams calendars, scheduling and invitations can fail, although most core calling, meetings and messaging remain functional. Direct access to files stored in SharePoint remains available, while external sharing and some dependent features are disrupted.

Microsoft also listed problems involving Copilot responses, some administration pages, security and compliance workflows, and education features. Not every user or function of these services is affected. The incident is not a confirmed outage of every Microsoft product.

The Associated Press reported government and business disruption, including Singapore government email outages and Japanese government IT problems. IndiGo reported interrupted email support but said flight operations were unaffected.

Recovery Follows Uneven Overnight Progress

Microsoft’s incident timeline places the start of Exchange Online problems at 11:17 a.m. EST on November 12. The company broadened its incident reporting to multiple Microsoft 365 services about two hours later.

Engineers redistributed traffic, restarted servers, and paused deployments. Overnight recovery was uneven, with some restored servers becoming unresponsive again.

Microsoft identified an overwhelmed process responsible for establishing secure connections and investigated a recent network configuration change. A definitive root cause remains pending.

According to AP, Microsoft said it was not aware of malicious activity causing the incident. That statement does not amount to a completed investigation ruling out an attack.

The next recovery milestone is confirmation that the expanded patch has restored reliable access, rather than simply improved server stability.