Finalize Azure Front Door/WAF
Employer not named by the sourceRemote
Frontier is not the employer and does not collect applications.
About this role
Web Security, Cloud Computing, C# Programming, Technical Support, Azure, Windows Server, Cloud Security, Microsoft Azure, DevOps, GoDaddy · My Azure Front Door instance and WAF policy are already provisioned and tied to a GoDaddy-hosted domain, but I want an experienced set of eyes to make sure everything is buttoned up before we go live.
Here’s where I specifically need your guidance:
• Reviewing security configurations – confirm the WAF rules, custom policies, and TLS settings are solid and aligned with best practices. • Configuring routing rules – validate path-based routing, caching, health probes, and any necessary header rewrites. • Finalizing domain integration – double-check CNAME/ALIAS records on GoDaddy, verify SSL certificate bindings, and ensure no DNS propagation surprises remain. • Code-level pointers – call out any application changes I should make (for example, handling X-Forwarded-For headers or redirect logic) so the app behaves correctly behind Front Door.
Access & collaboration I prefer to screen-share on a Zoom call so you can walk through the Azure Portal with me, explain adjustments, and let me implement them in real time. No direct credentials will be handed out.
Deliverables 1. A live session (or two, if needed) where we complete the review and fixes. 2. A concise post-call c