# Managed identity

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

An Azure identity assigned to a compute resource so that the resource can get Microsoft Entra tokens without any stored secret. It is either system-assigned, tied to one resource, or user-assigned, a standalone resource that several resources can use. Role assignments decide what it can reach.

## An example, sourced

Microsoft documents that managed identities eliminate the need for developers to manage credentials, and that applications use them to obtain Microsoft Entra tokens. A system-assigned identity is enabled on one resource, and its service principal always carries the same name as that resource. A user-assigned identity is created as a standalone resource and can be assigned to more than one. Either kind can then be authorized to reach downstream resources, such as a storage account, a SQL database or Cosmos DB.

## Why it matters here

Managed identities remove the leaked-key risk but not the question of scope. Whether an agent shares one with other apps, and what roles it holds, still has to be read from the role assignments. The reviewer also needs the list of resources the identity can be assigned to.

## Related pages

- [Workload identity: meaning and an example](/glossary/workload-identity/)
- [Workload identity federation: meaning and an example](/glossary/workload-identity-federation/)
- [EKS Pod Identity: meaning and an example](/glossary/eks-pod-identity/)
- [All of them](/glossary/)

## Sources

- https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/overview (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/glossary/managed-identity/
