are there any plans for implementing Microsoft Graph protocol for Microsoft Exchange online accounts?
Microsoft announced: on October 1, 2026, we will start blocking EWS requests from non-Microsoft apps to Exchange Online.
Sources:
The date is getting close.
I’m interested in this topic because I currently cannot setup my work account via EWS. It’s Microsoft online hybrid account (Mailbox Exchange online is connected with on domain account).
I can only connect to my account using “Outlook” option when adding an account. But then I can access mail only (IMAP, SMTP). Calendar and contact are not available.
I’m communicating with support but with no luck so far.
I was thinking.. EWS is deprecated protocol anyway (for Exchange online), maybe implementing Microsoft Graph will help.
Hello, in fact we internally have implementation of MS Graph protocol ready for almost 2 years. The problem is the protocol is very buggy on Microsoft side, changing all the time with new and new issues, so we decided not to use it yet. We’ll see whether and when Microsoft will resolve these issues (some of these are really major ones). It is on their road plan to replace EWS with MS Graph and we are ready for that, Microsoft is not.
Imagine a scenario where you see no improvement on the issues you described, and October 1 comes, and Microsoft follows through with blocking non Microsoft apps, what will you do then?
Will you deprecate support for Exchange Online, or switch over to Graph, despite the issues?
We are now revisiting our support of MS Graph, but it still has several issues on MS side that they need to resolve to be a real alternative for EWS. We are working on some workarounds, but we need some work to be done on MS as well. However we’ll be ready for the switch the best way possible, I can assure you about that.
Everything else is fully implemented on our side and it works. With all the items from the list above we have to wait on Microsoft. We doubt they’ll make it until EWS is fully deprecated.
I believe this is intentional and part of their vendor locking strategy.
The app I use in Android (not eM Clinet) updated yesterday to use the Graph API. Now a lot of people (me included) have an issue where we can’t authenticate that way because when using Graph, O365 admins have to specifically approve the app and it’s requested data access scope. A lot of enterprise users of third party apps are going to be disappointed when their admins refuse this extra work and just direct them to use Outlook / Outlook Mobile.
From what little I have read about this issue, it may be a result of the third party app asking for data access permissions outside of the users specific folders / account.
Is the eM Client team aware of this? If this will be an issue, wonder if some kind of access level config may be prudent when setting up a Graph authenticated account (aka Limited User Only, Shared, Maximum).
The app I use in Android (not eM Clinet) updated yesterday to use the Graph API. Now a lot of people (me included) have an issue where we can’t authenticate that way because when using Graph, O365 admins have to specifically approve the app and it’s requested data access scope. A lot of enterprise users of third party apps are going to be disappointed when their admins refuse this extra work and just direct them to use Outlook / Outlook Mobile
Then I would use eM Client app which works atm. You would need to contact your other mobile app technical support for assistance as sounds like they have pushed it out way to early.
Microsoft haven’t even officially started to disconnect EWS yet till October onwards and will have more work to do their end before Depreciation. I wouldn’t expect it to work yet.
Yeah, I didn’t bring this up expecting anyone to care about the other email app. I just wanted to know if the eM Client devs were aware of the potential for issues with the access limits and extra admin work on the O365 side.
I think things like asking for blanket permissions to company public or other users shared folders could trigger this “admin required” block.