707 votesSteve Ferguson supported this idea ·
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.
/ParakhSteve Ferguson commented
@Nasos, I opened a support ticket (119111924003237) and spoke to Travis Oelschlager on 11/20. He seemed unaware that there was an option to make it happen outside of self-service offerings, and I referenced this post in my ticket. Can you please put me in touch with the right person?
The only information I received as a result of my ticket was a link to the FAQ. https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-faqs?tabs=applications#can-i-use-my-own-urls-on-my-sign-up-and-sign-in-pages-that-are-served-by-azure-ad-b2c-for-instance-can-i-change-the-url-from-contosob2clogincom-to-logincontosocom
Please advise. Thank you.Steve Ferguson commented
You seem to be missing the point here. The problem is not (entirely) that the domain was Microsoft-branded, it's that the domain is not using *our* corporate domains. As something that is going to be the front door to our online presence, this is frequently the first thing the end-users see. And when they see 'b2clogin.com' anyone paying any attention at all is going to wonder what's going on. As someone currently in the process of evaluating B2C for our cloud presence, I need to know if this feature is available *today* via any means, even if that involves making a direct support request. Either it is, and I can proceed, or it is not, and I have to look elsewhere for an identity provider.