-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Teams Toolkit automatically logging into wring Azure account #13043
Comments
👋 Hi @wymersam, Thank you for reporting this issue! We want to let you know that: ⏱️ Our team will personally review your issue ✨ This is an AI-generated initial response Based on your description, it seems like you're experiencing an issue where the Teams Toolkit automatically logs into the wrong Azure account, and you are unable to log out and switch to the correct account. Here are some steps and suggestions to resolve this issue:
If you continue to face issues, you can refer to additional troubleshooting steps or report the issue on the Teams Toolkit GitHub issues page. By following these steps, you should be able to sign out of the incorrect Azure account and sign in with the correct one for your deployment. If the problem persists, consider providing more detailed feedback on the GitHub issues page to get further assistance.
|
Hi @wymersam , the Azure sign-out entry has moved to the 'Accounts' sidebar at the bottom left of VS Code. Please click 'Accounts' and choose your signed in Azure account to sign out. |
Describe the bug
When I install Teams Toolkit it is automatically logging into the wrong Azure account. There is no option for me to logout and when I click on the settings gear tool it just redirects me to Azure. I tried logging out here and it didn't fix the issue. In the past I was able to log in and out of my Azure accounts in Teams Toolkit but now I can't log in to the Azure account that I need for deployment.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No option to logout of currently logged in Azure account.
The text was updated successfully, but these errors were encountered: