I am migrating a data disk from Subscription A to Subscription B. The availability zone is not retained after it was migrated to Subscription B. Is it possible to configure it that the availability zone will not change. This is the problem I encountered: They are on the same region and both subscription is set in zone 1. The data disk migrated from Subscription A to Subscription B will automatically set to zone 2. I want to retained it into zone 1 after migrating it to Subscription B

Hi, It is possible that "Zone 1" in Subscription A maps to "Zone 2" in Subscription B. If that is the case, and I suspect it is, the disk is in fact staying in the same availability zone. Have you verified availability zone mapping between the two subscriptions? I can give you instructions if needed. -TP

Can the availability zone of a datadisk from backup be retained after it was migrated to a different subscription

Accepted answer

TP 75,541 Reputation points

2023-05-19T09:32:20.78+00:00

Hi,

It is possible that "Zone 1" in Subscription A maps to "Zone 2" in Subscription B. If that is the case, and I suspect it is, the disk is in fact staying in the same availability zone. Have you verified availability zone mapping between the two subscriptions? I can give you instructions if needed.

-TP
Please sign in to rate this answer.
Lester Soria 20 Reputation points

2023-05-22T05:38:17.0066667+00:00

Hello,

Thank you for the response.

If that is the case is there a way to check if that they are mapped? It would be a great help if you can give instructions regarding zone mapping and how its configured.

TP 75,541 Reputation points

2023-05-22T05:59:24.0666667+00:00

Yes, I will give you instructions for viewing the zone mapping. In meantime, please open Azure portal with subscription A set as your current, next open cloud shell, and enter below command:

az feature register -n AvailabilityZonePeering --namespace Microsoft.Resources

It usually takes about 15 minutes or so for the feature to be registered. The command will finish quickly, but it takes time for Azure to register it in the background. You will need the feature to be registered in order to check mapping when I post instructions. There is no charge for registering the feature nor for using it to view mapping.

Thanks.

Lester Soria 20 Reputation points

2023-05-22T06:21:42.99+00:00

Already registered the Microsoft.Resources

TP 75,541 Reputation points

2023-05-22T06:27:47.1066667+00:00

Please use command below to check if AvailabilityZonePeering is registered:

az feature show -n AvailabilityZonePeering --namespace Microsoft.Resources

In output, it needs to say "state": "Registered". If it still says "Registering" then it isn't finished yet.

Lester Soria 20 Reputation points

2023-05-22T06:40:28.05+00:00

It now says registered

TP 75,541 Reputation points

2023-05-22T07:16:21.92+00:00

Okay, sign in to Azure portal with subscription A as current (if you aren't already), open a new tab, and browse to below page:

https://learn.microsoft.com/en-us/rest/api/resources/subscriptions/check-zone-peers?tabs=HTTP#code-try-0

It should open with split windows. On right side it should prompt you for your account, and then Directory. After several seconds it should show you boxes with parameters. In the Body box, paste in content similar to below:

{ "location": "westus", "subscriptionIds": [ "subscriptions/11111111-1111-1111-1111-111111111111" ] }

In place of westus substitute Azure region code you want to check, and in place of 11111111-1111-1111-1111-111111111111 substitute the subscription id for your subscription B. Once you have that scroll down a bit and click blue Run button. It only takes a second and you should see Response code 200 with Headers and Body appear below. The Body box will contain the Logical Availability Zone mapping for your two subscriptions.

For example, in sample output below, Subscription A would be 00000000-0000-0000-0000-00000000000000 while Subscription B would be 11111111-1111-1111-1111-111111111111. Based on sample output we know that for region westus:

Subscription A Zone 1 = Subscription B Zone 3

Subscription A Zone 2 = Subscription B Zone 2

Subscription A Zone 3 = Subscription B Zone 1

{ "subscriptionId": "00000000-0000-0000-0000-00000000000000", "location": westus, "availabilityZonePeers": [ { "availabilityZone": "1", "peers": [ { "subscriptionId": "11111111-1111-1111-1111-111111111111", "availabilityZone": "3" } ] }, { "availabilityZone": "2", "peers": [ { "subscriptionId": "11111111-1111-1111-1111-111111111111", "availabilityZone": "2" } ] }, { "availabilityZone": "3", "peers": [ { "subscriptionId": "11111111-1111-1111-1111-111111111111", "availabilityZone": "1" } ] } ] }

Please let me know if you have any questions.

Thanks.

Soria, Lester 0 Reputation points

2023-05-23T07:02:45.5933333+00:00

Hello Good day,

I ran the json file code that you provided and the result is this:

subscription A zone 1 = subscription B zone 2

subscription A zone 2 = subscription B zone 3

subscription A zone 3 = subscription B zone 1

{ "subscriptionId": "0000000000000000000000", "location": "japaneast", "availabilityZonePeers": [ { "availabilityZone": "1", "peers": [ { "subscriptionId": "11111111111111111111", "availabilityZone": "2" } ] }, { "availabilityZone": "2", "peers": [ { "subscriptionId": "111111111111111111111111", "availabilityZone": "3" } ] }, { "availabilityZone": "3", "peers": [ { "subscriptionId": "1111111111111111111111", "availabilityZone": "1" } ] } ] }

Is there a way to map the zones in this order.

subscription A zone 1 = subscription B zone 1

subscription A zone 2 = subscription B zone 2

subscription A zone 3 = subscription B zone 3

TP 75,541 Reputation points

2023-05-23T07:21:15.55+00:00

Hi, unfortunately there is no way to change the mapping between subscriptions. When you need certain resources to be in the same availability zone across subscriptions you need to place them based on the mapping you were given.

For example, in your case if you need 2 VMs (each in different subscription) to be in same Availability Zone, then you need to create/move them to same matching zone. So if one VM in Subscription A is in Zone 1 then you need to place the Subscription B VM in Zone 2, that way they are in same physical zone.

Soria, Lester 0 Reputation points

2023-05-29T00:42:24.48+00:00

Thank you so much. This is very helpful.
Sign in to comment

Can the availability zone of a datadisk from backup be retained after it was migrated to a different subscription

0 additional answers