Office-js-docs-pr: Outlook v2.0 REST API deprecation inquiries

Created on 18 Dec 2020  路  6Comments  路  Source: OfficeDev/office-js-docs-pr


Inquiries on impact of the Outlook REST v2.0 API Deprecation

Article URL


https://docs.microsoft.com/en-us/previous-versions/office/office-365-api/api/version-2.0/use-outlook-rest-api

Issue


Hello Microsoft,

Recently, we found out that the Outlook V2.0 REST APIs will be deprecated and will not be supported anymore. This is according to this documentation : https://docs.microsoft.com/en-us/previous-versions/office/office-365-api/api/version-2.0/use-outlook-rest-api

That being said, I would just like to confirm my understanding :

  1. Starting November 17, 2020, there will be no more support/bug-fixes/updates for the Outlook V2.0 REST APIs. Correct? So if a bug was found in one of the V2.0 APIs, it will not be fixed anymore even if a github ticket was filed for it. Is my understanding correct?

  2. On November 30, 2022, all add-ins and applications using the Outlook V2.0 REST APIs, will not work anymore because of the decommissioning of the APIs. Is my understanding correct?

  3. Finally, how about the Exchange Web Service (EWS) SOAP APIs? Are they affected by this deprecation? Or will the support for EWS-APIs be continued? If these too were to be deprecated, what is the timeline for such?

Thank you very much and more power.

Outlook Needs product question

Most helpful comment

@glr0221 thanks for your inquiry.
Answer is yes for 1 and 2. Also:

The recommendation on that page is exactly the same for any client consuming Outlook v2.0 REST API, that included Outlook Add-ins, so basically you need to move to the Graph all such calls using Outlook REST APIs v2.0. Please check our documents and samples (i.e. script lab) on how to do this.

In addition to this, we also recommend you to use our SSO auth feature. in case you need to call APIs other than the Outlook scope.

Finally, this has no relationship whatsoever with our EWS Services, that is not affected by this issue.

All 6 comments

@glr0221 Thanks for asking about this. Assigning to @JuaneloJuanelo to take a look.

Thanks.

@ElizabethSamuel-MSFT. before anything else, Happy new year to all of you!!! As for this ticket, it seems that @JuaneloJuanelo is a bit busy. Any chance we can ask somebody else knowledgeable of this? Thank you.

@exextoc, could you please investigate?

@glr0221 thanks for your inquiry.
Answer is yes for 1 and 2. Also:

The recommendation on that page is exactly the same for any client consuming Outlook v2.0 REST API, that included Outlook Add-ins, so basically you need to move to the Graph all such calls using Outlook REST APIs v2.0. Please check our documents and samples (i.e. script lab) on how to do this.

In addition to this, we also recommend you to use our SSO auth feature. in case you need to call APIs other than the Outlook scope.

Finally, this has no relationship whatsoever with our EWS Services, that is not affected by this issue.

@ElizabethSamuel-MSFT can you please close the issue?

Thank you very much @JuaneloJuanelo Thank you very much @ElizabethSamuel-MSFT and @AlexJerabek. Your answers have enlightened me and have significant impact to our future plans. Thank you again.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

smozgur picture smozgur  路  8Comments

bilalchraibi picture bilalchraibi  路  4Comments

PeterBrodersen picture PeterBrodersen  路  3Comments

redcirkle picture redcirkle  路  3Comments

thunter05 picture thunter05  路  6Comments