Microsoft delays Outlook REST API deprecation until 2023

We’re sure that some of you remember that, back in November 2020, Microsoft announced that it is deprecating the Outlook REST API beta and Outlook REST API v2.0 endpoints.

As the company mentioned, this would be a two-year process as a part of Microsoft’s regular service deprecation policy.

Here we are, at the end of this two-year period, and Microsoft has now announced that it is delaying this deprecation indefinitely.

Outlook REST API deprecation will happen in 2023

Since we are talking about Outlook, just know that if the app won’t open, we have some solutions that will help you fix the situation.

You will also find the assistance you need if your Outlook is running slow, so you don’t need to look any further for answers.

Circling back to the matter at hand, the tech giant actually cited customer and partner feedback as the reasons behind its decision.

From what we can see, users of the API are not ready to let go of it completely and switch to Microsoft Graph, an action that would require somewhat major changes to current applications and use cases.

Note that Microsoft has cautioned customers to not get too comfortable with this delay or think that it’s a long-term option.

Even though the deprecation has been delayed indefinitely, Microsoft has emphasized that it will still happen in 2023 and that users will be given a six-month notice ahead of the deadline.

If you weren’t already aware, the Outlook REST API is being used by developers in applications that manage mailbox data, Calendars, Contacts, push notifications, and more.

The Redmond-based tech company has considered it a legacy surface since 2020 and has been encouraging customers to migrate to Microsoft Graph.

As you might have expected, once the Outlook REST API is inevitably deprecated, developers will no longer have access to the endpoint and the creation of new applications based on the API will be disabled.

Since nobody knows, it remains to be seen what the deprecation date ends up being next year and the kind of impact it would have on current use cases and scenarios.

What is your take on this entire situation? Share your thoughts and opinions with us in the comments section below.