Azure Resources Sign In Fails

[Sp3ctral]

Environment

• VS Code: 1.138.0 (Universal)
• Commit: 7debcd0e2acdea1c52de81bf9ee1620444407dda
• Electron: 42.10.0
• Node.js: 24.18.1
• OS: macOS Sonoma 14.6.1 (23G93), Darwin arm64 23.6.0
• Azure Resources Extension: 0.13.1

Issue

Interactive sign-in through the Azure Resources extension's GUI does not complete successfully.

Steps to Reproduce

1. Open the Azure Resources extension in VS Code.

2. Select the Sign In option in the extension's GUI.

3. VS Code displays the following prompt:

   The extension 'Azure Resources' wants to sign in using Microsoft.

4. Click Allow.

5. Complete the sign-in process successfully in the browser.

6. Return to VS Code.

Expected Behavior

After successfully signing in through the browser, the Azure Resources extension should recognize the authenticated session and update its GUI to reflect that the user is signed in.

Actual Behavior

After returning to VS Code, the Azure Resources extension returns to its default GUI state and continues to display the Sign In option, as though the sign-in process had never been initiated.

No authenticated session appears to be established within the extension.

The behavior is consistent across repeated attempts; every sign-in attempt results in the same state.

Troubleshooting Attempted

The following troubleshooting steps were performed but did not resolve the issue:

• Restarted the computer.
• Uninstalled and reinstalled the Azure Resources extension.
• Uninstalled and reinstalled Azure Core Tools using Homebrew.
• Uninstalled and reinstalled the Azure CLI using Homebrew.

Logs

Microsoft Authentication

[ID_REDACTED] : @azure/msal-node@5.4.0 : Info - Building oauth client configuration with the following authority: https://login.microsoftonline.com/organizations/oauth2/v2.0/token.
2026-09-22 00:38:00.237 [trace] [Tue, 22 Sep 2026 07:38:00 GMT] : [ID_REDACTED]  : @azure/msal-node@5.4.0 : Verbose - Silent flow client created
2026-09-22 00:38:00.237 [debug] [Tue, 22 Sep 2026 07:38:00 GMT] : [] : @azure/msal-node@5.4.0 : Info - Overwriting in-memory cache with persistent cache
2026-09-22 00:38:00.239 [debug] [Tue, 22 Sep 2026 07:38:00 GMT] : [ID_REDACTED] : @azure/msal-common@16.11.1 : Info - CacheManager:getAccessToken - Returning access token
2026-09-22 00:38:00.239 [debug] [Tue, 22 Sep 2026 07:38:00 GMT] : [ID_REDACTED] : @azure/msal-common@16.11.1 : Info - Token refresh is required due to cache outcome: '3'
2026-09-22 00:38:00.239 [debug] [Tue, 22 Sep 2026 07:38:00 GMT] : [ID_REDACTED] : @azure/msal-common@16.11.1 : Info - CacheManager:getRefreshToken - returning refresh token
2026-09-22 00:38:00.439 [trace] [Tue, 22 Sep 2026 07:38:00 GMT] : [ID_REDACTED] : @azure/msal-common@16.11.1 : Verbose - acquireTokenWithRefreshToken: bad refresh token, removing from cache
2026-09-22 00:38:00.439 [info] [getAllSessionsForPca] [https://management.core.windows.net/.default] [EMAIL_REDACTED] failed to acquire token silently, skipping account {"errorCode":"invalid_grant","errorMessage":"AADSTS700082: The refresh token has expired due to inactivity. The token was issued on 2025-09-19T09:08:08.3597509Z and was inactive for 90.00:00:00. Trace ID: ID_REDACTED Correlation ID: ID_REDACTED Timestamp: 2026-09-22 07:38:00Z","subError":"bad_token","correlationId":"ID_REDACTED","name":"InteractionRequiredAuthError","timestamp":"2026-09-22 07:38:00Z","traceId":"ID_REDACTED","claims":"","errorNo":700082}
2026-09-22 00:38:00.440 [info] [getSessions] [https://management.core.windows.net/.default] returned 0 session(s)

Similar issues discovered:
#1671
#1370
#1368