INDEPENDENT EXPLAINERS & GENERAL KNOWLEDGEKnow more. Think clearly.
World · AI-assisted explainer

Microsoft 365 Outage, Day Two: What Happened, Who Was Hit and Why It Matters — Explained

A global Microsoft 365 outage that began on Thursday, 12 November 2026, disrupted Outlook, Teams and Copilot for a second day on Friday, hitting email at airlines, hospitals and governments in India and abroad, before Microsoft reported broad recovery late on Friday night.

By · Published · Updated · 10 min read

The short answer

A global Microsoft 365 outage that began on Thursday, 12 November 2026, left millions of users unable to reach Outlook email, Teams calendars and Copilot for a second day on Friday, 13 November. Microsoft said servers had become unexpectedly unavailable and a core process was overwhelmed, and later described the cause as a technical issue linked to a network capacity upgrade and a recent network change — not a cyberattack. In India, IndiGo and Akasa Air reported disrupted email support, while hospitals, courts and governments abroad also felt the impact. By late on Friday, Microsoft reported broad recovery and stability, but as of the early hours of Saturday, 14 November, it had given no estimated time for full restoration.

How the outage unfolded

The outage began on Thursday, 12 November 2026. Microsoft's first advisory, posted on its @MSFT365Status account, said users were having trouble accessing Exchange Online mailboxes in the Americas; within hours it had become a worldwide service degradation tracked under incident IDs EX1550543 and MO1550821, affecting Teams, SharePoint, Copilot and other services. In India, users began flagging problems at around 11 pm on Thursday, according to outage tracker Downdetector, and reports spiked again after 6 am on Friday.

By Friday the disruption was global. Downdetector recorded nearly 130,000 reports of Outlook problems at the peak, just after 1 pm local time on Thursday according to The Hindu, and The New Indian Express reported that the disruption spread to 74 countries and territories within an hour. Microsoft's service health page showed 'service degradation' for Microsoft 365 business and enterprise customers as well as consumer products, in an update at 11.16 am India time on Friday, and the same status was still showing in an update at 4.30 pm, according to The New Indian Express.

The outage entered its second day on Friday, 13 November, with Microsoft saying it was still working to pinpoint the cause. The Hindu's live coverage, updated at 2.13 am IST on Saturday, 14 November, reported that Microsoft services were beginning to come back online after nearly 18 hours without access for millions of users — but also that Microsoft had no estimated time for full recovery. The picture on Friday night was therefore one of partial recovery, not a clean end to the incident.

What broke — and what kept working

The core of the problem was Exchange Online, the part of Microsoft 365 that handles email and calendars. Features that interact with Exchange Online and email were affected, while services that do not depend on it kept working, Microsoft said. Users might be unable to access their mailboxes through Outlook on the web and on the desktop, and email delivery could be delayed. Copilot Chat might fail to load or respond in the web and desktop apps, and Copilot experiences might be unable to reach work data such as email, calendars and files.

Teams was a mixed picture. Most core functions — joining calls and meetings, group chats and channel messages — were not affected, Microsoft said, but calendar-related tasks such as scheduling and viewing meetings could fail. That distinction mattered in practice: many workplaces could still meet, but could not reliably schedule the meeting in the first place. SharePoint and Defender XDR were also named among the affected services in Microsoft's incident tracking, according to the Financial Express.

The practical effect was hours of lost productivity. The Hindu reported that thousands of Microsoft users in India woke on Friday, 13 November, to find their inboxes inaccessible. Because email is the channel through which most organisations confirm bookings, share documents and receive customer queries, the failure rippled into sectors far removed from technology — airlines, hospitals, courts and stock exchanges all reported problems, as described below.

What Microsoft says caused it

Microsoft's explanation changed as the incident developed, and it has not yet published a final root cause. Early on, the company said the strain came not from a rise in traffic but from 'a number of servers being unexpectedly unavailable'. It later said a core process on affected servers was becoming overwhelmed, causing capacity loss, and that it was opening 'all available pathways to restore service' because its actions so far 'have not provided the anticipated relief'.

