Announcements
Hi,
The Dynamics 365 Enterprise license give the ability to run an unlimited number of apps (canvas, model driven) "within the same environment(s) as licensed Dynamics 365 application(s)" as per the licensing guide.
How does this restrict anything? If I install, for example, the Sales app in all my environment, I would then be able to create unrestricted Power Apps everywhere using my Sales Enterprise license.
Is there something I am missing?
Thank you.
Let's suppose for example that you build a Canvas App that, after providing 2 numeric values, gets the point on a map and is created on an environment that doesn't have a Database, or doesn't have Dynamics 365 apps.
If your users (with a Dynamics Enterprise license) try to access such app, Since the environment doesn't have a DB, or doesn't have Dynamics apps, users are expected to receive an error.
However, if you grab this same app, export it and import it into a Dynamics environment, and you add it to a custom form, then users (with dynamics enterprise license) would be able to access it.
Regards,
Hi Daniel,
Here is my real life example: I have 3 production environments with corresponding DEV and TEST environments, all of them with the Sales App installed (I will have more in the future). From what I understand, my Sales Enterprise licenses give the users access to all of them and any Canvas, MDD or Portal apps available on those environments.
My questions is, when does a Sales Enterprise license not have access to a Power App? The wording is throwing me off as I don't see a scenario where a licensed users would not have access to an App as long the Sales App is also installed on the environment.
Here is the exact wording from the Power Platform Licensing Guide under Power Apps use rights included with Dynamics 365 licenses :
"Limited Power Apps use rights are included within the same environment(s) as the licensed Dynamics 365 application(s) to allow users to customize and extend Dynamics 365 applications. Use of Power Apps capabilities included with Dynamics 365 licenses must be only within the context of the licensed Dynamics 365 application.
Run standalone apps (canvas/model driven) : Within same environment(s) as licensed Dynamics 365 application(s)"
Note: I exclude the storage requirements for this question but, yes, it is a limiting factor.
Thanks for your help.
Hey Luc!
Do you mind throwing an example? Let's suppose that youhave Dynamics 365 Sales Enterprise license assigned.and Production environment, Dev & Test environments (3 environments in total). Each one of them with Sales APP. If you want to deploy a custom app (either model driven or Canvas) it makes sense that you're able to deploy the app into the three environments.
If you wish to create a new environment with a DB but you don't want the Sales App (for example), you can still deploy your model driven or Canvas app into it. But the users with license (Sales enterprise) will be synchronized to the environment and potentially, access i (if they receive a Security Role on the environment and the App is shared with them). However, this will also happen with other licenses as well: PowerApps per User license, for example
If you wish to restrict users on the app, then you should use Security groups associated to the environments. Also, you should be aware that the more apps you install/deploy on each environment, your storage consumption will increase.
Regards
André Arnaud de Cal... 291,359 Super User 2024 Season 2
Martin Dráb 230,370 Most Valuable Professional
nmaenpaa 101,156