Skip to content

Commit cb7e5ca

Browse files
ShawnJacksonShawnJackson
committed
edit pass: microsoft-dev-box-docset-how-to
1 parent 5096121 commit cb7e5ca

File tree

4 files changed

+114
-94
lines changed

4 files changed

+114
-94
lines changed

‎articles/dev-box/how-to-configure-azure-compute-gallery.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ Use the following steps to manually assign each role.
105105
| **Assign access to** | Select **Managed Identity**. |
106106
| **Members** | Search for and select the user-assigned managed identity that you created when you [added a user-assigned identity to the dev center](#add-a-user-assigned-identity-to-dev-center). |
107107

108-
You can use the same managed identity in multiple dev centers and compute galleries. Any dev center with the managed identity added will have the necessary permissions to the images in the gallery that you've added the owner role assignment to.
108+
You can use the same managed identity in multiple dev centers and compute galleries. Any dev center with the managed identity added will have the necessary permissions to the images in the gallery that you've added the Owner role assignment to.
109109

110110
## Attach a gallery to a dev center
111111

‎articles/dev-box/how-to-customize-devbox-azure-image-builder.md

Lines changed: 26 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,9 @@ ms.topic: how-to
1414

1515
By using standardized virtual machine (VM) images, your organization can more easily migrate to the cloud and help ensure consistency in your deployments.
1616

17-
Images ordinarily include predefined security, configuration settings, and any necessary software. Setting up your own imaging pipeline requires time, infrastructure, and many other details. With Azure VM Image Builder, you can create a configuration that describes your image and submit it to the service, where the image is built and then distributed to a dev box project.
17+
Images ordinarily include predefined security, configuration settings, and any necessary software. Setting up your own imaging pipeline requires time, infrastructure, and many other details. With Azure VM Image Builder, you can create a configuration that describes your image. The service then builds the image and submits it to a dev box project.
1818

19-
In this article, you create a customized dev box using a template that includes a customization step to install Visual Studio Code (VS Code).
19+
In this article, you create a customized dev box by using a template. The template includes a customization step to install Visual Studio Code (VS Code).
2020

2121
Although it's possible to create custom VM images by hand or by using other tools, the process can be cumbersome and unreliable. VM Image Builder, which is built on HashiCorp Packer, gives you the benefits of a managed service.
2222

@@ -28,23 +28,23 @@ To reduce the complexity of creating VM images, VM Image Builder:
2828

2929
- Can fetch customization data from various sources, which removes the need to collect them all from one place.
3030

31-
- Can be integrated with Compute Gallery, which creates an image management system with which to distribute, replicate, version, and scale images globally. Additionally, you can distribute the same resulting image as a VHD or as one or more managed images, without having to rebuild them from scratch.
31+
- Can be integrated with Azure Compute Gallery. Compute Gallery creates an image management system with for distributing, replicating, versioning, and scaling images globally. Additionally, you can distribute the same resulting image as a virtual hard disk or as one or more managed images, without having to rebuild them from scratch.
3232

3333
## Prerequisites
3434

35-
To provision a custom image you've creating by using VM Image Builder, you need:
35+
To provision a custom image that you created by using VM Image Builder, you need:
3636

37-
- Owner or Contributor permissions on an Azure Subscription or a specific resource group.
38-
- A resource group
39-
- A dev center with an attached network connection. If you don't have a dev center with an attached network connection, follow the steps to attach the network connection in [Create a network connection](./quickstart-configure-dev-box-service.md#create-a-network-connection).
37+
- Owner or Contributor permissions on an Azure subscription or a specific resource group.
38+
- A resource group.
39+
- A dev center with an attached network connection. If you don't have a one, follow the steps in [Create a network connection](./quickstart-configure-dev-box-service.md#create-a-network-connection).
4040

41-
## Create a Windows image and distribute it to a compute gallery
41+
## Create a Windows image and distribute it to Azure Compute Gallery
4242

43-
The next step is to use Azure VM Image Builder and Azure PowerShell to create an image version in an Azure Compute Gallery (formerly Shared Image Gallery) and then distribute the image globally. You can also do this by using the Azure CLI.
43+
The next step is to use Azure VM Image Builder and Azure PowerShell to create an image version in Azure Compute Gallery (formerly Shared Image Gallery) and then distribute the image globally. You can also do this by using the Azure CLI.
4444

4545
1. To use VM Image Builder, you need to register the features.
4646

47-
Check your provider registrations. Make sure that each one returns Registered.
47+
Check your provider registrations. Make sure that each one returns `Registered`.
4848

4949
```powershell
5050
Get-AzResourceProvider -ProviderNamespace Microsoft.VirtualMachineImages | Format-table -Property ResourceTypes,RegistrationState
@@ -54,7 +54,7 @@ The next step is to use Azure VM Image Builder and Azure PowerShell to create an
5454
Get-AzResourceProvider -ProviderNamespace Microsoft.Network | Format-table -Property ResourceTypes,RegistrationState
5555
```
5656
57-
If they don't return Registered, register the providers by running the following commands:
57+
If the provider registrations don't return `Registered`, register the providers by running the following commands:
5858
5959
```powershell
6060
Register-AzResourceProvider -ProviderNamespace Microsoft.VirtualMachineImages
@@ -72,12 +72,12 @@ The next step is to use Azure VM Image Builder and Azure PowerShell to create an
7272
7373
3. Create variables to store information that you'll use more than once.
7474
75-
Copy the sample code and replace the Resource group with the resource group you have used to create the dev center.
75+
Copy the following sample code. Replace `<Resource group>` with the resource group that you used to create the dev center.
7676
7777
```powershell
7878
# Get existing context
7979
$currentAzContext = Get-AzContext
80-
# Get your current subscription ID.
80+
# Get your current subscription ID
8181
$subscriptionID=$currentAzContext.Subscription.Id
8282
# Destination image resource group
8383
$imageResourceGroup="<Resource group>"
@@ -91,10 +91,10 @@ The next step is to use Azure VM Image Builder and Azure PowerShell to create an
9191
9292
4. Create a user-assigned identity and set permissions on the resource group.
9393
94-
VM Image Builder uses the provided user-identity to inject the image into Azure Compute Gallery. In this example, you create an Azure role definition with specific actions for distributing the image. The role definition is then assigned to the user identity.
94+
VM Image Builder uses the provided user identity to inject the image into Azure Compute Gallery. The following example creates an Azure role definition with specific actions for distributing the image. The role definition is then assigned to the user identity.
9595
9696
```powershell
97-
# setup role def names, these need to be unique
97+
# Set up role def names, which need to be unique
9898
$timeInt=$(get-date -UFormat "%s")
9999
$imageRoleDefName="Azure Image Builder Image Def"+$timeInt
100100
$identityName="aibIdentity"+$timeInt
@@ -111,7 +111,7 @@ The next step is to use Azure VM Image Builder and Azure PowerShell to create an
111111
112112
5. Assign permissions for the identity to distribute the images.
113113
114-
Use this command to download an Azure role definition template, and then update it with the previously specified parameters.
114+
Use this command to download an Azure role definition template, and then update it with the previously specified parameters:
115115
116116
```powershell
117117
$aibRoleImageCreationUrl="https://raw.githubusercontent.com/azure/azvmimagebuilder/master/solutions/12_Creating_AIB_Security_Roles/aibRoleImageCreation.json"
@@ -129,9 +129,9 @@ The next step is to use Azure VM Image Builder and Azure PowerShell to create an
129129
New-AzRoleAssignment -ObjectId $identityNamePrincipalId -RoleDefinitionName $imageRoleDefName -Scope "/subscriptions/$subscriptionID/resourceGroups/$imageResourceGroup"
130130
```
131131
132-
## Create a compute gallery
132+
## Create a gallery
133133
134-
To use VM Image Builder with an Azure Compute Gallery, you need to have an existing gallery and image definition. VM Image Builder doesn't create the gallery and image definition for you. The definition created below will have Trusted Launch as security type and meets the windows 365 image requirements.
134+
To use VM Image Builder with Azure Compute Gallery, you need to have an existing gallery and image definition. VM Image Builder doesn't create the gallery and image definition for you. The following code creates a definition that has trusted launch as the security type and meets the Windows 365 image requirements.
135135
136136
```powershell
137137
# Gallery name
@@ -153,7 +153,7 @@ $features = @($SecurityType)
153153
New-AzGalleryImageDefinition -GalleryName $galleryName -ResourceGroupName $imageResourceGroup -Location $location -Name $imageDefName -OsState generalized -OsType Windows -Publisher 'myCompany' -Offer 'vscodebox' -Sku '1-0-0' -Feature $features -HyperVGeneration "V2"
154154
```
155155

156-
1. Copy the ARM template for Azure VM Image Builder. This template indicates the source image and also the customizations applied. With this template, we are installing choco and VS Code. It also indicates where the image will be distributed.
156+
1. Copy the following Azure Resource Manger template for VM Image Builder. This template indicates the source image and the customizations applied. This template installs Choco and VS Code. It also indicates where the image will be distributed.
157157

158158
```json
159159
{
@@ -233,7 +233,7 @@ New-AzGalleryImageDefinition -GalleryName $galleryName -ResourceGroupName $image
233233
}
234234
```
235235

236-
2. Configure the template with your variables.
236+
2. Configure the template with your variables:
237237

238238
```powershell
239239
$templateFilePath = <Template Path>
@@ -250,13 +250,13 @@ New-AzGalleryImageDefinition -GalleryName $galleryName -ResourceGroupName $image
250250

251251
3. Create the image version.
252252

253-
Your template must be submitted to the service. The following commands will download any dependent artifacts, such as scripts, and store them in the staging resource group, which is prefixed with IT_.
253+
Your template must be submitted to the service. The following commands download any dependent artifacts, such as scripts, and store them in the staging resource group. The staging resource group is prefixed with `IT_`.
254254

255255
```powershell
256256
New-AzResourceGroupDeployment -ResourceGroupName $imageResourceGroup -TemplateFile $templateFilePath -Api-Version "2020-02-14" -imageTemplateName $imageTemplateName -svclocation $location
257257
```
258258

259-
To build the image, invoke 'Run' on the template.
259+
To build the image, invoke `Run` on the template:
260260

261261
```powershell
262262
Invoke-AzResourceAction -ResourceName $imageTemplateName -ResourceGroupName $imageResourceGroup -ResourceType Microsoft.VirtualMachineImages/imageTemplates -ApiVersion "2020-02-14" -Action Run
@@ -269,17 +269,17 @@ New-AzGalleryImageDefinition -GalleryName $galleryName -ResourceGroupName $image
269269
Get-AzImageBuilderTemplate -ImageTemplateName $imageTemplateName -ResourceGroupName $imageResourceGroup | Select-Object -Property Name, LastRunStatusRunState, LastRunStatusMessage, ProvisioningState
270270
```
271271

272-
Alternatively, you can go to the Azure portal to your compute gallery > image definition to view the provisioning state of your image.
272+
Alternatively, you can view the provisioning state of your image in the Azure portal by going to your gallery and then the image definition.
273273

274-
![Provisioning state of the customized image version](./media/how-to-customize-devbox-azure-image-builder/image-version-provisioning-state.png)
274+
:::image type="content" source="media/how-to-customize-devbox-azure-image-builder/image-version-provisioning-state.png" alt-text="Screenshot that shows the provisioning state of the customized image version.":::
275275

276276
## Configure the gallery
277277

278-
After your custom image has been provisioned within the compute gallery, you can configure the gallery to use the images within the dev center. For more details, see [Configure Azure Compute Gallery](./how-to-configure-azure-compute-gallery.md).
278+
After your custom image has been provisioned in the gallery, you can configure the gallery to use the images in the dev center. For more information, see [Configure Azure Compute Gallery](./how-to-configure-azure-compute-gallery.md).
279279

280280
## Set up the Dev Box service with a custom image
281281

282-
After the compute gallery images are available in the dev center, you can use the custom image with the Dev Box service. For more details, see [Configure the Microsoft Dev Box Service](./quickstart-configure-dev-box-service.md).
282+
After the gallery images are available in the dev center, you can use the custom image with the Microsoft Dev Box Preview service. For more information, see [Quickstart: Configure Microsoft Dev Box Preview](./quickstart-configure-dev-box-service.md).
283283

284284
## Next steps
285285

‎articles/dev-box/how-to-dev-box-user.md

Lines changed: 14 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Provide access to dev box users
2+
title: Provide access for dev box users
33
titleSuffix: Microsoft Dev Box Preview
44
description: Learn how to provide access to projects for dev box users so that they can create and manage dev boxes.
55
services: dev-box
@@ -12,7 +12,7 @@ ms.topic: how-to
1212

1313
# Provide access to projects for dev box users
1414

15-
Team members must have access to a specific Microsoft Dev Box Preview project before they can create dev boxes. By using the built-in DevCenter Dev Box User role, you can assign permissions to Active Directory Users or Groups at the project level.
15+
Team members must have access to a specific Microsoft Dev Box Preview project before they can create dev boxes. By using the built-in DevCenter Dev Box User role, you can assign permissions to Active Directory users or groups at the project level.
1616

1717
[!INCLUDE [supported accounts note](./includes/note-supported-accounts.md)]
1818

@@ -27,30 +27,31 @@ A DevCenter Dev Box User can:
2727
## Assign permissions to dev box users
2828

2929
1. Sign in to the [Azure portal](https://portal.azure.com).
30-
31-
1. In the search box, type *Dev box* and select **Projects**.
3230

33-
1. Select the project you want to provide your team members access to.
34-
35-
:::image type="content" source="./media/how-to-dev-box-user/projects-grid.png" alt-text="Screenshot showing the list of existing projects.":::
31+
1. In the search box, enter **Dev box**. In the search results, select **Projects**.
32+
33+
1. Select the project that you want to give your team members access to.
34+
35+
:::image type="content" source="./media/how-to-dev-box-user/projects-grid.png" alt-text="Screenshot that shows a list of existing projects.":::
36+
37+
1. On the left menu, select **Access Control (IAM)**.
3638

37-
1. Select **Access Control (IAM)** from the left menu.
38-
3939
1. Select **Add** > **Add role assignment**.
4040

4141
1. Assign the following role. For detailed steps, see [Assign Azure roles using the Azure portal](../role-based-access-control/role-assignments-portal.md).
42-
42+
4343
| Setting | Value |
4444
| --- | --- |
4545
| **Role** | Select **DevCenter Dev Box User**. |
4646
| **Assign access to** | Select **User, group, or service principal**. |
47-
| **Members** | Select the users or groups you want to have access to the project. |
47+
| **Members** | Select the users or groups that you want to have access to the project. |
4848

49-
:::image type="content" source="media/how-to-dev-box-user/add-role-assignment-user.png" alt-text="Screenshot that shows the Add role assignment pane.":::
49+
:::image type="content" source="media/how-to-dev-box-user/add-role-assignment-user.png" alt-text="Screenshot that shows the pane for adding role assignments.":::
5050

51-
The user will now be able to view the project and all the pools within it. Dev box users can create dev boxes from any of the pools and manage those dev boxes from the [developer portal](https://aka.ms/devbox-portal).
51+
The user can now view the project and all the pools within it. Dev box users can create dev boxes from any of the pools and manage those dev boxes from the [developer portal](https://aka.ms/devbox-portal).
5252

5353
[!INCLUDE [dev box runs on creation note](./includes/note-dev-box-runs-on-creation.md)]
54+
5455
## Next steps
5556

5657
- [Quickstart: Create a dev box by using the developer portal](quickstart-create-dev-box.md)

0 commit comments

Comments
 (0)