Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Update automatic-environment-cleanup.md #2736

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions power-platform/admin/automatic-environment-cleanup.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ Only developer and [Dataverse for Teams environments](inactive-teams-environment

### Timeline for unused environments

The time between the first warning that the environment will be disabled to the final deletion of the environment is 37 days. Production enviroments are not subject to this timeline.
The time between the first warning that the environment will be disabled to the final deletion of the environment is 37 days. Production environments are not subject to this timeline.

The environment's administrators and the user who created the environment are notified by email according to the schedule described in the following table.

Expand Down Expand Up @@ -105,7 +105,7 @@ By default, administrators have 30 days to re-enable an environment. If the envi
2. Select **Environments**, and then select **Recover deleted environments**.
3. Select an environment to recover, and then select **Recover**.

[Learn more about recovering environment](recover-environment.md).
[Learn more about recovering environments](recover-environment.md).

> [!NOTE]
> Recovering a Teams environment that was deleted due to inactivity requires a tenant-level administrative role.
Expand Down