Tutorial: Set up lab to lab communication with advanced networking

Azure Lab Services advanced networking enables you to control the network for labs created using lab plans. You can use advanced networking to implement various scenarios including connecting to licensing servers, using hub-spoke model for Azure Networking, or lab to lab communication. In this tutorial, you set up lab-to-lab communication for a web development class.

After you complete this tutorial, you'll have a lab with two lab virtual machines that are able to communicate with each other: a server VM and a client VM.

Learn more about the supported networking scenarios in Azure Lab Services.

In this tutorial, you learn how to:

Prerequisites

• An Azure account with an active subscription. If you don't have an Azure subscription, create a free account before you begin.

• An Azure account with permission to create and manage resources in the subscription, such as the Contributor or Owner Azure RBAC role.

Create a resource group

A resource group is a logical container into which Azure resources, such as web apps, databases, and storage accounts, are deployed and managed. For example, you can choose to delete the entire resource group in one simple step later.

The following steps show how to use the Azure portal to create a resource group. For simplicity, you create all resources for this tutorial in the same resource group.

1. Sign in to the Azure portal.
2. Select Resource groups.
3. Select + Create from the top menu.
4. On the Basics tab of the Create a resource group page, do the following actions:
   1. For Subscription, choose the subscription in which you want to create your labs.
   2. For Resource group, type MyResourceGroup.
   3. For Region, select the region closest to you. For more information about available regions, see Azure geographies.
5. Select Review + Create.
6. Review the summary, and select Create.

Create a virtual network and subnet

The following steps show how to use the Azure portal to create a virtual network and subnet that can be used with Azure Lab Services.

1. Open MyResourceGroup created previously.

2. Select + Create in the upper left corner of the Azure portal and search for "virtual network".

3. Select the Virtual network tile and then select Create.

4. On the Basics tab of the Create virtual network, do the following actions:

   1. For Subscription, choose the same subscription as the resource group.
   2. For Resource group, choose MyResourceGroup.
   3. For Name, enter MyVirtualNetwork.
   4. For Region, choose region that is also supported by Azure Lab Services. For more information about supported regions, see Azure Lab Services by region.
   5. Select Next: IP Addresses.

   

5. On the IP Addresses tab, create a subnet that is used by the labs.

   1. Select + Add subnet
   2. For Subnet name, enter labservices-subnet.
   3. For Subnet address range, enter range in CIDR notation. For example, 10.0.1.0/24 has enough IP addresses for 251 lab VMs. (Azure reserves five IP addresses for every subnet.) To create a subnet with more available IP addresses for VMs, use a different CIDR prefix length. For example, 10.0.0.0/20 would have room for over 4000 IP addresses for lab VMs. For more information about adding subnets, see Add a subnet.
   4. Select OK.

6. Select Review + Create.

   

7. Once validation passes, select Create.

Delegate subnet to Azure Lab Services

Next, you configure the subnet to be used with Azure Lab Services. To use a subnet with Azure Lab Services, the subnet must be delegated to the service.

1. Open the MyVirtualNetwork resource.
2. Select the Subnets item on the left menu.
3. Select labservices-subnet subnet.
4. Under the Subnet delegation section, select Microsoft.LabServices/labplans for the Delegate subnet to a service setting.
5. Select Save.

Create a network security group

You can use an NSG to control traffic to one or more virtual machines (VMs), role instances, network adapters (NICs), or subnets in your virtual network. An NSG contains access control rules that allow or deny traffic based on traffic direction, protocol, source address and port, and destination address and port. The rules of an NSG can be changed at any time, and changes are applied to all associated instances.

For more information about NSGs, visit what is an NSG.

An NSG is required when using advanced networking in Azure Lab Services.

To create an NSG, complete the following steps:

1. Select + Create a Resource in the upper left corner of the Azure portal and search for "network security group".
2. Select the Network security group tile and then select Create.
3. On the Basics tab, of the Create network security group, do the following actions:
   1. For Subscription, choose the same subscription as used previously.
   2. For Resource group, choose MyResourceGroup.
   3. For the Name, enter MyNsg.
   4. For Region, choose same region as MyVirtualNetwork that was created previously.
   5. Select Review + Create.
