Giving back to the community what I have learned
Tag: environments
Sometimes, the most useful things may go unnoticed, this FLOW template can provide a list of new apps, flows, and connectors that have been introduced into your tenant within a configurable window. This is very useful when you are an admin and have to do some house keeping activities in the tenant.
Sharing an app with the user and, asking the user to run the app for one time will resolve this issue for most cases. I have had few instances where, new users with maker roles were unable to see the environment in the maker portal even after sharing the app. However, sharing a sample App with Co-owner permission resolved this issue.
From my experience, it’s better not to give delete permission to end users, upvote here, if you agree.
Dynamics 365 Enterprise licenses does not include general purpose Power Apps capabilities. Dynamics 365 Enterprise users will continue to be able to run apps and portals that extend and customize the licensed Dynamics 365 application, as long as those apps and portals are located in the same environment as their licensed Dynamics 365 application. Custom apps or portals outside of the Dynamics 365 environment will require a standalone Power Apps license. In short, If a user A has only dynamics 365 license applied, then A can be added only to environments which has at least one Dynamics 365 App installed. Read more here.
nijos.dev 