What is the difference between an environment and a tenant in Dynamics 365 and Power Platform?
By Emil Björk · Microsoft business apps consultant, Gothenburg
A tenant is the whole organisation's Microsoft 365/Entra ID container — one company, one identity boundary, one set of global admins. An environment is a smaller, Dataverse-scoped workspace inside that tenant — a database plus the apps, flows, and security around it. One tenant normally holds several environments (Development, Test, Production, and more), each isolated from the others even though all share the same tenant identity.
The mental model: tenant is the company; environments are separate workspaces or projects within that company, each with its own data and its own security boundary. A user's Entra ID identity is tenant-wide, but their access to a specific environment (and what they can do there) is controlled separately, per environment, through that environment's own security roles.
This distinction matters most in ALM: you never have 'the tenant's data' moving through a release pipeline — you have one environment's solution being deployed into another environment, all inside the same tenant. Confusing environment-level isolation with tenant-level isolation is a common source of surprise when a change in one environment doesn't automatically apply anywhere else the same tenant's users can see.
Go deeper
- Power Platform environmentsEnvironments in the Power Platform — types, capacity, regions, and how they relate to Dynamics 365 and Dataverse.
- Environment strategy for Dynamics 365 projectsHow to design dev / test / UAT / production environment topology for a Dynamics 365 implementation — naming conventions, refresh cadence, data isolation.
- Solution import / export pipelines for DataverseHow to automate Dataverse solution promotion through dev / test / prod — Power Platform CLI, Build Tools, GitHub Actions, and Power Platform Pipelines.