Outlook NAA issue : "Something went wrong. [9zj08]" Error

[akashsingheptura]

I have implemented NAA in my addin which work perfectly fine with OWA in Chrome, Edge, Safari and in Outlook App in MacOS but it doesn't work in Outlook Windows app. I have tried on both classic and new outlook app. All the MS office updates are installed in the system.

When I launch the addin in outlook app, the consent window does not load unless I use this combination of scope :

const tokenRequest = { scopes: ["User.Read", "api://" + {myADAppID} + "/access_as_user"] };

If I use anything other User.Read or access_as_user, then the app will stop opening the consent popup.

After using this scope, the consent popup opens but it does not return the token and keep giving this error.

Your Environment

• Platform [PC desktop, Mac, iOS, Office on the web]: PC Desktop
• Host [Excel, Word, PowerPoint, etc.]: Outlook
• Office version number: Microsoft® Outlook® for Microsoft 365 MSO (Version 2411 Build 16.0.18227.20082) 64-bit
• Operating System: Windows 11
• Browser (if using Office on the web): NA

Expected behavior

I should be able to acquire a token using MSAL and NAA approached defined in the example application in Windows Desktop Outlook client.

Current behavior

I receive the above error when attempting to obtain an access token.

It is occurring after calling the following line of code (popup opens with the error shown immediately). I have already allowed the permissions for my org when I tested in the browser the first time.:
const authResult = await this.pca.acquireTokenPopup(tokenRequest);

[github-actions]

Here are some similar issues that might help you. Please check if they can solve your problem.

• Outlook NAA: Something went wrong. [9zj08] ssoSilent fails when using shared mailbox scopes #4798

---

Possible solution (Extracted from existing issue, might be incorrect; please verify carefully)

Solution 1:

This error usually indicates that a token was requested for more than one resource. If you are including additional scopes that are not Graph, it could be the root cause. Also, the email scope could run into this issue. Could you provide the exact parameters you are passing?

const popupRequestParams: PopupRequest = {
  scopes: ["Mail.Read.Shared", "Mail.ReadBasic.Shared", "Mail.ReadWrite.Shared"],
};
const result = await msalInstance.acquireTokenPopup(popupRequestParams);

Reference:

• Outlook NAA: Something went wrong. [9zj08] ssoSilent fails when using shared mailbox scopes #4798 (comment)

Solution 2:

A few suggestions to diagnose further:

• The mailbox scopes require admin consent. Does your account have admin permissions?
• Is there any unique conditional access policy deployed in your tenant for this user?
• Have you tried a different user or dev tenant (created at https://developer.microsoft.com/en-us/microsoft-365/dev-program) to see if they can repro.
• Does your user have a valid Exchange license, and can use the shared mailbox feature.
• If you swap out createStandardPublicClientApplication for createNestablePublicClientApplication can you still repro? createStandardPublicClientApplication will not use the brk-multihub reply URI, and you will need a valid SPA endpoint registered to test.
• Have you tried https://mail.office365.com/ to see if it can repro the same issue for you?

Reference:

• Outlook NAA: Something went wrong. [9zj08] ssoSilent fails when using shared mailbox scopes #4798 (comment)