@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.Graham Hunter commented
Yes, that's exactly it. Take a corporate directory bot for example (not our real product). If "Tasty Juice Company" signs up for our service they will want the bot to have their own identity for their end users, set up security accordingly, and not allow a different customer of ours, say "Yummy Smoothie, Inc." to have access to the TJC directory and will be on a separate channel.
This is accomplished in Azure Web Apps by setting up custom domains, and in the server code we can detect the hostname of the incoming request and segment the tenant accordingly.
The keys to this would be in setup (something we can automate for new customers), single codebase (everyone runs on the same code), and simplicity of deployment (we don't want 1000 bots for 1000 customers).
Does that make sense?
Work on this feature has started. Will update here when this becomes generally available.
Thank you for your suggestion and votes.
Apologies for the confusion on our part.
This is currently not on our roadmap. However, we will review this item in the future as we prioritize future releases.
Thanks for your suggestion.Graham Hunter commented
Perhaps this is a project we could start in a github repository and request oversight from the docdb team?