By late on Friday, Microsoft had a firmer account. In a post on X reported by The Hindu at 10.32 pm on 13 November, the company said it was 'deeply sorry' for the disruption and was seeing 'broad recovery and stability'. It described the outage as a technical issue 'not related to cyber or AI / agents', introduced during an earlier network capacity upgrade and surfaced after a recent network change. It said services were being restored gradually, with stability validated at each stage, and promised a full post-incident report once its review is complete.

On the question users asked most — was this a cyberattack? — Microsoft was consistent throughout: it said it was not aware of any malicious activity behind the incident, and its status page said it had no evidence of malicious activity associated with it. Charles Lamanna, Microsoft's executive vice-president for Copilot, Agents and Platform, said on X that there was 'no indication this is the result of malicious or cyber activity', according to The New Indian Express. The company said full details of the root cause would be shared in a post-incident report once the issue was mitigated.

The impact in India

In India, the most visible impact was on airlines. IndiGo said its email support services were affected by the global Microsoft disruption and that it might not be able to receive customers' emails; it directed passengers needing urgent help to its 6E Skai assistant on its website or mobile app, and said all other support channels remained available. Akasa Air said its email support services were experiencing delays and that it might be unable to receive customer emails, asking passengers to contact its 24-hour Akasa Care Centre or reach out on social media.

Air India said its flight operations remained unaffected and there was currently no impact on any of its communication channels, after it temporarily rerouted its emails so messages continued to reach it. All three airlines stressed that flights themselves were not affected — the disruption was to email-based customer support, not to operations. The New Indian Express also reported that Microsoft completed recovery actions across parts of its affected infrastructure in the Asia Pacific region, including India, on Friday, and was gradually restoring traffic.

Beyond aviation, the outage fed a debate about dependence on a single provider. Sai Rahul Poruri, chief executive of FOSS United, told The Hindu that the outage should be a wake-up call for India to reduce dependence on external technology service providers, and argued that diversification of email providers would also support domestic micro, small and medium enterprises and the Make in India initiative. He pointed to Germany, where he said regions choose their own email providers, many using free and open-source software, and cautioned that moving government email from the National Informatics Centre to Zoho would only replace one dependence with another. That is his argument, not a government position.

The fallout around the world

The disruption reached public services in several countries. In Britain, the National Health Service faced what Rachel Harrison, public services head at the GMB union, described as a 'serious impact', with staff receiving emergency calls unable to refer patient details in the normal way and a 'massive backlog' building, although emergency and life-threatening call-outs appeared unaffected, The Hindu reported, citing AFP. The National Pharmacy Association said the outage was delaying prescriptions by affecting pharmacies' communication with doctors' offices.

Courts and governments were hit too. The UK Supreme Court said it was not receiving emails, though its portal and contact forms kept working. Singapore's Government Technology Agency said government emails were down and it was working with Microsoft to resolve the issue. The Philippines' Supreme Court said the outage had affected some of its operations, including email responses, and in Japan a deputy chief cabinet secretary said the outage had affected the government's IT infrastructure. European stock market operator Euronext told listed companies to use the telephone for corporate information after its email was disrupted.

Businesses improvised. The Financial Express reported that the outage forced some businesses and financial institutions to rely on telephones, fax machines and Bluetooth to keep operating on Friday, slowing trading and administrative work in banking, shipping and financial services. Security specialists warned about the knock-on risks: Ben Mudie, field chief technology officer for Asia Pacific at Tenable, told The Hindu that when essential tools become unavailable, employees look for workarounds such as personal email accounts or unapproved file-sharing services, which can move sensitive information beyond an organisation's control — and that an outage creates opportunities for impersonation, so urgent requests arriving through unfamiliar channels deserve extra scrutiny.

The recovery — and the wait

