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/quickstart-configure-dev-box-service.md
+24-24Lines changed: 24 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.custom: references_regions
14
14
15
15
# Quickstart: Configure Microsoft Dev Box Preview
16
16
17
-
This quickstart describes how to configure the Microsoft Dev Box Preview service by using the Azure portal to enable development teams to self-serve dev boxes.
17
+
This quickstart describes how to configure Microsoft Dev Box Preview by using the Azure portal to enable development teams to self-serve their dev boxes.
18
18
19
19
This quickstart takes you through the process of setting up your Dev Box environment. You create a dev center to organize your dev box resources, configure network components to enable dev boxes to connect to your organizational resources, and create a dev box definition that will form the basis of your dev boxes. You then create a project and a dev box pool, which work together to help you give access to users who will manage or use the dev boxes.
20
20
@@ -26,8 +26,7 @@ To complete this quickstart, you need:
26
26
27
27
- An Azure account with an active subscription. If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
28
28
- Owner or Contributor role on an Azure subscription or a specific resource group.
29
-
- An existing virtual network and subnet. If you don't have them, [follow these instructions to create them](#create-a-virtual-network-and-subnet).
30
-
- Network Contributor permissions on an existing virtual network (Owner or Contributor), or permission to create a new virtual network and subnet.
29
+
-- Network Contributor permissions on an existing virtual network (Owner or Contributor), or permission to create a new virtual network and subnet.
31
30
- User licenses. To use Dev Box Preview, each user must be licensed for Windows 11 Enterprise or Windows 10 Enterprise, Microsoft Intune, and Azure Active Directory (Azure AD) P1. These licenses are available independently and are included in the following subscriptions:
32
31
33
32
- Microsoft 365 F3
@@ -36,13 +35,8 @@ To complete this quickstart, you need:
36
35
- Microsoft 365 Business Premium
37
36
- Microsoft 365 Education Student Use Benefit
38
37
-[Azure Hybrid Benefit](https://azure.microsoft.com/pricing/hybrid-benefit/), which allows you to use your Windows licenses on Azure with Dev Box.
39
-
- A configured and working Azure AD join or hybrid Active Directory join:
40
-
41
-
- To learn how to join devices directly to Azure AD, see [Plan your Azure Active Directory join deployment](../active-directory/devices/azureadjoin-plan.md).
42
-
- To learn how to join your AD DS domain-joined computers to Azure AD from an on-premises Azure Active Directory Domain Services (AD DS) environment, see [Plan your hybrid Azure Active Directory join deployment](../active-directory/devices/hybrid-azuread-join-plan.md).
43
-
- Certain ports to be open so that the Dev Box service can function, if your organization routes egress traffic through a firewall. For more information, see [Network requirements](/windows-365/enterprise/requirements-network).
44
-
45
-
## Create a dev center
38
+
- Certain ports to be open so that the Dev Box service can function if your organization routes egress traffic through a firewall. For more information, see [Network requirements](/windows-365/enterprise/requirements-network).
39
+
## 1. Create a dev center
46
40
47
41
Use the following steps to create a dev center so that you can manage your dev box resources:
48
42
@@ -83,7 +77,7 @@ Use the following steps to create a dev center so that you can manage your dev b
83
77
84
78
1. When the deployment is complete, select **Go to resource**. Confirm that the dev center page appears.
85
79
86
-
## Create a network connection
80
+
## 2. Create a network connection
87
81
88
82
Network connections determine the region in which dev boxes are deployed. They also allow dev boxes to be connected to your existing virtual networks. The following steps show you how to create and configure a network connection in Microsoft Dev Box Preview.
89
83
@@ -114,13 +108,19 @@ You must have a virtual network and subnet available for your network connection
114
108
115
109
1. Select **Create**.
116
110
117
-
### Create the connection
111
+
### Create the network connection
112
+
113
+
You now need a network connection to associate the virtual network and subnet with the dev center. A network connection specifies the type of join dev boxes use to join your Azure AD domain, either an Azure AD join or a hybrid Active Directory join.
118
114
119
-
You now need a network connection to associate the virtual network and subnet with the dev center. To create the connection, complete the steps on the relevant tab.
115
+
- To determine which type of join is appropriate for your dev boxes, refer to:
116
+
117
+
-[Azure AD joined devices](https://https://learn.microsoft.com/en-us/azure/active-directory/devices/concept-azure-ad-join).
118
+
-[Hybrid Azure AD joined devices](https://https://learn.microsoft.com/en-us/azure/active-directory/devices/concept-azure-ad-join-hybrid).
119
+
To create the connection, complete the steps on the relevant tab.
120
120
121
121
#### [Azure AD join](#tab/AzureADJoin/)
122
122
123
-
1. Sign in to the [Azure portal](https://portal.azure.com).
123
+
1.1.1.Sign in to the [Azure portal](https://portal.azure.com).
124
124
125
125
1. In the search box, enter **network connections**. In the list of results, select **Network connections**.
126
126
@@ -181,8 +181,7 @@ You now need a network connection to associate the virtual network and subnet wi
181
181
1. When the deployment is complete, select **Go to resource**. The network connection appears on the **Network connections** page.
182
182
183
183
---
184
-
185
-
## Attach a network connection to a dev center
184
+
## 3. Attach a network connection to a dev center
186
185
187
186
To provide network configuration information for dev boxes, associate a network connection with a dev center:
188
187
@@ -192,7 +191,7 @@ To provide network configuration information for dev boxes, associate a network
192
191
193
192
1. Select the dev center that you created, and then select **Networking**.
194
193
195
-
1. Select **+ Add**.
194
+
1. Select **+ Add**.
196
195
197
196
1. On the **Add network connection** pane, select the network connection that you created, and then select **Add**.
198
197
@@ -202,7 +201,7 @@ After you attach a network connection, the Azure portal runs several health chec
202
201
203
202
To resolve any errors, see [Troubleshoot Azure network connections](/windows-365/enterprise/troubleshoot-azure-network-connection).
204
203
205
-
## Create a dev box definition
204
+
## 4. Create a dev box definition
206
205
207
206
Dev box definitions define the image and SKU (compute + storage) that will be used in creation of the dev boxes. To create and configure a dev box definition:
208
207
@@ -226,7 +225,7 @@ Dev box definitions define the image and SKU (compute + storage) that will be us
226
225
227
226
1. Select **Create**.
228
227
229
-
## Create a project
228
+
## 5. Create a project
230
229
231
230
Dev box projects enable you to manage team-level settings. These settings include providing access to development teams so that developers can create dev boxes.
232
231
@@ -260,7 +259,7 @@ To create and configure a project in a dev box:
260
259
261
260
1. Verify that the project appears on the **Projects** page.
262
261
263
-
## Create a dev box pool
262
+
## 6. Create a dev box pool
264
263
265
264
A dev box pool is a collection of dev boxes that have similar settings. Dev box pools specify the dev box definitions and network connections that dev boxes will use. You must associate at least one pool with your project before users can create a dev box.
266
265
@@ -301,7 +300,7 @@ The Azure portal deploys the dev box pool and runs health checks to ensure that
301
300
302
301
:::image type="content" source="./media/quickstart-configure-dev-box-service/dev-box-pool-grid-populated.png" alt-text="Screenshot that shows a list of dev box pools and status information.":::
303
302
304
-
## Provide access to a dev box project
303
+
## 7. Provide access to a dev box project for developers
305
304
306
305
Before users can create dev boxes based on the dev box pools in a project, you must provide access for them through a role assignment. The Dev Box User role enables dev box users to create, manage, and delete their own dev boxes. You must have sufficient permissions to a project before you can add users to it.
The Microsoft Dev Box Preview service makes it possible for you to delegate administration of projects to a member of the project team. Project administrators can assist with the day-to-day management of projects for their teams, like creating and managing dev box pools. To give users permissions to manage projects, assign the DevCenter Project Admin role to them.
339
+
Microsoft Dev Box Preview makes it possible for you to delegate administration of projects to a member of the project team. Project administrators can assist with the day-to-day management of projects for their teams, like creating and managing dev box pools. To give users permissions to manage projects, assign the DevCenter Project Admin role to them.
341
340
342
-
You can assign the DevCenter Project Admin role by using the steps described earlier in [Provide access to a dev box project](#provide-access-to-a-dev-box-project), but select the Project Admin role instead of the Dev Box User role. For more information, see [Provide access to projects for project admins](how-to-project-admin.md).
341
+
You can assign the DevCenter Project Admin role by using the steps described earlier in [Provide access to a dev box ](#provide-access-to-a-dev-box-project)project and select the Project Admin role instead of the Dev Box User role. For more information, see [Provide access to projects for project admins](how-to-project-admin.md).
0 commit comments