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
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,21 +88,21 @@ 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
-
### Updating or resetting MSI on image templates
91
+
### Reassigning MSI on image templates
92
92
93
93
#### Error
94
94
95
95
```text
96
-
The assigned managed identity cannot be used. Please re-assign an identity. For more troubleshooting steps go to https://aka.ms/azvmimagebuilderts
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
97
```
98
98
99
99
#### Cause
100
100
101
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
102
103
-
1. MSI is deleted before the image template is deleted (custom rg scenario)
104
-
1.MSI credentials URL is lost and therefore can't get credentials for the MSI
105
-
1.Other cases where the assigned MSI doesn't work
103
+
1. 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 Image Builder template uses a customer provided staging resource group
105
+
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.
106
106
107
107
108
108
#### Solution
@@ -112,13 +112,13 @@ Use Azure CLI to reset identity on the image template. Ensure you [update](/azur
112
112
Remove the managed identity from the target image builder template
0 commit comments