Sensitivity Label Inheritance for Teams Meeting Artifacts

Jul 1 2026

Inherited protection for recordings, transcripts, and notes

Teams meeting artifacts, including recordings, transcripts, and Loop notes, can now be configured to automatically inherit the sensitivity label from the original meeting. This ensures content generated during meetings is consistently protected without requiring manual labeling, reducing risk and simplifying protection at scale.

Please note that the exact configuration options are not yet available for preview as of the date of posting.

What’s Changing and When

This is a new feature and is not currently in preview.

Microsoft 365 Roadmap ID: 558686
Preview: May 2026
Expected GA: June 2026

As of mid-July 2026, there is no corresponding Message Center message indicating that this feature is queued for preview or general availability release.

Why This Matters

Today, when a Teams meeting is marked as confidential or sensitive, the organizer has to manually apply protection to the meeting-related artifacts, like transcripts, recordings, and Loop notes, after the meeting ends. With this new feature enabled, those items will automatically inherit the meeting’s sensitivity label, ensuring consistent protection without tedious manual intervention.

This feature extends the capabilities currently available for Teams meeting sensitivity labels via Teams Premium, an add-on license that provides advanced security, end-user, and administrative features for Teams meetings. Teams Premium licensing.

Meeting sensitivity labels allow organizations to classify and protect calendar items, Teams meetings, and related chats. Meeting organizers can apply a label that then enforces configured protections such as encryption, usage restrictions (for example, limiting forwarding), lobby and recording controls, and visual markings.

Key Risks Organizations Should Consider

Governance and Policy Alignment

If existing policies (e.g., on recordings, meeting notes, and classification) do not clearly address automatic inheritance of sensitivity labels and their implications (or the recording of meetings in general), the gap between written policy and actual practice can create regulatory compliance exposure.

Potential Discovery Impacts

Applying certain sensitivity labels may cause content to be watermarked or encrypted, and these protections may need to be identified and addressed before the content can be processed in eDiscovery workflows.

If the meeting’s sensitivity label does not accurately reflect the content of the artifact (e.g., generic meetings labeled as highly restricted or vice versa), organizations may face inconsistent protection, overrestriction of access, or underprotection of sensitive content, all of which can create operational and compliance challenges.

How eMerge Can Help

For companies not currently using Purview for data labeling, eMerge can help you assess whether broad deployment of such labels, including for meetings and meeting artifacts, is appropriate. If your organization is currently using sensitivity labels, eMerge can evaluate how automatic labeling of recordings, transcripts, and notes would impact your retention, eDiscovery, and information governance obligations and design configuration options that balance protection with business usability. We can also help develop or update policies, user guidance, and change management plans so that any rollout of sensitivity labels for meeting artifacts is both operationally practical and legally defensible.

Bottom Line

When implemented in a sound, defensible manner, this feature extends the information protection capabilities of sensitivity labels to meeting artifacts, which is broadly beneficial. However, it requires strong alignment with enterprise policies, effective end‑user training, and a well-designed governance program.

Want to talk through whether and how this new capability should be enabled in your environment?
Please contact eMerge Information Governance.