Power Platform Community Forum Thread Details

We are currently exploring how we can limit the development capabilities of normal end-users in the default environment from Dataverse.

Does anybody know how we can disable the possibility to use apps/flows for production purposes, that are created by users that are not permitted?

We now seem to have the ability to convert the default environment to a managed one, but this doesn't seem like it should be used for the purpose stated above.

Reason why we want to do this?

- We have seen a lot of people in the past that started to create Nintex workflows without IT knowing it, these flows are then used in daily work, and when that person leaves, there is no manual or knowledge concerning those flows, which can be quite frustrating.

We already use the CoE to identify, but it can't be the case imo that somebody needs to monitor this actively to see if some people are doing stuff they shouldn't.

Or if anybody has some other recommendations, please feel free to share.

Kind regards

Categories:

Microsoft Dataverse with Power Apps

You have very limited control over the default environment by design, that is supposed to be used as a playground, for personal productivity automations etc and for first-party integrations to SharePoint. I'm not familiar with Nintex, but as far as I know there's not a whole lot you can do expect internal communication and follow up with CoE and a governance strategy to identify and help users move their apps/flows to other proper dev/test/production environments. Only other way I can think of, and not sure if it is relevant, but it might be worth investigating setting up a DLP policy that blocks/limit connectors to be used in the default environment.

Microsoft also suggest renaming the default environment to "Personal Productivity", more recommendations and tips for environment startegies can be found here: https://powerapps.microsoft.com/en-us/blog/establishing-an-environment-strategy-for-microsoft-power-platform/