Multi-factor authentication in Azure - Time & Space Complexity

Time Complexity: Multi-factor authentication

O(n)

Understanding Time Complexity

We want to understand how the time needed to verify a user changes when using multi-factor authentication in Azure.

Specifically, how does adding extra verification steps affect the process time?

Scenario Under Consideration

Analyze the time complexity of this Azure multi-factor authentication flow.

// User signs in
az login
// If MFA is required, Azure prompts for additional verification (e.g., code from authenticator app or push notification)
// User provides the verification code or approves the push notification
// Access granted if verification succeeds

This sequence shows a user logging in and completing MFA by responding to a challenge.

Identify Repeating Operations

Look at what happens repeatedly during MFA.

• Primary operation: The MFA challenge and verification API calls.
• How many times: Usually once per login attempt, but can repeat if user retries or uses multiple factors.

How Execution Grows With Input

Each login triggers one MFA challenge and verification sequence.

Input Size (n)	Approx. API Calls/Operations
10 logins	10 MFA challenges + 10 verifications
100 logins	100 MFA challenges + 100 verifications
1000 logins	1000 MFA challenges + 1000 verifications

Pattern observation: The number of MFA operations grows directly with the number of login attempts.

Final Time Complexity

Time Complexity: O(n)

This means the time to process MFA grows linearly with the number of login attempts.

Common Mistake

[X] Wrong: "Adding MFA does not affect login time because it's just one extra step."

[OK] Correct: Each MFA step requires extra communication and verification, so total time increases with each login.

Interview Connect

Understanding how MFA impacts system response time shows you can think about user experience and security trade-offs in cloud design.

Self-Check

"What if the system required two different MFA methods per login? How would the time complexity change?"

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