Jun 23 2020 01:17 AM
Jun 23 2020 01:17 AM
Will it be possible to setup custom domains for B2C or even B2B in products Microsoft owns such as Azure Front Door? Functionality we have seen in other B2C configurations:
I have already tried to configure Front Door, but run into some challenges with B2C. Would love to also have the possibility to setup TLS 1.3 ("2.0”); the front door to the safe azure harbor. Similar functionality we have shown with VPN and other products, where we route quickly to the nearest region and utilize the azure network backbone routing traffic internally to different azure clouds and regions.
I assume we will also soon in Azure be able to set the default TLS version higher than 1.2; just as other cloud provider chooses to set the default version to 1.3.
BTW: a lot of excellent stuff your identity team delivers; love that you bring in more of the B2C functionality into the main tenant ( external identities in B2B)...
Jun 23 2020 09:10 AM
@Kjetil Smith Azure AD B2C is a white-label solution so you should be able to create custom URLs. https://docs.microsoft.com/en-us/azure/active-directory-b2c/overview
We are looking to bring additional custom branding options to Azure AD in the future.
Jan 28 2021 02:37 AM
> Azure AD B2C is a white-label solution so you should be able to create custom URLs.
You should be able to, but you can't. From the FAQ —
From this community post, it also seems like it's been "on the roadmap" for 4 years now.
This should be a deal-breaker for most big companies — when trying to educate customers about phishing attacks and the importance of making sure they're on the correct domain before entering sensitive details, to then have to say "oh, except for b2clogin.com, that one is OK" seems frankly bizarre.
Let alone that most companies don't advertise that they're using hosted Active Directory, so there's actually no mention of Microsoft or b2clogin.com on their site.
If an end-user does browse to www.b2clogin.com to try and validate who this is 3rd party entity and are they legitimate, rather than seeing anything to provide an explanation of what b2clogin.com is, they get redirected to https://login.microsoftonline.com/common/oauth2/authorize?redirect_uri=https://www.office.com — that is, prompted by a Microsoft branded login page & if they authenticate, presented with their Microsoft Office account!
Jan 28 2021 05:28 PM
I find this so bizarre that this is not a feature. This is a deal breaker for us as we need our users looking at the sign in page knowing it is coming from our domain.
This feels like a very basic feature and I see it's been 4 years in the pipeline.
We'll probably move to Auth0 because of this.
Mar 11 2021 04:30 AM
@Jeff_Bley do you have any updates on this, yet? We are also very keen on having this feature enabled so we can offer a white labeled solution to our customers.
Currently we are getting feedback from some of our customers if the b2clogin.com is really genuine and is ours, which is great to see that some customers pay attention to the domain prior to entering their personal credentials.
Thanks in advance!
Mar 16 2021 02:29 PM
Apr 15 2021 07:46 AM
Can we use Azure feedback instead of tech community?
https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/15334317-customer-owned-... here info comes straight from microsoft.