Exchange Online outage disrupts IMAP4 mailbox access

What Happened

Microsoft has confirmed an outage affecting Microsoft Exchange Online that intermittently blocks access to mailboxes via the IMAP4 protocol. The incident, recorded as EX1215307, was first reported on Wednesday at 23:35UTC. While Outlook and Outlook Web Access continue to operate normally, users attempting to connect through IMAP4 may experience failed logins or timeouts.

Whos Involved

The outage concerns Microsofts Exchange Online service, which forms part of the Microsoft365 suite used by a wide range of organisations. The issue primarily impacts organisations that rely on IMAP4based mail clients or custom applications that connect to Exchange Online through IMAP.

Key Details

• Root cause: a code conflict introduced in a recent IMAP deployment that created an authentication misconfiguration.
• Microsofts response: a fix has been deployed and the configuration change is expected to be fully applied during the next scheduled update.
• Incident classification: logged as an incident in the Microsoft365 admin centre, indicating notable user impact.
• Scope: no specific regions or user counts have been disclosed.
• Related history:
  • November outage that blocked classic Outlook client access.
  • LateOctober DNS failure affecting Azure and Microsoft365 services.
  • EarlyOctober MFArelated outage that disrupted Teams, Exchange Online and the admin centre.
• Policy note: Microsoft has cancelled the planned April2024 limit of 2000 external recipients per day for bulkemail senders in Exchange Online. This change is unrelated to the IMAP4 outage.

Why It Matters

For organisations that depend on IMAP4 for mail retrievalwhether for legacy applications, mobile devices, or specialised workflowsintermittent disruptions can hinder communication and productivity. The outage highlights several practical concerns:

• Retry guidance: Microsoft has advised that retrying the connection may help regain access after the fix is applied.
• Configuration vigilance: Code conflicts and misconfigurations in cloud services can have direct user impact, underscoring the importance of thorough testing before deployment.
• Monitoring: Robust, realtime monitoring of service health helps detect and respond to such incidents promptly.
• Bulkemail policies: The cancellation of the recipientlimit cap is a separate servicehealth note that may affect how largescale senders manage antispam and ratelimiting strategies.

What To Do

• Check your mail clients error logs for IMAP authentication failures and, where possible, enable automatic retries as suggested by Microsoft.
• Consult the Microsoft365 admin centre for realtime service status updates and guidance.
• If you experience prolonged disruption, consider using alternative access methods (Outlook, OWA) until the fix is fully applied.
• Review any recent configuration changes to your Exchange Online environment to ensure they align with Microsofts recommended settings.
• For bulkemail senders, reassess your sending patterns in light of the cancelled recipient limit and adjust antispam controls accordingly.

Conclusion

While the IMAP4 outage does not affect the core Outlook experience, it serves as a reminder that even wellestablished cloud services can be vulnerable to deploymentrelated misconfigurations. By staying informed through the Microsoft365 admin centre, following Microsofts retry guidance, and maintaining vigilant configuration practices, organisations can minimise the impact of similar incidents in the future.