I am facing domain resolving issue in Sitecore Multi-Site Solution using Azure PaaS with Azure WAF setup, however, it's working fine if I add the custom domain on Content delivery(Web Apps) level.
We have to set up the multi-site solution, which needs to configure on Azure WAF level. The request is coming on WAF first then, CD (web apps) then the web.config( where the domain is resolving)
We have setup multi-domain on Azure WAF using this Microsoft blog: https://docs.microsoft.com/en-us/azure/application-gateway/create-multiple-sites-portal
But the problem is – custom domain is not passing from Azure WAF to CD server(web apps) that’s the reason it’s not resolving the multi-site domain.
Below is the configuration we did on WAF level:
Configuring multi-site for Sitecore on Azure WAF Steps involved and pre-requisites
- Azure VNet setup
- Azure WAF setup
- Domain level changes
- WAF - configuring multi-site
Azure VNet setup:
Azure VNet is required to privately deploy WAF and publicize with public FQDN or IP. Azure VNet can be safeguarded using azure DDoS, this will protect from any public or private vulnerabilities.
Once the VNet is ready, the Azure application gateway can be launched in WAF mode (WAF/WAF2) to protect the Sitecore environment. Below are the elements of WAF to be created while consuming multi-site functionality at WAF.
- Backend pool
- HTTP Settings
- Front End IP configurations
- Health Probes
Domain level changes
All the origin websites (domains/sub-domains) must be configured with the CNames pointing to Azure WAF FQDN.
WAF Multi-site configuration
Once the required domains are mapped with the Azure WAF FQDN, multiple sets of above-mentioned WAF elements should be created pointing to the respective website.
It would be great if someone can help on this.