An admin deleted a virtual machine whose system-assigned managed identity held a role on a storage account, then created a new VM with the same name and enabled a system-assigned identity again. The app on the new VM is now denied access to storage. What is the cause?
Choose an answer to check it. Afterward, select any option to review its explanation.
Deleting the VM deleted its identity. Enabling the identity again creates a new service principal, which has never been authorized on the storage account, even though it carries the same name.
Managed identities can authenticate to any resource that supports Microsoft Entra authentication; access keys aren't required.
It is true that only the owning resource can use a system-assigned identity, but code running on that VM is exactly how the identity is used; this doesn't explain the denial.
Key Vault access policies govern key vault objects, not storage accounts; the missing piece is a role assignment for the new identity.
id q3fc0c0b58c