Microsoft Investigates Exchange Online Outage Causing External Email Delays
Users report 'Server busy' errors and intermittent failures when communicating with external domains.
Microsoft is currently investigating a service disruption within Exchange Online that is hindering the flow of emails between internal users and external domains. The outage has resulted in intermittent delivery delays and the appearance of "Server busy" errors for affected users.
Microsoft officially acknowledged the incident, tracked under service alert EX1467029, at 02:19 AM EDT. According to the company, the issue specifically impacts users attempting to send and receive email messages from external domains. While the disruption is intermittent, it has created a bottleneck for organizations relying on the cloud-based mail service for outside communication.
A Pattern of Disruptions
This latest incident arrives amid a period of instability for Microsoft 365. Earlier this same week, the platform suffered a massive outage characterized by widespread authentication and connection failures. This follows a separate incident in June that disrupted mail flow across North America, Europe, and the Asia-Pacific (APAC) region. These recurring events have placed a spotlight on the stability of Microsoft's integrated cloud ecosystem.
Enterprise Implications
Because Exchange Online serves as the primary communication infrastructure for millions of businesses worldwide, even intermittent failures in external mail flow can have significant operational consequences. The inability to reliably communicate with clients, vendors, and partners can delay time-sensitive transactions and disrupt critical business workflows. For enterprise customers, these repeated disruptions raise broader concerns regarding the reliability of centralized cloud services for mission-critical infrastructure.
Current Status
Microsoft continues to investigate the root cause of alert EX1467029. While the company has confirmed the nature of the impact on external mail flow, a definitive cause for the "Server busy" errors has not yet been publicly detailed. Administrators are advised to monitor the official service health dashboard for updates on the resolution process.