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

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?


Impactful Individual
Impactful Individual

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 II
Helper II

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

Power Apps News & Annoucements carousel

Power Apps News & Announcements

Keep up to date with current events and community announcements in the Power Apps community.

Community Call Conversations

Introducing the Community Calls Conversations

A great place where you can stay up to date with community calls and interact with the speakers.

Power Apps Community Blog Carousel

Power Apps Community Blog

Check out the latest Community Blog from the community!

Users online (4,087)