Azure always provides customers choice to select the region that best suits their needs. With the new service Azure Resource Mover, customers now have a platform level capability that allows them to move to new regions across the globe and expand their resiliency options by moving their resources into Azure Availability Zones.
In this blog, we will take a sample customer environment and share steps on moving it from a source region to a destination region into an Availability zone thereby achieving a reliability of 99.99%. From the product group, we have also been very closely engaged with customers, listening to their feature asks and feedback. We will also look at some of the feature updates that are now available as part of the recent GA launch announced in March'21.
Sample source environment: Let’s take an example of a sample application in North Central US with the following components.
Now, let's try to move these resources to a destination region (East US). Below highlights the outline of the steps:
The destination region environment would now look like below, we have added a comparison to help understand the changes better.
Azure Resource Mover is constantly being improved with customer feedback and experience in mind and we are hoping that more customers will be able to leverage the service to meet their cross region move needs. Learn more about Azure Resource Mover here, leverage the detailed tutorial to get started and watch the following video demo on moving resources into Availability Zones.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.