Azure Resources Sign In not Working

[Madison-Pavelich-Evolve]

Issue:
After the Azure Resources extension updated to v0.12.0 (released 2/12/2026), signing in to Azure via the "Sign in to Azure..." button in the Resources section no longer works. The browser popup opens and authentication completes successfully, but VS Code does not recognize the sign-in. The "Sign in to Azure..." button remains as if no sign-in occurred. Clicking it again does nothing, since the browser session is already authenticated, but deployment of functions is unavailable.

Environment
OS: Windows 11
VS Code version: 1.109.4
Azure Resources extension version: 0.12.0

Attempted Fixes (Did Not Resolve):
Waiting for the session to expire (1 hour) and signing in again.
Restarting the computer.
Removing Azure-related credentials from Windows Credential Manager, then closing and reopening VS Code.

Resolution:
Rolling back to the previous version of the Azure Resources extension (pre-0.12.0) via Extensions → Gear icon → "Install Another Version..." immediately resolved the issue. Upon refreshing, the Azure sign-in was recognized and all resources were visible as expected. No other changes were made, confirming the issue was introduced in v0.12.0.

[alexweininger]

We will investigate and try to fix this as soon as we can. If you can provide logs from the Microsoft authentication extension, that will help me. Also if there are any relevant logs from the Azure Resource Groups output channel that will help too. Here's how to do that:

Set the log level with the "Developer: Set Log Level..." command.

Then view the logs using the "Developer: Show Logs..." command and selecting "Microsoft Authentication".

[Sherlocco]

I hope i'll help:

With both V0.12 and 0.12.1 i have this error, it happens for every tenant, also after loggin in into the "accounts &tenants" blade-
The V0.11.8 instead cleans the tokens in the right way.

Cleaning cache, removing MS auth pipeline... no chance.
Just downgrading

errorCode":"interaction_required","errorMessage":"InteractionRequired: V2Error: invalid_grant AADSTS50173: The provided grant has expired due to it being revoked, a fresh auth token is needed. The user might have changed or reset their password. The grant was issued on '2026-01-09T18:06:15.2101985Z' and the TokensValidFrom date (before which tokens are not valid) for this user is '2026-02-18T02:36:18.0000000Z'.

[Alphin1234]

I think this might help you. For me, it worked after I cleared the globalStorage and CachedData folders from my system. You can refer to Google for a detailed step-by-step guide. Before doing this, I closed Visual Studio Code from Task Manager and also restarted my system.

[SimonAfek]

I have the same issue, occurring with both 0.12.1 and 0.12.0. Like the OP describes, manually downgrading to 0.11.8 fixes it for me.

Seems to have something to do with expired tokens? After signing in (and then nothing happening), clicking the "Sign in to Azure..."-button again causes this output:

