Forum Discussion
No push notifications from authenticator app when switching to Azure AD B2C direcories
Hi all,
I'm currently facing issues switching to one of my Azure AD B2C directories.
When I try to switch from my primary directory to the B2C directory, it prompts me with 2fa (which it should) however, I don't get the message on my phone. When I try to enter the temporary 6-digit number (xxx-xxx) it fails, saying that the code is incorrect.
Now the interesting part
the 2fa push message works perfectly fine when I try to sign in to my other MS products with the same profile, so I don't think it's a setting on the phone or my profile (I have followed all the "microsoft authenticator app no push notification" topics online).
Is there a temporary problem with Azure? How do I fix this? I have alternate methods, like SMS, call, and even an alternate Email, but I can't choose any of them in the login process. Also, I have restarted the phone, reassigned the account to the app, and more.
Is anyone facing the same issues?
Regards,
Steffen
1 Reply
You may take a look at the following area:
1. Check MFA settings in Azure AD B2C:
- Go to your B2C tenant in the Azure portal.
- Navigate to Authentication Methods.
- Ensure Microsoft Authenticator push notifications are enabled for your user flow.2. Re-register MFA for the B2C account:
- Remove the B2C account from the Authenticator app.
- Re-add it by signing in through a protected app or portal that triggers MFA setup.
3. Use Conditional Access Policies:
- If you're using custom policies, verify that push MFA is allowed and prioritized.
4. Fallback Options:
- Unfortunately, B2C login flows may not always offer alternate MFA methods (SMS, call, email) unless explicitly configured. You may need to adjust the user flow or use a custom policy to expose those options.
