Skip to content

Commit e474729

Browse files
authored
Adding support for build VM msi
1 parent 8028309 commit e474729

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/virtual-machines/image-builder-overview.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,9 @@ When you register for the (AIB), this grants the AIB Service permission to creat
103103

104104
To allow Azure VM Image Builder to distribute images to either the managed images or to an Azure Compute Gallery, you will need to create an Azure user-assigned identity that has permissions to read and write images. If you are accessing Azure storage, then this will need permissions to read private and public containers.
105105

106-
Permissions are explained in more detail for [PowerShell](./linux/image-builder-permissions-powershell.md), and [AZ CLI](./linux/image-builder-permissions-cli.md).
106+
In API version 2021-10-01 and beyond, Azure VM Image Builder supports adding an Azure user-assigned identity to the build VM to enable scenarios where you will need to authenticate with services like Azure Key Vault.
107+
108+
For more information on permissions, please see the following links: [PowerShell](./linux/image-builder-permissions-powershell.md), [AZ CLI](./linux/image-builder-permissions-cli.md) and [Image Builder template reference: Identity](https://docs.microsoft.com/azure/virtual-machines/linux/image-builder-json#identity).
107109

108110
## Costs
109111
You will incur some compute, networking and storage costs when creating, building and storing images with Azure Image Builder. These costs are similar to the costs incurred in manually creating custom images. For the resources, you will be charged at your Azure rates.

0 commit comments

Comments
 (0)