![]() ![]() The Azure AD account for the person is not assigned the Microsoft Azure Multi-Factor Authentication license (plan). Unfortunately, the status reason User failed to start the registration for Authenticator App with Notification and Code from the above log entry is not part of Microsoft’s Troubleshooting combined security information registration Docs page. In the Azure AD audit logs, we found the following information: For instance, when registering the Authenticator App, the person gets the following error in the registration experience after taking a photo of the QR code in the Authenticator App: Independent of the method chosen, the person gets an error. No Conditional Access policies were created or modified to include the Register security information action.Ī person in the organization tries to register the security information for their Azure AD account. ![]() All authentication methods in the legacy PhoneFactor portal are still allowed.The combined registration for Azure MFA and Azure AD Self-service Password Reset is enabled.The Security Defaults feature is disabled.When you run into the same situation, you might find it helpful.Īn Azure AD admin has configured the following tenant-wide settings: As is our mutual expectation, I decided to document the issue. Today, Raymond and I troubleshooted an issue for several people who received the ‘Sorry, we ran into a problem’ error when trying to register their security information. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |