How to create a lab with a shared resource in Azure Lab Services
This article references features available since the August 2022 Update, when lab plans replaced lab accounts. For more information, see What's New in the August 2022 Update.
If using a version of Azure Lab Services prior to the August 2022 Update, see How to create a lab with a shared resource in Azure Lab Services when using lab accounts.
When you're creating a lab, there might be some resources that need to be shared among all the students in a lab. For example, you have a licensing server or SQL Server for a database class. This article will discuss the steps to enable the shared resource for a lab. We'll also talk about how to limit access to the shared resource.
As shown in the diagram below we'll have a lab plan with a lab. The lab plan will have advanced networking enabled. In our example, the virtual network for the lab is the same network of the shared resource. Optionally, routing maybe used to connect lab VMs to shared resources in other subnets. The lab VMs can connect using the private IP of the shared server. Also, the virtual network is in the same region as the lab plan and lab.
Set up shared resource
The virtual network for the shared resource must be created before the lab plan or lab is created. For more information on how to create a virtual network and subnets, see create a virtual network and create a subnet. Planning out virtual network ranges is an important step when designing your network. For more information about planning your network, see the plan virtual networks article.
The shared resource can be software running on a virtual machine or an Azure provided service. The shared resource should be available through private IP address. By making the shared resource available through private IP only, you limit access to that shared resource.
The diagram also shows a network security group (NSG) which can be used to restrict traffic coming from the student VM. For example, you can write a security rule that states traffic from the student VM's IP addresses can only access one shared resource and nothing else. For more information on how to set security rules, see manage network security group.
If your shared resource is an Azure virtual machine running necessary software, you might have to modify the default firewall rules for the virtual machine.
To use a shared resource, the lab plan must be set up to use advanced networking. For more information, see Connect to your virtual network in Azure Lab Services. In this case, Lab Services will inject lab VM networking resources into the virtual network that holds the shared resource.
Advanced networking must be enabled during lab plan creation. It can't be added later.
When your lab plan is set to use advanced networking, the template VM and student VMs should now have access to the shared resource. You might have to update the virtual network's network security group, virtual network's user-defined routes or server's firewall rules.
One of the most common shared resources is a license server. The following list has a few tips to successfully configure a server.
Advanced networking must be enabled when the lab plan is created.
The license server needs to be located in the same region as the lab plan and virtual network.
By default virtual machines have a dynamic private ip. Before you setup any software, set the private ip to static.
Controlling access to the license server is key. When the VM is set up, access will still be needed for maintenance, troubleshooting, and updating. Following are a few ways for controlling access:
As an administrator, create a lab plan with advanced networking.
Submit and view feedback for