Enable combined security information registration in Azure Active Directory
Before combined registration, users registered authentication methods for Azure AD Multi-Factor Authentication and self-service password reset (SSPR) separately. People were confused that similar methods were used for Azure AD Multi-Factor Authentication and SSPR but they had to register for both features. Now, with combined registration, users can register once and get the benefits of both Azure AD Multi-Factor Authentication and SSPR.
Starting on August 15th 2020, all new Azure AD tenants will be automatically enabled for combined registration. Tenants created after this date will be unable to utilize the legacy registration workflows.
To make sure you understand the functionality and effects before you enable the new experience, see the Combined security information registration concepts.
Enable combined registration
To enable combined registration, complete these steps:
Sign in to the Azure portal as a user administrator or global administrator.
Go to Azure Active Directory > User settings > Manage user feature preview settings.
Under Users can use the combined security information registration experience, choose to enable for a Selected group of users or for All users.
After you enable combined registration, users who register or confirm their phone number or mobile app through the new experience can use them for Azure AD Multi-Factor Authentication and SSPR, if those methods are enabled in the Azure AD Multi-Factor Authentication and SSPR policies.
If you then disable this experience, users who go to the previous SSPR registration page at
https://aka.ms/ssprsetup are required to perform multi-factor authentication before they can access the page.
If you have configured the Site to Zone Assignment List in Internet Explorer, the following sites have to be in the same zone:
Conditional Access policies for combined registration
To secure when and how users register for Azure AD Multi-Factor Authentication and self-service password reset, you can use user actions in Conditional Access policy. This functionality may be enabled in organizations that want users to register for Azure AD Multi-Factor Authentication and SSPR from a central location, such as a trusted network location during HR onboarding.
This policy applies only when a user accesses a combined registration page. This policy doesn't enforce MFA enrollment when a user accesses other applications.
You can create an MFA registration policy by using Azure Identity Protection - Configure MFA Policy.
For more information about creating trusted locations in Conditional Access, see What is the location condition in Azure Active Directory Conditional Access?
Create a policy to require registration from a trusted location
Complete the following steps to create a policy that applies to all selected users that attempt to register using the combined registration experience, and blocks access unless they are connecting from a location marked as trusted network:
In the Azure portal, browse to Azure Active Directory > Security > Conditional Access.
Select + New policy.
Enter a name for this policy, such as Combined Security Info Registration on Trusted Networks.
Under Assignments, select Users and groups. Choose the users and groups you want this policy to apply to, then select Done.
Users must be enabled for combined registration.
Under Cloud apps or actions, select User actions. Check Register security information, then select Done.
Under Conditions > Locations, configure the following options:
- Configure Yes.
- Include Any location.
- Exclude All trusted locations.
Select Done on the Locations window, then select Done on the Conditions window.
Under Access controls > Grant, choose Block access, then Select.
Set Enable policy to On.
To finalize the policy, select Create.
If you need help, see troubleshoot combined security info registration or learn What is the location condition in Azure AD Conditional Access?
If needed, learn how to force users to re-register authentication methods.