|
1 | 1 | ---
|
2 | 2 | title: Understand shared IP addresses
|
3 |
| -description: Learn how Azure DevTest Labs uses shared IP addresses to minimize the public IP addresses required to access your lab VMs. |
| 3 | +description: Learn how Azure DevTest Labs uses shared IP addresses to minimize the public IP addresses you need to access your lab VMs. |
4 | 4 | ms.topic: how-to
|
5 |
| -ms.date: 06/26/2020 |
| 5 | +ms.date: 11/08/2021 |
6 | 6 | ---
|
7 | 7 |
|
8 | 8 | # Understand shared IP addresses in Azure DevTest Labs
|
9 | 9 |
|
10 |
| -Azure DevTest Labs lets lab VMs share the same public IP address to minimize the number of public IP addresses required to access your individual lab VMs. This article describes how shared IPs work and their related configuration options. |
| 10 | +Azure DevTest Labs virtual machines (VMs) can share the same public IP address, to minimize the number of public IPs you need to access lab VMs. This article describes how shared IPs work and how to configure shared IP options. |
11 | 11 |
|
12 |
| -## Shared IP setting |
| 12 | +## Shared IP settings |
13 | 13 |
|
14 |
| -When you create a lab, it's created in a subnet of a virtual network. By default, this subnet is created with **Enable shared public IP** set to *Yes*. This configuration creates one public IP address for the entire subnet. For more information about configuring virtual networks and subnets, see [Configure a virtual network in Azure DevTest Labs](devtest-lab-configure-vnet.md). |
| 14 | +Azure DevTest Labs creates labs in virtual networks that can have one or more subnets. The default subnet has **Enable shared public IP** set to **Yes**. This configuration creates one public IP address for the entire subnet. For more information about configuring virtual networks and subnets, see [Configure a virtual network in Azure DevTest Labs](devtest-lab-configure-vnet.md). |
15 | 15 |
|
16 | 16 | 
|
17 | 17 |
|
18 |
| -For existing labs, you can enable this option by selecting **Configuration and policies > Virtual Networks**. Then, select a virtual network from the list and choose **ENABLE SHARED PUBLIC IP** for a selected subnet. You can also disable this option in any lab if you don't want to share a public IP address across lab VMs. |
| 18 | +For existing labs, you can check or set this option by selecting **Configuration and policies** in the lab's left navigation, and then selecting **Virtual networks** under **External resources**. Select a virtual network from the list to see the shared IP settings for its subnets. |
19 | 19 |
|
20 |
| -Any VMs created in this lab default to using a shared IP. When creating the VM, this setting can be observed in the **Advanced settings** page under **IP address configuration**. |
| 20 | +To change the setting, select a subnet from the list, and then change **Enable shared public IP** to **Yes** or **No**. |
| 21 | + |
| 22 | +Any VMs you create in this subnet default to using a shared IP. When creating the VM, you can access this setting on the **Advanced settings** page next to **IP address**. |
21 | 23 |
|
22 | 24 | 
|
23 | 25 |
|
24 |
| -- **Shared:** All VMs created as **Shared** are placed into one resource group (RG). A single IP address is assigned for that RG and all VMs in the RG will use that IP address. |
25 |
| -- **Public:** Every VM you create has its own IP address and is created in its own resource group. |
26 |
| -- **Private:** Every VM you create uses a private IP address. You can't connect to this VM directly from the internet with Remote Desktop. |
| 26 | +- **Shared:** All VMs you create as **Shared** go into the same resource group. The resource group has one assigned IP address that all VMs in the resource group use. |
| 27 | +- **Public:** Every public VM has its own IP address and resource group. |
| 28 | +- **Private:** Every private VM uses a private IP address. You can't connect to these VMs from the internet by using Remote Desktop protocol (RDP). |
27 | 29 |
|
28 |
| -Whenever a VM with shared IP enabled is added to the subnet, DevTest Labs automatically adds the VM to a load balancer and assigns a TCP port number on the public IP address, forwarding to the RDP port on the VM. |
| 30 | +When you add a VM with shared IP to a subnet, DevTest Labs automatically adds the VM to a load balancer and assigns the VM a TCP port number on the public IP address. The port number forwards to the RDP port on the VM. |
29 | 31 |
|
30 |
| -## Using the shared IP |
| 32 | +## Use a shared IP |
31 | 33 |
|
32 |
| -- **Linux users:** SSH to the VM by using the IP address or fully qualified domain name, followed by a colon, followed by the port. For example, in the image below, the RDP address to connect to the VM is `mydevtestlab597975021002.eastus.cloudapp.azure.com:50661`. |
| 34 | +- **Linux users:** Secure shell (SSH) connect to the VM by using the IP address or fully qualified domain name, followed by a colon, followed by the port number. For example, the following screenshot shows an RDP connection address of `mydevtestlab597975021002.eastus.cloudapp.azure.com:50661`. |
33 | 35 |
|
34 | 36 | 
|
35 | 37 |
|
36 | 38 | - **Windows users:** Select the **Connect** button on the Azure portal to download a pre-configured RDP file and access the VM.
|
37 | 39 |
|
38 | 40 | ## Next steps
|
39 | 41 |
|
40 |
| -* [Define lab policies in Azure DevTest Labs](devtest-lab-set-lab-policy.md) |
41 |
| -* [Configure a virtual network in Azure DevTest Labs](devtest-lab-configure-vnet.md) |
| 42 | +- [Define lab policies in Azure DevTest Labs](devtest-lab-set-lab-policy.md) |
| 43 | +- [Configure a virtual network in Azure DevTest Labs](devtest-lab-configure-vnet.md) |
0 commit comments