
Business
Microsoft Says Its 365 Outage Is Over and Blames an Earlier Network Capacity Upgrade
Service was restored to the last affected customers early Saturday, about a day and a half after Outlook, Teams and other Microsoft 365 apps began failing. Microsoft has apologized and promised a full post-incident report.
Redmond, Wash. · Priya Shah, Business · Nov 15 2026
REDMOND, Wash. - Microsoft said early Saturday that it had restored service to the last customers hit by the outage that knocked out Outlook, Teams and other Microsoft 365 apps for businesses and governments around the world, and it has traced the failure to a problem introduced during an earlier upgrade of its network capacity.
“We have completed our efforts to address the underlying issue of the incident and restored service to the remaining impacted customers and regions,” the company’s Microsoft 365 Status account posted on X at about 1 a.m. Eastern time on Saturday. It pointed administrators to incident MO1550821 in the Microsoft 365 admin center for further updates.

Screenshot: @MSFT365Status on X
The problems began shortly before 1 p.m. Eastern time on Thursday, Nov. 12, CNBC reported, and spread through the Asian and European business days. Outlook, SharePoint and Copilot were among the services that went down, and companies that depend on Microsoft felt it too. Workhorse Group, the electric truck maker, pushed back its quarterly results, and Britain’s National Health Service said some of its services were affected, according to CNBC.
Microsoft first described the trouble as elevated load across multiple regions after a number of servers became unexpectedly unavailable, straining the rest of its infrastructure. Engineers brought servers back gradually and extended the window in which delayed email keeps retrying delivery to 48 hours, CNBC reported.
By Friday afternoon, Microsoft had an explanation. “This was a technical issue not related to cyber or AI / agents,” the company wrote in a post that opened with an apology. “The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change.”
“We are deeply sorry for the disruption this incident has caused our customers and partners,” the post said. Microsoft added that it had restored services gradually, validating stability at each stage, and that “while this took longer, it helped ensure a stable restoration.” It said it would publish a full post-incident report once its review is complete.

Screenshot: @MSFT365Status on X
Even after access returned on Friday, Microsoft kept the incident open while it watched the backlog of email built up during the outage. “Due to the severity of impact this incident caused, we’re monitoring for an extended period to ensure no additional mitigative actions are required,” it said late Friday. The resolution notice followed hours later.
Business customers may be owed money. Microsoft’s service level agreement for Exchange Online promises service credits when monthly uptime falls below 99.9 percent, rising from 25 percent of the bill to 50 percent below 99.5 percent and 100 percent below 95 percent, Wired reported. The credits are not automatic. Microsoft told Wired that customers should title their requests “SLA Credit Service Incidents: EX1550543/MO1550821,” and Wired said claims for the November incident must be filed by Dec. 31. Personal and family Microsoft 365 plans are not covered by the agreement.

Screenshot: status.cloud.microsoft
Microsoft’s public service health page reported on Sunday morning that all products were operational. The company has not said when the post-incident report will be published.