Unanswered

Power Pages with Azure Front Door

(1) Share

Report

Posted on by andypwc

Hi All,

Wondering if anyone has ever succesfully followed this?
https://learn.microsoft.com/en-us/power-pages/configure/azure-front-door

We are trying to enable WAF - but not the Preview toggle as it is not ready for Production.

Following that documentation we got stuck on step 2b of custom domain

We asked MS support and they said the doco is outdated and we should use the WAF toggle, but they cannot confirm if it is ready for production environment.

Thank you.

Categories:

General topics

I have the same question (0)

All responses (15)

Answers (0)

ragavanrajan 7,044 Most Valuable Professional on at

Like (0)

Report

Hi @andypwc

I will tag the Power Pages Product Managers / CAT to help you here @NikitaPolyakov @dileeps & @PriyaVR

Hope it helps.
------------

If you like this post, give it a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users to find it.

Was this reply helpful? Yes No
andypwc 37 on at

Like (0)

Report

Thanks. @NikitaPolyakov @dileeps @PriyaVR would appreciate any insights

We believe the issue is setting up cdn and customdomain on Power Pages first means there is already AFD set up.
Setting up another AFD with the same domain will throw error.

Looking for a supported way of configuring BOTH CDN + WAF on power pages while OOTB WAF is still in Preview.

Was this reply helpful? Yes No
rulesrchanged1 on at

Like (0)

Report

If u are setting up custom waf using azure front door, then I'll suggest setting up Cdn caching rules on afd as well instead of OOB Cdn. That will technically make the setup work and also would be better to reuse your own afd instance for that.

Was this reply helpful? Yes No
andypwc 37 on at

Like (0)

Report

Thanks for the prompt reply.

Yep we were thinking of that but would like confirmation from Microsoft as we don't want to deviate from OOTB capabilities for production support perspective.

Looks like that documentation is indeed outdated and not accurate.

Was this reply helpful? Yes No
rulesrchanged1 on at

Like (0)

Report

Hmm so the document you are referring to is for how to setup your own custom cdn/waf, in this case azure front door.

It's not related to OOB capabilities which are documented seperately

Was this reply helpful? Yes No
andypwc 37 on at

Like (0)

Report

Not really. You can see the section here
The instruction is to setup custom domain on power pages first.
then step 2 is to remove/update CNAME to AFD - then 2b is to setup custom domain on the own AFD.

That documentation is linked from Power Pages go-live checklist
https://learn.microsoft.com/en-us/power-pages/go-live/checklist

Was this reply helpful? Yes No
andypwc 37 on at

Like (0)

Report

Specifically this paragraph is the concern:
Web browsers reject cookies set by Power Pages when you use an Azure Front Door endpoint URL that's different from the URL of your site. Hence, you must set up a custom domain name both for your site and the Azure Front Door endpoint.

We want to make sure setting own AFD for both WAF+CDN will not break any functionalities.

Was this reply helpful? Yes No
rulesrchanged1 on at

Like (0)

Report

Ohh ok, i see the doc u mentioned is for setting up your own CDN/WAF (which is what AFD provides). It is written with an expectation that when customers bring their own, they will not be using our OOB CDN/WAF. But i see that part isn't explicitly articulated, so i will get that fixed.
So the step documentation is correct and you do need to setup custom domain on your power pages site first albeit without OOB CDN/WAF. This step is important not just for the reason for cookie, but also because without doing this step, you are essentially enabling domain fronting which alot of CDN/WAF provider blocks automatically now and AFD will start doing it very soon too (Azure Front Door - Frequently asked questions | Microsoft Learn)

Was this reply helpful? Yes No
andypwc 37 on at

Like (0)

Report

Hi Dileep, from your statement:
So the step documentation is correct and you do need to setup custom domain on your power pages site first

This is the reason I created this thread- if we setup power pages custom domain first, then when configuring our own AFD it will throw error as AFD does not allow same custom domain if it already exists on other AFD (in this case Power Pages managed AFD)

We are stuck on step 2b.

Was this reply helpful? Yes No
rulesrchanged1 on at

Like (0)

Report

Hey Andy,

Sry for not being clear on this, thats what i explained above, when u are using custom AFD, then turn off our OOB CDN/WAF. Once u turn them off there is no microsoft managed AFD setup in the backend and you will be able to set custom domain name in your own AFD.

Was this reply helpful? Yes No