microsoft teams phone · published

Microsoft Teams compliance recording

Verified 2026-09-25 · 60 sources · tier 2

Also known as policy-based recording, third-party compliance recording.

Microsoft states that its compliance recording integration is designed specifically for policy-based compliance recording, and it does not support any other use of it 41. Setup relies on a certified third-party partner's recording solution paired with an Azure-hosted recording bot and Microsoft Teams policies 37​6​7.

How it works

Third-party compliance recording captures voice, video, and screen share; unlike native convenience recording, Microsoft does not list PowerPoint Live for it 29. The recording is initiated by the administrator (system), and the administrator or compliance officer owns storage and access, while retention is configured in the partner solution rather than in Teams 25. Third-party compliance recording enforces participant notification but does not support participant consent 32. Recorded users might not be able to disable compliance recording and might lack access to the recordings, depending on the partner solution and its configuration 59.

Teams compliance recording bots must run on a Windows virtual machine deployed in Azure 6. The recorder bot's outbound firewall must allow the Azure public IP range as a destination, and its inbound firewall must allow the Teams IP range as a source 5. Every partner solution uses the same key Graph APIs, an application instance, and a compliance recording policy, with the partner's bot paired to its recording solution 37. An application cannot record or persist media obtained through the Graph Media Access API until it calls updateRecordingStatus to signal that recording has begun and receives a success reply 23. The updateRecordingStatus request takes a status of notRecording, recording, or failed, alongside a clientContext string of up to 256 characters 24. The call supports only application permissions—Calls.AccessMedia.All as least privileged and Calls.JoinGroupCall.All as higher privileged—and does not support delegated permissions 22.

Policy configuration and administration

Configuration begins by creating an application instance with New-CsOnlineApplicationInstance using the ApplicationId provided by the recording partner, followed by running Sync-CsOnlineApplicationInstance on its ObjectId 53. The administrator then creates a policy using New-CsTeamsComplianceRecordingPolicy, attaches the instance via Set-CsTeamsComplianceRecordingPolicy -ComplianceRecordingApplications (configured using New-CsTeamsComplianceRecordingApplication), and assigns the policy using Grant-CsTeamsComplianceRecordingPolicy 54. Assigning a recording policy to a user does not activate recording by itself; a policy-based recording application instance must exist in the tenant and be associated with the policy 40.

Policies are managed with Microsoft Teams PowerShell and apply at the tenant (Global), per-user, or security-group level 44. The -Enabled parameter defaults to False, and recording begins only when -Enabled is True and valid ComplianceRecordingApplications are set 42. Assigning, enabling, or disabling a policy affects only new calls and meetings, leaving sessions already in progress unaffected 43.

A single compliance recording policy can hold multiple recording application instances, recording assigned users with each application 30. All recording applications on a policy are invited in parallel; the Priority parameter sets only their display order in Get-CsTeamsComplianceRecordingPolicy output without affecting routing or invite sequence 36.

Setting -RecordReroutedCalls to True (default False) extends recording to calls rerouted from an enabled user through forwarding, transfer, delegation, call groups, or simultaneous ring 45. The WarnUserOnRemoval parameter defaults to True and is documented as reserved for future use 60.

Session resilience and fail-closed controls

Recording application behavior during failures is governed by 4 strict-recording parameters:

  • RequiredBeforeCallEstablishment defaults to True, cancelling the call if the recorder fails to join; setting it to False allows the call to proceed without recording 46.
  • RequiredDuringCall defaults to True, cancelling the call if the recorder disconnects or drops mid-call; setting it to False allows the call to continue 48.
  • RequiredBeforeMeetingJoin defaults to True, blocking the recorded user from joining a meeting if the recorder fails to join, though other participants can continue 47.
  • RequiredDuringMeeting defaults to True, ejecting the recorded user from the meeting if the recorder leaves or drops 49.

WarmTransfer's reading of the sources is that because all 4 Required* flags default to True, an application associated without overriding them will likely make calls fail and block or eject recorded users from meetings whenever the recorder is unavailable 20.

