
Windows Az Cli Logging Into Wrong Account Stack Overflow This command will clear the aad token cache, which will force the cli to prompt you to login again and select the correct account. another solution would be to check the environment variables on your machine to ensure that the correct tenant and subscription are being used. If i have previously logged in with one account (a), using connect azaccount for a different account (b) connects me to the first account (a). even after calling logout azaccount, this issue persists.

Windows Az Cli Logging Into Wrong Account Stack Overflow If you have multiple azure subscriptions, you might have experienced the frustration of logging into the wrong one with the az login command. this can cause errors and confusion when you try to run commands or access resources in the wrong subscription. I'm getting this error whenever i try to login to azure via the cli. here are the details: (now i get a popup browser window where both accounts have the same username email): 'local account id': 'ff37078a 25ee 4ca8 a555

Windows Az Cli Logging Into Wrong Account Stack Overflow Learn the different authentication types for your azure cli login — sign in with azure cli automatically, locally, or interactively using the az login command. I just downloaded and install the az cli. i ran the 'az login' command. it opened in chrome, my default browser. it shows my currently logged in (o365) account, and my test (microsoft) account. i want to log in with my test account. If you’ve encountered the error message "authentication failed against tenant" while using the azure cli, it can be frustrating. this issue often arises due to authentication mishaps, tenant misconfiguration, or account access issues. I have several connection issues since the last days when i try to connect to azure using either powershell azure cli. when i'm from home and i use az login or connect azaccount, i receive the following error. It seems like azure cli is picking up the account associated with the currently logged in pc user instead of the account selected during the login process. one workaround is to run the cmd.exe as a different user x@abc and then run az login from there, which seems to pick the right account. When your account is microsoft account (such as *@outlook , *@hotmail ), you will get the error log. the root reason is microsoft account does not support non interactive login.