If you have been experimenting with Power Apps Vibe, the AI-first app building experience at vibe.powerapps.com, there is an important date to put in your calendar. Microsoft has announced that Power Apps Vibe is retiring, and you will only be able to access your vibe apps until 30 November 2026.
In this article I will cover what the retirement means for your apps, the official migration paths Microsoft has documented, and the approach I prefer for makers and developers who want to keep full control of their app: converting the vibe app into a Power Apps code app that you can edit in VS Code and deploy back into a Power Platform solution.
What is happening to Power Apps Vibe?
Microsoft’s official guidance is published on Microsoft Learn: Migrate apps from Power Apps vibe. The key points are:
- Retirement date: vibe apps remain accessible until 30 November 2026.
- Automated migration: Microsoft has stated an automated migration option is planned. Until it is available, apps need to be migrated manually.
- Migration is a rebuild, not a move: the new app is separate from the original, so keep the original until the new one works as expected.
Microsoft’s documentation outlines what happens to each part of your app during migration:
| Part of your app | What happens |
|---|---|
| Screens, navigation, components and logic | Rebuilt from your source code |
| Data in Dataverse tables or SharePoint lists | Stays in place, the new app connects to the same data |
| Draft tables | Not migrated |
| Data connections | Not carried over, new connections are created |
| Sharing | Your admin’s sharing policies for the environment apply |
| ALM (application lifecycle management) | Not supported yet on the official rebuild paths |
The official migration paths
Microsoft documents two targets for rebuilding a vibe app. In both cases you download the app’s source code as a .zip file and attach it to a migration prompt, and an AI agent rebuilds the app.
| Consideration | Copilot Cowork | Apps in Copilot Studio |
|---|---|---|
| Where you build | Microsoft 365 Copilot | Copilot Studio |
| Availability | Frontier program only | Public preview |
| Licensing | Microsoft 365 Copilot license | Access to Copilot Studio |
| Billing | Copilot Credits | Copilot Credits |
| Sharing | Link, to people in your org who can use Microsoft 365 Copilot | Specific people or groups |
These options are a good fit for citizen makers who want to stay in a prompt-driven experience. However, there are a few things practitioners should be aware of:
- ALM is not supported yet, so you cannot move the rebuilt app to test or production environments.
- Apps in Copilot Studio is in public preview and is not meant for production use.
- The Copilot Cowork App skill is only available to Frontier program members.
- Rebuilt apps cannot connect to Dataverse tables in the default environment yet.
If your vibe app has become something your business relies on, you will most likely want it in a solution, under source control and deployable through your environments. That is where code apps come in.
Why convert to a code app?
Power Apps code apps let developers build custom web apps in a code-first IDE such as VS Code, using frameworks like React and Vue, and run them on Power Platform. They use Microsoft Entra authentication, can call Power Platform data sources and over 1,500 connectors directly from JavaScript, and they respect your organisation’s managed platform policies such as DLP, Conditional Access, sharing limits and tenant isolation.
Under the hood a vibe app is already a code-based web app. When you download the source you get pages, components, styles and configuration files, including a power.config.json file, the same configuration file used by code apps. This makes the code app route a natural fit, and it gives you:
- Full control of the source in VS Code, including the ability to keep it in Git.
- Solution support, as the CLI can push the app straight into a Power Platform solution.
- A repeatable deployment through the Power Apps CLI rather than a prompt-based rebuild.
- Your original code, rather than an AI interpretation of it.
Video walkthrough
The video below shows the end to end process: downloading a vibe app, converting it to a code app that can be managed and edited in VS Code, and redeploying it into a Power Platform solution.
Prerequisites
Before you start, make sure you have the following in place:
- Code apps enabled in the target environment. In the Power Platform admin center go to Manage > Environments > select the environment > Settings > Product > Features, then turn on Enable code apps and select Save.
- Developer tools: VS Code, Node.js (LTS) and Git.
- The Power Apps CLI, installed from npm (covered below).
- A solution in the target environment to hold the app, and its solution ID.
- Licensing: end users of code apps need a Power Apps Premium license, pay-as-you-go, an App Pass, or auto-claim enabled.
Step 1: Prepare your data
Draft tables in a vibe app only exist in memory and will not come across unless they are published.
- Sign in to vibe.powerapps.com and open your app to edit.
- Select Publish.
- Under Data environment, choose the environment for your tables. Dataverse tables should be published to the same environment as the app.
Then note down the details you will need:
- Dataverse: the environment ID and the table logical names (for example
cr8a1_inspection). - SharePoint: the site URL and list names.
Step 2: Download the source code
In vibe.powerapps.com, open your app, select Edit, then Download source. This gives you a .zip file containing the complete source code of the app.
Note that Microsoft’s guidance for the Copilot rebuild paths says not to extract the .zip, as it is attached to the prompt as is. For the code app route we want to work with the files directly, so extract it into a working folder and open that folder in VS Code.
Step 3: Install the Power Apps CLI and dependencies
Microsoft now recommends the npm-based Power Apps CLI for code apps. The older pac code commands are in preview and will be deprecated in a future release. From a terminal in the project folder, run:
npm install --global @microsoft/power-apps-cli
npm install --global @microsoft/power-apps
npm installStep 4: Initialise the code app
Initialise the project as a code app against your target environment. You will be prompted to sign in with your Power Platform account if you are not already authenticated.
pa app init --display-name "My Converted App" --environment-id <environment-id>This writes the app settings to power.config.json. You can confirm the settings at any time with:
pa app get-settingsStep 5: Reconnect your data sources
As with the official migration, data connections are not carried over. Add your data sources back using the CLI, which generates typed models and services for the app to use. For a Dataverse table:
pa app add data-source --connector dataverse --table cr8a1_inspectionFor a SharePoint list:
pa app add data-source \
--connector "SharePoint" \
--connection-id <connection-id> \
--dataset <site-url> \
--table <list-name>A couple of points to note:
- Native Dataverse supports one table per command, so run the command for each table.
- If you want the app to use a connection reference inside your solution, which is the better option for ALM, use
--connection-refwith--solution-id. - Update any data calls in the code to use the generated services where required.
Step 6: Run and test locally
pa app runOpen the URL labelled Local Play in the same browser profile you use for your Power Platform tenant. Chrome and Edge may block localhost requests, so you might need to grant local network access permission. Confirm the app shows your existing records rather than sample data, and test create, edit and delete actions.
Step 7: Build and push into your solution
Once you are happy with the app, build it and push it to Power Platform. Passing the solution ID adds the code app to your solution.
npm run build
pa app push --solution-id <solution-id>On success, the command returns a Power Apps URL where you can run the app. You will also see the app listed in your solution at make.powerapps.com, ready to be exported and deployed through your environments like any other solution component.
Step 8: Share the app
Share the app with users from the maker portal, or from the CLI:
pa app share --principal user@contoso.com --access playRemember that sharing the app and sharing the data are separate. Users also need permissions to the underlying tables or lists, along with the appropriate license.
Code app limitations to be aware of
Code apps are a strong option, but they do have some current limitations according to Microsoft Learn:
- No Power Platform Git integration support (use your own Git repository for the source).
- Not supported in Power Apps for Windows.
- No Power BI data integration (PowerBIIntegration function), although they can be embedded in Power BI reports using the Power Apps visual.
- No SharePoint forms integration.
- No Secure Implicit Connections support.
- No Storage SAS IP binding support. Use Conditional Access to restrict access by location instead.
Which option should you choose?
- Copilot Cowork or Apps in Copilot Studio if you are a citizen maker, the app is personal or team level, and you want to continue building with prompts.
- Code app if the app is business critical, needs to live in a solution, must move between dev, test and production, or will be maintained by developers in VS Code.
Summary
With Power Apps Vibe retiring on 30 November 2026, now is the time to take stock of the vibe apps in your tenant and plan their migration. Publish your draft tables, download the source and decide on your target. For anything that needs proper ALM, converting to a code app gives you the source in VS Code, deployment through the Power Apps CLI and a home inside your Power Platform solution.
Keep an eye on the Microsoft Learn migration page, as it is still being updated and the automated migration option may change the approach for some apps.