Need assistance with moving Outlook add-ins that use legacy Exchange tokens to nested app authentication

Question

Hello,

Please i need your help on this issue.

I will need assistance with moving Outlook add-ins that use legacy Exchange tokens to nested app authentication.

I need assistance with implementing required changes as per this article: https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/faq-nested

 Salesforce/Outlook add-in related article: https://help.salesforce.com/s/articleView?id=002723592&type=1&utm_source=techcomms&utm_medium=email&utm_campaign=FY25

Specifically what I need help with is implementing the changes recommended by Salesforce (see below) in order to allow the Salesforce/Outlook plug-in to continue to work after Microsoft turns off Exchange Online tokens for all tenants as part of the nested app authentication and Outlook legacy tokens deprecation.

Answer 1

Hi, @IniobongNkanga-8038

Can you describe your specific issue in detail so that I can more accurately provide support?

As stated in the documentation you provided, prior to turning off Exchange Online tokens in a tenant, verify that M365 does not have policies configured that would prevent the Outlook integration from working properly after turning off Exchange Online tokens in a tenant.

The current method of handling this transition is to migrate to the Graph API. Old Exchange tokens will be deprecated, which means that the recommended path for the future is to migrate add-ons to use the Microsoft Graph API, which provides better security and greater application architecture flexibility.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".