Skip to content

Commit 0a1c696

Browse files
authored
Merge pull request #229582 from ShawnJackson/microsoft-dev-box-docset
[AQ] edit pass: Microsoft Dev Box docset (conceptual and quickstart articles)
2 parents b430044 + 1e69b2e commit 0a1c696

8 files changed

+303
-272
lines changed

articles/dev-box/concept-dev-box-concepts.md

Lines changed: 33 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -8,35 +8,50 @@ author: RoseHJM
88
ms.author: rosemalcolm
99
ms.topic: conceptual
1010
ms.date: 10/12/2022
11-
ms.custom: template-concept
11+
ms.custom: template-concept
12+
#Customer intent: As a developer, I want to understand Dev Box concepts and terminology so that I can set up a Dev Box environment.
1213
---
1314

14-
<!--
15-
Customer intent:
16-
As a developer I want to understand Dev Box concepts and terminology so that I can set up Dev Box environment.
17-
-->
1815
# Microsoft Dev Box Preview key concepts
1916

20-
This article describes the key concepts and components of Microsoft Dev Box.
17+
This article describes the key concepts and components of Microsoft Dev Box Preview.
18+
19+
## Dev box
20+
21+
A dev box is a preconfigured, ready-to-code workstation that you create through the self-service developer portal. A new dev box has all the tools, binaries, and configuration required for a dev box user to be productive immediately. You can create and manage multiple dev boxes to work on multiple workstreams.
22+
23+
As a dev box user, you have control over your own dev boxes. You can create more as you need them and delete them when you finish using them.
2124

2225
## Dev center
2326

