Add support for the Microsoft Authenticator app in B2C
Enable the Microsoft Authenticator app to be used for 2FA in Azure B2C.
We are looking to add additional MFA options for Azure AD B2C in the next few months. As part of the investigation, we want to learn more about your requirements. Email your feedback to email@example.com.
When you say “support for Microsoft Authenticator”, which feature are you referring to?
1. The ability to see the codes in the authenticator app
2. The ability to receive push notifications for MFA
If both, which do you prefer more?
Again, please email your feedback to firstname.lastname@example.org. Feel free to include more details about your scenarios/requirements!
Norman Noonan | Flextime commented
I would like clarity in relation to charging for MFA with ADB2C. Currently the documentation states that charges apply when utilising only Voice or SMS.
This would imply using the Authenticator app to implement MFA with ADB2C will not incurr a charge.
Will North commented
will the authenticator app be supported soon and will there be a charge per MFA?
Ewan Crowe commented
We need the push notification ideally but both options would be good.
Bert Haggren commented
Both options is a must for us.
Marco Rentier commented
Will Microsoft Authenticator app becoming available in the AD free tier ( https://www.microsoft.com/security/blog/2019/11/04/microsoft-announces-new-innovations-in-security-compliance-and-identity-at-ignite/ ) make it easier to roll out this feature?
Yuri Nijsen commented
Any news on this item?
Both options but with #2 being preferred.
Yuri Nijsen commented
Christmas is coming, will it be there?
You can use custom policy to implement this feature. The sample is https://github.com/azure-ad-b2c/samples/tree/master/policies/custom-mfa-totp
Could we have an update of the status of this. The original comment said "in the next few months" over 2 years ago.
Without a secure 2FA mechanism (i.e. not SMS) we cannot use AD B2C.
Priority 1 - The ability to see the codes in the authenticator app
Rick van den Bosch commented
I think Azure AD B2C needs to support using the Authenticator app in all scenarios available. If I have to give one a preference, it would be option 2: The ability to receive push notifications for MFA.
Gijsbert Huijsen commented
Any of the two options would be an improvement for us, as currently the authenticator app cannot be used at all with B2C. We prefer option 2 as this is more user friendly.
My question is: Could you please remove the status NEED-FEEDBACK from this issue and please add this feature to your roadmap?
Ralph Blokpoel commented
Personally I prefer option #2 but both should be implemented without preference (and asap as far as I'm concerned)
Lasse Seten commented
We really would see a benefit to this as SMS system often is unreliable. Both should be implemented, no preference.
Andrew Cameron commented
An option that leverages #2 only makes it a bit easier of a UX (customer doesn't have to jump to Authenticator app to view a code), but both options should be available to implement.
Peter Hall commented
The app (push notification) is a substantially better user experience than a SMS, any news on this? And even better if we could go password-less.
#2 mainly. But both would be nice.
Wim van den Heijkant commented
Our experience is that "the phone system" is a lot slower and less reliable then the app. Even in a country like the Netherlands in a City like The Hague.. The push notification is just a lot more convenient, user friendly, reliable and fast.
Gabriel Corrêa de Oliveira commented
How does the MS Authenticator work with B2C today? How is it configured?