For recorder resilience, an administrator can configure multiple invites using ConcurrentInvitationCount (which accepts only 1 or 2, defaulting to 1) or specify a paired bot with ComplianceRecordingPairedApplications, but cannot use both resilience mechanisms at the same time 9​35​50. An application can pair with at most 1 other application, and each paired application receives a separate invite 35. When using multiple invites or paired applications, invitation succeeds if at least 1 invite is accepted, failing only if all are rejected; the application remains present as long as at least 1 instance stays in the session 51.

Notifications and banners

Teams clients display a visual compliance-recording notice across desktop, web, mobile (iOS and Android), Teams Phones, and Teams Rooms 34. Audio notices play for SIP phones, Skype for Business, audio-conferencing dial-in users, and PSTN callers; PSTN callers hear the audio prompt in the recorded Teams user's default language 33. Setting -DisableComplianceRecordingAudioNotificationForCalls to True turns off audio notifications for 1:1 calls (default False) 21.

Custom banner text up to 1,000 characters is created using New-CsTeamsCustomBannerText and linked to a policy with the -CustomBanner GUID parameter 3. In meetings, the meeting organizer's effective policy sets the banner text, which appears to all participants once at least 1 internal recorded user joins; an external recorded user's banner is never displayed 2. On a two-party call, the caller's policy is evaluated first, followed by the callee's; once selected, that banner remains for the rest of the call even if additional participants join 4.

Call queues

Compliance Recording for Call Queues records all agent-answered inbound queue calls without assigning compliance policies to individual agents, ignoring any agent-level policy for those calls 14. Conversely, outbound calls placed by agents are recorded only if the agent has an assigned user compliance recording policy, and those calls are treated as user calls rather than queue calls 15. First-party Automatic Recording for Call Queue stores recordings and transcripts in SharePoint, whereas Compliance Recording for Call Queue uses a third-party recording bot 19.

Compliance Recording for Call Queues requires conference mode on the queue, and an application instance must exist prior to template creation 11. A template specifies the bot resource account, an optional paired bot, strict-recording toggles, and a concurrent invitation count 18. Up to 2 templates can be assigned per queue, and modifying a template alters every queue referencing it 18. For compliance-critical queues, Microsoft advises setting the template concurrent invitation count to 2, as parallel invites reduce join delays 10.

Call queue announcements operate under specific rules:

  • Arriving callers hear an announcement, which defaults to "This call will be recorded for compliance purposes" 12. Greetings are configured per queue, not in the template 12.
  • When strict recording is enabled and the bot fails to join or leaves mid-call, callers hear a failure announcement and the call disconnects 13.
  • If an agent adds a second queue with compliance recording enabled to an existing call, the second queue's recording settings are ignored 16.

As of August 17, 2026, Compliance Recording for Call Queues configuration is available in the Teams admin center under Voice > Templates and resources 17.

Partner ecosystem and support

Microsoft operates a partner certification program to verify quality, compatibility, and reliability 7. Customers must contact their recording partner first for enablement or operational issues, and Microsoft may reject support cases involving non-certified solutions 55. Compliance recording partners maintain their own licensing requirements, and the Compliance Recording for Call Queue licensing entry points only to third-party licensing 38.

Partner Solution Certification Status
ASC Technologies Certified 8
AudioCodes Interaction Insights Certified 8
CallCabinet Certified 8
Cloud World Wide Services Certified 8
Dubber Certified 8
Imagicle Certified 8
Insightful Technology Certified 8
Liquid Voice Certified 8
Luware Certified 8
NICE Engage Certified 8
NICE NTR-X Certified 8
Numonix Certified 8
NUSO Certified 8
Oak Innovation Certified 8
Theta Lake Certified 8
Tollring Certified 8
Touch Call Recording Certified 8
Verint EDM Certified 8
Verint Verba Certified 8
Eleveo In process of certifying 39
Redwood Technologies In process of certifying 39
Uniphore In process of certifying 39
Vox Solutions In process of certifying 39

Operational limits and constraints

Teams compliance recording is not supported for E911 emergency calling services 56. It is also unsupported for users operating in Survivable Branch Appliance (SBA) mode 58. WarmTransfer's reading of the sources is that because compliance recording is unsupported in SBA mode, calls handled while a branch runs on its SBA during a cloud outage will likely go unrecorded, which regulated deployments should plan for 52. Additionally, compliance recording is not supported for PSTN calls of users in India 57.

