Upcoming API Deprecations in Exchange Web Services for Exchange Online

I think it would be good for Microsoft to provide some more clarification on the following statement "Today, we are announcing that we are going to remove the ability to create new EWS apps starting September 30, 2022.". Does it mean we can no longer add the "EWS.AccessAsUser.All" permission to new Azure Active Directory apps? If so, does it apply to both UI and API operations? How does Microsoft propose developers deal with needing to support both Exchange Online and Exchange On-premises ?

This is a major announcement and has the potential to impact every Microsoft customer from the point onward where no new EWS App Registrations are possible.

Right now, the Exchange Web Services API is the only way to get full-fidelity (preserving all properties) email information into and out of Office 365 (see MS-OXWSBTRF). Without this capability, 3rd Party applications addressing backup, eDiscovery, and migration (including Tenant-to-Tenant) will simply not be possible anymore! Also, even if the Graph API is extended to support the missing methods, will MSFT switch to the same "paid" model to use the Graph API as with Teams?  

Imagine the implications of an acquisition or divestiture scenario, where one needs to consolidate tenants and/or on- or offboard legacy data. Cost and Time implications might get enormous, and a lot of restructuring projects will never reach an ROI if suddenly the project costs and timelines multiply.

Completely agree wit JonasBack and stukey 

Microsoft needs to provide reporting so that we can easily identify the apps that are utilizing the impacted EWS APIs (and EWS more generally). I don’t think we can rely on the Azure AD Sign-In logs as they only allow you to filter on Client App, which for EWS is only listed for Basic Authentication connections.

What does that mean, "Today, we are announcing that we are going to remove the ability to create new EWS apps starting September 30, 2022."?

You mean you can't create Azure AD apps anymore with EWS permissions? You're kidding, right?

I agree with Jonas, Microsoft needs to provide reporting so that we can easily identify the apps that are utilising the impacted EWS APIs (and EWS more generally). I don’t think we can rely on the Azure AD Sign-In logs as they only allow you to filter on Client App, which for EWS is only listed for Basic Authentication connections.

Also how do these changes impact the Outlook for Windows and Outlook for Mac clients, since it’s my understanding that both clients still utilise EWS to connect to Exchange Online for some functionality (especially Outlook for Mac - current version, not the new UI version which uses Microsoft Sync Technology).

Renaud_B If you could add what particular methods are missing, I think that would help. Not only Microsoft but also us who talk to customers and vendors so we are aware what is missing and not. Since there is actually no "User Voice" anymore and this Tech Community is one place where Microsoft wants us to provide feedback.

Hello, the main issue we face today is that graph API does not cover all methods covered by EWS. It will be easier to move to graph API if we did not miss some of it. We are now in a situation where we need to do heavy developments using Graph API and EWS. knowing that we will need to do some more developments when those missing features will be covered by graph API. Hope we can use Graph API fully soon. thanks

Way to go! Are there any plans to provide insights if these particular API:s are in use in our tenant(s) so we know if we will be affected of these depreciations?