| title | description | services | documentationcenter | author | manager | editor | ms.service | ms.workload | ms.tgt_pltfrm | ms.devlang | ms.topic | ms.date | ms.author |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Connect to a peer network in Azure Lab Services | Microsoft Docs |
Learn how to connect your lab network with another network as a peer. For example, connect your on-premises organization/university network with Lab's virtual network in Azure. |
lab-services |
na |
spelluru |
lab-services |
na |
na |
na |
article |
05/15/2020 |
spelluru |
This article provides information about peering your labs network with another network.
Virtual network peering enables you to seamlessly connect Azure virtual networks. Once peered, the virtual networks appear as one, for connectivity purposes. The traffic between virtual machines in the peered virtual networks is routed through the Microsoft backbone infrastructure, much like traffic is routed between virtual machines in the same virtual network, through private IP addresses only. For more information, see Virtual network peering.
You may need to connect your lab's network with a peer virtual network in some scenarios including the following ones:
- The virtual machines in the lab have software that connects to on-premises license servers to acquire license.
- The virtual machines in the lab need access to data sets (or any other files) on university's network shares.
Certain on-premises networks are connected to Azure Virtual Network either through ExpressRoute or Virtual Network Gateway. These services must be set up outside of Azure Lab Services. To learn more about connecting an on-premises network to Azure using ExpressRoute, see ExpressRoute overview. For on-premises connectivity using a Virtual Network Gateway, the gateway, specified virtual network, and the lab account must all be in the same region.
Note
When creating a Azure Virtual Network that will be peered with a lab account, it's important to understand how the virtual network's region impacts where classroom labs are created. For more information, see the administrator guide's section on regions\locations.
During the new lab account creation, you can pick an existing virtual network that shows in the Peer virtual network dropdown list on the Advanced tab. The list will only show virtual networks in the same region as the lab account. The selected virtual network is connected (peered) to labs created under the lab account. All the virtual machines in labs that are created after the making this change will have access to the resources on the peered virtual network.
There is also an option to provide Address range for virtual machines for the labs. The address range property applies only if a peer virtual network is enabled for the lab. If the address range is provided, all the virtual machines in the labs under the lab account will be created in that address range. The address range should be in CIDR notation (for example, 10.20.0.0/20) and not overlap with any existing address ranges. When providing an address range, it's important to think about the number of labs that will be created and provide an address range to accommodate that. Lab Services assumes a maximum of 512 virtual machines per lab. For example, an ip range with '/23' can create only one lab. A range with a '/21' will allow for the creation of four labs.
If the Address range is not specified, Lab Services will use the default address range given to it by Azure when creating the virtual network to be peered with your virtual network. The range is often something like 10.x.0.0/16. This may lead to ip range overlap, so make sure to either specify an address range in the lab settings or check the address range of your virtual network being peered.
Note
Lab creation can fail if the lab account is peered to a virtual network but has too narrow of an IP address range. You can run out of space in the address range if there are too many labs in the lab account (each lab uses 512 addresses).
If the lab creation fails, contact your lab account owner/admin and request for the address range to be increased. The admin can increase the address range using steps mentioned in the Specify an address range for VMs in a lab account section.
The same property can be enabled from the Labs configuration tab of the Lab Account page if you didn't set up a peer network at the time of lab account creation. Change made to this setting applies only to the labs that are created after the change. As you can see in the image, you can enable or disable Peer virtual network for labs in the lab account.
When you select a virtual network for the Peer virtual network field, the Allow lab creator to pick lab location option is disabled. That's because labs in the lab account must be in the same region as the lab account for them to connect with resources in the peer virtual network.
Important
The peered virtual network setting applies only to labs that are created after the change is made, not to the existing labs.
The following procedure has steps to specify an address range for VMs in the lab. If you update the range that you previously specified, the modified address range applies only to VMs that are created after the change was made.
Here are some restrictions when specifying the address range that you should keep in mind.
- The prefix must be smaller than or equal to 23.
- If a virtual network is peered to the lab account, the provided address range cannot overlap with address range from peered virtual network.
-
On the Lab Account page, select Labs settings on the left menu.
-
For the Address range field, specify the address range for VMs that will be created in the lab. The address range should be in the classless inter-domain routing (CIDR) notation (example: 10.20.0.0/23). Virtual machines in the lab will be created in this address range.
-
Select Save on the toolbar.
See the following articles: