BharatBeat
MicrosoftOutageOutlookTeamsIndiGoAir India

Microsoft 365 Outage: Outlook, Teams and Indian Airline Emails, Explained

Microsoft 365 suffered a global outage from 12 November 2026 that hit Outlook, Teams and Copilot, and left IndiGo and Akasa Air warning that customer emails might not get through. Air India said it rerouted email and that flights were unaffected. Microsoft told the BBC the cause was a technical fault in an earlier network capacity upgrade, not a cyber or AI incident, and that the underlying issue had been addressed. On Saturday morning, 14 November, the public status page still listed service degradation, and Microsoft had said it had no time for full recovery while it drained queued mail.

By BharatBeat Technology Desk12 min read

Outlook, Teams and Copilot failed for a second day, and the failure reached the inboxes Indian passengers actually use. IndiGo told customers it might not receive their emails. Akasa Air sent people to a phone number. Air India said it had rerouted mail so that messages would still arrive, and that its planes were flying. None of that is a Microsoft post. It is what the airlines put on X on Friday, 13 November 2026, as carried by The Hindu and Mint.

Microsoft's own account of the cause came later on Friday. A spokesperson told the BBC the incident was a technical issue, not related to cyber or AI/agents, introduced during an earlier network capacity upgrade and surfaced by a recent network change. The underlying issue, Microsoft said, had been addressed. Restoration was gradual, because of the scale of demand. A full post-incident report would follow the review.

That is not the same thing as "it is over." At about 6:30 am IST on Saturday, 14 November, the public status page at status.cloud.microsoft still headed its board with service degradation on Microsoft 365 for business and enterprise, and on consumer products. The line under the business entry was still: users may be unable to connect to multiple Microsoft 365 services. Azure showed no issues on that page.

The 60-second version

  • What broke: Exchange Online first, then Microsoft 365 more widely. Outlook, Teams and Copilot are the names in the BBC's account. The Hindu's Friday story names Outlook and Teams.
  • When: BBC timeline, from Microsoft posts on X: first acknowledgement 5:54 pm GMT, 12 November (11:24 pm IST), Americas mailboxes. Global warning at 6:07 pm GMT. The Hindu, citing Downdetector, says India reports began around 11 pm IST on Thursday and jumped again after 6 am IST on Friday.
  • The cause Microsoft has given: not a cyber attack, not AI. A fault in an earlier network capacity upgrade, which showed up after a network change. Underlying issue addressed. Services brought back in stages.
  • What was still true overnight: BBC, 8:08 pm GMT Friday (1:38 am IST Saturday): Microsoft was still draining queued messages and rebalancing traffic, and could not say when full recovery would finish. Status page on Saturday morning: still service degradation.
  • India, the practical bit: IndiGo email support hit, flights not. Air India rerouted email, flights not hit, usual 24-hour replies. Akasa email hit. Mint's report of the Akasa advisory gives +91 9606 112131.
  • Your sent mail: BBC says Microsoft stretched the timeout window to 48 hours so delayed messages are not dropped while the queue clears. The stamp on a late message is when it was delivered.

Two statements, and then the one Microsoft settled on

Friday morning in India, the public wording was still a diagnosis in progress. The Hindu (PTI, published 2:30 pm IST, updated 3:10 pm IST) reported a Microsoft post on X: the strain was not triggered by increased traffic. It was "a number of servers being unexpectedly unavailable." The same story reported a service-health update at 11:16 am IST: service degradation for Microsoft 365 business and enterprise users, several workstreams trying to find the cause of a traffic influx and to recover backend servers, and this sentence: "As of now, we are not aware of any malicious activity that is causing this incident." A post-incident report would come once the problem was resolved.

Read those Friday-morning lines together and they do not yet pick a single cause. One says the strain was unavailable servers, not a traffic surge. The service-health wording The Hindu quoted was still looking for the cause of a traffic influx. Both rejected a malicious attack. Neither is the later explanation.

