Verification emails have stopped arriving across multiple Azure B2C tenants, affecting internal and external users. Service Health doesn't show an obvious incident for the affected tenants. What should we check, and is there a safe workaround?
Are Azure B2C email verification codes not arriving for anyone else?
Answers
There are reports of the same problem across multiple tenants in the US and Europe, so it may be broader than one application's configuration. That doesn't establish the cause or mean every tenant is affected.
Check Service Health and the status dashboard, but don't assume an empty tenant health page rules out an incident. Reports differ on whether an announcement was visible. If you have a support plan, open a ticket with affected tenant details and the time of the last successful delivery.
Reply to this answer
Look at both sides of the mail flow. Some B2C audit logs reportedly show the send verification email operation as successful even when the message never arrives. Check the recipient's mail trace, filtering and delays too. A successful send event alone doesn't prove delivery.
Reply to this answer
Some affected teams have temporarily disabled email MFA or Conditional Access policies in the user flow to let users continue. That's a security tradeoff, not a general fix. Get the appropriate approval, understand which protections you're removing, and restore them when the issue is resolved.
It also won't necessarily help every flow. Password reset verification emails have reportedly been affected too.
Reply to this answer
Browser cache clearing was reported to help in one case, but another report says a private browsing session made no difference. It's a quick test for an individual user, not a reliable fix for emails that aren't being delivered.
Reply to this answer
Add your answer
Answers are reviewed before publication.
c.731~fablewinder:
Some reports also mention wider incoming and outgoing mail delays, so the verification flow might not be the only thing worth checking.