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.
- If you are expecting more than 100 simultaneous recorded calls in your tenant(s), the bot has to be whitelisted by Microsoft to remove the throttling limits in the Graph API
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
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 Azure AD object ID of the users (not the User Principal Name or email address).
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.