Multi-factor authentication in Azure - Mini Project: Build & Apply

Enable Multi-factor Authentication in Azure

📖 Scenario: You are an IT administrator for a small company. You want to improve security by requiring users to verify their identity with a second step when signing in. This is called Multi-factor Authentication (MFA). You will configure MFA settings in Azure Active Directory.

🎯 Goal: Set up Multi-factor Authentication in Azure by creating a conditional access policy that requires MFA for all users when accessing cloud apps.

📋 What You'll Learn

Create a conditional access policy named RequireMFA

Target all users in the policy

Apply the policy to all cloud applications

Require multi-factor authentication as the access control

💡 Why This Matters

🌍 Real World

Multi-factor authentication helps protect company data by adding a second step to user sign-in, reducing the risk of unauthorized access.

💼 Career

IT administrators and cloud engineers often configure conditional access policies to enforce security standards in organizations.

1

Create the conditional access policy dictionary

Create a dictionary called conditional_access_policy with the key name set to 'RequireMFA' and the key state set to 'enabled'.

Azure

# Your code here

Hint

Use a Python dictionary with keys 'name' and 'state'.

2

Add user and application targets

Add the keys users and applications to conditional_access_policy. Set users to a dictionary with key include and value a list containing the string 'AllUsers'. Set applications to a dictionary with key include and value a list containing the string 'AllCloudApps'.

Azure

conditional_access_policy = {
    'name': 'RequireMFA',
    'state': 'enabled'
}
# Your code here

Hint

Use nested dictionaries for 'users' and 'applications' keys.

3

Add access controls to require MFA

Add the key grantControls to conditional_access_policy. Set it to a dictionary with key operator set to 'OR' and key builtInControls set to a list containing the string 'mfa'.

Azure

conditional_access_policy = {
    'name': 'RequireMFA',
    'state': 'enabled',
    'users': {
        'include': ['AllUsers']
    },
    'applications': {
        'include': ['AllCloudApps']
    }
}
# Your code here

Hint

Use a dictionary with keys 'operator' and 'builtInControls' for grantControls.

4

Complete the policy with session controls

Add the key sessionControls to conditional_access_policy and set it to an empty dictionary {} to complete the policy structure.

Azure

conditional_access_policy = {
    'name': 'RequireMFA',
    'state': 'enabled',
    'users': {
        'include': ['AllUsers']
    },
    'applications': {
        'include': ['AllCloudApps']
    },
    'grantControls': {
        'operator': 'OR',
        'builtInControls': ['mfa']
    }
}
# Your code here

Hint

Set 'sessionControls' to an empty dictionary to finish the policy.

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