Azure AD B2C user does not receive the email with the verification code

Question

Hello,

We are currently experiencing an issue with an user who is trying to sign in to our B2C tenant application but is not receiving the email verification code.

We are using Azure AD** B2C** for user management.

The user has the following domain: @libero.it

For all other domains, email delivery is working as expected.

Email details:

Sender: ****@microsoftonline.com

Subject: <Tenant name> account email verification code

Could you please advise if there is a way to resolve this issue?

Additionally, is it possible to access delivery logs for these email verification messages in order to understand whether the emails were sent and, if so, why they were not delivered to those specific recipients?

Thank you in advance for your support.

Answer 1

For a single domain such as @libero.it not receiving Azure AD B2C verification emails while others work, the behavior matches a delivery or filtering issue on the recipient side rather than a general B2C problem.

Key checks and actions:

1. Ask the affected user to check Junk/Spam
   • Verification codes are sent from an address like @accountprotection.microsoft.com or @microsoftonline.com.
   • The user should check Junk/Spam and any quarantine folders and mark the sender as a trusted/safe sender so future codes arrive in the inbox.
   • This is the same pattern as when SharePoint secure-link verification codes do not appear and must be located in Junk/Spam first.
2. Confirm the email address is correct in the account
   • Ensure the user’s email in the B2C account is exactly correct (no typos, no wrong domain variant).
   • In Microsoft account scenarios, only the primary alias or configured verification email receives codes; the same principle applies conceptually in B2C—codes go only to the configured address.
3. Check for domain-level blocking or filtering
   • Since other domains work, libero.it may be:
     • Rejecting or silently dropping messages from @microsoftonline.com / @accountprotection.microsoft.com, or
     • Aggressively filtering them to spam.
   • The recipient’s mail provider or admin must review their spam/quarantine settings and allow the sender domain.
4. Rate limiting / unusual activity
   • Excessive or repetitive requests for verification codes can cause Microsoft to temporarily stop sending codes to protect against abuse. Waiting and reducing repeated attempts can help if this is the case.
5. Logs and delivery tracing
   • For Microsoft consumer accounts and B2C verification messages, there is no customer-accessible, detailed delivery log for these system-generated verification emails similar to Exchange Online message trace.
   • The only practical checks are:
     • Confirming the address is correct and configured.
     • Having the recipient check their mailbox (including Junk/Spam) and any local rules.
     • If the domain is managed by an admin, they can check their own mail system’s logs for inbound messages from Microsoft and adjust filtering.

If the user still cannot receive codes, the only supported options are to use an alternate verification method (different email or phone) if configured, or to follow the account recovery/alternate sign-in flows provided by the application.

---

References:

• Troubleshoot Microsoft verification code issues
• No verification code when external recipients access shared secure links