Managed Environments: The Premium license is now visible in the app
A Managed Environment applies a licensing rule to the entire environment, not just its creators—a fact that is now indicated within the application itself. The compliance timeline, the report showing who is affected, and how this impacts architectural decisions.
Enabling a Managed Environment provides access to a suite of premium features—among the twenty or so documented by Microsoft—including sharing controls, data policies, and weekly usage insights. However, a licensing rule applies to the entire environment, not just to creators.
This rule is not new. What has changed is how it is communicated: Microsoft set the start date for in-app notifications for June 2026, and as of August 27, 2026, the process is still ongoing. Since this change took effect, users without the appropriate license have been seeing a notification within the app itself.
The rule, as it is written
As soon as an environment is marked as managed, any active use requires a standalone license or a pay-as-you-go meter. This applies not only to developers but to everyone who opens an application.
In practical terms:
- Every user who runs an application in a Managed Environment must have a Power Apps Premium license, a Power Automate Premium license, or an Dynamics 365Power Apps Premium.
- Every user who runs a flow cloud Power Automate in a Managed Environment is subject to the same requirement.
- A single user who does both does not need both licenses: either one satisfies the requirement.
For capacity-based licenses, the environment must be assigned Power Apps plans per application, or a Power Automate plan per stream for the automation component.
Managed Environments are included as a usage entitlement in Power Apps Premium, Power Automate Premium, Microsoft Copilot Studio, and Copilot Studio for Microsoft 365 Copilot (for its Copilot Studio features only), Power Pages, Dynamics 365 Premium, Enterprise, Team Members, and Customer Insights. The pay-as-you-go counters for Power Apps by application, Power Pages , and Copilot Studio also qualify—however, the Power Apps counter per application only covers usage of Power Apps : Power Automate feeds require standalone Power Automate licenses or per-feed plans.
There are two exceptions to keep in mind. Trial licenses do cover users, but they are subject to specific restrictions, including a 30-day time limit. And the Developer Plan does not include the right to use Managed Environments when users run their own resources there.
The Compliance Timeline
| Date | What's happening |
|---|---|
| March 2026 | Administrators receive a notification via the message center Microsoft 365. |
| After April 2026 | Recommendations appear in the admin center at Power Platform, under Actions > Recommendations. |
| June 2026 | Trigger set for in-app notifications, effective August 27, 2026. |
The user-side notification goes through three states, each of which advances to the next after seven days if nothing changes: information, warning, then error. The first two display “This application requires a valid Power Apps license. Request a license from your administrator.”; the third, reached after fourteen days, displays “Action required: This application requires a valid Power Apps license. Request a license from your administrator for continued access.” and remains displayed until an appropriate license is assigned.
Users can request a license directly from the notification. The request is sent to the administrator in the Administration Center at Power Platform under Actions > Recommendations, or in the Administration Center Microsoft 365 under Billing > Licenses > Requests.
The report that provides the answer
A dedicated report provides a list of these by name, in addition to the recommendations from the Administration Center. In the Administration Center Power Platform : Licenses, then Power Apps, the Summary tab, Download Report, and select the usage type “Users requiring licenses in Managed Environments.”
Three points to keep in mind when reading this, to avoid drawing the wrong conclusions:
- The report lists users who launched at least one application in a Managed Environment without the appropriate license during the selected month.
- It excludes users who did not open any apps that month. A user who meets the criteria but was not active that month will not appear.
- A user who has just been assigned a license remains on the list until they relaunch an application.
In other words, the report measures activity, not population. A park that is used seasonally requires a comparison across several months.
How This Affects Architectural Decisions
The key question isn't "Should we activate Managed Environments?", but "Which user group will the activation upgrade to a premium license?"
A Canvas application running in the context of Microsoft 365, using standard connectors and without Dataverse, accessed by 200 users covered by their licenses Microsoft 365, costs nothing today. The same application in a Managed Environment requires coverage for those two hundred users: a premium license per person, application-specific plans allocated to the environment, or a pay-as-you-go meter.
Two practical consequences:
The division of environments becomes a budgetary decision. Consolidating all applications into a single managed environment brings all users within the scope of the rule. The scope of the rule is determined by activation, environment by environment: only environments that have been activated as managed are affected.
Automatic allocation is available. The administration center’s automatic claim strategy Microsoft 365 assigns a license to active users, provided there is available capacity in the tenant. It eliminates the need for manual catch-up once the cost has been approved in advance.
Our take. For a park that’s used only occasionally, the app-based plans allocated to the environment often cost less than a per-person license—this is a question that needs to be addressed before activation, not after the first month of notifications. Here’s something you can check on your own, without waiting for a project: download the three-month report to gauge how many people would actually switch to a premium license before making a budget decision.
These trade-offs between governance, scope, and licensing arise as soon as a Power Platform deployment includes more than a few applications; our page Power Apps provides some background, and our article on the true cost of a Power Apps application details the cost of premium licenses.
Microsoft Sources
- Licenses — Managed Environments — Microsoft Learn
- Overview of Managed Environments — Microsoft Learn
- View License Usage (Preview) — Microsoft Learn
- Microsoft Power Platform Licensing Guide — Microsoft
What an article Can't Know
An article describes what applies to everyone. What varies from one organization to another is the inventory: which applications, which accounts, and which pieces of equipment are actually involved in your organization. The inventory determines the scope of the effort, and it cannot be summarized on a single page.
You'll be speaking directly with the engineers who will be doing the work, not with a middleman. We'll respond within 24 business hours.
Check what is still true
Announced dates are sometimes postponed, products are renamed, and conditions change. The blog tracks these topics over time: when a rule changes, a new post announces it.
Search for a topic in the blogIn the same issue
Three articles on the same topic. The blog has 149 articles, all of which are freely accessible.