-
Notifications
You must be signed in to change notification settings - Fork 403
Troubleshooting
Adrian Solis edited this page Aug 16, 2019
·
14 revisions
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: MsaAppId is already in use.
- 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.
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