Microsoft 365 outage drags on as restart fixes "not taking as expected"

Microsoft is still fighting a global Microsoft 365 outage more than nine hours after it began, with the company admitting its restart attempts were "not taking as expected" despite earlier "positive results".

The disruption hit in the early hours of Friday morning, Australian time. Business and enterprise users, along with individual subscribers, found themselves locked out of core productivity services just as the workday approached. The outage ran from Australia through the Americas, and it was still unresolved as of Friday afternoon.

Which services went down?

The failure cut a wide swath through Microsoft's business stack:

• Microsoft Copilot 365
• Microsoft 365 Admin Center
• Microsoft Teams
• Microsoft Fabric
• SharePoint Online
• Exchange Online, leaving users unable to open their mailboxes

Consumer products took a hit too. Outlook and OneDrive both reported troubles, per Microsoft's own status updates.

For Australian businesses, the timing was brutal. The outage landed right at the start of the business day, blocking access to email, chat and document-sharing systems — the basic plumbing of modern work. A company that runs its calendar, meetings and files on Microsoft 365 effectively lost its nervous system for most of Friday.

What does this change for businesses?

The practical question every IT manager should be asking: what's your fallback when the vendor's own infrastructure fails? This outage didn't stem from a cyberattack or a customer-side misconfiguration — it came from Microsoft's servers going "unexpectedly unavailable," as the company itself put it. Redundancy inside one vendor's cloud doesn't help when that vendor's regional infrastructure buckles.

The incident also shows how a single root cause cascades. When Exchange Online mailboxes fail, Teams, SharePoint and Copilot follow, because they all lean on the same identity and infrastructure layer.

A timeline of a bad day

Microsoft first flagged user-reported outages affecting Exchange Online mailboxes across the Americas in the early hours of Friday morning, Australian time.

By 5:35 AM AEDT, the company said it had "determined a portion of infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors."

At 6:31 AM AEDT, the diagnosis changed. Microsoft found the elevated load wasn't driven by a traffic spike — it came from numerous servers "being unexpectedly unavailable," which strained the remaining infrastructure.

At 9:09 AM AEDT, right as the Australian workday started, Microsoft delivered an uncomfortable update: "our actions taken thus far have not provided the anticipated relief."

The first genuinely hopeful note came at 12:59 PM AEDT. "We're seeing positive results with our efforts to restart affected infrastructure and recover server availability in an isolated manner," the company posted.

"We're actively monitoring the performance of these portions of infrastructure to verify stability, which we suspect will support improved availability as these actions are subsequently expanded more broadly," the post continued.

That hope lasted barely an hour. By 2:13 PM AEDT, Microsoft reported the attempted fixes were "not taking as expected."

"We're identifying alternate workstreams that can be applied to increase capacity in the face of sustained traffic management imbalances," the company said in a social media post.

The so-what

Nine-plus hours in, Microsoft was still wrestling with what it calls "sustained traffic management imbalances" — vendor-speak for infrastructure that won't rebalance itself even after a restart. Until Microsoft lands its "alternate workstreams," businesses should expect continued spotty availability across Teams, Exchange, SharePoint and the rest of the 365 suite, and plan Monday's critical communications accordingly.