Availability-Zone molded the design - Azure

Today my customer called and ask for the high-availability set up for the azure site and he said he wants the DR implemented too. Well i was still doing the migration from VMWare to Azure and only the initial sync was done and customer was performing the testing so that we would have the go ahead for the differential run and finally the cut-over. But suddenly due some Azure outage he got panicked and wanted us to provide HA not inside DC but HA on DC level , you right in correct he meant Availability Zone , he needed Availability Zone instead of the AV-set.

Now when we checked the availability of AV-Zone and we found it got GA recently

https://docs.microsoft.com/en-us/azure/availability-zones/az-overview

so we were like yeah that alright , we will recreate the VM's from existing disk and place them inside the AV-Zone problem solved and craft a plan for DR. But here is the kicker :




When we go through the above link just confirm we are on the right track and AV-Zone works as expected in East US but its not as per the MS Doc mentioned link above there are services which are not yet supported in East US guess what all those services were - VPN Gateway , Express Route , No paired region for DR hence the a small project become large and East US 2 got finalized because AV-Zone is pretty mature here and supports all the services.

Here is the learning ; Always check if the required services are available in particular region or not and if yes then to confirm all the Features are supported or not.

2 comments:

Azure DevOps

Azure DevOps is a suite of development tools provided by Microsoft, designed to support the entire development lifecycle of a software proje...