Power Platform Environment Types 🗂️

An environment is a container for your apps, flows, agents, connections and, optionally, a Dataverse database. Picking the right type decides who can build, whether data is backed up, and how you promote work from dev to production.

TL;DR: Use Production for live work, Sandbox for dev/test (copy and reset), and Developer for a personal, free maker workspace. Avoid building real solutions in the Default environment, every licensed user is a maker there and it has no backup guarantees. Trial environments expire, and Managed Environments is a governance layer you switch on over any type.

Environment types at a glance

Type	Purpose	Key limit
Default	Quick experimentation	No backup guarantees
Production	Business-critical work	Needs 1 GB+ Dataverse
Sandbox	Dev/test	Supports copy and reset
Developer	Personal workspace	Up to 3 per maker
Trial	Short-term evaluation	Expires after 30 days
Dataverse for Teams	Apps inside Teams	Scoped to the team
Support	Microsoft troubleshooting	Microsoft-managed

The Default environment: handle with care

🔸 There is one Default environment per tenant, created automatically. It’s fine for personal productivity and quick experiments.

🔸 Every licensed user in the tenant automatically gets the Environment Maker role, so you can’t cleanly control who builds there.

🔸 It has limited administrative control and no backup guarantees. Don’t put important or shared solutions here, create a dedicated environment instead.

Production vs Sandbox

🔸 Production is for permanent, day-to-day business work. It requires at least 1 GB of Dataverse capacity and gives you full administrative control.

🔸 Sandbox is a non-production environment for development and testing. It supports copy (clone a production environment into it) and reset (wipe it back to a clean state), which makes it a good place for safe testing before you ship.

🔸 A typical lifecycle: build in a Developer or Sandbox environment, test in a Sandbox copy of production, then deploy as a managed solution into Production.

flowchart LR
    A["Developer / Sandbox<br/>build"] --> B["Sandbox<br/>copy of Production, test"]
    B --> C["Production<br/>deploy as managed solution"]

Developer and Trial environments

🔸 Developer environments are free, personal workspaces for a single maker. You can have up to 3 per maker, they don’t consume tenant capacity, but they’re auto-disabled after 90 days without use. They don’t support Dynamics 365 apps.

🔸 A Developer environment includes Dataverse and premium/custom connectors for free, so it’s a good place to build and test a Dataverse-backed or premium-connector app before deciding on a paid plan. The catch: it’s for build and test only, not for sharing with other users or running in production.

🔸 Trial environments let you evaluate features short-term. They expire after 30 days and you get one per user, so never build anything you need to keep in a trial.

Managed Environments: a layer, not a type

🔸 Managed Environments is a premium governance capability you turn on over an existing environment (any type). It’s not a separate environment type.

🔸 It adds enterprise controls such as tighter sharing limits, usage insights, data policies and stronger backup/retention. For example, enabling Managed Environments on a production environment can extend backup retention from 7 to 28 days.

🔸 Turning it on has a licensing consequence people often miss: Microsoft’s Power Apps licensing FAQ confirms that once an environment is Managed, every active user needs a qualifying license, including users who only run standard-connector apps. The requirement is tied to activity in the environment, not to what the app uses. This is one of the areas Microsoft is moving from lenient to enforced starting February 2027, so budget for it before you flip the switch on a production environment.

Licensing and capacity

🔸 Environments draw on your tenant’s Dataverse capacity (database, file, log). A Production environment with Dataverse needs at least 1 GB available.

🔸 Developer environments don’t count against tenant capacity, which makes them a good fit for learning and prototyping.

🔸 Managed Environments is included with premium Power Platform, Power Apps and Power Automate licenses (and standalone Dynamics 365 licenses); confirm entitlement in the licensing guide.

⚠️ Watch out

🔸 A Developer environment can be made a Managed Environment, which is why it often runs fine without a premium license today: Microsoft’s own FAQ confirms a license isn’t required to build or preview an app or flow there, only to run one. Managed developer environments don’t get the Managed Environment entitlement in the Developer Plan itself though, and licensing enforcement in Managed environments generally tightens from February 2027. See Unmanaged vs Managed Environments vs Routing for the full picture, including Environment Routing.

🔸 Don’t build production solutions in the Default environment. There are no backup guarantees and maker access is uncontrolled.

🔸 Developer environments auto-disable after 90 days of inactivity and trials expire after 30 days. Move anything valuable into a proper Sandbox/Production environment first.

🔸 Right-size capacity before creating production environments, since they consume Dataverse capacity from the tenant pool.

🛠️ FAQ

Which environment should I build a real app in? A dedicated Production environment for live use, developed and tested first in a Sandbox (or Developer) environment, never the Default environment.

What’s special about a Sandbox environment? It supports copy and reset, so you can mirror production for testing and then wipe it clean.

Are Developer environments free? Yes, they’re personal maker workspaces that don’t consume tenant capacity, but you’re limited to 3 per maker and they auto-disable after 90 days of inactivity.

Is a Managed Environment a type of environment? No. It’s a governance layer you enable on top of any existing environment to add premium admin, security and backup controls.

Does enabling Managed Environments force everyone to get a premium license? Per Microsoft’s own licensing FAQ, yes, once active: every user running anything in that environment needs a qualifying license, even for a standard-connector-only app. Enforcement has historically been lenient here, but Microsoft has stated it tightens from February 2027, so plan licenses before you enable it on a production environment, not after.

How long does a Trial environment last? 30 days, after which it expires, so don’t store anything you need to keep.

🔗 Related

🔸 Unmanaged vs Managed Environments vs Routing, the full licensing picture, including Environment Routing.

🔸 Dataverse vs SharePoint, where your data actually lives.

🔸 Managed vs Unmanaged Solutions, how you move work between environments.

🔸 All Dataverse tips · Knowledge base overview

Details reflect Microsoft Learn at time of writing. Microsoft ships changes fast, so always confirm current limits and licensing in the Microsoft Power Platform documentation.