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.
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.
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.
Stuart Foulds-Duncan commented
Any news on when this will be possible?
It seems both Nuffield Health and Real Madrid (both of which are listed on your site) use their own custom URLs, but we cannot.
Brian Brewder commented
This feature is growing in importance as users learn how to avoid Internet scams by checking the domain. Also, complex, unique passwords are difficult to use without a password manager, which could get confused if the user has multiple sites they interact with all using this service.
It's difficult for us to base our login experience around a product that could result in a reduction of sales. There's already enough friction with login without the user worrying about being scammed as well.
James D commented
This is so important to us. Why is there no update since 2017?
Just had a demo with my product manager and now I will need to rip out AD B2C from our software.
redirection to 3rd party domain is simply unacceptable. It is a deal breaker.
It does not matter how wonderful this product is otherwise. This one feature completely destroys its usability.
So please, do yourselves and all of us a favour and start behaving as if you actually care about your paying customers.
Stop implementing the other terribly important features - none of them will get used until and unless we will be able to use our own domain and login pages styled by us.
Lachlan van der Velden commented
This is quite literally blocking me from using this service. How could this not already be implemented! I'm dumb founded...
Peter BRooke commented
Surely if ....
Here's my support ticket : 120032423001418
Its perplexing to me that the development started on 2017 and now it's 2020 still, no indication of if this is supported or not.
I didn't get an answer even through support channel which means there is a big disconnect between product team and support team.
Keeping users/customers not knowing a feature release date for 3 years is poor product management.
Ali Rashid commented
Hello @Amber Smith & @Nasos Kladakis ,
Just created support ticket 120032922000303.
Please can we have an update on this? Development apparently started 3 years ago in 2017...