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/dev-box/how-to-configure-network-connections.md
+78-62Lines changed: 78 additions & 62 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
1
---
2
2
title: Configure network connections
3
3
titleSuffix: Microsoft Dev Box
4
-
description: Learn how to manage network connections for a dev center in Microsoft Dev Box. Use network connections to connect to virtual network or enable connecting to on-premises resources from a dev box.
4
+
description: Learn how to manage network connections for a dev center in Microsoft Dev Box. Connect to a virtual network or enable connecting to on-premises resources.
5
5
services: dev-box
6
6
ms.service: dev-box
7
7
author: RoseHJM
8
8
ms.author: rosemalcolm
9
-
ms.date: 04/25/2023
9
+
ms.date: 12/20/2023
10
10
ms.topic: how-to
11
11
#Customer intent: As a platform engineer, I want to be able to manage network connections so that I can enable dev boxes to connect to my existing networks and deploy them in the desired region.
12
12
---
@@ -19,22 +19,25 @@ You can choose to deploy dev boxes to a Microsoft-hosted network associated with
19
19
20
20
You need to add at least one network connection to a dev center in Microsoft Dev Box.
21
21
22
-
When you're planning network connectivity for your dev boxes, you must:
22
+
## Prerequisites
23
+
24
+
- Sufficient permissions to enable creating and configuring network connections.
25
+
- At least one virtual network and subnet available for your dev boxes.
26
+
27
+
When you're planning network connectivity for your dev boxes, consider the following points:
23
28
24
-
- Ensure that you have sufficient permissions to create and configure network connections.
25
-
- Ensure that you have at least one virtual network and subnet available for your dev boxes.
26
29
- Identify the region or location that's closest to your dev box users. Deploying dev boxes into a region that's close to users gives them a better experience.
27
30
- Determine whether dev boxes should connect to your existing networks by using Microsoft Entra join or Microsoft Entra hybrid join.
28
31
29
-
##Permissions
32
+
### Verify your permissions
30
33
31
-
To manage a network connection, you need the following permissions:
34
+
To manage a network connection, confirm that you have the following permissions:
32
35
33
-
|Action|Permissions required|
34
-
|-----|-----|
35
-
|Create and configure a virtual network and subnet|Network Contributor permissions on an existing virtual network (Owner or Contributor), or permission to create a new virtual network and subnet.|
36
-
|Create or delete a network connection|Owner or Contributor permissions on an Azure subscription or on a specific resource group, which includes permission to create a resource group.|
37
-
|Add or remove a network connection |Write permission on the dev center.|
36
+
|Action| Role |Permissions required|
37
+
|---|---|---|
38
+
|_Create and configure a virtual network and subnet_|**Network Contributor** (**Owner** or **Contributor**) | Permissions on an existing virtual network or permission to create a new virtual network and subnet|
39
+
|_Create or delete a network connection_|**Owner** or **Contributor**| Permissions on an Azure subscription or on a specific resource group, which includes permission to create a resource group|
40
+
|_Add or remove a network connection_|**Contributor**| Permission to perform **Write** actions on the dev center|
38
41
39
42
## Create a virtual network and subnet
40
43
@@ -49,16 +52,16 @@ To create a network connection, you need an existing virtual network and subnet.
49
52
1. On the **Create virtual network** pane, on the **Basics** tab, enter the following values:
50
53
51
54
| Setting | Value |
52
-
|------- |----- |
55
+
|---|---|
53
56
|**Subscription**| Select your subscription. |
54
-
|**Resource group**| Select an existing resource group. Or create a new one by selecting **Create new**, entering **rg-name**, and then selecting **OK**. |
55
-
|**Name**| Enter *VNet-name*. |
57
+
|**Resource group**| Select an existing resource group, or create a new one by selecting **Create new**, entering a name, and then selecting **OK**. |
58
+
|**Name**| Enter a name for the virtual network. |
56
59
|**Region**| Select the region for the virtual network and dev boxes. |
57
60
58
-
:::image type="content" source="./media/how-to-manage-network-connection/example-basics-tab.png" alt-text="Screenshot of the Basics tab on the pane for creating a virtual network in the Azure portal." border="true":::
61
+
:::image type="content" source="./media/how-to-manage-network-connection/example-basics-tab.png" alt-text="Screenshot of the Basics tab on the pane for creating a virtual network in the Azure portal." lightbox="./media/how-to-manage-network-connection/example-basics-tab.png":::
59
62
60
-
> [!Important]
61
-
> The region that you select for the virtual network is the where the dev boxes will be deployed.
63
+
> [!IMPORTANT]
64
+
> The region you select for the virtual network is the where Azure deploys the dev boxes.
62
65
63
66
1. On the **IP Addresses** tab, accept the default settings.
64
67
@@ -78,98 +81,111 @@ If your organization routes egress traffic through a firewall, you need to open
78
81
79
82
The following sections show you how to create and configure a network connection in Microsoft Dev Box.
80
83
81
-
### Types of Active Directory join
82
-
83
-
Microsoft Dev Box requires a configured and working Active Directory join, which defines how dev boxes join your domain and access resources. There are two choices:
84
-
85
-
-**Microsoft Entra join**: If your organization uses Microsoft Entra ID, you can use a Microsoft Entra join (sometimes called a native Microsoft Entra join). Dev box users sign in to Microsoft Entra joined dev boxes by using their Microsoft Entra account and access resources based on the permissions assigned to that account. Microsoft Entra join enables access to cloud-based and on-premises apps and resources.
84
+
### Review types of Active Directory join
86
85
87
-
For more information, see [Plan your Microsoft Entra join deployment](../active-directory/devices/device-join-plan.md).
88
-
-**Microsoft Entra hybrid join**: If your organization has an on-premises Active Directory implementation, you can still benefit from some of the functionality in Microsoft Entra ID by using Microsoft Entra hybrid joined dev boxes. These dev boxes are joined to your on-premises Active Directory instance and registered with Microsoft Entra ID.
86
+
Microsoft Dev Box requires a configured and working Active Directory join, which defines how dev boxes join your domain and access resources. There are two choices: Microsoft Entra join and Microsoft Entra hybrid join.
89
87
90
-
Microsoft Entra hybrid joined dev boxes require network line of sight to your on-premises domain controllers periodically. Without this connection, devices become unusable.
88
+
-**Microsoft Entra join**. If your organization uses Microsoft Entra ID, you can use a Microsoft Entra join (sometimes called a _native_ Microsoft Entra join). Dev box users sign in to Microsoft Entra joined dev boxes by using their Microsoft Entra account. They access resources based on the permissions assigned to that account. Microsoft Entra join enables access to cloud-based and on-premises apps and resources. For more information, see [Plan your Microsoft Entra join deployment](../active-directory/devices/device-join-plan.md).
91
89
92
-
For more information, see [Plan your Microsoft Entra hybrid join deployment](../active-directory/devices/hybrid-join-plan.md).
90
+
-**Microsoft Entra hybrid join**. If your organization has an on-premises Active Directory implementation, you can still benefit from some of the functionality in Microsoft Entra ID by using Microsoft Entra hybrid joined dev boxes. These dev boxes are joined to your on-premises Active Directory instance and registered with Microsoft Entra ID. Microsoft Entra hybrid joined dev boxes require network line of sight to your on-premises domain controllers periodically. Without this connection, devices become unusable. For more information, see [Plan your Microsoft Entra hybrid join deployment](../active-directory/devices/hybrid-join-plan.md).
93
91
94
92
### Create a network connection
95
93
96
94
Follow the steps on the relevant tab to create your network connection.
97
95
96
+
<!-- Rose: For the first setting, Domain join type, in the Azure portal, the UI still shows the options as:
97
+
- Azure active directory join
98
+
- Hybrid Azure active directory join
99
+
100
+
"Microsoft Entra join" and "Microsoft Entra Hybrid join" are't shown.
101
+
Should we ignore these differences, add a note, or change this topic to show the current UI?
102
+
I recently did some screenshot updates for the Entra ID rebrand for SQL using the updated UI in the portal.
103
+
I'm surprised this section of the UI is still showing the old product name.
104
+
-->
105
+
106
+
98
107
<aname='azure-ad-join'></a>
99
108
100
-
####[**Microsoft Entra join**](#tab/AzureADJoin/)
109
+
# [**Microsoft Entra join**](#tab/AzureADJoin/)
101
110
102
111
1. Sign in to the [Azure portal](https://portal.azure.com).
103
112
104
-
1. In the search box, enter **network connections**. In the list of results, select **Network connections**.
113
+
1. In the search box, enter **network connections**. In the list of results, select **Network Connections**.
105
114
106
115
1. On the **Network Connections** page, select **Create**.
107
116
108
-
:::image type="content" source="./media/how-to-manage-network-connection/network-connections-empty.png" alt-text="Screenshot that shows the Create button on the page for network connections.":::
117
+
:::image type="content" source="./media/how-to-manage-network-connection/network-connections-empty.png" alt-text="Screenshot that shows the Create button on the page for network connections." lightbox="./media/how-to-manage-network-connection/network-connections-empty.png":::
109
118
110
119
1. On the **Create a network connection** pane, on the **Basics** tab, enter the following values:
|**Subscription**|Select the subscription in which you want to create the network connection.|
125
+
|**Resource group**|Select an existing resource group, or select **Create new** and then enter a name for the new resource group.|
126
+
|**Name**|Enter a descriptive name for the network connection.|
127
+
|**Virtual network**|Select the virtual network that you want the network connection to use.|
128
+
|**Subnet**|Select the subnet that you want the network connection to use.|
120
129
121
-
:::image type="content" source="./media/how-to-manage-network-connection/create-native-network-connection-full-blank.png" alt-text="Screenshot that shows the Basics tab on the pane for creating a network connection, with the option for Microsoft Entra join selected.":::
130
+
:::image type="content" source="./media/how-to-manage-network-connection/create-native-network-connection-full-blank.png" alt-text="Screenshot that shows the Basics tab on the pane for creating a network connection, with the option for Microsoft Entra join selected." lightbox="./media/how-to-manage-network-connection/create-native-network-connection-full-blank.png":::
122
131
123
132
1. Select **Review + Create**.
124
133
125
134
1. On the **Review** tab, select **Create**.
126
135
127
-
1. When the deployment is complete, select **Go to resource**. Confirm that the connection appears on the **Network connections** page.
136
+
1. When the deployment completes, select **Go to resource**. Confirm the connection appears on the **Network Connections** page.
1. Sign in to the [Azure portal](https://portal.azure.com).
134
143
135
-
1. In the search box, enter **network connections**. In the list of results, select **Network connections**.
144
+
1. In the search box, enter **network connections**. In the list of results, select **Network Connections**.
136
145
137
146
1. On the **Network Connections** page, select **Create**.
138
147
139
-
:::image type="content" source="./media/how-to-manage-network-connection/network-connections-empty.png" alt-text="Screenshot that shows the Create button on the page that lists network connections.":::
148
+
:::image type="content" source="./media/how-to-manage-network-connection/network-connections-empty.png" alt-text="Screenshot that shows the Create button on the page that lists network connections." lightbox="./media/how-to-manage-network-connection/network-connections-empty.png":::
140
149
141
150
1. On the **Create a network connection** pane, on the **Basics** tab, enter the following values:
|**Subscription**|Select the subscription in which you want to create the network connection.|
147
-
|**ResourceGroup**|Select an existing resource group, or select **Create new** and then enter a name for the new resource group.|
148
-
|**Name**|Enter a descriptive name for the network connection.|
149
-
|**Virtual network**|Select the virtual network that you want the network connection to use.|
150
-
|**Subnet**|Select the subnet that you want the network connection to use.|
151
-
|**AD DNS domain name**| Enter the DNS name of the Active Directory domain that you want to use for connecting and provisioning Cloud PCs. For example: `corp.contoso.com`. |
152
-
|**Organizational unit**| Enter the organizational unit (OU). An OU is a container within an Active Directory domain that can hold users, groups, and computers. |
153
-
|**AD username UPN**| Enter the username, in user principal name (UPN) format, that you want to use for connecting Cloud PCs to your Active Directory domain. For example: `[email protected]`. This service account must have permission to join computers to the domain and the target OU (if one is set). |
154
-
|**AD domain password**| Enter the password for the user. |
155
-
156
-
:::image type="content" source="./media/how-to-manage-network-connection/create-hybrid-network-connection-full-blank.png" alt-text="Screenshot that shows the Basics tab on the pane for creating a network connection, with the option for Microsoft Entra hybrid join selected.":::
|**Subscription**|Select the subscription in which you want to create the network connection.|
156
+
|**ResourceGroup**|Select an existing resource group, or select **Create new** and then enter a name for the new resource group.|
157
+
|**Name**|Enter a descriptive name for the network connection.|
158
+
|**Virtual network**|Select the virtual network that you want the network connection to use.|
159
+
|**Subnet**|Select the subnet that you want the network connection to use.|
160
+
|**AD DNS domain name**| Enter the DNS name of the Active Directory domain that you want to use for connecting and provisioning Cloud PCs. For example: `corp.contoso.com`. |
161
+
|**Organizational unit**| Enter the organizational unit (OU). An OU is a container within an Active Directory domain that can hold users, groups, and computers. |
162
+
|**AD username UPN**| Enter the username, in user principal name (UPN) format, that you want to use for connecting Cloud PCs to your Active Directory domain. For example: `[email protected]`. This service account must have permission to join computers to the domain and the target OU (if one is set). |
163
+
|**AD domain password**| Enter the password for the user. |
164
+
165
+
:::image type="content" source="./media/how-to-manage-network-connection/create-hybrid-network-connection-full-blank.png" alt-text="Screenshot that shows the Basics tab on the pane for creating a network connection, with the option for Microsoft Entra hybrid join selected." lightbox="./media/how-to-manage-network-connection/create-hybrid-network-connection-full-blank.png":::
157
166
158
167
1. Select **Review + Create**.
159
168
160
169
1. On the **Review** tab, select **Create**.
161
170
162
-
1. When the deployment is complete, select **Go to resource**. Confirm that the connection appears on the **Network connections** page.
171
+
1. When the deployment completes, select **Go to resource**. Confirm the connection appears on the **Network connections** page.
163
172
164
173
---
165
174
166
-
>[!NOTE]
175
+
>[!NOTE]
167
176
> Microsoft Dev Box automatically creates a resource group for each network connection, which holds the network interface cards (NICs) that use the virtual network assigned to the network connection. The resource group has a fixed name based on the name and region of the network connection. You can't change the name of the resource group, or specify an existing resource group.
168
177
169
178
## Attach a network connection to a dev center
170
179
171
180
You need to attach a network connection to a dev center before you can use it in projects to create dev box pools.
172
181
182
+
<!-- Rose: I'm not able to fully repro the creation process for the network connection.
183
+
As such, I'm not able to full repro the following steps to attach the connection to a dev center.
184
+
The network connection process fails during validation. My permissions are fine.
185
+
It might be a join issue with the Microsoft domain.
186
+
If you want me to try other options to complete the process, I'll need more assistance.
187
+
-->
188
+
173
189
1. Sign in to the [Azure portal](https://portal.azure.com).
174
190
175
191
1. In the search box, enter **dev centers**. In the list of results, select **Dev centers**.
@@ -180,13 +196,13 @@ You need to attach a network connection to a dev center before you can use it in
180
196
181
197
1. On the **Add network connection** pane, select the network connection that you created earlier, and then select **Add**.
182
198
183
-
:::image type="content" source="./media/how-to-manage-network-connection/add-network-connection.png" alt-text="Screenshot that shows the pane for adding a network connection.":::
199
+
:::image type="content" source="./media/how-to-manage-network-connection/add-network-connection.png" alt-text="Screenshot that shows the pane for adding a network connection." lightbox="./media/how-to-manage-network-connection/add-network-connection.png":::
184
200
185
201
After you attach a network connection, the Azure portal runs several health checks on the network. You can view the status of the checks on the resource overview page.
186
202
187
203
:::image type="content" source="./media/how-to-manage-network-connection/network-connection-grid-populated.png" alt-text="Screenshot that shows the status of a network connection.":::
188
204
189
-
You can add network connections that pass all health checks to a dev center and use them to create dev box pools. Dev boxes within dev box pools are created and domain joined in the location of the virtual network that's assigned to the network connection.
205
+
You can add network connections that pass all health checks to a dev center and use them to create dev box pools. Dev boxes within dev box pools are created and domain joined in the location of the virtual network assigned to the network connection.
190
206
191
207
To resolve any errors, see [Troubleshoot Azure network connections](/windows-365/enterprise/troubleshoot-azure-network-connection).
192
208
@@ -204,7 +220,7 @@ You can remove a network connection from a dev center if you no longer want to u
204
220
205
221
:::image type="content" source="./media/how-to-manage-network-connection/remove-network-connection.png" alt-text="Screenshot that shows the Remove button on the network connection page.":::
206
222
207
-
1.Read the warning message, and then select **OK**.
223
+
1.Review the warning message, and then select **OK**.
208
224
209
225
The network connection is no longer available for use in the dev center.
0 commit comments