Edit

Share via

Migrate from lab accounts to lab plans

  • Article

Important

Azure Lab Services will be retired on June 28, 2027. For more information, see the retirement guide.

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. Learn more about finding lab version.

Lab plans offer enhanced features such as improved performance, additional VM sizes, and enhanced student experience. There is no learning curve for students and teachers since the Labs Portal remains unchanged. Lab images can be reused from Azure Marketplace and Compute Gallery.

There are three key steps to adopt lab plans:

✅ Create a lab plan

✅ Request capacity for lab plans

✅ Create a lab

1. Create a lab plan

Review existing lab accounts in the Azure portal under the Lab configuration / Lab settings / Networking section and create lab plans for those that have virtual network peering disabled or labs no longer require connectivity to a specific network.

If virtual network peering is enabled, don’t upgrade to lab plans and focus on exploring recommended Microsoft and partner solutions to develop a retirement plan. Advanced networking scenarios can be complex and may require additional lead time.

Important

A lab plan’s resource group name is crucial because educators select it to create a lab. Similarly, a lab plan name is important. If multiple lab plans exist in the resource group, educators will choose from a dropdown when creating a lab.

2. Request capacity for lab plans

When using lab plans, you're assigned a dedicated VM cores quota per subscription. Initially, this quota is limited, so you need to request a core limit increase.

Important

A capacity request for lab plans is necessary since lab account VM cores are not automatically available with lab plans.

Capacity is assigned to your subscription and remains unaffected when creating or deleting lab plans. The first time you create a lab plan, a special Microsoft-managed Azure subscription is created internally to assign your dedicated VM lab capacity.

Request a core limit increase by opening an Azure support ticket with the required region, Lab VM size(s), and total number of cores needed.

3. Create a lab

Once you have capacity assigned to your subscription, you can create and publish representative labs to validate the educator and student experience.

Each VM size uses a newer Azure VM Compute SKU. If you use an attached compute gallery, validate your customized images with the new SKU by testing common student workloads. Before creating labs, verify that each image in the compute gallery is replicated to the same regions enabled in your lab plans.

Optional - Configure lab plans

While you're waiting for capacity to be assigned, you can continue creating lab plans that will be used for setting up your labs. The following table maps configurations with lab accounts to lab plans:

  1. Create and configure lab plans.
    • If you plan to use a license server, don't forget to enable advanced networking when creating your lab plans.
    • The lab plan’s resource group name is significant because educators will select the resource group to create a lab.
    • Likewise, the lab plan name is important. If more than one lab plan is in the resource group, educators will see a dropdown to choose a lab plan when they create a lab.
  2. Assign permissions to educators that will create labs.
  3. Enable Azure Marketplace images.
  4. Configure regions for labs. You should enable your lab plans to use the regions that you specified in your capacity request.
  5. Optionally, attach an Azure Compute Gallery.
  6. Optionally, configure integration with Canvas including adding the app and linking lab plans. Alternately, configure integration with Teams by adding the app to Teams groups.

If you're moving from lab accounts, the following table provides guidance on how to map your lab accounts to lab plans:

Lab account configuration Lab plan configuration
Role assignments
- Lab account owner\contributor.
- Lab creator\owner\contributor.		 Lab plans include new specialized roles.
1. Review roles.
2. Assign permissions.
Enabled Marketplace images.
- Lab accounts only support Gen1 images from the Marketplace.		 Lab plans include settings to enable Azure Marketplace images.
- Lab plans support Gen1 and Gen2 Marketplace images, so the list of images will be different than what you would see if using lab accounts.
Location
- Labs are automatically created within the same geolocation as the lab account.
- You can't specify the exact region where a lab is created.		 Lab plans enable specific control over which regions labs are created.
- Configure regions for labs.
Attached Azure Compute Gallery Lab plans can be attached to the same gallery used by lab accounts.
1. Attach an Azure Compute Gallery.
2. Ensure that you enable images for the lab plan.

Optional - Update cost management reports

Update reports to include the new cost entry type, Microsoft.LabServices/labs, for labs created using lab plans. Built-in and custom tags allow for grouping in cost analysis. For more information about tracking costs, see Cost management for Azure Lab Services.

Difference between lab plans and lab accounts

between the two concepts. A lab plan is a set of configurations and settings for labs you create from it. Also, a lab is now an Azure resource in its own right and a sibling resource to lab plans. Learn more about the difference between lab plans and lab accounts.

If you're moving from lab accounts to lab plans, there's likely to be a time when you're using both your existing lab accounts and using the newer lab plans. Both are still supported, can coexist in your Azure subscription, and can even share the same external resources.

Next steps