Microsoft Teams Copilot Transcription vs Compliance Recording: Why Regulated Firms Need Policy-Based Capture

Microsoft 365 Copilot has transformed how organisations interact with Teams meetings and calls. Its real-time transcription capabilities, AI-generated summaries, and in-meeting Q&A feel like a genuine leap forward for productivity. For compliance officers in regulated industries, however, the next question is:

Can we leverage the real time transcription feed for our compliance obligations?
The short answer is no.

Copilot’s transcription is a powerful collaboration tool, but it was not designed for regulatory compliance. Microsoft does not publish a documented API for streaming Copilot’s real time speech-to-text output to external systems, Copilot cannot be guaranteed to run on every call across an organisation, and its transcript behaviour depends on a combination of admin policy and individual organiser settings. For organisations operating under MiFID II, Dodd-Frank, GDPR, HIPAA, or FCA requirements, these gaps make Copilot unsuitable for automatic compliance workflows built using the real-time transcription feed.

This article explores the technical limitations of relying on Copilot for compliance transcription, explains how dedicated solutions like Argus Archive address these gaps using Microsoft’s Teams compliance recording framework, and outlines why the two approaches serve fundamentally different purposes.

TL;DR: Copilot is built for meeting productivity. Compliance recording is built for guaranteed, policy-enforced capture. They solve different problems and can run side by side. If you need a real-time transcription feed, that’s always on and that stores transcripts according to regional or regulatory obligations, you need a dedicated compliance capture, archive and speech analytics solution.

How Copilot’s Real-Time Transcription Actually Works

To understand why Copilot’s transcription cannot serve as a compliance recording mechanism, it helps to understand how it actually works under the hood.

Copilot’s speech-to-text capability is tightly integrated into the Teams meeting experience. When a licensed user activates Copilot during a meeting or call, Teams begins processing the audio internally to generate a live transcript. This transcript powers Copilot’s AI features: in-meeting Q&A, real-time summaries, action item extraction, and post-meeting recaps. The entire pipeline is designed to enhance the experience for participants in that session, not to feed data to external systems.

Whether that transcript is saved after the meeting depends on the Copilot meeting policy configured by the administrator and, critically, on choices made by the meeting organiser. Under the current default policy, the transcript is ephemeral; it exists only while the meeting is in progress and is deleted when the session ends. If a saved transcript is generated, it is written to the organiser’s OneDrive for Business account, where it is subject to standard OneDrive retention policies and can be manually deleted by the organiser at any time.

This architecture creates several characteristics that matter for compliance. Copilot must be actively triggered by a licensed user, it does not start automatically. The meeting organiser, co-organisers, and presenters can stop transcription at any time. It does not function in meetings hosted by external organisations, in end-to-end encrypted sessions, or for users without the correct licence combination and there is no documented API for third-party applications to access the live speech-to-text stream.

For productivity, none of this is a problem. Copilot delivers exactly what it was designed to, but for regulated organisations that need guaranteed, tamper-proof capture of every communication, these characteristics represent fundamental gaps. The following sections explore each of these limitations in detail.

The Policy Change That Matters: EnabledWithTranscript: Enabled

In 2025, Microsoft announced a significant change to the default Copilot meeting policy. Communicated via the Microsoft 365 Message Center (MC1139493) and widely discussed during the late August to mid-September 2025 timeframe, the default shifted from EnabledWithTranscript (Copilot usage automatically generates and saves a transcript) to Enabled (Copilot can be used without automatically generating a saved transcript).

For tenants using the default meeting policy, this means Copilot now runs on a “non-persisted” transcript by default. Teams generates an internal transcript to let Copilot reference what has been said, but deletes all trace of it when the meeting ends. No transcript is saved to OneDrive. No artifact exists for compliance review.

If your governance depends on transcripts being created as evidence, this default change is significant. Administrators can revert to EnabledWithTranscript via PowerShell, but that still does not solve the broader compliance gaps outlined below.

Set-CsTeamsMeetingPolicy -Identity <policy name> -Copilot EnabledWithTranscript

Set-CsTeamsMeetingPolicy -Identity <policy name> -Copilot EnabledWithTranscript

There Is No Documented API to Stream Copilot’s Live Transcription

One of the most common questions from technical teams evaluating Copilot for compliance is whether a third-party application can tap into Copilot’s real-time transcription stream. Based on currently published Microsoft documentation, the answer is that no such capability is available.

