App Builder and vibe.powerapps.com Retirement: Your Plan Before November 30

TL;DR: Microsoft is retiring the App Builder agent in Microsoft 365 Copilot and the Power Apps vibe experience at vibe.powerapps.com on November 30, 2026 (Message Center post MC1505609). Creating new apps in either tool has already stopped. Existing apps keep working until the retirement date, but apps that are not migrated by November 30 will no longer be accessible through those experiences, and the migration is not automatic. The new home for natural-language apps is Copilot Cowork and Microsoft Copilot Studio, running on Copilot Managed Runtime with Copilot Credit billing. Use the next six weeks to find every app, confirm where its data lives, keep only the apps that earn their place and move them into a governed, measured home.

On October 12, 2026, Microsoft notified Microsoft 365 administrators in Message Center post MC1505609 that the App Builder agent and vibe.powerapps.com are being retired. The hard date is November 30, 2026. That leaves roughly six weeks, and the U.S. Thanksgiving week and end-of-quarter work both land inside that window.

For many small and mid-market organizations, App Builder was the first place a business user turned a Copilot chat into a working app. A project tracker. A volunteer sign-up form. A site inspection checklist. Those apps were fast to build, which also means many of them were never registered, reviewed or assigned a backup owner. This retirement is a forced inventory, and a useful one.

If you need a refresher on where App Builder sat next to Power Apps and code apps, our earlier guide, Microsoft 365 App Builder vs. Power Apps vs. Code Apps: Which Should You Choose?, explains the trade-offs.

What is changing with App Builder and vibe.powerapps.com?

Microsoft is consolidating natural-language app creation into two experiences: apps in Copilot Cowork and apps in Microsoft Copilot Studio. Here are the key dates from MC1505609 and the related announcements, and what each one means for you.

What is not changing: this retirement covers two specific AI app-building tools, not Power Apps. Canvas apps, model-driven apps, Power Pages and the rest of Power Platform are not part of MC1505609. Microsoft's app-building announcement for Cowork and Copilot Studio also states that it does not affect other resources created in Power Platform or Copilot Studio.

Where do App Builder and vibe apps go next?

The replacement path is Copilot Cowork or Copilot Studio. In Cowork, users describe an app in a chat using the app skill, which is available through the Frontier program. In Copilot Studio, makers choose App (Preview) from the home page and describe the users, data and actions they need. Apps built in Cowork can be opened and further edited in Copilot Studio, and the Copilot Studio experience is enabled by default for eligible makers.

Both experiences publish to Copilot Managed Runtime, which entered public preview in late September 2026. That runtime is the real change for IT leaders:

• Governance in one place. Published apps appear in the Microsoft 365 admin center under Apps > All apps, with Microsoft Entra identity, organizational data policies and connector policies applied.
• Versioned code. Each app lives in a Git repository, so a developer can pick up an app a business user started and release a new version while the current one stays live.
• Metered cost. Building and running these apps consumes Copilot Credits. App Builder rode on the Microsoft 365 Copilot license. Its replacement is billed by usage.

For a deeper look at how apps, workflows and agents now fit together in Copilot Studio, read Copilot Studio Apps, Workflows and Agents: IT Leader's Guide. If your team is still sorting out when to use Cowork at all, Microsoft Copilot Chat vs Cowork vs Code vs Autopilot maps each experience to the work it suits.

Why does the App Builder retirement matter for IT leaders?

The deadline is short, but the bigger issue is what it reveals about how these apps were created.

• Hidden data stores. App Builder stored new data in Microsoft Lists on SharePoint, often in a site the app created for itself. Vibe apps created Dataverse tables inside a Power Platform environment. Before you migrate, you need to know which site or environment each app depends on, and who has access to it.
• Ownership gaps. These apps were built in minutes by individual employees. If the maker has moved roles or left, an app may still be running a business process with nobody accountable for it.
• A new cost model. Moving from license-included creation to Copilot Credits means every migrated app now has a running cost. That is healthy, because it forces a value conversation, but it needs a budget owner.
• Preview to preview. Apps in Copilot Studio and Copilot Managed Runtime are both in preview, and Cowork apps require Frontier enrollment. Organizations that only run generally available services need a policy decision, not just a migration.

This is the same pattern we described in Agent Sprawl Is the New Shadow IT. When building gets easy, inventory and ownership have to be designed in, or they never happen.

Some sectors have specific considerations:

• Nonprofits often had program staff build trackers for volunteers, events or grant deliverables in App Builder. Those lists may hold personal information about volunteers and clients. Confirm who can see each SharePoint site before you keep or move the app, and budget the Copilot Credits the replacement will use against donor-funded priorities.
• Education institutions should note that November 30 lands just before exams and the winter break. Finish migration of any app used for admissions, student services or course operations by mid-November, while the staff who built them are still available.
• Government organizations should confirm which of the new experiences is available in their cloud and whether preview services are allowed under their policies. If the answer is no, plan to rebuild essential apps as canvas or model-driven Power Apps rather than moving to a preview runtime.

