Clearance CLR-9136 · SAF637

SAFMIC

Safety & OperationsClearance sheet

Microsoft 365 Outage Hits Ten Airlines Across Three Continents

Ten airlines including Emirates, IndiGo and Singapore Airlines lost email and comms channels in the Nov. 12–13 Microsoft 365 outage; SpiceJet cancelled three flights.

Read-back

  1. Microsoft 365 outage ran from ~4:00 p.m. GMT Nov. 12 to at least 7:00 a.m. GMT Nov. 13, affecting 74 countries.
  2. Ten airlines reported impacts: IndiGo, Akasa Air, SpiceJet, Air India, Emirates, Aurigny, CemAir, Vueling, Malaysia Airlines, Singapore Airlines.
  3. SpiceJet cancelled three flights and delayed two at Delhi Airport, hitting Pune, Mumbai and Leh services.
  4. Over 43,000 service-issue reports were logged during the disruption.
  5. Microsoft has confirmed no root cause and no cyber activity; a post-incident report is promised after full mitigation.
Airlines Affected By Global Microsoft Outage
PlateAirlines Affected By Global Microsoft Outage — AS_Photography / pixabay

A Microsoft 365 outage spanning Nov. 12–13 disrupted operations at ten airlines on three continents, forcing SpiceJet to cancel three flights and delay two more at Delhi Airport (DEL). The carrier scrubbed services to Pune, Mumbai and Leh — the clearest operational damage from a cloud failure that knocked out Outlook, Teams and Copilot across 74 countries.

Which airlines were hit?

The affected carriers were IndiGo, Akasa Air, SpiceJet, Air India, Emirates, Aurigny, CemAir, Vueling, Malaysia Airlines and Singapore Airlines. Most saw relatively minor complications, concentrated in email and internal communication systems. In some cases, passengers could not reach airline customer service lines at all.

IndiGo disclosed its exposure in a post on X: "Due to a global Microsoft service disruption, our email support services are currently impacted, and we may not be able to receive your emails." The airline said alternative support channels stayed online, including its AI-powered chatbot, 6E Skai. That is a narrow comfort. If one channel of a carrier's customer-service stack depends on a single cloud tenant, the redundancy question answers itself.

What does the outage actually consist of?

The disruption began at roughly 4:00 p.m. GMT on Nov. 12 and remained ongoing as of 7:00 a.m. GMT on Nov. 13 — a window of at least fifteen hours. Monitoring services logged more than 43,000 reports of service issues during that period.

Microsoft has not confirmed a root cause. Some reports point to server overloads and failed automated health checks, but that remains unverified. The company also has not committed to a time for full network restoration, though it reports improving availability, with email queues slowly decreasing toward normal levels.

Charles Lamanna, Microsoft's Executive Vice President of Copilot, Agents and Platform, said: "We regret that today's outages caused disruptions for our customers, and we are working to address the issue. We will continue to share more information as soon as we have it, and for now I can confirm that there is no indication this is the result of malicious or cyber activity."

A Microsoft spokesperson added: "We're closely monitoring service health and validating recovery across affected connection methods to ensure sustained service stability. At this time, we have no evidence of malicious activity associated with this incident. We will continue to treat this with urgency until full mitigation, and we will share a full Post-Incident Report with root cause and defence-in-depth actions after mitigation is complete."

Note what is missing: a cause, a timeline and a completed recovery. What exists is a promise of a post-incident report after mitigation — a document that will arrive once the failure is over, not before.

What does this change for aviation?

The incident fits a pattern that should concern airline operations teams. Carriers now lean heavily on cloud-based communication and operational systems, and large-scale failures at single technology providers translate directly into network pain — delayed flights, cancelled services and severed customer contact. Two delays and three cancellations at one airport is manageable. A simultaneous outage across email, collaboration tools and support queues at ten carriers is not a worst case; it is a warning.

Microsoft says there is no sign of cyber activity. That leaves capacity and engineering as the likely culprits — the same class of failure that grounded fleets in previous cloud incidents. Airlines that outsource their communication backbone to one vendor will watch the post-incident report closely, and should treat its findings as a procurement question, not just an IT one.

via travelradar.aero (Source)

Filed under

  • microsoft-365
  • airline-operations
  • cloud-outage
  • flight-disruptions
  • it-resilience
Share this article:

More from James Calloway

James Calloway

Show full bio

Staff writer covering people, launches and day-to-day practice in Commercial aviation industry coverage at Flightdeck Report.

650 articles

Same bay

« Previous articleNext article »