Azure Front Door 403 errors when proxying Litmos Custom domain through Cloudflare-protected Litmos origin due to SNI/Host mismatch.
Customer attempted to place the Litmos custom domain behind Azure Front Door and a WAF for security hardening but encountered persistent 403 errors. Investigation showed that the issue was not caused by WAF rules but by Azure Front Door’s expected TLS behaviour when connecting to the Cloudflare-protected Litmos origin. Microsoft confirmed that proxying from Azure Front Door to a Cloudflare-protected origin in this way is not a supported topology, so the customer reverted DNS to point directly to Litmos. Questions this answers: Can we route our Litmos custom domain through Azure Front Door?