The Release Event
LeadThe update triggered an immediate drop in satisfaction, as device caches cleared and incoming mail failed to reach inboxes.[1] While previous releases focused on routine tweaks, this version became an operational hazard for professionals who rely on the client for time-sensitive business schedules.
Generic Release Boilerplate
Release SummaryBehind the generic release notes, client-side mailbox synchronizers were modified concurrently with backend Exchange Online shifts. The update changed local folder index handling, which flushed local mailbox caches while breaking sorting controls between the Focused and Other tabs. The gap between generic release documentation and broken user mailboxes quickly intensified user anger.
Wiped Inboxes and Downtime
Breaking ChangesAs one 1-star reviewer on v5.2644.0 put it, "Update wiped emails from my devices; two thumbs down." Another 1-star reviewer on v5.2644.0 wrote, "I missed several meetings. You people abruptly stopped your service." Users found the client stuck in an unusable offline state when attempting to open messages.
User Sentiment Shift
User ReceptionAfter version 5.2644.0 arrived, reviews detailed acute frustration with service dependency failures. A thread on r/Office365 noted that authentication and connection brokers failed automated health checks, driving prolonged mobile desynchronization. Archived.
Server Outage Overlap
Root CauseDowndetector recorded nearly 130,000 incident reports as connectivity dropped worldwide.[3] Concurrently, mistaken spam filtering rules bounced legitimate incoming mail back to senders, giving users the distinct impression that correspondence had vanished from inboxes.
Analytical Verdict
Expert VerdictClient resilience appears compromised whenever server degradation forces mobile stores to desynchronize. These figures compare the 156 US App Store reviews tagged with v5.2643.0 against the 71 tagged with v5.2644.0, measured on 2026-11-16.