Microsoft confirmed on Thursday that failures in its server infrastructure, not a surge in demand, disrupted Exchange Online mailbox access and Microsoft Teams functionality across the Americas and potentially worldwide.

The company disclosed the disruptions through posts on social media, its standard channel for service-status communications. The sequence began with Teams and widened within hours to Exchange Online, the cloud email platform that underpins Microsoft 365 (the company's subscription suite of workplace applications).

"We're investigating reports of users experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas," Microsoft wrote in one post, after first reporting "users experiencing issues when accessing or using Microsoft Teams functionality in North America."

What caused the outage?

Microsoft's initial working hypothesis pointed to capacity. The company said the mailbox problems could stem from infrastructure "experiencing elevated load across multiple regions."

That diagnosis changed as engineers examined the systems. Microsoft later clarified: "We determined the elevated load isn't driven by an increase in traffic, but by a number of servers being unexpectedly unavailable; straining the remaining infrastructure."

The distinction matters for enterprise customers. A traffic-driven slowdown would imply external demand pressure; unavailable servers point to an internal fault within Microsoft's data-centre estate, leaving remaining hardware to carry workloads it was not sized to handle alone.

The company also warned that the mailbox issue carried global reach. "We've confirmed the issue may affect Microsoft 365 service connectivity for users in any region," Microsoft wrote, widening the incident beyond the Americas where it was first detected.

Which services were restored?

The two failures resolved on different timelines, and Teams recovered first.

Microsoft followed up shortly after its first Teams report with a confirmation of repair: "Our mitigative actions have successfully restored service health and functionality."

Exchange Online mailbox access remained the open problem. Downdetector, an independent service that monitors user-reported outages, logged issue spikes for both Microsoft Teams and Outlook, among other Microsoft products, on Thursday — third-party corroboration that the disruption extended to Outlook, Microsoft's desktop email client.

The company continued to publish updates on a potential fix for the mailbox issue throughout Thursday.

What is Microsoft doing to fix it?

Microsoft described a three-part containment strategy, issued while the mailbox investigation was still under way. Its statement set out the steps:

• Pausing all deployments — halting the rollout of new code and configuration changes that could complicate diagnosis or recovery
• Moving additional traffic off the affected infrastructure — rerouting workloads onto healthy servers
• Restarting affected servers — cycling the unavailable machines to return them to service

"We're aggressively pursuing all pathways to reduce impact," the company said. "We've paused all deployments, we're moving additional traffic off the affected infrastructure, and we're restarting affected servers to return them to service."

Why the incident matters for business customers

The outage touches two of the most heavily used products in the Microsoft 365 portfolio. Exchange Online carries corporate email for a large share of the subscription base, and Teams is the company's core collaboration and messaging platform. An incident that degrades both simultaneously, and that Microsoft says may affect users in any region, tests the resilience claims central to cloud-productivity adoption.

For chief information officers, the episode is a reminder that dependency on a single vendor's infrastructure concentrates risk. Microsoft's decision to pause all deployments during the incident indicates the company prioritised stabilisation over its release schedule.

The situation remained unresolved at the time of the company's most recent update. Microsoft has not disclosed how many users were affected, how many servers went offline, or when full restoration is expected.