Update legacy Exchange token documentation #12447
Conversation
|
Learn Build status updates of commit 2ec9e2c: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 611648e: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 2426bfa: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit bfa6f49: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit ce9c622: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit c85b2b5: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit d9a4f09: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
| @@ -81,10 +81,13 @@ The AllowLegacyExchangeTokens switch specifies whether legacy Exchange tokens ar | |||
|
|
|||
| Legacy Exchange tokens include Exchange user identity and callback tokens. | |||
|
|
|||
| This switch also specifies the most recent date and time that an add-in was allowed or blocked from acquiring a token. | |||
There was a problem hiding this comment.
most recent date and time
this is not exactly accurate and going to be confusing... the date updates once a week or so. In other words, it has a precision of about a week.
| **Important**: | ||
|
|
||
| - Currently, the AllowLegacyExchangeTokens switch only specifies whether legacy Exchange tokens are allowed in your organization. For now, disregard the empty Allowed and Blocked arrays returned by the switch. | ||
| - Legacy Exchange tokens will eventually be blocked by default in all cloud-based organizations. For more information, see [Nested app authentication and Outlook legacy tokens deprecation FAQ](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens#what-is-the-timeline-for-shutting-down-legacy-exchange-online-tokens). | ||
| - As of February 10, 2025, the AllowLegacyExchangeTokens switch specifies any add-in that requested an Exchange token. |
There was a problem hiding this comment.
any add-in
I wonder if we should clarify that we're talking about 3rd party add-ins... E.g. Viva may still get those tokens (and people may see that in fiddler) but it's not gonna be listed. That may cause them to think telemetry is inaccurate, but the fact is Viva is simply excluded from the whole thing for now as they work on migration. Please check with Paul on whether we want to say anything here about this or not.
|
Learn Build status updates of commit f20edd7: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 479baec: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 0d32ca1: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 1279fd8: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
samantharamon
changed the title
|
Learn Build status updates of commit 644e2a6: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Co-authored-by: David Chesnut <davech@microsoft.com>
|
Learn Build status updates of commit bf2b82a: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit ff7bf23: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit c2566b4: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit bb11ebd: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 82d866a: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
@chrisda This PR is ready to be merged whenever you get a chance. Thanks! |
|
Learn Build status updates of commit b90b3d1: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Uh oh!
There was an error while loading. Please reload this page.