What an environment is
An environment is a bounded space holding apps, flows, connections, and (optionally) a Dataverse database — with its own security roles, its own region, and its own DLP policy scope. It is the unit of isolation, governance and lifecycle. Types:
| Type | Purpose |
|---|---|
| Default | Auto-created, EVERYONE is a maker in it — the shadow-IT petri dish |
| Production | Governed, purpose-built for a solution or team |
| Sandbox | Non-prod for dev/test; resettable |
| Developer | Individual maker's personal space (Dataverse included) |
The default-environment problem
Every tenant has a default environment that all users can create apps and flows in, and that cannot be deleted. Left ungoverned it accumulates: personal productivity flows, business-critical apps nobody sanctioned, connections to external systems, data in an ungoverned Dataverse. When a maker leaves, their orphaned flows die silently (the recurring flow-owner lesson). The first governance move in every serious estate is: lock down the default environment (restrict who can create, apply the strictest DLP) and route real work into governed production environments.
Environment strategy (the governance foundation)
- Least-maker default: restrict app/flow creation in the default env; makers get developer environments or a request-a-production-env flow.
- Purpose-built production envs: per solution/department/data-sensitivity, each with scoped DLP and named owners.
- Region and data residency: an environment has a region — data lives there (the residency conversation, Power Platform edition).
- Managed Environments (next concepts): the premium governance layer over all of this.
What to watch (proofs)
- The environment inventory: Power Platform admin center → environments — type, region, Dataverse yes/no, maker count; serv365 scans the environment surface nightly. A NEW environment appearing (especially with broad access) is a shadow-IT / governance-bypass signal.
- Default-environment lockdown: who can create in default (env settings) — should be restricted; 'everyone' is the finding.
- Orphaned assets: apps/flows whose owner has left (admin center / CoE toolkit) — the offboarding debt.
- DLP scope per environment: which policy governs each (governance module) — an environment with no/weak DLP is an open connector door.