Multi-factor authentication in Azure - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Multi-factor Authentication (MFA)?

MFA is a security method that requires users to provide two or more verification factors to access a resource, making it harder for unauthorized people to get in.

beginner

Name three common factors used in MFA.

1. Something you know (like a password)
2. Something you have (like a phone or hardware token)
3. Something you are (like a fingerprint or face scan)

intermediate

How does Azure MFA improve security for cloud services?

Azure MFA adds an extra step to sign-in by requiring a second form of verification, reducing the risk of stolen passwords being used to access accounts.

intermediate

What are some ways users can verify their identity with Azure MFA?

Users can verify using:
- A phone call
- A text message with a code
- A mobile app notification or code
- Hardware tokens

beginner

Why is MFA considered a best practice in cloud security?

Because it adds layers of protection beyond just passwords, making it much harder for attackers to access accounts even if passwords are compromised.

What does MFA stand for in cloud security?

A Managed Firewall Access

B Multiple File Access

C Multi-file Authorization

D Multi-factor Authentication

MFA means Multi-factor Authentication, which adds extra verification steps to secure access.

Which of the following is NOT a factor used in MFA?

A Something you know

B Something you have

C Something you want

D Something you are

MFA factors include knowledge, possession, and inherence, but not 'something you want'.

Which Azure service provides MFA capabilities?

A Azure Active Directory

B Azure Blob Storage

C Azure Virtual Machines

D Azure DevOps

Azure Active Directory includes MFA features to secure user sign-ins.

What is a common method for users to receive their second factor in Azure MFA?

A Phone call or mobile app notification

B Email with a password reset link

C Direct access without verification

D Using a VPN connection

Azure MFA commonly uses phone calls, text messages, or app notifications as second factors.

Why is MFA important even if you have a strong password?

A Because MFA removes the need for usernames

B Because passwords can be stolen or guessed

C Because MFA makes passwords shorter

D Because MFA replaces passwords

MFA protects accounts even if passwords are compromised by requiring additional verification.

Explain how Multi-factor Authentication works and why it is important in cloud security.

Think about how adding steps to sign-in protects accounts.

Describe the ways Azure MFA can verify a user's identity.

Consider the different devices or methods a user might use.

Practice

1. What is the main purpose of Multi-factor Authentication (MFA) in Azure?

easy

A. To provide free cloud storage

B. To speed up the login process

C. To allow users to reset their passwords automatically

D. To add an extra step to verify user identity for better security

Solution

1. Step 1: Understand MFA concept

   MFA requires users to provide two or more verification methods to prove their identity.

2. Step 2: Identify MFA's main goal

   This extra verification step improves security by making unauthorized access harder.

3. Final Answer:

   To add an extra step to verify user identity for better security -> Option D

4. Quick Check:

   MFA = extra verification step [OK]

Hint: MFA means more than one way to prove who you are [OK]

Common Mistakes:

• Thinking MFA speeds up login
• Confusing MFA with password reset
• Assuming MFA provides storage

2. Which of the following is the correct PowerShell command to enable MFA for a user in Azure AD?

easy

A. Set-MsolUser -UserPrincipalName [e-mail] -StrongAuthenticationRequirements @(@{RelyingParty="*";State="Enabled"})

B. Enable-MsolUser -UserPrincipalName [e-mail] -StrongAuthenticationRequirements @()

C. New-MsolUser -UserPrincipalName [e-mail] -EnableMFA $true

D. Add-MsolUser -UserPrincipalName [e-mail] -MFAEnabled

Solution

1. Step 1: Recall correct MFA enabling syntax

   In Azure AD PowerShell, enabling MFA uses Set-MsolUser with StrongAuthenticationRequirements set to enabled.

2. Step 2: Match command to syntax

   Set-MsolUser -UserPrincipalName [e-mail] -StrongAuthenticationRequirements @(@{RelyingParty="*";State="Enabled"}) correctly uses Set-MsolUser with StrongAuthenticationRequirements array containing State="Enabled".

3. Final Answer:

   Set-MsolUser -UserPrincipalName [e-mail] -StrongAuthenticationRequirements @(@{RelyingParty="*";State="Enabled"}) -> Option A

4. Quick Check:

   Enable MFA = Set-MsolUser + StrongAuthenticationRequirements enabled [OK]

Hint: Look for Set-MsolUser with StrongAuthenticationRequirements enabled [OK]

Common Mistakes:

• Using Enable-MsolUser which does not exist
• Confusing New-MsolUser with enabling MFA
• Using Add-MsolUser which is invalid

3. Consider this Azure AD MFA policy snippet:

{"state": "enabled", "methods": ["phoneAppNotification", "sms"]}

What happens when a user tries to sign in?

medium

A. User must use a hardware token only

B. User can sign in without any additional verification

C. User must verify identity using either phone app notification or SMS code

D. User is blocked from signing in

Solution

1. Step 1: Analyze MFA policy state

   The policy state is "enabled", so MFA is active and required.

2. Step 2: Check allowed verification methods

   Methods include phone app notification and SMS, so user can use either to verify.

3. Final Answer:

   User must verify identity using either phone app notification or SMS code -> Option C

4. Quick Check:

   MFA enabled means verification required via allowed methods [OK]

Hint: Enabled MFA means user must verify by one allowed method [OK]

Common Mistakes:

• Thinking user can skip verification
• Assuming user is blocked
• Believing only hardware tokens work

4. You configured MFA for a user but they report they are not prompted for the second factor. What is the most likely cause?

medium

A. The user is excluded from MFA in the conditional access policy

B. The user has not logged in for 30 days

C. The user's password is expired

D. The user is using a supported MFA method

Solution

1. Step 1: Understand why MFA prompt might be skipped

   If a user is excluded in conditional access policies, MFA won't be enforced for them.

2. Step 2: Evaluate other options

   Login inactivity or password expiry do not disable MFA prompts; supported methods enable MFA.

3. Final Answer:

   The user is excluded from MFA in the conditional access policy -> Option A

4. Quick Check:

   Exclusion in policy = no MFA prompt [OK]

Hint: Check if user is excluded in conditional access policies [OK]

Common Mistakes:

• Assuming password expiry disables MFA
• Thinking inactivity disables MFA
• Confusing supported methods with disabling MFA

5. You want to enforce MFA only when users access sensitive Azure resources from outside your corporate network. Which Azure feature should you use to achieve this?

hard

A. Enable MFA for all users unconditionally

B. Conditional Access policies with location-based conditions

C. Azure AD Identity Protection without conditions

D. Use Azure Firewall to block all external access

Solution

1. Step 1: Identify feature for conditional MFA enforcement

   Conditional Access policies allow setting MFA requirements based on conditions like user location.

2. Step 2: Match requirement to feature

   Location-based conditions in Conditional Access enable MFA only outside corporate network.

3. Step 3: Evaluate other options

   Identity Protection without conditions cannot target location; unconditional MFA applies everywhere; firewall blocks access but does not enforce MFA.

4. Final Answer:

   Conditional Access policies with location-based conditions -> Option B

5. Quick Check:

   Conditional Access + location = targeted MFA [OK]

Hint: Use Conditional Access with location rules for targeted MFA [OK]

Common Mistakes:

• Using unconditional MFA for all users
• Relying on Identity Protection without conditions
• Blocking access instead of enforcing MFA