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.
Heiko Luxenhofer commented
Youssef oleik commented
Any update on this?
Gregor Soll commented
It's now 2 Jears later that you have started. So what's going on. When is it finshed?
Tim S. commented
This feature could also solve the issue, that Safari 12 and the ITP 2.0 setting make the Azure AD B2C unusable for this browser. This affects desktop as well as mobile user. The issue is described here in detail: https://github.com/AzureAD/microsoft-authentication-library-for-js/wiki/Known-issue-on-Safari
The issue can be solved with the help of a custom domain like auth0 does: https://auth0.com/docs/api-auth/token-renewal-in-safari
Tim Getsch commented
We have Azure AD B2C sign in support completely implemented, but we are waiting to push it live until we get custom domains. When will this be available? We do not want to use the your-tenant-name.b2clogin.com option because this causes browsers that have saved passwords to not recognize the passwords as belonging to the same domain. We don't want to force a bunch of customers through the forgot password scenario just because *.b2clogin.com is different from our domain.
Ricky D commented
Previous comment from Azure AD Team says :
"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."
How do we register as a tenant that "needs it"? :)
Dipesh A commented
Any updates on eta or how to apply for this?
admin rg commented
Hi AD Team
According to the statement made, fully costimizable domains can be made available for those "who need it". How can a customer apply for this?
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.