-
Notifications
You must be signed in to change notification settings - Fork 40
Troubleshooting
Adrian Solis edited this page Oct 7, 2019
·
1 revision
There are certain issues that can arise that are common to many of the app templates. Please check here for reference to these.
Bot is not valid. Errors: The Microsoft App ID is already registered to another bot application.. See https://aka.ms/bot-requirements for detailed requirements.
- Creating the resource of type Microsoft.BotService/botServices failed with status "BadRequest"
This happens when the Microsoft Azure application ID entered during the setup of the deployment has already been used and registered for a bot, for instance, if a previous deployment step failed after the bot was created.
Either register a new Microsoft Azure AD application or delete the bot registration that is currently using the attempted Microsoft Azure application ID.
Please report the issue here