The later explanation is the spokesperson's statement to the BBC, published at 4:51 pm GMT on 13 November (10:21 pm IST). The BBC quotes it as a technical issue "not related to cyber or AI/agents." Then: "The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change." And: "We have addressed the underlying issue and continue to restore service to remaining customers and regions." The BBC adds that Microsoft said it was restoring gradually because of the "scale of demand," and that a full post-incident report would come after the review.

The BBC's timeline of the company's own posts, all GMT, is the clock between those two moments:

Time (GMT, 12-13 November)What the BBC says Microsoft posted
12 Nov, 5:54 pmFirst acknowledgement: Americas users unable to open Exchange Online mailboxes
6:07 pmDisruption may affect Microsoft 365 connectivity globally
7:31 pmA number of services had become "unexpectedly unavailable"
7:50 pmServers failing automated health checks
11:04 pmSome affected servers returned to service and "remain stable"
13 Nov, 12:06 amServers could become unresponsive again once they took traffic
4:36 am"Partial recovery" in some regions
9:24 amEarly stabilisation and capacity improvements
1:32 pmBroader improvement in North America, sustained improvement in much of Europe, encouraging signals in Asia Pacific
2:17 pmEmail queues "significantly reduced and approaching normal levels"
3:39 pm"Encouraging recovery"; no indication of malicious or cyber activity

At 8:08 pm GMT (1:38 am IST on Saturday) the BBC reported a further update: Microsoft was "still draining queued messages and rebalancing traffic," some customers might see access improve, and the company could not say when full recovery would be complete. That is the last timed Microsoft line in the live story this note uses. The status page check after it, Saturday morning in India, still showed degradation.

A separate BBC explainer (Tom Gerken, Laura Cress and Cachella Smith) says problems were reported in at least 74 countries, and that more than 430 million people use Microsoft 365 apps, a figure it attributes to Microsoft's website. The live blog's summary says Teams, Outlook and Copilot were inaccessible in at least 70 countries. Both numbers are the BBC's, from different pieces, and neither is a count of people who actually failed to log in. The explainer is explicit that the full scale has not been confirmed. Downdetector counts, which are reports rather than users, moved around. Mint, citing Reuters and Downdetector, said Outlook reports rose to 138,058 around 1 pm ET on Thursday and were 34,490 by Thursday night, with Microsoft 365 complaints near 13,000 by 5:47 pm ET.

What each Indian airline actually said

The Hindu's PTI copy quotes IndiGo directly: "Due to a global Microsoft service disruption, our email support services are currently impacted, and we may not be able to receive your emails." A later IndiGo post, also in that story, said the disruption was still hitting email support, that flight operations remain unaffected, that other support channels were operational, and that 6E Skai was still taking queries around the clock. Mint's reading of the same advisory is that urgent cases should go to 6E Skai on the website or the app.

Air India, quoted by The Hindu from its newsroom account: flight operations unaffected, and "there is currently no impact on any of our communication channels." The mechanism it gave is specific. It temporarily rerouted emails so that every message would still reach the airline, and it said it was answering within the usual 24-hour timeline. The channels it listed as working were voice, AI.g, social media and customer notifications. Mint describes the same post, and adds the phrase "actively tracking the situation."

Akasa is in Mint, not in The Hindu piece. Mint says Akasa stated that its email support was impacted, and that a travel advisory on X told passengers to contact the Akasa Care Centre at +91 9606 112131 or to use social media for immediate help. That phone number is Mint's report of the advisory. It is not printed in the Microsoft status page.

Mint also says Delhi Airport issued a passenger advisory urging people to verify flight tickets before boarding. The story does not quote the advisory in full, and it does not say Delhi flights were cancelled. The three airlines' own lines, above, are about email support. They are not cancellation notices.

The split is the useful part. A passenger emailing IndiGo was told the mail might not arrive, and was pointed at 6E Skai. A passenger emailing Air India was told the mail had been rerouted and would be answered on the normal clock. A passenger emailing Akasa was given a phone number. Treating "airlines are down" as one fact mixes three different notices.

What a delayed email is, and what it is not

