Power Apps Per App Per User License

(1) Share

Report

Posted on by luisoscarmtz

I have a power app that im trying to use with premium features, my organization bought 11 licenses to do some test before the release of the app, to test these we applied only 1 per app license to the environment but somehow more than 1 user can access the app

We get rid of the trial license of every user and they are still capable of using the app.

I wanna know how these per app license work, cause in documentation it says you need 1 license per user but in the practice it isn't working as intended.

PD: Some of the users that are trying to use the app have these Dynamics365 license that seems to include power apps.

Categories:

Governance & administering

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

MichaelFP 1,847 Super User 2025 Season 2 on at

Like (0)

Report

Dynamics 365 bring together the Power Apps capability, so link this license to the user it will be able to access the application. But of course you can control access by sharing the application and apply specific roles.

If your application is for Teams, so the users will be able to use because of license "Power Apps for Office 365".

The license "Power Apps Community" is the license that you received direct to your user because you create an environment for your self. I don't think that your user had this license. Announcing the PowerApps Community Plan - Microsoft Power Platform Blog

For more information you can take a look on the license guide. Licensing overview for Microsoft Power Platform - Power Platform | Microsoft Learn

Was this reply helpful? Yes No
Suggested answer

Vijay Tailor 2,961 on at

Like (0)

Report

Hi,
The issue is that the connection reference, not in the Environment Variable.
This could be because you don't have the necessary access or aren't the owner of the flows.
As a result, when deploying the solution to production, a new connection is required to manage it.
As a best practice, we always follow using a Service Principal Account for both deployment and development. This ensures that the same connection reference can be used in the target environment during any deployment.

Hope this help to resolve the issue.

Thanks
Vijay

Was this reply helpful? Yes No