The short version: A Power Platform tenant doesn't have a fixed environment count as at 22 September 2026; what actually gates it is database capacity, since every environment consumes at least 1 GB and a new environment with a database needs 1 GB free to be created. Developer environments sidestep that entirely: up to three per maker, free, and outside the tenant's capacity pool.
Six environment types, six sets of rules
| Type | Who can create it | Capacity rule |
|---|---|---|
| Default | One per tenant, automatic | 3 GB database, 3 GB file, 1 GB log included, excluded from the 1 GB check |
| Production | Admin, or anyone with a Power Apps licence | Needs 1 GB free database capacity to create |
| Sandbox | Admin, or as allowed by policy | Same 1 GB minimum as production |
| Developer | Anyone with the free Developer Plan | Up to 3 per maker, 2 GB database each, doesn't count against tenant capacity |
| Trial | One per user, 30-day life | Doesn't count against tenant capacity while active |
| Dataverse for Teams | Auto-created per Teams team | 2 GB per team, separate from full Dataverse capacity entirely |
Every environment, database or not, consumes 1 GB against the tenant's pool the moment it exists. The capacity check run before a new environment is created deliberately excludes the default environment's own included capacity from the sum, so it isn't quietly eaten into by every other environment's minimum requirement.
What it means for a firm under 20 staff
A firm this size rarely needs more than three or four environments: one production, one sandbox for testing changes before they go live, and maybe a developer environment for whoever builds the apps. Each of those first two needs 1 GB of free database capacity before Power Platform will let it be created, which is a low bar on any tenant with even one Premium licence, but it's the reason "just spin up a test environment" occasionally fails with a capacity error on a tenant running close to its included allowance. The fix is almost never buying more capacity; it's checking the Power Platform admin centre's capacity page first, since a forgotten trial or an old, unused environment is often quietly holding capacity nobody's using.
Developer environments are the free lever most solo builders and small teams under-use: up to three per person, entirely outside the tenant's capacity accounting, and enough for one maker to build, test and rebuild without ever touching a shared sandbox. The catch is that Dynamics 365 apps can't be installed in them and they auto-disable after 90 days of no use, so they suit active build work, not long-term storage.
The workaround
Before assuming a new environment needs a capacity purchase, check the admin centre's Capacity page for anything sitting idle: an old trial that never got cleaned up, a sandbox from a finished project, or the default environment quietly holding a few gigabytes nobody remembers filling. Reclaiming that is free. For an actively growing build, a Developer environment for the maker's own iteration, promoted through a solution into a shared sandbox and then production once it's ready, keeps day-to-day development entirely off the tenant's paid capacity pool. Which licence tier actually grants environment-creation rights in the first place, since not every Microsoft 365 plan does, is sorted in the licence picker.
Common questions
How many environments can a small Power Platform tenant have?
There's no fixed headline number; the practical ceiling is database capacity, since every environment, with or without a database, consumes at least 1 GB against the tenant's pool, and a new production or sandbox environment needs 1 GB of that free before it can be created at all. A tenant on a base licence with a handful of Premium users can typically run several environments comfortably.
How many free developer environments can one person have?
Up to three per maker with a Power Apps Developer Plan, and they don't count against the tenant's capacity pool at all. They're capped at 2 GB of database and 750 flow runs a month each, meant for one person's own build and test work, and get automatically disabled after 90 days of inactivity.
How much database capacity does a production environment need to be created?
1 GB of available database capacity, the same minimum that applies to copying, restoring or converting a trial environment to production. The tenant's default environment doesn't count against this check, since its own 3 GB database, 3 GB file and 1 GB log allowance is excluded from the calculation before the 1 GB requirement is tested.
Can't create a new environment?
Free 30-minute call. Tell me what the admin centre says and I'll tell you whether it's a cleanup job or a licence gap.