Bot service is something that more than one of our customers has expressed interest in, but we don't want to have to deploy a new Bot instance for every one of them. Please add multi-tenant capabilities to ABS so we can detect the bot name that received the request and use the same back-end code across multiple endpoints.14 votes
@Graham, I would like to clarify the ask. Are you looking to create a single bot (with the same functionality) that can serve multiple ‘different’ (for lack of better term) companies/ groups? Can you clarify if all groups are on the same channel? Will each group use a different bot name as part of their intents? Please provide additional details for your scenario.
Message thrown by bot connector service in case of any exception scenario should be improved "Sorry, my bot code is having issue"
Message thrown by bot connector service in case of any exception scenario should be improved. The message now thrown is "Sorry, my bot code is having issue" , can be improved to much better matured message or code2 votes
Great feedback – thank you. Can you clarify which version of the SDK are you using?
I can create Brazilian Portuguese APPs with LUIS using the luis.ai portal, but I can't create an Azure Bot Service with an empty LUIS application in Brazilian Portuguese...2 votes
@Renan, are you looking to deploy an Azure Bot at the Brazil South (South Central US) region? If not please clarify your ask.
- Don't see your idea?