[info] [getAllSessionsForPca] [https://management.azure.com//.default] [xxx@xxx.onmicrosoft.com] failed to acquire token silently, skipping account {"errorCode":"interaction_required","errorMessage":"InteractionRequired: V2Error: invalid_grant AADSTS700082: The refresh token has expired due to inactivity. The token was issued on 2025-09-22T11:10:44.1505696Z and was inactive for 90.00:00:00. Trace ID: 3df2742b-2d66-4684-9166-050d33472900 Correlation ID: a78a731c-426e-4b00-8fb3-846d261c9431 Timestamp: 2026-02-19 11:54:05Z (Error Code: 3399614467, Tag: 7rhah)","subError":"","name":"InteractionRequiredAuthError","timestamp":"","traceId":"","correlationId":"","claims":"","platformBrokerError":{"errorCode":"InteractionRequired","errorMessage":"V2Error: invalid_grant AADSTS700082: The refresh token has expired due to inactivity. The token was issued on 2025-09-22T11:10:44.1505696Z and was inactive for 90.00:00:00. Trace ID: 3df2742b-2d66-4684-9166-050d33472900 Correlation ID: a78a731c-426e-4b00-8fb3-846d261c9431 Timestamp: 2026-02-19 11:54:05Z (Error Code: 3399614467, Tag: 7rhah)","subError":"","name":"PlatformBrokerError","statusCode":3399614467,"tag":"7rhah"}}

[Madison-Pavelich-Evolve]

We will investigate and try to fix this as soon as we can. If you can provide logs from the Microsoft authentication extension, that will help me. Also if there are any relevant logs from the Azure Resource Groups output channel that will help too. Here's how to do that:

Set the log level with the "Developer: Set Log Level..." command.

Then view the logs using the "Developer: Show Logs..." command and selecting "Microsoft Authentication".

I did as you requested and this is the error message I received after attempting signing in with version 0.12.1 of the Azure Resources extension:

{"errorCode":"interaction_required","errorMessage":"InteractionRequired: V2Error: invalid_grant AADSTS700082: The refresh token has expired due to inactivity. The token was issued on 2025-09-27T05:04:48.1755568Z and was inactive for 90.00:00:00. Trace ID: 26190e5a-9c6d-4e9f-8d49-bb564cf40700 Correlation ID: d0e688b5-b3dd-4bb5-a003-2c43af430d49 Timestamp: 2026-02-19 15:30:47Z (Error Code: 3399614467, Tag: 7rhah)","subError":"","name":"InteractionRequiredAuthError","timestamp":"","traceId":"","correlationId":"","claims":"","platformBrokerError":{"errorCode":"InteractionRequired","errorMessage":"V2Error: invalid_grant AADSTS700082: The refresh token has expired due to inactivity. The token was issued on 2025-09-27T05:04:48.1755568Z and was inactive for 90.00:00:00. Trace ID: 26190e5a-9c6d-4e9f-8d49-bb564cf40700 Correlation ID: d0e688b5-b3dd-4bb5-a003-2c43af430d49 Timestamp: 2026-02-19 15:30:47Z (Error Code: 3399614467, Tag: 7rhah)","subError":"","name":"PlatformBrokerError","statusCode":3399614467,"tag":"7rhah"}}

Reading over a couple of the other recent issue posts, I think both issue number #1370 and #1368 are describing the same problem.

[entish-tyler]

following advice in #1368, i reverted to version 0.11.8 which resolved the issue for me in US non-government.

[rmcmoorewsb]

I confirm, version 0.11.8 works while the newer versions do not. Even with 11.8 I have problems where after some amount of time, can be at little as an hour or two from sign-in, I have to re-sign-in, regardless of my amount of usage between those points in time. The account I'm using does have a CA policy with a 9 hour periodic reauthentication requirement.

[Madison-Pavelich-Evolve]

I confirm, version 0.11.8 works while the newer versions do not. Even with 11.8 I have problems where after some amount of time, can be at little as an hour or two from sign-in, I have to re-sign-in, regardless of my amount of usage between those points in time. The account I'm using does have a CA policy with a 9 hour periodic reauthentication requirement.

I'm not sure if the situation is the same for you, but I use my home computer to work sometimes and my Microsoft account with my home computer does not match up with my Azure account (from work). So I have to re-sign into my Azure account often. I believe it is a security feature that requires the generation of a new access token once an hour. Maybe that's what's happening to you.

When I work on my computer in the office where my Microsoft sign in is the same as my Azure account, I don't have to re-sign in because the Primary Refresh Token (PRT) is stored securely on the device.

[rmcmoorewsb]

I confirm, version 0.11.8 works while the newer versions do not. Even with 11.8 I have problems where after some amount of time, can be at little as an hour or two from sign-in, I have to re-sign-in, regardless of my amount of usage between those points in time. The account I'm using does have a CA policy with a 9 hour periodic reauthentication requirement.

I'm not sure if the situation is the same for you, but I use my home computer to work sometimes and my Microsoft account with my home computer does not match up with my Azure account (from work). So I have to re-sign into my Azure account often. I believe it is a security feature that requires the generation of a new access token once an hour. Maybe that's what's happening to you.

When I work on my computer in the office where my Microsoft sign in is the same as my Azure account, I don't have to re-sign in because the Primary Refresh Token (PRT) is stored securely on the device.

ok, that makes sense for the refresh. I do use a separate Azure admin account from my logged in user account on the computer. I do have the complete sign in failure though on the newer versions.

[bwateratmsft]

Folks here, can you try running one of these Azure CLI commands to see if that unblocks things? It will help inform what the fix on our end should be.

Bash:

az account get-access-token --scope https://management.azure.com/.default > /dev/null

CMD:

az account get-access-token --scope https://management.azure.com/.default > nul

PowerShell:

az account get-access-token --scope https://management.azure.com/.default > $null

This command is trying to get a token for the default management.azure.com scope, and then piping it to the void since we don't actually need it. I expect it may trigger an interactive sign in for some...if it doesn't, but errors, try az login first?

[entish-tyler]

another note - this issue is not present on macOS using extension v 0.12.1. the tested macOS is intune managed and joined with enterprise sso.

[rmcmoorewsb]

I think this might help you. For me, it worked after I cleared the globalStorage and CachedData folders from my system. You can refer to Google for a detailed step-by-step guide. Before doing this, I closed Visual Studio Code from Task Manager and also restarted my system.

Since I ran into another login issue, I got stuck connected with my normal account instead of my admin one.... I loaded the latest extension version, cleared these two folders, launched vs code and attempted login. The problem persisted with not actually logging in. reverting to the older version got me back to a working state.