Run Azure AD B2C's sign-up & sign-in pages under a custom domain, for e.g., login.contoso.com, instead of login.microsoftonline.com.
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
@Azure AD Team - Thank you for the update on this, we are very interested in testing this out when its available
Miguel Ansaras commented
I would be grateful to receive confirmation that by raising a customer support ticket it will be possible to have a full custom domain such as login.<organisation_name>.com, instead of <organization_name>.b2clogin.com.
Greg Allain commented
@Nasos Kladakis @Amber Smith
Hi, I've created a support ticket for a custom domain request
Dhananjay Modak commented
We have been looking at the product, but this is a big sticking point. Any plans to address this?
M Farag commented
Any updates on that? I know it is in private preview right now, anytime expected for GA?
Shaun Hayward commented
Wow, this is pathetic.
I just spent a week researching and learning B2C. It's a very impressive product. I present my recommendations to the CTO tomorrow and B2C was a slam dunk.
Since discovering this, it's not a slam dunk.
What a basic and fundamental feature to have started THREE years ago and not finished.
Michael Unterberger commented
Has Microsoft given up on this?
It's a vital feature for every serious solution seeking to use Azure AD B2C.
Horia Pop (Admin) commented
It is just unacceptable to not have this working after three years!
How do you expect companies to use AAD B2C service with a non own domain put in front of their users to input their passwords?
this thing shows that it has started back in 2017?
does it really need 4 years to do this? i doubt ADB2C took that long!
Andrew Bambury commented
Hi @Nasos and @Amber
I have created a support ticket: 120062925001687
would very much appreciate a custom domain login for our production b2c tenant, as it breaks our token auto-renewal on many browsers
Chen Y Machluf commented
Wow, I can't believe this feature is missing.
How the h*ll I suppose to release this to customers? It makes all ADB2C not relevant.
I can't believe I wasted a week to integrate it.
D*mn Microsft , D*mn
Malcolm Jack commented
still not implemented ?!?
Aurel Avramescu commented
Subway is using B2C with their own domain. How they are doing it?
Almost 4 years and no progress? Any ideas about ETA?
Louis C commented
I'm building a Xamarin app and intended to use Azure AD B2C for authorisation, but sadly this really is a deal-breaker.
The industry has been training users for years now to be suspicious of URLs they don't recognise appearing in their browser, but now we're asking people to put email addresses and passwords into a site with a URL that has nothing to do with the service they were signing up for? microsoftonline.com was bad enough because it really does look like a phishing attempt at making someone think they're on a page created by Microsoft. But there's just no way I can put "b2clogin.com" in front of users.
Moving to auth0.
Viktor Grus commented
So adding custom domain name through Azure Active Directory (not B2C) resource in portal does not solve this issue ?
when is the next update
Jesus Santander commented
We have a ready to production using Azure AD B2C, but without a custom domain is not viable for us. I'm wondering if this is going to be ready soon? if so, we can adopt a temporary 3rd provider solution and if not, we will adopt 3rd provider.
Any ETA updates guys?
Kumar Vivek commented
Any update on this? Guys it has been years now! Its a paid service and mandatory requirement, how can you build something without thinking about this basic feature.