Power Platform Managed Environments are a suite of premium governance controls you switch on per environment, and they carry no separate license fee of their own. The real cost is a licensing obligation: once an environment is managed, every active user who launches an app or runs a flow in it must hold a qualifying premium license such as Power Apps Premium or Power Automate Premium, and starting February 2027 Microsoft will block unlicensed users from opening those apps. So the honest answer to "what do Managed Environments cost" is not a line item on the feature — it is the per-user license math across everyone who touches the environment.

This guide is written for the IT directors, Power Platform admins, and Center of Excellence leads deciding whether to turn Managed Environments on, which environments to put under governance first, and how to budget for the license true-up before the enforcement date lands. It covers what you get, exactly who needs a license, the current price points, and a decision framework for sequencing the rollout.

Key Takeaways

• Managed Environments have no standalone price. The capability is included as an entitlement in Power Apps Premium, Power Automate Premium, Copilot Studio, Power Pages, and qualifying Dynamics 365 licenses — there is no SKU to buy for the feature itself.
• One premium license per active user is the rule. Since the November 2024 licensing update, a single Power Apps Premium or Power Automate Premium license per active user satisfies compliance, even for standard apps and standard-connector flows.
• February 2027 is the hard deadline. Admin notifications began March 2026 and end-user in-app notifications began June 2026; from February 2027, users without an appropriate license are blocked from opening apps in managed environments.
• Only active users count, not everyone in the tenant. The obligation applies to users who launch an app or run a flow in a managed environment — not to dormant accounts or users who never open an asset there.
• The list price is $20 or $15 per user per month. Power Apps Premium is $20/user/month and Power Automate Premium is $15/user/month, both billed annually, with Power Apps Premium dropping to $12 at a 2,000-seat minimum.
• Capacity-based licenses are excluded from the simplified model. Pay-as-you-go meters and capacity SKUs follow their own rules; the "one premium license covers it" simplification applies to user-based licenses.

The short answer: what Managed Environments actually cost

Managed Environments is a governance layer, not a product you buy. Turning it on unlocks controls like sharing limits, weekly usage insights, data policies, and pipelines — and it simultaneously triggers a licensing requirement for the environment. There is no per-environment or per-feature charge.

The cost shows up in three places you need to budget for:

• Premium user licenses: Every active user in a managed environment needs Power Apps Premium ($20/user/month) or Power Automate Premium ($15/user/month), billed annually. This is the largest and most overlooked line item.
• The license true-up before February 2027: Many tenants have standard-connector apps running on seeded Microsoft 365 rights today. Once that environment is managed, those users need premium licenses, so the real cost is the gap between who is licensed now and who will need to be.
• Operational setup: No cash cost, but real effort — configuring sharing rules, data policies, pipelines, and usage insights, and running the discovery to find out who is actually active in each environment.

What do Managed Environments include?

Managed Environments bundle a set of premium administrative capabilities that let you govern Power Platform at scale. Per Microsoft, a managed environment encompasses — but isn't limited to — the following, drawn from the Managed environments overview.

• Governance controls: Environment groups, limit sharing, data policies, solution checker enforcement, and maker welcome content for onboarding.
• Visibility: Weekly usage insights, export of telemetry to Azure Application Insights, and license consumption reporting.
• Release management: Pipelines in Power Platform for application lifecycle management across environments.
• Security and network: IP firewall, IP cookie binding, customer-managed key (CMK), Lockbox, virtual network support, conditional access on individual apps, and data masking rules.
• Resilience and routing: Extended backup, data policies for desktop flows, and default environment routing that gives each maker their own developer environment instead of the shared Default.

Who needs a license in a managed environment?

This is where most budgets break. The requirement attaches to active usage, not to the type of app. Every user who runs an app or runs a cloud flow in a managed environment must have one of the qualifying licenses — even if the app only uses standard connectors. Dormant users and users who never open an asset in that environment are out of scope.

The pivotal simplification came at Microsoft Ignite in November 2024: a single premium license per active user is sufficient. Before that, there was genuine confusion about whether a user needed both a Power Apps and a Power Automate license. Microsoft clarified in its licensing update announcement that it does not intend to "double charge" — as long as every active user holds at least one qualifying premium license, managed environment features work and the organization is compliant.

What still requires a dedicated premium license

The single-license rule covers standard apps and standard flows. It does not relax the rules for genuinely premium workloads, which keep their own requirements regardless of environment.

Standard app or standard-connector flow

• Covers it: One Power Apps Premium or one Power Automate Premium license per active user.
• Note: A Power Apps Premium license alone can run a standard standalone flow in the environment.

Standalone flow with a premium connector (for example SQL or Dataverse)

• Covers it: Power Automate Premium is required when the flow is not triggered in the context of an app.
• Note: Power Apps Premium does not cover standalone premium-connector flows.

Desktop flow (RPA) or AI Builder in a flow

• Covers it: Power Automate Premium is required regardless of the user's Power Apps license.
• Note: Power Apps Premium does not cover desktop automation or AI Builder usage.

Premium Power App (Dataverse or premium connectors)

• Covers it: Power Apps Premium is required; a Power Automate Premium license alone does not grant access to premium apps.
• Note: Capacity-based pay-as-you-go meters follow separate rules and are excluded from the simplified model.

Managed Environments do not add a bill for the feature — they expose the bill you already owe for how your users actually work.

If you are staring at a tenant full of citizen-built apps and cannot say with confidence who is active in which environment, that discovery is the work. BabyBots runs fixed-fee Power Platform governance assessments that map active usage against license entitlements, model the February 2027 true-up cost, and sequence which environments to bring under management first — so the rollout lands as a planned budget line, not a surprise block. You can see how we approach where automation should live and how it is licensed in our companion guide.

