3.1 Recommending Environment Types

Environments: The Boundary Every Decision Starts With

In Microsoft Power Platform, an environment is a container that stores, manages, and shares your organization's business data, apps, agents, and flows. Every governance decision on the AB-410 exam — data policies, security roles, capacity, backups — attaches to an environment, so recommending the right environment type is a foundational skill for an Intelligent Applications Builder. Environments are created and managed in the Power Platform admin center (admin.powerplatform.microsoft.com) under Manage > Environments, or programmatically with PowerShell.

The Default Environment

Every tenant has exactly one default environment, created automatically, and it cannot be deleted. Key facts the exam loves:

• Every user with a Power Platform license is automatically a maker in the default environment — you cannot remove them from it.
• New makers land in the default environment unless environment routing redirects them elsewhere.
• The default environment can be renamed, and Microsoft Dataverse can be added to it — but once added, Dataverse cannot be removed.
• You cannot create manual backups of the default environment.

Because everyone is a maker there, treat the default environment as the home for personal productivity apps built on Microsoft 365 data — not for business-critical intelligent applications.

Production and Sandbox Environments

A production environment hosts live, business-critical workloads. Creating one requires at least 1 GB of available Dataverse database capacity in the tenant, and running premium apps in it requires premium licenses for users.

A sandbox environment is a non-production copy used for development and testing. Sandboxes support two admin operations that production environments do not:

• Copy — duplicate an environment. A full copy includes the data; a minimal copy brings over customizations and schema only, with no records.
• Reset — deletes and reprovisions the environment, permanently removing its apps and data.

Sandboxes can also be placed in administration mode, restricting access to users with admin roles while you perform maintenance.

Developer Environments

A developer environment is a personal, single-user workspace provisioned through the free Power Apps Developer Plan. Concrete limits to memorize: 750 flow runs per month and 2 GB of Dataverse database capacity, and each user can have up to three developer environments. Developer environments never expire, do not consume tenant capacity, and — critically — are licensed for development and testing only, never production use.

Trial Environments

A trial environment lets an organization evaluate premium features, including Dynamics 365 apps, for 30 days. It can be converted to a production environment before it expires; otherwise it is disabled and eventually deleted. Exam trap: trial environments are not backed up — every other environment type with a database receives automatic system backups.

Dataverse for Teams Environments

A Dataverse for Teams environment is created automatically the first time someone builds an app or agent inside a Microsoft Teams team — one environment per team, with roughly 2 GB of storage. It supports standard connectors and apps embedded in Teams, and it offers a documented upgrade path to a full Dataverse production environment when a solution outgrows the Teams boundary.

Managed Environments: The Premium Governance Layer

Any environment type — production, sandbox, developer, even the default — can be converted to a managed environment in the Power Platform admin center (select the environment, then Enable Managed Environments). Managed environments unlock premium governance features, including:

• Limit sharing — cap how broadly makers share canvas apps and agents
• Usage insights — a weekly digest email to admins with top apps, active makers, and unused resources
• Solution checker enforcement — block or warn when solutions with critical errors are imported
• Pipelines in Power Platform — built-in ALM automation (covered in section 3.2)
• IP firewall and customer-managed keys for data protection
• Extended backup retention — up to 28 days instead of the default 7
• Maker welcome content — a custom greeting with governance guidance shown to makers

Exam trap: enabling a managed environment has a licensing consequence — every active user of that environment needs a premium license (Power Apps Premium, Power Automate Premium, or a qualifying Dynamics 365 license). Running premium apps there with only Microsoft 365 licenses puts the environment out of compliance.

Environment Groups and Routing New Makers

Environment groups let admins organize environments into collections (for example, Personal Development, UAT, Production) and apply rules — such as sharing limits — to every environment in the group at once. Groups pair with environment routing, a premium governance setting that automatically sends new (or existing) makers to their own personal developer environment instead of the default environment when they visit make.powerapps.com or copilotstudio.microsoft.com. The personal environment is provisioned on demand inside the chosen group and inherits its rules. The classic exam scenario — 'stop new makers from building in the default environment' — maps directly to environment routing.

Recommend the Right Environment: Scenario Guide

Storage and Backup Basics

Environment storage is tracked on the Resources > Capacity page of the Power Platform admin center across three meters: database, file, and log. Capacity is pooled at the tenant level from purchased licenses; developer environments do not consume it.

For data protection, the platform automatically creates system backups of every environment that has a database — except trial environments. The default retention for system backups is 7 days; on a production managed environment, admins can extend retention to 7, 14, 21, or 28 days. Admins can also take manual backups before major customizations — supported on production and sandbox environments only, never the default environment. Restore is an environment-level operation: it returns the whole environment to a backup point, not individual records, so the exam expects you to treat backup and restore as an environment decision, not a data-editing tool.