Microsoft Graph
A Microsoft programmability model that exposes REST APIs and client libraries to access data on Microsoft 365 services.
10,512 questions
Questions about deprecation of Outlook Rest APIs
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 87%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEY%3C/text%3E%3C/svg%3E)
Eugene Yon
6
Reputation points
Hello Microsoft Graph Support,
We are trying to spin up investigation work specifically around the deprecation of Outlook Rest APIs.
My understanding is that this is the correct forum to ask our questions to move our investigation forward, and ultimately implement changes in the near future. Below is some context, and specific questions we have for you. Thank you very much in advance!
We have a question regarding the Outlook Rest API deprecation: Outlook REST API v2.0 production and beta endpoint deprecation
We have an OAuth application that utilizes the following OAuth scopes:
1 "openid",
2 "profile",
3 "offline_access",
4 "https://outlook.office.com/SMTP.Send",
5 "https://outlook.office.com/mail.send",
6 "https://outlook.office.com/IMAP.AccessAsUser.All"
Per the guidance, the recommendation is to move the Microsoft Graph API. However, they do not appear to support SMTP.Send and IMAP.AccessAsUser.All. We tested this by modifying our application to utilize the https://graph.microsoft.com/SMTP.Send and the application failed with an authentication error.
Our questions are:
Does Microsoft Graph OAuth tokens, support SMTP and IMAP?
Will the https://outlook.office.com/SMTP.Send and https://outlook.office.com/IMAP.AccessAsUser.All be deprecated with the Outlook Rest API deprecation?