The outage impacted multiple Microsoft services including Outlook, Teams, Copilot, and other Microsoft 365 products connected to Exchange Online and email infrastructure.
Waited For Your Outlook Emails? Microsoft Begins Restoring Services After 16-Hour Disruption
In its latest update, Microsoft said it has extended email timeout to 48 hours to help preserve delayed emails during the disruption.

- Microsoft services faced a 16-hour global outage.
- Recovery actions ongoing, gradually restoring affected services worldwide.
- Email timeout extended 48 hours preserving delayed messages.
New Delhi, Nov 13 (IANS) Users in India began to receive emails via Microsoft Outlook on Friday evening, albeit slowly, after nearly a 16-hour long outage across the company services including Teams and Copilot, as the tech giant informed it was seeing early stabilisation and capacity improvements as recovery actions continue.
In its latest update, Microsoft said it has extended email timeout to 48 hours to help preserve delayed emails during the disruption.
“Recovery actions are ongoing across affected Microsoft 365 infrastructure and progressing in phases. We’re seeing incremental improvement in several workloads, but service health remains variable and capacity has not yet fully returned to baseline,” said Microsoft 365 in a post on X.
To protect delayed mail, “we’ve extended the email timeout window to 48 hours while queue and backlog processing continues,” it added.
The company added that a comprehensive update is available under incident number “MO1550821” in the Microsoft 365 admin centre. Users can also track developments through its service status page.
It further stated that it has made additional progress toward recovery, with actions now completed across portions of affected infrastructure and traffic being gradually restored.
Also Read : Jensen Huang’s Nvidia Exit Timeline: What Happened Behind The Scenes Before He Resigned?
“We’re seeing improvements in key scenarios, including mailbox access and delayed email processing, though some intermittent issues may continue. Our focus is extending these recovery actions across remaining affected infrastructure while continuing stabilization and adding capacity to improve consistency,” said Microsoft.
The mega outage, which began Thursday night, is linked to server health-check failures that caused affected servers to become unavailable. Microsoft initially attempted to address the problem by testing configuration changes and restarting affected servers. It also introduced an alternative health-check method, allowing some affected servers to return to service.
A prolonged Microsoft outage disrupted businesses, airlines and government operations across several countries on Friday, knocking out access to widely used services including Outlook, Teams and its AI assistant Copilot, as the technology giant struggled to restore normal operations hours after the disruption began.
The US-headquartered tech giant said the incident affected multiple Microsoft 365 products connected to its Exchange Online and email infrastructure.
(This report has been published as part of the auto-generated syndicate wire feed. Apart from the headline, no editing has been done in the copy by ABP Live.)
Frequently Asked Questions
What services were affected by the Microsoft outage?
How long did the Microsoft outage last?
The outage lasted for nearly 16 hours, beginning Thursday night. Users in India started to receive emails slowly by Friday evening as recovery actions began.
What caused the recent Microsoft service disruption?
The outage was linked to server health-check failures that caused affected servers to become unavailable. Microsoft attempted configuration changes and server restarts to address it.
What measures did Microsoft take to address delayed emails?
Microsoft extended the email timeout window to 48 hours to help preserve delayed emails. This measure was taken while queue and backlog processing continued during the disruption.
Are Microsoft services fully restored now?
Microsoft is seeing incremental improvements in several workloads, but service health remains variable. Capacity has not yet fully returned to baseline, and recovery actions are ongoing.

























