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.
This feature is highly desirable, would prefer to use B2C vs Auth0
In July 2017 we were told we would have to wait "for a few more months". Those months have passed and so has the year. What's happening?
Sad Customer commented
I'm disappointed that MS has not implemented this feature or provided a clear answer to when it will be implemented. Is this a true technical limitation or simply an incompetent project manager at MS?
We need this feature for a big corporation with +50 million end-consumer clients.
We would prefer Azure B2C, but this missing feature is blocking.
Otherwise, we need to consider other vendors like Auth0 or Okta.
Does this work for non-b2c domains? (in regular Azure AD)
Seamus Walsh commented
Is this feature still being considered?
Vladimir Ignatov commented
Hi, can you at least tell us what is the status and if any work is being done on this?
gilberto pavanelli commented
Singaravelu Souppourayen commented
Is there any progress on this feature? We need custom url for applications.
Coding Panda commented
Our product owner wants this for our web site. Is this on a road map yet?
It's a year after this was promised "in a few more months". Can we please have a real ETA?
We need the corresponding B2C emails (such as verification codes) to be sent form the customer owned domains as well rather than From: Microsoft on behalf of [customer name] <firstname.lastname@example.org>.
Is there any update for this? It's practically summer of 2018 now...
Any update on this? We are using B2C and user wants to see their domain instead of microsoft while signing in. Is that possible?
Yes we are thinking of using ad b2c. Any firm update? If not we will have to look elsewhere.
"We’re currently hoping to have this available by summer 2017.".
We are approaching summer 2018. Do you have any news on when we can expect this?
Building a new web service planned for release end of 2018, and not being able to use our own domain is most likely a show-stopper. Can we expect this feature to be done by then?
Thuan Soldier commented
This would be an enterprise-class feature to take fully advantages of Microsoft cloud identity platform. Is there any update?
Any update on this?
As others have said - we really need an update on this since it plays into our authentication decision. Need to know very soon what the status is!