Microsoft Outage Hits 70+ Countries, Leaves 430 Million Users in the Lurch

Microsoft has apologized for a global outage that disrupted Outlook, Teams and other Microsoft 365 products across more than 70 countries, affecting a user base the company counts at over 430 million people. Services were only broadly recovering nearly 24 hours after the first failures on Thursday afternoon.

The cause, according to Microsoft, was a technical issue introduced during a "network capacity upgrade" — not a cyberattack and not a failure tied to artificial intelligence agents. The company has given no "ETA" for when services will fully recover, though it says it is making "encouraging progress."

"We are deeply sorry for the disruption this incident has caused our customers and partners," a Microsoft spokesperson said. "We know the trust they place in our services and take that responsibility extremely seriously."

What does this change for businesses that run on Microsoft?

For a single day, the answer was: almost everything. The outage cascaded from multinationals to national governments and solo traders. In the US, House of Representatives staff told Politico the disruption set back an entire day of legislative work because everything runs on Outlook. Canada's national rail network warned passengers they might not receive email trip updates, and hospitals across the country reported email problems.

The UK saw impacts on parts of the NHS, including GPs and hospitals, plus some schools and police forces. UK cyber minister Liz Lloyd said the incident had "limited" impact on critical frontline services such as 999 calls, and that the transport network saw no disruption.

The list of affected institutions runs long:

• The Japanese government and the Philippines Supreme Court
• The Australian spy agency
• Trains, hospitals and courts in North America
• Some Singapore government systems
• Officials and advisers at the COP31 climate summit in Antalya, Turkey, who couldn't access Outlook

Smaller operators felt it just as sharply. Peter Pentz, a winemaker on South Africa's Cape West Coast, said his entire business was basically brought to a "standstill" — export communications froze and "critical production work" halted because the winery "relies on these systems for parts of our day-to-day operations."

The outage also reached into personal finances. Georgia, a buyer in Staffordshire, England, was due to complete her first house purchase on Friday after an eight-month wait. Her solicitor warned of delays because agencies couldn't be contacted. "We're not the only one completing today, there are hundreds of houses and for them to ring everyone in time is unfeasible," she said.

How did the recovery unfold?

The timeline matters for anyone mapping Microsoft's incident response. The company first acknowledged at 17:54 GMT on Thursday that users in the Americas couldn't access Exchange Online mailboxes, and shortly after warned the disruption could be affecting Microsoft 365 globally. By 04:36 GMT on Friday, it was reporting only a "partial recovery" in some regions.

At 13:32 GMT, Microsoft reported "broader improvements" in North America, "sustained improvements" across much of Europe and "encouraging recovery signals" in Asia Pacific. The company said it restored services gradually because of the scale of the problem, and to keep services stable once back online. A full post-incident report will follow once its review is complete.

Why there's no easy fix for next time

Security experts say the deeper issue is concentration risk. "The global Microsoft outage is a stark reminder of how heavily we rely on a handful of big tech providers," said Rob Demain, chief executive of cybersecurity firm e2e-assure.

Matt Saunders, field chief technology officer at tech consultancy Adaptavist, put the practical problem bluntly: "Classic IT disaster planning strategies suggest using a second service for resilience, but in practice, it's almost impossible for a business to function without tools such as Microsoft." His advice for operators: "In the wake of this outage, organisations must have a plan in place for how to work without such tools, for when incidents like this occur."

The takeaway for IT leaders is uncomfortable but simple. Redundancy across vendors is the textbook answer, yet the outage showed that a single failed capacity upgrade can stall legislatures, hospitals and house closings at once. The post-incident report, when it lands, will be the document to watch — it will show whether Microsoft can explain a nearly day-long global failure without denting the trust its 430 million users are already lending it.