- Article
- 9 minutes to read
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 multifactor 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 multifactor authentication and SSPR. We recommend this video on How to enable and configure SSPR in Azure AD
Note
Effective Oct. 1st, 2022, we will begin to enable combined registration for all users in Azure AD tenants created before August 15th, 2020. Tenants created after this date are enabled with combined registration.
This article outlines what combined security registration is. To get started with combined security registration, see the following article:
Enable combined security registration
Before enabling the new experience, review this administrator-focused documentation and the user-focused documentation to ensure you understand the functionality and effect of this feature. Base your training on the user documentation to prepare your users for the new experience and help to ensure a successful rollout.
Azure AD combined security information registration is available for Azure US Government but not Azure China 21Vianet.
Important
Users that are enabled for both the original preview and the enhanced combined registration experience see the new behavior. Users that are enabled for both experiences see only the My Account experience. The My Account aligns with the look and feel of combined registration and provides a seamless experience for users. Users can see My Account by going to https://myaccount.microsoft.com.
You can set Require users to register when signing in to Yes to require all users to register when signing in, ensuring that all users are protected.
You might encounter an error message while trying to access the Security info option, such as, "Sorry, we can't sign you in". Confirm that you don't have any configuration or group policy object that blocks third-party cookies on the web browser.
My Account pages are localized based on the language settings of the computer accessing the page. Microsoft stores the most recent language used in the browser cache, so subsequent attempts to access the pages continue to render in the last language used. If you clear the cache, the pages re-render.
If you want to force a specific language, you can add ?lng=<language> to the end of the URL, where <language> is the code of the language you want to render.
Methods available in combined registration
Combined registration supports the authentication methods and actions in the following table.
| Method | Register | Change | Delete |
|---|---|---|---|
| Microsoft Authenticator | Yes (maximum of 5) | No | Yes |
| Other authenticator app | Yes (maximum of 5) | No | Yes |
| Hardware token | No | No | Yes |
| Phone | Yes | Yes | Yes |
| Alternate phone | Yes | Yes | Yes |
| Office phone* | Yes | Yes | Yes |
| Yes | Yes | Yes | |
| Security questions | Yes | No | Yes |
| App passwords* | Yes | No | Yes |
| FIDO2 security keys* | Yes | No | Yes |
Note
Office phone can only be registered in Interrupt mode if the users Business phone property has been set. Office phone can be added by users in Managed mode from the Security info without this requirement.
App passwords are available only to users who have been enforced for Azure AD Multi-Factor Authentication. App passwords are not available to users who are enabled for Azure AD Multi-Factor Authentication by a Conditional Access policy.
FIDO2 security keys, can only be added in Managed mode only from the Security info page
Users can set one of the following options as the default multifactor authentication method.
- Microsoft Authenticator – push notification or passwordless
- Authenticator app or hardware token – code
- Phone call
- Text message
Note
Virtual phone numbers are not supported for Voice calls or SMS messages.
Third party authenticator apps do not provide push notification. As we continue to add more authentication methods to Azure AD, those methods become available in combined registration.
Combined registration modes
There are two modes of combined registration: interrupt and manage.
- Interrupt mode is a wizard-like experience, presented to users when they register or refresh their security info at sign-in.
- Manage mode is part of the user profile and allows users to manage their security info.
For both modes, users who have previously registered a method that can be used for Azure AD Multi-Factor Authentication need to perform multifactor authentication before they can access their security info. Users must confirm their information before continuing to use their previously registered methods.
Interrupt mode
Combined registration adheres to both multifactor authentication and SSPR policies, if both are enabled for your tenant. These policies control whether a user is interrupted for registration during sign-in and which methods are available for registration. If only an SSPR policy is enabled, then users will be able to skip (indefinitely) the registration interruption and complete it at a later time.
The following are sample scenarios where users might be prompted to register or refresh their security info:
- Multifactor Authentication registration enforced through Identity Protection: Users are asked to register during sign-in. They register multifactor authentication methods and SSPR methods (if the user is enabled for SSPR).
- Multifactor Authentication registration enforced through per-user multifactor authentication: Users are asked to register during sign-in. They register multifactor authentication methods and SSPR methods (if the user is enabled for SSPR).
- Multifactor Authentication registration enforced through Conditional Access or other policies: Users are asked to register when they use a resource that requires multifactor authentication. They register multifactor authentication methods and SSPR methods (if the user is enabled for SSPR).
- SSPR registration enforced: Users are asked to register during sign-in. They register only SSPR methods.
- SSPR refresh enforced: Users are required to review their security info at an interval set by the admin. Users are shown their info and can confirm the current info or make changes if needed.
When registration is enforced, users are shown the minimum number of methods needed to be compliant with both multifactor authentication and SSPR policies, from most to least secure. Users going through combined registration where both MFA and SSPR registration is enforced and the SSPR policy requires two methods will first be required to register an MFA method as the first method and can select another MFA or SSPR specific method as the second registered method (e.g. email, security questions etc.)
Consider the following example scenario:
- A user is enabled for SSPR. The SSPR policy requires two methods to reset and has enabled Authenticator app, email, and phone.
- When the user chooses to register, two methods are required:
- The user is shown Authenticator app and phone by default.
- The user can choose to register email instead of Authenticator app or phone.
The following flowchart describes which methods are shown to a user when interrupted to register during sign-in:
If you have both multifactor authentication and SSPR enabled, we recommend that you enforce multifactor authentication registration.
If the SSPR policy requires users to review their security info at regular intervals, users are interrupted during sign-in and shown all their registered methods. They can confirm the current info if it's up to date, or they can make changes if they need to. Users must perform multi-factor authentication when accessing this page.
Manage mode
Users can access manage mode by going to https://aka.ms/mysecurityinfo or by selecting Security info from My Account. From there, users can add methods, delete or change existing methods, change the default method, and more.
Key usage scenarios
Set up security info during sign-in
An admin has enforced registration.
A user has not set up all required security info and goes to the Azure portal. After the user enters the user name and password, the user is prompted to set up security info. The user then follows the steps shown in the wizard to set up the required security info. If your settings allow it, the user can choose to set up methods other than those shown by default. After users complete the wizard, they review the methods they set up and their default method for multifactor authentication. To complete the setup process, the user confirms the info and continues to the Azure portal.
Set up security info from My Account
An admin has not enforced registration.
A user who hasn't yet set up all required security info goes to https://myaccount.microsoft.com. The user selects Security info in the left pane. From there, the user chooses to add a method, selects any of the methods available, and follows the steps to set up that method. When finished, the user sees the method that was set up on the Security info page.
Set up other methods after partial registration
If a user has partially satisfied MFA or SSPR registration due to existing authentication method registrations performed by the user or admin, users will only be asked to register additional information allowed by the Authentication methods policy settings when registration is required. If more than one other authentication method is available for the user to choose and register, an option on the registration experience titled I want to set up another method will be shown and allow the user to set up their desired authentication method.
Delete security info from My Account
A user who has previously set up at least one method navigates to https://aka.ms/mysecurityinfo. The user chooses to delete one of the previously registered methods. When finished, the user no longer sees that method on the Security info page.
Change the default method from My Account
A user who has previously set up at least one method that can be used for multifactor authentication navigates to https://aka.ms/mysecurityinfo. The user changes the current default method to a different default method. When finished, the user sees the new default method on the Security info page.
Switch directory
An external identity such as a B2B user may need to switch the directory to change the security registration information for a third-party tenant.In addition, users who access a resource tenant may be confused when they change settings in their home tenant but don't see the changes reflected in the resource tenant.
For example, a user sets Microsoft Authenticator app push notification as the primary authentication to sign-in to home tenant and also has SMS/Text as another option.This user is also configured with SMS/Text option on a resource tenant.If this user removes SMS/Text as one of the authentication options on their home tenant, they get confused when access to the resource tenant asks them to respond to SMS/Text message.
To switch the directory in the Azure portal, click the user account name in the upper right corner and click Switch directory.
Or, you can specify a tenant by URL to access security information.
https://mysignins.microsoft.com/security-info?tenant=<Tenant Name>
https://mysignins.microsoft.com/security-info/?tenantId=<Tenant ID>
Next steps
To get started, see the tutorials to enable self-service password reset and enable Azure AD Multi-Factor Authentication.
Learn how to enable combined registration in your tenant or force users to re-register authentication methods.
You can also review the available methods for Azure AD Multi-Factor Authentication and SSPR.
FAQs
How do I enable combined registration for SSPR and MFA? ›
Go to User–>User settings–>Choose the setting “Manage user preview settings”. Under the option “Users can use the combined security information registration experience” choose “All” and then click “Save”. At the next login via the web portal, users should be prompted if they have not set up MFA/SSPR.
Which three authentication types support both SSPR and MFA? ›SMS and Voice call are both available for MFA usage, as well as SSPR usage; but app passwords can only be used for MFA – and even in those cases, it can only be used in certain conditions. The Azure AD password is considered an authentication method. It's the only authentication method that cannot be disabled.
Is MFA required for SSPR? ›Users going through combined registration where both MFA and SSPR registration is enforced and the SSPR policy requires two methods will first be required to register an MFA method as the first method and can select another MFA or SSPR specific method as the second registered method (e.g. email, security questions etc. ...
Can you use SSPR self service password reset with Microsoft authenticator? ›Mobile app and SSPR
When using a mobile app as a method for password reset, like the Microsoft Authenticator app, the following considerations apply: When administrators require one method be used to reset a password, verification code is the only option available.
Enable combined registration
Go to Azure Active Directory > User settings > Manage user feature settings. Under Users can use the combined security information registration experience, choose to enable for a Selected group of users or for All users.
Azure MFA requires Users to have Azure AD Premium P1 or P2 License.
What are the three 3 main types of authentication? ›Authentication factors can be classified into three groups: something you know: a password or personal identification number (PIN); something you have: a token, such as bank card; something you are: biometrics, such as fingerprints and voice recognition.
What are the three 3 common identification and authentication methods? ›Common types of biometrics include the following: Fingerprint scanning verifies authentication based on a user's fingerprints. Facial recognition uses the person's facial characteristics for verification. Iris recognition scans the user's eye with infrared to compare patterns against a saved profile.
Which three authentication methods can be used by Azure MFA? ›Available verification methods
The following additional forms of verification can be used with Azure AD Multi-Factor Authentication: Microsoft Authenticator app. Windows Hello for Business. FIDO2 security key.
Sign in to the Azure portal. Search for and select Azure Active Directory, then select Password reset from the menu on the left side. From the Properties page, under the option Self service password reset enabled, select None. To apply the SSPR change, select Save.
Does Self service password reset require MFA? ›
Self-Service Password Reset (SSPR) allows you to reset your Microsoft 365 account password yourself by confirming your identity with the MFA method. This avoids a call to the service desk to reset your password. To register for MFA and Self-Service Password Resets, follow the steps below.
Is multi factor authentication mandatory? ›Partners are required to enforce MFA for all user accounts in their partner tenant, including guest users.
What are the authentication methods supported for self-service password reset? ›When SSPR is enabled, users can only reset their password if they have data present in the authentication methods that the administrator has enabled. Methods include phone, Authenticator app notification, security questions, etc.
Is Microsoft authenticator safer than password? ›An authenticator app provides an additional layer of security that is more than just a username and password. Authentication is the process a user goes through to validate who they are by way of logging basic identification details such as an email address or username followed by a password.
What is MFA and SSPR? ›Multi-Factor Authentication (MFA) and Self-Service Password Reset (SSPR)
What license is required for SSPR? ›If you are planning for SSPR for Cloud users, then you will need to have an Azure AD Basic, Premium P1 or P2, or a Microsoft 365 Business subscription. If you are synchronizing your users from your on-premises Active Directory, then you will need an Azure AD Premium P1 or P2 or a Microsoft 365 Business subscription.
What does SSPR registered mean? ›Self-service password reset (SSPR) is a solution that provides an automated process that allows end users to reset or regain access to their account password without help desk involvement by proving their identity via alternative means.
What is the strongest form of multi-factor authentication? ›Physical Security Key (Hardware Token) The strongest level of 2FA online account protection and the best phishing attack prevention is a physical security key.
What are those 4 commonly authentication methods *? ›Common biometric authentication methods include fingerprint identification, voice recognition, retinal and iris scans, and face scanning and recognition.
What are the 4 factors of authentication? ›Four-factor authentication (4FA) is the use of four types of identity-confirming credentials, typically categorized as knowledge, possession, inherence and location factors.
What are the three 3 authentication methods that can be used to assign access rights to shared resources? ›
There are three common factors used for authentication: Something you know (such as a password) Something you have (such as a smart card) Something you are (such as a fingerprint or other biometric method)
What is an example of 3 factor authentication? ›Three-factor authentication – in addition to the previous two factors, the third factor is “something a user is.” Examples of a third factor are all biometric such as the user's voice, hand configuration, a fingerprint, a retina scan or similar.
What are the two types of authentication Microsoft Azure Active Directory users? ›Microsoft offers the following three passwordless authentication options that integrate with Azure Active Directory (Azure AD): Windows Hello for Business. Microsoft Authenticator app. FIDO2 security keys.
Which two methods can be used to implement multifactor authentication? ›Which methods can be used to implementmultifactor authentication? IDS and IPStokens and hashesVPNs and VLANspasswords and fingerprints*Explanation:A cybersecurity specialist must be aware of the technologies available thatsupport the CIA triad.
How do I authenticate using Azure Active Directory? ›Sign in to the Azure portal, search for and select App Services, and then select your app. Note your app's URL. You'll use it to configure your Azure Active Directory app registration. From the portal menu, select Azure Active Directory, then go to the App registrations tab and select New registration.
Can hackers bypass MFA? ›Another social engineering technique that is becoming popular is known as “consent phishing”. This is where hackers present what looks like a legitimate OAuth login page to the user. The hacker will request the level of access they need, and if access is granted, they can bypass MFA verification.
How do attackers bypass MFA? ›MFA bypass via proxy attacks
In a proxy attack, the phishing site sits between the user and the target website. The phishing site passes relevant web pages and data, including passwords and multifactor authentication, back and forth between the user and the target site.
Require Re-register MFA makes it so that when the user signs in next time, they're requested to set up a new MFA authentication method. The user's currently registered authentication methods aren't deleted when an admin requires re-registration for MFA.
Is Microsoft forcing MFA? ›Admins will always be prompted for MFA on login. Users will be prompted for MFA "when necessary" (this is not strictly defined by Microsoft but includes when users show up on a new device or app, and for critical roles and tasks). Access to Azure portal, Azure CLI or Azure PowerShell by anyone will always require MFA.
What is the risk of multifactor authentication? ›This is extremely dangerous if the attacker is then able to brute-force the verification code as it would allow them to log in to arbitrary users' accounts based entirely on their username. They would never even need to know the user's password.
Which three authentication types are supported by both SSPR and MFA? ›
SMS and Voice call are both available for MFA usage, as well as SSPR usage; but app passwords can only be used for MFA – and even in those cases, it can only be used in certain conditions. The Azure AD password is considered an authentication method. It's the only authentication method that cannot be disabled.
What is the 6-digit code from my authentication app? ›Google Authenticator is a software-based authentication token developed by Google. The token provides an authenticator, which is a six digit number users must enter as the second factor of authentication. You need to install the Google Authenticator app on your smart phone or tablet devices.
What is the 6-digit code from my authentication app for Instagram? ›When you add multiple devices to two-factor authentication on a single Instagram account, you'll get a 6-digit login code from the authentication app on that device. Keep in mind that one device will need to set up two-factor authentication through an authentication app first before other devices can be added.
Does Microsoft Authenticator track browsing history? ›The Microsoft Authenticator app can be used to authenticate to many resources including personal accounts (such as your bank), work or school accounts, and other accounts (such as LinkedIn). Does the Microsoft Authenticator track me? The Microsoft authenticator does not track you and it does not log location data.
Can Microsoft Authenticator track your location? ›A: The Authenticator app collects your GPS information to determine what country you are located in. The country name and location coordinates are sent back to the system to determine if you are allowed to access the protected resource.
Can Microsoft MFA be hacked? ›MFA Fatigue: A Novel Hacking Tactic
In an MFA Fatigue Attack, a hacker will make multiple attempts to log into a given user account configured with multi-factor authentication, using stolen credentials, sending an endless stream of sign-in approval requests to the user's device.
SSO: How Do MFA and SSO Work Together? MFA and SSO are not mutually exclusive. As a matter of fact, you can combine these two technologies to provide your users with high security while ensuring a good user experience. MFA can add an extra layer of protection to the SSO logins of your users.
Do we have to enable MFA at both the SSO and Salesforce levels? ›Do we have to enable MFA at both the SSO and Salesforce levels? No. If MFA is enabled for your SSO identity provider, you don't need to enable Salesforce's MFA for users who log in via SSO.
How do I enable multi-factor authentication on my MFA? ›Choose the Security Credentials tab. Under Multi-factor authentication (MFA), choose Assign MFA device. In the Select MFA device wizard, type a Device name, choose Authenticator app, and then choose Next. IAM generates and displays configuration information for the virtual MFA device, including a QR code graphic.
Can hackers beat MFA? ›Multifactor authentication provides a high level of security, but phishers, scammers and other malicious actors are highly motivated to find ways around this protection so they can steal valuable data. Hackers use techniques called MFA bypass to defeat MFA.
What is the difference between 2 factor authentication and multi factor authentication? ›
MFA vs 2FA. So, two-factor authentication (2FA) requires users to present two types of authentication, while MFA requires users to present at least two, if not more types of authentication. This means that all 2FA is an MFA, but not all MFA is a 2FA.
What is the difference between enabled and enforced MFA? ›Enabled: The user has been enrolled in MFA but has not completed the registration process. They will be prompted to complete the registration process the next time they sign in. Enforced: The user has been enrolled and has completed the MFA registration process.
Should MFA be enabled on service accounts? ›Requiring multifactor authentication (MFA) on those accounts is an easy way to reduce the risk of those accounts being compromised. Microsoft recommends you require MFA on the following roles at a minimum, based on identity score recommendations: Global administrator. Application administrator.
Why is my multi factor authentication not working? ›The most common cause of 2-factor authentication problems is that the time on your Google Authenticator app is not synced correctly.
Can you bypass 2 step verification? ›Some platforms enable users to generate tokens in advance, sometimes providing a document with a certain number of codes that can be used in the future to bypass 2FA should the service fail. If an attacker obtains the user password and gains access to that document, they can bypass 2FA.
What happens if MFA is not enabled? ›If you use Microsoft 365 products and you don't have MFA (Multi-Factor Authentication) enabled in your organization yet, you are at heightened risk of user accounts getting compromised.
How do you find the 6-digit code for two factor authentication? ›You need to install the Google Authenticator app on your smart phone or tablet devices. It generates a six-digit number, which changes every 30 seconds. With the app, you don't have to wait a few seconds to receive a text message.
How do I get my 6-digit code from Authenticator? ›How do I get the 6-digit code from Authenticator app? To receive a 6-digit code on your device via Authenticator App, you'll need to copy the given key from the Instagram app and enter it in the Authenticator App to link it to Instagram.