Microsoft Restores Outlook, Teams and Copilot After 24-Hour Outage

⚡ The 5-Second Summary

• Microsoft announced the restoration of Outlook, Teams and Copilot: the outage lasted more than 24 hours.
• Microsoft 365 was affected in both business and consumer plans; complaints came from more than 70 countries.
• The cause was described as technical, not an attack. A postmortem with a step-by-step timeline is promised later.

🔍 What Happened

Early Saturday morning, Microsoft wrote on X: "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 first registered the failures shortly before 1:00 p.m. Eastern Time on Thursday. On Thursday, Downdetector received more than 130,000 complaints, and by Friday morning the flow began to subside — details and quotes are compiled in CBS News' report.

Email broke, along with everything that relies on it. The problems revolved around Exchange Online: without it, Outlook, Teams and the Copilot assistant went down. More than 430 million people use Microsoft 365 apps — that's the overall audience size, not the number of affected users. The wave also reached neighbors: OpenAI and Anthropic reported difficulties connecting to Microsoft 365 tools. Workhorse Group postponed its quarterly earnings call.

Microsoft described the cause as technical. Australia's Minister for Home Affairs Tony Burke relayed a conversation with Microsoft's leadership in the country: there, the outage was compared to the 2024 CrowdStrike story — "an update that went wrong". Executive Vice President for Copilot, Agents and Platform Charles Lamanna admitted that "technical challenges and failure modes" made the recovery "harder than usual", and promised a postmortem with a timeline.

🧠 Our Take

Our assessment: this isn't about Outlook. Exchange Online is the shared foundation for mail, calendars, chats and AI add-ons. A single failure at this level hits a dozen products at once, and the list of affected services grows on its own. Agents and Copilot have also added new API clients — the complaints from OpenAI and Anthropic best illustrate just how interconnected everything has become.

What it changes for business: a couple of hours without email isn't a lost deal, it's stuck approvals and delayed reports. From experience, companies rarely switch office suites after days like this. But they do start seriously discussing a backup channel and service-level clauses. That's where Microsoft will lose money — in negotiations, not in subscriber churn.

The CrowdStrike comparison, honestly, favors Microsoft. Back then, a buggy update crashed millions of machines, grounded planes and shut down banks. Here, a cloud service broke, and the fix was handled on the vendor's side. The difference is huge — but even that was enough to make IT directors remember last July.

⚠️ What We Don't Know

There are no key numbers: how many customers were affected and exactly how many hours each service was down. "A technical issue" is not a diagnosis. The CrowdStrike comparison came from the Australian minister, not from Microsoft: it's a retelling, not an official statement. The postmortem hasn't been released yet. And keep in mind: Downdetector counts complaints, not people — 130,000 reports could come from a single office of a thousand employees.

Forecast: within the quarter, Microsoft will publish a postmortem, but without specific figures on compensation, while large corporate clients will start writing measurable downtime penalties for email outages into their contracts.

Source: CBS News