TL;DR

  • Unmanaged developer environments are a class of Power Platform environments of the Developer type that sit outside Managed Environments policies, usage insights and sharing limits, so an administrator sees them in a list and governs little of what happens inside.
  • Microsoft ends their creation on 15 November 2026: the Power Apps Developer Plan no longer provisions a developer environment, and no new unmanaged developer environment can be created from Power Apps, the Power Platform admin center, PowerShell or the Power Platform CLI.
  • Existing unmanaged developer environments are suspended from 15 December 2026, when their apps, flows, agents, Power Pages developer sites and data become unavailable, and deletion starts on 15 January 2027.
  • The conversion runs through Managed Environments, which bring environment groups, limit sharing, weekly usage insights, data policies, pipelines, solution checker, an IP firewall, customer managed keys and conditional access on individual apps.
  • Licensing decides the answer: Managed Environments use rights are included with standalone Power Apps, Power Automate, Microsoft Copilot Studio, Power Pages and Dynamics 365 licenses, and the Power Apps Developer Plan carries no such entitlement.
  • The environments to act on are found under Manage, Environments in the admin center, filtered by Type Developer and Managed No, and the Last activity column ranks the ones still in use.
  • Environment routing gives each maker a managed developer environment, one per user, which is the path Microsoft recommends for makers who need a personal space to build and test.

Deprecation section with the three dates, learn.microsoft.com/en-us/power-platform/important-changes-coming

Microsoft's important-changes page carries the three phases, the reason for the change and the steps for administrators. Source: learn.microsoft.com/en-us/power-platform/important-changes-coming, retrieved 15 November 2026.

What an unmanaged developer environment leaves outside admin control

Microsoft's own explanation is the clearest part of the notice. Unmanaged developer environments sit outside many of the governance controls administrators rely on, and the page names three: Managed Environments policies, usage insights and sharing limits. These environments appear in the admin center, consume capacity, run business processes and remain outside Managed Environments policies, usage insights and sharing limits.

The detail that catches teams is where these environments come from. Power Platform created these environments whenever a user signed up for the free Power Apps Developer Plan. The deprecation covers those environments explicitly, which means the population is spread across a tenant and often owned by people outside the IT team.

A developer environment is one of those boxes. It holds apps, flows, agents, Power Pages developer sites and data, and Microsoft states that those assets become unavailable at suspension. Developer environments continue in managed form.

Tenant diagram with Dev, Prod and Test per country, learn.microsoft.com/en-us/power-platform/admin/environments-overview

Microsoft's diagram of a tenant: Dev, Prod and Test environments organised by country, each with its own apps, flows and Dataverse storage. Source: learn.microsoft.com/en-us/power-platform/admin/environments-overview, retrieved 15 November 2026.

Three dates end creation, access and data

The timeline is short and dated, which makes it easy to put in front of a management team.

Creation ends on 15 November 2026. Signing up for the Power Apps Developer Plan no longer creates a developer environment, and no new unmanaged developer environment can be created from Power Apps, the admin center, PowerShell or the CLI. Microsoft adds the point that matters for planning: from that date users can create only managed developer environments, with a limit of one per user, and existing managed developer environments keep their current state even where a user already has more than one.

Managed environments feature page, learn.microsoft.com/en-us/power-platform/admin/managed-environment-overview

Microsoft's Managed environments overview page, which lists the controls a managed environment adds and the licensing that covers them. Source: learn.microsoft.com/en-us/power-platform/admin/managed-environment-overview, retrieved 15 November 2026.

Suspension starts on 15 December 2026. Existing unmanaged developer environments are suspended, and their apps, flows, agents, Power Pages developer sites and data become unavailable. Deletion starts on 15 January 2027 for the suspended environments. Microsoft's instruction for anyone who wants a copy of the work is to export the solutions before 15 December 2026.

A parallel change sits on the same page and shares the first date. New Dataverse for Teams environments cannot be created starting 15 November 2026, and existing ones are decommissioned on 30 October 2027. A tenant that still runs apps in Teams environments has two clocks to plan around.

Managed Environments bring policies, insights and sharing limits

Netics definition card explaining an unmanaged developer environment and how tenants get one

Netics visual, 15 November 2026: what the environment type is, and how it arrives in a tenant.

The conversion target is a managed environment, and Microsoft's overview lists what that adds: environment groups, limit sharing, weekly usage insights, data policies, pipelines in Power Platform, maker welcome content, solution checker, IP firewall, IP cookie binding, customer managed key, lockbox, extended backup, data policies for desktop flow, export to Azure Application Insights, catalog administration, default environment routing, virtual network support and conditional access on individual apps.

These controls support Microsoft's governance case, and the licensing rule turns conversion into a budget decision for work that began under a free plan. Sharing limits and usage insights are exactly the controls a tenant lacks when personal environments remain unmanaged, and data policies are the control a risk committee usually asks about first.

The licensing sentence decides whether a conversion happens this quarter. Managed Environments use rights are included with standalone Power Apps, Power Automate, Microsoft Copilot Studio, Power Pages and Dynamics 365 licenses, and the Power Apps Developer Plan carries no such entitlement. A maker who built something useful on the free plan therefore cannot simply keep it: the environment can be converted only if the people who run its apps and flows hold a licence that carries the entitlement.

Finding and converting the environments that are still in use

Netics checklist of the admin steps for finding and converting unmanaged developer environments

Netics visual, 15 November 2026: the six checks that turn the environment list into a conversion plan.

The admin-center path Microsoft gives is short. Open Manage, Environments, then filter the list where Type is Developer and Managed is No. The Last activity column ranks the environments still in use, which turns a long list into a work queue.

From there the steps split by intent. An environment worth keeping is converted by enabling Managed Environments on it, once licensing allows it, and it keeps its apps, flows, agents and data while remaining a developer environment. An environment nobody needs is left alone; it will be suspended and then deleted on the published dates. Solutions that matter should be exported regardless, because the export is the only copy that survives a deletion.

Makers get their own path in the message Microsoft sends them: export the solutions, then ask an administrator to convert the environment or to provide another environment for development and testing. Administrators also get a tenant setting to review, the Developer environment assignments control over who may create environments.

Environment routing gives each maker a managed space

Netics timeline of the three Power Platform dates

Netics visual, 15 November 2026: creation, suspension and deletion on one timeline.

Microsoft's recommended alternative for makers who need a personal space is environment routing, which creates managed developer environments automatically and is managed by default. Environment routing creates personal developer environments for makers entering supported portals, with premium licensing required to run assets and a limit of one managed developer environment per user.

For a tenant, the practical difference between the two paths is who does the work. Converting existing environments requires an administrator to check licensing and enable Managed Environments on every environment selected for retention, so the workload grows with the inventory. Turning on routing shapes what happens next: new makers receive a managed environment from the start, and the inventory that platform and infrastructure governance depends on stays current without a quarterly clean-up.

The one-month interval before suspension creates operational risk because licence checks and per-environment decisions must finish before apps, flows and data become unavailable. Between the creation stop in November and the suspension in December there is one month to find the environments, check licences and convert or export what matters, and the deletion date in January removes anything left suspended. A tenant that starts with the filtered list and the Last activity column has the inventory it needs on the first day.

Netics before-and-after card comparing an unmanaged environment with a converted managed one

Netics visual, 15 November 2026: what changes when an environment is converted, from the controls that apply to the one-environment-per-user rule.

Originally published on the Netics blog.