Microsoft Retires Copilot App Builder and Vibe Power Apps: November 2026 Migration Deadline

Message Center advisory MC1505609 describes the change. Microsoft is retiring the App Builder agent and vibe.powerapps.com by November 30, 2026, consolidating app creation into Copilot Cowork and Microsoft Copilot Studio. New app creation in retired platforms ends mid-October 2026. Neowin reported the change. The notice itself appears in public Message Center archives, which list it as published Oct 12, 2026 and tagged as a user-impact, admin-impact retirement with an act-by date of November 30.

If your organization built apps with either tool, you have about seven weeks, and you'll have to do most of the work yourself.

What is being retired, and what isn't​

The scope is narrower than the headline suggests, which helps if you're worried:

• App Builder agent: an agent inside Microsoft 365 Copilot that builds apps from a chat conversation.
• vibe.powerapps.com: the "vibe coding" app-authoring site that Microsoft launched at Ignite in November 2025.
• Not affected: Power Apps as a whole. Canvas apps, model-driven apps and the rest of the Power Platform are not named in the notice.

Don't mix up App Builder with the separately documented "agent builder" feature in canvas apps. Microsoft Learn describes agent builder as a tool that creates Copilot agents from an existing canvas app's metadata, and MC1505609 doesn't mention it.

Microsoft's stated reason is about consistency. The advisory says Copilot Cowork and Microsoft Copilot Studio will become the primary experiences for creating apps using natural language. This retirement helps consolidate app creation experiences and provides makers with a consistent path forward for building and managing apps. Neowin argued that keeping AI app builders outside the Copilot brand would have confused customers. That's a fair reading, but it's Neowin's analysis, not something the advisory says.

Section summary: Two specific AI app-building tools are being shut down, not Power Apps. Microsoft says it's consolidating everything under Copilot Cowork and Copilot Studio.

The timeline​

The archived notice gives this schedule, and states that creation of new apps in App Builder agent and vibe.powerapps.com is no longer supported from the mid-October milestone. As of today, October 13, that cutoff is either about to arrive or has already reached your tenant. Neowin says new app creation has already stopped and that the migration tool should arrive within days.

One wording difference matters. Neowin says unmigrated apps become "permanently inaccessible." The advisory says they will no longer be accessible through these retired experiences, according to the archived text in the source packet. The notice doesn't say what happens to the underlying data stores, so don't assume they get deleted, and don't assume they're safe either. Either way, the practical result for users is the same: after November 30, the app is gone.

Why "not automated" is the most important detail​

Both Neowin and the advisory say migration is not automated. Microsoft will provide an in-product migration experience, and the notice says existing App Builder and Vibe apps can be opened to begin the migration process once in-product migration becomes available. But makers and admins have to start each migration and see it through.

The two tools were built very differently, which suggests migrations won't feel the same for each:

• App Builder apps sit on SharePoint. Consultancy Forward Forever reviewed the Power Platform vibe tools earlier this year and found that App Builder is essentially an agent running in M365 Copilot. Its use requires an M365 Copilot license. It is the only tool that uses SharePoint lists as a data repository. They also observed that when building an app, App Builder always creates a new SharePoint site and the lists needed by the app.
• Vibe apps sit on Dataverse. Forward Forever's earlier hands-on piece found that Vibe Power Apps are always created in an environment, and that everything, including apps, plans and generated tables, can be found in the default solution for that environment (Common Data Services Default Solution). Power Platform MVP April Dunnam put it this way: Code Apps are the new app type. vibe.powerapps.com is one way to create them without needing to start in a code IDE.

This is my analysis, not Microsoft guidance. Before migrating, find out which SharePoint sites or Dataverse environments each app depends on. That way you can check afterward that the migrated app still connects to the same data. Microsoft hasn't published a compatibility matrix, so nobody can say yet whether every app will move over unchanged.

Section summary: Each app has to be migrated by hand. App Builder apps depend on SharePoint lists and Vibe apps depend on Dataverse, so you should know where each app's data lives before you start.

Where apps go next: Copilot Cowork and Copilot Studio​

Microsoft announced the replacements on September 10. In Cowork, makers use an /app skill through the Frontier early-access program. In Copilot Studio, they choose App (Preview) from the home screen. Microsoft's blog post describes the process: you state the business outcome, the users, the data and the actions you need, and agentic coding produces an app scaffold. You can then refine it in conversation, preview it and look at the underlying code.

Microsoft is emphasizing governance this time:

• Apps run on Copilot Managed Runtime, which is in public preview. Microsoft's October 7 Copilot Studio update says it handles hosting, identity, governed data access, lifecycle management, Git-backed versioning and centralized visibility across Copilot Studio, Cowork and Copilot Code.
• Microsoft Entra identity, organizational data policies and connector policies apply by default.
• Admins can see published apps in the Microsoft 365 admin center under Apps > All apps, according to Microsoft Learn's preview documentation.
• Users open apps they have access to from a single portal, managedapps.cloud.microsoft.
• Microsoft says app building and running follow a usage-based billing model.

The billing change deserves some attention. App Builder required a Microsoft 365 Copilot license. The new tools are metered. Microsoft hasn't published a cost comparison in the material reviewed here, so finance teams should get one before November.

There's also a maturity issue. Microsoft Learn labels the Managed Runtime documentation as prerelease and subject to change, and the Cowork path requires Frontier enrollment. So the instruction is to leave a preview tool for another preview tool. That may not suit organizations that only adopt generally available services.

What admins and makers should do now​

The advisory includes its own checklist. In short:

1. Find the makers. Identify everyone who has used App Builder or vibe.powerapps.com.
2. Tell them the dates. New creation ends mid-October, and retirement is November 30.
3. Redirect new projects to Copilot Cowork or Copilot Studio.
4. Decide what to keep. Not every experimental app is worth migrating, so triage.
5. Migrate when the in-product tool appears, and finish before November 30.

Based on how the tools work, I'd add a few steps of my own:

• Record each app's data source: the SharePoint site for App Builder apps, or the Dataverse environment for Vibe apps.
• Check Frontier enrollment if you plan to use Cowork, and confirm Copilot Studio preview access in the environments you need.
• After migrating, test with real users in the managedapps portal and confirm the app appears in the admin center inventory.
• Agree internally on a buffer deadline, such as mid-November, so migration problems don't run into the final date.

Section summary: Inventory your apps, triage them, record where their data lives, migrate when the tool arrives, and set an internal deadline well before November 30.

Analysis: Microsoft keeps changing its app-building tools​

At Ignite 2025, Microsoft's Power Platform blog promoted vibe.powerapps.com as developers can build apps using Microsoft tools like App Builder and Power Apps and deploy them on one managed platform. Less than a year later, both tools are being retired and the governance story has moved from the Power Platform admin center to the Microsoft 365 admin center.

There is a case for Microsoft. It had at least three overlapping natural-language app builders: App Builder, Vibe, and generative pages. Forward Forever's review noted that Vibe looks suspiciously like Plan Designer. As if it had been separated from Plan Designer into its own entity. Cutting that overlap down to two connected entry points on one runtime is reasonable, and the Managed Runtime model with Entra identity, Git versioning and admin inventory is stronger on paper.

There is also a case against. Organizations that adopted early are the ones doing the cleanup. They get about seven weeks, migration isn't automated, and the replacement is still in preview with a different billing model. If you're a maker who built a useful onboarding tracker in App Builder last spring, what you'll take from this is probably not "consistent path forward." More likely it's "don't build anything important on a preview."

That lesson applies beyond this retirement, and it's the one to keep in mind with the new Copilot app tools as well.