MC1279068 - Microsoft Purview | Information Protection: Sensitivity label inheritance for Teams meeting artifacts
Service
Published
Tag
Platforms
Summary
Microsoft Purview Information Protection will support sensitivity label inheritance for Teams meeting artifacts, such as transcripts, recordings, and Loop notes. Admins must enable this feature and configure policies. Rollout begins May 2026 (preview) and June 2026 (general availability), enhancing consistent protection of meeting content.
More information
Introduction
Microsoft Purview Information Protection is introducing support for sensitivity label inheritance for Microsoft Teams meeting artifacts. With this update, meeting transcripts, recordings, and Loop meeting notes will be able to automatically inherit the sensitivity label applied to the meeting. This capability will help reduce manual labeling and will support more consistent protection of meeting content.
This message is associated with Microsoft 365 Roadmap ID 558686.
When this will happen
- Public preview: We will begin rolling out in early May 2026 and expect to complete by mid‑May 2026.
- General availability (Worldwide): We will begin rolling out in early‑June 2026 and expect to complete by mid-June 2026.
How this affects your organization
Who is affected
- Admins who manage Microsoft Purview Information Protection label policies
- Users who organize Microsoft Teams meetings where sensitivity labels are published
What will happen
- Admins will be able to configure sensitivity label inheritance for Teams meeting artifacts in the Microsoft Purview portal:
- When enabled, meeting transcripts, recordings, and Loop meeting notes will inherit the sensitivity label applied to the meeting.
- Users will see the inherited sensitivity label applied to these artifacts.
- Users may be able to manually override the inherited label, depending on label permissions.
- Existing policies will not be affected, but existing policies can be updated to inherit the sensitivity labels.
- This feature will not be enabled by default and will require admin configuration.
Prerequisites for label inheritance
- The sensitivity label will need to include both the Meetings and Files scopes.
- The sensitivity label will need to be published to the meeting organizer.
- The tenant policy setting Apply inheritance between Teams meetings and artifacts will need to be enabled and published to the organizer.
What you can do to prepare
No action is required if you do not plan to enable sensitivity label inheritance.
If you plan to use this capability:
- Review existing sensitivity labels and confirm the Meetings and Files scopes are included.
- Ensure the label is published to relevant meeting organizers.
- Enable the Apply inheritance between Teams meetings and artifacts setting in the Microsoft Purview portal.
- Update internal documentation if your organization manages meeting content workflows.
Compliance considerations
| Question | Answer |
| Does the change alter how existing customer data is processed, stored, or accessed (e.g., documents, emails, chats)? | Yes. When enabled by an admin, sensitivity labels applied to Teams meetings will be inherited by related artifacts (meeting transcripts, recordings, and Loop meeting notes), which will change how existing meeting content is labeled and protected. |
| Does the change modify, interrupt, or disable any Microsoft Purview capabilities (such as Information Protection labels, DLP, eDiscovery, or retention)? | Yes. This update will modify how Information Protection sensitivity labels are applied by enabling inheritance from Teams meetings to associated artifacts when configured by admins. |
| Does the change include an admin control? | Yes. Admins will need to enable the Apply inheritance between Teams meetings and artifacts tenant policy in the Microsoft Purview portal. The feature will not be enabled by default. |