Registering the Microsoft Teams Bot in Azure

Creating a bot channel registration

Step 1 - Log in to the Azure portal.

Step 2 - Search for Bot Channels Registration in the search box on the top, then click on the link under the Marketplace section.

Step 3 - In the left panel, provide a unique name at the Bot handle, then select the Subscription, the Resource group, and the Location of the bot channel registration. The Location should be the same region where the Verba Bot virtual machine resides in Azure.

Step 4 - Click on the Create button. Creating the Bot Channel Registration may take some seconds.

Step 5 - Once the Bot Channels Registration is completed, search for Bot Services in the search box on the top, then click on the link under the Services section.

Step 6 - Select the previously created Bot service from the list.

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 - At the Webhook (for calling) setting, provide the following URL: https://verba_bot_vm.domain.com:9440/api/calling

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 - In the second left panel, under the Bot management section, click on the Settings menu.

Step 13 - Take a note of the Microsoft App ID. It will be needed later.

Configuring authentication for the bot

Step 14 - Click on the Manage link next to the Microsoft App ID.

Step 15 - Under the Client secrets section, click on the New Client Secret button.

Step 16 - Provide a Description, set when the secret Expires, then click on the Add button.

Step 17 - Take a note of the new Client secret. It will be needed later.

Step 18 - In the left panel, under the Manage section, click on the Authentication menu.

Step 19 - Under the Platform configuration sections, click on the Add a platform button.

Step 20 - In the right panel, select Web.

Step 21 - Provide a Redirect URI. It can be any website. Take a note of the URI provided, it will be needed later.

Step 22 - Click on the Configure button in the bottom.

Configuring permissions to the bot

Step 23 - In the left panel, under the Manage section, click on the API permissions menu.

Step 24 - Click on the Add a permission button.

Step 25 - Select Microsoft Graph, then select Application permissions.

Step 26 - Select the following permissions:

• • Calls.AccessMedia.All
  • Calls.Initiate.All
  • Calls.InitiateGroupCall.All
  • Calls.JoinGroupCall.All
  • Calls.JoinGroupCallAsGuest.All
  • OnlineMeetings.Read.All
  • User.Read.All

Step 27 - Click on the Add permissions button.

Granting admin consent to the permissions

Step 28 - Open the main Azure hamburger menu (in the upper left corner) and select the Azure Active Directory menu.

Step 29 - Take a note of the Tenant ID. It will be needed later.

Step 30 - Build the consent URL. The format is the following:

https://login.microsoftonline.com/{tenant_id}/adminconsent?client_id={microsoft_app_id}&state=12345&redirect_uri={redirect_uri}

Replace the {tenant_id} part with the ID from Step 29. Replace the {microsoft_app_id} part with the ID from Step 13, Replace {redirect_uri} part with the URI from Step 21.

Step 31 - 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.

2N Recording

In the case of 2N recording, all the steps above have to be done twice. Take a note of the second Microsoft App ID also at Step 13. It will be needed in the next part of the configuration guide.