Power Apps per app plan allows organizations to get started with the platform at a lower entry point.

Customers on the per app plan typically start with 1-2 leading use case scenarios, i.e., Mekorma PowerApprovals, before adopting the platform more broadly. Power Apps per app plan is also an attractive licensing option to license end users that run only a few apps.

Power Apps per app plan allows individual users to run 2 custom applications (be it canvas or model or both) and access 1 custom portal based on the full capabilities of Power Apps.

Entitlement Summary for Power Apps per app license

Plans and capabilities Power Apps per app plan
Run custom apps / portals Run custom apps (both canvas and model driven) 2 apps
Access custom portals 1 custom portal
Connect to your data Standard connectors +
Premium connectors +
On-premises data gateway +
Custom connectors +
Store and manage data Utilize Common Data Service +
Create and access custom entities (includes complex entities) +
Dynamics 365 restricted entities access Read Only
Execute flows Power Automate Use Rights Within app context
Classic Common Data Service non real-time and real-time workflows +
Per license capacity Common Data Service Database Capacity 50 MB
Common Data Service File Capacity 400 MB
Daily API request limit 1000 requests
Infuse AI AI Builder capacity add-on $

Note:

• Embedded canvas apps within a model-driven app will not count towards the two-app limit.

• A single user might be covered by multiple ‘per app’ licenses to allow the user to use multiple solutions targeted at various business scenarios, without requiring a per-user license

• Once a pool of Power Apps per app licenses are purchased, individual licenses need to be assigned to specific environments and to individual users (i.e. if the same app exists in two environments, a user would require two per app SLs to access both).

• The Power Apps Per App plan is available to education customers under faculty and student pricing. Since these licenses are sold as tenant level capacity and not assigned to users in Active Directory, customers and partners will be responsible for ensuring that student pricing is only being applied to students. This means that when licenses are purchased with student pricing, the number of app licenses assigned to non-students (i.e. faculty) in the product may not exceed the number of faculty licenses purchased as this would indicate that student licenses have been assigned to faculty

Last modified: Sep 29, 2020

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment