Power Platform Retirements: 5 Deadlines Before Feb 2027

TL;DR: Five Power Platform retirements land between November 15, 2026 and February 2027: Power Apps vibe and App Builder, new Dataverse for Teams environments, unmanaged developer environments, the Copilot Studio app in Teams and Power BI Q&A. Most replacements need a premium license, Dataverse capacity, Copilot Credits or Fabric capacity. Inventory now, then upgrade, move or retire each item.

Five Power Platform retirements arrive within four months, and the first is 15 days away. On November 15, 2026, Microsoft stops creating new Dataverse for Teams environments and new unmanaged developer environments. On November 30, Power Apps vibe and App Builder close. Editing in the Copilot Studio app in Teams ends in January 2027, and Power BI Q&A goes away in February.

Seen side by side, the five share a pattern: Microsoft is closing the free, team-owned corners of Power Platform and moving that work into governed environments. Our Microsoft 365 quarterly newsletter for November 2026 maps the Microsoft 365 deadlines to owners. This article does the same for the Power Platform lead.

The tools that are retiring were free to start and easy to forget. Their replacements have an owner, a license and a meter.

Which Power Platform features are retiring, and when?

Five features retire in stages between November 15, 2026 and February 2027, though existing Dataverse for Teams environments run until September 2027. Here are the dates and replacements.

Smaller removals follow: copresence and AI-generated model-driven app descriptions after November 30, and Power Apps Ideas and formula generation in canvas apps after December 11. All of them sit on Microsoft's list of important changes coming in Power Platform.

Why do these Power Platform retirements matter to IT leaders?

They move work from free, team-owned spaces into governed environments that someone has to license and fund. That is good governance, and a budget decision most organizations haven't made yet.

Easy building is also why so much of it has no owner, the pattern behind why agent sprawl is the new shadow IT. Here is where the cost shows up:

• Licenses. After a Dataverse for Teams upgrade, people who use its apps, flows and agents need Power Apps, Power Automate or Copilot Studio licenses. Managed developer environments need premium licenses too; the free Developer Plan doesn't include Managed Environments rights. Power Apps Premium rises from $20 to $22 per user per month for terms starting on or after January 1, 2027.
• Capacity. Each upgraded environment, up to 2 GB, starts counting against your tenant's Dataverse capacity, and Microsoft blocks the upgrade if you don't have enough.
• Meters. Rebuilt vibe and App Builder apps consume Copilot Credits, so each needs a budget owner. See who owns the Copilot Credits meter.
• Fabric capacity. Copilot in Power BI needs a paid Fabric capacity (F2 or higher), Power BI Premium (P1 or higher) or a Fabric Copilot capacity. A Pro or Premium Per User license alone isn't enough.
• Lost work. Unmanaged developer environments are suspended from December 15 and deleted from January 15. Anything not exported is gone.

Three sectors should look closer:

• Nonprofit: small teams often built in Dataverse for Teams precisely because it was free. Price each upgrade before you promise a program team its app will survive.
• Education: department apps built in Teams often outlive their builders. Inventory them before the winter break, while those people can still explain them.
• Government: Microsoft lists sovereign clouds as unsupported for Copilot in Power BI. Confirm what replaces Q&A in your cloud before February.

What do you need to know about each retirement?

Each retirement has one detail that changes the plan.

Power Apps vibe and App Builder: rebuild, convert or retire by November 30

Vibe and App Builder apps stay accessible until November 30, 2026. Migration rebuilds an app from its downloaded source code rather than moving it. Data in Dataverse tables or SharePoint lists stays put, but draft tables, connections and sharing links don't carry over, and Microsoft's vibe migration guidance notes that rebuilt apps can't yet move between environments.

The App skill in Copilot Cowork requires the Frontier program, and Apps in Copilot Studio is in public preview; both consume Copilot Credits. Our App Builder and vibe.powerapps.com retirement plan covers the seven steps.

Dataverse for Teams: decide before anyone needs a new one

Dataverse for Teams is a subset of Microsoft Dataverse that Teams creates the first time someone builds an app, flow or agent in a team, capped at 2 GB and without direct API access, custom connectors, desktop flows or AI Builder. From November 15, 2026, Teams stops creating these environments, including from Teams app catalog installs.

Existing environments keep working until September 15, 2027, when any not upgraded are suspended, and they're decommissioned on October 30, 2027. The team's channels, chats and files aren't affected. An upgrade in the Power Platform admin center keeps apps, flows, agents and data, makes team owners System Administrators and unties the environment from the team. You can also export solutions into an existing Dataverse environment.

Unmanaged developer environments: the deadline with the least margin

From November 15, 2026, the free Power Apps Developer Plan no longer creates a developer environment. Existing unmanaged developer environments are suspended from December 15 and deleted from January 15, 2027, with their apps, flows, agents, Power Pages developer sites and data.

To keep one, enable Managed Environments on it before December 15, which needs standalone premium licenses for the people who build and run in it. Otherwise, export its solutions to a sandbox. From now on, each maker gets one managed developer environment, which environment routing can create automatically.

Copilot Studio app in Teams: agents keep running, editing moves

Creating classic agents in the Teams app ended in June 2026. Editing ends in January 2027 and the app leaves Teams in February 2027 (Message center post MC1511056). Published agents keep answering employees; makers manage them in the Copilot Studio web app.

