Manage environments in the PowerApps Admin center
We are moving environment management from other admin centers to the Power Platform Admin center. Until this is completed, some management can be or must be done in other admin centers such as the PowerApps Admin center.
In the PowerApps Admin center, manage environments that you've created and those for which you have been added to the Environment Admin or System Administrator role. From the admin center, you can perform these administrative actions:
- Create environments.
- Rename environments.
- Add or remove a user or group from either the Environment Admin or Environment Maker role.
- Provision a Common Data Service database for the environment.
- Set Data Loss Prevention policies.
- Set database security policies (as open or restricted by database roles).
- Members of the Azure AD tenant Global administrator role (includes Office 365 Global admins) can also manage all environments that have been created in their tenant and set tenant-wide policies.
For more information, see Environments overview.
Access the PowerApps Admin center
To access the PowerApps Admin center:
Go directly to admin.powerapps.com, OR
Go to powerapps.com, and then select the gear icon in the navigation header.
To manage an environment in the PowerApps Admin center, you must have one of these roles:
The Environment Admin or System Administrator role of the environment, OR
The Global Administrator role of your Azure AD or Office 365 tenant.
You also need either a PowerApps plan or Power Automate plan to access the admin center. For more information, see the PowerApps pricing page.
Any changes that you make in PowerApps Admin center affect the Power Automate admin center and vice versa.
Create an environment
For instructions on how to create an environment, see Create an environment.
View your environments
When you open the admin center, the Environments tab appears by default and lists all the environments for which you are an Environment Admin (as shown below):
If you are a member of the Global Administrator role of your Azure AD or Office 365 tenant, all the environments that have been created by users in your tenant appear, because you're automatically an Environment Admin for all of them.
Rename your environment
Open the PowerApps Admin center, find the environment to be renamed in the list, and click or tap it.
Click or tap Details.
in the Name text box, enter the new name, then click Save.
If you have created the database in the environment, then you will not see this option. You can rename the environment from Dynamics 365 Admin center by clicking on the link in Details tab.
Delete your environment
In the PowerApps Admin center, click or tap the environment that you want to delete.
Click or tap Details.
Click or tap Delete environment to delete your environment.
Create a Common Data Service database for an environment
If an environment doesn't already have a database, an Environment Admin can create one in the PowerApps Admin center by following these steps. Only users with a PowerApps plan can create Common Data Service databases.
Select an environment in the environments table.
Select the Details tab.
Select Create a database.
After you create a database, choose a security model. For more information, see Configure database security.
Manage security for your environments
In an environment, all the users in the Azure AD tenant are users of that environment. However, for them to play a more privileged role, they need to be added to a specific environment role. Environments have two built-in roles that provide access to permissions within an environment:
The Environment Admin role (or System Administrator role) can perform all administrative actions on an environment including the following:
Add or remove a user from either the Environment Admin or Environment Maker role.
Provision a Common Data Service database for the environment.
View and manage all resources created within an environment.
Set data loss prevention policies. For more information, see Data loss prevention policies.
If the environment has the database, then you need to assign users the System Administrator role, instead of the Environment Admin role.
The Environment Maker role can create resources within an environment including apps, connections, custom connectors, gateways, and flows using Power Automate. Environment Makers can also distribute the apps they build in an environment to other users in your organization. They can share the app with individual users, security groups, or all users in the organization. For more information, see Share an app in PowerApps.
To assign a user or a security group to an environment role, an Environment Admin can take these steps in the PowerApps Admin center:
Select the environment in environments table.
Select Security tab.
If there is no database created in the environment:
a. Select either the Environment Admin or Environment Maker role.
b. Specify the names of one or more users or security groups in Azure Active Directory, or specify that you want to add your entire organization.
c. Select Save to update the assignments to the environment role.
If database is created in the environment:
a. Add the user to the environment and click on the link to assign the user a role.
b. Select the user from the list of users in the environment / environment.
c. Assign the role to the user.
d. Select OK to update the assignments to the environment role.
Users or groups assigned to these environment roles are not automatically given access to the environment’s database (if it exists) and must be given access separately by a Database owner. For more information, see Configure database security.
The ability to create and modify a database schema and to connect to the data stored within a database that is provisioned in your environment is controlled by the database's user roles and permission sets. You can manage the user roles and permission sets for your environment's database from the User roles and Permission sets section of the Security tab. For more information, see Configure database security.
An organization's data must be protected so that it isn't shared with audiences that should not have access to it. To protect this data, you can create and enforce policies that define which consumer services and connector-specific business data can be shared with. Policies that define how data can be shared are referred to as data loss prevention (DLP) policies. You can manage the DLP policies for your environments from the Data Policies section of the PowerApps Admin center. For more information, see Data loss prevention policies.
Frequently asked questions
How many environments and databases can I create?
Provisioning environments is based on the available storage in your organization. You need at least 1GB minimum database storage to create an environment.For more information, see Environments overview.
Which license includes Common Data Service?
PowerApps plan. See PowerApps pricing page for details on all the plans that include this license.
While trying to create a new environment, I am getting an error. How should I resolve it?
If you are getting the following error message: "Either your plan doesn’t support the environment type selected or you’ve reached the limit for that type of environment.", it can mean one of the two things:
You have already utilized your quota to create a specific type of environments. Say you were creating a Trial environment and you get this error message. That means, that you have already provisioned two Trial environments. You can view all the environments in PowerApps Admin center. If you want, you can delete an existing environment of that specific type and create a new one. But, please make sure that you don't lose your data, apps, flows and other resources which you want to retain.
You do not have a quota to create that specific type of the environment.
If you are getting any other error message or have more questions, please connect with us here.
When will my Trial environment expire?
Trial environments expire after 30 days from their creation. If you don't want your Trial environments to expire, you can convert them to Production environments.
Does my current database (created with previous version of the Common Data Service) also gets counted in the quota?
If you had a database (created with previous version of the Common Data Service), they will also get counted with your Production environment quota. If you now create a database in an environment (created prior to March 15, 2018) then it will also get counted as Production environment.
Can I rename an environment?
Yes, this functionality is available from the PowerApps Admin center. See Environments Administration for more details.
Can I delete an environment?
Yes, this functionality is available from the PowerApps Admin center. See Environments Administration for more details. Please note that you currently can't delete a Production environment with a database (with latest version of the Common Data Service). This will be coming soon!
As an Environment Admin, can I view and manage all resources (apps, flows, APIs, etc.) for an environment?
Yes, the ability to view the apps and flows for an environment is available from the PowerApps Admin center. See View Apps for more details.