question

Hi @AbhayChandramouli-2076 • Thank you for reaching out.

The sign-in logs contain the sign-in activities of the Local (signed up) users but the authentication for signing in to the application(s) using B2C user flows/custom policy is facilitated by ProxyIdentityExperienceFramework and IdentityExperienceFramework applications. So, you won't see the information by the actual application registered to use user flows/custom policy in the sign-in activity logs. Rather you will see the Application: ProxyIdentityExperienceFramework and Resource: IdentityExperienceFramework in the sign-in activity of the local users.

Read More:
Ref: https://docs.microsoft.com/en-us/azure/active-directory-b2c/tutorial-create-user-flows?pivots=b2c-custom-policy#register-identity-experience-framework-applications
Azure AD B2C requires you to register two applications that it uses to sign up and sign in users with local accounts: IdentityExperienceFramework, a web API, and ProxyIdentityExperienceFramework, a native app with delegated permission to the IdentityExperienceFramework app. Your users can sign up with an email address or username and a password to access your tenant-registered applications, which creates a "local account."

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.