Teams Meeting Compliance Recording: Licensing Requirements and Strategy

Financial services firms, healthcare organisations, and legal practices operating under MiFID II, HIPAA, Dodd-Frank, or FCA recording obligations face a licensing architecture that Microsoft does not make transparent. Teams compliance recording is a policy-based capability that requires a certified third-party solution — not a Teams Premium licence, not E5, and not anything Microsoft sells directly. Getting this wrong costs enterprises $200-$500 per user in misaligned licensing decisions. This guide gives you the accurate architecture and the commercial framework to build it correctly.

The Architecture: How Teams Compliance Recording Actually Works

Teams supports two categories of recording: convenience recording (user-initiated, stored in OneDrive/SharePoint) and compliance recording (policy-based, mandatory, cannot be stopped by the user). These are entirely separate technical implementations with different licensing requirements.

Compliance recording uses the Microsoft Graph Communications API — specifically the Recording Policy framework. When a compliance recording policy is applied to a user in Teams Admin Center, every qualifying communication (VoIP meeting, PSTN call, channel message, depending on scope) is captured and routed to a certified bot application operated by the recording ISV. The Microsoft platform itself does not store or manage the compliance recording — it provides the capture stream to the partner system.

This means Teams compliance recording is a two-vendor solution by design: Microsoft provides the policy framework and API; the certified partner provides the recording engine, storage, and retrieval system. Both components carry separate licensing costs.

Microsoft Licence Requirements for Compliance Recording

For a pure audio/video compliance recording deployment (MiFID II-style, voice calls and meeting recording only), an E3 licence plus Phone System add-on covers the Microsoft platform requirements. You do not need E5 for the recording capture itself. E5 (or E5 Compliance add-on) becomes relevant when you want to bring recording data into Purview eDiscovery Premium, apply Purview retention policies to the ISV-stored recordings, or use Communication Compliance for message monitoring. These are retention and discovery features, not recording features.

Certified ISV Recording Partners: Capabilities and Cost Model

Microsoft maintains a certification programme for Teams compliance recording vendors. Certified partners must implement the Graph Communications API correctly and pass annual compliance reviews. As of 2026, certified partners include NICE Engage, Verint Intelligent Recording, Dubber, ASC Technologies, Oak Innovation, Liquid Voice, and several others.

The ISV cost dominates the total compliance recording solution cost. At $15/user/month for 500 regulated users, the ISV component alone is $90,000/year — versus the Microsoft platform component (E3 at ~$36/user/month) of $216,000/year for those same users. The Microsoft licence is not the cost lever for compliance recording; the ISV selection and negotiation is.

E5 vs E3 for Compliance Recording: The Decision Framework

The E3-to-E5 upgrade costs approximately $20/user/month ($240/user/year). This is only justified for compliance recording deployments when you need capabilities that live in E5 Compliance or the Communication Compliance add-on.

The most cost-efficient architecture for organisations needing voice-and-video compliance recording only (the majority of MiFID II, FCA, and Dodd-Frank scenarios) is E3 + Phone System add-on + ISV recording partner. Moving to E5 for recording alone wastes $20/user/month. The E5 Compliance features only add value when you need message-level monitoring, advanced eDiscovery, or insider risk workflows.

Recording Policy Configuration: What IT Needs to Know

