Microsoft 365 Outage: 5 Things We Know And Don’t Know
‘We know the trust they place in our services and take that responsibility extremely seriously,’ Microsoft said Friday.
Microsoft still had not provided an estimated time for fully resolving its massive Microsoft 365 outage as of Friday evening Eastern time, more than 30 hours after it began investigating Exchange Online problems Thursday morning.
The vendor’s latest post to the X social media network at 1:55 p.m. Pacific said it continued “to observe sustained service recovery across the previously affected environments” and was “monitoring for an extended period to ensure no additional mitigative actions are required” due to the severity of the impact.
“In parallel, we’re monitoring the backlog of email messages accrued during this event to ensure all process [sic] successfully before considering the issue resolved,” Microsoft said on X.
A spokesperson for the Redmond, Wash.-based technology giant issued an apology Friday morning, saying in an email to CRN that “we are deeply sorry for the disruption this incident has caused our customers and partners.” Microsoft is promising a full post-incident report once its review is complete.
“We know the trust they place in our services and take that responsibility extremely seriously,” according to the statement. “We are seeing broad recovery and stability across our services.”
Kelly Yeh, president of Microsoft solution provider Phalanx Technology Group, said failover measures should have protected customers during a prime business period. “I expect a full explanation about what caused the outage and steps Microsoft will take to avoid this from happening again,” Yeh said.
Of more concern than the short-term financial impact is the reputational damage the outage may have caused, investment firm William Blair said in a report Friday. The Microsoft 365 productivity application suite is used daily by hundreds of millions of commercial users, with communications, collaboration, security, administration and AI workflows dependent on the platform.
Users will have to reevaluate the tradeoff of vendor consolidation and operational simplicity compared to managing a single point of failure and the more-expensive but more-resilient multi-vendor redundancy strategy, according to the investment firm.
Here’s what to know about how the outage unfolded and how the channel stepped up to help clients.
Microsoft Blames Earlier Network Upgrade, Promises Full Report
Microsoft said the outage was caused by “a technical issue not related to cyber or AI / agents.”
“The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change,” according to Microsoft’s Friday statement. The company said it addressed the underlying issue and restored services gradually to validate stability given the scale of demand.
Microsoft is promising a full post-incident report once its review is complete.
Charles Lamanna, Microsoft’s executive vice president of Copilot, agents and platform, emailed CRN a statement Friday that “we know our customers rely on our services to get important work done every day, and regret the impact these outages had on those who depend on us.”
“Our teams are reviewing what happened and how we can prevent similar issues going forward,” Lamanna said.
Solution Providers Show Up For Customers
Microsoft solution providers turned to phone calls, text messages, email-continuity tools and endpoint pop-ups to help customers navigate the outage.
They told CRN they were surprised that an incident of this scale could hit a cloud provider as large as Microsoft and called for transparency in the post-incident report.
Corey Kirkendoll, CEO of 5K Technical Services, used OpenText email continuity while calling and texting customers. “Almost all of our customers are affected and calls are rolling in,” he said. Some customers even asked about moving to Google products.
Bob Venero, CEO of Future Tech Enterprise, said businesses lost “millions and millions of dollars” and called the outage a warning about overdependence on hyperscalers. His company is exploring on-premises email alternatives, although Venero would prefer Microsoft to offer an on-premises or air-gapped version of Microsoft 365 or Outlook.
David Stinner, president of US itek, used Invarosoft endpoint pop-ups to notify customers and receive maintenance tickets. That “eliminated hundreds of phone calls into our help desk,” he said. “You can’t just rely on email for ticketing and communicating with customers.”
Jason Wright, CEO of Avatar, said businesses need multiple ways to communicate when cloud services fail. “We’re moving from an era where businesses expected technology to always be available to an era where resilience is measured by how well they operate when it isn’t,” he said.
Meanwhile, TD Synnex sent partner-customers an intake form to collect information and evidence for Microsoft service-level agreement credit claims, according to an email reviewed by CRN. The distributor pledged to coordinate submissions to Microsoft and track their progress.
Partner-customers were asked to include the form for each affected customer and include available evidence of the disruption. Microsoft doesn’t typically automatically issue SLA credits to every customer associated with reported service outages, according to the TD Synnex email. Microsoft is also the one making the final determination for credit eligibility and the amount.
A TD Synnex spokesperson told CRN in an email Friday that the distributor “is working closely with our partners and Microsoft following the recent service disruptions to help partners navigate the SLA credit process.”
“We recognize that Microsoft’s immediate focus is ensuring systems are operating smoothly and reliably, and our priority is to support partners through the process and work with Microsoft to make it as efficient as possible,” the spokesperson said.
CRN has asked competing distributors about similar efforts for their partner-customers.
Microsoft’s web page explaining how to request credits notably says that credit requests are accepted only from Microsoft Cloud Solution Provider (CSP) Program members direct solution providers and indirect providers—what Microsoft calls distributors like TD Synnex. Requests aren’t accepted from indirect resellers, according to the vendor.
Microsoft Tries Multiple Fixes As Problems Persist
Microsoft tried a succession of recovery measures Thursday as engineers’ initial actions failed to provide sustained relief.
The vendor first posted about any issues at 7:40 a.m. Pacific Thursday to say it was “investigating reports of users experiencing issues when accessing or using Microsoft Teams functionality in North America,” later posting at 9:09 a.m. that the customer impact had been fully mitigated.
Then at 9:54 a.m., Microsoft published on X a notice that it was “investigating reports of users experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas,” with Exchange appearing to suffer a separate issue from the Teams one. It added minutes later that “the issue may affect Microsoft 365 service connectivity for users in any region.”
Microsoft identified “elevated load across multiple regions, which is likely contributing to the connectivity errors” by 10:35 a.m. and began “redistributing connection traffic across our broader worldwide infrastructure to help balance the load” before pausing all deployments, moving additional traffic off the affected infrastructure and restarting affected servers to return them to service.
Microsoft temporarily limited the types of traffic that could reach affected infrastructure in some locations and rebuilt a subset of affected servers with a previous configuration to see if that prevented the problem.
Microsoft engineers were “seeing positive results” with affected infrastructure restarts and recovered server availability in isolation by 5:59 p.m. They saw “partial recovery across regions” with adjusted traffic protocols, redistributed traffic and strategic traffic blocking measures, but not sustained recovery.
Entering Friday, by 1:24 a.m. Microsoft engineers saw “early stabilization and capacity improvements” and extended email timeouts to 48 hours to preserve delayed messages.
Microsoft pursued recovery actions across its M365 infrastructure in phases with “incremental improvement in several workloads,” but service health remained unstable and capability was still not at baseline.
Microsoft was gradually restoring traffic by 3:11 a.m., with mailbox access and delayed email processing improving. Recovery progress continued into 5:32 a.m. Pacific in North America, Europe and Asia Pacific.
Email queues “significantly reduced” by 6:17 a.m., but intermittent access issues persisted for some users. Sign-in and access continued improving into 12:05 p.m. as traffic rebalanced and the number of queued messages came down. By 1:55 p.m., Microsoft was still monitoring sustained service recovery while also watching the backlog of email messages, with no estimated time for full resolution.
Outage Hits Governments, Businesses, AI Services
Online outage tracker Downdetector recorded around 130,000 Outlook outage reports and 46,000 Microsoft 365 reports near the initial peak, although reports across products may overlap and do not represent unique affected users.
Microsoft 365 services spanning the Teams collaboration application, Copilot artificial intelligence app and Defender cybersecurity tools saw impacts in features interacting with Exchange Online.
Failures extended beyond email to device enrollment, administrative and security portals, compliance-policy enforcement, Microsoft Graph requests, Teams scheduling, Copilot access to work data, Power BI exports, external SharePoint sharing, printing and some Windows 365 Cloud PC connections.
Organizations and government agencies also publicly documented operational disruptions online. Cumberland County, N.C., said employees could not send or receive internal or external email and urged residents to call or visit offices in person.
Workhorse Group, a U.S. industrial technology company, postponed its Thursday quarterly earnings call until Monday because of the outage.
OpenAI reported Thursday that new Microsoft 365 connections might be broken and tools might not work as expected. The ChatGPT maker acknowledged signs of recovery Friday morning.
Outages Remain An Inevitability In The Cloud Era
Cloud services have brought new capabilities and efficiencies to workplaces, but major outages remain a recurring business-continuity challenge for solution providers and their customers.
This latest disruption follows other Microsoft service failures in 2026, including a nine-hour-plus Microsoft 365 outage in January that affected Teams, Outlook, Exchange Online, Purview, Defender XDR and other products, plus a four-hour, 25-minute Copilot outage in June.
Other major outages in 2026 include Cloudflare’s six-hour, seven-minute outage in February for users of its Bring Your Own IP service and Verizon’s wireless voice and data services outage that resulted in $20 credits for impacted customers.
Google Gemini experienced an outage in June and Anthropic saw elevated Claude error rates in April in other noteworthy examples.
Should Microsoft pay out SLA credits, it should experience a manageable financial impact, William Blair said in a Friday report. The investment firm considered any reputational impact the more consequential consequence, with enterprises reviewing their dependence on a single vendor.
However, the firm still sees Microsoft maintaining its competitive position in the near term due to the high cost and complexity of replacing deeply embedded productivity workflows.
In the long run, more customers could explore competing productivity application suites like Google Workspace.
The outage also notably comes the week of Claude maker Anthropic revealing some of its own productivity apps, including betas for the Microsoft Word-esque Claude Whiteboards and the Excel-esque Claude Sheets spreadsheet app.
Claude Data—formerly called Dashboards—became generally available Tuesday as a way to interact with company data and might bring to mind Microsoft Power BI.
Independent data protection and recovery vendors including Rubrik, Commvault and AvePoint—and their solution provider partners—could see a surge in demand due to the incident
