Azure AD B2C Missing Sign In Logs When Using Magic Links

Christopher Norris 6 Reputation points


I have recently deployed the Sign In With Magic Links Template and discovered that when users sign in with the magic-link, there is no sign-in logs generated. Normally, when a user signs in they generate a log that displays the following information in Azure AD B2C > Users > Sign-in logs blade: Date, Request ID, User, Application, Status, IP Address, Location, Conditional Access, Authentication require...

This information is very helpful to our organization and am inquiring to see if this is my design, or are we missing something?

Any help would be greatly appreciated.

Microsoft Entra External ID
Microsoft Entra External ID
A modern identity solution for securing access to customer, citizen and partner-facing apps and services. It is the converged platform of Azure AD External Identities B2B and B2C. Replaces Azure Active Directory External Identities.
2,764 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Yoel Hor 81 Reputation points Microsoft Employee

    There are two logs in Azure AD B2D: Sign-in logs which provides insight into how your users access applications and services. For example, when admin sign-in into the Azure Portal, or Azure AD B2C users sign-in with a local account where their credentials are validated. This log will not show any sign-in activity for other scenarios, such as a user sign-in with a federated account, uses SSO (since the user doesn't sign-in and their credentials aren't validated), or federated accounts. Using the magic link, the user's credentials are not validated, so it's will not appear in that log.

    For Azure AD B2C you should use the audit logs . This is were you can find all of the activities.

    0 comments No comments