Microsoft services return after global Microsoft 365 outage

By Elena Vasquez

Microsoft said at 10:39 AM on Friday that service availability and email delivery performance were improving across a growing portion of the infrastructure hit by Thursday afternoon’s global Microsoft 365 outage.

The disruption took down Outlook, Teams and Copilot 365, according to Microsoft’s account of the incident. It affected businesses and organizations around the world. Health care providers, schools and governmental bodies were among the users affected, turning service continuity into a practical issue for workplaces and public services rather than a consumer inconvenience alone.

When did Microsoft start restoring service?

Microsoft worked overnight after the Thursday afternoon issue. Around 10 PM ET, the company said some attempts to “improve serviceability” had not worked as hoped. It had not yet declared the incident fully resolved.

The timeline matters because the first recovery effort had not worked as hoped. Microsoft tied better stability and capacity to traffic optimization as the recovery progressed.

By 2:45 AM Friday, Microsoft said it was “seeing positive results for service stability and increased capacity as a result of our latest traffic optimization actions.” That update marked the clearest early sign of progress, although the company still described its work as a recovery process.

Around 8:30 AM, Microsoft reported “continued recovery progress across affected regions, with broader improvements in North America, sustained improvements across much of Europe and encouraging recovery signals in Asia Pacific.” The regional picture remained uneven, but each of those areas showed gains.

Microsoft’s wording also showed the unevenness. It described “broader improvements” in North America, “sustained improvements” across much of Europe, and only “encouraging recovery signals” in Asia Pacific.

An update 45 minutes later said some people could still face delayed email deliveries in Outlook or spotty connectivity. Microsoft also reported “sustained improvements” in the availability of affected services.

The company had not yet said every affected user had normal service. Its alerts remained focused on specific symptoms, including delayed messages and inconsistent connections.

The company’s 10:39 AM update provided the clearest summary of the recovery to that point: “We’re seeing encouraging recovery progress, with service availability and email delivery performance improving across a growing portion of affected infrastructure.”

Microsoft then acknowledged the cost to users: “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.”

That sequence shows a gradual restoration rather than a single clean switch back to normal. By late morning, Microsoft reported better availability and email delivery, while still warning of delays and intermittent connectivity for some users.

How far did the outage reach?

The documented impact reached calls to emergency services, governments, the House of Representatives, court systems, schools and other organizations around the globe.

The affected groups included:

• Calls to emergency services
• Governments and the House of Representatives
• Court systems
• Schools and health care providers
• Businesses and organizations worldwide

Microsoft’s public updates gave times and regions but no total customer count, no single global restoration time and no final root cause. The breadth of the documented impact therefore mattered more than Microsoft’s broad descriptions of improving availability.

That breadth turned the incident into a test of organizational resilience. When one provider’s email and collaboration services fail, the documented consequences reached public offices, health care workflows and court operations during the same working day.

The UK’s National Pharmacy Association said the email issues could cause “delays to some prescriptions.” That warning showed how a communications failure could become a delay in a specific health care workflow.

The association did not say all prescriptions were delayed, and the outage report did not quantify the effect. The warning still connected email availability to a concrete process rather than a generic office productivity complaint.

In Japan, where the report said most businesses and institutions use Microsoft services, some companies seemingly went back to using fax machines temporarily. The return to fax provided an old-fashioned fallback when digital communication failed, even if the report did not establish how widespread that practice became.

The outage report said the day-long event underscored how important redundancies were for people and organizations. In practical terms, the failures showed the cost of relying on one service without another way to keep essential work moving.

That conclusion carries weight because emergency calls, courts, schools and prescriptions appeared within the same outage timeline. Redundancy became an operating issue, not an abstract precaution.

How did workers respond?

Some workers in Australia and the UK used the outage as an excuse to clock off early on Friday, according to the report, because it kept them from doing their jobs properly. The disruption supplied an unexpected break from the normal working day.

The report did not provide employer attendance figures or say how widespread early clock-offs became. It described the behavior as something some workers did, not as a coordinated response.

Not everyone welcomed the return to normal. The Japan Times quoted one person describing the transition in stark terms:

“I thought it was heaven because I wasn’t getting any emails at all, but this is just a Microsoft outage, so I’m actually just waiting in line at the gates of hell,” the Japan Times quoted one person as saying.

The reaction split along the same fault line as the outage. Some workers treated lost email as permission to stop, while another person heard the restored service as bad news, a sharp reminder that ordinary digital routines had become the measure of a normal working day.

Email had become part of the workday’s basic infrastructure, so its absence was easy to read as permission to stop. Its return carried a different meaning for people who had already adapted to a day without it.

What caused the failure?

Microsoft said it had not seen any evidence of malicious activity that could have caused the outage. The company had not said every malicious possibility had been ruled out, and the available evidence did not support calling the incident a confirmed cyberattack. It also did not identify a technical cause or publish a benign explanation.

Its updates focused on serviceability, traffic optimization, regional availability and customer impact. They did not provide a technical root-cause account. Microsoft said that, once it had fully resolved the situation, it would release a post-incident report detailing what caused the failure.

The technical account remained incomplete through 10:39 AM. The promised report would therefore arrive after Microsoft finished restoring service, leaving customers to judge the incident against operational explanations rather than a completed root-cause account.

For Microsoft, the next milestone is the promised post-incident report and a clear account of the root cause. For customers, Thursday showed that redundancy is not an abstract safeguard when email failures reach emergency calls, prescriptions, courts and schools.