I run a WordPress site that must sit comfortably behind Azure Front Door while using our custom domain on every internal link. At the moment WP Engine insists on making the custom domain “Primary,” which collides with Azure’s own resolution and throws the site into an endless redirect loop. Here’s what I need from you: • Analyse the current WP Engine setup, pinpoint exactly why the loop occurs, and outline a clean, conflict-free way to keep Azure Front Door in place while preserving the custom domain. • If WP Engine simply can’t accommodate that architecture, recommend a host that can—balancing performance, security and scalability—and map out the migration plan. • Should we choose to move, carry out the end-to-end migration: staging environment, database and file transfer, domain cut-over, HTTPS, and post-launch testing. • Optimise the resulting CDN configuration so that page rules, caching headers and SSL settings work seamlessly. • Document the final setup clearly so anyone on our side can reference it. We lack in-house WordPress expertise, so I’m looking to build an ongoing relationship with someone who can own our WP stack after this project—handling future content changes, optimisations, plugin vetting and troubleshooting. If you’ve solved similar Azure Front Door or CDN issues before and feel confident orchestrating a painless host migration, let’s talk.