This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(278.4, 23%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello!
Our customers are currently not receiving email verification codes to sign in in their application. I checked with them to see if it was in their spam box and I also used my personal email addresses to check it out.
Also it is to be mentioned that Azure B2C is used for user management in our system.
I can see in the B2C audit logs that the email was succesfully send.
All domains seem to have issues. And gmail is one of them.
@gmail.com
The email subj and sender are like this:
From: Microsoft namens Winbase Groep BV ******@microsoftonline.com
Subject: E-mailverificatiecode voor het account Winbase Groep BV
Tell me please is there any way to resolve this issue?
I wanted to check in and see if you had any other questions or if you were able to resolve this issue?
If you have any other questions, please let me know. Thank you for your time and patience throughout this issue.
If the information helped address your question, please Accept the answer. This will help us and also improve searchability for others in the community who might be researching similar information.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 17%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGM%3C/text%3E%3C/svg%3E)
@Aschwin Thank you for reaching out to us, many customers have reported the same yesterday, our engineering team identified the cause and fixed it at earliest. let me know if the issue still persists.