First, we removed the Microsoft Authenticator app and reinstalled it… unfortunately that didn’t work. So it must be a problem with the device itself. I guess we can rule out a user-based issue. We scanned the QR code on a different iPhone and it immediately worked. The next thing we tried, was determining if it was a user or device problem. I hoped to see the problem user but again no luck. To make sure this wasn’t our issue, we opened the Azure Ad Portal and opened the MFA settings.Īs shown above, it clearly stated: No results. Every blog says the same damn thing… you will need to unblock your user. again the same error.Įveryone tells you that Google is your best friend, so we googled the error. Okay, let’s try to require the user to re-register MFA, maybe something will be fixed in the background. The first thing we tried, removing the account in Microsoft Authenticator and adding the account again. Please make sure push notifications are enabled.
So we did… but you can guess the outcome, the same error occurred. You have already used this QR code to add an account. I will divide this blog into multiple parts The Authenticator threw 2 different kinds of errors when scanning the QR-Code. We handed out the surface, so the user could complete the steps to configure Windows Hello and set up MFA with the Microsoft Authenticator app. It’s obvious that MFA needs to be required when devices need to join Azure Ad.
We were very glad because it can really save some time. The user in question already had the Company and Authenticator app installed on their iPhone.
This blog will be about a weird MFA problem when we were enrolling devices and at the same time configuring MFA.
0 kommentar(er)
