Jira and Outlook: How to deal with nested app authentication and Outlook legacy tokens deprecation

[#1]

Microsoft announced that Exchange Online legacy tokens are deprecated in February 2025. This means that all add-ins relying on these tokens must switch to the new Entra ID authentication system to remain functional.

We have received a few support inquiries asking whether yasoon's Outlook add-in (Outlook Email for Jira or Microsoft 365 for Jira) is affected by these changes.

It is already fully compatible with the new tokens and it remains fully functional.

This post is intended to provide reassurance and help users understand the impact of Microsoft's authentication updates. To assist with the transition, Microsoft has introduced new testing tools and a report that helps administrators identify add-ins still relying on legacy tokens. If you encounter the following error, it indicates that your add-in is incompatible with the new authentication system:

• Message: "Error retrieving ID token"
• Code: FAILED_TO_GET_ID_TOKEN

In this case, you should contact the provider of the affected add-in for further support. For more details, refer to the official Microsoft resources:

• FAQ on nested app authentication and legacy token deprecation
• Microsoft Dev Blog on the topic