Thank you for your patience. We have released custom domains for Azure AD B2C to public preview.
Documentation can be found here: https://docs.microsoft.com/en-us/azure/active-directory-b2c/custom-domain?pivots=b2c-custom-policy
An error occurred while saving the commentSingaravelu Souppourayen commented
Is there any progress on this feature? We need custom url for applications.
This feature is now available in public preview through custom policies. Check out some examples here:
This is available in private preview and we’re actively looking for customers to try it out and give us feedback.
If you’re interested, contact us at firstname.lastname@example.org with the following info:
– TenantName (x.onmicrosoft.com)
– Description of your app and why GitHub is relevant
– Estimated user count (total to the app and specific to GitHub)
We are making this feature available through custom policies. We expect this to be available in public preview in the next few weeks. More details to come.
Twitter is now in public preview! It should be available as one of the identity providers in your Azure AD B2C tenant. Here are the instructions to get setup – https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-setup-twitter-app.
Check it out and let us know if you have any feedback!
Authenticating using a SAML identity provider is now in public preview via custom policies. You can check out the instructions on how to set up a sample SAML identity provider like Salesforce here – https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-setup-sf-app-custom.
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.
Hi all, unfortunately we don’t have plans to share out a public roadmap. This is constantly changing as we’re listening to customer requests. We will continue to update feedback.azure items as they come up so feel free to suggest anything you are curious about.
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
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.
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.