Environments and environment types

What it does

An environment is the container for a Dataverse database plus everything built against it — apps, flows, agents, connections, gateways. It sits inside one Entra tenant, is pinned to one geography, and can hold zero or one Dataverse database. The type you pick at creation decides what admin operations you get afterwards.

Key facts

The types you'll actually meet are production, sandbox, trial, developer, default and Dataverse for Teams. Production is the only one you should depend on.
Sandbox is the one with the useful operations: copy and reset. Production can't be copied to, and can't be restored to without switching it to sandbox first.
Trial environments expire after 30 days, one per user, and get no backups at all.
Developer environments come from the Power Apps Developer Plan, are meant for a single owner, and can't have a security group assigned.
Each tenant gets exactly one default environment, created in the tenant's home region, named {tenant} (default). You can't delete it and you can't take manual backups of it.
The default environment gives every licensed user in the tenant the Environment Maker role automatically. Nobody is automatically an Environment Admin.
The default environment is capped at 1 TB and ships with 3 GB database, 3 GB file and 1 GB log capacity included, which is excluded from the capacity check when you create new environments.
Trial, preview, support, developer and Teams environments don't count against tenant capacity in the reports — but every environment consumes 1 GB whether or not it has a database.
Production, sandbox, trial and (via the admin portal) developer environments let you choose a region at creation. Default and Teams environments follow the tenant home location unless you set a preferred environment location with PowerShell.
Every environment carries a History timeline of create, edit, copy, reset and delete actions with initiator and status. It's deleted along with the environment.

When to use / skip

The question is never "do I need environments", it's "how many and who's allowed to make them". Three per solution — dev, test, production — is the floor for anything you'd call a project, and the Managed Environment features you'll want later (backup retention beyond seven days, long-term retention, CMK enforcement) attach to production environments specifically. Developer environments are genuinely good for individual makers and cost you nothing but governance attention. The default environment is the one that will hurt you: it's shared, it's open to every licensed user by default, and it accumulates business-critical junk that nobody owns. Lock it down on day one or accept that you'll be doing archaeology on it in two years.

Configuration decisions

Whether to block production, sandbox, trial and developer environment creation for non-admins, and what request process replaces it.
Which environments become Managed Environments, since that gates backup retention, long-term retention and several governance rules.
Region per environment, remembering an environment can sit in a different region from the tenant, subject to the India and Australia tax restrictions.
Whether to bind a security group to each environment, which is your main lever for who can even see it — and remember developer environments don't support this.
What the default environment is for, and whether you rename it to something that says so.

Gotchas

Converting production to sandbox can't be blocked, even when production creation is. Anyone with the right role can flip the type and then reset the environment.
Switching a production environment to sandbox to perform a restore limits you to backups from the last seven days. Switch it back immediately afterwards or you lose the older ones.
Environment history disappears when the environment is hard deleted, so "who deleted this?" often has no answer.
Power Platform admins aren't automatically given the Dataverse System Administrator role in the default environment any more. Assign a couple of trusted users directly or you'll lock yourself out.
Users added to Environment Admin or Environment Maker aren't automatically given access to the Dataverse database. That's a separate assignment.

Consultant notes

Get the environment strategy signed off before anyone builds anything. Retrofitting a split from a single shared environment is a solution-extraction exercise nobody budgets for.
When a client says "we'll just use the default environment for now", price the eventual migration and show them the number.
Early release environments are the cheapest insurance you can buy against a wave update breaking a go-live. Ask for one per programme, not per project.
Push for a naming convention that encodes purpose and region. The admin centre list is sortable and filterable, which only helps if the names mean something.

Worth another look once macro-region provisioning has finished rolling out globally, or if environment groups pick up more environment-level rules.