EngineeringPower Platform

Unmanaged developer environments end December 15

No new unmanaged developer environments after November 15. The ones you have are suspended on December 15 and deleted from January 15, 2027. Here's how to pick which to keep, and what keeping them costs.

Cohash Enterprise Platforms Practice November 2026 13 min read 8 chapters 3-question check
part 10 of 12 · Running enterprise platforms well
Time to decide No new ones Suspended Deletionstarts Nov 2026 Feb 2027

the ideaExport or convert before December 15. After that the work goes dark.

after reading, you can
  • Find every unmanaged developer environment in your tenant and who owns it
  • Decide whether each one gets converted, moved or retired, and what the licences would cost
  • Spot the flows and connections that won't survive a solution export on their own

From November 15, nobody in your tenant can create an unmanaged developer environmentdefinitionA private Power Platform space for one person to build and test apps, flows and agents. It isn't meant for anything people rely on day to day., and the free Power Apps Developer PlandefinitionMicrosoft's free Power Apps plan for building and testing. Until November 15, 2026 signing up also gave you a developer environment, and after that date it doesn't. stops handing them out. The ones you already have go dark on December 15 and start being deleted on January 15, 2027. Find yours this week, then convert, move or retire each one before December 15.

in plain wordsSuspension: Dec 15, 2026

Free maker sandboxes switch off in December

Power Platform is Microsoft's toolkit for building business apps, automated workflows and chat agents without much code. For years anyone with a work account could sign up for the free Developer Plan and get a private space, called a developer environment, to try things out. Microsoft is ending the free, ungoverned version of that space. If nobody acts, the space and everything in it stop working in mid-December, and Microsoft starts deleting them a month later. An admin can keep one by switching on Managed Environments, Microsoft's governance layer, but then anyone who runs those apps needs a paid premium licence. The other routes are to copy the work somewhere else or let it go.

think of it like this

Think of a company that let staff set up their own workbench in the basement, with no sign-up sheet and no inspections. Management is now clearing the basement. You can register a bench and pay for its upkeep, carry your projects upstairs to a shared workshop, or let the cleaners take it. The cleaners come on a date, whether or not you've emptied the drawers.

who should care
  • Power Platform admins
  • Makers and citizen developers
  • Pro developers and ISVs
  • Microsoft 365 admins
  • Licensing and finance owners
  • CoE and governance leads
chapter 01

Why a free sandbox deserves a decision this month

Nov 15, 2026No new unmanaged developer environments, from any route
Dec 15, 2026Existing ones suspended: apps, flows, agents, sites and data unavailable
Jan 15, 2027Suspended environments start being deleted
1 per userManaged developer environments each user can create from now on

Developer environments were meant for one person's experiments, and plenty of them stayed that way. Others drifted. A maker builds a handy approval flow, shares the app with five colleagues, and a year later a team's weekly process runs out of a space with nobody's name on the budget. Microsoft puts a banner on apps running in a developer environment, but a banner doesn't tell anyone what happens in December.

Suspension stops the apps, flows, agents, Power Pages developer sites and data all at once. So the people who'll notice first are the colleagues using that approval app, and the person who built it may be on holiday that week. Nobody gets a gradual slowdown to warn them.

what changesOne unmanaged developer environment, from today to deletionLeave it alone and it ends at step five. Convert it or export the solutions at step three and the work survives.
  1. 01 Today: still works

    Nothing's changed yet. Apps open, flows run and the maker can still edit, so nobody using them has a reason to look up the date.

  2. 02 Nov 15: creation ends

    Signing up for the Developer Plan stops creating a space. Power Apps, the admin center, PowerShell and the CLI all refuse new unmanaged ones.

  3. 03 Someone decides

    An admin enables Managed Environments on it, or the maker exports the solutions and imports them somewhere else. Or everyone agrees to let it go.

  4. 04 Dec 15: suspended

    Whatever is still unmanaged stops. Users open the app and get nothing, and scheduled flows don't fire.

  5. 05 Jan 15: deletion starts

    Microsoft starts deleting the suspended environments. Solutions exported earlier are the only copy left.

For engineers: "unmanaged" here has nothing to do with unmanaged versus managed solutions. It's an environment property, the managed environmentsdefinitionThe governance switch an admin flips on an environment. You get sharing limits and usage insights, and the people running apps there need premium licences. flag an admin switches on per environment. A managed developer environment, including every personal environment that environment routingdefinitionAn admin setting that gives each maker their own managed space. They land there automatically the first time they open the maker tools. creates, isn't affected at all.

