Skip to content

Commit 8198352

Browse files
Revise VM deletion policy details
Updated the VM deletion policy to clarify the timeline and process for automatic deletions.
1 parent fef5a3e commit 8198352

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

articles/lab-services/vm-deletion-policy.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,12 +11,12 @@ ms.date: 04/23/2025
1111

1212
[!INCLUDE [Retirement guide](./includes/retirement-banner.md)]
1313

14-
On June 9, 2025, Azure Lab Services will delete all virtual machines (VMs) that have been inactive since July 1, 2023.
14+
Starting June 9, 2025, Azure Lab Services will automatically delete any virtual machines (VMs) that have been inactive for more than two years, as part of a monthly cleanup process.
1515

1616
A virtual machine is considered inactive if no operations were performed on it. These operations include actions such as starting, stopping, resetting passwords, and reimaging. Any associated labs for these virtual machines will also be deleted. This policy applies to template VMs and production VMs.
1717

1818
After the virtual machines are deleted, we won't be able to recover them or their data.
1919

2020
**Recommended actions**:
2121
1. Back up any required data from your inactive virtual machines.
22-
1. Delete the virtual machines and the associated labs to avoid incurring any unnecessary charges.
22+
1. Delete the virtual machines and the associated labs to avoid incurring any unnecessary charges.

0 commit comments

Comments
 (0)