Skip to content

Commit 58f0c8f

Browse files
committed
Add compute gallery section
1 parent d6ad169 commit 58f0c8f

File tree

1 file changed

+18
-7
lines changed

1 file changed

+18
-7
lines changed

articles/dev-box/concept-dev-box-deployment-guide.md

Lines changed: 18 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -117,7 +117,7 @@ Microsoft Dev Box uses Azure role-based access control (Azure RBAC) to grant acc
117117
- Grant project administrators access to perform administrative tasks on Microsoft Dev Box projects (Project Admin role)
118118
- Grant dev box users access to create and manage their dev boxes in a Dev Box project (Dev Box User role)
119119

120-
You can create security groups in Microsoft Entra ID for granting or revoking access for admins and users for each project. By using a security group, you can delegate the task of granting access independently of their permissions on the Azure resources. For example, you could delete granting access for dev box users to the dev team lead for that project.
120+
Consider creating security groups in Microsoft Entra ID for granting or revoking access for admins and users for each project. By using a security group, you can delegate the task of granting access independently of their permissions on the Azure resources. For example, you could delete granting access for dev box users to the dev team lead for that project.
121121

122122
Learn more about [Microsoft Entra ID groups](/entra/fundamentals/concept-learn-about-groups).
123123

@@ -154,13 +154,24 @@ Consider creating a separate network connection in the following scenarios:
154154
- A developer or team needs access to corporate, on-premises resources. Create an Azure network connection and configure it for hybrid connectivity.
155155
- Dev box users need to authenticate with their Active Directory account. Create an Azure network connection and configure it for hybrid connectivity.
156156

157-
### Step x: Create compute galleries
158-
- Marketplace vs compute gallery
159-
- create galleries
160-
- create custom images
161-
- consider base image and apply customizations
157+
### Step 6: Create compute galleries
162158

163-
### Step x: Attach catalog
159+
By default, dev box definitions can use any virtual machine (VM) image from the Azure Marketplace. You can assign one or more Azure compute galleries to the dev center to control the VM images that are available across all dev center projects.
160+
161+
Azure Compute Gallery is a service for managing and sharing images. A gallery is a repository that's stored in your Azure subscription and helps you build structure and organization around your image resources.
162+
163+
Consider using an Azure compute gallery in the following cases:
164+
165+
- Development teams can standardize on a supported image version until a newer version is validated.
166+
- Development teams can use the latest version of an image definition to ensure they always receive the most recent image when creating dev boxes.
167+
- Development teams can choose from images that are preconfigured with software components and configurations for their project or usage scenario. For example, images for data science projects, front-end web development, and more.
168+
- You want to maintain the images in a single location and use them across dev centers, projects, and pools.
169+
170+
When you create custom VM images, also consider using [dev box customization tasks](#step-7-attach-catalog) to limit the number of VM image variants and enable developers to fine-tune their dev box configuration themselves. For example, you might create a gneral-purpose development image, and use customization to let developers configure it for specific development tasks and preconfigure their source code repository.
171+
172+
Learn more about how to [configure a compute gallery for a dev center](./how-to-configure-azure-compute-gallery.md).
173+
174+
### Step 7: Attach catalog
164175
- create repo
165176
- add customization tasks
166177

0 commit comments

Comments
 (0)