This integration is in limited availability. Contact your CSM to connect.
Connect Gong with Microsoft Teams phone so your calls are available in Gong.
We have created a technical partnership with Numonix LLC, a policy-based recording solution certified for Microsoft Teams to offer a seamless integration that allows your company’s phone call recordings made through Microsoft Teams dialer to be available in your Gong instance. This guide explains how to set up the end-to-end integration between your Microsoft Teams dialer and your Gong instance.
When a Microsoft Teams phone call takes place, Numonix's Compliance Bot, integrated with Microsoft Teams, records these calls on behalf of the end-customer, and is stored within Numonix's Azure servers.
From the Numonix Azure servers, the recorded calls are seamlessly ingested by Gong, ensuring that they are readily accessible for Gong users across the platform.
Note
For troubleshooting purposes, recorded calls remain in Numonix’s Azure servers for 7 days, and then are automatically deleted thereafter.
Gong covers the additional costs of this integration, its end-to-end maintenance and support.
Contact Gong support for any technical and troubleshooting help.
By setting up this integration, you will be subject to the Terms and Conditions of Numonix LLC (a third-party service provider), which govern the recording and management of your calls when being processed by Numonix. You agree that any matters relating to your data when processed or stored by Numomix are between your organization and Numonix.
Setting up the Gong integration with Microsoft Teams phone involves creating an application instance, and a compliance recording policy. The compliance recording policy is then associated with users or groups in your Active Directory.
The integration is by default configured in strict mode. This means that users who are associated with the Gong compliance policy can only make calls that are recorded. You must disable strict mode in order to allow your users to make all types of calls.
Configure the MS Teams phone integration with Gong:
-
Contact Dev/Product team to enable the MS Teams phone feature flag in your customer’s instance.
-
In Gong, hover over your user name and select Settings > Telephony systems. Click Add Telephony System.
-
Select Microsoft Teams to open the Microsoft Teams phone integration page.
-
Give a name to the connection and click CONNECT IN MICROSOFT TEAMS.
-
The Microsoft permissions page is displayed. Click Accept to give permissions for your Gong user to access your MSFT tenant (see the appendix for more details). Once you have granted permissions, you will be redirected back to the Gong settings page.
Contact Gong support if you want to set up the Microsoft Teams integration for multiple Microsoft tenants.
Once you have set up the integration in Gong, your Microsoft Azure admin must set up Teams phone to enable compliance recording of calls.
You must install PowerShell and Microsoft Teams phone to set up this integration
-
In Microsoft Teams PowerShell module, install MicrosoftTeams.
Install-Module -Name MicrosoftTeams
-
Verify the MicrosoftTeams module is installed.
GET-InstalledModule -Name MicrosoftTeams
Create a compliance recording policy and associate it with your users or groups:
-
Get your TenantID. In PowerShell, connect to your Teams Tenant:
Connect-MicrosoftTeams
-
Create an application instance using the Gong Compliance Bot application ID. This script creates an application instance together with a user in Azure’s Active Directory. This user is the user that used to record calls. Define the following parameters for the script:
-
appID: the appId you got after connecting to Microsoft Teams phone to Gong.
-
UserPrincipalName: an email to be associated with the Gong Compliance bot. This email address will be added to Active Directory after running the script.
-
DisplayName: the display name for the user created in Active Directory. This name is displayed if the user is added to a call. Use a descriptive name such as 'Recording Assistant'.
New-CsOnlineApplicationInstance -UserPrincipalName <teamsrecorder@acme.com> -DisplayName <displayName> ` -ApplicationID <appId>
-
-
The script returns the application ID, display name, and the object ID for the Gong Compliance bot generated. Keep a copy of the object id.
Tip
Add the resource account (UserPrincipalName) to a whitelist in your security scanning or risk mitigation software. Do not disable or mark the resource account (UserPrincipalName) as inactive in your Active Directory; this will affect and/or disable your service.
-
Create a Compliance Recording Policy with the following parameter:
-
policyIdentity: the policy identifier which is then associated with users you want to record.
New-CsTeamsComplianceRecordingPolicy -Identity <policyidentity> -Enabled $true ` -Description "Teams Compliance Recording" -DisableComplianceRecordingAudioNotificationForCalls $true
-
-
Associate the compliance recording policy with the Gong Compliance Bot application with the following parameters:
-
policyIdentity: the policy identifier which is then associated with the users you want to record
-
objectId: the ID of the object generated when creating the application instance
Set-CsTeamsComplianceRecordingPolicy -Identity <policyidentity> -ComplianceRecordingApplications ` @(New-CsTeamsComplianceRecordingApplication -Id <objectId> -Parent <policyidentity> )
-
When strict mode is enabled, users associated with the Gong Compliance policy can only make calls that are recorded. Gong’s Compliance Bot records PTSN calls.
To enable your users to make other types of calls, disable strict mode in the Teams compliance recording profile.
-
Connect to MSTeams using Powershell.
-
Identify the application that needs to be changed:
Get-CsTeamsComplianceRecordingApplication
The script returns the following:
Identity:
Tag: <application identifier>
Priority:
0
ComplianceRecordingPairedApplications:
{}
Id:
<appID instance>
RequiredBeforeMeetingJoin
True
RequiredBeforeCallEstablishment
True
RequiredDuringMeeting
True
RequiredDuringCall:
True
ConcurrentInvitationCount:
1
-
Set the parameters in bold to False:
Set-CsTeamsComplianceRecordingApplication –Identity Tag:<application identifier> -RequiredBeforeMeetingJoin ` $false -RequiredDuringMeeting $false -RequiredBeforeCallEstablishment $false -RequiredDuringCall $false
-
Confirm the settings were updated:
get-CsTeamsComplianceRecordingApplication
The script returns the following:
Identity:
Tag: <policy identifier>
Priority:
0
ComplianceRecordingPairedApplications:
{}
Id:
<appID instance>
RequiredBeforeMeetingJoin
False
RequiredBeforeCallEstablishment
False
RequiredDuringMeeting
False
RequiredDuringCall:
False
ConcurrentInvitationCount:
1
-
In Gong: Make sure to enable importing telephony system calls for users whose calls you want to record. Check that the list of users in Microsoft Teams and the list of users in Gong are aligned.
-
Assign the compliance recording policy to a user or group:
-
Assign to User:
Grant-CsTeamsComplianceRecordingPolicy -Identity <recordeduser@acme.com> -PolicyName <policyidentity>
-
To remove a policy from a user:
Grant-CsTeamsComplianceRecordingPolicy -Identity recordeduser@acme.com -PolicyName $null
-
Assign to group:
New-CsGroupPolicyAssignment -GroupId <objectid of security group> -PolicyType TeamsComplianceRecordingPolicy ` -PolicyName <policyidentity> -Rank 1
-
Remove a policy from a group:
Remove-CsGroupPolicyAssignment -GroupId <objectid of security group> -PolicyType TeamsComplianceRecordingPolicy
-
-
Verify the policy was applied to a user or to the Azure Active Directory Security Group:
-
Verify user:
Get-CsOnlineUser -Identity '<User’s UPN that was associated with compliance policy>' | Select-Object ` -ExpandProperty 'TeamsComplianceRecordingPolicy'
-
Verify group:
Get-CsGroupPolicyAssignment -PolicyType TeamsComplianceRecordingPolicy
-
Scope |
Microsoft description |
Gong explanation |
---|---|---|
Read all users' basic profiles |
Allows the app to read a basic set of profile properties of other users in your organization on behalf of the signed-in user. This includes display name, first and last name, email address and photo. |
Required by Gong to retrieve relevant call metadata for the recorded user. |
Sign in and read user profile |
Allows users to sign-in to the app, and allows the app to read the profile of signed-in users. It also allows the app to read basic company information of signed-in users. This is a permission requested to access your data in the account. |
Required by Gong to retrieve the relevant user email for a recorded user, to match the Microsoft user to the Gong user. |
Access media streams in a call as an app |
Allows the app to get direct access to media streams in a call, without a signed-in user.This is a permission requested to access your data in the account. |
In order to record calls, Numonix needs access to the call’s audio stream. This is part of Microsoft’s minimum requirements to enable the compliance recording feature. |
Join group calls and meetings as an app |
Allows the app to join group calls and scheduled meetings in your organization, without a signed-in user. The app will be joined with the privileges of a directory user to meetings in your organization. This is a permission requested to access your data in the account. |
In order to record, the Numonix Bot will silently join calls in order to access the audio stream. The bot user will not be visible to users. This is part of Microsoft’s minimum requirements to enable the compliance recording feature. |
Join group calls and meetings as a guest |
Allows the app to anonymously join group calls and scheduled meetings in your organization, without a signed-in user. The app will be joined as a guest to meetings in your organization. This is a permission requested to access your data in the account. |
In order to record, the Numonix Bot will silently join calls in order to access the audio stream. The bot user will not be visible to users.Join group meetings as a guest is for covering the scenario when the recorded user joins a meeting hosted by another Teams org. The bot needs to be able to join said meeting even though they don’t have admin consent into the Organizers tenant. This is part of Microsoft’s minimum requirements to enable the compliance recording feature. |
Comments
0 comments
Article is closed for comments.