Update 1/20/2022: We have edited this post for clarity based on customer feedback.
Over the last few years, we have invested heavily in Microsoft Graph to enable developers to access the rich data ...
Updated Jan 20, 2022
Version 5.0
Blog Post
So just to confirm again as WGroenestein asked earlier (and I do see it was responded to), after the stated date, no new apps will be able to be granted the EWS.AccessAsUser.All API permission? Seeing as that permission is so universal and we're only talking about a small portion of API's being deprecated, this particular step seems like going too far, and in parallel, barely calling attention to this.
When I'm using EWS Managed API, I'm doing all kinds to basic EWS stuff that isn't part of any one of those API's. Like Folder.FindItems, or ExchangeService.FindItems, or Folder.Emtpy, etc. I don't even know what sub-API these fall into. My understanding was the the API in this case is Exchange Web Services, though I realize EWS (the web service) has the SOAP/XML interface that is the main function (as opposed to the 'managed API').
I just don't get why you're selling this as though you're deprecating a few of the EWS API's, but then you're taking away any net new ability to setup new apps to use the non-deprecated API's. Seems less than open book and more like trying to pull something off without getting called out before it happens.