Hi All - thank you all for the feedback, we'll continue to review feedback on licensing scenarios and how we can improve it in the future. I'd like to make a couple clarifications for this thread so we are all on the same page :
Are not all Apps run in a browser? So can a P1 run a model-driven App or not? If so, in what context?
Clay : This line on the pricing page is in specific reference to Canvas apps, sorry for the confusion. We are going to have the pricing page updated to explicitly state Canvas apps.
Clay : This line on the pricing page is referring to the APIs included as part of the Dynamics 365 apps. It is not referring to all endpoints. Entity metadata and data CRUD operations can be performed through the APIs following the same entity license restrictions as if you were using Canvas or Model driven apps. An example is you can use the Web APIs or SOAP endpoints to create a new Opportunity, or update an Account using a PowerApps license. However, if you wish to use the GenerateQuoteFromOpportunityRequest action, you would require a Dynamics 365 license. We are going to work on how we can clarify this in our pricing page and documentation with our team.
[Removed and reposted in seperate post below with an updated response]
So, to me, it seems that users can use Plan 1 to run this apps as long as you don't use plugins or RT workflows in your app...
Clay : Correct. Plan 1 can run apps, as long as they don't contain entities which use plugins or real time workflows - or a restricted entity.
But I wonder... Isn't it cheaper to make users use a Team Member license instead to run the app?
Clay : Depending on your scenario, it may be - but please remember that the Team member license has limited use cases and features which are allowed under its license. It's designed to license the user for specific light tasks outlined in the Dynamics 365 Licensing Guide. Before using this license, I'd review the licensing guide here.
We will continue to improve our documentation and clarify these types of questions on the docs and pricing page.
It is great to get some clarification, specially in the docs. Thanks.
Regarding "P1 License access to Restricted Entities", I was quoting the Pricing Page table below, which shows P2 has ReadOnly and P1 has none:
By the way, can Plugins in Activities be excluded from the P1 Plugin restriction?
That is, please allow a P1 user to use any type of Activity entity that has a Plugin.
This is because, P1 users, just like Team Members, typically complete some tasks within app and do not need any other functionalty of the app.
And Plugins in Activities will allow to do validation before allowing the P1 User to complete the task.
So please consider allowing P1 user to use Plugins in Activities.
Thanks - and I should clarify as I have reread the thread.
Your question was specifically about P1, and I responded about PowerApps plans in general. I've confirmed with our team and wanted to clarify that for the restricted entities, you do require a PowerApps or Flow Plan 2 license even for read and you are correct that a PowerApps Plan 1 cannot access restricted entities.
I've clarified my response here :
P1 does not even have Read access to Restricted Entities
Clay : PowerApps Plan 2 is required to read restricted entities, and full CRUD operations require a specific license for the app.
Sorry my intiial response was unclear, I've edited the post to remove the original text and point to this clarification.
Well Clay, the fact that even you (Microsoft PowerApps staff) were confused with if P1 could access Restricted Entities or not, just proves my point:
PowerApps Licensing is just too complex to understand!!!
Please, please, please make it simpler with more resonable limitations.
We are dying to start selling this to our prospects.
Could not agree more. While $40 is a bargin for the developer capabilities, it's too much just to run the app. This price point will definately prevent uptake of this awesome opportunity.
Please remember that CSP ISV partners with IP built on CDS need markup your price to make money.
For users of model-driven apps, we need a license priced between Team Member and P2. With that you could even consider raising the price of P2 - or not. :-)
Here is a an idea...please vote:
Thanks for listening.
Plugins in Activities be excluded from the P1 Plugin restriction is a very valid point, we're facing the same challenge.
As soon as you have Dynamics in an environment most entites have those activity plugins installed and would need a P2 license. This includes applicationCommon entities like Account and Contact.
It would be great to have these plugins exempted, in order to create a really small canvas app for user in that environment who would otherwise neve given a bigger license.