Organizations using Microsoft Power Apps should be aware of an important Power Apps licensing enforcement change coming in February 2027.
Microsoft has confirmed that beginning in February 2027, users will need an appropriate qualifying license to open Power Apps running in a Managed Environment. Users who do not have an appropriate license will be blocked from opening the app until the licensing requirement is addressed.
While this may sound like a new licensing requirement, Microsoft has clarified that the licensing requirement itself is not new. What is changing is how strictly Microsoft will enforce it.
A Managed Environment in Power Platform provides enhanced governance and administrative controls for an organization’s environments.
When an environment is configured as a Managed Environment, Microsoft requires active users to have appropriate licensing. Importantly, this requirement is based on usage within the Managed Environment, not simply whether the individual app uses premium functionality. Microsoft specifically states that users running standard apps in Managed Environments are also subject to the licensing requirement.
Starting in February 2027, Microsoft will enforce that requirement when users attempt to open an app.
If a user does not have an appropriate license:
This means organizations could have business applications that work today but become inaccessible to some users once enforcement begins.
Not necessarily.
Power Apps Premium licensing is one way to satisfy the requirement, but it is not the only licensing option.
Depending on the use case, qualifying Power Apps licensing may include Power Apps Premium, Power Automate Premium, certain Dynamics 365 licenses with the appropriate Power Apps usage rights, capacity-based licensing or applicable pay-as-you-go options. Organizations should review the current Microsoft Power Platform Licensing Guide to determine which licensing approach applies to their specific users and solutions.
Do not assume that using only standard connectors automatically means an app’s users are covered. For apps operating within a Managed Environment, the environment itself introduces licensing requirements for active usage.
February 2027 may seem far away, but organizations should begin assessing their Power Platform footprint now to prevent potential access issues.
We recommend focusing on four areas:
Microsoft has already begun communicating about the upcoming enforcement. Administrative notifications began in March 2026, and in-app notifications for affected end users began in June 2026.
Organizations using Power Platform should use the time before February 2027 to understand their Power Apps licensing exposure and address gaps proactively.
A relatively simple review today can help prevent unexpected application access issues when stricter enforcement takes effect.
For Microsoft’s official guidance, see:
Get ahead of Power Apps licensing changes. See how Withum can help you assess your environment and prepare for February 2027.
When someone says, “just build it in Power Apps,” the next question should always be: which one? Power Apps isn’t a single tool. It’s four different app types, each built for a different audience, a different data scale and a different level of technical skill. Picking the wrong app costs real time and money. This guide helps you pick the right one before you start…
The Microsoft ecosystem has several admin portals: Microsoft 365 Admin Center, Azure Portal, Microsoft Entra (Azure AD), Intune and more. It is genuinely easy to get lost. The Power Platform Admin Center is its own dedicated space and understanding where it lives, who can access what is inside it and how it supports Power Platform…
In another recent blog post, we talk about how to access Microsoft 365 Defender and Microsoft Purview Compliance Portals (formerly Office 365 Security and Compliance Center) and a set of admin roles used for securing and governing tenant data. In this post, we will cover the various admin roles and responsibilities of Microsoft 365, including the impact…
