getUserIdentityTokenAsync method keeps returning obsolete identity token until 30 minutes when EdgeHtml used as browser in Outlook add-in

Question

We are using getUserIdentityTokenAsync method provided by Microsoft to fetch the identity token for our custom Outlook add-in.

Whenever we are updating the manifest file in Outlook to install the add-in, getUserIdentityTokenAsync keeps returning obsolete identity token with old aud value instead of updated one. getUserIdentityTokenAsync method returns the correct updated token only after 30 minutes of installing new manifest. This issue is only occurring where EdgeHTML is used as browser for add-in . For Outlook where Chromium is used as browser, it is working fine(https://learn.microsoft.com/en-us/office/dev/add-ins/concepts/browsers-used-by-office-web-add-ins). Can you please look into the issue & let us know if there is any recent change done by Microsoft in its behavior & what is the reason if done or is it an issue?

Answer 1

Hi @Srishti Chaurasia ,

The delay looks like an expected behavior according to this doc (among those comments): https://techcommunity.microsoft.com/t5/outlook-blog/centralized-deployment-for-outlook-add-ins-will-now-be-generally/ba-p/161164
Since Edge Chromium has no such delay, I suggest using Edge Chromium instead of EdgeHTML (the desktop app is out of support).

---

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

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Best Regards,
Shijie Li