Microsoft is retiring the App Builder agent and vibe[dot]powerapps[dot]com on November 30, and bringing chat-based app building together in Copilot Cowork and Copilot Studio.
Both tools were previews (App Builder never left Frontier), so a change like this is part of the deal. Creating new apps in either ends this month, and any app you want to keep can be moved with an in-product migration tool that should arrive around now (MC1505609).
Consolidating makes a lot of sense. We’ve had more ways to prompt our way to an app over the last year than most organizations could keep track of, and the new home comes with real governance built in, including personal developer environments, DLP, and an admin inventory.
It’s worth knowing what you’re moving to. App building in Cowork is a Frontier feature, app building in Copilot Studio entered public preview this month, and Copilot Managed Runtime underneath both is in preview too. As far as I can see there’s no roadmap entry or GA date yet, so this is a move from one preview to another.
The licensing is already live, however. Every person who runs an app on Managed Runtime needs Copilot Credits or a Power Apps Premium license, and the preview enforces that after 20 operations.
Yesterday I published a video on using coding agents like Claude Code and GitHub Copilot to build in Power Platform, and argued the managed path may be the better one for most business users, because you pay Microsoft for the boundary instead of building it yourself. I still think that. But there’s a nice irony in the timing. Parts of the coding-agent tooling are already generally available, while the governed path is preview from end to end. That’s fine, as long as you go in knowing it and manage your risk appropriately.
Once we understand the migration path, more information will be available on how data and capabilities actually move to the new approach.
Are there processes in your business relying on App Builder or vibe apps? How does this change impact AI-assisted app building approach?
First posted on Linkedin on 10/14/2026 → View Linkedin Post Here