Copilot App Builder Retires on 30 Nov 2026: Moving Your Apps

What Microsoft announced and when

Microsoft posted the retirement in the Microsoft 365 admin center as message MC1505609 on 12 October 2026 ("Microsoft 365 Copilot and Power Apps: Retirement of App Builder agent and vibe.powerapps.com"). Admins can read it in Message center; a public copy is kept in the Message Center archive. The reason given is to consolidate natural-language app building into two places: Copilot Cowork and Microsoft Copilot Studio.

Who is affected

Two groups of people built apps with these tools, and many small businesses have neither. You are affected only if someone in your organisation used one of them.

• App Builder agent users. App Builder was an agent inside Microsoft 365 Copilot, available to tenants in Microsoft's Frontier early-access program. Users added it from the Agent Store and described an app in plain words.
• vibe.powerapps.com users. The Power Apps vibe experience was a preview that built a plan, data model and app from a description. It ran in Power Platform environments, not the default environment.
• Admins who support those makers. The notice asks admins to find makers, tell them the timeline and point new work to the replacements.

If no one in your company has a Microsoft 365 Copilot licence with Frontier enabled, and no one has used vibe.powerapps.com, there is nothing to migrate. Classic Power Apps (canvas and model-driven apps) are not part of this retirement.

Where the apps can move: Copilot Studio or Copilot Cowork

Microsoft's announcement of apps in Copilot Cowork and Copilot Studio describes both as conversation-first app builders whose apps run on the new Copilot Managed Runtime, with Entra sign-in and an inventory in the Microsoft 365 admin center.

Both replacements are previews. Microsoft's Copilot Studio apps overview states that preview features are not meant for production use and may have restricted functionality. Moving a business-critical app from one preview to another is a risk you should name, not ignore.

What happens to the data behind your app

This is the part owners usually care about most. The app screen is easy to rebuild; the records inside it are not.

• App Builder apps store their data in Microsoft Lists on a SharePoint site. Microsoft's App Builder help page notes that deleting an app does not delete the SharePoint site; it must be deleted manually. So the list data stays in your tenant until you remove it.
• vibe.powerapps.com apps keep their data model in the Power Platform environment they were built in. Check that environment before you delete anything.
• Sharing links. App Builder apps were shared by link, and anyone in the organisation with the link could use the app and its data. Review who had access before you republish anything.

Before migrating, export the list or table to Excel or CSV and save it somewhere your backups cover. That gives you a clean copy even if the migration tool misses something.

Migration steps for a small business

For one or two simple apps, this is an afternoon of work for the person who built them.

1. 1

   List every App Builder and vibe app in use

   Ask staff who have Copilot or Power Apps access. Note the app name, the owner and what data it holds.

2. 2

   Export the data first

   Open the Microsoft List or table behind each app and export to Excel or CSV. Store the file in a backed-up location.

3. 3

   Decide keep, rebuild or drop

   Some apps were experiments. Drop those. For apps people use daily, decide whether a preview tool is acceptable or whether a stable tool is safer.

4. 4

   Run the in-product migration

   Open the existing app in its old tool and follow the migration prompt that Microsoft made available from mid-October 2026. Check that the app opens in Copilot Studio afterwards.

5. 5

   Test with real users and real data

   Have the people who use the app run a normal day's tasks. Check forms save, lists update and permissions match the old app.

6. 6

   Clean up before 30 November

   Once the migrated app works, remove old sharing links and, if no longer needed, the old SharePoint site holding App Builder data.

Should you move to another preview or rebuild on something stable?

The honest answer depends on how much the app matters. A team lunch roster can live in a preview tool. A job sheet, stock count or customer record your staff open every day probably should not.

Stable options include a classic Power Apps canvas app with Power Automate, a plain Microsoft List with a form, or a small custom web app. For AI features inside a business tool, compare model choices in our guide to ChatGPT vs Claude vs Gemini for business. Choosing between automation tools is covered in Power Automate vs Zapier.

Do it yourself or get help?

If the app is simple and the person who built it is still with you, follow the steps above and test before 30 November. Export the data no matter what you decide.

If a retired app ran part of your operations, our Custom Business App service rebuilds it as an app you own (from S$4,900, fixed price, paid upfront). For simpler cases, such as a form that feeds a list and sends approvals, Workflow Automation (S$390) is often enough. IT Sorted is a Singapore-based team of developers with over 10 years of experience. For a sense of what custom builds usually cost, see how much a website costs in Singapore.