For Microsoft Entra administrators, Microsoft Teams administrators, and MCO eComms administrators.
Before you begin
Confirm you have access to Microsoft Entra ID with the required administrator role.
Confirm you can run PowerShell as an administrator.
Confirm the PowerShell execution policy is set to at least
RemoteSigned.Confirm the Microsoft Teams PowerShell module is installed.
Confirm the covered users or groups that should be recorded.
Confirm Microsoft Teams Voice and Meetings capture is enabled in your MCO eComms account.
Confirm the users who need Teams V&M source mappings in MCO eComms.
For more information about Microsoft Teams recording, see Introduction to Teams recording.
PowerShell prerequisites
You need the following PowerShell setup before you create the Microsoft Teams compliance recording policy:
Requirement | Description |
PowerShell | Use PowerShell 5.1 or later. PowerShell 5.1 is included with Windows. |
Administrator mode | Run PowerShell as an administrator. |
Execution policy | Use an execution policy of at least |
Teams module | Use the Microsoft Teams PowerShell module. |
Microsoft Entra role | Use a Microsoft Entra administrator account that can configure Teams compliance recording policies. |
Microsoft provides setup guidance for the Microsoft Teams PowerShell module and installing Microsoft Teams PowerShell.
Connect to Microsoft Teams PowerShell
On your Windows computer, open the Start menu.
Search for PowerShell.
Right-click Windows PowerShell.
Click Run as Administrator. An elevated PowerShell window opens.
Set the execution policy to
RemoteSigned.Set-ExecutionPolicy RemoteSigned
For more information, see Microsoft’s Set-ExecutionPolicy documentation.
Install the Microsoft Teams PowerShell module.
Install-Module MicrosoftTeams
If the Microsoft Teams PowerShell module is already installed, update it.
Update-Module MicrosoftTeams
Import the Microsoft Teams PowerShell module.
Import-Module MicrosoftTeams
Connect to Microsoft Teams PowerShell with Microsoft Entra administrator credentials.
Connect-MicrosoftTeams
Create the compliance recording application instance
A Microsoft Teams compliance recording policy requires an application instance, a recording policy, and a recording application.
The application instance connects your Microsoft Entra tenant to the MCO recording application.
Create the application instance.
New-CsOnlineApplicationInstance -UserPrincipalName <email of the generated Microsoft Entra ID resource> -DisplayName <name for the generated Microsoft Entra ID resource> -ApplicationId 82da7f37-355e-4430-a678-1ff49f539458
The
ApplicationIdvalue82da7f37-355e-4430-a678-1ff49f539458is the MCO recorder application ID.Copy the
ObjectIdreturned by the command.If you need to retrieve the
ObjectIdlater, run this command:Get-CsOnlineApplicationInstance -DisplayName <the name you provided>
Synchronize the application instance into the Agent Provisioning Service.
Sync-CsOnlineApplicationInstance -ObjectId <the object ID of the application instance> -ApplicationId 82da7f37-355e-4430-a678-1ff49f539458
Create the compliance recording policy
The compliance recording policy defines which users are recorded.
Create the recording policy.
New-CsTeamsComplianceRecordingPolicy -Identity <provide a name for your policy> -Enabled $true
Save the policy name. You need it when you create the recording application and assign the policy.
NOTE: At this point, the policy exists but does not record calls or meetings until a recording application is assigned to it.
Create the recording application
The recording application associates the compliance recording policy with the application instance.
Create the recording application.
New-CsTeamsComplianceRecordingApplication -Parent <recording policy name> -Id <application instance object ID>
Confirm the
Parentvalue matches the policy name you created.Confirm the
Idvalue matches the application instanceObjectId.
Assign the compliance recording policy
Assign the recording policy to the users or groups that should be recorded.
NOTE: It may take a few minutes for the policy to take effect. Signed-in Teams users may need to sign out and sign back in to receive a new access token.
Assign the policy to all users
Use this option if all users in the tenant should use the recording policy.
Grant-CsTeamsComplianceRecordingPolicy -Global -PolicyName <recording policy name>
Assign the policy to one user
Use this option if only specific users should use the recording policy.
Grant-CsTeamsComplianceRecordingPolicy -Identity <user principal name> -PolicyName <recording policy name>
The user principal name is often the user’s email address, but it can be different. You can find the user principal name in the Microsoft Entra admin center.
To verify that the policy was assigned, run:
Get-CsOnlineUser <user principal name> | ft sipaddress, tenantid, TeamsComplianceRecordingPolicy
Assign the policy to a group
Use this option if users in a group should use the recording policy.
Grant-CsTeamsComplianceRecordingPolicy -Group <group object ID> -PolicyName <recording policy name>
You can find the group object ID in the Microsoft Entra admin center.
Connect Teams Voice and Meetings in MCO eComms
MCO eComms uses the MCO eComms Teams Archiver application to connect your Microsoft Teams environment to your MCO eComms account.
Sign in to MCO eComms as an administrator.
Go to Settings > Integrations.
Locate the Microsoft Teams Voice and Meetings integration.
Click the More options menu.
Click Connect. Microsoft prompts you to select the account used to install the MCO eComms app.
Sign in with a Microsoft Entra account that has the Application Administrator or Cloud Application Administrator role.
Review the confirmation message.
Approve the connection. Microsoft adds the MCO eComms application to your Microsoft Entra enterprise applications.
Return to MCO eComms and confirm the integration is connected.
Map covered users
Covered users must be mapped in MCO eComms before their Teams Voice and Meetings communications can be associated with the correct user profiles.
NOTE: The same users must also be included in the Microsoft Teams compliance recording policy.
Sign in to MCO eComms as an administrator.
Go to Settings > Users. The Users page opens.
Locate the user you need to map.
Click Edit. The user profile opens.
Locate the Sources section.
Click Edit in the Sources section. The section enters edit mode.
Click Add Source. A new source mapping row appears.
In Source name, select Teams V&M.
In Unique Identifier, enter the user’s Teams email address.
Click the check icon. The source mapping row is saved in the profile editor.
Add any additional Teams Voice and Meetings identities required for the user.
Click Save. MCO eComms saves the user profile.
Remove a recording policy assignment
Use this section only if you need to remove a compliance recording policy assignment from users or groups.
To remove a recording policy assignment, pass $null as the PolicyName value.
Grant-CsTeamsComplianceRecordingPolicy -Identity <user principal name> -PolicyName $null
Remove a compliance recording policy
Use this section only if you need to remove the policy from Microsoft Teams.
List the configured policies.
Get-CsTeamsComplianceRecordingPolicyRemove the policy.
Remove-CsTeamsComplianceRecordingPolicy -Identity <policy name>
NOTE: You may also need to remove related configuration entities, such as the application instance. The underlying user principal must be removed through Microsoft Entra directory operations.
Result
Microsoft Teams Voice and Meetings capture is configured. MCO eComms can use the MCO recording bot to capture supported Teams calls and meetings for users assigned to the compliance recording policy and mapped in MCO eComms.
Captured recordings and transcripts can be archived, monitored, and reviewed according to your organization’s configured policies and license limitations.