Power Platform deadline

Power Apps developer environment retirement: keep, move or export your work before December 15

The Power Apps developer environment retirement gives every free, unmanaged developer environment in your tenant about seven weeks of useful life. Microsoft stops new ones on November 15, 2026, suspends existing ones on December 15, 2026, and starts deleting them on January 15, 2027. For each environment there are three honest answers — convert it to a managed environment and license the people who use it, move its solutions somewhere supported, or export a copy and let it go — and the deadline that matters is the suspension date, not the deletion date.

This is a different retirement from the one hitting apps built inside Microsoft Teams. Both stop new environments on November 15, 2026, but the Dataverse for Teams retirement does not suspend anything until September 15, 2027. Developer environments go dark nine months sooner, so they belong at the top of the list. Every Microsoft date and rule below was checked against Microsoft’s documentation on October 26, 2026.

What is retiring, and on which dates?

Microsoft is deprecating unmanaged developer environments, including the free one created when someone signs up for the Power Apps Developer Plan. From November 15, 2026 no new ones can be created. From December 15, 2026 existing ones are suspended, so their apps, flows, agents and data stop being available. Deletion starts January 15, 2027.

The schedule comes from Microsoft’s important changes coming to Power Platform (opens in new tab) page, which sets out the three phases below. The right-hand column is our suggestion for what should already be done by each date.

PhaseDateWhat Microsoft says happensWhat you should have done by then
Creation endsNovember 15, 2026Signing up for the Developer Plan no longer creates an environment; no new unmanaged developer environments from Power Apps, the admin center, PowerShell or the Power Platform CLIInventory every developer environment and tell makers where new work should be built
Suspension startsDecember 15, 2026Existing unmanaged developer environments are suspended; their apps, flows, agents, Power Pages developer sites and data are not availableEach environment converted, its solutions moved, or a copy exported
Deletion startsJanuary 15, 2027Suspended unmanaged developer environments are deletedNothing left to rescue; anything not exported is gone

If your situation doesn’t fit neatly into one row, tell us what you’re seeing.

Describe my situation →

Which developer environments are affected?

Only unmanaged ones. A developer environment that already has Managed Environments switched on is untouched, and so are the personal developer environments that environment routing creates, because those are managed by default. Other environment types, such as sandbox and production, sit outside this notice. Check each developer environment in the Power Platform admin center.

In practice the list is longer than expected. The Developer Plan let anyone with a work account sign up, so environments appear wherever a maker once wanted to experiment, and until November 15 each person could create up to three. Record who owns each one, what is in it, and whether anyone outside the owner uses it. Expect many to be abandoned tests that need nothing more than a polite email and an export. That same inventory is where Power Platform governance consulting starts, and it is worth keeping once the deadline has passed.

Should you convert, move or export each environment?

It depends on what the environment is doing. Active development with a licensed maker usually belongs in a converted, managed developer environment. Anything colleagues rely on day to day belongs in a sandbox or production environment instead. Abandoned experiments only need a solution export. Decide per environment with its owner, not once for the whole tenant.

PathWhat it involvesLicence position afterwardsBest fit
Convert to a managed environmentAn admin enables Managed Environments on the existing developer environment before December 15, 2026Every person running its apps or flows, including the maker, needs a premium licence; the Developer Plan does not include these rightsOngoing development by a maker who already holds, or will be given, a premium licence
Move solutions elsewhereExport the solutions and import them into a sandbox, production or other supported environment, then re-create connections and testWhatever that environment already requires; production use needs a paid planApps or flows that colleagues already use for real work, which a developer environment was never meant to host
Export and let it goExport each solution as a file and keep it somewhere safe; let the environment be suspended and deletedNo ongoing costTraining exercises, finished proofs of concept, environments whose owner has left

Whichever path you pick, the work only travels if it is inside a solution. Apps and flows built outside one need to be added to a solution, or rebuilt, before they can be exported cleanly, so leave time for that on the environments that matter.

What does keeping a developer environment cost?

Converting is free; running anything inside afterwards is not. Managed Environments use rights are not part of the Developer Plan, so every person who runs an app or flow there, including the maker testing their own work, needs a premium licence such as Power Apps Premium, Power Automate Premium or a qualifying Dynamics 365 licence.

