Skip to content

Commit cc7e061

Browse files
committed
updates
1 parent 79341db commit cc7e061

File tree

2 files changed

+19
-1
lines changed

2 files changed

+19
-1
lines changed

articles/lab-services/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
items:
55
- name: Azure Lab Services retirement guide
66
href: retirement-guide.md
7-
- name: VM deletion policy
7+
- name: Deletion policy for virtual machines
88
href: vm-deletion-policy.md
99
- name: Find and delete lab resources
1010
href: find-delete-lab-resources.md
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
title: Deletion policy for virtual machines
3+
description: The VM deletion policy for Azure Lab Services
4+
ms.topic: overview
5+
ms.date: 04/23/2025
6+
7+
# customer intent: As an Azure Lab Services customer, I want to understand the VM deletion policy for Azure Lab Services.
8+
---
9+
10+
# Virtual machine deletion policy
11+
12+
[!INCLUDE [Retirement guide](./includes/retirement-banner.md)]
13+
14+
On June 9, 2025, Azure Lab Services will delete all virtual machines (VMs) that have been inactive since July 1, 2023.
15+
16+
A VM 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 VMs will also be deleted. This policy applies to template VMs and production VMs.
17+
18+
After the VMs are deleted, we will not be able to recover them or their data. Back up any required data from these inactive VMs, and then delete the VMs if you don't need them. Delete the VMs and the associated labs yourself to avoid incurring any unnecessary charges. Once the VMs are deleted, there is no way to recover the VMs or the data on them.

0 commit comments

Comments
 (0)