Hi @Anonymous ,
this is a clumsy one 🙂
When you use b2c for signing up, the users first create an account in azure b2c and the user (contact) in portal would then be created with the external id gathered from the b2c. Then its too late 🙂 (and it may be does not work, when the email is already present)
If i were to do it, i would do it the other way round: use your contacts which are planned for portal users to create azure b2c user (there is an api, i tried it once with powershell). Then assign an external identity to the contact which refers to the azure b2c directory.
There are a bunch of attributes to be set like userid, securitytoken, log in enabled and things like that.
Additionally disable accountcreation in your portal.
Of course, you now have to let the users know, that they have a userid in your b2c 🙂
Another idea would be, to invite users to the portal. I am not sure, whether it works: when you disable local accounts and allow azure b2c the users should cerate an account in the b2c directory and then they know 🙂 . But as i said: i do not know, whether redeeming invitations to the portal also work with only b2c set up with prior to the invitation no b2c account is there. No idea, would have to look by myself 🙂 .
So, may be one of these two idea help you to sort out what to do. Is case of questions just feel free to ask 🙂
Have fun,
Christian
