Back to Blog
Thankfully this one was an easy fix!Īfter fixing the above, device registration worked fine through the app.Īfter registering the device, the next step was to enable the additional notifications required for password-less MFA within the app. There were a number of failed sign-ins which were caused by us reaching the configured limit for the maximum number of devices that can be joined per user (screenshot of config setting below). To troubleshoot the issue, I had a look at the Sign-in history in the User Details blade for the specific users in question. Something went wrong error in the MS Authenticator app FYI this is the first of two errors so skip this bit if device registration works fine for your users. At this point, for some of our staff device registration failed and we got a ‘Something went wrong’ error in the app (see screenshot below). At this point, to use password-less auth, your users need to register their IOS/Android devices with your Azure AD (if they haven’t already). I set-up password-less using the official Microsoft guide (this is the one I imagine will be updated) and ran the PowerShell cmdlet to configure the Azure AD policy. The documentation is going to be updated though so keep an eye out for that. However I did hit a few snags along the way but got there in the end with some sterling help from the Microsoft Authenticator team – thanks guys! I thought I would blog about the issues I encountered along the way in case anyone else comes across them too. If you’re thinking of enabling it – I can confirm – it’s brilliant! but keep in mind it’s still in public preview. A number of our staff already used the Authenticator app for MFA sign-in so it made sense to make the move to password-less! I recently enabled password-less authentication for our Azure tenant.
0 Comments
Read More
Leave a Reply. |