This message was deleted.

So looks like automation is the way to go to build a new deployment...

I use Azure Traffic Manager to replace GSLB. Used it to bridge between on-prem and Azure NetScalers

By the time you've dealt with the upstream network config, DNS and NSG's etc... shipping a VHD into Azure is probably low priority in the grand scheme of things. I don't think it's a supported workload for ASR, but you could sync it into Azure using some other tools (albeit a dirty approach!). I'd look at an automation route personally but that's going to be lead by your RTO. Without GSLB and a "hot" DR appliance you'll need some manual intervention anyway so it's really a question of to what degree you automate it.

Got it... thanks, lads. Great feedback... I am running Azure Traffic Manager for a customer on on standard licensing... never considered a hybrid setup, cheers

We used it because we wanted the transition for the users to be seamless and were going from hardware on-prem to VPX in Azure. So we had concern around load. ATM allowed us to move over slowly and move back if needed

Cool... this is not a particularly large deployment so scale/load is not a concern...

One thing to bear in mind is Traffic Manager can only view your on-prem (presumably primary) DC from the outside, so you can only automatically failover based on gateway availability - which may be fine depending on setup! Usually with GSLB I'll have monitors validating critical services to ensure users are logging in to a healthy site, so capabilities wise, not entirely a replacement but better than nothing definitely

Thanks, Andy. In this scenario I just need to be able to manually 'flip a switch' should there be a total primary outage so Traffic Manager should do the job 🙂

Gotcha, big red button! 🙂