How to remove Managed Environment status with PowerShell
Diesen Beitrag auf Deutsch lesen
A PowerShell method changes the governance configuration to Basic and effectively removes Managed Environment status.
TL;DR
The Microsoft.PowerApps.Administration.PowerShell module can change a Managed Environment to unmanaged by setting protectionlevel to Basic. An environment or tenant administrator creates a custom object, signs in with Add-PowerAppsAccount, and runs Set-AdminPowerAppEnvironmentGovernanceConfiguration with the Environment ID. The change removes the managed status, but also requires weighing premium licensing against lost guardrails and visibility.
Original by Michael Roth, on MichaelRoth42 Blog. Read the original · suggested by Michael Roth
This is our own summary, not a republication or full translation.
Governance takeaway
- Admins/CoE: Install the Microsoft.PowerApps.Administration.PowerShell module and use environment or tenant admin permissions before running the configuration cmdlet.
- Admins/CoE: Pass the Environment ID, not a display name, and set protectionlevel to Basic to remove the managed status.
- Leadership/Business: Weigh the premium license requirement for every user against the structure, guardrails, visibility, and ALM benefits that Managed Environments provide.
Frequently asked questions
Why would you want to remove the Managed Environment status again?
The post names licensing as the background. Managed Environments require a premium license for every user, which the author calls a tough sell in many organizations.
What do you need before running the command?
The PowerShell module Microsoft.PowerApps.Administration.PowerShell must be installed. You also need rights as environment admin or tenant admin.
Which cmdlet removes the managed status, and with which parameters?
The cmdlet Set-AdminPowerAppEnvironmentGovernanceConfiguration. It needs two parameters: EnvironmentName with the identifier of the environment and UpdatedGovernanceConfiguration with the object created before.