Skip to content

Commit bd27620

Browse files
authored
Merge pull request #298736 from mijacobs/resources-deletion-notificatio-revisions
Minor updates to VM deletion notification
2 parents 5ad7fbe + 5e0fc5a commit bd27620

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

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

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,10 @@ ms.date: 04/23/2025
1313

1414
On June 9, 2025, Azure Lab Services will delete all virtual machines (VMs) that have been inactive since July 1, 2023.
1515

16-
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.
16+
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

18-
After the virtual machines are deleted, we won't be able to recover them or their data. Back up any required data from these inactive virtual machines, and then delete the virtual machines if you don't need them. Delete the virtual machines and the associated labs yourself to avoid incurring any unnecessary charges. Once the virtual machines are deleted, there's no way to recover the virtual machines or the data on them.
18+
After the virtual machines are deleted, we won't be able to recover them or their data.
19+
20+
**Recommended actions**:
21+
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.

0 commit comments

Comments
 (0)