Microsoft 365 Recovery Advances Region by Region; Email Timeout Extended to 48 Hours
The Takeaway: Microsoft said on Friday it had completed recovery actions across parts of its Asia Pacific infrastructure after a global Microsoft 365 outage, with mailbox access improving, and was extending them to other regions, though some users might still see intermittent issues. Microsoft said earlier on Friday that its email timeout window had been extended to 48 hours to preserve delayed messages. The company said it had no evidence of malicious activity and would publish a post-incident report with the root cause once mitigation is complete.
Email access through Exchange Online stayed patchy on Friday, a day after Microsoft first reported mailbox problems in the Americas and warned that users in any region could be affected.
Microsoft reports recovery in Asia Pacific and moves on to other regions
In an update for business customers on the Microsoft 365 service health page, posted at 11:04 GMT, the company said it had completed recovery actions across portions of the affected infrastructure in the Asia Pacific region. Traffic was being gradually restored, it said, with improvements in mailbox access and delayed email processing, although some users might continue to experience intermittent problems.
Microsoft said it was now extending those recovery actions to affected infrastructure in other regions, while adding capacity to make service more consistent. Reducing email queues and backlogs remained a priority, and the extended 48-hour email timeout window stayed in place to protect delayed messages as delivery catches up.
Its previous update, at 10:01 GMT, had described recovery progressing in phases, with incremental improvement in several workloads but service health still variable and capacity not yet fully back to baseline. The company’s status account on X carried that assessment at 10:28 GMT, and the 11:04 update at 11:11 GMT.
The company said it had no evidence of malicious activity associated with the incident. It said it would publish a full post-incident report, with the root cause and the defense-in-depth actions it plans, after mitigation is complete.
In a post on X at 19:31 GMT on Thursday, Microsoft said the “elevated load” on its infrastructure was driven not by a rise in traffic but by a number of servers being unexpectedly unavailable, which strained the remaining infrastructure.
Overnight fixes fell short before capacity began to improve
Microsoft’s status account first reported the issue at 17:54 GMT on Thursday 12 November, saying it was investigating problems accessing mailboxes on Exchange Online, its email service, through multiple connection methods in the Americas. At 18:07 GMT it said the issue might affect Microsoft 365 connectivity for users in any region.
By 21:00 GMT the company had validated an alternative service health check that let a subset of affected servers return to service, and it began applying the change more broadly. At 21:40 GMT it said it was restarting and validating affected servers, and assessing whether reverting a small number of recent configuration updates could speed recovery.
At 22:09 GMT Microsoft said the actions taken so far had not provided the anticipated relief. It had found that a core process on affected servers was becoming overwhelmed, causing capacity loss, and it was isolating part of the infrastructure to test a recovery before applying it more widely.
Shortly after midnight GMT, the company said servers returned to service could become unresponsive again once they received traffic. It was temporarily limiting which types of traffic could reach the affected infrastructure in some locations, and rebuilding a subset of servers with a previous configuration.
At 04:36 GMT on Friday Microsoft reported partial recovery in regions where it had adjusted traffic, but said those actions were not resulting in sustained recovery. By 07:44 GMT it said its latest traffic optimization was producing positive results for stability and capacity, and at 09:24 GMT it reported early stabilization and capacity improvements.
Email-linked features fail across more than a dozen services
Microsoft said features of its Microsoft 365 services that interact with Exchange Online were affected, while elements that do not depend on it remained functional. Users might be unable to reach their mailboxes through Outlook on the web, Outlook desktop and other connection methods, and email delivery might be delayed.
The company listed effects across more than a dozen services, including:
Copilot, Microsoft’s AI assistant: users might be unable to load Copilot Chat or receive responses, and Copilot might be unable to reach work data such as email, calendar and files.
Teams: most core functions, including calls, meetings and group chats, were not affected, but calendar scheduling and invitations were failing, as was the creation of live and virtual events, and users might be unable to create or delete private or shared channels.
SharePoint Online: files stored directly in SharePoint remained accessible, but some sharing with people outside an organization, and features that depend on Exchange Online, were affected.
Purview, its data-compliance tools: data loss prevention and information protection labeling were affected, and audit searches and eDiscovery search and export might also be affected.
Intune, its device-management service: device enrollment, check-in and compliance policies may have been intermittently affected.
Power Apps: users might be intermittently unable to sign in to the mobile apps; Microsoft said the web versions could serve as a workaround and that users already signed in could potentially avoid the impact by not signing out.
Fabric and Power BI: some exports of reports carrying sensitivity labels, tags that mark confidential content, could fail, intermittently in Power BI; Microsoft said Fabric users could remove the label to complete the operation where their organization’s data protection policies allow it.
Windows 365: some users of Cloud PCs, Windows desktops streamed from Microsoft’s cloud, might be unable to connect where their organization uses Purview Customer Key, which lets it supply its own encryption keys.
Microsoft Graph, the interface apps use to reach Microsoft 365 data, along with Planner, its task-planning app, and Defender, its security tools: a range of functions were affected, some intermittently.
For personal users, Microsoft said the issue affected Outlook.com, OneDrive, OneNote, Microsoft To Do, Teams and Microsoft 365 for the web, and that other Microsoft 365 services might also show issues. In a consumer update at 11:21 GMT, it said it was pursuing multiple workstreams to pinpoint the source of the issue.
In The Edge’s reading, Microsoft’s two status posts pointed in different directions at midday on Friday: the business post reported completed recovery work in Asia Pacific and better mailbox access, while the consumer post, then last updated at 11:21 GMT, said the company was still working to pinpoint the source of the issue.
Outage reaches governments, health services and OpenAI
More than 430 million people use Microsoft 365 apps, according to Microsoft’s website, the BBC reported. The outage reached the Singapore government, Australia’s spy agency, and doctors’ surgeries, pharmacies, police forces and schools across the United Kingdom, according to the same report. OpenAI said it was investigating an issue affecting its connections to Microsoft’s services, the report added.
In Kuwait, the Central Agency for Information Technology said on Friday it had seen no indication so far of malicious activity or a security breach linked to the outage, that services were recovering gradually and that delayed mail would not be lost, the state news agency KUNA reported.
What to watch: The full post-incident report Microsoft has promised once its review is complete.
Method: Microsoft’s statements are from its Microsoft 365 service health page (business posts of 13 November 2026 and consumer posts of 13 and 14 November 2026) and its Microsoft 365 Status account on X (posts of 12 to 14 November 2026).
Update, 13 November 2026: In its latest business update, posted at 22:00 GMT, Microsoft said it continued to see sustained service recovery across the previously affected environments. Because of the severity of the incident, it said it was monitoring for an extended period to make sure no further mitigation was needed, and was monitoring the backlog of email built up during the outage to make sure all messages were processed before it would consider the issue resolved. It said it believed most of the affected scenarios for related Microsoft 365 products had been addressed. In its latest update for personal users, posted at 20:03 GMT, it said it was still draining queued messages and rebalancing traffic, and did not yet have an estimate for full recovery. Its status page still showed service degradation for both business and consumer products, although it listed each consumer product as operational.
Update, 14 November 2026: Microsoft said at 06:09 GMT on Saturday that it had completed its efforts to address the underlying issue of the incident and restored service to the remaining affected customers and regions. In its final update for personal users, last updated at 03:51 GMT on Saturday, it said services across the previously affected environments had fully recovered and the backlog of email messages had been processed. It put the start of that incident at 10:05 GMT on 12 November. It put the end at 16:10 GMT on 13 November. In a post on X at 18:05 GMT on Friday, the company said the outage was a technical issue not related to cyber or to AI and agents. It said the incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change. Microsoft’s status page now shows all products as operational, and the company said it would provide a full post-incident report once its review is complete.
Sources: Microsoft, BBC, KUNA.



