Microsoft retires App Builder and consolidates AI app building
Diesen Beitrag auf Deutsch lesen
App Builder and vibe.powerapps.com retire on November 30. Apps can move through an in-product migration tool, while the replacement path remains preview-based.
TL;DR
Microsoft retires the App Builder agent and vibe.powerapps.com on November 30. Apps worth keeping can move through an in-product migration tool. Chat-based building shifts to Copilot Cowork and Copilot Studio, with personal developer environments, DLP and an admin inventory, but the replacement remains preview-based and Managed Runtime licensing is enforced after 20 operations.
Original on Bright Ideas Agency. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Identify processes relying on App Builder or vibe apps and plan migration for apps the business needs to retain.
- Admins/CoE: Use the new path's personal developer environments, DLP and admin inventory to manage the transition.
- Leadership/Business: Treat the replacement as preview technology and account for Copilot Credits or Power Apps Premium when people run apps on Managed Runtime.
Frequently asked questions
What happens to apps built with App Builder after November 30?
New apps can no longer be created in App Builder or vibe.powerapps.com after November 30. Apps worth keeping can move with an in-product migration tool.
How does the in-product migration tool support App Builder apps?
The tool is intended to move apps that organizations want to retain. Further information about how data and capabilities move will become available.
What licensing applies when an app runs on Copilot Managed Runtime?
Each person running an app on Managed Runtime needs Copilot Credits or a Power Apps Premium license. The preview enforces this after 20 operations.