Create an Azure Bot

An Azure Bot is required to define a Microsoft Teams channel with a calling webhook URL, which serves as the endpoint where Microsoft sends call invitations. In addition, the bot must be associated with an Azure App Registration, which represents the deployment within Azure.

Task owner

• If your organization hosts the recorder server(s), your Azure administrator performs this procedure.

• If Verint hosts the recorder server(s), then Verint's Azure administrator performs it.

Before you begin 

Create a DNS entry

Procedure 

1. Open the Azure management portal at https://portal.azure.com.

2. Search for Azure Bot.

3. Under Marketplace, select Azure Bot.

4. On the Create an Azure Bot form, provide the following information:  

   1. In Bot handle, enter a unique name for this bot.

   2. Select the relevant subscription.

   3. In the Type of App, select Single Tenant.

   4. Select the resource group that contains the Verint Recorder VM.

5. In Creation type, select Create new Microsoft App ID.

   If you are using an existing Microsoft app registration instead, select Use existing app registration and provide App ID and App Tenant ID.

6. Select Review + Create.

7. Validate that the information is correct, then click Create.

   Within seconds, the Azure Bot is created and registered as an App with Azure Bot Services.

8. After Azure deploys the registration, go to the Bot Services and select the previously registered Bot Channel.

9. Select Channels.

10. In Add a featured channel section, select Teams.

11. Go to the Calling tab, select Enable calling.

12. Enter the Webhook URL that the Teams Bot will use to make calls, then click Save.

    The URL format is https://teamsbot.domainName:port/api/calling.

    domainName is the DNS CNAME entry

    port is the public signaling port #1.

    The /api/calling endpoint is a bot-specific HTTP endpoint that waits for an HTTP request from the Microsoft Teams platform.

    Example: https://teamsbot.verint.com:9440/api/calling

13. Get the Microsoft App ID:
    1. Select Settings and then select Configuration.

    2. Take note of the Microsoft App ID.

14. Create the client secret:

    1. Select Manage password next to Microsoft App ID.

    2. Go to Certificates & secrets page, and select the Client Secrets tab.

    3. Select New client secret.

    4. Add a description, and then set Expires to 24 months.

    5. Write down the new client secret.

    You must copy the client secret value immediately because it will not be displayed again.

15. Add the Redirect URI:

    1. In the navigation panel, under Manage, select Authentication (Preview).

    2. Select the Redirect URI configuration tab and click + Add Redirect URI.

    3. In the right panel, from Web applications, select Web.

    4. In Redirect URI, enter https://verint.com.

    5. Record the redirect URI for later configuration.

    6. Select Configure.

16. Configure Supported accounts:

    1. In the navigation panel, under Manage, select Authentication (Preview).

    2. Select the Supported accounts tab.

    3. In the Supported account types list, select Multiple Entra ID tenants.

    4. Select Allow all tenants or Allow only certain tenants (Preview).

17. Add permissions:

    1. Go to API permissions.

    2. Select Add a permission.

    3. Select Microsoft Graph.

    4. Select Application permissions.

    5. Add the following permissions:

       • Calls.AccessMedia.All

       • Calls.Initiate.All

       • Calls.InitiateGroupCall.All

       • Calls.JoinGroupCall.All

       • Calls.JoinGroupCallAsGuest.All

       • OnlineMeetings.Read.All

       • User.Read.All

For dual recording (N+N) deployments, follow the Recording Redundancy for Microsoft Teams Integrations section.

What to do next 

Grant admin consent for the permissions

Related information 

Use the Azure portal to Create an Azure Bot resource (Microsoft Docs)