
Consultant at Bright Ideas Agency | Digital Transformation | Microsoft 365 | Modern Workplace
In a recent YouTube video, Nick DeCourcy of Bright Ideas Agency demonstrates a striking new capability from Microsoft: Build PowerPoint Interactive Slides with Copilot. The video walks viewers through how Copilot can generate fully clickable, dynamic slides from prompts and source data, and it frames the feature as both exciting and disruptive for PowerPoint workflows. Consequently, this summary explains what the video shows, how the feature works, and the practical tradeoffs that teams should weigh before deploying it broadly.
DeCourcy frames the release as part of the Microsoft Copilot Frontier preview and notes that the feature arrived in late August 2026 under a message center notice. He demonstrates that, after invoking the Create interactive slides skill in the Copilot pane, users can ask Copilot to generate a slide with controls such as filters, totals, and visual swaps. The resulting slide looks and behaves like an app inside PowerPoint, and the video highlights the speed and polish of the generated interactions.
According to the demo, you start by opening the Copilot pane in PowerPoint and selecting the interactive-slides skill or using the mention trigger to call @create-interactive-slides. Then you provide source material — for example an Excel table or an existing slide — and describe the interaction you want, after which Copilot takes a couple of minutes to produce a clickable slide. DeCourcy tests filters and dynamic totals to show how visuals change on user input, illustrating the shift from static slides to an embedded interactive experience.
Technically, the video explains that the interactivity is embedded as HTML inside a PPTX, which is central to both its power and its problems. The interactive object is not a set of native editable PowerPoint elements; instead, it behaves like a self-contained web component that Copilot controls. As a result, direct editing of individual elements is not possible in the usual way — every change must be routed back through Copilot.
DeCourcy highlights clear benefits: teams can create engaging, audience-driven presentations without building a separate app or dashboard, and they can reuse familiar source files from Microsoft 365. This can greatly speed up the creation process and let presenters pivot during a meeting by applying filters, swapping visuals, or showing calculated totals on demand. Moreover, the fact that the interactive content lives inside a single PowerPoint deck simplifies distribution compared with linking to external services.
These advantages make the feature well suited to sales demos, executive briefings, and classroom settings where interactivity helps tell the story. For small teams or busy presenters, the ability to generate a polished interactive slide in minutes is particularly appealing. Nevertheless, the video suggests that speed and visual flair come with practical costs that organizations should evaluate.
DeCourcy stresses several important limitations that create tradeoffs between interactivity and compatibility. First, because the interactive content is HTML-based, it renders as a flat image in PowerPoint Live during Teams presentations, so the interactive controls are lost in that common meeting mode. Second, when you export or print the deck to PDF, the interactivity disappears and viewers only get a static snapshot.
Another challenge is Copilot’s own ability to read the content back. The video shows that asking Copilot in PowerPoint to summarize the generated interactive slide returns nothing useful via standard summarization workflows, and Copilot Chat only receives a thumbnail that it mostly cannot parse as text. However, if you explicitly invoke the interactive-slide builder skill, Copilot can reproduce or reference the content, which means some automation paths still work but others degrade.
The HTML embedding also raises governance issues because these slides can pull from tenant files, meetings, and chats. DeCourcy points out that sensitivity labels are inherited by Copilot-generated content and that the connections are point-in-time rather than live, meaning the deck can contain snapshots of tenant data that Copilot may not be able to inspect easily. Put simply, interactivity increases the attack surface for compliance and auditing while reducing the transparency of what Copilot can read back.
Given those risks, the video’s clear recommendation is to treat this as a Frontier preview and not to deploy it in high-risk scenarios without documented controls. DeCourcy argues that organizations should demand clearer documentation from Microsoft about data handling, sensitivity label behavior, and Copilot’s read-back limitations before rolling this into production workloads. In the meantime, testers should try the skill to understand its behavior but avoid using it with confidential or regulated information.
Finally, teams must balance the benefit of rapid interactivity against the loss of native editability and degraded export or live-presentation paths. DeCourcy’s demonstration shows real promise for more engaging slides, yet it also underscores a familiar tradeoff: new capabilities can improve storytelling, but they can also create compatibility, governance, and workflow challenges that require careful planning. Overall, his video offers a practical, cautious view that will help decision-makers weigh the value and risks of adopting this evolving Copilot skill.
PowerPoint interactive slides, Microsoft Copilot PowerPoint, create interactive PowerPoint, Copilot for PowerPoint, PowerPoint AI features, interactive presentation design, PowerPoint automation Copilot, add interactivity PowerPoint