Managed identities concept in Azure - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a managed identity in Azure?

A managed identity is a special account created and managed by Azure to let services securely access other resources without needing to store credentials.

beginner

How does a managed identity improve security?

It removes the need to store passwords or keys in code or configuration, reducing the risk of leaks or theft.

intermediate

What are the two types of managed identities in Azure?

System-assigned managed identity (tied to one resource) and user-assigned managed identity (can be shared across resources).

intermediate

How does a system-assigned managed identity lifecycle work?

It is created with the resource and deleted automatically when the resource is deleted.

intermediate

Can a user-assigned managed identity be used by multiple resources?

Yes, it can be assigned to multiple resources, allowing shared access to other services.

What does a managed identity eliminate the need for?

A Setting up firewalls

B Using virtual machines

C Creating resource groups

D Storing credentials in code

Managed identities let services authenticate without storing credentials in code or config.

Which managed identity type is tied to a single Azure resource?

A User-assigned

B System-assigned

C Group-assigned

D Tenant-assigned

System-assigned managed identities are created with and tied to one resource.

Can a user-assigned managed identity be shared across multiple resources?

A Yes, it can be shared

B No, only one resource can use it

C Only if resources are in the same region

D Only for virtual machines

User-assigned managed identities can be assigned to multiple resources.

What happens to a system-assigned managed identity when its resource is deleted?

A It is deleted automatically

B It remains active

C It must be deleted manually

D It is transferred to another resource

System-assigned managed identities are deleted automatically with their resource.

Which Azure service feature uses managed identities to access other resources securely?

A Azure Monitor

B Azure Active Directory

C Azure Key Vault

D Azure DevOps

Azure Key Vault often uses managed identities to allow secure access without credentials.

Explain what a managed identity is and why it is useful in Azure.

Think about how apps get permission without passwords.

Describe the difference between system-assigned and user-assigned managed identities.

One is created with a resource, the other is independent.

Practice

1. What is the main purpose of managed identities in Azure?

easy

A. Allow resources to access other services securely without passwords

B. Store user passwords for Azure services

C. Create virtual machines automatically

D. Manage network traffic between resources

Solution

1. Step 1: Understand managed identities purpose

   Managed identities provide a way for Azure resources to authenticate to other services without needing passwords.

2. Step 2: Compare options

   Only Allow resources to access other services securely without passwords correctly describes this purpose. The other options describe unrelated functions.

3. Final Answer:

   Allow resources to access other services securely without passwords -> Option A

4. Quick Check:

   Managed identities = secure access without passwords [OK]

Hint: Managed identities remove password use for resource access [OK]

Common Mistakes:

• Thinking managed identities store passwords
• Confusing managed identities with VM creation
• Assuming managed identities manage network traffic

2. Which syntax correctly enables a system-assigned managed identity in an Azure resource configuration?

easy

A. "managedIdentity": "system"

B. "identity": { "enabled": true }

C. "identity": { "type": "SystemAssigned" }

D. "identity": "system-assigned"

Solution

1. Step 1: Recall correct identity block syntax

   Azure resource config uses an "identity" block with a "type" property set to "SystemAssigned" to enable system-assigned managed identity.

2. Step 2: Validate options

   "identity": { "type": "SystemAssigned" } matches the correct JSON syntax. The other options do not follow Azure's expected configuration format.

3. Final Answer:

   "identity": { "type": "SystemAssigned" } -> Option C

4. Quick Check:

   Correct identity block syntax = "identity": { "type": "SystemAssigned" } [OK]

Hint: Use "identity": { "type": "SystemAssigned" } to enable system identity [OK]

Common Mistakes:

• Using incorrect property names like "enabled"
• Omitting the "type" key
• Using wrong string values like "system" or "system-assigned"

3. Given this Azure resource configuration snippet:

{
  "identity": { "type": "UserAssigned", "userAssignedIdentities": { "/subscriptions/123/resourceGroups/rg/providers/Microsoft.ManagedIdentity/userAssignedIdentities/identity1": {} } }
}

What does this configuration do?

medium

A. Enables a system-assigned managed identity for the resource

B. Assigns a user-assigned managed identity named 'identity1' to the resource

C. Disables all managed identities for the resource

D. Creates a new user-assigned identity named 'identity1'

Solution

1. Step 1: Analyze the identity type

   The "type" is "UserAssigned", meaning the resource uses an existing user-assigned identity.

2. Step 2: Check the userAssignedIdentities property

   The resource assigns the existing identity at the given resource ID path, named 'identity1'. It does not create a new identity.

3. Final Answer:

   Assigns a user-assigned managed identity named 'identity1' to the resource -> Option B

4. Quick Check:

   UserAssigned with identity path = Assigns a user-assigned managed identity named 'identity1' to the resource [OK]

Hint: UserAssigned type with identity path means assign existing identity [OK]

Common Mistakes:

• Confusing system-assigned with user-assigned identity
• Thinking the identity is created, not assigned
• Ignoring the userAssignedIdentities property

4. You wrote this Azure resource config to enable a system-assigned managed identity:

{
  "identity": { "type": "systemassigned" }
}

Why does this configuration fail to enable the identity?

medium

A. The resource group name is missing

B. The identity block is missing the "enabled" property

C. User-assigned identities require a different syntax

D. The type value is case-sensitive and must be "SystemAssigned"

Solution

1. Step 1: Check the type value case

   Azure expects "SystemAssigned" with capital S and A. "systemassigned" is invalid due to case sensitivity.

2. Step 2: Validate other options

   Stating that the identity block is missing the "enabled" property is incorrect because "enabled" is not required. User-assigned identities require a different syntax, but this config is for system-assigned. The resource group name is unrelated to this error.

3. Final Answer:

   The type value is case-sensitive and must be "SystemAssigned" -> Option D

4. Quick Check:

   Case-sensitive type value = The type value is case-sensitive and must be "SystemAssigned" [OK]

Hint: Check capitalization of "SystemAssigned" exactly [OK]

Common Mistakes:

• Ignoring case sensitivity in type value
• Adding unnecessary properties like "enabled"
• Confusing system-assigned with user-assigned syntax

5. You want two Azure virtual machines to share the same managed identity to access a database securely. Which approach should you use?

hard

A. Create a user-assigned managed identity and assign it to both VMs

B. Assign a system-assigned managed identity to each VM separately

C. Use a shared password stored in Azure Key Vault

D. Enable managed identity only on one VM and share its credentials manually

Solution

1. Step 1: Understand identity sharing options

   System-assigned identities are unique per resource and cannot be shared.

2. Step 2: Identify user-assigned identity use

   User-assigned managed identities can be created once and assigned to multiple resources, allowing sharing.

3. Step 3: Evaluate other options

   Using shared passwords or manual credential sharing is insecure and against best practices.

4. Final Answer:

   Create a user-assigned managed identity and assign it to both VMs -> Option A

5. Quick Check:

   User-assigned identity allows sharing = Create a user-assigned managed identity and assign it to both VMs [OK]

Hint: Use user-assigned identity to share across multiple resources [OK]

Common Mistakes:

• Trying to share system-assigned identities
• Using passwords instead of managed identities
• Manually sharing credentials insecurely