"This app requires a valid Power Apps license": what to do by 2027

You open a Power Apps app and a notice says: "This app requires a valid Power Apps license. Request a license from your admin." The notice means the app lives in a managed environment, where Microsoft requires every person who runs an app to have a qualifying licence, and your account doesn't have one. After 7 days the notice moves to a warning, and 7 days after that to an error. Starting February 2027, a person who has had the final notice can't open the app until a qualifying licence is detected. The fix is a licence, requested by the user and assigned by an admin.

• A notice in a Power Apps app says it needs a valid Power Apps licence and asks you to request one from your admin.
• Later the notice starts with "Action required" and says you need the licence for continued access.
• It appears in some environments but not others, or for some colleagues but not others.
• It appears even on a simple app that uses only SharePoint or other standard connectors.

Why the app says it needs a licence

The rule isn't new; the notices are. Microsoft's page on licensing for managed environments says that once an environment is made a managed environment, all active use in it needs a standalone licence or a pay-as-you-go meter. For apps, that means every person who runs one needs a qualifying licence.

Three points catch people out:

• Standard apps count. Learn says every user who runs an app in a managed environment is in scope, including users of standard apps. The rule follows the environment, not the type of app. Microsoft 365 licences aren't among the licences Learn lists as including managed environments.
• Only managed environments are in scope. Learn says only environments you enable as managed environments are in scope, which is why the notice can appear in one environment and not in another.
• The Developer Plan doesn't count. Learn says a managed environment isn't included in the Developer Plan when people run their assets.

The three notices and the February 2027 block

Microsoft has been warning admins since March 2026, through the Microsoft 365 Message center and recommendations in the Power Platform admin center. People using apps without a licence started seeing in-app notices in June 2026. Each person's notice moves through three stages:

Starting February 2027, a person without a qualifying licence can't open apps in a managed environment once they've had the final notice. They see Power Apps' standard message, "You need a Power Apps license to use this app". Microsoft says the apps aren't removed from the environment, and access comes back once a qualifying licence is detected. Both kinds of notice carry on after February 2027.

1. Step 1March 2026: admins notified
2. Step 2June 2026: in-app notices begin
3. Step 3Informational notice
4. Step 4Warning 7 days later
5. Step 5Error 7 days after that
6. Step 6February 2027: no licence, no app

If you use the app

1. Request a licence from the notice. Learn says the notice lets you request one directly, and the request goes to your tenant's administrator.
2. Wait for the answer. Microsoft's page on requesting a Power Apps licence says a banner confirms the request was sent, that your admin might take a few days to respond, and that you get an email saying whether it was approved.
3. Know the date. Learn calls the time before February 2027 a courtesy notification period, and says that starting February 2027 a licence is strictly required to open an app in a managed environment. If you're on a Power Apps trial, Learn says you can keep using the trial while you wait for your request to be approved.

If you're the admin

Learn says blocking starts in February 2027, for people who have had the final notice. Microsoft's own advice is to review your users and assign licences before then.

Answer the requests

Learn names two places where requests from the notice show up:

• Power Platform admin center: Actions > Recommendations. The recommendations also list users in managed environments who need a licence.
• Microsoft 365 admin center: Billing > Licenses, on the Requests tab.

On the Requests tab, select a request, choose which users to approve, pick the product to assign, and submit. Users get an email with the decision. Microsoft's page for this needs you to be at least a User Administrator or License Administrator, and it says requests are kept for 12 months. That page is written for self-service purchase requests; Learn's page on requesting a Power Apps licence links to it for how admins respond.

Find everyone who needs a licence

Don't rely on requests alone. Microsoft provides a report of the people this notice is about. These steps are from Learn's page on licensing for managed environments; the licence consumption page describes the button as Download Reports near the top of the page, so the label may differ in your admin center:

1. Sign in to the Power Platform admin center.
2. In the navigation pane, select Licensing, then Power Apps.
3. On the Summary tab, select Download report.
4. From the Usage type list, choose Users requiring licenses in Managed Environments, pick the month from the Lookback window list, and select Download report.

What the report shows, per Microsoft's documentation:

• each person who opened at least one app in any managed environment without a qualifying licence, with the environments and apps they used;
• only people who launched an app in the month you chose;
• people you've since licensed, until they next open an app. So a name that's still listed after you assigned a licence isn't necessarily a problem.

The licence consumption pages are labelled a preview.

Let licences assign themselves

An auto-claim policy gives a person a Power Apps per user licence automatically when they open an app in a managed environment without one, as long as the tenant has a licence available.

• You may already have one. Learn says that since December 2023, tenants with managed environments get a policy called Auto-Created Policy for Power Apps in the Microsoft 365 admin center. Admins can turn it off or delete it, so check it's still on, under Billing > Licenses on the Auto-claim policy tab.
• It needs spare licences. Learn says the policy assigns a licence only if one is available in your tenant, and the licensing page for managed environments says to make sure you have enough licence capacity.
• Choose its reach. Learn's steps: in the Power Platform admin center, go to Settings, select Auto-claim policies, and choose All Environments or Only Managed Environments. That page was last revised in February 2025, so check the labels in your admin center.
• Group-based option. A policy can add people to a security group that carries the licence instead. Learn says that route can take up to 24 hours to assign the licence.
• Not in US government clouds. Auto-claim policies aren't supported in GCC, GCC High or DoD.

Learn's pages differ on who can manage the policies. The Power Platform page on auto-claim policies says you need global admin privileges to create and manage them. The Microsoft 365 page says you must be a Global Administrator to manage auto-claim policies at the organization level, and that User, License and Global admins can create and manage them on the Auto-claim policy tab under Licenses.

Pick a licence that counts

For apps in a managed environment, Microsoft's page lists:

Microsoft points to the Microsoft Power Platform Licensing Guide for the complete, current list. Our Power Apps licensing explained guide compares Premium with the per app meter.

Edge cases worth checking

• Developer environments. Learn says unmanaged developer environments are deprecated, and that to keep one you must make it a managed environment before 15 December 2026. Once it's managed, the Developer Plan doesn't cover running apps there. Our Developer Plan deadline guide covers the choices.
• Cloud flows. Someone who runs a cloud flow in a managed environment needs a qualifying licence too. Learn says one Premium licence, Power Apps or Power Automate, covers both, and that flows triggered from within apps are covered by the Power Apps licence.
• Other checks from February 2027. Learn's Power Apps licensing FAQ lists two more areas, besides managed environments, where users need an appropriate premium licence starting February 2027: model-driven apps, and apps used outside a Dynamics 365 environment context. Its wording is "including but not limited to", so the list may not be complete.
• A trial that just ended. Microsoft's FAQ says access can carry on for up to two hours after a trial expires, and caching may need an extra refresh before it stops.

For the bigger picture across products, see our Power Platform licensing map. Our Power Platform admin interview questions cover managed environments more widely.

The steps follow Microsoft's documentation as of 27 October 2026. We haven't seen the notices in a tenant ourselves, so check the labels against your own admin centers.

Sources

• Licensing requirements for managed environments — Microsoft Learn
• Request a Power Apps license for yourself — Microsoft Learn
• View license consumption for Power Apps (preview) — Microsoft Learn
• Manage self-service license requests in the Microsoft 365 admin center — Microsoft Learn
• Auto-claim policies for Power Apps licenses — Microsoft Learn
• Manage auto-claim policies in the Microsoft 365 admin center — Microsoft Learn
• Managed environments overview — Microsoft Learn
• Power Apps licensing FAQs: licensing compliance — Microsoft Learn
• Deprecation of unmanaged developer environments and the Power Apps Developer Plan — Microsoft Learn