Microsoft·17 Nov 2026 · 17:09 UTCDegradedHigh priority

Microsoft Copilot Create and Clipchamp video generation unavailable

Microsoft reported that users could not generate videos through the Copilot Create and Clipchamp video-creation feature. Manual video creation and editing remained available through Clipchamp Editor.

Reported durationOngoing at latest service-health update
Impact scopeProduct-level
Incident categoryEnterprise SaaS / video creation

Microsoft’s captured service-health record had not published a resolution by the latest snapshot.

WHAT HAPPENED

Incident summary

Microsoft reported that users could not generate videos through the Copilot Create and Clipchamp video-creation feature. Manual video creation and editing remained available through Clipchamp Editor.

Users attempting to generate videos in Copilot Create or Clipchamp were affected. Microsoft’s latest captured record still marked the issue as service degradation; manual editing remained a workaround.

ROOT CAUSE

What the provider reported

Microsoft’s service-health record did not publish a root cause in the captured updates. The company was evaluating the feature behavior and its documentation while investigating the issue.

Editorial note: This is a concise summary of the provider’s public explanation, not an independent technical investigation.

AFFECTED SURFACE

Services and systems

Microsoft 365 Copilot CreateClipchamp Video Hub and Editor video generation

Reported scope: Global / affected users

EVENT TIMELINE

Latest source updates

Showing up to the 3 latest updates available in the source record. UTC is fixed; local time is converted in this browser (your local timezone).

  1. Feature unavailability confirmed

    Microsoft confirmed that Copilot Create and Clipchamp video generation were unavailable, while manual editing remained possible in Clipchamp.

  2. Investigation continues

    Microsoft said it was continuing to evaluate how to restore the video-generation feature and update its documentation.

  3. Degradation remains open

    The service-health record was updated and continued to list the incident as service degradation, with the next update expected later on Nov 18 UTC.

Latest source record: ·

COMMUNITY SIGNAL

What did this incident feel like?

React anonymously. Counts are shared across visitors and are not a measure of the number of customers affected.

Community signal
Shared anonymous reactions