chapter 02

What Microsoft changed, and what stays the same

The changes that touch your makers

removedDeveloper Plan sign-up no longer creates a space

People can still sign up for the plan. From November 15 it just doesn't give them an environment any more, so they'll have to ask an admin.

deprecatedUnmanaged developer environments

Suspension comes on December 15 and deletion from January 15, 2027. Microsoft's FAQ says activity doesn't matter, so a busy environment goes the same way as an idle one.

changedOne managed developer environment per user

The old allowance was the sign-up environment plus up to three created in the admin center. Going forward each user gets one. People who already own several managed ones keep them.

changedRunning assets needs a premium licence

The Developer Plan carries no Managed Environments rights. Makers can still build and preview for free, but anyone running the app or flow in a managed developer environment needs a premium licence.

enhancedPersonal environments through routing

With routing on, a maker who opens Power Apps lands in a managed space of their own, no request needed. Microsoft now calls these personal environments.

fixedProduction, sandbox, trial and default unchanged

Only unmanaged developer environments are in scope. Solutions you export before suspension are yours to keep and import elsewhere.

Microsoft says the reason is governance. These spaces sat outside the controls admins rely on, like sharing limits, usage insights and Managed Environments policies. In a managed environment those controls apply, and the maker still gets a space of their own.

chapter 03

The dates, and the ones already in motion

Dates to plan around

  1. Mar 2026
    Licence notices to admins begin

    Admins start getting licence warnings for managed environments.

  2. Oct 2026
    Docs carry the warning

    Microsoft's pages carry the three dates.

  3. Nov 15, 2026
    Creation ends

    No new unmanaged developer environments. Dataverse for Teams creation ends the same day.

  4. Dec 15, 2026
    Suspension starts

    Apps, flows, agents, sites and data all stop.

  5. Jan 15, 2027
    Deletion starts

    Suspended environments start being deleted.

  6. Feb 2027
    Licence check gets strict

    No licence, no app, in any managed space.

The February line matters if you convert. Microsoft says premium licences in managed environments aren't a new rule, but from February 2027 an unlicensed user can't open the app at all. So a developer environment you convert in December to save a team's app can stop that team opening its apps from February, unless the premium licences come with it.

There's a quieter clock too. Unused developer environments already get disabled after 30 days with no activity and deleted 15 days after that, with warning emails along the way. Some of what you find in the inventory may already be on that countdown, and a few may be gone before December 15 arrives.

chapter 04

Your options for each environment

Treat every environment on the list as its own decision. Most will be abandoned tutorials and need nothing more than a quick check with the owner. The handful with real users behind them are where the money and the risk sit.

tableYour choices for each environment, before Dec 15
RouteWhat you keepWhat it costs youFits when
Convert to managedEverything in place: apps, flows, agents, data, sitesPremium licences for everyone who runs the assets; admin governance workReal people use it and you'd pay to keep it running
Export and moveSolutions and their data model; records only if you export themRe-creating connections and gateways; adding custom connectors and non-solution items to the solutionThe work belongs in a team sandbox or dev environment you already pay for
Standard trialA 30-day place to try premium featuresIt ends after 30 days unless an admin extends it onceSomeone only needs to experiment for a few weeks
Let it retireNothing, unless you export firstNo spend; possibly a surprised userTutorials, abandoned tests, leavers' experiments
side by sideDeveloper spaces, before and after
Before: free and ungoverned
  • Sign up for the plan and you got a space, and you could create up to three in the admin center
  • No sharing limits from Managed Environments
  • Outside usage insights and environment policies
  • Premium connectors free while building
After: one governed space each
  • One managed developer space per user
  • Personal spaces share with five people by default
  • Usage insights and solution checker on by default
  • Running anything there needs a premium licence

Converting is Microsoft's recommended path, and it's the right one when the users already hold premium licences. Plenty of shops won't be in that position. A flow builder who only has Microsoft 365 can keep building in a managed space for free, but the moment their colleagues run the app, each of them needs a licence. Power Apps Premium lists at $20 per user per month, paid yearly, rising to $22 for terms that start on or after January 1, 2027. Use that as a rough yardstick and check your own agreement before you quote anyone.