The BBC explainer's answer on lost mail is the narrow one Microsoft's own warning supports. Access can come back before the queue does. Microsoft warned of intermittent access and delayed email delivery. It extended the timeout window to 48 hours "to help protect delayed messages as delivery catches up." The BBC explains that window as the time Outlook will wait to receive a message, and says that when a delayed message does appear, the timestamp is the delivery time, not the time it was sent.

That is a reason not to resend everything at once, and a reason not to assume a Friday-evening mail is already in the inbox. It is not a promise that every message will arrive. Microsoft has not published a count of messages dropped.

The same explainer quotes people interpreting the length of the outage, and those sentences are theirs. James Ferryman, of the University of Reading, told the BBC that the disclosed detail suggests the part of the servers that sets up secure connections got swamped, that one failed server passes work to the next, and that devices retrying all at once are why you cannot switch the system back on in one go. Gergely Orosz told the BBC he could not recall a business email outage taking this long, and called this one possibly the most disruptive of its kind. Troy Hunt told the BBC that Microsoft is a large part of the internet's backbone and that email still sits under appointments, purchases and account checks. Those are explanations and judgements. The cause Microsoft itself has signed is the capacity upgrade and the network change.

Elsewhere, the BBC explainer says OpenAI was investigating an issue in its connections to Microsoft's services that had caused some tools to fail, and that Anthropic had also reported problems. It says the Japanese government reported disruption to a shared IT platform. The live blog says NHS staff in England were disrupted, that the UK cyber minister described limited impact on frontline service delivery, and that the outage did not affect 999 calls or NHS 111. It also records disruption to hospitals and rail passengers in Canada, and to court and government offices in the United States. The live blog's summary puts Teams, Outlook and Copilot out of reach in at least 70 countries. None of those reports is a figure for India beyond the airline notices and the Downdetector timing The Hindu gave.

What to watch next

  1. The status label. Saturday morning it still said service degradation, for business and consumer Microsoft 365, with Azure clear. The sentence that matters is the one that replaces "users may be unable to connect."
  2. The post-incident report. Microsoft has promised one, to the BBC and in the Friday health notes The Hindu quoted. Until it exists, the capacity-upgrade line is the company's account, not a finished root-cause paper.
  3. The mail queue, not the login screen. The 1:38 am IST update was about draining queued messages. The BBC's 48-hour timeout is the window in which a delayed message can still be delivered, with a delivery-time stamp.
  4. The three airline notices. IndiGo's "we may not be able to receive your emails" is a different operational fact from Air India's reroute. Akasa's phone line is a third. A later post from each carrier is the update, not a general "Microsoft is back" line.
  5. Anything that revises "not cyber." Microsoft has said that three times in the record above: the Friday health note, the 3:39 pm GMT post, and the spokesperson's statement. A later report that changes it would be news. A screenshot of a phishing mail riding the outage would not, by itself, be that change.

The outage began as Exchange Online in the Americas on Thursday evening GMT. By Saturday morning in India the status page had not cleared it, the airlines had split three ways on email, and Microsoft's cause, in its own words to the BBC, was a network capacity upgrade, not an attack.


