Showing results for 
Search instead for 
Did you mean: 
Helper I
Helper I

Environment: Best Practices



Is there a way to restrict creation on new Dataverse for a Team when an app is added, and instead use and an existing environment to publish the app?


Continued Contributor
Continued Contributor

Hello @anka,


A Dataverse for Teams environment is automatically created for a specific team when an app is created in this team:

So if your users create an app in a team that does not yet have a Dataverse for Teams environment, it is automatically created.

Afaik, the only way to govern who can create environments is by restricting the use of the Power Apps and Power Automate apps in Teams:

If your users deploy one of Microsoft's sample apps in a team without a Dataverse for Teams environment, it will also create one, so you may want to restrict this too.

As part of the CoE Starter Pack, you can automatically react to the creation of a new Dataverse for Teams environment. If users do not provide a business justification, the environment will be deleted automatically:


Helper I
Helper I

Thank you for your response. So potentially there can be one environment for each team. I wish if there was a way to have users use an existing environment. I tried to research it but could not figure out if that feature is available. Let's see if any other community member responds to this, who has been able to accomplish it.

Helpful resources

UG GA Amplification 768x460.png

Launching new user group features

Learn how to create your own user groups today!

Power Apps Community Call Jan. 2022 768x460.png

Power Apps Community Call

Please join us on Wednesday, January 19th, at 8a PDT. Come and learn from our amazing speakers!

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

Top Kudoed Authors
Users online (1,019)