Kanwal Khipple, a Microsoft MVP who runs the consultancy 2toLead, put it bluntly in an October write-up: decide who pays for the licences before you pick the technical route. That's the order we'd use too. Converting one environment is a few clicks, and getting a budget owner to say yes can take much longer than that.

chapter 05

What to do now, by role

Who does what before December 15

Business ownerthis week
  • Ask IT whether any app your team relies on lives in someone's developer environment. People often don't know.
  • Name a budget owner for premium licences if a kept app needs them. Without one, nothing gets converted.
  • Agree a retire-by date for experiments nobody will pay for, and tell the makers.
Power Platform adminby Nov 21
  • Filter Manage, Environments for Type Developer and Managed No, and sort by Last activity.
  • Email each owner with their environment name and the December 15 date. Ask keep, move or retire.
  • Switch on environment routing so new makers land in a personal environment instead of the default one.
  • Check the Developer environment assignments setting. It decides who can still create spaces by hand.
Makers and developersbefore Dec 1
  • Put every app and flow you want to keep into a solution, then export it. Keep the zip somewhere backed up.
  • Write down the connections, custom connectors and gateways your work uses. Put the custom connectors in the solution, and set up the connections and gateways again by hand.
  • If colleagues run your app, tell your admin. Converting means they'll each need a premium licence.
Licensing and financeby Dec 8
  • For each app you're keeping, get the list of people who run it from the admin and price a premium licence for each of them.
  • Make sure the licences arrive before February. After that, unlicensed users can't open apps in managed environments.
