Microsoft Teams compliance recording (third-party)

Publisher

Microsoft

URL

https://learn.microsoft.com/en-us/microsoftteams/teams-recording-compliance

Published

2026-07-20

Updated

unknown

Accessed

2026-09-25

HTTP status

200

License

Microsoft Learn content; Microsoft Terms of Use; no-redistribution; short excerpts and locators only

Source notes citing this source

• 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. in context
• A Teams compliance recording bot must run on a Windows virtual machine deployed in Azure. in context
• Microsoft runs a certification program for Teams compliance recording partners that tests and verifies each participating partner's solution for quality, compatibility and reliability. in context
• 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. in context
• 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. in context
• 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. in context
• 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. in context
• For extra-large meetings, Microsoft advises using events optimized for large audiences, such as town halls, and contacting the recording partner. in context
• 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. in context
• 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. in context
• 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. in context
• Teams clients show a visual compliance-recording notice on desktop and web, mobile (iOS and Android), Teams Phones and Teams Rooms. in context
• 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. in context
• Eleveo, Redwood Technologies, Uniphore and Vox Solutions are listed as being in the process of certifying, not as certified partners. in context
• Microsoft states the compliance recording integration is designed specifically for policy-based compliance recording, and it does not support any other use of it. in context
• 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 in context
• 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. in context
• Teams compliance recording is not supported for E911 emergency calling services. in context
• Teams compliance recording is not supported for PSTN calls of users in India. in context
• Teams compliance recording is not supported for users operating in Survivable Branch Appliance mode. in context
• 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. in context

Cite this source record

APA

WarmTransfer. (2026, July 20). Microsoft Teams compliance recording (third-party). WarmTransfer. https://warmtransfer.net/knowledge/sources/ms-learn-teams-recording-compliance

BibTeX

@misc{warmtransfer-ms-learn-teams-recording-compliance,
  title  = {Microsoft Teams compliance recording (third-party)},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/ms-learn-teams-recording-compliance},
  note   = {Microsoft, accessed 2026-09-25}
}