The spokesperson's statement (technical issue, not cyber or AI/agents, network capacity upgrade, recent network change, underlying issue addressed, gradual restoration, post-incident report), the GMT timeline of Microsoft posts, the 8:08 pm GMT update on queued messages and no recovery time, the "at least 70 countries" summary, and the notes on NHS, 999, Canada and US courts are from the BBC live story "Microsoft says it is 'deeply sorry' for global outage after almost 24 hours of disruption," 13 November 2026. The 74-country count, the 430 million figure attributed there to Microsoft's website, the 48-hour timeout, the delivery-time stamp, the quotes from James Ferryman, Gergely Orosz and Troy Hunt, and the lines on OpenAI, Anthropic and Japan's shared IT platform are from the BBC explainer "Why is Microsoft's outage lasting so long and will emails be lost?" by Tom Gerken, Laura Cress and Cachella Smith. IndiGo and Air India's wording, the Downdetector timing in India (about 11 pm IST Thursday, surge after 6 am IST Friday), the 11:16 am IST service-health update, the X post on servers unexpectedly unavailable, and the "no malicious activity" sentence are from The Hindu, PTI, published 13 November 2026, 2:30 pm IST, updated 3:10 pm IST. Akasa's email notice and the +91 9606 112131 care-centre number, the Delhi Airport advisory as paraphrased, and the Reuters Downdetector counts of 138,058, 34,490 and about 13,000 are from Mint, Pragya Singha Roy, published 13 November 2026, 4:14 pm IST. The Saturday status (service degradation on Microsoft 365 business, enterprise and consumer products; Azure clear) is from the public page at status.cloud.microsoft, checked at about 6:30 am IST on 14 November 2026. Airline flight operations were described as unaffected in the posts quoted above. That is not a claim about every airport system.

Share this explainer

Frequently asked questions

›Is Microsoft Outlook still down on 14 November 2026?

Not in the sense of a total blackout, and not fully back either. On Saturday morning, 14 November 2026, at about 6:30 am IST, Microsoft's public status page still listed service degradation for Microsoft 365 business and enterprise and for consumer products, with the line that users may be unable to connect to multiple Microsoft 365 services. Azure showed no issues on that page. The BBC, at 8:08 pm GMT on 13 November (1:38 am IST on 14 November), reported Microsoft saying it was still draining queued messages and rebalancing traffic, and that it could not say when full recovery would be complete.

›What caused the Microsoft outage?

A Microsoft spokesperson told the BBC, in a statement the broadcaster published at 4:51 pm GMT on 13 November, that it was a technical issue not related to cyber or AI/agents. The spokesperson said the incident was introduced by an issue during an earlier network capacity upgrade that surfaced after a recent network change, that the underlying issue had been addressed, and that service was being restored gradually because of the scale of demand. A full post-incident report was promised after the review. Earlier on Friday, The Hindu reported a Microsoft post on X saying the strain was not from increased traffic but from a number of servers being unexpectedly unavailable.

›Are IndiGo, Air India and Akasa flights cancelled because of the Microsoft outage?

The airlines' own posts, as carried by The Hindu and Mint on 13 November, said flight operations were not the thing that broke. IndiGo said email support was impacted and it might not receive customer emails, and pointed urgent queries to its assistant 6E Skai. Air India said it had temporarily rerouted emails so messages would still arrive, that it would reply within the usual 24 hours, and that voice, AI.g, social media and customer notifications were working. Mint said Akasa Air's email support was impacted and that its advisory gave the Akasa Care Centre number +91 9606 112131, or social media, for immediate help.

›Will emails sent during the Microsoft outage be lost?

Microsoft has not said they will be deleted. The BBC reported that Microsoft extended the email timeout window to 48 hours to protect delayed messages while delivery catches up, and that when a delayed message arrives its timestamp is the delivery time, not the time it was sent. The same report said Microsoft had warned of intermittent access and delayed email delivery, so a message sent during the outage should not be assumed to be in the other inbox immediately.

›When did the Microsoft 365 outage start?

The BBC's timeline of Microsoft posts on X, in GMT, has the first acknowledgement at 5:54 pm GMT on 12 November: users in the Americas unable to access Exchange Online mailboxes. At 6:07 pm GMT Microsoft said the disruption might affect Microsoft 365 connectivity globally. In India, The Hindu, citing Downdetector, said users started reporting problems around 11 pm IST on Thursday, 12 November, with a fresh surge after 6 am IST on Friday.

›Was the Microsoft outage a cyber attack?

Microsoft has said it has no indication of that. The Hindu quoted a Friday service-health update: 'As of now, we are not aware of any malicious activity that is causing this incident.' The BBC timeline has Microsoft, at 3:39 pm GMT on 13 November, saying there was no indication of malicious or cyber activity. The spokesperson's later statement to the BBC called it a technical issue not related to cyber or AI/agents.