![]() ![]() We did eventually get the process to complete by fully removing the Microsoft Authenticator app from the device. ![]() This still did not make any improvements. This has been attempted but nothing changes in the process.Īdditionally, we have removed the Authenticator App from the user so it is no longer associated with the user and is no longer an option as an MFA method. The error reported from the Intune Company Portal app indicates that the app data may be corrupted and needs to be reinstalled. If you switch back to the Intune Company Portal, it reports an error and asks to retry or close. After the user confirms the MFA challenge the Authenticator App goes to white a screen and never proceeds. ![]() Set the MFA caller ID number to the number you want users to see on their phones. The login process switches over to the Microsoft Authenticator App and seems to process normally. To configure your own caller ID number, complete the following steps: Go to Azure Active Directory > Security > Multifactor authentication > Phone call settings. When it proceeds to the second step where it needs to download the management profile, the user is prompted to login again. This begins the process of enrolling the device with EndPoint Manager. The user launches the Intune Company Portal app and is able to login just fine. ![]() We have run into an issue if the device is already using the Microsoft Authenticator App. This preview brings both push notifications and TOTP to the Outlook. No additional installation of the Microsoft Authenticator app is needed. Users can now enroll for Azure MFA using just their Outlook mobile app. We are trying to enroll our iOS devices into EndPoint Manager. Microsoft released a new feature where the Outlook mobile app now has some of the Microsoft Authenticator App features onboard. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |