Announcements
35
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.
to be exact click on number 5:
you get that note :
and then here that pretty much tells you not to:
So has anyone managed to put azure front door or anything else infront of a portal?
On the same topic...although i am also stuck on the same point with custom domain names etc...on a step further down in order to make the portal accept traffic only from your custom front door you need to use restrict ips. How ever it is stated not to hardcode the ip ranges of azure front door (which are far too many) because they are changing..so what is the other way?
Its not required to delete SSL certificate, although its not going to be used as such. For step 2a, i will get it updated to mention that OOB CDN/WAF should be turned off and also will add it to the top of the document.
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.
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.
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)
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.
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
#1
Lucas001
60
Super User 2025 Season 1
#2
Fubar
55
Super User 2025 Season 1
#3
surya narayanan
35
Share
Report
All responses (
Answers (
