NAA - "Something went wrong. [7q6cl]" (new Outlook on Windows)

[sznorbert07]

Provide required information needed to triage your issue

Recently I reported an issue to AzureAD/microsoft-authentication-library-for-js regarding using NAA in Outlook Add-in in new Outlook on Windows just did not work.
(AzureAD/microsoft-authentication-library-for-js#8345)

We made a fallback to this where we use custom implementation for OAuth process and are looking forward to rollback to NAA if possible.
I just noticed that I cannot reproduce the issue anymore and have not yet received an answer regarding this.
It's likely because I was supposed to report the issue here. Hoping to receive an answer here, I am asking you if you are aware of such an issue having occurred recently. Has the new Outlook version fixed this issue, or has something changed on this side in the last two weeks?

Best regards,
Norbert Székely

[github-actions]

Regression Analysis Needs Your Input

Our automated system analyzed this issue but couldn't determine with confidence if this is a regression bug.

A regression bug is when functionality that previously worked properly no longer works after a recent change.

If you believe this is a regression issue, please confirm below:

• Yes, confirm this is a regression issue

Note: Once confirmed, the issue will be labeled as regression.
After selecting the option, your choice will be automatically processed.

---

[github-actions]

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

• Outlook NAA issue: "Something went wrong. [7q6cl]" Error #4767
• NAA issues on Outlook for Windows (classic): "Something went wrong. [7q6cl]" #5406

---

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

Solution 1:

I learned recently that you need to preauthorize your client application to call itself. Can you try these steps and see if it fixes the issue?

1. In your app registration, go to Manage > Expose an API.
2. In the same Expose an API pane, select Add a client application.
3. Enter the client ID of your app registration (the same one you are in) which is found on the Overview page.
4. Select the access_as_user scope and then select Add application.

Reference:

• NAA issues on Outlook for Windows (classic): "Something went wrong. [7q6cl]" #5406 (comment)

Solution 2:

Adding permission to access_as_user did the trick. It is now working on New Outlook. We still can't get classic working though, but we fall back to getAccessToken in that case.

Reference:

• Outlook NAA issue: "Something went wrong. [7q6cl]" Error #4767 (comment)

Solution 3:

To fix it, I added an API permission for accessing my access_as_user scope, and granted admin consent. All works after this on all platforms.

Reference:

• Outlook NAA issue: "Something went wrong. [7q6cl]" Error #4767 (comment)

Powered by issue-sentinel

[sznorbert07]

Yes, confirm this is a regression issue

[ElizabethSamuel-MSFT]

@sznorbert07 Thanks for asking.

@davidchesnut Can you tell if this issue had been addressed and if so, provide build details where support is available?

Thanks.

[davidchesnut]

Hi @sznorbert07, unfortunately if the problem no longer repros it's really tough to figure out what happened. It looks like the log is indicating it was related to preauthorization. Did you add any static scopes in the app registration or preauthorize any apps in the registration (this would be required if you needed to call your own API service). Also can you provide the following details.

• Outlook client version.
• Outlook release channel audience (for client).
• Type of account being used.

Thanks!
David

[sznorbert07]

Hi @davidchesnut,
I have used the following Outlook (new) client:

Microsoft Outlook Version: 1.2026.225.400
Client Version: 20260227002.16
WebView2 Version: 146.0.3856.72 (Stable)
Session ID: 745d6a55-29eb-4e46-9ebe-073eda1ca9e8
Release Channel: Targeted Release
User has Microsoft 365 Business Standard license

I only configured the app to work with Graph API, no other app registration were added.

Best regards,
Norbert