MC1325419: Microsoft Clipchamp: Licensing SKU and service plan naming update
Microsoft Clipchamp licensing SKU and service plan names will be updated in mid-June 2026 for clarity and consistency with Microsoft 365 standards. No changes to features or user experience. Updates apply automatically; no action required, but review internal references after June 10, 2026.
[What and Why]
We are updating the licensing SKU and service plan names for Microsoft Clipchamp to improve clarity and consistency across purchasing, billing, and subscription management experiences. This update aligns Clipchamp naming with Microsoft 365 standards, helping administrators and procurement teams more easily identify and manage licenses. There are no changes to Clipchamp functionality, features, or user experience.
[Rollout Schedule]
General Availability (Worldwide): Rollout will begin in mid-June 2026 and is expected to complete in mid-June 2026.
[Impact on Your Organization]
Who is affected
- Administrators and procurement teams managing Microsoft 365 licensing
Platforms/Services
- Microsoft 365 admin center
- Microsoft commerce and billing systems
- Reporting, exports, and APIs that surface license and service plan names
What will happen
- Clipchamp license (SKU) names and associated service plan names will be updated across:
- Microsoft 365 admin center
- Billing and purchase experiences
- Reporting and license exports

- Existing Clipchamp subscriptions will automatically reflect the new names.
- There are no changes to:
- Clipchamp features or capabilities
- User workflows or access
- Service availability
- The change is applied automatically and enabled by default.
[Action Required / Recommendations]
No action is required.
We recommend that you:
- Review and update any internal documentation, scripts, or processes that reference Clipchamp SKU or service plan names after June 10, 2026.
- Notify helpdesk, licensing, and procurement teams about the updated naming to avoid confusion when reviewing licenses and service plans.
[Compliance considerations]
No compliance considerations identified. Review as appropriate for your organization.