We have a sample for this use case here: https://github.com/azure-ad-b2c/samples/tree/master/policies/invite
Let us know what you think and if this fits your use case.sanjay commented
looks good. One question, If I set username as sign in then how it will work?.
Need username also while creating user. user can sign in using username as well as email address(any one, users choice). If user selects username for sign in. then email address must support for change or recover password. i.e recently i implemented user module using Azure B2C. I am creating user using graph API . But If I Selects username as sign in then the email address which is added while creating user is not supporting to change or recover password.
1 votesanjay shared this idea ·
Thank you for your feedback! We are taking this into consideration and would love to hear any other ideas or concerns you have in the meantime.
Sadie Henry (sahenry)
381 votes49 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →
The MFA team is currently working on adding get/set/read/delete abilities for StrongAuthentication data to the Graph API.
"local account is based on a user name, then the email address is stored in a strong authentication detail property."
How I can store email address in strong authentication detail property while creating local user account through Graph API?. So I can get the email verification code.