1- Make sure to be the Global admin in the Microsoft Azure portal. Other roles are not able to create a bot.
2- Before publishing Mindbehind bot, make sure to have a healthy bot in Microsoft Azure.
3- After having a healthy Teams bot on Azure, make sure to have MICROSOFT APP ID and MICROSOFT APP PASSWORD.
Make sure to follow all these steps:
https://kb.verba.com/display/docs/Registering+the+Microsoft+Teams+Bot+in+Azure
Step 1 - Log in to the Azure portal.
Step 2 - Search for Azure Bot in the search box on the top, then click on the link under the Marketplace section.
Step 4 - Click on the Review + Create button and if the configuration is correct, click on the Create button again. Creating the Azure Bot may take some seconds. Azure will actually create an App Registration and a Bot Service assigned to it.
Step 5 - Once the Bot Channels Registration is completed, search for Bot Services in the search box on the top, then click on the Bot Services link under the Services section.
(Alternatively, the Bot Services can be also found by opening the hamburger menu in the upper right corner, then selecting All services, then the AI + machine learning category.)
Step 6 - Select the Bot Service from the list that was created previously using the name provided at Step 3 (Bot handle).
Step 7 - In the second left panel, under the Bot management section, click on the Channels menu.
Step 8 - Under the Add featured channel section, select the Teams icon (Configure Microsoft Teams channel).
Step 9 - Select the Calling tab, then tick the Enable calling checkbox.
Step 10 - (IGNORE THIS STEP. WE DO NOT NEED TO ADD WEBHOOK CALL FOR OUR TEAMS CHANNEL).
Replace the verba_bot_vm part with the hostname of the Azure virtual machine which will host the Verba Bot service. At the domain part, use the domain of the Teams tenant (also specified in the SSL certificate).
Step 11 - Click on the Save button. Agree with the terms of service.
Step 12 - Search for App registrations in the search box on the top, then click on the App registrations link under the Services section.
(Alternatively, the App registrations can be also found by opening the hamburger menu in the upper right corner, then selecting the Azure Active Directory, then selecting App registrations in the left panel.)
Step 13 - Select the App Registration from the list that was created previously using the name provided at Step 3 (Bot handle).
Step 14 - Take a note of the Application (client) ID and the Directory (tenant) ID. They will be needed later.
Step 16 - Under the Client secrets section, click on the New Client Secret button.
Step 17 - Provide a Description, set when the secret Expires, then click on the Add button.
Step 18 - Take a note of the new Client secret. It will be needed later.
Step 19 - In the left panel, under the Manage section, click on the Authentication menu.
Step 20 - Under the Platform configuration sections, click on the Add a platform button.
Step 21 - In the right panel, select Web.
Step 22 - Provide a Redirect URI. It can be any website. Take a note of the URI provided, it will be needed later.
Step 23 - Click on the Configure button in the bottom.
Step 24 - In the left panel, under the Manage section, click on the API permissions menu.
Step 25 - Click on the Add a permission button.
Step 26 - Select Microsoft Graph, then select Application permissions.
Step 27 - Select the following permissions:
Using the same App Registration for Chat Recording also
The same App Registration can be used for the chat recording. In that case, add the following permissions also:
If the Chat recording will be used, the protected API access has to be requested. See Protected API Access for Chat Recording section at the bottom.
Step 28 - Click on the Add permissions button.
Separate Azure tenants for the recording provider (bot) and for the Teams environment to record
In the case when the recorded Teams environment and the recording bot are in separate Azure tenants, the following steps have to be done using the Tenant ID of the Azure tenant where the Teams environment to record resides, and also using a user that has the Teams Service Admin or Global Admin role in that tenant. In order to gather the Tenant ID for Step 29, you have to log in to the Azure portal of that tenant, then go to the Azure Active Directory.
If the same bot is being used in multiple tenants, then the following steps have to be done for each tenants using the guidelines above.
Step 29 - Build the consent URL. The format is the following:
Replace the {tenant_id} part with the Directory (tenant) ID and ****the {microsoft_app_id} part with the Application (client) ID from Step 14. Replace {redirect_uri} part with the URI from Step 22.
Step 30 - Copy the previously created consent URL into the browser, then hit enter. Log in with a Teams Service Admin or Global Admin user of the Azure tenant where the Teams environment to record resides. Click on the Accept button. The page will redirect to the webpage provided in the Redirect URI setting.
After successfully publishing bot,
Step 31 - Please visit Configuration page on left menu, add messaging endpoint such as: **https://app.mindbehind.com/external/v1/incoming/teams/{microsoftAppID}** Provide Microsoft App ID that you received on Step 14. You can also see your Microsoft App ID below.
As Mindbehind, we have an endpoint for you to receive your messages through the bot. We just need you to provide messaging endpoint with your app ID.
You can see your bot URL that you can send through teams from Channels tab. You will see your Microsoft Teams Healthy channel and Open in Teams button which redirect you to Teams App:
Congratulations! Your bot is running on your Teams bot as well.