learn.microsoft.com Open in urlscan Pro
2a02:26f0:1300:1b3::3544  Public Scan

Submitted URL: https://docs.microsoft.com/en-us/power-platform/admin/inactive-teams-environment
Effective URL: https://learn.microsoft.com/en-us/power-platform/admin/inactive-teams-environment
Submission: On November 28 via manual from US — Scanned from DE

Form analysis 0 forms found in the DOM

Text Content

Skip to main content


This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security
updates, and technical support.

Download Microsoft Edge More info about Internet Explorer and Microsoft Edge

Table of contents Exit focus mode

Read in English Save
Table of contents Read in English Save Feedback Edit Print

Twitter LinkedIn Facebook Email
Table of contents


AUTOMATIC DELETION OF INACTIVE MICROSOFT DATAVERSE FOR TEAMS ENVIRONMENTS

 * Article
 * 10/06/2022
 * 5 minutes to read
 * 3 contributors

Feedback


IN THIS ARTICLE

Power Platform provides a cleanup mechanism that automatically removes inactive
Dataverse for Teams environments from your tenant. Dataverse for Teams
environments that are considered inactive are first disabled. They're deleted
after a period of time if no action is taken by the administrators.

The process is automatic. If you no longer need an inactive Dataverse for Teams
environment, you don't need to do anything.

Administrators can set the Teams environment deletion policy to configure how
long an environment can be inactive before it's automatically disabled. The
permissible range of values are: 15 days, 30 days, 45 days, 60 days, and 90 days
of inactivity. The policy also determines how long an environment can be
disabled before it's automatically deleted.

Disabling a Dataverse for Teams environment prevents any meaningful use of the
environment and its resources. Apps can't be launched, flows are suspended,
chatbots can't be interacted with, and so on.

For information on automatic cleanup of production and sandbox environments, see
Automatic environment cleanup.


TIMELINE FOR INACTIVE DATAVERSE FOR TEAMS ENVIRONMENTS

The following table describes the schedule of notifications and actions for
Dataverse for Teams environments that are considered inactive.

State of Dataverse for Teams Power Platform action 83 days after no user
activity Send a warning that the environment will be disabled. Update the
environment state on the Environments list page1 and the Environment page2. 87
days after no user activity Send a warning that the environment will be
disabled. Update the inactive environment state on the Environments list page1
and the Environment page2. 90 days after no user activity Disable the
environment. Send a notice that the environment has been disabled. Update the
disabled environment state on the Environments list page1 and the Environment
page3. 113 days after no user activity Send a warning that the environment will
be deleted. Update the disabled environment state on the Environments list page1
and the Environment page3. 117 days after no user activity Send a warning that
the environment will be deleted. Update the disabled environment state on the
Environments list page1 and the Environment page3. 120 days after no user
activity Delete the environment. Send a notice that the environment has been
deleted.

1 Environment state on the Environments list page in Power Platform admin center

2Inactive environment alert on the Environment page in Power Platform admin
center

Note

The Environment inactive warning tile only displays if the Dataverse for Teams
environment is <= 7 days until disablement.

3Disabled environment alert on the Environment page in Power Platform admin
center

Note

The Environment disabled tile displays anytime a Dataverse for Teams environment
is disabled due to inactivity.


NOTIFICATION RECIPIENTS

The following users will receive email notifications on the schedule described
in the timeline:

 * The environment's system administrators
   
   A Dataverse for Teams environment is paired with a team in Microsoft Teams.
   The owners of the team are automatically granted the System Administrator
   role for the environment. They receive email notifications and can trigger
   activity, re-enable, and recover the environment in the Power Platform admin
   center. Team members and guests don't receive the email notifications.

 * The user who created the environment

Additionally, users and makers are notified on the Environments list page and
Environment page when the Dataverse for Teams environment is disabled.


DEFINITION OF USER ACTIVITY

Power Platform calculates a single measure of inactivity for each Dataverse for
Teams environment. The measure accounts for all activity by users, makers, and
admins across Power Apps, Power Automate, Power Virtual Agents, and Dataverse.

Most create, read, update, and delete operations on the environment and its
resources that a user, maker, or admin initiates are considered activity. Most
read operations aren't accounted for.

Here are some examples of the types of activities that are included in the
measure:

 * User activity: Launch an app, execute a flow (whether automatic or not), chat
   with a Power Virtual Agents bot

 * Maker activity: Create, read, update, or delete an app, flow (desktop and
   cloud flows), Power Virtual Agents bot, custom connector

 * Admin activity: Environment operations such as copy, delete, back up,
   recover, reset

Activity includes automated behaviors such as scheduled flow runs. For example,
if there's no user, maker, or admin activity in an environment, but it contains
a cloud flow that runs daily, then the environment is considered active.


TRIGGER ACTIVITY, RE-ENABLE, AND RECOVER A DATAVERSE FOR TEAMS 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. See Recover a
deleted Dataverse for Teams environment.


TRIGGER ACTIVITY FOR AN INACTIVE DATAVERSE FOR TEAMS ENVIRONMENT

 1. Sign in to the Power Platform admin center.

 2. Select Environments, and then select the inactive Dataverse for Teams
    environment.

 3. On the Environment page, select Trigger environment activity.


RE-ENABLE A DISABLED DATAVERSE FOR TEAMS ENVIRONMENT

 1. Sign in to the Power Platform admin center.

 2. Select Environments, and then select the disabled Dataverse for Teams
    environment.

 3. On the Environment page, select Re-enable environment.


RECOVER A DELETED DATAVERSE FOR TEAMS ENVIRONMENT

 1. Sign in to the Power Platform admin center.

 2. Select Environments, and then select Recover deleted environments.

 3. Select an environment to recover, and then select Recover.

For more information, see recover environment.


SET DATAVERSE FOR TEAMS ENVIRONMENT DELETION POLICY

Administrators can change the length of time Power Platform waits to disable
inactive and delete disabled Dataverse for Teams environments.

Note

This view is not yet available. We will be rolling out this policy in a future
release.

 1. Sign in to the Power Platform admin center.

 2. Select Policies > Environment policies.

 3. In Disable the environment after, select the number of days Power Platform
    should wait to disable a Dataverse for Teams environment that becomes
    inactive.

 4. In Delete the disabled environment after, select the number of days Power
    Platform should wait to delete a Dataverse for Teams environment that has
    been disabled.
    
    Note
    
    Ninety days is the maximum number of days you can set for Power Platform to
    wait to disable a Dataverse for Teams environment due to inactivity. The
    permissible range of values are: 15 days, 30 days, 45 days, 60 days, and 90
    days of inactivity.

 5. Select Save.
    
    


SEE ALSO

Microsoft Dataverse for Teams environments
Recover environment
Automatic environment cleanup









FEEDBACK

Submit and view feedback for

This product This page
View all page feedback

Theme
 * Light
 * Dark
 * High contrast

 * 
 * Previous Versions
 * Blog
 * Contribute
 * Privacy
 * Terms of Use
 * Trademarks
 * © Microsoft 2022


IN THIS ARTICLE




Theme
 * Light
 * Dark
 * High contrast

 * 
 * Previous Versions
 * Blog
 * Contribute
 * Privacy
 * Terms of Use
 * Trademarks
 * © Microsoft 2022