MicrosoftMicrosoftI am surprised that there is not more chatter from admins on Exchange Online Token Deprecation as June 2025 approaches. Any organization using common add-ins such as Salesforce, Condeco and other CRM related integrations risk them breaking come June 2025.
How many people have actually performed a scream test by turning Exchange Online tokens off in their tenant? It is easier for smaller tenants compared to large tenants.
I have seen the wording of the FAQ https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens change in recent months.
Onhttps://web.archive.org/web/20250324201045/https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens this FAQ stated the following in a note:
"Note
We've been working to provide a command update to Exchange Online PowerShell that reports any add-ins using legacy Exchange Online tokens. Unfortunately, we've had difficulties rolling out this update due to the complexities of capturing specific token usage in the Microsoft 365 ecosystem. We continue to work on this update and will provide new information in this FAQ when it is available."
This note has disappeared in current versions of the FAQ. I take this to mean even Microsoft was having trouble providing its customers specific details on what was using Exchange Online tokens in an M365 tenant. There is a note in the document showing how to turn on/off Exchange Online tokens stating if you run Get-AuthenticationPolicy -AllowLegacyExchangeTokens, the data returned is "old data" and not applicable. Not all vendors of add-ins\integrated apps have put a banner on their tools that alert end users of an upcoming possible interruption. This means some are flying blind.
The end result, or the result currently, is if admins of a tenant are unsure they can perform a scream test which is a decision that would impact any and all add-ins using Exchange Online tokens by taking them offline.
1. To turn off Exchange Online tokens it can take 24 hours for it to apply.
"The update is rolled out per user. This means that one or more users may have an add-in affected when Exchange tokens are off, but other users would still have a working add-in. "
2. Time for users to report an outage to some tools they rely on.
3. To turn on Exchange Online tokens it can take 24 hours for it to apply.
For an add-in\integrated app that is deployed to thousands of people (my organization has multiple) this would be very intrusive if they were impacted by turning Exchange Online tokens off.
IMHO, there should be a method to selectively disable Exchange Online Tokens per add-in\integrated app. Not for discovery but for testing and confirmation that the add-in starts using the new method for authorization\tokens. At the moment, an admin would think they are ready for when MS turns of Exchange Online tokens but it cannot be proven unless one wishes to impact the entire tenant, all the add-ins at once.
Also IMHO, the commands mentioned in the note I mentioned above should really have been a requirement to help admins, not an attempt to provide them. If by that note it meant to "look at your code for the following", a typical Exchange admin that isn't the right audience for that.
Finally, I do not think Microsoft is providing robust enough tools for admins to confirm they will not have an impact when Exchange Online tokens are turned off. If you search forums for comments on this, I have found admins mentioning this on reddit where you can clearly see they are Exchange Admins only, with limited understandings of the Enterprise Application area of Entra ID, likely having Enterprise Apps not correctly locked down especially if permission type is of Application instead of Delegation.
Not providing as many robust tools to Admins as a priority risks kicking the can further down road.
