Power Platform environments

What is a Power Platform environment?

A Power Platform Environment is like a container or boundary for your Power Platform resources.

Think of it as a workspace that holds:

• Power Apps
• Power Automate flows
• Power BI datasets (linked)
• Power Virtual Agents
• Dataverse databases
• Connections and connectors
• Permissions and user roles

Each environment is isolated from others — data, apps, and users do not cross environments unless you explicitly allow it.

Why environments exist

Environments help you separate:

1. Development, testing, and production (Dev/Test/Prod lifecycle)
2. Business units or regions (e.g., Europe vs. US)
3. Security boundaries (e.g., HR apps vs. Finance apps)
4. Governance and compliance (specific policies per environment)

They also determine which Dataverse database you’re connected to — each environment can have its own Dataverse instance (or none at all).

How environments work with Dataverse

• Every Dataverse database belongs to one environment.
• An environment can have one Dataverse database.
• Apps and automations in that environment use that database by default.
• Power BI, Automate, and Virtual Agents can also connect to it.

Example scenario

Imagine your company is deploying a Helpdesk app using the Power Platform:

Environment	What’s inside	Dataverse use
Development	Power App draft, test flows	Stores test data in Dev Dataverse
Test	QA app copy, user acceptance testing	Separate Dataverse for test data
Production	Final app used by employees	Live Dataverse storing real tickets

Result: you can build, test, and deploy safely — each environment keeps its apps, data, and users isolated.

How to use environments practically

Create environments

• In the Power Platform Admin Center (admin.powerplatform.microsoft.com), admins can create new environments.
• You can choose to include a Dataverse database or not.

Assign users and permissions

• Each environment has security roles.
• You can assign users as Environment Admins (manage environment and users in it), Makers (build and share apps) or Users (use apps).
• Users or groups assigned to these environment roles aren't automatically given access to the environment's database (Dataverse - if it exists) and must be given access separately.

Build and deploy

• Build your app in the Dev environment.
• Export it as a solution and import it into Test, then Prod.
• This allows version control and change management.

Environment types

Power Platform environment types - Power Platform

• Production (Security - Full Control)
  • Intended for permanent work in an organization.
• Default (Security - Limited Control. All licensed users have the environment maker role.)
  • Intended for experimentation and lightweight development. No backup guarantees, not for production workloads.
• Sandbox (Security - Full control)
  • Nonproduction environment that supports copy/reset; commonly used for development and testing.
• Trial (Security - Full Control)
  • Short-term testing; expires after 30 days; limited to one per user.
• Developer (Security - Limited control)
  • Created by users with the Developer Plan license; special environment intended only for the owner.
• Microsoft Dataverse for Teams (Security - Limited control)
  • Created for a Team when building in Teams; limited admin controls; security roles are mapped from Teams membership.