Skip to content

Commit 0a5a0c0

Browse files
Merge pull request #212362 from kof-f/patch-56
Adding pointer to auth error
2 parents 115c754 + 069dc35 commit 0a5a0c0

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/virtual-machines/linux/image-builder-json.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1150,6 +1150,9 @@ properties: {
11501150
- **The stagingResourceGroup property is specified with a resource group that exists**
11511151

11521152
If the `stagingResourceGroup` property is specified with a resource group that does exist, then the Image Builder service will check to make sure the resource group isn't associated with another image template, is empty (no resources inside), in the same region as the image template, and has either "Contributor" or "Owner" RBAC applied to the identity assigned to the Azure Image Builder image template resource. If any of the aforementioned requirements aren't met, an error will be thrown. The staging resource group will have the following tags added to it: `usedBy`, `imageTemplateName`, `imageTemplateResourceGroupName`. Pre-existing tags aren't deleted.
1153+
1154+
> [!IMPORTANT]
1155+
> You will need to assign the contributor role to the resource group for the service principal corresponding to Azure Image Builder's first party app when trying to specify a pre-existing resource group and VNet to the Azure Image Builder service with a Windows source image. For the CLI command and portal instructions on how to assign the contributor role to the resource group see the following documentation [Troubleshoot VM Azure Image Builder: Authorization error creating disk](https://learn.microsoft.com/us/azure/virtual-machines/linux/image-builder-troubleshoot#authorization-error-creating-disk)
11531156
11541157
- **The stagingResourceGroup property is specified with a resource group that doesn't exist**
11551158

0 commit comments

Comments
 (0)