Skip to content

Commit f790458

Browse files
committed
added to aditional articles
1 parent 0307982 commit f790458

File tree

3 files changed

+7
-1
lines changed

3 files changed

+7
-1
lines changed

articles/lab-services/find-delete-lab-resources.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,9 @@ ms.date: 12/05/2024
1313

1414
There are two versions of Azure Lab Services. Labs created from lab accounts use the older version, while labs created from lab plans use the newer version. This guide explains how to review lab resources, determine lab version, and delete unused resources.
1515

16+
> [!WARNING]
17+
> On June 9, 2025, we will delete all virtual machines (VMs) which have been inactive since July 1, 2023. 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. 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.
18+
1619
## Review labs
1720
A lab inventory can be found in the Azure portal under [Labs - Microsoft Azure](https://ms.portal.azure.com/#browse/Microsoft.LabServices%2Flabs).
1821
* Browse and manage deployed lab resources

articles/lab-services/lab-services-overview.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,9 @@ ms.date: 03/12/2024
1616

1717
Azure Lab Services enables you to create labs with infrastructure managed by Azure. The service handles all the infrastructure management, from spinning up virtual machines (VMs) to handling errors and scaling the infrastructure. For example, configure labs for specific class types, such as data science or general programming, and quickly assign lab users their dedicated lab virtual machine.
1818

19+
> [!WARNING]
20+
> On June 9, 2025, we will delete all virtual machines (VMs) which have been inactive since July 1, 2023. 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. 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.
21+
1922
To create, manage, and access labs in Azure Lab Services, use the dedicated Azure Lab Services website, or directly integrate labs in Microsoft Teams or the Canvas Learning Management System (LMS).
2023

2124
Azure Lab Services is designed with three major personas in mind: administrators, educators, and students. Take advantage of Azure Role-Based Access Control (RBAC) to grant the right access to the different personas in your organization. In this article, you learn about these personas and how to use Azure Lab Services for conducting classes.

articles/lab-services/retirement-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.date: 12/05/2024
1212
Azure Lab Services will be retired on June 28, 2027, but we strongly recommend that you start developing your retirement plan now to resolve pricing differences, secure necessary cores, and enhance the student experience with seamless in-browser labs and other key features offered by our recommended Microsoft and Azure partner solutions.
1313

1414
> [!WARNING]
15-
> On June 9, 2025, we will delete all virtual machines (VMs) which have been inactive since July 1st, 2023. 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. 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.
15+
> On June 9, 2025, we will delete all virtual machines (VMs) which have been inactive since July 1, 2023. 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. 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.
1616
1717
Transition your Azure Labs Services workflows to a Microsoft service or Microsoft partner solution by June 28, 2027. Azure Lab Services will be fully retired on this date.
1818

0 commit comments

Comments
 (0)