Onboarding Step 2 – Configure Recording Profile
After completing Onboarding Step 1 – Grant MS365 Admin Consents, configure recording profiles, which define which calls are recorded and how the recordings are handled. On the onboarding wizard page, click Configure Recording Profile.
| ➢ | To set up a Recording Profile: |
| 1. | Configure the Recording Profile (see Adding Recording Profiles for details), then click Next. |
| 2. | Assign one or more Azure groups to the profile: |
| a. | Log in to the Azure portal for your tenant to confirm which group you wish to associate with the profile. |
| b. | Return to the Recording Profile; start typing the name of the group, and then click Add Group. |
If you later add or remove group members, you must perform a synchronization operation (see Synchronizing Recording Profiles).
Once assigned, the confirmation message below is displayed.
| c. | Click Next to continue. |
| 3. | Configure the following MSFT Policies: |
| ● | Disconnect Calls when Recorder Unavailable: Calls are disconnected when recording functionality is not available. |
| ● | Disable Compliance Recording Audio Notifications: Disable Microsoft Teams Recording banner notifications. |
| 4. | Click the Download Configuration Script link to download the Recording Profile script. |
| 5. | Open PowerShell console and run the following policy: |
Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope LocationMachine
The following message may appear in the console if the above command is not run.
| 6. | Run the script create<RecordingProfileName>-dd-m-yyyy.ps1 as Administrator. Once running, you are prompted to enter the credentials of the Azure customer tenant account. |
The M365 tenant administrator running the script must have 'Teams Administrator' permissions.
| 7. | Enter Admin credentials of your customer tenant and authenticate the tenant using the Microsoft Authenticator when prompted. |
The script supports Multifactor authentication.
Once the script has successfully completed, a confirmation message is displayed in the PowerShell console as shown below.