Licenses required to consume Model Driven App

(0) Share

Report

Posted on by Arioule

156

Hi,

According to my Microsoft Documentation reading, It seems that a model driven app user needs a Power Apps Plan 2 license.

However, I have given to a user just a Microsoft Power Automate Free License and he was able to access a Model Driven App, to create/delete/update entity records (once the right security roles assigned).

So, it is quite confusing for me. Is a Microsoft Power Automate Free License sufficient to consume Model Driven Apps ?

Thanks,

Arioule

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

Joel CustomerEffective 3,224 on at

Like (1)

Report
Copy link

Link copied!

Plan 2 is the old licensing. Under new licensing user must have a per user or per app license, not a free license. If they can see the model driven app it may be that they have a trial license or a dynamics 365 license. D365 includes power apps and model driven apps

@Arioule if this answers your questions please mark it a solution

Was this reply helpful? Yes No
Arioule 156 on at

Like (0)

Report
Copy link

Link copied!

Hi @jlindstrom,

You are right I have a Power Apps per user plan Licence.
But as far as I know we do not have a trial license or a dynamics 365 license.

The only thing I have done to give access to my model driven app user is to assign him a Microsoft Power Automate Free as shown below :

It seems that Licence give access to the "Common Data Service". Is it the reason why my user can consume the model driven App without restriction ?

Thanks,

Arioule

Was this reply helpful? Yes No
Ben Thompson 1,400 on at

Like (0)

Report
Copy link

Link copied!

Yes, I would suspect that by ticking that Common Data Service App box the user is given access to all Common Data Service environments so that the data can be accessed (for readonly purposes).

And once the user is granted the ability to access CDS environments its then possible to grant them rights to create and update records as MS's technical enforcement of licensing is limited so it is open to abuse and accidentally misuse. And there is a reason for that, technical enforcement usually create complex and time consuming support issues.

However, it is your responsibility to enforce the rules so while you could use it to provide users with more rights than they should have MS could easily review your licenses and charge for all the breaches

Was this reply helpful? Yes No