Unmanaged vs Managed Environments vs Routing 🗂️

Not to be confused with managed vs unmanaged solutions, that’s about how you package and ship components. This page is about Managed Environments, a governance layer you switch on for an entire environment, and Environment Routing, the feature that automatically gives every maker their own Managed developer environment instead of dumping them into Default.

TL;DR: A plain (unmanaged) environment costs nothing beyond whatever the app itself needs. Turning on Managed Environments adds real governance (sharing limits, backup, DLP, usage insights) but also means every active user needs a qualifying premium license, even for a standard-connector-only app, and Microsoft starts strictly enforcing that from February 2027. Environment Routing builds on top of Managed Environments: it auto-creates a personal, Managed developer environment for each maker. Building and previewing there stays free; only running an app or flow there needs a license.

The three states at a glance

	Unmanaged	Managed	Managed + Routing
Governance	None	Sharing limits, backup, DLP	Same, per maker automatically
Needs a license	Only premium apps	Every active user	Every user who runs an asset
Makers land in	Default / assigned env	Wherever it’s enabled	Their own personal Dev env
Setup	None	Enable per environment	One tenant-wide setting

Unmanaged (plain) environments

🔸 This is the default state of any environment (Default, Production, Sandbox, Developer) before you touch the Managed Environments toggle. No sharing limits, no enforced backup policy, no admin-defined data policies beyond whatever the tenant already sets globally.

🔸 Licensing follows the app, not the environment: a canvas app that only uses standard connectors can run on seeded Microsoft 365 rights, and a Dataverse or premium-connector app needs Power Apps/Automate Premium for its users, exactly as described on Power Apps app types and connectors.

Managed Environments: what you actually get, and what it costs

🔸 Managed Environments is a suite of governance capabilities you enable on any existing environment: sharing limits, weekly usage insights, data policies, Pipelines, the Solution Checker, maker welcome content, an IP firewall, Customer Managed Key, Lockbox, and extended backup retention (for example 7 to 28 days on Production).

🔸 The licensing consequence is the part people miss. Per Microsoft’s own FAQ: once Managed Environments is active, every user running anything there needs a qualifying license, a Power Apps Premium, Power Automate Premium, Copilot Studio, Power Pages or qualifying Dynamics 365 license, or the matching pay-as-you-go meter. This applies to standard-connector-only apps too, because the requirement is tied to activity in the environment, not to what the app uses.

🔸 One license covers both: a user running an app and triggering a Power Automate flow in the same Managed environment doesn’t need separate Power Apps and Power Automate licenses, either one satisfies the requirement.

🔸 Trial licenses count, but only for their normal 30-day window.

flowchart TD
    A["An environment"] --> B{"Need governance:<br/>sharing limits, backup, DLP, insights?"}
    B -->|"No"| C["Leave it Unmanaged<br/>licensing follows the app only"]
    B -->|"Yes"| D["Enable Managed Environments"]
    D --> E["Every active user now needs<br/>a qualifying premium license"]

Environment Routing: Managed developer environments without the chaos

🔸 Environment Routing is a tenant-level setting that automatically sends a maker who has no assigned environment into their own personal Developer environment the moment they open Power Apps, Power Automate, or Copilot Studio, instead of landing in Default. Makers don’t pick anything, it happens for them.

🔸 Every environment routing creates is a Developer environment, and by default it’s Managed, preconfigured with sharing limited to 5 individuals, Solution Checker set to warn, and usage insights on.

🔸 Multi-rule routing lets admins route different security groups to different environment groups, so, for example, one team’s makers land under stricter governance than another’s.

🔸 The Default environment itself doesn’t need to be Managed for routing to work, and routing has no effect on developer environments a maker already created that aren’t Managed.

flowchart TD
    A["Maker opens Power Apps / Automate / Copilot Studio"] --> B{"Environment Routing on,<br/>and a rule matches?"}
    B -->|"No"| C["Lands in the Default environment"]
    B -->|"Yes, owns a Dev environment already"| D["Routed to their own Dev environment"]
    B -->|"Yes, no Dev environment yet"| E["A new Managed Dev environment<br/>is created for them"]

The distinction that explains the confusion: build vs run

🔸 Microsoft draws a specific line here: a premium license isn’t required to create or preview an app or flow in a Managed developer environment. A premium license is required to actually run one there.

🔸 That’s why building, testing and previewing inside a Managed developer environment routinely works without hitting a license wall, while formally the Developer Plan still doesn’t include Managed Environment entitlement for running assets. Both things are true at once: the build/preview path is genuinely free, the run path technically isn’t, whether or not that gets enforced yet depends on the environment and the date below.

The February 2027 enforcement deadline

🔸 This isn’t a new rule taking effect, it’s an existing rule Microsoft is now actively enforcing. In-app end-user notifications started June 2026 (informational, then warning, then an error state after repeated 7-day windows), admin notifications in the Power Platform admin center and Microsoft 365 Message center started March 2026.

🔸 Starting February 2027, a user without an appropriate license is actually blocked from opening an app in a Managed environment (“You need a Power Apps license to use this app”). The app itself isn’t removed, and access resumes the moment a license is assigned.

🔸 Use the Users requiring licenses in Managed Environments report (Power Platform admin center → Licensing → Power Apps → Download report) now to see exactly who’s affected before the deadline, rather than finding out from a support ticket in 2027.

⚠️ Watch out

🔸 Don’t enable Managed Environments on Production expecting it to be “just governance”. Budget premium licenses for every active user first.

🔸 Environment Routing’s free ride only covers building and previewing. The moment someone runs the published app or flow in that Managed developer environment, licensing applies.

🔸 A Managed developer environment still isn’t a substitute for Production. It’s for one maker’s build/test, not for sharing a finished solution with a team.

🛠️ FAQ

Does turning on Managed Environments force standard-connector apps to need a premium license too? Yes. Microsoft’s licensing FAQ is explicit that the requirement is tied to active usage in the environment, not to whether the app uses premium capabilities.

If Environment Routing makes my Dev environment Managed automatically, do I need to pay for anything to build there? No, not to build or preview. You only need a premium license the moment you (or anyone else) actually runs an app or flow in that environment.

Does the Default environment need to be Managed for Environment Routing to work? No, they’re independent settings.

What happens if I don’t assign licenses before February 2027? Affected users simply can’t open the app anymore until they get an appropriate license. Nothing about the app or its data is deleted.

🔗 Related

🔸 Power Platform Environment Types, Default, Production, Sandbox, Developer and Trial explained.

🔸 Managed vs Unmanaged Solutions, the ALM packaging concept this page isn’t about.

🔸 Power Apps app types, what actually makes an app premium in the first place.

🔸 All Dataverse tips · Knowledge base overview

Details reflect Microsoft Learn at time of writing, including the managed environments licensing and environment routing documentation. Always confirm current behavior and enforcement dates in the Microsoft Power Platform documentation.