Teams compliance recording is configured through recording policies in Teams Admin Center. Policies define which users are subject to recording, what communications are in scope, and which certified bot (the ISV's recording application) receives the stream. Key configuration decisions:

Policy scope: Policies can be scoped to all users, specific groups, or individual users. Regulatory recording typically applies to a defined population — traders, advisers, patient-facing clinicians — not all employees. Scoped policies are essential for cost control; universal policies drive unnecessary ISV licence costs for non-regulated workers.

Recording mode: Teams supports Always Record (every qualifying communication is recorded), Record with Notification (user sees an indicator that recording is active, cannot stop it), and Record with Pause (user can pause but not stop). For regulatory compliance, Always Record with notification is the standard. Users cannot consent to not be recorded once a compliance policy is active.

Bot registration: The ISV deploys a bot application registered in your Azure AD tenant. This bot joins every qualifying Teams session as a silent participant. If your security posture includes conditional access policies on application registrations, you need to ensure the recording bot is not blocked. This is a common deployment failure mode.

Total Cost of Ownership: Compliance Recording at Scale

For a regulated financial services firm with 500 subject-to-recording users, the total compliance recording cost stack looks like this:

The ISV component ($102,000 of $414,000+) represents 25% of total solution cost. It is also the most negotiable element. Large ISVs like NICE and Verint have significant price flexibility when you commit to multi-year contracts, provide competitive bids, or consolidate recording from a legacy on-premises system. A well-run ISV negotiation typically achieves 15-30% off list — potentially $15,000-$30,000/year saved on the 500-user example above.

Regulatory Context: What Each Regulation Actually Requires

The specific regulatory obligation shapes the technical and licensing requirements. Over-engineering for a regulation's actual requirements is expensive; under-engineering creates regulatory risk. Here is the mapping:

MiFID II (EU): Requires recording of communications that lead to or could lead to a transaction in financial instruments. Covers phone calls, VoIP, and in-person conversations. Text-based channels (email, chat) are subject to surveillance rather than verbatim capture. Teams voice/video recording with 5-year retention covers the core obligation. E5 Compliance is not required unless you also want advanced eDiscovery on the recordings.

FCA (UK): Substantially equivalent to MiFID II post-Brexit. Same call/meeting recording scope. FCA additionally emphasises retrieval speed — recordings must be accessible within 72 hours of a regulatory request. Ensure your ISV platform supports rapid retrieval, not just cold archive storage.

Dodd-Frank (US): Applies to swap dealers and major swap participants. The recording obligation scope is narrower than MiFID II but the retention period is longer (up to 5 years for voice, longer for electronic). Contact your legal team for the exact scope applicable to your entity type.

HIPAA (US Healthcare): Recording of telehealth consultations requires a Business Associate Agreement with the recording vendor. Ensure your ISV has a signed BAA and that their storage infrastructure meets HIPAA's technical safeguards. This is a vendor due diligence issue, not a Teams licensing issue.

For the complete Teams licensing architecture including calling, rooms, and devices, see our deep-dive guide. For context on Communication Compliance licensing, see our Purview guide. Our Teams calling architecture guide covers Phone System and PSTN connectivity in detail.

Frequently Asked Questions

Does Teams Premium include compliance recording?

No. Teams Premium adds intelligent recap, meeting protection features, and advanced webinars — none of which are regulatory compliance recording. Policy-based compliance recording requires a certified third-party ISV solution integrated via the Microsoft Graph Communications API. Teams Premium and compliance recording are entirely separate capabilities with different licensing and cost structures.

What Microsoft licence is required for Teams compliance recording?

Any M365 plan that includes Teams (E1, E3, E5, F3) is sufficient for the Microsoft platform component of compliance recording. For PSTN call capture, you additionally need Phone System (included in E5, ~$8/month add-on for E3). E5 Compliance is only needed if you want Purview eDiscovery Premium, Communication Compliance, or Insider Risk Management integrated with your recording data.

Is E5 Compliance required for Teams compliance recording?

No, for audio/video capture alone. E5 Compliance (or the add-on at $12/user/month) is needed if you additionally want Purview eDiscovery Premium for legal hold on recordings, Communication Compliance for message surveillance, or Insider Risk Management. Pure audio/video compliance recording under MiFID II or Dodd-Frank does not require E5.

Which vendors provide certified Teams compliance recording?

Microsoft-certified partners include NICE Engage, Verint Intelligent Recording, Dubber, ASC Technologies, Oak Innovation, Liquid Voice, CallCabinet, and others. Each charges separately per user for their recording, storage, and retrieval platform, on top of your Microsoft licensing. ISV costs typically range from $8-$30/user/month depending on vendor, features, and volume.

Does Teams compliance recording work with PSTN calls?

Yes. Policy-based recording captures Teams PSTN calls (through Calling Plans, Operator Connect, or Direct Routing) as well as VoIP meetings. Users need a Phone System licence for PSTN calls. The certified recording bot joins the communication session and receives the media stream regardless of whether it is VoIP or PSTN.