With ADSelfService Plus, administrators can define MFA policies for any app, user group, or OU directly from the management console. Choose from a wide range of authenticators, including FIDO2 passkeys, TOTP, push notifications, biometrics, and security questions. Once set up, end users can seamlessly verify their identity before accessing enterprise applications.
ADSelfService Plus offers a wide range of MFA capabilities. In this MFA series, we'll be focusing on MFA for applications.
Unauthorized application access can lead to data breaches and compliance risks. In this video, I'll show you how to enforce MFA for SSO-enabled applications to add a strong identity verification layer at sign-in.
Start by logging in to ADSelfService Plus with your administrator credentials. Now go to Configuration and under Self-Service click on Multi-Factor Authentication, and you will land on the Authenticators set up page. ADSelfService Plus supports 20 authenticators, so make sure to configure the ones you want to use before heading to the MFA for Endpoints page.
At the top of the page, use the Policy drop-down to select the policy these settings should apply to.
In this page, you'll find the MFA configuration options for all supported endpoints. In this video, we'll focus on Enterprise Applications.
Enable MFA for Enterprise Applications, then specify how many authentication methods users must complete during sign-in. Next, select the authenticators users can use to verify their identity.
Additionally, You can also click the asterisk that's available next to an authenticator to mandate an authenticator. Or if you want users to use authenticators in a particular sequence, that can be done by dragging the authenticator to reorder them. Once you're done, hit Save Settings to save the configuration.
If you want to configure additional settings for application logins, click Advanced in the top-right corner and open the Endpoint MFA tab and scroll down to Cloud Applications Login MFA. Here, you can enable passwordless login, configure the MFA session timeout, require unenrolled users to enroll after successful password verification, allow users to reuse authenticators they've already enrolled for on other endpoints, keep the preselected and define how long the browser remains trusted before users are prompted for MFA again.
With policy-based controls, you can apply different MFA requirements to different users based on their OU or group—giving you granular control over application access
Today's hybrid work environment makes enterprise applications a prime target for credential-based attacks like phishing, keyloggers, and manipulator-in-the-middle.
MFA ensures that stolen credentials alone are never enough to breach your environment. You can also take it a step further and enable passwordless, such as Face ID and fingerprint, eliminating the most common entry point for attackers entirely.
And with trusted browser settings, verified users won't be re-prompted on every login—keeping your teams productive without compromising security.
Now let's see what the experience looks like when accessing an application as an end user. In this example, I sign in to an application and choose ADSelfService Plus for login. After entering my credentials, I'm prompted to complete MFA based on the policy configured by the administrator. Since I've already enrolled in the required authentication methods, I verify my identity using the configured authenticators. Depending on the administrator's configuration, I may be required to complete one or more authentication methods. Once the required verification is complete, I'm securely logged in to the application.
If you want to learn more about ADSelfService Plus, visit the website below.