Live Publish (03/24/2025 06:00:01 AM)

Author: bishalgoswami

power-platform/admin/automatic-environment-cleanup.md

@@ -3,7 +3,7 @@ title: Automatic deletion of Power Platform environments
 description: Learn about the automatic processes that identify and disable Power Platform environments and how you can prevent them from being deleted.
 ms.component: pa-admin
 ms.topic: how-to
-ms.date: 03/18/2025
+ms.date: 03/24/2025
 ms.subservice: admin
 author: matapg007
 ms.author: matgupta 
@@ -47,12 +47,10 @@ If an environment has already been deleted, you have a limited window of time to
 
 ## Inactivity-based cleanup
 
-A cleanup mechanism in Power Platform automatically removes environments that aren't being used. After 90 days of inactivity, an environment is turned off. After 30 days, if no action is taken, the environment that was turned off is deleted. You have seven days to recover deleted environments.
-
-Only default, developer, and [Dataverse for Teams environments](inactive-teams-environment.md) are affected by the activity-based automatic cleanup.
+A cleanup mechanism in Power Platform automatically removes environments that aren't being used. Only default, developer, and [Dataverse for Teams environments](inactive-teams-environment.md) are affected by the activity-based automatic cleanup.
 
 ## Default environment 
-Power Platform is implementing a cleanup process for default environments that meet the following criteria:
+Power Platform is implementing a cleanup process for default environments that meet the following criteria. After 90 days of inactivity, two warning notifications are sent to environment administrators, if no action is taken, the environment is deleted. You have seven days to recover deleted environments.
 
 - Environments with [premium licenses](pricing-billing-skus.md) aren't included in the cleanup.
 - Environments with Microsoft 365 agents or planner activity aren't included in the cleanup.
@@ -66,20 +64,25 @@ During the deletion process, a new replacement default environment is created wi
 > [!IMPORTANT]
 > You can't turn off this cleanup mechanism. However, you can review the last activity date for environments in the Power Platform admin center. 
 
-### Timeline for unused environments
+## Develeoper environment
+ Power Platform is implementing a cleanup process for developer environments that meet the following criteria. After 30 days of inactivity, an environment is turned off. After 30 days, if no action is taken, the environment that was turned off is deleted. You have seven days to recover deleted environments.
 
-The time between the first warning that the environment will be disabled to the final deletion of the environment is 37 days. Production environments aren't subject to this timeline.
+- Admins receive two warning notifications before the environment is deleted due to inactivity.
+- Any activity within 15 days of the notification resets the inactivity period.
+- Inactive environments are deleted after 15 days of inactivity notification.
+  
+### Timeline for unused environments
 
 The environment's administrators and the user who created the environment are notified by email according to the schedule described in the following table.
 
 | State of environment | Power Platform action |
 | --- | --- |
-| 83 days with no [user activity](#definition-of-user-activity) | Send a warning that the environment will be disabled and display a countdown in the **Environment state** on the **Environments** list page and the **Environment** page. |
-| 87 days with no user activity | Send a second warning that the environment will be disabled. |
-| 90 days with no user activity | Disable the environment, send a notice that the environment has been disabled, and update the **Environment state** on the **Environments** list page and the **Environment** page. |
-| 23 days after the environment is disabled | Send a warning that the environment will be deleted and display a countdown in the **Environment state** on the **Environments** list page and the **Environment** page. |
-| 27 days after the environment is disabled | Send a second warning that the environment will be deleted. |
-| 30 days after the environment is disabled | Delete the environment, and send a notice that the environment has been deleted. |
+| 23 days with no [user activity](#definition-of-user-activity) | Send a warning that the environment will be disabled and display a countdown in the **Environment state** on the **Environments** list page and the **Environment** page. |
+| 27 days with no user activity | Send a second warning that the environment will be disabled. |
+| 30 days with no user activity | Disable the environment, send a notice that the environment has been disabled, and update the **Environment state** on the **Environments** list page and the **Environment** page. |
+| 7 days after the environment is disabled | Send a warning that the environment will be deleted and display a countdown in the **Environment state** on the **Environments** list page and the **Environment** page. |
+| 11 days after the environment is disabled | Send a second warning that the environment will be deleted. |
+| 15 days after the environment is disabled | Delete the environment, and send a notice that the environment has been deleted. |
 
 A notification appears on the **Environments** list page and **Environment** page when an environment is disabled.
 
@@ -99,7 +102,7 @@ Activity includes automations such as scheduled flow runs. For example, if there
 
 ## Trigger activity, re-enable, and recover an environment
 
-By default, administrators have 30 days to re-enable an environment. If the environment remains disabled for 30 days, it's automatically deleted. Administrators have seven days to [recover a deleted environment](#recover-a-deleted-environment).
+By default, administrators have 15 days to re-enable an environment. If the environment remains off for 15 days, it's automatically deleted. Administrators have seven days to [recover a deleted environment](#recover-a-deleted-environment).
 
 ### Trigger activity in an inactive environment