Microsoft Outlook outage: India users get emails after 48-hour timeout fix
Synopsis
A 16-hour Microsoft outage that knocked out Outlook, Teams, and Copilot across India and several countries is slowly unwinding — but Microsoft has had to extend its email timeout window to 48 hours just to ensure delayed messages aren’t lost. With server health-check failures at the root and capacity still below baseline, the incident exposes how a single cloud platform failure can simultaneously disrupt businesses, airlines, and governments worldwide.
Key Takeaways
Microsoft Outlook users in India began receiving emails slowly on Friday evening, 13 November , after a nearly 16-hour outage .
Microsoft extended the email timeout window to 48 hours to prevent delayed messages from being permanently lost.
The outage, which began Thursday night , was caused by server health-check failures affecting Exchange Online and Microsoft 365 infrastructure.
Services affected included Outlook , Teams , and Copilot , disrupting businesses, airlines, and government operations across multiple countries.
Microsoft is tracking the incident under reference number MO1550821 in the Microsoft 365 admin centre ; capacity has not yet returned to baseline.
Microsoft Outlook users in India began receiving emails slowly on Friday evening, 13 November, following a nearly 16-hour outage that knocked out access to Microsoft 365 services including Teams and Copilot. The tech giant said it was seeing early stabilisation and introduced a 48-hour email timeout extension to protect delayed messages while queue and backlog processing continues.
What Microsoft Said
Microsoft 365, in a post on X, stated: “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.”
The company confirmed that the email timeout window has been extended to 48 hours “while queue and backlog processing continues,” adding that it has made additional progress with traffic being gradually restored across portions of the affected infrastructure.
Microsoft further noted improvements in “key scenarios, including mailbox access and delayed email processing,” though it cautioned that “some intermittent issues may continue.” A comprehensive update is available under incident number MO1550821 in the Microsoft 365 admin centre, and users can also track progress via Microsoft’s service status page.
What Triggered the Outage
The outage began on Thursday night and is linked to server health-check failures that caused affected servers to become unavailable. Microsoft initially attempted to resolve the issue through configuration changes and server restarts, before introducing an alternative health-check method that allowed some affected servers to return to service.
The disruption ultimately affected multiple Microsoft 365 products connected to Exchange Online and its broader email infrastructure, making it one of the more prolonged platform-wide incidents for the company in recent memory.
Scale of Disruption
Beyond India, the outage disrupted businesses, airlines, and government operations across several countries on Friday, with Outlook, Teams, and Copilot all affected. The US-headquartered tech giant struggled to restore normal operations for hours after the incident first surfaced. This follows a broader pattern of cloud-dependency risk—when centralised platforms experience failures, the downstream impact on enterprise operations can be swift and widespread.
What Users and Businesses Should Do
Microsoft has advised affected users and administrators to monitor the Microsoft 365 admin centre under incident reference MO1550821 for the latest updates. The 48-hour timeout window means emails that were queued or delayed during the outage should still be delivered, reducing permanent data loss risk. Organisations relying on Outlook for critical communications are encouraged to check their mail queues and confirm delivery of time-sensitive correspondence.
Point of View
Airlines, and government systems is a stark reminder that enterprise cloud concentration carries systemic risk that few organisations have adequately planned for. Microsoft’s decision to extend the email timeout to 48 hours is a sensible safeguard, but it also signals just how deep the backlog runs — this was not a brief blip. The root cause — server health-check failures — points to infrastructure monitoring gaps at a scale that the world’s most valuable software company should not be seeing in 2026. As Teams and Copilot become deeper fixtures in enterprise workflows, a single Exchange Online failure increasingly carries the blast radius of a utility outage, not a software glitch.
NationPress
14 Nov 2026
Frequently Asked Questions
What caused the Microsoft Outlook outage on 13 November 2026?
The outage was triggered by server health-check failures that caused affected servers to become unavailable, disrupting Microsoft 365 services including Outlook, Teams, and Copilot. The incident began Thursday night and lasted nearly 16 hours before recovery actions began to take effect.
Why did Microsoft extend the email timeout to 48 hours?
Microsoft extended the email timeout window to 48 hours to protect emails that were delayed or queued during the outage, preventing them from being permanently lost. This measure was introduced while queue and backlog processing continues across the affected infrastructure.
How can users and admins track the Microsoft outage recovery?
Microsoft has made a comprehensive update available under incident number MO1550821 in the Microsoft 365 admin centre. Users can also monitor recovery progress through Microsoft’s official service status page.
Which services were affected by the Microsoft outage?
The outage disrupted multiple Microsoft 365 products including Outlook, Teams, and the AI assistant Copilot, all of which are connected to Microsoft’s Exchange Online and email infrastructure. Businesses, airlines, and government operations across several countries were impacted.
Has Microsoft fully restored Outlook and Teams services?
As of Friday evening, services were recovering but had not yet returned to full baseline capacity. Microsoft said service health remained variable and that some intermittent issues may continue even as mailbox access and email processing show incremental improvement.
