Skip to content

Commit 053eb90

Browse files
committed
.
1 parent 03dd609 commit 053eb90

File tree

3 files changed

+10
-9
lines changed

3 files changed

+10
-9
lines changed
-23.2 KB
Loading
461 Bytes
Loading

articles/devtest-labs/network-isolation.md

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.date: 03/31/2025
1010

1111
# Configure network isolation for a lab in Azure DevTest Labs
1212

13-
Azure DevTest Labs creates all labs inside virtual networks. By default, DevTest Labs creates a new [Azure virtual network](/azure/virtual-network/virtual-networks-overview) for each lab, but you can also use an existing virtual network. The virtual network acts as a security boundary to isolate lab resources from the public internet.
13+
Azure DevTest Labs creates all labs inside [Azure virtual networks](/azure/virtual-network/virtual-networks-overview). The virtual network acts as a security boundary to isolate lab resources from the public internet. By default, DevTest Labs creates a new virtual network for each lab, but you can also use an existing virtual network.
1414

1515
If your organizational networking policies require it, you can isolate all lab resources to the lab's virtual network. This article walks you through how to use the Azure portal to create or configure a network-isolated lab in DevTest Labs.
1616

@@ -24,7 +24,7 @@ Network isolation lets you:
2424

2525
## Prerequisites
2626

27-
- Sufficient permissions to create labs in an Azure subscription.
27+
- **Owner** or **Contributor**-level permissions in the Azure subscription where you want to create the network-isolated lab.
2828

2929
## Enable network isolation
3030

@@ -50,9 +50,10 @@ To use a different, existing virtual network for the lab, and enable network iso
5050

5151
:::image type="content" source="./media/network-isolation/create-lab.png" alt-text="Screenshot that shows selecting a virtual network.":::
5252

53-
1. Select a subnet.
53+
1. Select a subnet in the virtual network.
54+
5455
:::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+
5657
1. Select **Yes** next to **Isolate lab resources**, and finish creating the lab.
5758

5859
If you enable network isolation for a different network than the default, complete the following instructions to configure service endpoints for network access.
@@ -70,7 +71,7 @@ If you enabled network isolation for a virtual network other than the default, c
7071

7172
You can also open the lab storage account from **Storage accounts** or the lab's resource group. 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`.
7273

73-
:::image type="content" source="./media/network-isolation/contoso-test.png" alt-text="Screenshot that shows selecting the lab storage account..":::
74+
:::image type="content" source="./media/network-isolation/contoso-test.png" alt-text="Screenshot that shows selecting the lab storage account.":::
7475

7576
1. On the storage account page, expand **Security + networking** and select **Networking** from the left navigation menu.
7677

@@ -116,23 +117,23 @@ You can automate these steps with PowerShell or Azure CLI to configure network i
116117

117118
1. Once the service endpoint is successfully enabled, select **Add**.
118119

119-
1. On the **Networking** page, make sure **Allow trusted Microsoft services to bypass this firewall** is selected under **Exceptions**, and select **Apply**.
120+
1. On the **Networking** page, make sure **Allow trusted Microsoft services to bypass this firewall** is selected under **Exception**, and select **Apply**.
120121

121122
:::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.":::
122123

123124
## Use a network-isolated lab
124125

125-
You must configure several other items to use a lab in a network isolated mode.
126+
To use a lab in a network isolated mode, you must configure several other items.
126127

127128
### Enable access to the storage account from outside the lab
128129

129-
The lab administrator must explicitly enable any 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.
130+
You must explicitly enable any access to the network isolated lab's storage account from an allowed endpoint, such as a local or virtual machine (VM). 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 VM and securely accessing the lab's storage account from that VM.
130131

131132
For more information, see [Connect to a storage account using an Azure Private Endpoint](/azure/private-link/tutorial-private-endpoint-storage-portal).
132133

133134
### Provide storage account to export lab usage data
134135

135-
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.
136+
To [export usage data](personal-data-delete-export.md) for a network isolated lab, you 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 you don't explicitly specify the storage account to use.
136137

137138
For more information, see [Export or delete personal data from Azure DevTest Labs](personal-data-delete-export.md).
138139

0 commit comments

Comments
 (0)