We are introducing an automated process to delete inactive personal developer environments, starting April 24, 2026.
Personal developer environments in your tenant follow an inactivity-based lifecycle policy. Non-Managed developer environments are automatically cleaned up after 30 days of inactivity. This policy extends to Managed developer environments, with a 60-day inactivity window before cleanup begins, giving makers more time before any action is taken. Environment owners and admins will receive multiple emails before any disablement occurs.
Activity includes any user, maker, or admin action such as creating, editing, or launching an app; creating, editing, or running a flow; creating, editing, or chatting with a Microsoft Copilot Studio agent; or copy, restore or reset environment. Any activity resets the 60-day inactivity period.
How does this affect me?
Starting April 24, 2026, environment owners of the personal developer environments that are inactive for 60+ days receive warning notifications.
Re-enabling your environment from the Power Platform Admin Center (PPAC) at any point resets the timeline. Deleted environments remain recoverable for up to 7 days from the environment page in PPAC.
What action do I need to take?
No action is needed if your personal developer environments are in active use. You can check the last activity of an environment from the environments list in PPAC.
To keep an environment active, select Trigger environment activity on the environment page in PPAC when you receive a warning notification or ensure any user or maker performs activity in the environment.
No action is needed if you no longer need inactive developer environments, as they will be cleaned up automatically.
Why is this action needed?
Unused personal developer environments add governance overhead with no corresponding business value. Today Managed developer environments are exempted from inactivity cleanup, leaving abandoned environments behind indefinitely. Extending cleanup to Managed developer environments closes this gap, with a 60-day threshold that gives makers a longer inactivity window before cleanup. Makers and admins receive multiple warning notifications before any disablement or deletion, and deleted environments remain recoverable for 7 days.
If you would like more information on this update, please visit:
Details
Change History
No change history available
Never Miss a Microsoft 365 Update
Join thousands of IT professionals who rely on DeltaPulse for real-time Microsoft 365 change intelligence, automated notifications, and community insights.