Admins enable, disable, and edit Managed Environments in the Power Platform admin center. Admins can also use PowerShell to disable Managed Environments. This article explains the permissions you need to manage environments and the steps to get started in the Microsoft Power Platform admin center or with PowerShell.
Permissions
To enable or edit Managed Environments, you need the Power Platform Administrator or Dynamics 365 Administrator role in Microsoft Entra ID. You can learn more about these roles in Use service admin roles to manage your tenant.
- Any user with permission to view environment details can see the Managed Environments property for an environment.
- Users with the Delegated Admin role or the Environment Admin security role can't change the Managed Environments property in an environment.
Important
The Managed Environments property must be the same in the source and destination before you can start copy and restore environment lifecycle operations.
Enable or edit Managed Environments in the admin center
Sign in to the Power Platform admin center.
In the navigation pane, select Environments.
Select the check mark to the left of an environment.
On the command bar, select Enable Managed Environments. If the environment is already managed, select Edit Managed Environments.
Configure the settings, and then select Enable or Save.
Use the following settings to increase visibility and control for the selected environment.
| Setting |
Description |
| Limit sharing |
Help reduce risk by limiting how widely canvas apps can be shared. |
| Don't set limits |
Select to not limit sharing of canvas apps. |
| Exclude sharing with security groups |
Select if makers aren't allowed to share canvas apps with any security groups. Admins may share with a limit on who an app can be shared with. |
| Limit total individuals who can be shared to |
If Exclude sharing with security groups is selected, select to limit the number of people that makers can share canvas apps with. |
| Enable AI-generated app descriptions (preview) |
If descriptions of apps are blank, AI is used to generate them. This happens when an app is published and can help people understand what the purpose of an app is. |
| Usage insights |
Select to include insights for this environment in the weekly email digest. |
| Data policies |
Help safeguard your organizational data by limiting the connectors available. |
| See active data policies for this environment |
View the policies that define the consumer connectors that specific data can be shared with. |
Enable Managed Environments using PowerShell
Admins can also use PowerShell to enable Managed Environments. The following PowerShell script enables it for a single environment.
$GovernanceConfiguration = [pscustomobject] @{
protectionLevel = "Standard"
settings = [pscustomobject]@{
extendedSettings = @{}
}
}
Set-AdminPowerAppEnvironmentGovernanceConfiguration -EnvironmentName <EnvironmentID> -UpdatedGovernanceConfiguration $GovernanceConfiguration
Copy Managed Environment settings using PowerShell
Admins can use PowerShell to copy settings from one Managed Environment to another environment. If the target environment isn't a Managed Environment, copying settings also enables it as a Managed Environment.
#Get settings from the source Managed Environment
$sourceEnvironment = Get-AdminPowerAppEnvironment -EnvironmentName <SourceEnvironmentId>
# Copy the settings from the source Managed Environment above to the target environment
Set-AdminPowerAppEnvironmentGovernanceConfiguration -EnvironmentName <TargetEnvironmentId> -UpdatedGovernanceConfiguration $sourceEnvironment.Internal.properties.governanceConfiguration
Disable Managed Environments using PowerShell
Admins can use PowerShell to remove the Managed Environments property from an environment. Before you disable Managed Environments, make sure none of the Managed Environments capabilities are in use.
Here's an example PowerShell script that calls the API to set the Managed Environments property:
$UpdatedGovernanceConfiguration = [pscustomobject]@{
protectionLevel = "Basic"
}
Set-AdminPowerAppEnvironmentGovernanceConfiguration -EnvironmentName <EnvironmentID> -UpdatedGovernanceConfiguration $UpdatedGovernanceConfiguration
See also