Skip to content

Commit 8db62d4

Browse files
author
RoseHJM
committed
Updated intro
1 parent 7101909 commit 8db62d4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/deployment-environments/how-to-schedule-environment-deletion.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,9 +17,9 @@ In this article, you learn how to set an expiration, or end date for a deploymen
1717

1818
Working with many deployment environments across multiple projects can be challenging. Scheduled deletion helps you manage your environments by automatically deleting them on a specific date at a specific time. Using automatic expiry and deletion helps you keep track of your active and inactive environments and helps you avoid paying for environments that you no longer need.
1919

20-
As a developer, you can schedule an environment for deletion when you create it. You can also change the expiration date and time for an environment that you created.
20+
As a developer, you can view and schedule the expiration dates for your environment through the developer portal. You can schedule an environment for deletion when you create it, or at a later time. You can also change the expiration date and time for an environment that you created.
2121

22-
As as dev team lead, you can schedule any environment in your project for deletion, regardless of who created it. You can also change the expiration date and time for any environment in your project.
22+
Deployment Environments provides platform engineers with a centralized way of viewing and managing deletion schedules for environments in Azure portal. As as user with Project Admin permissions, you can schedule any environment in your project for deletion, regardless of who created it. You can also change the expiration date and time for any environment in your project.
2323

2424
## Prerequisites
2525

0 commit comments

Comments
 (0)