Power Platform – Managed personal developer environments are now included in inactivity-based cleanup
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: Automatic deletion of Power […]
The post Power Platform – Managed personal developer environments are now included in inactivity-based cleanup appeared first on M365 Admin.
Published on:
Learn moreWe can help you with Power Platform – Managed personal developer environments are now included in inactivity-based cleanup
If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.
Related posts
Intune: Windows Health Attestation Migration to Microsoft Azure Attestation
Microsoft Intune will migrate Windows Health Attestation compliance evaluation from the current Device Health Attestation (DHA) service to Mic...
Dynamics 365 Commerce – Print receipts using Adyen payment terminal printers
We are announcing the ability to print receipts using the built-in printer on supported Adyen payment terminals in Dynamics 365 Commerce. This...
Outlook: Multi Account Search
Users will be able to see results from multiple mailboxes interweaved in a single ranked list and will be able to do standard mail actions. Pr...
Dynamics 365 Field Service: Manage rental service demand with work order requests
Rental organizations need to coordinate commercial rental activity, equipment availability, asset condition, and service execution across mult...
Microsoft Teams: Schedule Channel Meetings from Outlook Calendar
Users will be able to schedule Microsoft Teams channel meetings directly from Outlook Calendar. This streamlines meeting creation and helps ke...
Microsoft 365 admin center: Optional Public CDN Support in Brand Center Setup
We are updating the Brand Center setup experience so that administrators can set up Brand Center without enabling Public CDN. Today, Public CD...
Dynamics 365 Field Service: Book Work Orders with Multiple Requirements
Dispatchers can now select which resource requirement to schedule when booking a work order that has multiple requirements. The new Book exper...
Brand Skill support now available in PPT Copilot [Web]
Brand managers can upload custom presentation skills as Markdown files to Brand Kit for use with Copilot in PowerPoint Web, enabling consisten...
Brand Skill support now available in PPT Copilot [Desktop]
Brand managers can now upload custom presentation skills as Markdown files to Brand Kit for use with Copilot in PowerPoint Desktop, enabling c...