This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 39%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
hello there,
I just wanted to confirm something, after adding a custom domain to AD for a B2C tenant authentication page can we use a custom domain name directly like "login.example.com" to land on exact B2C login page?
I have followed below URL:
https://learn.microsoft.com/en-us/azure/active-directory-b2c/custom-domain?pivots=b2c-custom-policy
but it does not specify that I can use directly domain name to land on the B2C authentication page. Instead, I always needed some parameter in the URL after the domain name to land on the login page.
Any thoughts?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 1%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
Hi BM, I hope I can help you with this question.
Can you show the section in the linked documentation where you assume more parameters need to be specified?
To my knowledge, there should be no problem with you using a URL such as "login.customerDomain.com".
...During DNS resolution, a canonical name (CNAME) record with a custom domain name (eg. login.customDomain.com) points to your Front Door default front-end host (for example,
contoso-frontend.azurefd.net)....
If the reply was helpful, please don’t forget to upvote or accept it as an answer, thank you.
Sorry, ignore the message, wrong thread
thanks @Patchfox for your reply. yes I followed the same and from the B2C tenant in the users flow I clicked on run flow then got the url "https://login.domain.com/defaultdomain.onmicrosoft.com/oauth2/v2.0/"
it only works when i manually change = login.domain.com to custom domain name not directly when I search for my custom domain name in browser.
Ok, if I understand it correctly, you can't call the login page with the custom domain?
You only want to enter login.domain.com and then get a redirect to the oauth2 URL, right?
How did you set the CNAME record?
same way mentioned in documentation
You only want to enter login.domain.com and then get a redirect to the oauth2 URL, right? -- YES
Ok, but the Azure B2C tenant doesn't know anything about your custom domain. So you have to implement the redirection to the oauth endpoint by yourself.
You can try this as an alternative: https://login.customDomain.com/<tenant ID GUID>/
nope, still need whole URL to land on login page.
Sorry I meant to write in my previous message that the parameters in the URL are still needed because the custom domain acts instead of the Microsoft domain of the endpoint URL.
No matter if with TenantName or TenantID in the URL.
Another redirection without parameters is not provided and would have to be developed by yourself. E.g. login.customDomain.com --> Redirect to -> https://login.Custom domain.com/defaultdomain.onmicrosoft.com/oauth2/v2.0/
May we know why you don't want the parameters in the URL, to begin with?
The goal of custom domains is to allow the user to continue logging in with the same custom URL.
Sorry I meant to write in my previous message that the parameters in the URL are still needed because the custom domain acts instead of the Microsoft domain of the endpoint URL.
No matter if with TenantName or TenantID in the URL.
Another redirection without parameters is not provided and would have to be developed by yourself. E.g. login.customDomain.com --> Redirect to -> https://login.Custom domain.com/defaultdomain.onmicrosoft.com/oauth2/v2.0/
May we know why you don't want the parameters in the URL, to begin with?
The goal of custom domains is to allow the user to continue logging in with the same custom URL.
Edit: the only solution I can think of here is to do a URL rewrite (as a kind of fallback) already at AFD.
That everything that is requested via login.customDomain.com is redirected to the URL with endpoint parameters.
If the reply was helpful, please don’t forget to upvote or accept it as an answer, thank you.
Hi @Patchfox sorry for the delay, in URL rewrite option there is not block to add query parameters which is required with the URL, so for me URL redirect option worked however it is not showing custom domain in the browser URL.
also there is login behavior issue. so in my web page there is sign in button by which I am redirecting to B2C login page and after login I directly land on dashboard of that app, but when using front door custom domain name which I have added, after login in B2C authentication I land on that web app sign in page only and when I click on sign in button then only I can land on dashboard.