The Microsoft Teams Cloud Recorder, also called API ingestion, lets Conversation Intelligence capture your Microsoft Teams meetings through Microsoft Teams' own cloud recording instead of the Conversation Intelligence bot joining the meeting. When the meeting ends and Microsoft Teams finishes processing the recording, Conversation Intelligence imports it and generates the transcript, AI summary, and action items. Use the Cloud Recorder when your organization restricts third-party bots in meetings.
You choose one recording method for your entire organization, either the bot or the Cloud Recorder. You cannot set the method per user.
In this article, you will learn how to configure the Microsoft Teams Cloud Recorder for your team, from the required Microsoft licensing and policies through to your Conversation Intelligence recorder settings.
This article includes:
The Cloud Recorder works for a user only when all three of the following are in place. If any one is missing, the integration can appear approved but does not import recordings.
- A qualifying Microsoft 365 license and a Microsoft Teams meeting policy that allows recording and transcription.
- Organization-level admin consent for the Conversation Intelligence app's Microsoft Graph permissions.
- A Microsoft Teams Application Access Policy that grants the app access to the meeting data of specific users or groups.
Before you configure the Cloud Recorder, you must:
- Be a Salesloft admin.
- Have access to a Microsoft admin who holds the Teams Administrator role to run the PowerShell steps and manage meeting policies.
- Have access to a Microsoft admin who holds the Cloud Application Administrator or Application Administrator role to approve the app's permissions.
- Have access to a Microsoft admin who holds the Exchange Administrator or Groups Administrator role, if you plan to cover users through a group.
- Can run PowerShell on a Windows, macOS, or Linux machine.
Each method has trade-offs. Review the differences before you change your recording method.
|
Aspect
|
Conversation Intelligence Bot
|
Microsoft Teams Cloud Recorder
|
|
Real-time features
|
Live transcription supports real-time features, such as battlecards.
|
No live transcription, so no real-time features.
|
|
Availability in Conversation Intelligence
|
Within minutes of the call ending.
|
Conversation Intelligence checks for new recordings every 15 minutes, and Microsoft Teams must finish processing first. Expect a longer delay.
|
|
AI summary and action items
|
Available.
|
Available, identical to bot-recorded calls.
|
|
Bot in the meeting
|
The bot appears in the participant list.
|
No bot joins the meeting.
|
|
Stopping a recording for confidential topics
|
Remove the bot from the meeting.
|
Stop or pause the recording in Microsoft Teams. If a recording is paused and resumed, only the longest recording is imported.
|
|
Consent
|
Conversation Intelligence consent features apply.
|
Limited to what Microsoft Teams offers natively.
|
|
Externally hosted meetings
|
The bot can join and record.
|
Cannot be imported. The recording goes to the external host's Microsoft Teams cloud, which Salesloft cannot access.
|
Scenarios
- Your security team blocks third-party bots: Use the Cloud Recorder.
- Your reps rely on real-time battlecards: Use the bot.
- Many of your meetings are hosted by customers or prospects: Use the bot. Cloud recordings of externally hosted meetings cannot be imported.
- You want internal meetings on the Cloud Recorder and external meetings on the bot: Not available. You choose one method for your organization.
Complete Parts 1 through 3 before you switch your recording method in Part 4. Switching to the Cloud Recorder turns off the Conversation Intelligence bot for all Microsoft Teams meetings, so recordings are not captured until the Microsoft setup is complete.
Parts 1 and 3 include PowerShell commands. To run a command, copy it, paste it into your PowerShell session, and press Enter. Where a command contains example values, such as "user@yourdomain.com", replace them with your own before you run it.
If you have not set up PowerShell, complete "Prepare PowerShell" in Part 3 first.
Part 1: Confirm Licensing and Meeting Policy in Microsoft
The Cloud Recorder retrieves recordings that Microsoft Teams creates. Microsoft Teams recording and transcription must be licensed and turned on for each user, independent of any Conversation Intelligence setting.
Confirm licensing
Both the meeting organizer and the recorder must have one of the following licenses: Office 365 Enterprise E1, E3, E5, F3, A1, A3, A5, or Microsoft 365 Business, Business Premium, or Business Essentials. The same license tiers cover base transcription.
- Go to the Microsoft 365 admin center (admin.microsoft.com).
- Select Users > Active users, and then select the user.
- Select Licenses and apps, and confirm the user has a qualifying license.
Things to Note: Live translated transcription and Intelligent Recap (AI-generated notes and chapters) additionally require Microsoft Teams Premium or Microsoft 365 Copilot licensing. They are not required for the Cloud Recorder to retrieve recordings and transcripts.
Enable recording and transcription in the meeting policy
A licensed user can still be blocked if the meeting policy does not allow recording and transcription. Use one of the following options:
- Option 1: Microsoft Teams admin center
- Go to the Microsoft Teams admin center (admin.teams.microsoft.com) > Meetings > Meeting policies.
- Open Global (Org-wide default), or select Add to create a custom policy, such as RecordingEnabledPolicy.
- Under Recording & transcription, turn on Cloud recording and Transcription, and then select Save.
- If you created a custom policy, assign it from Manage users or from each user's Policies page.
- Option 2: PowerShell: Use this option if you prefer to run commands instead of using the admin center. Run the commands in a PowerShell session that is connected to your Microsoft tenant. If you have not set that up, complete "Prepare PowerShell" in Part 3 first. Choose one of the following approaches. Run only the commands for the approach you choose:
- Turn on recording and transcription for your entire organization. This command changes the Global policy, which applies to every user who does not have a custom policy.
- Set-CsTeamsMeetingPolicy -Identity Global -AllowCloudRecording $true -AllowTranscription $true
- Turn on recording and transcription for specific users. The first command creates a custom policy named RecordingEnabledPolicy with recording and transcription turned on. The second command assigns that policy to one user. Run the second command once for each user, and replace user@yourdomain.com with the user's email address.
- Set-CsTeamsMeetingPolicy -Identity "RecordingEnabledPolicy" -AllowCloudRecording $true -AllowTranscription $true
- Grant-CsTeamsMeetingPolicy -Identity "user@yourdomain.com" -PolicyName "RecordingEnabledPolicy"
- Turn on recording and transcription for a group. Run the first command from the previous approach to create the custom policy, if you have not already. Then run the following command to assign the policy to a group, and replace GroupObjectId with the Object ID of your group from Microsoft Entra.
- Grant-CsTeamsMeetingPolicy -Group "GroupObjectId" -PolicyName "RecordingEnabledPolicy"
Things to Note: The meeting policy controls whether recording and transcription can happen at all. The Application Access Policy in Part 3 controls whether the Conversation Intelligence app can retrieve the results. They are separate policy objects, and you need both.
Part 2: Connect Microsoft Teams and Approve the App's Permissions
- In Salesloft, go to Settings > Conversation Intelligence > Integrations > Web Conferencing, and connect Microsoft Teams through an admin account.
- Sign in as a Microsoft admin who holds the Cloud Application Administrator or Application Administrator role.
- Review the Microsoft Graph permissions the app requests. The app appears in Microsoft Entra as prod-clari-teams-cloud-sync.
- Select Accept to grant organization-level consent
Things to Note: This step authorizes the app for your organization. It does not give the app access to any user's meetings. You grant that access in Part 3.
Part 3: Grant the App Access to Users with an Application Access Policy
Microsoft requires an Application Access Policy when an app uses application permissions to reach meeting data through the Microsoft Graph cloud communications API. You define which users the app can access. You run this step in PowerShell, and you can repeat it any time you need to add, change, or remove coverage.
Use this Application Client ID. It identifies the Conversation Intelligence app to Microsoft, and you enter it exactly as shown in the command that creates the policy: 48be434e-a8ec-4cd7-9763-e628b57acb47
Prepare PowerShell
PowerShell is Microsoft's command-line tool for managing settings. Complete these steps once on the computer you will use. A Microsoft admin who holds the Teams Administrator role must sign in.
- Check whether PowerShell is installed. Open a terminal and run the following command. If it shows a version number, PowerShell is installed.
pwsh --version - If PowerShell is not installed on macOS, install it with Homebrew: brew install powershell.
- Start a PowerShell session: Run: pwsh
- Install the Microsoft Teams module if you do not already have it. The module adds the Teams commands that you use in the rest of this article.
Install-Module -Name MicrosoftTeams -Force -AllowClobber - Connect to your tenant. Run the following command. PowerShell displays a web address and a code. The device-code sign-in works on macOS, Windows, and Linux: open the address in a browser, enter the code, and sign in as a Teams Administrator.
Connect-MicrosoftTeams -UseDeviceAuthentication
Things to Note: On macOS, running Connect-MicrosoftTeams without -UseDeviceAuthentication on module version 8.0.0 produced a kernel32.dll error during testing. Use -UseDeviceAuthentication to avoid it.
Create the access policy
Run this command in your connected PowerShell session to create the policy. You create the policy once. The command names the policy CloudRecorderPolicy and identifies the Conversation Intelligence app by its Client ID. You do not change any values. The backtick at the end of the first two lines tells PowerShell the command continues on the next line, so paste all three lines together.
New-CsApplicationAccessPolicy -Identity "CloudRecorderPolicy" `
-AppIds "48be434e-a8ec-4cd7-9763-e628b57acb47" `
-Description "Allows the Conversation Intelligence Cloud Recorder to access meeting data"
A successful command returns no output. At this point the policy exists but does not cover any users.
To confirm the policy exists, run:
Get-CsApplicationAccessPolicy -Identity "CloudRecorderPolicy"
Choose who the policy covers
Assign the policy to the users whose meetings you want Conversation Intelligence to record. Complete Option A to cover individual users, or Option B to cover a group.
Option A: Grant access to individual users
Run the following command once for each user who needs coverage, and replace user@yourdomain.com with the user's email address.
Grant-CsApplicationAccessPolicy -PolicyName "CloudRecorderPolicy" -Identity "user@yourdomain.com"
Each user can hold only one application access policy at a time. Assigning a new policy overwrites any policy the user already has.
Option B: Grant access to a group
The group must be a mail-enabled security group. You must hold the Exchange Administrator or Groups Administrator role to create one. If you already have a suitable group, skip to assigning the policy.
To create the group in the Exchange admin center:
- Go to admin.exchange.microsoft.com > Groups, and select Add a group.
- For Group type, select Mail-enabled security, and then select Next.
- Under Basics, enter a display name, such as Cloud Recorder Users, add a description if you want, and then select Next.
- Under Owners, assign one or more owners, and then select Next.
- Under Members, add the users whose meetings you want to record, and then select Next.
- Under Settings, set the group's primary SMTP address, such as recorder-users@yourdomain.com, and then select Next.
- Review the summary, and then select Create group. The group appears under Groups > Mail-enabled security.
To create the group with PowerShell instead, run the following commands. The first two install the Exchange Online module and sign you in to Exchange. The third creates the group, and the fourth adds a user to it. Replace the example group name, email addresses, and user with your own, and run the fourth command once for each user you want to add.
Install-Module -Name ExchangeOnlineManagement
Connect-ExchangeOnline
New-DistributionGroup -Name "Cloud Recorder Users" -Alias "recorder-users" -Type Security -PrimarySmtpAddress "recorder-users@yourdomain.com"
Add-DistributionGroupMember -Identity "recorder-users@yourdomain.com" -Member "user@yourdomain.com"
Then return to your Microsoft Teams PowerShell session and run the following command to assign the policy to the group. Replace recorder-users@yourdomain.com with your group's email address.
Grant-CsApplicationAccessPolicy -PolicyName "CloudRecorderPolicy" -Group "recorder-users@yourdomain.com"
Things to Note: Microsoft documents the -Group parameter but does not list the supported group types. Community guidance indicates that only mail-enabled security groups work. Standard Microsoft 365 groups and distribution lists do not. Membership changes propagate after a short synchronization delay. Test the group assignment in a non-production environment before you deploy it.
Verify who is covered
Run any of the following commands to check coverage. Replace user@yourdomain.com with the user's email address where it appears.
Get-CsApplicationAccessPolicy
Get-CsOnlineUser -Identity "user@yourdomain.com" | fl ApplicationAccessPolicy
Get-CsOnlineUser -Filter {ApplicationAccessPolicy -eq "CloudRecorderPolicy"}
The first command lists every application access policy in your tenant. The second checks whether a specific user has the policy. The third lists everyone the policy currently covers. Microsoft does not publish a service-level agreement for policy propagation, so a new assignment can take time to take effect. Check coverage again if access is not active right away.
Remove access
To stop the Cloud Recorder from accessing a user's meetings, remove the policy from that user. Run the following command, and replace user@yourdomain.com with the user's email address. The $null value clears the policy:
Grant-CsApplicationAccessPolicy -Identity "user@yourdomain.com" -PolicyName $null
To remove coverage for a group, run the following command, and replace recorder-users@yourdomain.com with your group's email address:
Grant-CsApplicationAccessPolicy -Group "recorder-users@yourdomain.com" -PolicyName $null
Things to Note: Microsoft documents $null for individual users but does not provide an example that pairs -Group with $null. Confirm the command works in your tenant before you rely on it. Alternatively, remove the user from the mail-enabled security group, and coverage updates after synchronization.
Part 4: Set Your Recorder Settings in Conversation Intelligence
- Navigate to Recorder settings: Go to Settings > Conversation Intelligence > Recorder and Transcription > Recorder settings.
- Select the recording method: Under Microsoft Teams, set the recording method to Cloud Recorder. This turns off the Conversation Intelligence bot for all Microsoft Teams meetings.
- Enable auto-record (optional): Turn on Auto-record Microsoft Teams calls to import calls automatically. If you leave it off, the meeting host must start the recording in Microsoft Teams.
- Choose which recordings to import: Select one of the following:
- All cloud recordings from recording users
- Recordings for meetings scheduled on the recording user's calendar
- Only meetings that match the auto-recording configuration
- Set the auto-recording rule: If you selected the third option, choose one of the following:
- Any meeting with an external participant
- Any meeting with an external participant where the host is a recording user
- All meetings
- Exclude domains and emails (optional): Add domains or email addresses to Restricted Domains and Restricted Emails to exclude them from auto-recording.
- Let users override (optional): Turn on Allow users to control recording of their meetings so users can override the organization-wide auto-record setting for their own meetings.
- Sign in to Microsoft Teams as a user covered by the Application Access Policy, and then schedule and join a test meeting that the user hosts.
- In the meeting, select More > Record and transcribe > Start recording.
- Record a short audio sample, and then end the meeting.
- Wait for Microsoft Teams to finish processing the recording. Conversation Intelligence then checks for it on its next 15-minute cycle.
- In Conversation Intelligence, confirm the meeting appears with its recording, transcript, AI summary, and action items.
Setup Checklist
- Each user has a qualifying Microsoft 365 license.
- The Microsoft Teams meeting policy has cloud recording and transcription turned on for each user.
- Microsoft Teams is connected in Conversation Intelligence, and admin consent is approved in Microsoft Entra.
- The application access policy is created with the correct Application Client ID.
- Users or a group are granted the policy, and Get-CsOnlineUser confirms they are covered.
- The recording method is set to Cloud Recorder in Recorder settings.
- A test meeting appears in Conversation Intelligence for at least one covered user.
- The meeting host starts a recording in Microsoft Teams, either manually or because auto-record applies to the meeting.
- The call ends, and Microsoft Teams processes the recording in its cloud.
- Conversation Intelligence checks Microsoft Teams for new cloud recordings every 15 minutes.
- If you select Only meetings that match the auto-recording configuration, Conversation Intelligence checks your configuration twice: before the call to decide whether auto-recording applies, and after the recording is available to decide whether to import it.
- If the call qualifies, Conversation Intelligence imports it and generates the transcript, AI summary, and action items.
- The Cloud Recorder cannot provide real-time transcription or live in-call features.
- A recording appears in Conversation Intelligence no sooner than 15 minutes after Microsoft Teams finishes processing it.
- You can stop a recording only from within Microsoft Teams.
- If a host pauses and resumes a recording, Conversation Intelligence imports only the longest recording.
- Conversation Intelligence does not add its own consent experience to Cloud Recorder meetings. Consent is limited to Microsoft Teams settings, such as the options your Microsoft Teams admin configures to prevent non-consenting participants from using their microphone or video.
- Conversation Intelligence cannot import recordings of meetings hosted by an external party.
PowerShell Command Reference
Action
|
Command
|
|---|
|
Install the module
|
Install-Module -Name MicrosoftTeams -Force -AllowClobber
|
|
Connect to your tenant
|
Connect-MicrosoftTeams -UseDeviceAuthentication
|
|
Enable recording and transcription in a policy
|
Set-CsTeamsMeetingPolicy -Identity <name> -AllowCloudRecording $true -AllowTranscription $true
|
|
Assign a meeting policy to a user
|
Grant-CsTeamsMeetingPolicy -Identity <user> -PolicyName <name>
|
|
Create the access policy
|
New-CsApplicationAccessPolicy -Identity <name> -AppIds <id> -Description <text>
|
|
Grant access to a user
|
Grant-CsApplicationAccessPolicy -PolicyName <name> -Identity <user>
|
|
Grant access to a group
|
Grant-CsApplicationAccessPolicy -PolicyName <name> -Group <group>
|
|
List all access policies
|
Get-CsApplicationAccessPolicy
|
|
Check a user's access policy
|
Get-CsOnlineUser -Identity <user> | fl ApplicationAccessPolicy
|
|
List users on a policy
|
Get-CsOnlineUser -Filter {ApplicationAccessPolicy -eq <name>}
|
|
Remove access from a user
|
Grant-CsApplicationAccessPolicy -Identity <user> -PolicyName $null
|
|
Remove access from a group (not verified by Microsoft)
|
Grant-CsApplicationAccessPolicy -Group <group> -PolicyName $null
|
Microsoft Documentation
Troubleshooting Tips
- A recording does not appear. Wait at least 15 minutes after Microsoft Teams finishes processing it. If it still does not appear, confirm that the meeting was hosted in your Microsoft Teams tenant and that it matches the recording import option you selected.
- The app is approved, but a user's recordings and transcripts are not imported. A missing Application Access Policy is the most common cause. Application permissions alone are not sufficient, and the app fails with an authorization error until the policy is assigned to the user. Check each layer in order:
- The user has a qualifying license, and their Microsoft Teams meeting policy has recording and transcription turned on.
- Admin consent was completed in Microsoft Entra.
- The user, or a group the user belongs to, has been granted the Application Access Policy.
- No application access policy is found for the app. Confirm that the policy name matches exactly between New-CsApplicationAccessPolicy and Grant-CsApplicationAccessPolicy. If you assign the policy to a group, confirm that the group is a mail-enabled security group and that you reference it by its email address.
- A new assignment does not take effect. Wait for synchronization, and then run the verification commands in Part 3 again.