Skip to content
/ idmgmt Public

Ensuring secure Azure identity management with Conditional Access and MFA. Focused on enhancing security, compliance, and seamless user access.

Notifications You must be signed in to change notification settings

jwnfld3/idmgmt

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

22 Commits
 
 

Repository files navigation

Implement Conditional Access & Multi-Factor Authentication (MFA)

Summary

This lab demonstrates how to enforce security policies in Microsoft Entra ID by implementing Conditional Access and Multi-Factor Authentication (MFA) within the framework of a Zero Trust security model. The objective is to strengthen authentication security by blocking risky sign-ins, requiring MFA for high-privilege accounts such as Global Administrators, and ensuring that only verified users and devices gain access to critical resources. By configuring Conditional Access policies, organizations can minimize unauthorized access, ensure continuous verification, and enhance overall security compliance in line with Zero Trust principles.


Definition: Implementing Conditional Access & Multi-Factor Authentication (MFA)

Conditional Access is a security feature in Microsoft Entra ID (formerly Azure AD) that enforces access policies based on specific conditions such as user identity, device compliance, location, and risk level. It helps organizations control who can access resources and under what circumstances.

Multi-Factor Authentication (MFA) is an authentication method that requires users to verify their identity using multiple factors, typically something they know (password) and something they have (authentication app, phone, or security key). MFA significantly reduces the risk of unauthorized access, even if passwords are compromised.

By implementing Conditional Access and MFA together, organizations strengthen security by ensuring that access to critical resources is granted only under secure and verified conditions.


Click on the images below to view the full-size version

Lab Requirements

Before starting this lab, ensure the following requirements are met:

  • Microsoft Entra ID Admin Access – Access to the Microsoft Entra Admin Center with Global Administrator or Conditional Access Administrator permissions.
  • Test Admin Account – A separate test account with Global Administrator privileges for testing.
  • Multi-Factor Authentication (MFA) Setup – Ensure MFA is enabled in the Microsoft Entra ID tenant.
  • Internet Connection – Required to access the Microsoft Entra Admin Center.
  • VPN (Optional) – Used to simulate sign-ins from untrusted locations.

Who

This lab is intended for IT administrators, security analysts, and identity management professionals responsible for securing user authentication in Microsoft Entra ID. The lab assumes basic familiarity with Microsoft Entra ID and Conditional Access policies.


What

The lab involves configuring a Conditional Access policy to enforce MFA for Global Administrators and block access from untrusted locations. This ensures that only verified users can access sensitive resources, reducing the risk of unauthorized access and credential-based attacks.


When

This lab is applicable when:

  • Implementing security policies for privileged accounts.
  • Strengthening authentication mechanisms to comply with security frameworks.
  • Responding to an increase in unauthorized sign-in attempts.
  • Enhancing identity protection for cloud-based services.

Where

The lab is performed within the Microsoft Entra Admin Center, specifically under the Security and Conditional Access sections.


Why

Enforcing MFA and Conditional Access is critical for:

  • Reducing the risk of compromised administrator accounts.
  • Preventing unauthorized access from risky locations.
  • Ensuring compliance with security best practices and regulatory requirements.
  • Strengthening authentication security for sensitive resources.

Steps to Implement Conditional Access & MFA

Conditional Access is a policy-based access control feature in Microsoft Entra ID (formerly Azure Active Directory) that enforces security requirements based on specific conditions. It evaluates signals such as user identity, device status, location, and application being accessed to determine whether to allow or block access—or require additional actions like Multi-Factor Authentication (MFA).


Key Capabilities:

  • Granular Control: Apply policies based on user groups, roles, applications, device compliance, IP locations, and risk levels.
  • Adaptive Access: Enforce additional security requirements (like MFA or device compliance) only when certain conditions are met.
  • Real-Time Decisions: Evaluate access requests in real-time to ensure compliance and reduce risk.

Why It Matters:

  • Reduces the attack surface by requiring stronger controls only when necessary.
  • Supports zero-trust security by verifying user identity, device health, and session context.
  • Helps organizations meet compliance standards and minimize the risk of unauthorized access.

Common Use Cases:

  • Require MFA for users signing in from outside trusted locations.
  • Block access to sensitive applications from unmanaged or non-compliant devices.
  • Allow access only if the user's risk level is low (based on Microsoft Entra ID Identity Protection).

1. Access Conditional Access Settings:

  • Open a web browser and navigate to the Microsoft Entra Admin Center.
  • Go to SecurityConditional Access. If it cannot be located use the search bar on the home screen.

image

2. Create a New Conditional Access Policy:

  • Click on New Policy and name it "Require MFA for Admins".

image

3. Assign Policy to Global Administrators:

  • Under Assignments, select Users.
  • Click Spefific Users Included and under Include Click Users and groups radio button and the Users and groups check box and select the group that you have created for Global Administrators

image

4. Define Access Conditions:

  • Navigate to ConditionsLocations.
  • Configure the policy to "Include Any network or location". Policies with "Any network or location" ensure users meet security conditions (e.g., MFA, device compliance) regardless of where they are.

5. Enforce MFA:

  • Under Grant Controls, select Require Multi-Factor Authentication (MFA).
  • Ensure the policy is set to Enabled. image

6. Test the Policy:

  • Use an admin test account to verify that MFA is required when signing in. image

Summary: Enforcing Authentication from Any Location

This lab ensures users must meet security conditions such as Multi-Factor Authentication (MFA) and device compliance no matter where they connect from. By configuring the policy to "Include Any network or location," authentication requirements apply universally whether users are on a corporate network, public Wi-Fi, or a remote connection. This enhances security by preventing location-based bypasses and ensuring consistent enforcement of access policies across all environments.


Testing and Validation

1. Verify MFA Enforcement:

  • Sign in with a Global Administrator test account.
  • Confirm that an MFA prompt appears before access is granted.

2. Review Sign-In Logs:

  • Go to Microsoft Entra IDSign-in Logs.
  • Verify that policy enforcement details, such as MFA requirements and blocked sign-ins, are correctly logged.

3. Adjust and Troubleshoot if Needed:

  • If unexpected behavior occurs, review policy settings and adjust conditions accordingly.
  • Ensure that MFA settings in Identity Protection align with Conditional Access policies.

Summary: Enforcing Authentication from Any Location

This lab ensures users must meet security conditions such as Multi-Factor Authentication (MFA) and device compliance no matter where they connect from. By configuring the policy to "Include Any network or location," authentication requirements apply universally whether users are on a corporate network, public Wi-Fi, or a remote connection. This enhances security by preventing location-based bypasses and ensuring consistent enforcement of access policies across all environments.

By following these validation steps, the effectiveness of the Conditional Access policy can be confirmed, ensuring that privileged accounts remain secure.

About

Ensuring secure Azure identity management with Conditional Access and MFA. Focused on enhancing security, compliance, and seamless user access.

Topics

Resources

Stars

Watchers

Forks