Communication Recording Agent MS Teams Integration Guidelines
Version 1.6
This topic provides a technical overview of the Communication Recording Agent integration for Microsoft Teams and provides general install/configuration details.
Note
This topic is designed for use by Uniphore and partner installation and support engineers and is not intended for customer use – a cut-down Technical Guidelines topic is available for customer System Administrators, see MS Teams Technical Guidelines.
New in this Article
Version 1.1 of this Integration Guidelines topic contains the following general updates:
General architecture details have been updated.
MS Teams/Azure configuration guidelines have been updated to include PowerShell processes to help clarify the steps needed for this integration.
Compliance Bot upgrade and client secret update processes have been added.
An additional limitation was added regarding the Microsoft Prevent Toll Bypass calling policy.
MS Teams/Azure pre-reqs and the bot deployment guidelines have been updated. Note that this update is driven by the latest (Nov 2021) subscription options and bot deployment processes published by Microsoft – it does not relate to a specific Communication Recording Agent release.
For Communication Recording Agent upgrades (that have an existing MS Teams integration), no configuration changes are required for the integration, although you should upgrade the existing Compliance Bot to the latest version within Azure – see Upgrade the Azure Bot.
Version 1.2 of this Integration Guidelines topic contains the following general updates:
Tested Configuration section added.
A new Azure Bot version is available – 1.12.
Changes made to reflect updated VM options.
Set API Permissions section updated.
Configuration options for appsettings.remote.json have been updated.
Version 1.3 of this Integration Guidelines topic contains the following general updates:
Call Metadata topic updated to include additional metadata captured by the Azure bot (Version 1.12 and above)
Integration Dependent Features topic updated to reflect that max concurrent channels is Azure bot size specific, as well as specify that captured audio is stereo.
Configure the Integration Adapter topic updated to include the NATS JetStream settings introduced in U-Capture 2024.2.
U-Capture was previously called Conversa, in this topic all instances of the "Conversa" name have been updated to U-Capture, be aware that UI and API names may not have been updated in the actual product at the time of reading.
Version 1.4 of this Integration Guidelines topic contains the following general updates:
Minor adjustments have been made throughout the topic to better align with the next generation of U-Capture.
Resiliency and Known Limitation topics updated to address duplication limitation when using multiple Collectors for resiliency.
Channel Registration topic updated to reflect maximum recorded users per Compliance Bot / Collector pair.
Version 1.5 of this Integration Guidelines topic contains the following general updates:
The call metadata list has been updated to include a description for each metadata field.
Changes have been made throughout this topic to reflect that the Core Services are no-longer used to stream captured conversation data to the Audio Connector.
The Integration Adapter settings have been updated with new configuration fields.
Version 1.6 of this Integration Guidelines topic contains the following general updates:
U-Capture is now the Communication Recording Agent. This product name change has been made throughout the article, but may not be present in every aspect of the product at the time of reading.