You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/devtest-labs/network-isolation.md
+38-32Lines changed: 38 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Network isolation
2
+
title: Create a network isolated lab
3
3
description: Learn how to enable and configure network isolation for labs in Azure DevTest Labs.
4
4
ms.topic: how-to
5
5
ms.author: rosemalcolm
@@ -8,46 +8,54 @@ ms.custom: UpdateFrequency2
8
8
ms.date: 03/31/2025
9
9
---
10
10
11
-
# Network isolation in Azure DevTest Labs
11
+
# Configure network isolation in Azure DevTest Labs
12
12
13
13
By default, Azure DevTest Labs creates a new [Azure virtual network](/azure/virtual-network/virtual-networks-overview) for each lab. The virtual network acts as a security boundary to isolate lab resources from the public internet.
14
14
15
15
If your organizational networking policies require it, you can isolate all lab resources to a selected virtual network. This article walks you through how to create or configure a network-isolated lab in DevTest Labs.
16
16
17
-
You can use these networking options:
17
+
You can use network isolation to implement these networking options:
18
18
19
19
- Isolate all lab [virtual machines (VMs)](devtest-lab-configure-vnet.md) and [environments](connect-environment-lab-virtual-network.md) in a preexisting virtual network that you select.
20
20
- Completely isolate the lab, including VMs, environments, the lab storage account, and key vaults, to a selected virtual network.
21
-
22
-
You can also join an Azure virtual network to an on-premises network to securely connect to on-premises resources. For more information, see [DevTest Labs enterprise reference architecture: Connectivity components](devtest-lab-reference-architecture.md#connectivity-components).
21
+
- Join an Azure virtual network to an on-premises network to securely connect to on-premises resources. For more information, see [DevTest Labs enterprise reference architecture: Connectivity components](devtest-lab-reference-architecture.md#connectivity-components).
23
22
24
23
## Prerequisites
25
24
26
25
-**Owner** or **Contributor** permissions in the Azure subscription that contains the lab.
27
26
28
27
## Enable network isolation
29
28
30
-
You can use the Azure portal to enable network isolation only during lab creation. To convert an existing lab and associated lab resources to isolated network mode, use the PowerShell script [Convert-DtlLabToIsolatedNetwork.ps1](https://github.com/Azure/azure-devtestlab/blob/master/Tools/ConvertDtlLabToIsolatedNetwork/Convert-DtlLabToIsolatedNetwork.ps1).
29
+
You can use the Azure portal to enable network isolation only during lab creation. To convert an existing lab and its resources to isolated network mode, use the PowerShell script [Convert-DtlLabToIsolatedNetwork.ps1](https://github.com/Azure/azure-devtestlab/blob/master/Tools/ConvertDtlLabToIsolatedNetwork/Convert-DtlLabToIsolatedNetwork.ps1).
31
30
32
31
During lab creation, you can enable network isolation for the default lab virtual network, or for another, preexisting virtual network that you use for the lab.
33
32
34
-
To enable network isolation for the lab:
33
+
## Enable network isolation for the default virtual network
34
+
35
+
To create the lab in the default virtual network and enable network isolation:
35
36
36
37
1. During [lab creation](devtest-lab-create-lab.md), select the **Networking** tab on the **Create DevTest Lab** screen.
37
-
1. On the **Networking** screen, **Default** appears next to **Virtual Network**.
38
+
1. On the **Networking** screen, leave **Virtual Network** set to **Default**. Select **Yes** next to **Isolate lab resources**, and finish creating the lab.
39
+
40
+
:::image type="content" source="./media/network-isolation/isolate-lab-resources.png" alt-text="Screenshot that shows enabling network isolation for the default network.":::
38
41
39
-
- To create the lab in the default virtual network and enable network isolation, select **Yes** next to **Isolate lab resources**, and finish creating the lab.
40
-
:::image type="content" source="./media/network-isolation/isolate-lab-resources.png" alt-text="Screenshot that shows enabling network isolation for the default network.":::
41
-
- To use a different, existing virtual network for the lab, and enable network isolation for that network:
42
-
1. Select a network other than **Default** from the dropdown list next to **Virtual Network**. The list only shows networks in the same region and subscription as the lab.
43
-
:::image type="content" source="./media/network-isolation/create-lab.png" alt-text="Screenshot that shows selecting a virtual network.":::
44
-
1. Select a subnet.
45
-
:::image type="content" source="./media/network-isolation/create-lab-subnet.png" alt-text="Screenshot that shows selecting a subnet and selecting Yes for network isolation.":::
46
-
1. Next to **Isolate lab resources**, select **Yes**, and finish creating the lab.
42
+
If you enable network isolation for the default network, no further action is needed. The lab handles isolating resources from now on.
47
43
48
-
If you enabled network isolation for the default network, no further action is needed. The lab handles isolating resources from now on.
44
+
## Enable network isolation for a different virtual network
49
45
50
-
If you enabled network isolation for a different network than the default, complete the following instructions to configure service endpoints for network access.
46
+
To use a different, existing virtual network for the lab, and enable network isolation for that network:
47
+
48
+
1. During [lab creation](devtest-lab-create-lab.md), select the **Networking** tab on the **Create DevTest Lab** screen.
49
+
1. On the **Networking** screen, select a network other than **Default** from the dropdown list next to **Virtual Network**. The list only shows networks in the same region and subscription as the lab.
50
+
51
+
:::image type="content" source="./media/network-isolation/create-lab.png" alt-text="Screenshot that shows selecting a virtual network.":::
52
+
53
+
1. Select a subnet.
54
+
:::image type="content" source="./media/network-isolation/create-lab-subnet.png" alt-text="Screenshot that shows selecting a subnet and selecting Yes for network isolation.":::
55
+
56
+
1. Select **Yes** next to **Isolate lab resources**, and finish creating the lab.
57
+
58
+
If you enable network isolation for a different network than the default, complete the following instructions to configure service endpoints for network access.
51
59
52
60
<aname="steps-to-follow-post-lab-creation"></a>
53
61
## Configure service endpoints
@@ -58,31 +66,29 @@ If you enabled network isolation for a virtual network other than the default, c
58
66
59
67
1. On the lab's **Overview** page, select **Resource visualizer**.
60
68
61
-

62
-
63
69
1. On the **Resource visualizer** page, select the lab's storage account. The lab storage account is named `a<labName><4-digit number>`. For example, if the lab name is `Fabrikam`, the storage account name could be `afabrikam1234`.
64
70
65
71

66
72
67
73
1. On the storage account page, expand **Security + networking** and select **Networking** from the left navigation menu.
68
74
69
-
1. On the **Firewalls and virtual networks** tab, ensure that:
70
-
-**Enabled from selected virtual networks and IP addresses** is selected.
71
-
-**Allow Azure services on the trusted services list to access this storage account** at the bottom of the page is selected. DevTest Labs is a [trusted Microsoft service](/azure/storage/common/storage-network-security#trusted-microsoft-services), so selecting this option lets the lab operate normally in a network isolated mode.
75
+
1. On the **Firewalls and virtual networks** tab, ensure that **Enabled from selected virtual networks and IP addresses** is selected, and select **Add existing virtual network**..
72
76
73
-
1. Select **Add existing virtual network**.
77
+
:::image type="content" source="./media/network-isolation/add-existing-virtual-network.png" alt-text="Screenshot that shows the resource group networking pane with add existing virtual network highlighted.":::
74
78
75
79
1. On the **Add networks** pane, select the virtual network and subnet you chose when you created the lab, and then select **Enable**.
76
80
77
-
:::image type="content" source="./media/network-isolation/add-existing-virtual-network.png" alt-text="Screenshot that shows the resource group networking pane with add existing virtual network highlighted.":::
81
+
:::image type="content" source="./media/network-isolation/contoso-lab.png" alt-text="Screenshot that shows the resource group networking pane with add existing virtual network highlighted.":::
78
82
79
83
1. Once the service endpoint is successfully enabled, select **Add**.
80
84
81
85
:::image type="content" source="./media/network-isolation/allow-trusted-services.png" alt-text="Screenshot that shows allowing trusted services access to a resource group.":::
82
86
83
-
1. On the **Networking** page, select **Save**.
87
+
1. On the **Networking** page, ensure that **Allow Azure services on the trusted services list to access this storage account** at the bottom of the page is selected. DevTest Labs is a [trusted Microsoft service](/azure/storage/common/storage-network-security#trusted-microsoft-services), so selecting this option lets the lab operate normally in a network isolated mode.
84
88
85
-
:::image type="content" source="./media/network-isolation/add-network-pane.png" alt-text="Screenshot that shows the added network with Save highlighted.":::
89
+
1. Select **Save**.
90
+
91
+
:::image type="content" source="./media/network-isolation/allow-trusted-services.png" alt-text="Screenshot that shows allowing trusted services access to a resource group.":::
86
92
87
93
Azure Storage now allows inbound connections from the added virtual network, which enables the lab to operate successfully in a network isolated mode.
88
94
@@ -107,24 +113,24 @@ You can automate these steps with PowerShell or Azure CLI to configure network i
107
113
:::image type="content" source="./media/network-isolation/key-vault-enable-network.png" alt-text="Screenshot that shows enabling a virtual network and subnet in a key vault.":::
108
114
109
115
1. Once the service endpoint is successfully enabled, select **Add**.
110
-
111
-
:::image type="content" source="./media/network-isolation/key-vault-add-network.png" alt-text="Screenshot that shows adding a virtual network and subnet in a key vault.":::
112
116
113
-
1. On the **Networking** page, select **Save**.
117
+
1. On the **Networking** page, select **Apply**.
118
+
119
+
:::image type="content" source="./media/network-isolation/key-vault-add-network.png" alt-text="Screenshot that shows adding a virtual network and subnet in a key vault.":::
114
120
115
121
## Use a network-isolated lab
116
122
117
123
Here are some things to remember when using a lab in a network isolated mode:
118
124
119
125
### Enable access to the storage account from outside the lab
120
126
121
-
The lab administrator must explicitly enable access to the network isolated lab's storage account from an allowed endpoint. Actions like uploading a VHD to the storage account for creating custom images require this access. You can enable access by creating a lab VM and securely accessing the lab's storage account from that VM.
127
+
The lab administrator must explicitly enable access to the network isolated lab's storage account from an allowed endpoint. Actions like uploading a virtual hard disk (VHD) to the storage account for creating custom images require this access. You can enable access by creating a lab virtual machine (VM) and securely accessing the lab's storage account from that VM.
122
128
123
129
For more information, see [Connect to a storage account using an Azure Private Endpoint](/azure/private-link/tutorial-private-endpoint-storage-portal).
124
130
125
131
### Provide storage account to export lab usage data
126
132
127
-
To [export usage data](personal-data-delete-export.md) for a network isolated lab, the lab owner must explicitly provide a storage account and generate a blob within the account to store the data. Exporting usage data fails in network isolated mode if the user doesn't explicitly provide the storage account to use.
133
+
To [export usage data](personal-data-delete-export.md) for a network isolated lab, the lab administrator must explicitly specify a storage account and generate a blob within the account to store the data. Exporting usage data fails in network isolated mode if the user doesn't explicitly specify the storage account to use.
128
134
129
135
For more information, see [Export or delete personal data from Azure DevTest Labs](personal-data-delete-export.md).
0 commit comments