Note: Multi-factor authentication (MFA) for endpoints, VPNs, and SSO require the Professional edition of ADSelfService Plus with Endpoint MFA.
ADSelfService Plus' MFA augments traditional username- and password-based authentication with an additional layer of authentication (e.g., biometrics, TOTP codes, or FIDO2 Passkeys) to verify a user's identity. MFA provides a high level of identity assurance for access requests.
You can enable MFA in ADSelfService Plus for the following events:
To enable MFA for these events, follow these steps:
Please refer to the authenticators page for the list of supported authentication methods and how to configure them.
Combined with Conditional Access, MFA for Endpoints can be enabled only for high-risk users, ensuring high-risk actions stay secure while minimizing the impact on the user experience overall. To learn more about Conditional Access, click here.
ADSelfService Plus enables you to configure MFA for two sets of users:
Domain users are part of an AD domain and are typically imported into ADSelfService Plus via the AD Synchronizer set up during domain configuration .
To configure MFA for domain users, first assign them to a policy. You can then apply MFA settings to that policy, and all the users under that policy will have MFA configured for them.
Domain users must enroll themselves by providing the necessary information, as per the enabled authentication methods, to be able to prove their identity. For example, if you have enabled biometric authentication, users must scan their fingerprint or face using the ADSelfService Plus mobile app, only after which they will be able to use their biometrics during password reset or endpoint logins.
To force enrollment for specific authentication methods:
This table provides detailed information on each MFA type, including the supported authenticators and the settings and options available to improve the functionality and security of the authentication process.
MFA type | Authentication methods supported | Passwordless login | Backup recovery codes | CAPTCHA |
---|---|---|---|---|
MFA for self-service actions via the web portal | All the authenticators supported by ADSelfService Plus | Not applicable | Supported | Supported |
Self-service actions from the GUI machine login screen for Windows, macOS, and Linux machines | All the authenticators supported by ADSelfService Plus. Smart Card Authentication is not supported for macOS or Linux machines | Not applicable | Supported | Supported |
MFA for domain user logins to Windows, macOS, and Linux machines | All the authenticators supported by ADSelfService Plus. Smart Card Authentication is not supported for macOS or Linux machines | Not supported | Supported | Supported |
MFA for local user logins to Windows machines |
|
Not supported | Supported | Supported |
Offline MFA for Windows and macOS logins |
|
Not applicable | Not supported | Not supported |
MFA for OWA and the EAC | All the authenticators supported by ADSelfService Plus | Not applicable | Supported | Supported |
MFA for RADIUS-based VPNs, RDP, and other endpoints via the VPN Client Verification option |
|
Not applicable | Supported* (Backup codes can be used only for challenge-based authenticators) |
Not applicable |
MFA for RADIUS-based VPNs, RDP, and other endpoints via the Verify via Secure Link through Browser option | All the authenticators supported by ADSelfService Plus | Not applicable | Supported | Supported |
MFA for cloud applications | All the authenticators supported by ADSelfService Plus | Supported | Supported | Supported |
MFA for ADSelfService Plus logins | All the authenticators supported by ADSelfService Plus | Supported | Supported | Supported |
MFA type | Can an idle time limit be set? | Can the browser or machine be trusted not to require MFA for a certain period? | Restrict user logins and self-service actions for unenrolled users: |
---|---|---|---|
MFA for self-service actions | Yes | No | Deny access to self-service actions when users are unenrolled. Partially-enrolled users can be forced to enroll for the remaining authenticators and proceed with self-service actions. |
MFA for domain user logins to Windows, macOS, and Linux machines | Yes | Yes | Deny or allow machine logins for unenrolled users, or enforce enrollment during login attempt. |
MFA for local logins to Windows machines | Yes. Supports Windows logins only. | Yes. Supports Windows logins only. | Deny or allow machine logins for unenrolled users. |
MFA for Outlook on the web and EAC | Yes | Yes | Access to OWA and Exchange logins is denied for unenrolled users by default. |
MFA for RADIUS-based VPNs, RDP, and other endpoints via the VPN Client Verification option | Yes* (A session time limit is set to enforce users to complete authentication within the specified time.) |
No | Deny or allow logins for unenrolled users. |
MFA for RADIUS-based VPNs, RDP, and other endpoints via the Secure Link Email Verification option | Yes* (An idle time limit is set to enforce users to complete authentication within the specified time, and it cannot be greater than the secure link's validity period.) |
No | Deny or allow logins for unenrolled users. |
MFA for cloud applications | Yes | Yes | Deny or allow cloud application logins for unenrolled users. |
MFA for ADSelfService Plus logins | Yes | Yes | Deny or allow ADSelfService Plus logins for unenrolled users. |
MFA type | Can an idle time limit be set? | Can the browser or machine be trusted not to require MFA for a certain period? | Restrict user logins and self-service actions for unenrolled users: |
---|---|---|---|
MFA for self-service actions | No | No | Not applicable as local users are always enrolled. |
Yes. Supports Windows logins only. | Yes. Supports Windows logins only. | Yes | Not applicable as local users are always enrolled. |
MFA for Outlook on the web and EAC | No | No | Not applicable as local users are always enrolled. |
MFA for RADIUS-based VPNs, RDP, and other endpoints via the VPN Client Verification option | No | No | Not applicable as local users are always enrolled. |
MFA for RADIUS-based VPNs, RDP, and other endpoints via the Secure Link Email Verification option | Yes. Supports RDP server logins only. | Yes. Supports RDP server logins only. | Not applicable as local users are always enrolled. |
MFA for cloud applications | No | No | Not applicable as local users are always enrolled.. |
MFA for ADSelfService Plus logins | No | No | Not applicable as local users are always enrolled. |
* Users do not have to enroll for these methods because they are automatically enrolled upon logging in the first time.
+ These authenticators are native to the mobile app and cannot be used in the mobile browser portal.
* Local user MFA can be configured to secure logins to and peripheral connections from standalone (Workgroup) and domain-joined Windows machines. It cannot be configured for self-service actions, cloud applications, and other endpoints that can be secured for domain users.
ADSelfService Plus offers 21 types of authenticators. Of these, eight basic authenticators are available with every edition of ADSelfService Plus. The other 13 are advanced authenticators, available only with the Professional edition of ADSelfService Plus.
This table provides detailed information on the basic and advanced authenticators supported for MFA in the ADSelfService Plus mobile app and mobile browser portal along with provisions for authenticator enrollment in the two consoles.
Authenticator | Authenticator type | Mobile browser portal | Mobile app | ||||
---|---|---|---|---|---|---|---|
Can users enroll in the authenticator in the mobile browser portal? | Is the authenticator supported for MFA for ADSelfService Plus logins? | Is the authenticator supported for MFA for self-service actions? | Can users enroll in the authenticator in the mobile app? | Is the authenticator supported for MFA for logins to the ADSelfService Plus Mobile App ? | Is the authenticator supported for MFA for self-service actions? | ||
Security Questions and Answers | Basic | Yes | Yes | Yes | Yes | Yes | Yes |
Email Verification | Basic | Yes | Yes | Yes | Yes | Yes | Yes |
SMS Verification | Basic | Yes | Yes | Yes | Yes | Yes | Yes |
Google Authenticator | Basic | Yes | Yes | Yes | Yes | Yes | Yes |
Microsoft Authenticator | Basic | Yes | Yes | Yes | Yes | Yes | Yes |
Duo Security | Advanced authenticator | Yes | Yes | Yes | Yes | Yes | Yes |
Radius Authentication | Advanced authenticator | No* | Yes | Yes | No* | Yes | Yes |
Push Notification | Advanced authenticator | No+ | No+ | No+ | Yes | No | No |
QR Code Based Authentication | Advanced authenticator | No+ | No+ | No+ | Yes | No | No |
Biometric Authentication | Advanced authenticator | No+ | No+ | No+ | Yes | Yes | Yes |
TOTP Authentication (Using ADSelfService Plus Mobile app) | Advanced authenticator | No+ | No+ | No+ | Yes | No | No |
AD Security Questions | Basic | No* | Yes | Yes | No* | Yes | Yes |
Zoho OneAuth TOTP | Basic | Yes | Yes | Yes | Yes | Yes | Yes |
Custom TOTP authenticator (Hardware Token) | Advanced authenticator | Yes | Yes | Yes | Yes | Yes | Yes |
Custom TOTP authenticator (Software Token) | Basic | Yes | Yes | Yes | Yes | Yes | Yes |
Smart Card Authentication | Advanced authenticator | No* | No | No | No* | No | No |
SAML Authentication | Advanced authenticator | No* | Yes | Yes | No* | Yes | Yes |
YubiKey Authenticator | Advanced authenticator | Yes | Yes | Yes | Yes | Yes | Yes |
Azure AD MFA | Advanced authenticator | No* | Yes | Yes | No* | Yes | Yes |
RSA SecurID | Advanced authenticator | No* | Yes | Yes | No* | Yes | Yes |
FIDO2 Passkeys | Advanced authenticator | Yes | Yes | Yes | No | No | No |
+ These authenticators are native to the mobile app and cannot be used in the mobile browser portal.
Copyright © 2025, ZOHO Corp. All Rights Reserved.