Here is what is supported and documented:

• Post-meeting/post-call transcript retrieval: Microsoft Graph APIs allow applications to retrieve meeting and call transcripts after the session ends, provided a transcript exists and the application has appropriate permissions.
• Copilot APIs (Microsoft Graph namespace): These provide access to AI capabilities such as grounding data, semantic search, and enterprise knowledge retrieval. They do not provide access to Copilot’s raw speech-to-text feed.
• Meeting policy configuration: Organisers can control Copilot modes and whether transcripts are persisted, but this is a policy control, not an integration point for external applications.

Here is what is not documented as available:

• A public API to subscribe to, stream, or intercept Copilot’s live speech-to-text output in real time.
• Any supported mechanism for piping Copilot’s internal transcript data to a third-party compliance archive during a call.

Key Takeaway: Microsoft does not publish a documented API for streaming Copilot’s live speech-to-text output to external systems. Post-meeting Graph transcript retrieval exists, but it depends on a transcript having been generated and saved which is no longer the default.

Can Copilot Be Forced On for Every Teams Call and Meeting?

No. Copilot availability is governed by policy, but actual activation depends on a chain of factors that compliance teams cannot fully control:

• Meeting organiser control:
  • The meeting organiser decides whether Copilot is available and in which mode. They can set it to “During and after the meeting,” “Only during the meeting,” or “Off.” Even when an administrator enables Copilot in the tenant’s meeting policy, the organiser retains the ability to turn Copilot off on a per-meeting basis, which also disables recording and transcription for that meeting.

    

  • Certain admin policy configurations (such as “On with saved transcript required”) can lock the Copilot mode so that the organiser cannot change it to a less restrictive setting, but this does not prevent the organiser from disabling Copilot entirely.

    

• User activation required: A licensed participant must actively click the Copilot button to start it. Copilot does not run automatically simply because it is enabled in policy. If nobody activates it, Copilot will not generate any output, however, speech-to-text processing may still occur if a participant independently starts transcription, captions, or recording, which is separate from Copilot activation.
• Licensing dependency: Only users with a Microsoft 365 Copilot licence can activate or interact with Copilot. If no licensed user joins or triggers it, Copilot remains inactive regardless of the administrator’s policy settings.
• External meeting limitation: Copilot does not work in meetings hosted by external organisations. Even if a licensed user joins an externally hosted meeting, they cannot access Copilot’s features. This is a current product limitation by design.
• Teams calling (PSTN and peer-to-peer / 1:1 calls):
  • Copilot availability in Teams calls, including peer-to-peer calls and PSTN calls, is governed by a separate calling policy (CsTeamsCallingPolicy), not the meeting policy. The same governance pattern applies: Copilot must be enabled in the calling policy, the user must have the appropriate licences (including Teams Phone and a calling plan for PSTN), and a licensed user must start transcription during the call to retain any transcript or Copilot content afterwards.
  • The default calling policy sets Copilot to “Enabled,” which means Copilot can be used during a call but, unless transcription is actively started, no transcript artifact is saved after the call ends. If a call is not transcribed or recorded, there may be no reviewable artifact available for post-call compliance review even if Copilot was available during the call.

For regulated industries where every call must be captured regardless of user behaviour, this model is fundamentally insufficient. Compliance recording requires guaranteed, automatic capture with no dependency on individual users remembering to click a button, organisers choosing the right meeting option, or licensing availability.

The Compliance Recording Approach: Policy-Enforced, Guaranteed Capture

Microsoft recognised early on that its native recording and transcription features were designed for collaboration, not compliance. That is why it built a dedicated compliance recording framework into Teams, supported through a certification programme for third-party partner solutions.

How Teams Compliance Recording Works

Unlike Copilot’s transcription, compliance recording operates at the platform level using Microsoft Teams Compliance Policy Recording. When a compliance recording policy is assigned to a user or group (configured via CsTeamsComplianceRecordingPolicy in Teams PowerShell), the Teams platform automatically forces a recording application into every new call and meeting that the user participates in.

The recording application receives a separate copy of the audio, video, and screen-sharing content from the Teams media pipeline. This is not dependent on Copilot being activated, transcription being turned on, or any user clicking a button. The recording is automatic, policy-enforced, and cannot be disabled by the end user.

