You can use managed identities by following the steps below: How can I use managed identities for Azure resources? For example, a workload where multiple virtual machines need to access the same resource.

Workloads where resources are recycled frequently, but permissions should stay consistent. Workloads needing pre-authorization to a secure resource, as part of a provisioning flow. Workloads that run on multiple resources and can share a single identity. For example, an application that runs on a single virtual machine. Workloads needing independent identities. Workloads contained within a single Azure resource. The same user-assigned managed identity can be associated with more than one Azure resource. It can only be associated with a single Azure resource.Ĭan be shared. Must be explicitly deleted.Ĭan’t be shared. When the parent resource is deleted, the managed identity is deleted as well. Shared life cycle with the Azure resource that the managed identity is created with. The following table shows the differences between the two types of managed identities: PropertyĬreated as part of an Azure resource (for example, Azure Virtual Machines or Azure App Service). User-assigned identities can be used by multiple resources.The service principal is managed separately from the resources that use it. A service principal of a special type is created in Microsoft Entra ID for the identity.When you enable a user-assigned managed identity: You can create a user-assigned managed identity and assign it to one or more Azure Resources. You may also create a managed identity as a standalone Azure resource. For a deployment slot, the name of its system-assigned identity is /slots/.

The name of the system-assigned service principal is always the same as the name of the Azure resource it is created for.

You authorize the managed identity to have access to one or more services.

By design, only that Azure resource can use this identity to request tokens from Microsoft Entra ID.

When the Azure resource is deleted, Azure automatically deletes the service principal for you. The service principal is tied to the lifecycle of that Azure resource. When you enable a system-assigned managed identity:

Some Azure resources, such as virtual machines allow you to enable a managed identity directly on the resource. There are two types of managed identities: Managed identities for Azure resources is the new name for the service formerly known as Managed Service Identity (MSI).

Slot machine stand table