Unanswered

Power Apps licensing access issue in Production environment

(0) Share

Report

Posted on by AndersonR12

Hello everyone,

I am facing a confusing scenario related to Power Apps licensing and user access, and I would like some guidance on what might have happened.

Context

I developed a Power Apps application and published it to the Production environment.
The app was properly shared with users in the company for regular use.
Initially, all users were able to access the app without any issues.

Identified issue

After some time, some users started reporting that they could no longer access the app. Instead, they were presented with a message indicating that they needed to acquire a license.

Important details:

Not all users were affected, only a subset.
Other users continued to access the app normally.

Additional situation that increased the confusion

At the same time:

Another developer built a second Power Apps application, for a different purpose.
This second app was:
- Also published to the Production environment
- Shared with the same group of users
Initially, there were no access or licensing issues with this second app.

However:

Later on, some users started reporting access/licensing issues with both apps
Again, not all users, only some of them.

Summary of the scenario

Different apps
Different developers
Same environment (Production)
Same users
Licensing issue occurs intermittently and selectively, not for all users

Questions

What could cause this type of inconsistent licensing-related behavior?
Could this be related to:
- Use of standard vs. premium connectors?
- Changes made to the apps after publishing?
- Tenant-level licensing or policy changes?
- Differences in user license assignments or security profiles?

Is there a recommended way to diagnose or audit the root cause when only some users are impacted?

Both apps are currently published in Production, and as far as we know, there were no intentional changes to user sharing or permissions for the affected users.

Any insights or recommendations would be greatly appreciated.

Thank you!

Categories:

Building Power Apps

I have the same question (0)

All responses (7)

Answers (0)

WarrenBelz 154,777 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @AR-24031644-0,

I am going to take an initial guess that either the App or a Flow connected to it uses a Premium connector and a set of users do not have Premium licences.

So before we go any further does the App or any flows require Premium connectors ? Also if so, are any premium licences you have per user or per app ?

Was this reply helpful? Yes No
AndersonR12 6 on at

Like (0)

Report
Copy link

Link copied!
Hi @WarrenBelz.

I checked that too.

Both apps use the same types of connectors
Both applications (mine and the other developer’s app) rely only on standard connectors. No Premium connectors are used in either app.

No Power Automate flows use Premium connectors
Any flows associated with the apps also use standard connectors only. There are no per‑user, per‑flow, or per‑app Premium licenses involved.

The affected users were able to access the app previously
Users who are now seeing the license requirement message had accessed and used the app successfully before. If a Premium license were required, the error would have occurred from the first access.

The issue does not affect all users
Some users can access the apps without any issue, while others receive a license prompt. Premium licensing issues are deterministic and would consistently affect all users without the required license.

Both apps are published in the same Production environment
There is no difference in environment (DEV vs PROD) or environment-level licensing policies between the apps.

The issue later appeared in the second app as well
Initially, only my app showed the issue. Later, some users also experienced the same problem when accessing the other developer’s app, which indicates the problem is not app‑specific.

No recent license changes were made for affected users
There were no known removals, expirations, or plan changes in Microsoft 365 or Power Apps licenses for these users.

Was this reply helpful? Yes No
11manish 769 on at

Like (0)

Report
Copy link

Link copied!

This sounds like a classic transition from Standard to Premium features, which often triggers "grace periods" where things work temporarily before the system enforces a license check.

Was this reply helpful? Yes No
AndersonR12 6 on at

Like (0)

Report
Copy link

Link copied!

Hi @11manish

I understand, and that explanation does make sense. However, I am still a bit unsure, because there was no request or intentional change to migrate the app from standard to premium features. Could this behavior still occur even without such a transition?

Was this reply helpful? Yes No
WarrenBelz 154,777 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @AndersonR12,

I should have asked this specifically before - what are you using as a Data Source ? If SharePoint, then are you using the same List/s in Development and Production or different ones ? If different, have you checked the sharing on both. If Dataverse, then that requires a Premium Connector and I suspect that the users had trial licences that have expired. What licenses do to users have ?

Was this reply helpful? Yes No
AndersonR12 6 on at

Like (0)

Report
Copy link

Link copied!

Hi @WarrenBelz

In our case, the data source used by the app is SharePoint. The same SharePoint lists are used in both Development and Production environments.

We are not using Power Apps Solutions, so the app is not linked to Dataverse and there are no Dataverse tables involved. The app only uses standard connectors, such as SharePoint, Office 365 Users, and Office 365 Outlook.

Sharing and permissions are managed directly in SharePoint, using groups, with permissions inherited from the parent site and lists. All sharing settings and permissions have been reviewed and are correctly configured.

User licenses are standard Microsoft 365 licenses, and no Power Apps Premium licenses were explicitly assigned.

An important detail is that the license prompt appears immediately when the app is opened, before any screen loads and before any App.OnStart logic runs.

Exemple:

Region: Brazil - Pt-br

The same users who cannot access this app are able to access another Power Apps application developed by a different developer, in the same tenant and environment, also using SharePoint as the data source.

Given this scenario, we are trying to understand what could cause this behavior and what else should be verified.

Was this reply helpful? Yes No
WarrenBelz 154,777 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @AndersonR12,

I did not get a notification on your response (you sometimes need to tag me), however your latest post indicates an App sharing issue (not a data source sharing problem). For the purpose of posting the message in English

Start a Power Apps trial?*
You don't have a current Power Apps plan. Ask your administrator for one or start a free trial.

Start a free trial

So just for a debugging test, try sharing the app directly with one of the affected user (not via a Group).

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥
Visit my blog Practical Power Apps LinkedIn

Was this reply helpful? Yes No