On Monday a new post showed up in Message Center in my test tenant. Its title is Microsoft 365 Copilot and Power Apps: Retirement of App Builder agent and vibe.powerapps.com. Its ID is MC1505609, and it went up on October 12, 2026.
A pink banner sits across the top of it: Action required by Nov 30, 2026.
App Builder is the agent in Microsoft 365 Copilot that builds a small app from a chat. vibe.powerapps.com is the Power Apps site that does the same thing from a prompt. Some of your staff tried them, liked the result, and shared a link with their team. Those links now have an end date.
Message Center · MC1505609
The rollout table from MC1505609. The last row is the one that matters.
The hard part is finding the apps
The first reaction I expect from most offices is “We don’t use Power Apps much, so we’re fine.”
This notice targets a different kind of app. Business users made these on their own, in a chat window, often in an afternoon. Nobody filed a ticket. Nobody wrote them down. The person who made one may have shared it with ten people and moved on.
So most of this month’s work is a list: what exists, and who relies on it. Moving each app should be quick once you know it’s there. The app nobody wrote down is the one that breaks on December 1.
The dates, in order
Here is the timeline from MC1505609, word for word where it counts.
| When | What happens |
|---|---|
| September 8, 2026 | Apps in Copilot Cowork open up through the Frontier program. |
| early October 2026 | Public preview of Apps in Microsoft Copilot Studio starts rolling out. |
| mid-October 2026 | In-product migration becomes available. You can no longer create new apps in App Builder or vibe.powerapps.com. |
| November 30, 2026 | Both tools are retired. |
Note the gap between the last two rows. You get about six weeks to open each app and move it. After that, Microsoft says apps that were not moved “will no longer be accessible through these retired experiences.”
What happens to the apps you already built
Until November 30, nothing changes for the people using them. The app opens, the data is there, the share link works.
Between now and then, a maker can open an existing App Builder or vibe app and start the move. Microsoft calls this in-product migration. I could not run it myself. My tenant has no App Builder apps, and vibe.powerapps.com refuses my tenant outright (more on that below). So I won’t tell you which button to press. Open the app, and look for the migration prompt Microsoft says will appear.
After November 30, an app you did not move stops opening. The data behind it is murkier. MC1505609 only says the app won’t be reachable “through these retired experiences.” It says nothing about the data.
Microsoft’s other pages give a hint. App Builder keeps app data in lists on a SharePoint site, and its support page says deleting an app “doesn’t delete the SharePoint site. The site must be deleted manually.” vibe builds each app inside a Power Platform environment, which is where its data lives too.
So my reading is that the data will still sit in SharePoint or Dataverse after the app is gone. But that is my reading. Microsoft hasn’t promised it. If an app holds data you need, export it before November 30. Exporting a list to Excel takes about a minute, and I’d rather spend that minute than test my guess on December 1.
A Canadian tenant can’t use vibe by default, and that helps you
vibe.powerapps.com has rules about where it runs. Microsoft’s Learn page says it works only in environments in the US, Australia, Asia, and India, only in English, and never in a default environment.
My test tenant lives in Canada. When I open vibe.powerapps.com, this is what I get.
vibe.powerapps.com · Canadian tenant
vibe.powerapps.com turning away a Canadian tenant's default environment.
For an Ontario organisation this narrows the search. Your makers could only have used vibe if someone created an environment in one of those regions. In the Power Platform admin center, go to Manage > Environments and look at the Region column. If every environment says Canada, you have no vibe apps. Your exposure is App Builder only.
How to find App Builder and vibe apps
Microsoft’s own action list starts with “Identify makers and teams currently using the App Builder agent or vibe.powerapps.com.” It does not say how. Here is what I would do, in this order.
- Ask. Send one short note to all staff. “Did you build an app by chatting with Copilot, or at vibe.powerapps.com? Reply with the app name and who uses it.” This finds more than any report will.
- Check environment regions. Use the Region column above. No US, Australia, Asia or India environments means no vibe apps.
- Look for the SharePoint sites. App Builder keeps each app’s lists on a SharePoint site. Ask your makers for those site links, then check who else is a member.
- Sort into keep and drop. For each app, ask one question. Would anyone notice if it stopped on December 1? If no, let it retire.
- Move the keepers first. Start the migration on the apps people use every day. The oldest ones can wait.
For a small office the list is usually short, and an afternoon should cover it.
Migrate to Copilot Studio or Copilot Cowork
Microsoft points makers to two places. Both run apps on the same platform, called Copilot Managed Runtime. Both are in preview.
| Copilot Cowork | Copilot Studio | |
|---|---|---|
| Who it suits | Business users who want to describe an app in chat | Makers who want more control over build, preview and publish |
| How you get in | Your tenant must join the Frontier program | Copilot Studio access, with the App (Preview) tile turned on |
| Who pays for building | Copilot Credits, per user, through a Cowork spending policy | Copilot Credits, per environment, through Copilot Studio billing |
| Where admins manage build cost | Microsoft 365 admin center | Power Platform admin center |
For most Ontario offices I’d pick Copilot Studio. Cowork apps need the Frontier program, which is an early-access track. Copilot Studio app creation is on by default, and your admin can limit it to a security group.
Admins should also check environment routing early. Apps built this way live in a personal developer environment for each maker, assigned by environment routing rules. Microsoft’s FAQ says a maker who matches no routing rule “can’t get a personal developer environment or create an app.” It also says that once the platform switches on, the Everyone catch-all rule can’t be deleted or changed. Look at your routing rules before your first maker clicks New app.
What this does not fix
Migration moves the app, and the bill changes with it. App Builder lived inside Microsoft 365 Copilot. The new home has its own meter, and Microsoft’s admin page says building apps “consumes Copilot Credits.” Running them can too. That covers everyone who uses the app, along with the person who built it.
There is one exception. Users with a Power Apps Premium licence can run these apps without spending credits, unless the app calls separately billed services or goes over its API limits.
Everyone else needs to be covered by a spending policy. During the preview, Microsoft says a user without credit coverage gets a warning first. Then access is blocked after 20 app operations or five minutes of use, whichever comes first. Picture a team leader opening the shift roster on December 2 and losing it mid-shift.
So before you migrate an app, go to Copilot > Cost management in the Microsoft 365 admin center. Set a spending policy that covers the people who use that app, with a cap. I wrote about how credits work, and why the cap matters, in what a Copilot prompt costs.
Watch for these as well.
- You are moving a preview app into another preview. Copilot Studio apps and Cowork apps are both preview features. Microsoft says preview features “aren’t meant for production use.” If an app runs something your business can’t do without, rebuild it properly instead. If you rebuild it as a classic canvas app, plan for phones that keep running an old version of the app.
- Sharing an app doesn’t share its data. Copilot Studio’s FAQ says users “might need separate permission to connected SharePoint content, Dataverse data, or other resources.” Sign in as a normal user to test the migrated app, because that is the person who hits the missing permission.
The bottom line
Find every App Builder and vibe app this week. Ask your staff, then check your environment regions. Keep the few that matter, set up Copilot Credits for the people who run them, and migrate before November 30, 2026. Export the data from anything you let go.