24-
A dev center is a collection of projects that require similar settings. Dev centers enable dev infrastructure managers to manage the images and SKUs available to the projects using [dev box definitions](concept-dev-box-concepts.md#dev-box-definition) and configure the networks the development teams consume using [network connections](./concept-dev-box-concepts.md#network-connection).
25-
## Projects
27+
A dev center is a collection of projects that require similar settings. Dev centers enable dev infrastructure managers to:
28+
29+
- Manage the images and SKUs available to the projects by using dev box definitions.
30+
- Configure the networks that the development teams consume by using network connections.
31+
32+
## Project
33+
34+
A project is the point of access for development team members. When you associate a project with a dev center, all the settings at the dev center level are applied to the project automatically.
35+
36+
Each project can be associated with only one dev center. Dev managers can configure the dev boxes available for a project by specifying the dev box definitions that are appropriate for their workloads.
2637

27-
A project is the point of access for the development team members. When you associate a project with a dev center, all the settings at the dev center level will be applied to the project automatically. Each project can be associated with only one dev center. Dev managers can configure the dev boxes available for the project by specifying the [dev box definitions](./concept-dev-box-concepts.md#dev-box-definition) appropriate for their workloads.
2838
## Dev box definition
2939

30-
A dev box definition specifies a source image and size, including compute size and storage size. You can use a source image from the marketplace, or a custom image from your own [Azure Compute Gallery](./how-to-configure-azure-compute-gallery.md). You can use dev box definitions across multiple projects in a dev center.
40+
A dev box definition specifies a source image and size, including compute size and storage size. You can use a source image from Azure Marketplace or a custom image from your own [Azure Compute Gallery](./how-to-configure-azure-compute-gallery.md) instance. You can use dev box definitions across multiple projects in a dev center.
41+
42+
## Network connection
43+
44+
IT administrators and dev infrastructure managers configure the network that's used for dev box creation in accordance with their organizational policies. Network connections store configuration information, like Active Directory join type and virtual network, that dev boxes use to connect to network resources.
45+
46+
When you're creating a network connection, you must choose the Active Directory join type:
47+
48+
- If your dev boxes need to connect exclusively to cloud-based resources, use native Azure Active Directory (Azure AD).
49+
- If your dev boxes need to connect to on-premises resources and cloud-based resources, use hybrid Azure AD.
3150

32-
## Network connection
51+
To learn more about native Azure AD join and hybrid Azure AD join, see [Plan your Azure Active Directory device deployment](../active-directory/devices/plan-device-deployment.md).
3352

34-
IT administrators and dev infrastructure managers configure the network used for dev box creation in accordance with their organizational policies. Network connections store configuration information like Active Directory join type and virtual network that dev boxes use to connect to network resources.
53+
The virtual network specified in a network connection also determines the region for a dev box. You can create multiple network connections based on the regions where you support developers. You can then use those connections when you're creating dev box pools to ensure that dev box users create dev boxes in a region close to them. Using a region close to the dev box user provides the best experience.
3554

36-
When creating a network connection, you must choose whether to use a native Azure Active Directory (Azure AD) join or a hybrid Azure AD join. If your dev boxes need to connect exclusively to cloud-based resources, use a native Azure AD join. Use a hybrid Azure AD join if your dev boxes need to connect to on-premises resources and cloud-based resources. To learn more about Azure AD and hybrid Azure AD joined devices, [Plan your Azure Active Directory device deployment](../active-directory/devices/plan-device-deployment.md).
37-
The virtual network specified in a network connection also determines the region for the dev box. You can create multiple network connections based on the regions where you support developers and use them when creating different dev box pools to ensure dev box users create a dev box in a region close to them. Using a region close to the dev box user provides the best experience.
55+
## Dev box pool
3856

39-
## Dev box pool
40-
A dev box pool is a collection of dev boxes that you manage together and to which you apply similar settings. You can create multiple dev box pools to support the needs of hybrid teams working in different regions or on different workloads.
41-
## Dev box
42-
A dev box is a preconfigured ready-to-code workstation that you create through the self-service developer portal. The new dev box has all the tools, binaries, and configuration required for a dev box user to be productive immediately. You can create and manage multiple dev boxes to work on multiple work streams. As a dev box user, you have control over your own dev boxes - you can create more as you need them and delete them when you have finished using them.
57+
A dev box pool is a collection of dev boxes that you manage together and to which you apply similar settings. You can create multiple dev box pools to support the needs of hybrid teams that work in different regions or on different workloads.

articles/dev-box/includes/note-dev-box-runs-on-creation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,4 +7,4 @@ ms.service: dev-box
77
---
88

99
> [!IMPORTANT]
10-
> A dev box is automatically started and running when the creation process completes. Dev boxes incur costs whenever they are running.
10+
> A dev box is automatically started and running when the creation process finishes. Dev boxes incur costs whenever they're running.

articles/dev-box/includes/note-permission-to-create-dev-box.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,4 +7,4 @@ ms.service: dev-box
77
---
88

99
> [!IMPORTANT]
10-
> A user that's assigned the Dev Box User role or the Project Admin role can create a dev box.
10+
> A user who is assigned the Dev Box User role or the Project Admin role can create a dev box.

articles/dev-box/index.yml

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -32,14 +32,14 @@ landingContent:
3232
linkLists:
3333
- linkListType: quickstart
3434
links:
35-
- text: Configure the Microsoft Dev Box service
35+
- text: Configure Microsoft Dev Box
3636
url: quickstart-configure-dev-box-service.md
37-
- text: Create a Dev Box
37+
- text: Create a dev box
3838
url: quickstart-create-dev-box.md
3939
- text: Use the Remote Desktop client to connect to a dev box
4040
url: quickstart-connect-to-dev-box-with-remote-desktop-app.md
4141
# Card
42-
- title: Provide access to dev box
42+
- title: Provide access to Microsoft Dev Box
4343
linkLists:
4444
- linkListType: how-to-guide
4545
links:
@@ -53,17 +53,17 @@ landingContent:
5353
linkLists:
5454
- linkListType: how-to-guide
5555
links:
56-
- text: Configure an Azure Compute Gallery
56+
- text: Configure Azure Compute Gallery
5757
url: how-to-configure-azure-compute-gallery.md
58-
- text: Provision a custom image with Azure Image Builder
58+
- text: Provision a custom image by using Azure VM Image Builder
5959
url: how-to-customize-devbox-azure-image-builder.md
6060

6161
# Card
62-
- title: Reference docs
62+
- title: References
6363
linkLists:
6464
- linkListType: reference
6565
links:
66-
- text: CLI
66+
- text: Azure CLI
6767
url: https://learn.microsoft.com/en-us/azure/dev-box/cli-reference-subset
6868
- text: REST API
6969
url: https://aka.ms/dev-box/restapidocs

0 commit comments

Comments
 (0)