The short version

Microsoft reported recovery of affected cloud services following a disruption spanning Thursday and Friday; the company did not attribute the incident to a cyberattack or AI agents.

Cloud services restored after widespread problems

Microsoft said affected services had fully recovered following a broad Microsoft 365 disruption that impaired Outlook, Teams and other business tools across multiple countries. Users, companies and public institutions had reported problems beginning Thursday, November 12, with recovery extending into Friday. The latest restoration statement is a provider update rather than a guarantee that every individual account or downstream system experienced recovery at exactly the same time.

What Microsoft has said about the cause

According to reporting by the Associated Press, Microsoft linked the disruption to a problem during a network-capacity upgrade following an earlier network change. The company said it was not caused by a cyberattack or autonomous AI systems. Investigation and incident-review details may develop further. These statements concern the Microsoft outage, not the separate FAA air-traffic-control communications failure that disrupted U.S. flights on November 13.

Why the incident matters

The interruption affected everyday email, collaboration and business processes used by organizations across the globe. It illustrated how reliance on shared cloud platforms can transmit technical failures across otherwise unrelated industries. Organizations can review continuity plans, alternative communication routes and incident-status monitoring, while users should rely on the provider's official status channels for new service advisories rather than assume a past news report reflects live system availability.

Follow the evidence

Sources & transparency

Associated Press — Microsoft says services fully restored after global outageReuters — Microsoft restores Outlook and Teams service after global outage

Original CDN News coverage. Sources are linked for reference.

Source linked ·

Request a correction