Visual Code Teams Toolkit Bot notification provision error:[Login.UnknownSubscription]: Unable to apply this subscription. Select a subscription you've access to or try again later.

Question

Hi

I am trying to provision a BOT in Visual Studio Code using Teams Toolkit. I can run it locally but when I try to provision it I get the following error:

[Login.UnknownSubscription]: Unable to apply this subscription. Select a subscription you've access to or try again later.

Teams toolkit version: 5.12.1

node.js version: v22.14.0

Steps taken to get this far.

Install Teams toolkit

Install node.js latest version

In Visual Code Studio, click on Teams Toolkit - create a new app

• bot
• chat notification message
• HTTP Trigger (Express server)
• Javascript
• default folder
• [app name]
• wait for install
• local debug in teams (edge) (opens teams in the browser)
• run Invoke-Webrequest -Method POST -URI http://localhost:3978/api/notification in PowerShell.
• This returns card in teams window
• Provision
  • error message during the provision

[Login.UnknownSubscription]: Unable to apply this subscription. Select a subscription you've access to or try again later.

I am logged into a 365 account* and Azure account* in teams toolkit

I can see the subscription in azure

My role: Specified Access

Status: Active

*note this is a separate tenant to our business tenant. it is essentially a totally separate tenant for sandbox.

I have added a resource group to Azure and a azure bot. then added these details into the .env.dev file but still the same.

Logged out and back into the 365 and azure connectors - still the same.

Could it be an issue with Azure I am using? as it is active.

Thanks

Iain

Answer 1

I have managed to get passed this now by installing Azure Resources in Visual Studio Code.

I also needed to tick the account - this is the part I needed to do.

In Visual Studio code, install Azure Resources extension

• Add Azure login
• In the ACCOUNTS & TENANTS section (under RESOUCES & WORKSPACE)
• Select the account (you may need to log in again)

This enabled me to provision the BOT