Sign in to Azure does not work

[WietskeV]

Describe the bug
When I click 'Sign in to Azure', nothing happens.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Microsoft 365 Agents Toolkit' in VS Code, 'Accounts' section
2. Click on 'Sign in to Azure'
3. Nothing happens.

Expected behavior
Some prompt for credentials, just like for signing in to your M365 account.

Screenshots

VS Code Extension Information (please complete the following information):

• OS: Windows
• Version teamsdevapp.ms-teams-vscode-extension 6.4.1

[m365-agent-toolkit-assistant]

👋 Hi @WietskeV,

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 2 business days

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

This is a known issue with the Microsoft 365 Agents Toolkit extension for VS Code. Several users reported the "Sign in to Azure" button not working or not showing a login prompt (GitHub #12436, #3777).

Actionable Steps:

1. Restart VS Code—some users resolved it this way.
2. Try signing in via the VS Code "Accounts" sidebar (lower left corner), which may bypass extension UI issues.
3. Ensure the Azure Account extension is up-to-date.
4. If a device code prompt appears, use the "Copy & Open" button and complete sign-in via browser.
5. Check your default browser; some setups (see issue #5795) hide the login window.

If still blocked, this may be a bug. Watch linked GitHub issues for updates.

✨We'd love your feedback! Please take a moment to fill out our survey.

---

Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!

[WietskeV]

Update: I managed to fix it by signing out through the 'Accounts' section of VS Code itself (not inside the toolkit). Apparently I was still signed in there with another account, which was used but not displayed by the toolkit.

[HuihuiWu-Microsoft]

@WietskeV We'll fix this in the coming pre-release. Please try it out later