Gmail problems with Exchange ActiveSync resolved
The Gmail app has not had problems with Exchange Online accounts for the first time. Google has now fixed the recent outages.
(Image: Jess Rodriguez/Shutterstock.com)
About two weeks ago, it became known that there were problems processing emails on Microsoft Exchange Online accounts with Gmail. Since the beginning of May, user complaints have increased, and there were again issues with the Exchange ActiveSync protocol.
The issue reports indicated that logging into the Microsoft 365 Exchange Online access was no longer possible. An error message suggested checking the account information or using modern authentication. A Google spokesperson has now responded to heise online's inquiry and stated that the issue has now been resolved.
Gmail Problem Over Time
According to Google, the current issue was corrected at the end of last week. A post on the Google Workspace Status Dashboard discusses the details. The disruption reportedly began on Wednesday, May 6, 2026. From May 16th, Google's IT specialists investigated the issue. On Monday of last week, they suggested using the Microsoft web app as a tip for affected users to access the Exchange Online inbox. According to an entry from Tuesday of last week, the programmers were then able to narrow down the error and create a new version of the Gmail Android app that contains a fix resolving the blockage for those impacted. Users who have already received the new app version can log in again and sync their accounts successfully.
On Friday before the weekend, Google added that app version 2026.05.11 of Gmail will be released in the Google Play Store. It contains the aforementioned bug fix. Converted to Friday at 00:00 midnight in our time zone, Google then marked the problem as resolved.
Videos by heise
However, Google does not state the actual cause of the issue that prevented users from logging into their Microsoft Exchange Online accounts with Gmail. Google does not confirm the suspicion of some affected users that Microsoft's enforcement of the Exchange ActiveSync protocol in version 16.1 since March 1, 2026, was the trigger.
(dmk)