Skip to main content
CallTower Solutions Center

MS Teams Atmos Call Recording - Configure Office 365 for Compliance Recording

This document will take you through the installation and set up instructions to both install and configure the Atmos Teams recording policy and bot.

  1. Access to PowerShell ISE in Admin mode
  2. Microsoft Teams Powershell 5.1 or higher.
  3. Teams Admin (or Global Admin) permissions to your Microsoft 365 Tenant.
  4. Microsoft Azure account with active subscription is required but is a free service. Microsoft will ask for you to enter your credit card information when creating a new Azure subscription. However, the bot will be created using the free teir. Recordings are stored on CallCabinets service and not within your Azure enviroment.


Create the Atmos Teams Bot:

Note: because this installation takes place in a browser, some of the page elements can be obscured if the browser window is too small.. We recommend you maximize your browser window size before proceeding.

Register the bot Channel:

  1. log into azure ( using the same domain \ admin account that you use to administer Teams (Note: it is important that the bot resides within the same domain)
  2. Search for and select Bot Services, then Click "+ Create":
    1. clipboard_e01d5f9445d8cc5d6945ab64f4cdd98f8.png
  3. Scroll to the bottom of the list and find "Azure Bot" (Note: click "Load More" if it doesn't appear)
    1. clipboard_e9b7608f5389cd569e66f52a290e6c250.png
  4. Click on "Create"
    1. clipboard_e2915e8813e06ff9b331930cb7ddf6a71.png
  5. Fill out the form with the following values:
            a. Bot Handle: AtmosTeamsBot<<Customer Name>>
            b. Select your Subscription and Resource group or Create a new Resource Group. (*NOTE: your subscription may have a different name)
            c. Change the Pricing Tier to "Free" and Type of App to "Single Tenant"
            d. Select "Create New Microsoft App ID". Then Click "Review + Create"clipboard_e83b11f6e5c0438df3de8a754beeb87e9.png
  6. Make sure the validation passes and click "Create"
    1. clipboard_ec8b5fa99f6e04cb4b0f9cf88b1c0ab65.png
  7. Once created go to the resouce then Channels (deprecated) and Connect to the Teams channel


  1. Click "Configuration" from the left menu
    • clipboard_e17749fbaf449c8b469045163ccf0dd1b.png
    • Copy the "Microsoft App ID" to a separate document you will need this later during the setup process.
    • Click "Manage" (in blue next to the Microsoft App ID, above the actual App ID)
  2. Add a "New Client Secret"
    • clipboard_eb663d66a34890ab2daf4f3c7bfcf76fc.png
    • Click on "New client secret.", give it a description set it to 24 months expire and click add:
    • clipboard_ec6c59501f60ef6d7585bf7170c1287af.png
    • Copy the Secret Value to a seperate document for later use. The secret value will be needed by the Atmos Teams Recorder.
    • Note: The secret key value will not be available after save, so it MUST be saved to an external document.
  3. Click "Authentication" on the left hand menu
    • clipboard_e6ff28b5ae197255f595e6da46787be93.png
    • Click "Add a platform"
    • clipboard_ee6ff17946d1941161ec5246b6a8dc71e.png
    • Select "Web"
    • clipboard_ed0a368e2c6d61a0982f34e2caf2d44e0.png
    • Enter "" as the Redirect URI and Click "Configure"
    • Configure API Permissions
    • clipboard_e8cca520d03209c2cc0c9e50f68ece7ea.png
    • Select API Permissions then click on "Add a permission" and Select "Microsoft Graph"
    • clipboard_ed11fb4f3c1dcb4b2a5a6ca811d241678.png
    • Select Application permissions. This will expand the permissions menu.
    • clipboard_ef05bd230f3117c9cc0cad0ff3414e928.png
    • open the "CallRecords" permission and click the checkbox:clipboard_e3c01873a54c576ba7d325805a5e2d0d5.png
    • open the "Calls" permission and click on the selected checkboxes:clipboard_edb53436083af527255a489b04b6ae49d.png
    • Open the "OnlineMeetings" permission and click on the checkboxes:clipboard_efea2344695f8be829a9add3c6de6913c.png
    • Open the "User" permissions then click the selected checkboxe: clipboard_e074b46e27a8a098ebcccad13b4da8a30.png
    • Click "Add permissions" to add the permissions.
    • clipboard_e406ac7d481605643c36b5f8a87eb8eec.png
    • Ensure the API/Permission names match the previous steps. then click "Grant admin consent for ....". You will be prompted to confirm grant of admin consent. Click Yes. It may be necessary to refresh your screen to update the Microsoft Graph Status column.
    • clipboard_e5ed77486edfb16a7a8fdf9d614546867.png
    • Grant Admin Consent, In order to grant admin consent you will need to construct the admin consent URL. It will help you to have a simple text application like notepad open for copying and pasting the text strings involved in the following steps. When you're ready to continue:
    • Copy the URL into a web browser and grant permissions using an admin account on the tenant.
    • clipboard_edc76339558982216f2c887f4f11aa24a.png
    • Click Accept

Setup the Atmos Teams Application and Recording Policy

  1. In Azure Active Directory go to Groups and create a Recording group "Atmos Teams Recording".
  2. Open the group and Make note of the Object ID for the Group.
  3. run the following powershell after replacing the key values at the start of the the script

#Get Connected to Microsoft Teams PowerShell
Install-Module MicrosoftTeams
Import-Module MicrosoftTeams

### New Atmos Bot + Policies
### Important please update the following values for your environment.
$applicationid = "<< Paste Application ID Here >>" # the application ID for the bot from azure subscription
$securitygroupid = "<< Paste Security Group Object ID Here >>" # Group ID for assigning recording policy.
$domain = "<< Your Domain Name Here >>" # your primary domain for the bot (i.e.
$botname = "atmosteamsbot" # Bot Username
$botdisplayname = "Atmos Bot App" # Bot Display Name
$policyname = "AtmosTeamsRecordingPolicy" # Recording Policy Policy Name

# Create Atmos Bot
New-CsOnlineApplicationInstance -UserPrincipalName "$botname@$domain" -DisplayName $botdisplayname -ApplicationId $applicationid
$appinstance = Get-CsOnlineApplicationInstance "$botname@$domain"
Start-Sleep -Seconds 15
Sync-CsOnlineApplicationInstance -ObjectId $appinstance.ObjectId

# Create Compliance Recording Policy on Tenant.
New-CsTeamsComplianceRecordingPolicy -Enabled $true -Description $policyname -Identity $policyname
Start-Sleep -Seconds 15
Set-CsTeamsComplianceRecordingPolicy -Identity $policyname -ComplianceRecordingApplications @(New-CsTeamsComplianceRecordingApplication -Parent $policyname -id $appinstance.ObjectId)
Start-Sleep -Seconds 15
Set-CsTeamsComplianceRecordingApplication -Identity "Tag:AtmosTeamsRecordingPolicy/$($appinstance.ObjectId)" -RequiredBeforeCallEstablishment $false -RequiredDuringCall $false -RequiredBeforeMeetingJoin $false -RequiredDuringMeeting $false
Start-Sleep -Seconds 15

# Assign Compliance Policy to Security Group
New-CsGroupPolicyAssignment -GroupId $securitygroupid -PolicyType TeamsComplianceRecordingPolicy -PolicyName $policyname -Rank 1


If you want to disable the audio notification for calls run this command:

Set-CsTeamsComplianceRecordingPolicy -Idenity "AtmosTeamsRecordingPolicy" -DisableComplianceRecordingAudioNotificationForCalls $true

Final Steps

  • Send an email to your CallTower IPM with the following information:
    • The Bot Name (Bot handle)
    • The Bot Microsoft App Id       
    • The Client Secret (secret key)
    • The Directory Tenant ID
    • Customer Name (as shown on the CallCabinet activation email)
    • Customer ID (as shown on the CallCabinet activation email)
    • Site name (of your initial site as shown on the CallCabinet activation email)
    • Site ID (as shown on the CallCabinet activation email)
    • Webhook used in the Register the Bot Channel section above
  • Add Users to the group and begin testing once you get confirmation that the recording setup is completed.