Microsoft states that the compliance recording platform is tested to scale to 750 users per meeting, and performance might be impacted above 750 users in paired bot mode 26. For extra-large meetings, Microsoft advises using events optimized for large audiences, such as town halls, and contacting the recording partner 27.

See also

Applicability

The Graph API that carries a third-party recorder's recording status is available in the global service, US Government L4 and US Government L5 (DoD), but not in China operated by 21Vianet 31.

User eligibility requires a Microsoft 365 A3, A5, E3, E5, G3, G5, Business Premium, or Business Standard license; an Office 365 A3, A5, E3, or E5 license; a Teams Rooms Pro or Basic license; or a Teams Shared Device license 28. PSTN calls for users located in India are excluded from compliance recording support 57.

What remains uncertain

The exact partner-specific storage, retention, and licensing mechanisms across individual certified third-party solutions are not covered by the sources below.

See also

Related to

Referenced by

  • Webex Calling call recording — Parallel compliance-recording topic on Microsoft Teams; same questions (provider choice and announcements and retention) on a different platform

Sources

  1. 1
    Microsoft's recording comparison table lists 'Audio only supported: No' for third-party compliance recording, yet the compliance recording pages describe recording PSTN calls, audio notices to PSTN and SIP callers, and call queue calls. What the row means is unresolved.disputed
    Introduction to recording Microsoft Teams calls, meetings, and events · Overview, comparison table row 'Audio only supported' · Checked 2026-09-25
  2. 2
    In meetings, the meeting organizer's effective compliance recording policy (user or Global) sets the custom banner text. It is shown to all participants once at least one internal compliance-recorded user joins, and an external recorded user's banner is never shown.
    Configure a custom banner for compliance recording in Microsoft Teams · How compliance recording policies determine banner text in meetings and calls > Meetings > Banner text policy behavior · Checked 2026-09-25
  3. 3
    Custom compliance recording banner text is created with New-CsTeamsCustomBannerText (maximum 1,000 characters) and attached to a policy through the -CustomBanner GUID on New- or Set-CsTeamsComplianceRecordingPolicy.
    Configure a custom banner for compliance recording in Microsoft Teams · Create and configure custom banner text > Step 1 table and Step 3 · Checked 2026-09-25
  4. 4
    In a two-party call the caller's effective policy is checked for banner text first, then the callee's; once a banner is selected it stays for the rest of the call even if more parties join.
    Configure a custom banner for compliance recording in Microsoft Teams · Two-party calls and group calls > Two-party calls · Checked 2026-09-25
  5. 5
    The recorder bot's outbound firewall must allow the Azure public IP range as destination, and its inbound firewall must allow the Teams IP range as source.
    Microsoft Teams compliance recording (third-party) · Recorder development, bot requirements list · Checked 2026-09-25
  6. 6
    A Teams compliance recording bot must run on a Windows virtual machine deployed in Azure.
    Microsoft Teams compliance recording (third-party) · Recorder development, bot requirements list · Checked 2026-09-25
  7. 7
    Microsoft runs a certification program for Teams compliance recording partners that tests and verifies each participating partner's solution for quality, compatibility and reliability.
    Microsoft Teams compliance recording (third-party) · Third-party compliance recording partners, first paragraph · Checked 2026-09-25
  8. 8
    As of its 2026-08-10 update, Microsoft's compliance recording page lists 19 certified partner solutions: ASC Technologies, AudioCodes Interaction Insights, CallCabinet, Cloud World Wide Services, Dubber, Imagicle, Insightful Technology, Liquid Voice, Luware, NUSO, NICE Engage, NICE NTR-X, Numonix, Oak Innovation, Theta Lake, Tollring, Touch Call Recording, Verint Verba and Verint EDM.
    Microsoft Teams compliance recording (third-party) · Third-party compliance recording partners, certified partners table · Checked 2026-09-25
  9. 9
    ConcurrentInvitationCount sets how many invites go to the same recording application for one call or meeting; it accepts only 1 or 2 and defaults to 1.
    New-CsTeamsComplianceRecordingApplication (MicrosoftTeams) · Parameters > -ConcurrentInvitationCount · Checked 2026-09-25
  10. 10
    For compliance-critical call queues, Microsoft advises setting the template's concurrent invitation count to 2, because parallel invites reduce join delays.
    Setup - Compliance Recording for Call Queues template · Create the compliance Recoding for call queue template, step 11 · Checked 2026-09-25
  11. 11
    Compliance Recording for Call Queues requires conference mode on the call queue, and a compliance recording application instance must exist before a call queue template can be created.
    Setup - Compliance Recording for Call Queues template · Prerequisites · Checked 2026-09-25
  12. 12
    When call queue compliance recording is enabled, all callers arriving at the queue hear a recording announcement, by default 'This call will be recorded for compliance purposes.' Greetings are set per queue, not in the template.
    Setup - Compliance Recording for Call Queues template · Recording announcement; Compliance recording for call queue templates, final paragraph · Checked 2026-09-25
  13. 13
    When call queue compliance recording is strict and the bot cannot join (Required before call) or leaves early (Required during call), callers hear a failure announcement and the call is disconnected.
    Setup - Compliance Recording for Call Queues template · Assign the template to the call queue > Recording failure announcement · Checked 2026-09-25
  14. 14
    Compliance Recording for Call Queues records all agent-answered inbound call queue calls without assigning a compliance recording policy to agents, and any agent policy is ignored for those calls.
    Microsoft Teams compliance recording (third-party) · Considerations > Call queues (Compliance Recording for Call Queues), first paragraph · Checked 2026-09-25
  15. 15
    Outbound calls made by call queue agents are recorded only if the agent has a user compliance recording policy, and those calls are treated as user calls not associated with the queue.
    Microsoft Teams compliance recording (third-party) · Considerations > Call queues, third paragraph · Checked 2026-09-25
  16. 16
    If an agent adds a second call queue with compliance recording enabled to an existing call, the second queue's compliance recording settings are ignored.
    Setup - Compliance Recording for Call Queues template · Unsupported calling scenarios · Checked 2026-09-25
  17. 17
    Microsoft's call queue what's-new list dated August 17, 2026 says Compliance Recording for Call Queues configuration is now available in the Teams admin center, under Voice > Templates and resources.
    Setup - Compliance Recording for Call Queues template · What's new in Call Queues (last six months) > August 17, 2026; Create the compliance Recoding for call queue template, step 1 · Checked 2026-09-25
  18. 18
    A Compliance Recording for Call Queue template names the recording bot resource account, an optional paired bot, strict-recording toggles and a concurrent invitation count. Up to two templates can be assigned per queue, and editing a template changes every queue that uses it.
    Setup - Compliance Recording for Call Queues template · Compliance recording for call queue templates; Create the compliance Recoding for call queue template, steps 7-11 · Checked 2026-09-25
  19. 19
    Automatic Recording for Call Queue is a separate first-party Microsoft feature that stores recordings and transcripts in SharePoint, whereas Compliance Recording for Call Queue uses a third-party recording bot.
    Planning - Recording voice applications calls · Automatic Recording for Call Queue; Compliance Recording for Call Queue · Checked 2026-09-25
  20. 20
    Because all four Required* flags default to True, a recording application associated without overriding them will likely make calls fail and block or eject recorded users from meetings whenever the recorder is unavailable.inferred
    New-CsTeamsComplianceRecordingApplication (MicrosoftTeams) · Parameters > -RequiredBeforeCallEstablishment, -RequiredDuringCall, -RequiredBeforeMeetingJoin, -RequiredDuringMeeting (default value tables) · Checked 2026-09-25
  21. 21
    Setting the policy parameter DisableComplianceRecordingAudioNotificationForCalls to True turns off recording audio notifications for compliance-recorded 1:1 calls; the default is False.
    Set-CsTeamsComplianceRecordingPolicy (MicrosoftTeams) · Parameters > -DisableComplianceRecordingAudioNotificationForCalls · Checked 2026-09-25
  22. 22
    updateRecordingStatus supports only application permissions: Calls.AccessMedia.All as least privileged and Calls.JoinGroupCall.All as higher privileged. Delegated permissions are not supported.
    call: updateRecordingStatus - Microsoft Graph v1.0 · Permissions table · Checked 2026-09-25
  23. 23
    An application may not record or persist media obtained through the Graph Media Access API until it has called updateRecordingStatus to indicate that recording has begun and received a success reply.
    call: updateRecordingStatus - Microsoft Graph v1.0 · Introductory 'Additional Restriction' note · Checked 2026-09-25
  24. 24
    The updateRecordingStatus request takes a status of notRecording, recording or failed, plus a clientContext string of up to 256 characters.
    call: updateRecordingStatus - Microsoft Graph v1.0 · Request body table · Checked 2026-09-25
  25. 25
    In compliance recording the recording is initiated by the admin (system), and the admin or compliance officer owns storage and access; retention is configured in the partner solution, not in Teams.
    Introduction to recording Microsoft Teams calls, meetings, and events · Overview, comparison table rows 'Recording initiator', 'Storage and access owner', 'Retention policy' · Checked 2026-09-25
  26. 26
    Microsoft says the compliance recording platform is tested to scale to 750 users per meeting, and performance might be impacted above 750 users in paired bot mode.
    Microsoft Teams compliance recording (third-party) · Considerations > Large meetings · Checked 2026-09-25
  27. 27
    For extra-large meetings, Microsoft advises using events optimized for large audiences, such as town halls, and contacting the recording partner.
    Microsoft Teams compliance recording (third-party) · Considerations > Large meetings, bullet list · Checked 2026-09-25
  28. 28
    To be eligible for Teams compliance recording, a user account needs one of: Microsoft 365 A3, A5, E3, E5, G3, G5, Business Premium or Business Standard; Office 365 A3, A5, E3 or E5; a Teams Rooms Pro or Basic license; or a Teams Shared Device license.
    Microsoft Teams compliance recording (third-party) · Considerations > Licensing · Checked 2026-09-25
  29. 29
    Third-party compliance recording captures voice, video and screen share; unlike native convenience recording, Microsoft does not list PowerPoint Live for it.
    Introduction to recording Microsoft Teams calls, meetings, and events · Overview, comparison table row 'Media recorded' · Checked 2026-09-25
  30. 30
    A single compliance recording policy can hold more than one recording application instance, in which case users assigned the policy are recorded by each of them.
    Set-CsTeamsComplianceRecordingPolicy (MicrosoftTeams) · Examples > Example 2 · Checked 2026-09-25
  31. 31
    The Graph API that carries a third-party recorder's recording status is available in the global service, US Government L4 and US Government L5 (DoD), but not in China operated by 21Vianet.
    Microsoft Teams compliance recording (third-party) · Compliance recording overview, national cloud deployments table · Checked 2026-09-25
  32. 33
    SIP phones, Skype for Business, audio-conferencing dial-in participants and PSTN callers receive an audio compliance-recording notice; PSTN callers hear it in the Teams user's default language.
    Microsoft Teams compliance recording (third-party) · Supported notification methods > Other endpoints - audio notice · Checked 2026-09-25
  33. 34
    Teams clients show a visual compliance-recording notice on desktop and web, mobile (iOS and Android), Teams Phones and Teams Rooms.
    Microsoft Teams compliance recording (third-party) · Supported notification methods > Teams clients - visual notice · Checked 2026-09-25
  34. 35
    A compliance recording application can be paired with at most one other recording application through ComplianceRecordingPairedApplications, and each paired application receives a separate invite.
    New-CsTeamsComplianceRecordingApplication (MicrosoftTeams) · Parameters > -ComplianceRecordingPairedApplications; Examples > Example 6 · Checked 2026-09-25
  35. 36
    All recording applications on a policy are invited in parallel; the Priority parameter only sets their display order in Get-CsTeamsComplianceRecordingPolicy output and does not affect invitation order or routing.
    New-CsTeamsComplianceRecordingApplication (MicrosoftTeams) · Parameters > -Priority · Checked 2026-09-25
  36. 37
    Every partner compliance recording solution uses the same key Graph APIs, an application instance and a compliance recording policy, with the partner's bot paired to its recording solution.
    Microsoft Teams compliance recording (third-party) · Recorder development, first paragraph · Checked 2026-09-25
  37. 38
    Microsoft states that compliance recording partners have their own licensing requirements, and the Compliance Recording for Call Queue licensing entry points only to third-party licensing.
    Planning - Recording voice applications calls · Licensing requirements, final sentence · Checked 2026-09-25
  38. 39
    Eleveo, Redwood Technologies, Uniphore and Vox Solutions are listed as being in the process of certifying, not as certified partners.
    Microsoft Teams compliance recording (third-party) · Third-party compliance recording partners, 'in the process of certifying' table · Checked 2026-09-25
  39. 40
    Assigning a Teams recording policy to a user does not by itself activate compliance recording; a policy-based recording application instance (bot) must also exist in the tenant and be associated with the policy.
    Set-CsTeamsComplianceRecordingPolicy (MicrosoftTeams) · Description, second paragraph · Checked 2026-09-25
  40. 41
    Microsoft states the compliance recording integration is designed specifically for policy-based compliance recording, and it does not support any other use of it.
    Microsoft Teams compliance recording (third-party) · Compliance recording overview, paragraph after the national cloud table · Checked 2026-09-25
  41. 42
    The -Enabled parameter of a Teams compliance recording policy defaults to False; recording starts only when it is True and valid ComplianceRecordingApplications are set.
    Set-CsTeamsComplianceRecordingPolicy (MicrosoftTeams) · Parameters > -Enabled, parameter properties table · Checked 2026-09-25
  42. 43
    Assigning, enabling or disabling a compliance recording policy affects only new calls and meetings; calls and meetings already in progress are unaffected.
    Set-CsTeamsComplianceRecordingPolicy (MicrosoftTeams) · Description, final paragraph; Parameters > -Enabled · Checked 2026-09-25
  43. 44
    Compliance recording policies are managed with Microsoft Teams PowerShell and can be applied at the tenant (Global), per-user or security-group level.
    Set up compliance recording in Microsoft Teams · Create and manage your compliance recording policy, second paragraph · Checked 2026-09-25
  44. 45
    RecordReroutedCalls (default False), when True, extends compliance recording to calls re-routed from a compliance-recording-enabled user via forward, transfer, delegation, call groups or simultaneous ring.
    Set-CsTeamsComplianceRecordingPolicy (MicrosoftTeams) · Parameters > -RecordReroutedCalls · Checked 2026-09-25
  45. 46
    RequiredBeforeCallEstablishment defaults to True: the call is cancelled if the recording application fails to join; if set to False, the call proceeds normally without it.
    New-CsTeamsComplianceRecordingApplication (MicrosoftTeams) · Parameters > -RequiredBeforeCallEstablishment · Checked 2026-09-25
  46. 47
    RequiredBeforeMeetingJoin defaults to True: the recorded user is not allowed to join a meeting if the recording application fails to join, though the meeting continues for users already in it.
    New-CsTeamsComplianceRecordingApplication (MicrosoftTeams) · Parameters > -RequiredBeforeMeetingJoin · Checked 2026-09-25
  47. 48
    RequiredDuringCall defaults to True: the call is cancelled if the recording application leaves or is dropped mid-call; if set to False, the call continues.
    New-CsTeamsComplianceRecordingApplication (MicrosoftTeams) · Parameters > -RequiredDuringCall · Checked 2026-09-25
  48. 49
    RequiredDuringMeeting defaults to True: the recorded user is ejected from the meeting if the recording application leaves or is dropped, while the meeting continues for other users.
    New-CsTeamsComplianceRecordingApplication (MicrosoftTeams) · Parameters > -RequiredDuringMeeting · Checked 2026-09-25
  49. 50
    Recorder resilience can come from multiple invites to the same application (ConcurrentInvitationCount) or from a paired application (ComplianceRecordingPairedApplications), but not both at once.
    New-CsTeamsComplianceRecordingApplication (MicrosoftTeams) · Parameters > -ConcurrentInvitationCount, final paragraph (repeated under -ComplianceRecordingPairedApplications) · Checked 2026-09-25
  50. 51
    With multiple invites or a paired application, invitation succeeds if at least one invite is accepted and fails only if all are rejected; the application counts as present while at least one instance remains in the session.
    New-CsTeamsComplianceRecordingApplication (MicrosoftTeams) · Parameters > -ConcurrentInvitationCount and -ComplianceRecordingPairedApplications, middle paragraphs · Checked 2026-09-25
  51. 52
    Because compliance recording is unsupported in Survivable Branch Appliance mode, calls handled while a branch runs on its SBA during a cloud outage will likely go unrecorded, which regulated deployments should plan for.inferred
    Microsoft Teams compliance recording (third-party) · Supported compliance recording capabilities > Considerations, unsupported list · Checked 2026-09-25
  52. 53
    Setup begins by creating an application instance with New-CsOnlineApplicationInstance using the ApplicationId supplied by the recording provider, then running Sync-CsOnlineApplicationInstance on its ObjectId.
    Set up compliance recording in Microsoft Teams · Create a compliance recording application instance · Checked 2026-09-25
  53. 54
    After the application instance exists, the admin creates a policy with New-CsTeamsComplianceRecordingPolicy, attaches the instance with Set-CsTeamsComplianceRecordingPolicy -ComplianceRecordingApplications (built with New-CsTeamsComplianceRecordingApplication), and assigns it with Grant-CsTeamsComplianceRecordingPolicy.
    Set up compliance recording in Microsoft Teams · Create and manage your compliance recording policy, steps 1 and 2 · Checked 2026-09-25
  54. 55
    For compliance recording enablement or operational issues, customers must contact their recording partner first; Microsoft may reject support cases involving a non-certified compliance recording solution.
    Microsoft Teams compliance recording (third-party) · Support boundaries · Checked 2026-09-25
  55. 56
    Teams compliance recording is not supported for E911 emergency calling services.
    Microsoft Teams compliance recording (third-party) · Supported compliance recording capabilities > Considerations, 'Compliance recording isn't supported for' list · Checked 2026-09-25
  56. 57
    Teams compliance recording is not supported for PSTN calls of users in India.
    Microsoft Teams compliance recording (third-party) · Supported compliance recording capabilities > Considerations, 'Compliance recording isn't supported for' list · Checked 2026-09-25
  57. 58
    Teams compliance recording is not supported for users operating in Survivable Branch Appliance mode.
    Microsoft Teams compliance recording (third-party) · Supported compliance recording capabilities > Considerations, 'Compliance recording isn't supported for' list · Checked 2026-09-25
  58. 59
    Depending on the partner solution and its configuration, recorded users might not be able to disable compliance recording and might not have access to the recordings.
    Microsoft Teams compliance recording (third-party) · Supported notification methods, first paragraph · Checked 2026-09-25
  59. 60
    The WarnUserOnRemoval policy parameter is documented as reserved for future use (default True).
    Set-CsTeamsComplianceRecordingPolicy (MicrosoftTeams) · Parameters > -WarnUserOnRemoval · Checked 2026-09-25

