Microsoft 365 Outage Hits Day Two: Outlook, Teams, Copilot

0

Microsoft blames a network-capacity upgrade and a later network change for the disruption, says it was not a cyberattack, and warns some users may still see delays

Microsoft building with Outlook, Teams and Copilot icons beside an outage warning
Microsoft says recovery is progressing after the global outage disrupted Outlook, Teams and Copilot services.

A global Microsoft outage that began on November 12 stretched into a second day, leaving businesses, schools, government offices and healthcare organizations struggling to reach email and some other workplace tools. By the November 13 update, Microsoft said recovery was broadening, but it cautioned that some customers could still experience intermittent access problems and delayed email delivery.

Outlook was the most visible casualty, though the trouble was not limited to it. Microsoft 365, Exchange Online, Microsoft Teams and Copilot all appeared in the incident, along with services such as SharePoint and Defender.

How the Outage Began

Microsoft began reporting problems accessing Outlook mailboxes shortly before 1 p.m. Eastern Time on November 12. The company first described the problem as affecting the Americas, then warned that users in any region could be affected.

Within roughly an hour, Downdetector had logged outage reports from 74 countries and territories, according to figures reported by the Associated Press. USA TODAY reported that Outlook outage reports approached 130,000 at their peak, and that earlier Microsoft 365 reports topped 47,000.

Those numbers come with an important caveat. Downdetector tallies problem reports submitted by users, so the totals show the scale of the reaction but are not a verified count of affected customers. The same applies to the more than 450 million paid commercial Microsoft 365 subscriptions the AP cited: that figure describes Microsoft's customer base, not the number of people who lost access.

What Microsoft Says Went Wrong

Microsoft's explanation changed as its engineers learned more. The company first reported elevated load on its infrastructure. Further investigation pointed to servers that had become unexpectedly unavailable and to problems with automated server health checks.

Early recovery steps did not hold. Microsoft paused deployments, redirected traffic and restarted affected servers, then brought infrastructure back gradually while checking that the servers stayed stable.

In its November 13 statement, Microsoft said the root problem was a technical issue introduced during an earlier network-capacity upgrade that surfaced after a later network change. The company said it had addressed the underlying issue and was continuing to restore service for remaining customers and regions.

The public record does not yet say exactly which component failed or how each step unfolded. Microsoft has promised a full post-incident report once its review is complete.

Cyberattack and AI Ruled Out, Company Says

With so many services down at once, questions about security and Microsoft's growing AI products came quickly. Microsoft addressed both in plain terms:

"This was a technical issue not related to cyber or AI / agents."

Charles Lamanna, Microsoft's executive vice president of Copilot, Agents and Platform, said the company was reviewing what happened and how to prevent similar problems. Microsoft also apologized to customers and partners on November 13.

What Was and Wasn't Affected

Impact varied by service, and not everything stopped working.

  • Outlook: Users reported trouble opening inboxes, and some could not send or receive mail normally. Delivery was delayed, and mailbox access and email queues were affected.
  • Teams: Microsoft said core functions, including joining calls and meetings, group chats and channel messages, were not affected in the relevant update. Calendar features that depend on Exchange Online did have problems, including scheduling, invitations, and viewing or editing meetings.
  • Copilot: Some functions and integrations were disrupted, but not every Copilot feature was unavailable.
  • Other services: Exchange Online, SharePoint and Defender were among those named in incident reporting, with different levels of disruption.

Why Email Takes So Long to Catch Up

Readers may wonder why mail can still arrive late after Microsoft says a service has recovered. Email works on a store-and-forward model: when a receiving system is unavailable, messages pile up in queues and are retried later. Fixing the underlying service therefore does not instantly clear the backlog, and some messages can arrive hours behind schedule. PBS NewsHour has published a detailed explainer on why restoring email can take so long.

Who Felt It

Businesses reported communication disruptions, and the AP reported impact on government agencies, schools, healthcare organizations and some law enforcement and public services. The episode shows how much day-to-day work now runs through a single provider's cloud infrastructure, since one provider's trouble can reach very different kinds of organizations at the same time. Total financial losses have not been established.

Where Things Stand

As of the latest research check on November 14, Microsoft had reported broad recovery and improving stability, and said email queues were approaching normal levels in its November 13 update. It reported broader recovery in North America, sustained improvement across much of Europe and encouraging signs in Asia-Pacific.

The picture is not fully settled. Microsoft's public service-health page was still showing service degradation for Microsoft 365 business and enterprise services and for consumer products. That page is dynamic, and what it displays does not by itself prove every listed issue is tied to this incident. Still unconfirmed are the final number of affected users, total losses, the exact number of affected servers, the complete technical failure sequence, and the recovery time for every region.

Customers can follow live updates on Microsoft's official service-health page at status.cloud.microsoft, while the company's promised post-incident report should provide the detailed account of what went wrong.

Post a Comment

0 Comments
* Please Don't Spam Here. All the Comments are Reviewed by Admin.
Post a Comment (0)
To Top