What changes in February 2027, and what is the timeline?

Microsoft is rolling out managed environments licensing compliance in stages, moving from courtesy notifications to hard enforcement. The requirement itself is not new — what changes is that it becomes strictly enforced.

• March 2026 — administrator notifications: Admins began receiving alerts through the Microsoft 365 Message center and Power Platform admin center recommendations, flagging users who lack an appropriate license.
• June 2026 — end-user notifications: In-app notifications began for users running apps without a qualifying license, escalating through informational, warning, and error states roughly every 7 days.
• February 2027 — enforcement: Users without an appropriate license are blocked from opening apps in managed environments and see the standard "You need a Power Apps license to use this app" message. Apps are not deleted, and access resumes once a license is detected.

The practical takeaway: you have a defined window to run discovery and assign licenses before access is interrupted. Admins can use the Users requiring licenses in managed environments report in the Power Platform admin center to find exactly who needs coverage based on app-launch activity.

When should you turn Managed Environments on?

Turn them on when the governance value clears the licensing cost — which usually means the environment holds assets that matter, and its users are already (or should be) premium-licensed. Enable it where you need sharing limits, DLP, pipelines, backup, or usage visibility, and where you can account for every active user's license.

A practical sequencing framework:

1. Start with production environments that hold business-critical apps. These are where governance pays off most and where users are most likely already licensed.
2. Audit active users before you flip the switch. Run the discovery so you know the true-up cost per environment, not after notifications start reaching end users.
3. Weigh the Default environment carefully. It can be managed, but it is often full of standard-connector apps built by users on seeded M365 rights — managing it can create the largest surprise license bill. Consider default environment routing to move makers into their own governed developer environments instead.
4. Hold off on low-value sandboxes. If an environment has no sensitive data and no production load, the governance benefit may not justify licensing its occasional users.

Managed vs. unmanaged: what you trade

The decision is a straight trade between governance and licensing scope. The comparison below frames it the way an admin actually evaluates it.

Managed vs. unmanaged environment

Unmanaged environment

• Governance: Basic — no sharing limits, no built-in usage insights, no pipelines or maker onboarding controls.
• Licensing: Only the specific premium app or flow needs a premium license; standard-connector apps can run on seeded M365 rights.
• Best for: Low-risk sandboxes and personal productivity environments with no sensitive data.

Managed environment

• Governance: Full — sharing limits, data policies, usage insights, pipelines, backup, IP and network controls, and masking.
• Licensing: Every active user needs a qualifying premium license, enforced from February 2027.
• Best for: Production environments with business-critical apps, sensitive data, or regulatory exposure.

Frequently asked questions

Do Managed Environments cost extra?

There is no separate charge for the Managed Environments feature. The capability is included as an entitlement in premium licenses like Power Apps Premium, Power Automate Premium, Copilot Studio, Power Pages, and qualifying Dynamics 365 licenses. The cost is indirect: once an environment is managed, every active user in it must hold one of those premium licenses.

Does every user in the tenant need a premium license?

No. The requirement applies only to active users — those who launch an app or run a flow in a managed environment. Users who never open an asset in a managed environment, and dormant accounts, are not in scope. The license obligation follows activity, not headcount.

Does a user need both Power Apps and Power Automate Premium?

Not for standard workloads. Since November 2024, a single premium license per active user satisfies compliance for standard apps and standard-connector flows. You only need a dedicated Power Automate Premium license for specific premium scenarios such as standalone premium-connector flows, desktop flows (RPA), or AI Builder usage.

What happens in February 2027 if a user is unlicensed?

Starting February 2027, a user without an appropriate license is blocked from opening apps in a managed environment and sees the standard "You need a Power Apps license to use this app" message. The apps are not removed, and access resumes automatically once an appropriate license is assigned and detected.

How much is Power Apps Premium versus Power Automate Premium?

Power Apps Premium lists at $20 per user per month, billed annually, dropping to $12 per user per month at a 2,000-seat minimum. Power Automate Premium lists at $15 per user per month, billed annually. Either one satisfies the premium requirement for standard activity in a managed environment.

Can I manage the Default environment?

Yes, the Default environment can be managed. But it is usually the riskiest one to manage without planning, because it tends to hold many standard-connector apps built by users on seeded Microsoft 365 rights who are not premium-licensed. Default environment routing, which auto-creates governed developer environments for makers, is often a cleaner path than managing Default directly.

Where this is heading

Microsoft is steadily closing the gap between "governance is available" and "governance is expected." The February 2027 enforcement date signals a broader direction: as AI agents and Copilot-connected automations multiply inside tenants, Microsoft wants those assets inside governed environments with licensed, accountable users. Managed Environments are becoming the default control plane for serious Power Platform estates, not an optional add-on. The organizations that audit active usage and plan the license true-up now will treat February 2027 as a non-event; the ones that wait will treat it as a fire drill.

Plan your Managed Environments rollout with BabyBots

If you are weighing whether to turn Managed Environments on — or you know you need to and want the license math nailed down before February 2027 — book a BabyBots Power Platform governance assessment. In a single working session we map your active users against entitlements, model the true-up cost per environment, and give you a sequenced rollout plan. Start at babybots.ai and we will turn the enforcement deadline into a planned budget line instead of a surprise. For the cost side of the adjacent AI-agent decision, see our breakdown of what AI agents actually cost in Microsoft 365.

Sources

• Microsoft Learn — Licensing requirements for managed environments
• Microsoft Learn — Managed environments overview
• Microsoft Power Platform Blog — Announcing updates to managed environments licensing (November 19, 2024)
• Microsoft Learn — Limit sharing in managed environments
• Microsoft — Power Apps licensing and pricing
• Microsoft — Power Automate pricing