Documents

tier 2 current vendor documentation

call: updateRecordingStatus - Microsoft Graph v1.0

Microsoft · 2024-04-04 · accessed 2026-09-25

tier 2 current vendor documentation

Configure a custom banner for compliance recording in Microsoft Teams

Microsoft · 2026-07-02 · accessed 2026-09-25

tier 2 current vendor documentation

Introduction to recording Microsoft Teams calls, meetings, and events

Microsoft · 2024-11-11 · accessed 2026-09-25

tier 2 current vendor documentation

Microsoft Teams compliance recording (third-party)

Microsoft · 2026-07-20 · accessed 2026-09-25

tier 2 current vendor documentation

New-CsTeamsComplianceRecordingApplication (MicrosoftTeams)

Microsoft · 2025-08-01 · accessed 2026-09-25

tier 2 current vendor documentation

Planning - Recording voice applications calls

Microsoft · 2026-08-31 · accessed 2026-09-25

tier 2 current vendor documentation

Set up compliance recording in Microsoft Teams

Microsoft · 2026-07-20 · accessed 2026-09-25

tier 2 current vendor documentation

Set-CsTeamsComplianceRecordingPolicy (MicrosoftTeams)

Microsoft · 2025-08-01 · accessed 2026-09-25

tier 2 current vendor documentation

Setup - Compliance Recording for Call Queues template

Microsoft · 2026-08-31 · accessed 2026-09-25

Cite this page

APA

WarmTransfer. (2026, September 25). Microsoft Teams compliance recording. WarmTransfer. https://warmtransfer.net/knowledge/teams-compliance-recording

BibTeX

@misc{warmtransfer-teams-compliance-recording,
  title  = {Microsoft Teams compliance recording},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/teams-compliance-recording},
  note   = {Verified 2026-09-25}
}