You can use the login_hint parameter for this.
We are looking for private preview customers who are interested in using Azure AD (single tenant only) or any other custom OIDC compliant identity providers in your built-in policies. If you are interested, please send an email specifying this specific request to firstname.lastname@example.org with your Azure AD B2C tenant name.
We have a private preview of this feature available. If you are interested in joining, please contact email@example.com with the name of your tenant.
Thanks for the feedback. So to clarify, you would the ability to interrupt the user during the sign in process to ensure their info is in sync with the identity provider they are using. Is that correct? Would you like to see this at all times or just when the data is out of sync?
Could you elaborate more on the use case for this?
We are in the process of planning this feature and hope to have a preview available by the end of november. In the meantime, could you please respond to firstname.lastname@example.org with your responses to the following questions:
- If you had a “password change” policy, what kind of information would you like to get back once the policy has been executed?
- Would you prefer to have a policy that forces you to sign in first, and then asks you to change the password, or one that let’s you do it all on the same page?
- Would you want an email to get sent out to the user whenever the password is changed?
We are currently prioritizing Azure AD as and identity provider into B2C. We will review this request after that work is done. Keep the requests coming! /Jose Rojas
We continue evaluating several alternatives to provide full email customization. We are actively working on an alternative.
Unfortunately we do no yet have an ETA.
Thank you. We will examine the experience of duplicate sign ups across Identity providers. Would performing this check by using the email address be sufficient?
BTW, Linking multiple provider accounts to one user is in our roadmap and we’ve already achieved it in preview…
We look forward to your feedback
Due to various technical limitations, the first iteration of the customer-owned domains functionality will not be available for a few more months. We will provide an update as soon as we can get a more specific ETA.
We definitely recognize the popularity of this feature, and we discuss it constantly during the planning phases. However there are certain technical limitations in the system that add a large amount of development cost. Because of the cost and the fact that there is a workaround available, other features get prioritized over this one.
That being said, please keep voting for it. The popularity of the feature does help bring it up and makes us reconsider every time.
Apologies for the delay.
We’re doing some research both on the specifics of this ask as well as what it would take to support this.
Is the ask here to do the same thing that regular Azure AD does (see: https://blogs.technet.microsoft.com/enterprisemobility/2014/12/18/azure-active-directory-now-with-group-claims-and-application-roles/) or is are there different requirements around this for Azure AD B2C?
An error occurred while saving the commentGreg Fyans commented
Is there an update to Alexander's suggestion? It would seem to me this is a popular use case for applications using B2C, as B2C is essentially a replacement for more common membership providers that have such functionality.
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.
This is a scenario we are looking to support in the future however, it is not on our immediate roadmap for the next 6 months. Please continue voting and we will evaluate at a later date.
This is not planned for the next 6 months. If this is needed for your scenario, please continue voting and we will re-evaluate at a later.