Forum Discussion

Former Member's avatar
Former Member
2 months ago
Solved

Request for Guidance on Legacy Token Usage for GoTo Meeting Add-In

Hello,

We are currently conducting a review of all add-ins used within our organization in preparation for Microsoft's deprecation of legacy authentication tokens scheduled for February 2025. During this review, we discovered that the GoTo Meeting add-in is listed in our exported data from Microsoft as utilizing legacy tokens.

Given the upcoming changes, we would like to understand the following:
Does the GoTo Meeting add-in currently depend on legacy authentication tokens or callback tokens?
If so, are there plans to transition the add-in to use modern authentication protocols?
Do we, as administrators, need to take any specific steps to ensure the continued functionality of the add-in beyond February 2025?

For your reference, you can find more information about Microsoft’s deprecation of legacy authentication tokens and their impact on add-ins here: 

- https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens#can-i-turn-exchange-online-legacy-tokens-back-on

- https://github.com/OfficeDev/office-js/tree/release/add-in-ids

Thank you in advance for your assistance. 

Best regards,
Burak

  • Hi Former Member, the team has confirmed that our newer Outlook plugin is not affected by this change, so please switch to using that instead. It requires a Microsoft account to work, but not a subscription.

     

      

2 Replies

  • GlennD's avatar
    GlennD
    GoTo Manager
    2 months ago

    Hi Former Member, the team has confirmed that our newer Outlook plugin is not affected by this change, so please switch to using that instead. It requires a Microsoft account to work, but not a subscription.

     

      

  • GlennD's avatar
    GlennD
    GoTo Manager
    2 months ago

    Hi Former Member, welcome to the community.

     

    I have reached out to the team for a comment on this and will update you once I hear back.