Key points

• A managed identity gives a supported Azure workload an Entra identity without an application-held secret.
• The target resource still needs a role or data permission assigned to that identity.

Best-known use cases

• Let scale-out Azure workloads request short-lived tokens without distributing credentials to instances.

What candidates often confuse it with

• Managed identities remove credential custody for Azure-hosted workloads; federated credentials serve supported external identity scenarios.

Key takeaway

Choose a managed identity when an Azure resource must access another service without stored credentials.

Relevant exam tasks

• D1.2.S2 — Recommend an identity management solution
• D1.2.S5 — Recommend a solution to manage secrets, certificates, and keys

Learn more

• Microsoft Entra architecture