Skip to content

Commit bcfbe80

Browse files
author
RoseHJM
committed
MDB - Image builder update
1 parent 93a9bc4 commit bcfbe80

File tree

1 file changed

+9
-11
lines changed

1 file changed

+9
-11
lines changed

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

Lines changed: 9 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -7,27 +7,25 @@ ms.service: dev-box
77
ms.custom: devx-track-azurepowershell
88
author: RoseHJM
99
ms.author: rosemalcolm
10-
ms.date: 01/02/2024
10+
ms.date: 10/22/2024
1111
ms.topic: how-to
12+
ai-usage: ai-assisted
1213
---
1314

1415
# Configure a dev box by using Azure VM Image Builder and Microsoft Dev Box
1516

1617
In this article, you use Azure VM Image Builder to create a customized dev box in Microsoft Dev Box by using a template. The template includes a customization step to install Visual Studio Code (VS Code).
1718

18-
When your organization uses standardized virtual machine (VM) images, it can more easily migrate to the cloud and help ensure consistency in your deployments. 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.
19+
Using standardized virtual machine (VM) images helps you ensure consistent deployments as you migrate to the cloud. These images can include predefined security, configuration settings, and necessary software. Setting up an imaging pipeline can be time-consuming and complex. Azure VM Image Builder simplifies this process by allowing you to create a configuration for your image, which the service then builds and submits to a dev box project.
1920

20-
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.
21+
Creating custom VM images manually or with other tools can be difficult and unreliable. VM Image Builder, which is built on HashiCorp Packer, offers the advantages of a managed service.
2122

22-
To reduce the complexity of creating VM images, VM Image Builder:
23+
To simplify VM image creation, VM Image Builder:
2324

24-
- Removes the need to use complex tooling, processes, and manual steps to create a VM image. VM Image Builder abstracts out all these details and hides Azure-specific requirements, such as the need to generalize the image (Sysprep). And it gives more advanced users the ability to override such requirements.
25-
26-
- Works with existing image build pipelines for a click-and-go experience. You can call VM Image Builder from your pipeline or use an Azure VM Image Builder service DevOps task.
27-
28-
- Fetches customization data from various sources, which removes the need to collect them all from one place.
29-
30-
- Integrates with Azure Compute Gallery, which creates an image management system 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.
25+
- Eliminates the need for complex tools, processes, and manual steps. It abstracts these details and hides Azure-specific needs, like generalizing the image (Sysprep), while allowing advanced users to override if necessary.
26+
- Works with existing image build pipelines. You can call VM Image Builder from your pipeline or use an Azure VM Image Builder service DevOps task.
27+
- Gathers customization data from various sources, so you don't have to collect it all in one place.
28+
- Integrates with Azure Compute Gallery, creating an image management system for global distribution, replication, versioning, and scaling. You can distribute the same image as a virtual hard disk or managed images without rebuilding them.
3129

3230
> [!IMPORTANT]
3331
> Microsoft Dev Box supports only images that use the security type [Trusted Launch](/azure/virtual-machines/trusted-launch-portal?tabs=portal%2Cportal2) enabled.

0 commit comments

Comments
 (0)