4. When validation passes, select Create.

Update the network security group inbound rules

To ensure that lab users can use remote desktop to connect to the lab VMs, you need to create a security rule to allow this type of traffic. When you use Linux, you need to adapt the rule for SSH.

To create a rule that allows both RDP and SSH traffic for the subnet you created previously:

1. Open MyNsg.

2. Select Inbound security rules on the left menu.

3. Select + Add from the top menu bar. Fill in the details for adding the inbound security rule as follows:

   1. For Source, select Any.
   2. For Source port ranges, select *.
   3. For Destination, select IP Addresses.
   4. For Destination IP addresses/CIDR ranges, select subnet range from labservices-subnet created previously.
   5. For Service, select Custom.
   6. For Destination port ranges, enter 22, 3389. Port 22 is for Secure Shell protocol (SSH). Port 3389 is for Remote Desktop Protocol (RDP).
   7. For Protocol, select Any.
   8. For Action, select Allow.
   9. For Priority, select 1000. Priority must be higher than other Deny rules for RDP and/or SSH.
   10. For Name, enter AllowRdpSshForLabs.
   11. Select Add.

   

4. Wait for the rule to be created.

5. Select Refresh on the menu bar. The new rule now shows in the list of rules.

Associate network security group to virtual network

You now have an NSG with an inbound security rule to allow lab VMs to connect to the virtual network.

To associate the NSG with the virtual network you created earlier:

1. Open MyVirtualNetwork.
2. Select Subnets on the left menu.
3. Select + Associate from the top menu bar.
4. On the Associate subnet page, do the following actions:
   1. For Virtual network, select MyVirtualNetwork.
   2. For Subnet, select labservices-subnet.
   3. Select OK.

Create a lab plan using advanced networking

Now that the virtual network is created and configured, you can create the lab plan:

1. Select Create a resource in the upper left-hand corner of the Azure portal.

2. Search for lab plan.

3. On the Lab plan tile, select the Create dropdown and choose Lab plan.

   

4. On the Basics tab of the Create a lab plan page, do the following actions:

   1. For Azure subscription, select the subscription used earlier.
   2. For Resource group, select an existing resource group or select Create new, and enter a name for the new resource group.
   3. For Name, enter a lab plan name. For more information about naming restrictions, see Microsoft.LabServices resource name rules.
   4. For Region, select a location/region in which you want to create the lab plan.

   

5. Select Next: Networking.

6. On the Networking tab, do the following actions:

   1. Check Enable advanced networking.
   2. For Virtual network, choose MyVirtualNetwork.
   3. For Subnet, choose labservices-subnet.
   4. Select Review + Create.

   

7. When the validation succeeds, select Create.

Create two labs

Next, create two labs that use advanced networking. These labs use the labservices-subnet that's associated with Azure Lab Services. Any lab VMs created using MyLabPlan can communicate with each other. Communication can be restricted by using NSGs, firewalls, and more.

Perform the following steps to create both labs. Repeat these steps the server VM and the client VM.

1. Navigate to the Azure Lab Services website: https://labs.azure.com.

2. Select Sign in and enter your credentials. Azure Lab Services supports organizational accounts and Microsoft accounts.

3. Select MyResourceGroup from the dropdown on the menu bar.

4. Select New lab.

   

5. In the New Lab window, do the following actions:

   1. Specify a name. The name should be easily identifiable. Use MyServerLab for the lab with the server VMs and MyClientLab for the lab with the client VMs. For more information about naming restrictions, see Microsoft.LabServices resource name rules.
   2. Choose a virtual machine image. For this tutorial, use Windows 11 Pro, but you can choose another available image if you want. For more information about enabling virtual machine images, see Specify Marketplace images available to lab creators.
   3. For size, select Medium.
   4. Region only has one region. When a lab uses advanced networking, the lab must be in the same region as the associated subnet.
   5. Select Next.

   

