4.1 Environments & Their Purposes

Microsoft Power Platform Fundamentals PL-900

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 What PL-900 Tests in 2026 1.2 Exam Logistics & Scoring 1.3 The Power Platform Ecosystem

2 Business Value of Microsoft Power Platform (5-10%)

2.1 Business Value of Power Apps & Power Automate 2.2 Business Value of Dataverse & Connectors 2.3 Business Value of Power Pages, Generative AI & Copilot Studio Agents

3 Manage the Environment: Microsoft Dataverse (20-25%)

3.1 Dataverse vs Traditional Databases; Tables, Columns, Relationships 3.2 Forms, Views & Business Logic (Power Fx, Business Rules) 3.3 Using AI to Create & Edit Dataverse Schema

4 Manage the Environment: Administration & Governance (20-25%)

4.1 Environments & Their Purposes 4.2 The Power Platform Security Model (Roles, Business Units, Teams) 4.3 Data Privacy (DLP), Monitoring/Analytics & ALM Pipelines

5 Demonstrate the Capabilities of Power Apps (20-25%)

5.1 Canvas Apps: Use Cases & Capabilities 5.2 Model-Driven Apps, Plan Designer & Code Apps 5.3 Building Apps with AI (Vibe Experience)

6 Demonstrate the Capabilities of Power Automate (20-25%)

6.1 Cloud & Desktop Flows: Types & Use Cases 6.2 Building Flows: Triggers, Actions & AI Assistance 6.3 Automating Microsoft 365 & Document Processes

7 Agents in Microsoft Copilot Studio (20-25%)

7.1 Building Agents: Topics, Knowledge, Tools (MCP, Agent Flows), Publishing 7.2 Managing Agents: Microsoft Agent 365, Monitoring & Evaluations

4.1 Environments & Their Purposes

Key Takeaways Explain This Topic AI

An environment is a container that separates and secures apps, flows, connections, and data, permanently tied to a Microsoft Entra ID tenant and a geographic region

The five core environment types are Default, Production, Sandbox, Trial, and Developer, each with a distinct purpose and lifecycle

Not every environment has a Dataverse database; environments without one can still host canvas apps and flows that use connectors

The Power Platform admin center is used to create, back up/restore, copy, restrict access to, and delete environments

Organizations use multiple environments to isolate testing from production, scope data to the right audience, and support a controlled release process

Last updated: July 2026

Before a maker builds a single app or automates a single process, they need somewhere to build it. That "somewhere" is an environment — and the PL-900 exam expects you to know what an environment is, which types exist, and how administrators use them to keep an organization's apps, data, and flows organized and secure.

What Is an Environment?

An environment is a container that separates and secures apps, flows, connections, and data (including a Dataverse database, if one is provisioned) from other environments in the same tenant. Every environment is tied to two things that never change after creation:

A Microsoft Entra ID tenant — the identity boundary for the organization

A geographic region — the physical location where the environment's data is stored, which affects data residency, compliance, and network latency for users in that region

An environment may also be tied to a Dataverse database . Not every environment has one: a lightweight environment with no Dataverse database can still host canvas apps and cloud flows that connect directly to external data sources through connectors, but it cannot host model-driven apps, custom tables, or anything that depends on Dataverse's relational data model and built-in security roles.

The Five Core Environment Types

The exam blueprint expects you to distinguish between the standard environment types available in the Power Platform admin center:

Type Purpose Dataverse Database Notes

Default Automatically provisioned when the Microsoft 365/Power Platform tenant is created Yes One per tenant; every licensed user is automatically an environment maker here; not recommended for building or storing production solutions because it lacks isolation and governance controls

Production Hosts live, business-critical apps, flows, and agents used by real users Optional (recommended) The destination for solutions once they are tested and approved

Sandbox Non-production space for development, testing, and experimentation Optional Can be reset to a clean state, copied to or from another environment, and later converted to a Production environment

Trial Time-limited environment for evaluating the platform or a specific scenario Optional Automatically provisioned with a Dataverse database and sample content; expires if not converted before the trial period ends

Developer A free, personal environment for an individual maker to build and test solutions Yes (one database) Created through the Power Apps Developer Plan; tied to a single user's account rather than shared across a team

A well-run tenant typically has one Default environment (largely left alone), one or more Sandbox environments for building and testing, and one or more Production environments where finished solutions actually run.

Managing Environments

Environments are created, configured, and monitored from the Power Platform admin center , the central console for Power Platform Administrators and Environment Admins. From there, an admin can:

Create a new environment and choose its type, region, and whether to provision a Dataverse database
Back up and restore an environment's Dataverse database to a point in time

Copy an environment's contents (a full or minimal copy) into another environment, most often to refresh a Sandbox with recent Production data for testing

Restrict access to an environment using a Microsoft Entra security group, so only intended users and makers can see or use it

Delete environments that are no longer needed, freeing the capacity they consumed

Every tenant has a finite pool of capacity — database storage, file storage, and log storage — measured in the admin center's Capacity/Analytics area. Each environment with a Dataverse database draws from this shared tenant capacity, so administrators monitor consumption to avoid hitting limits that would block new environment creation or data growth.

Choosing an Environment Strategy

A core administration skill tested on PL-900 is knowing why organizations use multiple environments rather than building everything in one place. Separating environments by purpose and, often, by department or business unit accomplishes several goals at once:

Isolation — a bug introduced while testing in Sandbox cannot affect the live data or apps running in Production

Security — sensitive data (for example, HR or finance) can live in an environment restricted to only the users who need it, rather than being visible to every maker in the tenant

Governance — administrators can apply different Data Loss Prevention policies, different security models, and different monitoring to each environment based on its purpose

Lifecycle management — solutions move deliberately from Development to Test to Production environments as part of a controlled release process, rather than being edited directly by users

Example: A maker builds and unit-tests a new expense-approval app inside a Sandbox environment. Once it passes review, the underlying solution is exported and imported into the Production environment where employees actually use it — the Sandbox copy remains available for the next round of changes.

Understanding this flow — that environments are the foundation everything else (security, DLP policies, ALM pipelines) is layered on top of — is essential context for the rest of this chapter.