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.
Michael Keymolen commented
If i go to Microsoft conference and i follow talks about Azure AD B2C, the speakers all show subway.com as a their demo. Subway is using azure ad b2c with their custom domain (id.subway.com) so it is definitely possible. please provide us with information how to achive this. Custom DNS is critical for a decent identity provider. It's a shame this is still not being implemented!
Fully customizable domains (e.g. any_subdomain. any_domain.com) are not widely available. It is goal to eventually provide this flexibility for all tenants who need it.
However, developers can now use "your-tenant-name".b2clogin.com" for all end user redirects to Azure AD B2C so as to eliminate all references to Microsoft from your redirect URL.
For example, if your b2c tenant name today is your-tenant-name.onmicrosoft.com with GUID; aZZZZZZZ-YYYY-HHHH-GGGG-abcdef569123
The new recommended URL for your B2C tenant is:
For more details:
Nick De Frangh commented
How is this still not being worked on? Can we get an ETA Microsoft?
Sean Leonard commented
Any updates here? Last response indicates "a few months" and that was in 2017
Clint Mann commented
Product appears to be abandoned. Might as well choose another provider like Auth0.
Please provide an update. We're coming up on 2 years since your last update, which indicated the functionality would be available in "a few more months"...
Rami Karhu commented
Any updates on this? It's a long hoped for feature. And a pretty basic one, too. Having to send users to register and login via microsoftonline.com not only looks shady, but also breaks the conversion paths in our analytics.
Same, it is so strange that they have not implemented this yet.
The microsoft domain is deemed unacceptable for us because it does not build trust with the user. I am looking at options to display the login form as a popup. Looks like the MSAL js library provides a way to show a new popup window but no modal popup. If a modal popup can be used then I think it would make a workaround for the trust issue.
Any update on this?
Still no update from the Azure AD Team. It's been a year and a half.
Chuck Whitson commented
What is the current status of this?
David Starling commented
Any ETA? Been over a year since Microsoft's last status update
Would need to configure our own company domain too, this is a must have feature.
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?