inventory-environments.ps1example output
# example: Windows PowerShell 5.x
Install-Module -Scope CurrentUser `
  Microsoft.PowerApps.Administration.PowerShell
Add-PowerAppsAccount
# every environment, for the owner spreadsheet
Get-AdminPowerAppEnvironment |
  Export-Csv '.\environments.csv'
# how many apps sit in each environment
Get-AdminPowerApp |
  Select -ExpandProperty EnvironmentName |
  Group | Sort Count -Descending
# example output
Count Name
    9 3b9e7c41-...
    1 c20f5d88-...

The script gives you a spreadsheet and an app count per environment. Take the type, the managed flag and Last activity from the admin center list, because that's the filter Microsoft's own guidance uses, and join the two on the environment ID.

The order we'd run it in

  1. 01
    Take the inventory

    Pull every developer environment with Managed set to No. Add the owner, last activity date and a rough count of apps and flows, then sort by activity so the live ones come first.

  2. 02
    Ask the owners

    Send each owner a short note with the date and three choices. Silence after a week counts as retire, but export the solutions first anyway. It costs a few minutes and saves an awkward January.

  3. 03
    Count the users

    For anything marked keep, list who actually runs the apps and flows, then check their licences. That list decides between converting and moving.

  4. 04
    Convert the licensed ones

    Enable Managed Environments on each one, from the admin center or in PowerShell. It takes the Power Platform Administrator or Dynamics 365 Administrator role, so an environment admin can't do it alone.

  5. 05
    Move the rest

    Wrap non-solution flows and apps into solutions, export them and import into a sandbox the team already pays for. Then rebuild connections under an account that won't leave with one person.

  6. 06
    Set up the replacement

    Turn on environment routing with an environment group, so the next maker gets a governed personal space on day one. Then tell people where to go.

chapter 06

Close the identity gaps these environments leave

Developer environments carry access nobody reviews. The maker who created one is its admin, and every connection inside it runs as whoever signed in when the flow was built. When that maker leaves, the flow still holds their connection to SharePoint, SQL or Salesforce until something breaks or someone notices.

Use the clean-up to fix that. Each flow you keep should run under a named service account or a connection reference in a solution, with an owner who's still employed. When you re-import or rebuild custom connectors, rotate their client secrets and API keys as you go, and delete the old ones from the source system.

Routing helps here too. Microsoft's defaults for personal environments block sharing with security groups and cap sharing at five people. An app can't quietly grow to forty users there unless an admin changes the rule, which forces the conversation about where it belongs.

before

Before: free developer spaces, nobody watching

Anyone could sign up and get a space. Apps got shared with whoever asked, and every connection ran as the maker who built it.

Before: free developer spaces, nobody watching Anyone could sign up and get a space. Apps got shared with whoever asked, and every connection ran as the maker who built it. 01 · MAKERS 02 · UNMANAGED DEVELOPER 03 · SYSTEMS as maker as leaver Maker A Developer Plan Maker B left in June A's environment approval app, 40 users B's environment nightly sync flow SharePoint maker's connection SQL database B's credentials © Cohash · cohash.com
01 · MAKERS02 · UNMANAGED DEVELOPER03 · SYSTEMS Maker A: Developer Plan Maker A Developer Plan Maker B: left in June Maker B left in June A's environment: approval app, 40 users A's environment approval app, 40users B's environment: nightly sync flow B's environment nightly sync flow SharePoint: maker's connection SharePoint maker's connection SQL database: B's credentials SQL database B's credentials as maker as leaver © Cohash · cohash.com
after

After: routed, managed and owned

Makers land in their own managed space. Anything with real users moves to a team environment with licences and named connections.

After: routed, managed and owned Makers land in their own managed space. Anything with real users moves to a team environment with licences and named connections. 01 · MAKERS 02 · MANAGED ENVIRONMENTS 03 · SYSTEMS solution connection ref Maker A premium licence New makers routed on first visit Personal environment share with 5 max Team sandbox approval app imported SharePoint service account SQL database rotated secret © Cohash · cohash.com
01 · MAKERS02 · MANAGED ENVIRONMENTS03 · SYSTEMS Maker A: premium licence Maker A premium licence New makers: routed on first visit New makers routed on firstvisit Personal environment: share with 5 max Personalenvironment share with 5 max Team sandbox: approval app imported Team sandbox approval appimported SharePoint: service account SharePoint service account SQL database: rotated secret SQL database rotated secret solution connection ref © Cohash · cohash.com

Durable fixes

  1. 01
    Route every maker

    Turn on routing and tie it to an environment group. Each maker gets a managed space, and new work stops piling up in the default environment everyone shares.

  2. 02
    Control who creates what

    Set the Developer environment assignments setting deliberately. Admins can also block non-admin creation with PowerShell if you'd rather hand out spaces by request.

  3. 03
    Build in solutions from day one

    Solution-aware flows get connection references, environment variables, versioning and run history in Dataverse. Non-solution flows get none of those, and they're the ones that strand during a move like this.

  4. 04
    Give every kept flow an owner

    Record the business owner and the account each connection uses. Check that list when people leave, alongside their mailbox and laptop.

chapter 07

If nobody acted in time

When a team's app has already gone dark

Work out what state the environment is in first. Then get the business process running again, and only after that rebuild things properly.

  1. 01Find out where it isfirst hour
    • Find the environment in the admin center and write down its state. Disabled, suspended and recently deleted each need a different fix.
    • If it was disabled for inactivity before the deprecation dates, re-enable it and export straight away.
    • Tell the team which app is down. Agree how they'll do the work by hand for now.
  2. 02Try to get it backsame day
    • If it's under Recently deleted, try Recover. Microsoft's soft-delete window is normally seven days, and it doesn't promise this works for deprecation deletions.
    • If it's suspended, ask Microsoft Support what your options are, quoting the environment ID. Don't promise the team a date yet.
    • Ask the maker for any exported solution zip or app package. Check their OneDrive and repos too.
  3. 03Rebuildthis week
    • Import whatever export you found into a sandbox, then re-create connections and gateway links, plus any custom connectors the export missed.
    • If nothing was exported, rebuild from screenshots and the users' memory of the steps, smallest useful version first.
    • Put the rebuilt app in a solution with connection references, so a move never strands it again.
  4. 04Recover the datathis week
    • If the records lived in Dataverse and nothing was exported, assume they're gone and say so early.
    • Check whether flows copied data elsewhere, into SharePoint lists, Excel files or email, and rebuild from there.
  5. 05Learn from itnext month
    • Add each recovered app to an owner list with its users and licences. Next time, the inventory finds it.
    • Work out why this one was missed. Check whether the owner had left or the warning emails went to a mailbox nobody reads.

Four typical situations

01 Approval app 12 weekly users 02 Developerspace unmanaged 03 Export orconvert before Dec 15 04 Suspended if nobody acts
scenario 01High risk
A finance team's approval app in one person's space
the setup
An analyst built an invoice approval app and two flows in their Developer Plan environment last year. Twelve people use it every week, and none of them has a premium licence.
what happens
On December 15 the app stops opening during month-end. Converting would have kept it, but then all twelve users would need licences before February.
what to do
Export the solution now. Either price twelve licences and convert, or import the app into a finance sandbox you already license and repoint the users.
01 60environments Managed = No 02 Sort byactivity 03 2 live syncs export and move 04 58 retire
scenario 02Medium risk
A mid-size tenant with dozens of forgotten spaces
the setup
Developer Plan sign-up was open for years. The admin center lists sixty unmanaged developer environments, and most show only a little recent activity.
what happens
The admin doesn't have time to interview sixty owners before the freeze, and two of the quiet ones turn out to run nightly data syncs.
what to do
Sort by Last activity and look at flows first, since a flow run counts as activity even when nobody signs in. Export everything active, then let the rest retire.
01 Developer Plan sign-up 02 No environment after Nov 15 03 Ask admin managed space
scenario 03Medium risk
A software vendor building for Marketplace
the setup
A small ISV's developers each used a Developer Plan environment in a test tenant to build and package a solution they sell.
what happens
After November 15 a new hire signs up and gets no environment. The existing ones will be suspended in December, in the middle of a release.
what to do
Export the solutions to source control now. Then decide between premium licences for a managed space per developer, or a shared sandbox for the team.
01 Routing on new makers 02 Old dev spaces still unmanaged 03 Convert or export
scenario 04Low risk
An enterprise that already routes makers
the setup
A large company turned on environment routing last year, so new makers already work in managed personal environments.
what happens
The new routing spaces are fine. The trouble is a set of older developer environments created before routing, still unmanaged and owned by long-serving makers.
what to do
Filter for Managed No, convert the few with licensed users, and export and retire the rest. Routing handles everyone new.
chapter 08

How Cohash helps

We run the inventory, talk to owners and sort each environment into keep, move or retire, with the licence count next to each one. Then we convert or move what's kept and fix the connections and service accounts while we're in there. See our Power Platform page, the engineers who do this work, our notes on the Dataverse for Teams retirement, or start with an assessment.

key takeaways

What to take from this

  1. 01

    From November 15 nobody can create an unmanaged developer environment, and the Developer Plan stops creating one.

  2. 02

    December 15 is the real deadline. Suspended environments start being deleted on January 15, 2027.

  3. 03

    Converting keeps everything, but anyone who runs the apps then needs a premium licence.

  4. 04

    Put non-solution flows and apps into a solution before you export, and expect to rebuild connections.

  5. 05

    Backups and recovery aren't a plan here. Microsoft says plainly they don't replace keeping your work.

  6. 06

    Turn on routing. New makers then start in a governed space instead of the default one.

platforms in this noteMicrosoft Power Platform →
fact-checked November 2026 against vendor and official documentation · where to go next
  1. How Cohash delivers Microsoft Power Platform: scope, roles and architecture
  2. Hire vetted Microsoft Power Platform engineers
  3. Workflow automation
  4. Book a 30-minute working session with a senior engineer
01Is the Developer Plan going away?

Microsoft hasn't said sign-up is ending. What changes on November 15, 2026 is that signing up no longer gives you a developer environment. After that, you ask an admin for a managed one, usually through environment routing, or use a standard 30-day trial.

02What happens to my developer space in December?

If it's unmanaged, it gets suspended on December 15. Everything inside stops working at once, and a month later Microsoft starts deleting suspended environments. If it's already managed, nothing changes for you.

03How do I tell if my environment is managed?

Ask your admin, or look in the Power Platform admin center under Manage, Environments. Filter Type to Developer and look at the Managed column. Anything showing No is in scope.

04Do I need a premium licence to keep my developer environment?

To build and preview in a managed developer environment, no. To run the apps and flows there, yes, and so does everyone else who runs them. The Developer Plan doesn't include Managed Environments rights.

05Can I have more than one developer environment after November 15?

Each user can create only one managed developer environment from now on. If you already own several managed ones, you keep them. Unmanaged ones can't be created at all.

06Will exporting a solution save my data?

It saves the tables and components that are in the solution, not the records in them. Export the data separately if you need it, and expect to re-create connections and gateway links in the new environment. Custom connectors only come along if you added them to the solution.

07Is this the Dataverse for Teams change?

No, though both stop taking new environments on the same day. Dataverse for Teams has longer, with suspension in September 2027. Unmanaged developer environments get suspended this December.

next step

Tell us what you're running. We'll tell you what we'd do first.

A 30-minute working session with a senior engineer. No slides.

useful to bring
  • The platform and the version you're on
  • Where you need to get to, and by when
  • What's custom: rules, plugins, integrations
  • Any audit finding or deadline driving it