What should IT leaders do before November 30, 2026?

1. Confirm the notice in your tenant. Open MC1505609 in the Message Center, note any tenant-specific timing and share it with the owners of Microsoft 365 and Power Platform administration.
2. Find every app and every maker. List the people who used App Builder in Copilot and anyone with access to vibe.powerapps.com. Note that the vibe experience was available only in some regions and never in default environments, so many tenants will find their exposure is App Builder only.
3. Record where each app's data lives. For App Builder apps, capture the SharePoint site and lists. For vibe apps, capture the environment and Dataverse tables. Export any data you cannot afford to lose before November 30, because Microsoft has not committed to what happens to it.
4. Decide to migrate, rebuild or retire. Migrate apps that are used weekly and have a named owner. Rebuild as a canvas or model-driven Power App when the app needs relational data, row-level security or must avoid preview services. Retire the rest, and tell their users what replaces them.
5. Set up the destination before you move. Decide whether Cowork through Frontier, Copilot Studio or both are allowed. Configure Copilot Credit billing and spending limits in Copilot cost management, and agree who approves apps that connect to business systems.
6. Migrate early and test with real users. Use the in-product migration as soon as it reaches your tenant. Have each owner test the migrated app with real users, confirm it still connects to the right data and check it appears in Apps > All apps in the admin center.
7. Set an internal deadline of November 16. A two-week buffer gives you room to fix migration problems and lets you communicate the change before users find a broken link.

These steps hold up best inside a standing governance routine. If you do not have one yet, Establishing a Power Platform Center of Excellence shows how to build one that covers apps, flows and agents together.

How do you tie app spend to measurable value?

Under App Builder, apps looked free because the Microsoft 365 Copilot license covered them. In the new model, every app consumes Copilot Credits to build and to run. For organizations buying Copilot Business, usage-based billing is also switched on by default for new licenses from December 1, 2026, with a default spending cap per user. Our Microsoft 365 Copilot Licensing Changes: December 2026 Guide covers those defaults.

That makes this retirement the right moment to put a simple scorecard on every app you keep:

• Usage: monthly active users and sessions
• Outcome: the process the app supports and whether it finishes faster or with fewer errors
• Value: tasks completed through the app multiplied by the time each task would take without it
• Cost: Copilot Credits consumed, plus owner hours to maintain the app

For example, a site inspection app used by 20 field staff to log 200 inspections a month, each saving about 10 minutes of paperwork, returns roughly 33 hours a month. That is easy to weigh against its credit consumption. An app opened twice last quarter by its own maker is a retirement candidate, however clever it was.

Review the scorecard quarterly and fund what pays back. Beyond 'Active Users': The Copilot Adoption Metrics That Actually Prove Value shows how to turn these signals into an ROI story leadership will support.

App Builder and vibe.powerapps.com retirement FAQ

Will our existing App Builder apps stop working before November 30?

No. Existing apps keep working until the retirement date, and you can open them to start the in-product migration once it reaches your tenant. Only the creation of new apps has stopped.

What happens to the data in our App Builder and vibe apps?

The notice says unmigrated apps will no longer be accessible through the retired experiences. It does not say what happens to the underlying SharePoint lists or Dataverse tables. Treat that data as at risk: record where it lives and export anything important before November 30.

Is Power Apps being retired?

No. MC1505609 covers only the App Builder agent in Microsoft 365 Copilot and vibe.powerapps.com. Canvas apps, model-driven apps and the rest of Power Platform are not affected.

Do we need new licenses to use Copilot Cowork or Copilot Studio apps?

Building and running apps in the new experiences consumes Copilot Credits, so you need usage-based billing or a credit capacity in place. Cowork apps also require a Microsoft 365 Copilot license and Frontier enrollment. Confirm the right mix with your licensing partner before you migrate.

How can 2toLead help?

2toLead works with small and mid-market organizations across healthcare, nonprofit, education, financial services, professional services, government and manufacturing to build, govern and measure apps and agents on Microsoft 365 and Power Platform. Before November 30, we can help you:

• Inventory App Builder and vibe apps, confirm owners and data locations, and flag what to migrate, rebuild or retire
• Rebuild essential apps as governed Power Apps, or migrate them to Copilot Studio with the right environment and connector policies
• Configure Copilot Credit billing, spending limits and a simple value scorecard for every app you keep
• Get your makers confident in the new experience with hands-on Copilot Studio in a Day training

For more on Copilot, agents and governance, browse the 2toLead Insights hub. If you would like a second set of eyes on your app inventory, book an App Builder migration review with our team before the November 30 retirement.

No hype. Just practical, governed AI that actually gets adopted.