This is fundamentally different from “someone clicks record” or “someone turns on Copilot.”

Key Differences: Copilot Transcription vs Compliance Recording (Argus Archive)

Why a Separate Media Stream Matters for Compliance

The fundamental architectural difference between Copilot’s transcription and compliance recording is how audio data is captured. Copilot’s speech-to-text operates within the meeting experience itself, tightly coupled to the Teams UI and designed to enhance the session for participants.

Compliance recording operates differently. When a user with a compliance recording policy joins a call, the Teams platform provides a separate copy of the media streams to the compliance recording application. This captured stream is entirely independent of:

• Whether Copilot is enabled or running
• Whether native transcription or recording has been turned on
• The organiser’s meeting options or preferences
• Whether participants have Copilot licences

This separation is what gives compliance recording its regulatory credibility. The captured data has a clear chain of custody, is not subject to user interference, and flows directly into a secure archive where it can be retained, searched, supervised, and produced for regulators or legal proceedings.

How Argus Archive Addresses These Challenges

Argus Archive is a compliance recording and archiving platform purpose-built for regulated industries. It leverages Microsoft’s Teams compliance recording framework to automatically capture all Teams calls and meetings for users under policy, then enriches that data with AI-powered analytics designed specifically for compliance professionals.

Automatic, Policy-Enforced Capture

Once a compliance recording policy is applied to a user or group, Argus Archive’s recording application is automatically loaded into every new call and meeting. Users cannot disable or bypass recording. A separate media stream is captured at the platform level, completely independent of Copilot or native Teams transcription settings.

AI-Powered Transcription and Analytics

Argus Archive generates its own high-accuracy transcriptions from the captured audio, independent of Copilot’s speech-to-text output. These transcriptions feed into a suite of AI-powered analytics:

• Sentiment analysis to detect signs of risk, misconduct, or customer dissatisfaction
• Keyword and entity extraction for supervisory review and trade reconstruction
• Semantic and vector search for investigations and audit response
• A natural-language AI rule engine for real-time compliance monitoring and alerting
• AI-assisted search where supervisors can ask plain-language questions across the entire archive

Compliance Grade Storage and Access

Recordings and transcriptions are stored with encryption, digital signature, immutability controls, and comprehensive audit logging. Retention periods are fully configurable and policy-driven, supporting the specific requirements of regulatory frameworks including MiFID II, Dodd-Frank, GDPR, HIPAA, and FCA rules. Legal holds can be applied to prevent deletion during investigations, and role-based access control ensures only authorised compliance, legal, or audit personnel can review recordings.

Understanding When Each Tool Is Appropriate

Copilot and compliance recording are not competing solutions. They serve entirely different purposes within an organisation’s Microsoft Teams deployment and can run simultaneously without interference:

• Use Copilot for: enhancing meeting productivity, generating in-meeting summaries, catching up late joiners, creating action items, and powering post-meeting recaps for internal collaboration.
• Use a compliance recording solution for: guaranteed capture of all regulated communications, long-term archival, regulatory audit response, eDiscovery, supervisory review, and meeting your legal obligations under MiFID II, Dodd-Frank, GDPR, HIPAA, FCA, SEC, and other frameworks.

Many organisations will run both. Copilot provides value to every knowledge worker, while compliance recording is applied through policy to those individuals whose communications are subject to regulatory capture requirements, traders, advisers, client-facing staff, and other regulated personnel.

Frequently Asked Questions

Conclusion

Microsoft Copilot’s real-time transcription is a powerful productivity feature, but it was designed for collaboration, not compliance. With no documented API for streaming its live speech-to-text output, no mechanism to guarantee activation across all calls, and a recent default policy change that makes transcript persistence opt-in rather than automatic, Copilot cannot serve as a compliance recording mechanism for regulated organisations.

Compliance recording requires a fundamentally different approach: a separate, policy-enforced media stream captured automatically at the platform level, stored immutably, enriched with AI analytics, and governed by configurable retention policies. This is exactly what purpose-built solutions like Argus Archive provide.

If your organisation operates in financial services, healthcare, legal, or any other regulated industry and relies on Microsoft Teams for voice and video communications, the question is not whether to use Copilot or compliance recording. It is how to use both effectively: Copilot for productivity, and a dedicated compliance archive for your regulatory obligations.

On this page

↑ Back to top