What is a Managed Environment:
- Managed Environments is a suite of premium capabilities that allows admins to manage Power Platform at scale with more control, less effort, and more insights.
- Admins can use Managed Environments with any type of environment. Certain features can be configured upon enabling a Managed Environment.
In this article, let me demonstrate how to enable or disable the environment as ‘Managed’.
Enable Managed Environment:
- Admins can enable, disable, and edit Managed Environments in the Power Platform admin center.
- You must be an admin to enable or edit Managed Environments. That is, you must have the role of global admin, Power Platform service admin, or Dynamics 365 admin Azure Active Directory.
- Any user with permission to see environment details can view the Managed Environments property for an environment.
- Users with the Delegated Admin role or the Environment Admin security role aren’t allowed to change the Managed Environments property in an environment.
Steps to enable Managed Environment:
- In the Power Platform admin center, select Environments.
- In the context menu, select Enable Managed Environments. You can also use 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.

- After enabling, you should observe the ‘Managed’ property of the Environment set to ‘Yes’.

Disable a Managed Environment:
Admins can use PowerShell to disable Managed Environments.
- Open the PowerShell console.
- Connect to the ‘Power Apps Account’ using Add-PowerAppsAccount command as shown below.

- To initiate the disable command, we require the ‘Environment ID’ of the managed environment.
- Copy the ‘Environment ID’ as shown below from Power Platform admin center.

- Execute the following PowerShell command, and you should receive the 202 code.
$UpdatedGovernanceConfiguration = [pscustomobject]@{
protectionLevel = "Basic"
}
Set-AdminPowerAppEnvironmentGovernanceConfiguration -EnvironmentName 0d006b76-d1c4-e357-a851-e5da6217c006 -UpdatedGovernanceConfiguration $UpdatedGovernanceConfiguration

- Return to the Power Platform admin center , and you should observe the ‘Managed’ property set to ‘No’.

Note:
- Before disabling Managed Environments, the administrator must ensure that none of the Managed Environments capabilities are in use.
- Managed Environments is included as an entitlement with standalone Power Apps, Power Automate, Power Virtual Agents, Power Pages, and Dynamics 365 licenses. Trial licenses can be used to license users in Managed Environments, with the restrictions specific to these types of licenses.
- Managed Environment isn’t included as an entitlement in the Developer Plan when users run their assets.
🙂

![[Step by Step] Configure and consume 'Environment Variables' of type 'Secret' using 'Azure Key vault'](https://rajeevpentyala.com/wp-content/uploads/2023/05/image.png)
Leave a comment