Blog Post

Exchange Team Blog
1 MIN READ

Outlook REST API v2.0 and beta endpoints decommissioning update

The_Exchange_Team's avatar
Sep 06, 2023

In January 2023 we announced the decision to delay the final decommissioning date for Outlook REST API v2.0 and corresponding beta endpoints. This was done as a response to signals and feedback received from our customers who required more time to achieve a successful migration to Microsoft Graph. At that time, we did not define a new decommissioning date.  

Today, we are announcing that we will fully deprecate Outlook REST v2.0 and beta endpoints on March 31st, 2024.  

After this date, every call to the Outlook REST v2.0 and beta endpoints will result in a HTTP 410 (Gone) error with a deprecation message in the error response. This will only be active for 60 days, after that we will not provide any response. 

If you are using Outlook REST API v2.0 or beta endpoints in your app, you should plan on transitioning to Microsoft Graph as soon as possible. Please refer to: https://aka.ms/FromOutlookRestToGraph for initial guidance.  

It is critical to highlight that this breaking change will not affect Modern Outlook add-ins using Outlook REST where the token was obtained from the Office JavaScript Library.

Please check this change affecting authentication for Add-ins.

We understand that for some applications this change, even if anticipated, will require some amount of work to accommodate, but we are confident it will ensure better security, reliability, and performance for our customers. 

The Microsoft 365 Team

Updated Jul 03, 2024
Version 4.0
  • Andrej_Welther's avatar
    Andrej_Welther
    Copper Contributor

    Please confirm following APPLICATION permissions are not at scope of this decommission:

     

    Office 365 Exchange Online/ReportingWebService.Read.All

    Office 365 Exchange Online/Exchange.ManageAsApp

  • Just to clarify, Is this anything using the Office 365 Exchange Online API? (resourceAppId: 00000002-0000-0ff1-ce00-000000000000 in the manifest), or a more legacy one which may not be visible to all tenants?

    Therefor anything under that API is due for decommissioning? Mail.Read / EWS.AccessAsUser.All / full_access_as_app etc.?

    I only ask as the documentation for authenticating EWS with OAuth (Authenticate an EWS application by using OAuth | Microsoft Learn) still says to use the Office 365 Exchange Online API.

     

  • owainwtb's avatar
    owainwtb
    Iron Contributor

    Hi,

    I've been reviewing this article in regard to this change:

    https://techcommunity.microsoft.com/t5/exchange-team-blog/identify-applications-using-exchange-online-outlookrestv2-or/ba-p/3957435

     

    It states:

    Depending on the API used, there are two locations where the API permissions to connect to Exchange Online can be granted:

    • Azure AD using App Registrations: used for all Exchange Online APIs including OutlookRESTv2, Exchange Web Services (EWS), Microsoft Graph, IMAP, POP, SMTP
    • Exchange Online using RBAC for Applications: used only for Microsoft Graph and EWS applications.

     

    And talks further about reviewing App Registrations.

    In our environment we use Thunderbird and Apple mail as email clients, these use IMAP/POP/SMTP and EWS respectively.

    These applications are represented by an Enterprise Application only, there is no associated App Registration.

    So when I run this script with the "All" switch to export everything, these are not picked up even though they are using the protocols that the script is suppose to find and as stated above.

     

    These are the Thunderbird Enterprise Application permissions, as set by default:

     

     

    These are the Apple mail (Apple Internet Accounts) Enterprise Application permissions, as set by default:

     

    My concern is that as the referenced article and associated script is only talking about and checking App registrations, then Enterprise Apps with permissions in scope of deprecation will be missed if they do not have an associated Application Registration, as for the example given above for Thunderbird and Apple mail. 

     

    Best regards

     

    Owain

  • owainwtb's avatar
    owainwtb
    Iron Contributor

    I assume this change has been implemented as it was due to be on 31/03/2024, no message in the M365 message center to confirm and no update here either.

    Considering the complete lack of engagement by Microsoft, yet again, on these blogs I'm likely talking to myself.

    Appalling support.