[All hosts] (NAA) Latest NAA updates #4856
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Learn Build status updates of commit 8dfeee9: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit c1cae49: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
AlexJerabek
approved these changes
Oct 15, 2024
| @@ -61,7 +61,7 @@ The following steps show how to enable NAA in the `taskpane.js` or `taskpane.ts` | |||
|
|
|||
| ```json | |||
| "dependencies": { | |||
| "@azure/msal-browser": "^3.15.0", | |||
| "@azure/msal-browser": "^3.24.0", | |||
| ... | |||
There was a problem hiding this comment.
Any idea why this is showing up weird in GitHub?
| | _setActiveAccount_ | NO | | ||
| | _setLogger_ | YES | | ||
| | _ssoSilent_ | YES | | ||
| | *acquireTokenByCode* | NO (throws exception) | |
There was a problem hiding this comment.
Instead of italic, should these method names be in code ticks?
| | _setActiveAccount_ | NO | | ||
| | _setLogger_ | YES | | ||
| | _ssoSilent_ | YES | | ||
| | *acquireTokenByCode* | NO (throws exception) | |
There was a problem hiding this comment.
Can we change the "YES" and "NO" to "Yes" and "No"?
| @@ -59,7 +62,7 @@ To find out whether your add-in uses legacy Exchange user identity tokens and ca | |||
|
|
|||
| If your add-in calls any of these APIs, you should adopt NAA and migrate to using Entra ID tokens to access Microsoft Graph instead. | |||
|
|
|||
| We'll provide tooling via PowerShell for Microsoft 365 administrators in October 2024 to turn legacy Exchange tokens on or off in your tenant. This will allow you to test if any add-ins are using Exchange tokens. We'll provide more information when the tooling is ready in this FAQ. | |||
| We'll provide tooling via PowerShell for Microsoft 365 administrators in October 2024 to report the app ID of any add-in that used legacy Exchange online tokens in the last 28 days. The tooling will also allow you to turn legacy Exchange online tokens on or off for the entire tenant. We'll provide more information when the tooling is ready in this FAQ. | |||
There was a problem hiding this comment.
Since it's October, do we know when this tooling is coming?
|
Learn Build status updates of commit 0078882: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Learn Build status updates of commit 25a1cb2: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This updates the walkthrough and FAQ with latest updates around NAA preview and GA.