Why Azure Front Door is required while using third party WAF for custom domain in Azure AD B2C

Viewed 28

I was trying to implement custom domains for Azure AD B2C, so that when a user tries to login/register into my application,they should not be displayed with a URL .b2clogin.com instead should use my custom domain

While going through the MS Docs for this requirement, (Refer here) they recommend to use Azure Front Door, but they also allow to use third party WAF such as Akamai.(Refer here)

Can use Third Party WAF

and Here the documentation (Refer here) says that Azure Front Door is required even if we bring in a third party WAF. Azure Front Door as a Component

The question is why here Azure Front Door is required ? Is there anything special Azure AD B2C Requires?

1 Answers

AFD and AAD B2C services are doing some behind the scenes things to make it work. One of those things is adjusting how cookies are set. Hence it is required.

Related