SHD / MC Checker

[serviceDegradation] EX1228240 | Exchange Online | Users’ MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes



EX1228240 | Exchange Online | Users’ MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes

Status serviceDegradation
Classification advisory
User Impact Users’ MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes.
Last Updated 02/11/2026 19:42:34
Start Time 02/06/2026 18:45:07
End Time
Latest Message Title: Users’ MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes

User impact: Users’ MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes.

More info: This issue is specific to the Outlook desktop client in organizations with a hybrid environment using Exchange Web Services (EWS) for MailTips. Users may notice that the MailTips free/busy feature isn’t operating as expected and may see an error stating “we can’t show MailTips right now.”

The Outlook desktop crashes occur when attempting to add a new on-premises mailbox.

Admins may be unable to create new on-premises mailboxes, and their cross-tenant AutoDiscover requests general may fail from hybrid environments.
While we work on deploying the fix, admins may be able to mitigate the impact by restarting the Autodiscover app pool.

Current status: Our monitoring of the deployment of the fix to prevent the header duplication issue indicates that the majority of admins should be experiencing remediation, and we’re beginning to validate impact resolution with a subset of affected admins as the saturation of the fix fully completes.

Scope of impact: Any admins’ cross-tenant AutoDiscover requests may fail from hybrid environments, causing MailTips free/busy not to show and crashing for users’ Outlook desktop clients when adding additional on-premises mailboxes. This information may be updated as our investigation continues.

Start time: Tuesday, January 27, 2026, at 12:30 AM UTC

Root cause: A routing change for Autodiscover requests introduced a header duplication issue causing a backlog of requests that ultimately fail or timeout, resulting in the impact.

Next update by: Wednesday, February 18, 2026, at 2:00 AM UTC