You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: includes/virtual-machines-image-builder-overview.md
+10-23Lines changed: 10 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
author: cynthn
3
3
ms.author: cynthn
4
-
ms.date: 01/23/2020
4
+
ms.date: 05/05/2020
5
5
ms.topic: include
6
6
ms.service: virtual-machines-linux
7
7
manager: gwallace
@@ -26,7 +26,7 @@ For the preview, these features are supported:
26
26
- Integration with the Azure Shared Image Gallery, allows you to distribute, version, and scale images globally, and gives you an image management system.
27
27
- Integration with existing image build pipelines, just call Image Builder from your pipeline, or use the simple Preview Image Builder Azure DevOps Task.
28
28
- Migrate an existing image customization pipeline to Azure. Use your existing scripts, commands, and processes to customize images.
29
-
- Creation of images in VHD format.
29
+
- Creation of images in VHD format to support Azure Stack.
30
30
31
31
32
32
## Regions
@@ -51,8 +51,7 @@ AIB will support Azure Marketplace base OS images:
51
51
- Windows 2016
52
52
- Windows 2019
53
53
54
-
RHEL ISOs support is being deprecated, please review the Template documentation for further details.
55
-
54
+
RHEL ISOs support is not longer supported.
56
55
## How it works
57
56
58
57
@@ -73,29 +72,18 @@ The Azure Image Builder is a fully managed Azure service that is accessible by a
73
72
74
73
75
74
## Permissions
75
+
When you register for the (AIB), this grants the AIB Service permission to create, manage and delete a staging resource group (IT_*), and have rights to add resources to it, that are required for the image build. This is done by an AIB Service Principal Name (SPN) being made available in your subscription during a successful registration.
76
76
77
-
To allow Azure VM Image Builder to distribute images to either the managed images or to a Shared Image Gallery, you will need to provide 'Contributor' permissions for the service "Azure Virtual Machine Image Builder" (app ID: cf32a0cc-373c-47c9-9156-0db11f6a6dfc) on the resource groups.
78
-
79
-
If you are using an existing custom managed image or image version, then the Azure Image Builder will need a minimum of ‘Reader’ access to those resource groups.
80
-
81
-
You can assign access using the Azure CLI:
77
+
To allow Azure VM Image Builder to distribute images to either the managed images or to a Shared Image 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 containers.
Initially you must [create Azure user-assigned managed identity](https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-cli) documentation on how to create an identity.
89
80
90
-
You can assign access using the PowerShell:
81
+
Once you have the identity you need to grant it permissions, to do this, you can use an Azure Custom Role Definition, and then assign the user-assigned managed identity to use the Custom Role Definition.
If the service account is not found, that may mean that the subscription where you are adding the role assignment has not yet registered for the resource provider.
83
+
Permissions are explained in more detail [here](https://github.com/danielsollondon/azvmimagebuilder/blob/master/aibPermissions.md#azure-vm-image-builder-permissions-explained-and-requirements), and the examples show how this is implemented.
98
84
85
+
> [Note!]
86
+
> Previously with AIB, you would use the AIB SPN, and grant the SPN permissions to the image resource groups. We are moving away from this model, to allow for future capabilities. From 1st June 2020, Image Builder will not accept templates that do not have a user-assigned identity, existing templates will need to be resubmitted to the service with a [user-identity](https://docs.microsoft.com/azure/virtual-machines/linux/image-builder-json?toc=%2Fazure%2Fvirtual-machines%2Fwindows%2Ftoc.json&bc=%2Fazure%2Fvirtual-machines%2Fwindows%2Fbreadcrumb%2Ftoc.json#identity). The examples here already show how you can create a user-assigned identity and add them to a template.
99
87
100
88
## Costs
101
89
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.
@@ -110,4 +98,3 @@ Azure Image Builder will distribute the image to your chosen regions, which migh
110
98
111
99
To try out the Azure Image Builder, see the articles for building [Linux](../articles/virtual-machines/linux/image-builder.md) or [Windows](../articles/virtual-machines/windows/image-builder.md) images.
0 commit comments