The catch: the Copilot Studio Teams plan only supports Dataverse for Teams environments, so most of these agents inherit that retirement too. Upgrading keeps the agent, but Microsoft notes qualified sessions can then be billed. Our Copilot Studio Teams app retirement plan has the six steps.

Power BI Q&A retirement: the date moved, the license question didn't

Microsoft first announced the retirement for December 2026; Microsoft Learn now says Q&A goes away in February 2027. Q&A in reports, dashboards, mobile and embedded scenarios stops working, as does Q&A setup, including synonyms and Teach Q&A.

Microsoft recommends Copilot in Power BI instead, with Prep data for AI replacing Q&A setup. Copilot needs the capacity described above, so find reports with Q&A visuals now and decide which audiences get Copilot and which get a standard visual. First, review how to control which data Copilot in Power BI can use.

How do you triage every app, environment and agent?

Sort every item into keep, move or retire, using last activity, a named owner and business impact. Make the license decision before the technical one.

Last activity is your fastest filter. The Power Platform admin center shows it for every environment, and a Power Platform Center of Excellence inventory adds the apps, flows and agents inside them.

What should IT leaders do before November 15?

Start with the two deadlines that hit first: steps 1 to 3 fit before November 15, and steps 4 to 7 carry you through February.

1. Find unmanaged developer environments. In the Power Platform admin center, go to Manage > Environments and filter where Type is Developer and Managed is No. Sort by Last activity and contact every owner.
2. Find Dataverse for Teams environments. In the same list, filter where Type is Microsoft Teams, and record each one's team, owners, size and last activity.
3. Turn on environment routing. It gives each maker a managed developer environment to build in after November 15. Review the Developer environment assignments tenant setting too.
4. Download vibe and App Builder source. Have every owner download source and publish draft tables by an internal deadline of November 16, two weeks before access ends.
5. Price what you keep. Count users who need Power Apps, Power Automate or Copilot Studio licenses, check Dataverse capacity and confirm which reports sit on Copilot-ready capacity. Premium purchases and renewals from January 1, 2027 are $22.
6. Convert or export before December 15. Enable Managed Environments on the developer environments you keep, export the rest and upgrade your first Dataverse for Teams environments in the same window.
7. Brief makers and the help desk. Explain where to build after November 15, where to edit agents after January and what replaces Q&A in February.

How do you put a dollar value on Power Platform retirement triage?

Compare the cost of keeping everything with the cost of keeping what people use. The gap usually pays for the triage many times over.

In a 2toLead illustrative model (swap in your own figures), a 1,200-person healthcare network finds 24 Dataverse for Teams environments whose apps reach 520 people. Upgrading all of them and licensing every user at Power Apps Premium costs $10,400 a month, or $11,440 at the $22 price for renewals from January 1, 2027.

Triage changes that. Fifteen environments show no activity in 90 days. Of the nine still in use, four are upgraded, three move into one existing Dataverse environment as solutions and two become SharePoint lists. The kept apps reach 150 people: $3,000 a month at $20, or $3,300 at $22.

That is $7,400 a month, about $88,800 a year, at today's price. The triage takes about 60 hours of admin and owner time, roughly $5,400 at a $90 loaded hourly rate, so it pays back in the first month. Then track environments retired, licenses avoided and the share of kept apps with a named owner.

What do IT leaders ask about Power Platform retirements?

Four questions come up most.

Do existing Dataverse for Teams apps stop working on November 15, 2026?

No. November 15 only stops new Dataverse for Teams environments from being created. Existing environments keep working until September 15, 2027, when any that haven't been upgraded to Dataverse are suspended, and they're decommissioned on October 30, 2027.

Do users need new licenses after a Dataverse for Teams upgrade?

Yes. After the upgrade, people who use the environment's apps, flows and agents need Power Apps, Power Automate or Copilot Studio licenses, and the environment's storage counts toward your tenant's Dataverse capacity.

What happens to unmanaged developer environments on December 15, 2026?

They start being suspended, and their apps, flows, agents, Power Pages developer sites and data become unavailable. Deletion starts January 15, 2027. Enable Managed Environments or export your solutions before December 15 to keep your work.

When does Power BI Q&A retire, and what replaces it?

Microsoft Learn says Q&A experiences go away in February 2027. Microsoft recommends Copilot in Power BI, which needs a paid Fabric capacity (F2 or higher), Power BI Premium (P1 or higher) or a Fabric Copilot capacity.

How can 2toLead help?

2toLead helps organizations in healthcare, nonprofit, education, financial services, professional services, government and manufacturing govern what their teams build. In a fixed-scope, two-week Power Platform Retirement Triage Sprint, our Microsoft MVP team will:

• Inventory every app, environment, classic agent and Q&A report affected by the five retirements
• Apply the triage matrix with each owner: keep, move or retire
• Model the license, capacity and Copilot Credits cost of everything you keep
• Convert or export developer environments before December 15 and upgrade priority Dataverse for Teams environments
• Hand over an owner register and a February readiness plan for Copilot Studio and Power BI

Find more practical guidance on the 2toLead Insights hub, or book a Power Platform Retirement Triage Sprint before the first deadline on November 15.

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