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: articles/virtual-machines/linux/image-builder-troubleshoot.md
+34-2Lines changed: 34 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,8 +3,8 @@ title: Troubleshoot Azure VM Image Builder
3
3
description: This article helps you troubleshoot common problems and errors you might encounter when you're using Azure VM Image Builder.
4
4
author: kof-f
5
5
ms.author: kofiforson
6
-
ms.reviewer: cynthn
7
-
ms.date: 10/02/2020
6
+
ms.reviewer: erd
7
+
ms.date: 02/10/2023
8
8
ms.topic: troubleshooting
9
9
ms.service: virtual-machines
10
10
ms.subservice: image-builder
@@ -88,6 +88,38 @@ The template already exists.
88
88
89
89
If you submit an image configuration template and the submission fails, a failed template artifact still exists. Delete the failed template.
90
90
91
+
### Reassigning MSI on image templates
92
+
93
+
#### Error
94
+
95
+
```text
96
+
The assigned managed identity cannot be used. Please remove the existing one and re-assign a new identity. For more troubleshooting steps go to https://aka.ms/azvmimagebuilderts.
97
+
```
98
+
99
+
#### Cause
100
+
101
+
There are cases where [Managed Service Identities (MSI)](/azure/virtual-machines/linux/image-builder-permissions-cli#create-a-user-assigned-managed-identity) assigned to the image template cannot be used:
102
+
103
+
1. The Image Builder template uses a customer provided staging resource group and the MSI is deleted before the image template is deleted ([staging resource group](/azure/virtual-machines/linux/image-builder-json?#properties-stagingresourcegroup) scenario)
104
+
1. The identity is deleted and attempted to recreate the identity with the same name, but without re-assigning the MSI. Though the resource ids are the same, the underlying service principal has been changed.
105
+
106
+
107
+
#### Solution
108
+
109
+
Use Azure CLI to reset identity on the image template. Ensure you [update](/azure/update-azure-cli) Azure CLI to the 2.45.0 version or later.
110
+
111
+
Remove the managed identity from the target image builder template
0 commit comments