MFA sending multiple text messages

[Deleted]

We're looking at enabling MFA across our organisation, but in pilot group testing we have received feedback from our users that when at home (or other untrusted/unknown network), if the user starts their laptop and three applications try launch at the same time, eg. OneDrive Sync, Skype for Business and Outlook, the user receives 3 seperate SMS/text messages from Microsoft for MFA but appears to cause confusion as to which MFA code relates to which application.

I'd be interested to hear your thoughts or opinions on this and how you'd approach fixing this for users who would encounter this?

[#2]

I'd strongly recommend using the authenticator app instead with the notification method configured, it's the only method that can give you context as to what the MFA request you're seeing is for.

[#3]

I believe that you can also force the end users to reset their MFA contact info so it defaults to the app.

Maybe this article will help - https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfa-userdevicesettings

[#4]

thanks I already do and have recommended to do so but have found there are going to be pockets of people who don't want to install the app or in fact don't have a smart phone so can only receive text/SMS...

[#5 · Accepted solution]

thanks

[#6]

Hi Baronne,

I facing a similar issue, have you found any solutions please?

In my case though, when my users log into O365 they receive 3 messages.

All 3 codes contained in each message fail when they attempt to authenticate.

It quite frustrating.

[#7]

we ended up advising people to use the authenticator app

[#8]

It seems that this hasn't been fixed. Today I got 12 codes for verification most of them (8-9) out of the blue. I'm only using Outlook 2016 and logged online once or twice.

G

[#9]

I am piloting MFA and having the exact same experience. Random SMS texts telling me to authenticate on my phone, or multiple SMS alerts when firing up my laptop.

in ADFS 2019, there is this

• Bug fix: Persistent SSO state for Win10 devices when doing PRT auth This addresses an issue where MFA state was not persisted when using PRT authentication for Windows 10 devices. The result of the issue was that end users would get prompted for 2nd factor credential (MFA) frequently. The fix also makes the experience consistent when device auth is successfully performed via client TLS and via PRT mechanism.

not sure if the above fixes it

but i can't recommend rolling it out like this. I will have to look at alternative vendors.