|
[What and why]
We’re updating the SharePoint Online PowerShell setting EnableSensitivityLabelForVideoFiles so it applies to both MP4 video files and Microsoft Clipchamp project files (.clipchamp).
Today, this setting controls sensitivity label support for MP4 files only. After this change, the setting will also control sensitivity label behavior for .clipchamp files. This update creates a more consistent experience across supported video file types and simplifies administration of sensitivity label behavior for video content.
[Rollout schedule]
- General Availability (Worldwide): Beginning in mid-September 2026 and expected to complete in mid-October 2026
[Impact on your organization]
Who is affected
- SharePoint Online and OneDrive administrators who manage sensitivity labels for video files
- Organizations that use Microsoft Clipchamp and sensitivity labels
Platforms and services
- Microsoft Clipchamp
- SharePoint Online
- OneDrive
What will happen
The SharePoint Online PowerShell setting:
Set-SPOTenant -EnableSensitivityLabelForVideoFiles
will continue to control MP4 files and will also begin controlling sensitivity label behavior for .clipchamp files.
If EnableSensitivityLabelForVideoFiles is set to $true:
- The Clipchamp editor will apply the organization’s default sensitivity label policy to projects.
- Users will be able to update project labels, subject to the organization’s existing sensitivity label policies.
- The Clipchamp editor will enforce the applicable label policies.
- Exported MP4 videos will inherit the sensitivity label applied to the Clipchamp project.
If EnableSensitivityLabelForVideoFiles is set to $false and a .clipchamp project does not already have a sensitivity label:
- The organization’s default sensitivity label policy will not be applied to the project.
- Users will not be able to assign or update a sensitivity label on the project.
- The sensitivity label picker will not be displayed in the Clipchamp editor.
- Exported MP4 videos will not inherit a sensitivity label from the project.
If EnableSensitivityLabelForVideoFiles is set to $false and a .clipchamp project already has a sensitivity label:
- The existing project label will remain applied and its policies will continue to be enforced.
- Users will not be able to update the project label.
- Exported MP4 videos will not inherit the project’s sensitivity label.
- The Clipchamp editor will warn users that the exported video will not inherit the project label.
Organizations currently using EnableSensitivityLabelForVideoFiles = $true should not experience a change in behavior because sensitivity labels will continue to be supported for both MP4 and .clipchamp files when this setting is enabled.
Organizations currently using EnableSensitivityLabelForVideoFiles = $false will see a change. Unlabeled .clipchamp projects will remain unlabeled and will not support sensitivity label assignment in the Clipchamp editor. Projects that already have a label will retain it and continue to enforce its policies, but users will not be able to update the label, and exported videos will not inherit it.
[Action required and recommendations]
Review your current EnableSensitivityLabelForVideoFiles configuration before rollout completes.
If your organization wants sensitivity labels applied to video content, including Clipchamp project files and exported MP4 videos, ensure that EnableSensitivityLabelForVideoFiles is set to $true.
If your organization keeps the setting set to $false, review workflows involving existing labeled Clipchamp projects. Their labels and associated policies will remain in effect, but users will not be able to update those labels, and newly exported videos will not inherit them.
Administrators can review the current setting in the Video support (MP4 files) section of the Microsoft Learn article. Documentation will be updated to include the new .clipchamp behavior.
Be aware that video files with sensitivity labels will follow your existing sensitivity labeling policies. Depending on your label configuration, protected video files may be subject to restrictions such as limited sharing or download capabilities.
Learn more
[Compliance considerations]
| Question |
Answer |
| Does the change modify Information Protection labels or sensitive information types? |
Yes. The scope of the existing admin control is expanding to include .clipchamp files in addition to MP4 files. Existing labels on .clipchamp projects will remain applied when the setting is disabled, but users will not be able to update them and exported videos will not inherit them.
|
| Does the change alter how admins can monitor, report on, or demonstrate compliance activities? |
Yes, indirectly. Sensitivity label behavior for .clipchamp files will align with the existing tenant setting. When the setting is disabled, existing labeled projects will continue to enforce their label policies, while unlabeled projects and newly exported videos will remain unlabeled. This may affect compliance workflows and reporting related to labeled content.
|
|