In my org, we have environment routing activated to direct new citizen developers away from the default environment for their initial exploration into the power platform. Our hope is that they will use their personal developer environment to create, explore, and learn without creating unused apps and flows in the default environment.
However, as you may have guessed, we now have a ton of personal developer environments. I was expecting that this feature of the power platform, (unused Environments - https://learn.microsoft.com/en-us/power-platform/admin/automatic-environment-cleanup#unused-environments) would handle this concern. According to this information, Developer and Dataverse for teams environments are the only types of environments affected by the activity-based automatic cleanup.
I have noticed that the last activity date on most of the personal developer environments are virtually the same. Most developer environments are not actually being used by their owners. Some try a few things in the power platform, and some continue their journey to develop solutions, but most don't invest much time their initial interest. In my investigation, I noticed that all environments are affected by a new feature in the form of a power platform solution, automatically installed by Microsoft, called the Power Platform Environment Settings solution (part of the 2024 Release wave plan 2 - power-platform release-plan 2024wave2 | Microsoft Learn). (Use the Power Platform Environment Settings app | Microsoft Learn)
This solution is hoping to create a single unified admin experience inside an actual power app that would allow admins to manage environment settings without actually leaving their environment, totally avoiding the power platform admin center.
That seems like a good idea, except for the fact that any update or release from Microsoft that is pushed directly to an environment, like the Environment Settings App, would qualify as an activity on the environment. Each activity updates the "Last activity" date, meaning that environment is not in an "inactive" state to be considered for automatic deletion.
If this continues, the environments in my Org that are actually inactive and should be deleted will never be deleted. The auto-deletion of inactive environments is rendered useless.
Is there some way to control the auto-deletion of unused environments to ensure that truly inactive environments are actually deleted?
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
19
Share
Report
All responses (
Answers (