6. On the Virtual machine credentials page, specify default administrator credentials for all VMs in the lab. Specify the name and password for the administrator. By default all the lab VMs have the same password as the one specified here. Select Next.

   

   Important

   Make a note of user name and password. They won't be shown again.

7. On the Lab policies page, leave the default selections and select Next.

8. On the Template virtual machine settings window, leave the selection on Create a template virtual machine. Select Finish.

   

9. You should see the following screen that shows the status of the template VM creation.

   

10. Wait for the template VM to be created.

Enable ICMP on the lab templates

Once the labs are created, enable ICMP (ping) for testing communication between the lab VMs. First, enable ICMP on the template VMs for both labs. Enabling ICMP on the template VM also enables it on the lab VMs. Once the labs are published, the lab VMs are able to ping each other.

To enable ICMP, complete the following steps for each template VM in each lab.

1. On the Template page for the lab, start and connect to the template VM.

   1. Select Start template.

   

   Note

   Template VMs incur cost when running, so ensure that the template VM is shutdown when you don’t need it to be running.

   1. Once the template is started, select Connect to template.

   

When you're logged in to the template VM, modify the firewall rules on the VM to allow ICMP. Because you're using Windows 11, you can use PowerShell and the Enable-NetFilewallRule cmdlet. To open a PowerShell window:

1. Select the Start button.
2. Type "PowerShell"
3. Select the Windows PowerShell app.

Run the following code:

Enable-NetFirewallRule -Name CoreNet-Diag-ICMP4-EchoRequest-In
Enable-NetFirewallRule -Name CoreNet-Diag-ICMP4-EchoRequest-Out

On the Template page for the lab, select Stop to stop the template VM.

Publish both labs

In this step, you publish the lab. When you publish the template VM, Azure Lab Services creates VMs in the lab by using the template. All virtual machines have the same configuration as the template.

1. On the Template page, select Publish.

   

2. Enter the number of machines that are needed for the lab, then select Publish.

   

   Warning

   Publishing is an irreversible action! It can't be undone.

3. You see the status of publishing the template page. Wait until the publishing is complete.

Test communication between lab VMs

In this section, confirm that the two lab virtual machines in different labs are able to communicate with each other.

First, start and connect to a lab VM from each lab. Complete the following steps for each lab.

1. Open the lab in the Azure Lab Services website.

2. Select Virtual machine pool on the left menu.

3. Select a single VM listed in the virtual machine pool.

4. Take note of the Private IP Address for the VM. You need the private IP addresses of both the server lab and client lab VMs later.

5. Select the State slider to change the state from Stopped to Starting.

   Note

   When an lab educator starts a lab VM, quota for the lab user isn't affected. Quota for a user specifies the number of lab hours available to a lab user outside of the scheduled class time. For more information on quotas, see Set quotas for users.

6. Once the State is Running, select the connect icon for the running VM. Open the download RDP file to connect to the VM. For more information about connection experiences on different operating systems, see Connect to a lab VM.

Now, use the ping utility to test cross-lab communication. From the lab VM in the server lab, open a command prompt. Use ping {ip-address}. The {ip-address} is the Private IP Address of the client VM, that you noted previously. This test can also be done from the lab VM from the client lab to the lab VM in the server lab.

When done, navigate to the Virtual machine pool page for each lab, select the lab VM and select the State slider to stop the lab VM.

Clean up resources

If you're not going to continue to use this application, delete the virtual network, network security group, lab plan and labs with the following steps:

1. In the Azure portal, select the resource group you want to delete.
2. Select Delete resource group.
3. To confirm the deletion, type the name of the resource group

Troubleshooting

Lab creation fails with You are not authorized to access this resource

When you create a new lab plan, it might take a few minutes for the permissions to propagate to the lab level. You can assign the Lab Creator role at the resource group level to prevent this behavior:

1. In the Azure portal, go to the resource group that contains the lab plan.
2. Select Access control (IAM) from the left navigation.
3. Select Add > Add role assignment.
4. Assign the Lab Creator role to the user account.

Next steps