Forum Discussion
Notification bot not detecting any installations
If you want to external users are interacting with your Azure, you need to use multi-tenant during app registration in the Azure portal.
Multi-tenant apps are available to users in both their home tenant and other tenants.
The multi-tenant organization is what enables the Azure Bot Service servers (in the botframework.com tenant) to authenticate requests coming from the bot (registered in the customer's tenant) through our servers. It's part of our service-to-service authentication protocol. it is not used for other purposes, and not to have any claims added to it for other access.
Reference Doc-
Best practices for multi-tenant apps
Thanks,
Sayali
----------------------------------------------------------------------------
If the response is helpful, please click "**Mark as Best Response**" and like it. You can share your feedback via Microsoft Teams Developer Feedback link.
Actually, when running in debug mode the bot the 3rd step ((3/5) Updating the bot messaging endpoint ...) fails: "MessageEndpointUpdatingError: Failed to update message endpoint with https://3384-46-193-104-169.ngrok.io/api/messages". Even though it created the tunnel with ngrok it doesn't work.
In the bot settings (accessed through https://dev.botframework.com/bots), I added the microsoft mail of the teamsappstudio in the owner section.
To clarify a few things, the tutorial you sent me works (https://learn.microsoft.com/en-us/microsoftteams/platform/sbs-gs-notificationbot?tabs=vscode). However, it does not work when I try to use my own bot instead of the one created by default. When I try to use my own bot, I get the error previously mentioned "MessageEndpointUpdatingError: Failed to update message endpoint with https://<ngrok_url>/api/messages".
Besides if I try to upload a custom manifest with my bot credentials to teams (upload custom app), run the bot with node locally and trigger the messages it does not work (the bot does not detect any installations). Probably I'm doing something wrong either in Azure, in the manifest or just the generic testing methodology.
Sayali-MSFTMicrosoft
BarneyGood- We will try it with our own bot and let you know the update.- I managed to use my own bot by running the node app locally and creating a tunnel with ngrok. The message endpoint on the bot framework was not the right one, but it works now !
I have one more question. Is it possible to use the bot in another teams organization ? The bot would be hosted on my company's Azure, but it would be used by external clients whom we would give the manifest so they can add the bot to their organization. But they would not have to interact with the bot framework or Azure in any way.BarneyGood how did you manage to do it? i also encounter similar issue. for some reason there is no installations or member
