Skip to content

Commit 2c87d35

Browse files
authored
Merge pull request #298704 from mijacobs/resources-deletion-notice
Add notice about resources deletion
2 parents 6ae7d6b + 5e77bea commit 2c87d35

File tree

2 files changed

+20
-0
lines changed

2 files changed

+20
-0
lines changed

articles/lab-services/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@
44
items:
55
- name: Azure Lab Services retirement guide
66
href: retirement-guide.md
7+
- name: Deletion policy for virtual machines
8+
href: vm-deletion-policy.md
79
- name: Find and delete lab resources
810
href: find-delete-lab-resources.md
911
- name: What is Azure Lab Services?
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 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.
17+
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.

0 commit comments

Comments
 (0)