Copilot Clipchamp Video Hub: Conversational Video Creation Preview Planned for December 2026

The submitted roadmap listing marks the feature in development, with a December 2026 preview and January 2027 general availability estimated for worldwide standard multi-tenant environments. Those are planning windows, not launch commitments: Microsoft says its AI at Work roadmap descriptions and release estimates can change. The currently rendered roadmap page does not expose the text of item 570963, so its feature details and dates come from the submitted listing rather than an independently visible entry on that page.

What changes—and what already works​

Copilot can already help eligible work users make Clipchamp videos. Microsoft Support documents a Create-hub workflow that turns a prompt into a script, AI voice narration and a project assembled with stock footage. Users can preview the draft inline, prompt for another version, or open it in Clipchamp for further editing. The Clipchamp editor also has a Generate a Video option. So neither prompt-based creation nor inline preview, by itself, is new.

The proposed shift is the Video Hub workflow: the listing describes generating, editing and refining through chat, with either explicitly supplied documents or implicit Work IQ knowledge providing context. Microsoft describes Work IQ more broadly as an intelligence layer drawing on work signals such as files, messages and meetings. That explains the idea behind contextual grounding, but it does not tell us which sources this particular video feature will use or how a user will inspect that context. Nor does “agentic” establish what Copilot can do without approval.

There is a useful distinction for teams planning content. Microsoft’s Clipchamp-specific support guidance says the existing document-to-video flow supports PowerPoint decks, not other document types. The roadmap’s reference to “documents” could indicate a broader future experience, but it does not name supported formats. A training team could reasonably prepare a reviewed source deck today; it should not yet design a workflow that depends on Copilot accepting, say, a Word policy document in Video Hub.

What IT teams should watch​

For the existing Create-hub feature, Microsoft says Clipchamp must be enabled by the organization and describes access for commercial users with an Entra ID account, a Microsoft 365 plan and Copilot Chat access. Those are documented rules for today’s workflow—not a confirmed licensing or enrollment checklist for roadmap item 570963. The listing gives no specific license, preview-enrollment steps, tenant controls or browser requirements for the planned experience.

Storage and information protection deserve equal attention. Microsoft Learn says Clipchamp video files and editing projects are generally stored in OneDrive or SharePoint; Microsoft Support says videos generated by the existing video creator are saved in the user’s corporate OneDrive. Neither statement establishes where this future Video Hub experience will put its drafts, generated assets or final videos. Microsoft also notes that the current PowerPoint conversion flow rejects files with protected sensitivity labels. Administrators should verify the new feature’s storage, permissions and labeling behavior when Microsoft documents it, rather than assuming today’s rules carry over.

The practical promise is clear: fewer trips between prompting, watching a draft and requesting revisions. The practical test is still ahead. Until Microsoft specifies the editing controls and Work IQ boundaries—and the preview arrives—treat Video Hub as a planned extension to Clipchamp, not an available replacement for the workflows teams use now.