There's a rare auth issue affecting small number of users where various azd commands result in an AADSTS700082 error:

Running azd auth login to re-authenticate does not resolve the error, even if the exact --tenant-id was passed. Subsequent azd commands (e.g. azd deploy, azd init) continue to fail with the same stale token error, even though the user just logged in successfully.
There's a rare auth issue affecting small number of users where various azd commands result in an AADSTS700082 error:

Running
azd auth loginto re-authenticate does not resolve the error, even if the exact--tenant-idwas passed. Subsequent azd commands (e.g. azd deploy, azd init) continue to fail with the same stale token error, even though the user just logged in successfully.For anyone internal who's running into this issue, we added additional debug capabilities in v1.23.15 (to be released by EOD today) to help the team investigate the issue further. Please follow the instructions below and share the logs with us internally.
Instructions
Important
Do not run
azd auth logoutor delete~/.azdfirst. We want to preserve the existing cached auth state.Install the latest version of azd (at least v1.23.15).
Reproduce login with MSAL cache tracing enabled:
Immediately run the command that fails for you:
Also collect these follow-u…