Microsoft’s licensing requirements for managed environments (opens in new tab) spell this out, and they are now enforced: unlicensed users of apps in managed environments have been seeing in-app notices since June 2026, and from February 2027 they are blocked from opening those apps. On Microsoft’s pricing page as we read it on 14 September 2026, Power Apps Premium was listed at $20.00 per user per month, paid yearly. Our guide to Power Apps licensing for small business covers when a seat, the pay-as-you-go meter or a different plan is the cheaper answer. Note too that from November 15, 2026 each user can create only one managed developer environment, although existing managed ones are left as they are.

Who has to act before December 15?

Both makers and admins. A maker can export their own solutions, but enabling Managed Environments on a developer environment, assigning premium licences and creating a sandbox to move work into are admin tasks. Microsoft’s own guidance to makers is to ask their admin, so admins should expect those requests in the next few weeks.

The Power Apps Developer Plan guide (opens in new tab) lists the same three options and recommends conversion where the licensing is in place. The case that needs the most care is the one Microsoft says developer environments are not for: a real business process running out of someone’s developer environment, with colleagues using the app every day. Moving that to a production environment, with proper connections, owners and licences, is a small migration in its own right, and afterwards it needs someone to look after it — the kind of ongoing work covered by Power Apps support and maintenance services.

How is this different from the Dataverse for Teams retirement?

The two notices share a November 15, 2026 creation cutoff and little else. Dataverse for Teams environments live inside a team, are suspended on September 15, 2027 and decommissioned on October 30, 2027. Unmanaged developer environments are suspended on December 15, 2026 and deleted from January 15, 2027, so they come first.

The remedies differ too. A Dataverse for Teams app is upgraded to full Dataverse or rebuilt on SharePoint lists; a developer environment is converted to a managed environment or has its solutions moved. Many tenants have both, often built by the same makers, so one inventory can cover the two — just schedule the developer environments for this year and the team apps for next.

We handle the developer environment work as a fixed-fee project agreed in writing before anything starts: the inventory, a keep, move or export decision for each environment with its licence position, and the conversions or migrations that follow. It is delivered by senior US-based Microsoft engineers, typically within 2–4 weeks, with 30 days of hypercare afterwards. With the suspension date close, tell us how many developer environments you have, or see how the fixed-fee process works.

FAQ

Questions makers and admins ask about the deadline

Yes, but from November 15, 2026 signing up no longer creates a developer environment. Ask your admin for a managed developer environment instead, for example through environment routing. Going forward each user can create only one, and running apps or flows in it needs a premium licence because the Developer Plan lacks those rights.

From December 15, 2026, the apps, flows, agents, Power Pages developer sites and data in a suspended unmanaged developer environment are not available. Deletion starts January 15, 2027. Microsoft advises exporting solutions before December 15 if you want a copy, so treat suspension, not deletion, as the real deadline for getting work out.

For trying premium features, yes. Microsoft says standard trial environments remain available and suggests them when you only need to test premium capabilities. They are short-lived, so they are not a home for ongoing development or anything people rely on; for that, use a managed developer environment, a sandbox or a production environment.

No. The licence a person holds does not protect the environment; its type does. An app built by a fully licensed maker inside their unmanaged developer environment is suspended on December 15, 2026 like any other, so it still needs to be converted to a managed environment or moved before that date.

Talk through your developer environments with a senior engineer

No hourly meter and no retainer. We scope the work in writing, you approve one fixed price, and the engineer who scoped it does the work.

Free consultation · Written fixed price before any work starts · Reply within one business day

Book a free consultation

See what your Power Apps project would take

Tell us what you’re trying to fix. We reply within one business day, and you get a written fixed-fee proposal to approve before any work begins.

Step 1 of 2: What do you need?

How can we help? Pick one

Tap to add, or type your own:

Step 2 of 2: Where should we reply?

Used only to contact you about this inquiry.

We reply within one business day. Fixed price approved before any work begins. We don’t sell your information.

Tell us what you’re trying to fix — a report, an approval process, an intranet, a Copilot rollout. We scope it as a fixed-fee project, you approve, and a senior engineer delivers in 2–4 weeks.

  • Fixed-fee scope agreed before any work starts
  • Senior, US-based Microsoft engineers — no handoffs
  • Typical 2–4 week delivery
  • 30 days of post-delivery hypercare included
Book my free consultation