Power Platform environments

An environment in the Power Platform is an isolated container for apps, flows, Dataverse data, and security. Environments are the unit of administration, capacity, region, and licensing. Every Dynamics 365 CRM-side app is an environment with Dataverse plus the relevant Dynamics 365 components installed. Understanding the environment model is foundational.

Environment types.

• Default. Every tenant has a single default environment, automatically created and owned by Microsoft Entra ID. It's intended for personal productivity makers and casual flows, not for production business apps. Treat it as untrusted; lock it down with DLP policies.
• Production. A first-class environment for running real apps. Includes Dataverse. The standard target for any deployed Dynamics 365 or Power Apps app.
• Sandbox. A non-production environment for testing, training, and demos. Can be reset, copied from another environment, and converted to production.
• Developer. Personal environments for individual makers, with Dataverse, scoped to the maker's own work. Free up to a usage cap.
• Trial. Time-limited environments that expire automatically.
• Microsoft Dataverse for Teams. A lightweight, Teams-scoped environment with a constrained Dataverse for in-team apps. Different storage model from full Dataverse.

Capacity

Each tenant has Dataverse storage capacity allocated by licences and add-ons. Environments compete for that capacity; the Power Platform admin centre shows usage per environment. Production environments consume more capacity than sandboxes; defaults are surprisingly small.

Regions

Environments are pinned to a region (Europe, North America, Asia Pacific, etc.) at creation. Region determines where Dataverse data physically lives. Moving an environment between regions requires a Microsoft-supported migration; default to creating in the right region.

Security groups

Each environment can be assigned a Microsoft Entra security group that controls who's allowed in. Without one, anyone in the tenant with a sufficient licence can access the environment — usually not what you want for production. Set the security group on day one.

Environment admin and DLP

Tenant admins enforce data loss prevention (DLP) policies that classify connectors (e.g. SharePoint and Dataverse as Business; Twitter and HTTP as Non-Business) and forbid flows from combining Business with Non-Business. DLP applies per environment or globally.

Lifecycle

Environments can be copied (data and customisations), reset (data wiped), backed up (Dataverse storage), and restored from backup. Production environments get 28 days of point-in-time restore by default.

Cost

Beyond Dataverse storage, environments themselves are usually free up to a count. Pay-as-you-go billing is available for tenants that want capacity-billed environments without licence allocation.

Choosing an environment type in practice

Environment sprawl

The most common environment-governance failure isn't too few environments, it's too many uncontrolled ones. Once Managed Environments and self-service environment creation are both on, any maker with the right licence can spin up a new Dataverse environment in seconds — useful for experimentation, corrosive for governance if nobody owns the resulting sprawl. A Center of Excellence typically caps who can self-create environments, requires a business justification and an owner on request, and runs a periodic sweep that flags environments with no activity for archival or deletion. Sandbox environments that outlive the project they were created for are the single biggest source of forgotten Dataverse capacity consumption.

Copying vs resetting a sandbox

Copy clones an existing environment's data and customisations into a new or existing environment — the standard way to get realistic test data without touching production. Reset wipes an environment back to an empty Dataverse with the base solution only — the right move when a sandbox has accumulated months of test junk and a clean slate is more useful than its current state. Neither operation is available on production environments directly; production is only ever a copy source, never a copy or reset target, which is the platform's guardrail against accidentally overwriting live data.

Where to go next

The design question — how many, for whom — is environment strategy for Dynamics 365 projects. Governance on top of environments is Managed Environments and DLP policies, administered from the Power Platform admin center. Capacity is explained in Dataverse storage types.