Microsoft Teams Added Transcription. Your NDA Still Applies.

In April 2026, Microsoft began rolling out a "transcribe only" option for Teams meetings. Meeting organizers can now start transcription without creating a video recording. IT admins got new controls to customize consent notification language — up to 200 characters, with a custom privacy link. On paper, this looked like progress for professionals worried about recording sensitivity.

It wasn't progress for the ones who needed it most.

Around the same time, a class action was filed in Illinois alleging that Teams had been collecting voiceprints from meeting participants — without their knowledge and without valid consent under the Illinois Biometric Information Privacy Act. The complaint covers residents going back to March 2021. The question at the center of that case is straightforward: does a participant's voice, as processed by a meeting platform, become a biometric identifier that the platform can retain? The plaintiffs say yes.

The new transcription feature and that lawsuit exist in the same moment because they reflect the same underlying reality. The architecture is cloud-first. Everything in the meeting — every word, every voice — passes through Microsoft's infrastructure.

What "transcription only" actually means

When Teams transcribes a meeting, the audio is processed on Microsoft's servers. The transcript is saved to OneDrive for private meetings, or SharePoint for channel meetings. IT admins in your organization have access. Anyone invited to the meeting has view permissions by default. The data is retained under Microsoft 365 policies, which vary by tenant configuration.

None of that changed in 2026. What changed is that no video file is created alongside the transcript, and your IT admin can now customize the consent notification message. That's the scope of the update.

The risk lives in the contract, not the settings panel

Risk Management (Chapter 11 of the PMBOK Guide) requires that third-party dependencies — vendors, platforms, subcontractors — be evaluated as part of risk identification. The question isn't whether Microsoft 365 is a reputable vendor. The question is whether your client's NDA permits your meeting conversation to be processed by any third party, regardless of that party's reputation.

Most NDAs don't carve out exceptions for meeting platforms. They restrict disclosure of confidential information to third parties. When audio from a client meeting is transmitted to a cloud provider for processing, that transmission is a disclosure. Whether it constitutes a breach depends on the specific language of the agreement — but the risk exists the moment the audio leaves the device.

What I've seen in practice

One of my clients prohibited recording from day one — it was in the contract before the project kicked off. Through dozens of meetings covering scope decisions, change orders, and client commitments, we depended entirely on whoever had the fastest hands to take notes. My firm's IT policy made it worse: no AI tools permitted, period. Teams had both transcription and recording disabled at the tenant level.

There was nothing that could keep pace with a real conversation. No tool existed that could capture speech as fast as people talk — so I built one for my own use.

What changes when the audio never leaves the device

The only clean solution to third-party data exposure is to eliminate the third party. For meeting transcription, that means processing audio locally — on the device of the person running the meeting — and never transmitting it.

No audio is ever saved — not on a server, not on your machine. Speech converts to text in memory and is gone the moment it's transcribed. Only the text stays. There's no admin with access. No platform terms to audit. No biometric data traveling through someone else's infrastructure. The NDA isn't implicated because nothing left the room.

For professionals operating under formal confidentiality agreements, this isn't a preference — it's a compliance requirement. The meeting platform you choose is a risk management decision.

BarnOwl is built on this architecture — on-device transcription, no audio saved anywhere, no cloud dependency.

For a full breakdown of how local-first transcription works — and who it's built for — read Meeting Transcription Without a Bot.

Frequently asked questions

The settings panel won't save you from a clause in a contract. The architecture will.