Microsoft Tackles Exchange Online Outage That’s Slowing External Email Flow

Microsoft confirmed an ongoing disruption to its Exchange Online service that is causing noticeable delays and "Server busy" errors for email sent to or received from addresses outside the Microsoft 365 ecosystem.

Exchange Online, the cloud‑based email component of the broader Office 365 suite, powers the inboxes of millions of businesses and individuals worldwide. When the platform experiences a hiccup, the ripple effect can be felt across corporate communications, partner interactions and time‑sensitive transactions.

Users reporting the issue have described messages queuing for extended periods, bounce‑back notices that reference server overload, and intermittent failures when attempting to deliver mail to external domains. The problem appears limited to cross‑domain traffic; internal Microsoft‑to‑Microsoft messages are reportedly functioning normally.

The incident was first flagged on the Microsoft 365 Service Health dashboard earlier today, prompting the company’s engineering teams to launch a dedicated response. According to the status page, technicians are actively diagnosing the root cause and working to restore full connectivity.

For organizations that rely on Exchange Online as a primary communication channel, the outage can impede workflow, delay client responses and, in worst‑case scenarios, stall critical business processes that depend on timely email delivery.

While Microsoft has weathered similar service interruptions in the past, the company typically aims to resolve such outages within a few hours, leveraging its global data‑center network and automated remediation tools. Past incidents have underscored the importance of diversified communication plans, but the scale of the current disruption appears limited to external mail routing.

Microsoft has advised customers to monitor the official Service Health portal for real‑time updates and to consider temporary alternative channels for urgent outreach. The firm expects to lift the incident flag once normal mail flow to external domains is re‑established, though no exact resolution timeline has been provided at this stage.