Skip to content

Commit ff62da4

Browse files
Update shared-image-galleries.md
Added Required RBAC Permissions section.
1 parent da7831d commit ff62da4

File tree

1 file changed

+25
-0
lines changed

1 file changed

+25
-0
lines changed

articles/virtual-machines/shared-image-galleries.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -139,6 +139,31 @@ There are three main ways to share images an Azure Compute Gallery, depending on
139139
| RBAC + [Direct shared gallery](./share-gallery-direct.md) | Yes | Yes | Yes | Yes | No |
140140
| RBAC + [Community gallery](./share-gallery-community.md) | Yes | Yes | Yes | No | Yes |
141141

142+
## What RBAC Permissions are required to create an ACG Image:
143+
ACG images can be created by users from various sources, including virtual machines, disks/snapshots, and VHDs. The section outlines the various user permissions necessary for creating an Azure Compute Gallery image. Identifies without the necessary permissions will not be able to create ACG images.
144+
145+
### [VM as source](#tab/vmsource)
146+
- Users will require write permission on the Virtual Machine to create an ACG Image version.
147+
- For Azure SDK, use the property “properties.storageProfile.source.virtualMachineId”, This property requires API version 2023-07-03 or Version 1.4.0 (or higher) of .NET SDK
148+
### [Disk/Snapshot as Source](#tab/disksnapsource)
149+
- Users will require write permission (contributor) on the source disk/snapshot to create an ACG Image version.
150+
### [VHD as Source](#tab/vhdsource)
151+
- Users will require Microsoft.Storage/storageAccounts/listKeys/action, Microsoft.Storage/storageAccounts/write permission (contributor role) on the storage account.
152+
- For SDK, use the property “properties.storageProfile.osDiskImage.source.storageAccountId”, This property requires minimum api-version 2022-03-03.
153+
### [Managed Image and Gallery Image Version as Source](#tab/managedgallerysource)
154+
- Users will require read permission on the Managed Image/Gallery Image.
155+
156+
|Source type |Permissions Required |
157+
|---|---|
158+
| Virtual machine | Write |
159+
| Disk/snapshot | Write |
160+
| VHD | Write (listKeys) |
161+
|Managed Image |Read|
162+
|Gallery Image |Read|
163+
164+
Refer to our documentation for additional information regarding [Azure built-in roles](https://learn.microsoft.com/azure/role-based-access-control/built-in-roles), for [granting RBAC permissions](https://learn.microsoft.com/azure/role-based-access-control/quickstart-assign-role-user-portal)
165+
166+
142167
## Shallow replication
143168

144169
When you create an image version, you can set the replication mode to shallow for development and test. Shallow replication skips copying the image, so the image version is ready faster. But, it also means you can't deploy a large number of VMs from that image version. This is similar to the way that the older managed images worked.

0 commit comments

Comments
 (0)