Does a Power Apps license cover the use of "complex" entities/tables (e.g. "opportunity", "account") in a model driven app?

[MariusHT]

Hello, all!

I'm creating a model driven power app for my department. Most users will have access through a Per-App licence, while I have a Premium license.

When creating the environment, I checked the option to "Enable Dynamics 365 apps". I thus have access to different "complex" entities/tables, such as "Account", "Lead", and "Opportunity".

My question is this: If I include any of these "complex" entities/tables in our model driven app, will we be required to obtain additional licenses - e.g. Dynamics 365 licenses?

I am not planning to actually use any of the Dynamics 365 apps. So if I understand the table licensing scheme and complex tables overview correctly, we will not need any other license than Power Apps Premium/Per-App.

Also, none of these special entities/tables are listed as "Restricted tables requiring Dynamics 365 licenses". Thus - can I use all other tables as I'd like, as long as I have a Power Apps License?

I would really like to *not* have to move my solution and app over to a new environment (without Dynamics 365 apps enabled). And I find the whole Power Platform license scheme very unclear.

[Michaelfp · Accepted solution]

You will need at least one Dynamics 365 Sales Professional or Enterprise to cover what you need. 

As you can see in the table below to works with leads and opportunity you must have the D365 Sales Pro or Enterprise.

And as you can see below the mix of the licenses allow you to you Per App use the same table, since they are on the same context.

If my answer helped you, please give me a thumbs up (👍). If solve your question please mark as solution ✔️. This is help the community.

[MariusHT]

Thank you very much, @Michaelfp!

I cannot find the documentation you refer to in your screenshots. Is there a link you can share with me?

I really think that Microsoft should make this clear in the Dataverse/Power Apps documentation. We want to have the correct licenses, but it's really difficult to find information about what is allowed an not when using only Power Apps licenses. 

Except from not using any restricted tables, are there any downsides with activating "Enable Dynamics 365 apps" in the environment as a default? Our thought is that we might want to move to a Dynamics solution in the future, and we've therefore activated it (since it cannot be activated later on). But for now, we want to use our custom model driven app with only Power Apps licenses. As I understand it from the documentation, we don't need any Dynamics license as long as we do not use the provided Dynamics apps (CRM/Sales), or use Dynamics restricted tables in our custom model driven apps. Is this correct?

Again, thank you very much for your help.

[Michaelfp]

Hi! The link is here https://www.bing.com/ck/a?!&&p=6f6fc46ba18ff0aeJmltdHM9MTcxODg0MTYwMCZpZ3VpZD0zN2ZhNjExZi0wODE5LTY0M...

You can activate, but it will consume a space that will not gonna use. But if is your plan to use, i would recommend to create the environment with d365 apps.

[MariusHT]

Thanks again, @Michaelfp !