Configuring Microsoft Teams Recording

For the general overview of the Microsoft Teams recording refer to the Microsoft Teams article.


Before starting the deployment of the Verba system for Microsoft Teams, the following prerequisites has to be met:

  • Virtual machines have to be created in Azure with Recording Server roles which will host the Verba Microsoft Teams Bot service and the Unified Call Recorder service. It is recommended to have the servers in the same region as the Teams tenant. The servers need to have a public IP address.
  • For resilient and/or high volume configurations, multiple virtual machines (running the Recording Server role) has to be deployed. In order to distribute the load across multiple Verba Microsoft Teams Bot services, an Azure Application Gateway has to be deployed in front of the VMs.
  • A new CNAME entry has to be created in a public domain, pointing to the Verba virtual machines in Azure.
  • A publicly signed certificate is required for the virtual machines. Only CSP certificates are supported (CNG/KSP certificates are not supported). The SAN configuration of the certificate must include the virtual machines (with the public domain). Using asterisk in the SAN is accepted. The private key of the certificate has to be exportable.
  • Configure the firewall rules both on the operating system and the Azure virtual machine level.
  • The Microsoft Graph Communications Calling SDK does not support FIPS 140-2 validation. Make sure the validation is disabled on the server. Please refer to this documentation on how to disable FIPS 140-2 Validation

The following permissions and roles required to configure the system:

  • Azure: Application Administrator or Global administrator
  • Office 365 / Teams: Global Administrator
  • Windows: Local Administrator
  • Verba: System Administrator

Creating the Microsoft Teams Recording Bot

Step 1 - Registering the Bot

Step 2 - Whitelisting the App

Step 3 - Creating a Compliance Policy

Configuring Verba for Microsoft Teams recording

Step 4 - Configuring the Verba Microsoft Teams Bot and Unified Call Recorder Services

Adding Users for Recording

In order to enable recording for the users, first, the previously created compliance policy has to be assigned to the user. For the configuration steps, see Administering Compliance Policy for Microsoft Teams Users.

Once the compliance policy is set, create the users and the extensions on the Verba side. This can also be done via Active Directory Synchronization. The extensions have to match the Microsoft Entra (formerly Azure AD) object ID of the users (not the User Principal Name or email address).

Selective recording rules can only also be applied to record calls/meetings where there is an external participant or the meeting was scheduled, etc. For more information see Microsoft Teams selective recording settings.

Controlling recording using the Teams Application

The Verint Capture for Microsoft Teams - Recording Controls Application, is a native Microsoft Teams Application that allows privileged Microsoft Teams users to control compliance recording, by starting and or stopping the VFC Compliance Recorder. For more information, see Microsoft Teams Application.

Adding a Verba Tab to Microsoft Teams

For adding a Verba tab to the Microsoft Teams client, see Adding Verba Tab to a Microsoft Teams Channel.

If SSO is being used, then it is required to modify the settings of the web application to make it working in the Microsoft Teams client. This will lower the security of the web application. For the configuration steps, see Enabling the Verba Web Application in 3rd Party Frame.

Recording Meeting Subjects as Metadata

The Verba Microsoft Teams Bot service checks several Graph API calls in order to gather the meeting subjects. In order to make sure that the Bot has the ability to gather this information, besides the Calendars.Read permission, additional policy settings may be required.

For the configuration steps, see: Configuring Access Policy for Meeting Metadata