Microsoft's recovery proceeded in stages through Friday. It said it was seeing improvements in mailbox access and delayed email processing, that email queues were significantly reduced and approaching normal levels, and that recovery actions had been completed across portions of the affected infrastructure in the Asia Pacific region, with broader improvements in North America and across much of Europe. Its focus, it said, was on reducing the email queue and backlog and extending recovery to affected infrastructure in other regions.

To protect mail caught in the disruption, Microsoft extended the email timeout window to 48 hours, so delayed messages would not be discarded while systems recovered. It also applied a patch to an upstream authentication and routing configuration component and reported improvements in server stability, according to the Mac Observer's account of the incident. Even so, Microsoft said some users might continue to face intermittent access issues and delayed email delivery while it restored infrastructure and monitored recovery.

As of the early hours of Saturday, 14 November, there was still no estimated time for full recovery. The Hindu reported at 1.56 am that Microsoft said it did not have an ETA, adding that it was 'still draining queued messages and rebalancing traffic' and that customers might see improved sign-in and access. The company's own account by then was that services were beginning to come back online after nearly 18 hours — a recovery in progress, with the final root-cause report still to come.

What it means

The outage is a reminder of how much of daily work now runs through a small number of cloud platforms. When Outlook and the services around it stop, the damage is not limited to unread email: calendars, customer support, prescriptions, court filings and stock-exchange notices all slow down at once, because they share the same plumbing. The fact that Teams calls mostly kept working while its calendar failed shows how a single dependency — in this case Exchange Online — can decide which parts of a suite survive.

For users, the practical advice from the incident is straightforward: keep an alternative contact route for anything urgent, be wary of messages offering to restore access or asking for credentials during an outage, and expect delayed email to arrive late rather than never, given the extended 48-hour timeout. For organisations, the questions are longer-term — whether to keep backup communication channels, how quickly staff can switch to them, and whether relying on one provider for email, calendars, documents and AI assistance is a risk worth pricing in.

What remains unanswered is the full technical account. Microsoft has said the cause was a technical issue linked to a network capacity upgrade and a recent network change, and not a cyberattack, but the detailed post-incident report has not yet been published. Until it is, the most honest description of the cause is the company's own evolving account — servers unexpectedly unavailable, a core process overwhelmed, and fixes that took time to hold under live traffic. This article will need updating when that report appears.

Editorial disclosure

This article was researched with AI assistance and reviewed by the publisher before publication. Report factual errors through our contact page.

Frequently asked questions

When did the Microsoft 365 outage start?

The outage began on Thursday, 12 November 2026, with Microsoft's first advisory about Exchange Online mailbox access in the Americas. In India, users began flagging problems at around 11 pm on Thursday, and the disruption continued into its second day on Friday, 13 November.

Which Microsoft services were affected by the outage?

Outlook email and mailboxes, email delivery, Copilot Chat and Teams calendar functions were affected, because they depend on Exchange Online. Most core Teams functions — joining calls and meetings, group chats and channel messages — kept working, and services that do not depend on Exchange Online were unaffected.

Was the Microsoft outage a cyberattack?

Microsoft said it was not aware of any malicious activity behind the incident and that its status page showed no evidence of malicious activity. The company later described the cause as a technical issue, not related to cyber or AI, introduced during an earlier network capacity upgrade and surfaced after a recent network change. A full post-incident report is still awaited.

How were Indian airlines affected by the outage?

IndiGo said its email support services were impacted and it might not be able to receive customer emails, while Akasa Air reported delays to its email support. Air India said its flight operations and communication channels were unaffected after it temporarily rerouted its emails. All three airlines said flights were not affected.

When was Microsoft 365 service fully restored?

Recovery was under way through Friday, 13 November, with Microsoft reporting improvements in mailbox access and email delivery and completed recovery actions in parts of Asia Pacific, including India. But as of the early hours of Saturday, 14 November, Microsoft had given no estimated time for full recovery, and some users could still face intermittent issues.

Sources & further reading

Sources reviewed 2026-11-14. Official statements describe the issuing organisation’s position; this article is an independent explainer.

Suggest a correction · More in World

Keep exploring