You can require multi-factor authentication by registered user class. You can also exempt users individually.
Note: It is best practice to notify users of any security policies that alter the sequence of steps or information needed at sign on before you apply these controls.
Require multi-factor authentication according to risk and the level of access for a specific user class. For example, information system best practices and regulatory compliance typically require the use of these controls for administrator accounts --based on the business value and range of resources they manage.
This setting enables you to require a specific class of user (Administrators, for example) validate their identity with another means such as mobile authenticator or email. It is an organization-wide setting for each user class you select.
If you enforce Email-only MFA on a user class and a user from that class has no email address associated with his account, enforcing Email-only MFA limits his availability to sign-on until the account has a valid email address.
Registered User Class |
Level of Access/Function |
Administrators |
SysAdmins and Administrators
|
File Administrators |
|
Users |
Regular users or users designated as GroupAdmins for a particular group.
Unless you need to take contingency measures for a security incident, consider making MFA for regular users optional at first for a period of time before you require it as policy. |
Temp Users |
|
See Also |