Azure Geography Vs Region Vs Location impact on Azure VMs

Question

Azure Geography Vs Region Vs Location impact on Azure VMs

Shridhar Srinivasan 220

As per this, Azure Regions Page we have EastUS and EastUS2 in same Location i.e. Virginia.

I have Virtual Network named VNet1 in EastUS Virginia. I create a Virtual Machine named VM1 in EastUS2 Virginia.

Can I associate the VM1 to VNet1 ?

Accepted answer

1 additional answer

Your answer

Answer 1

KapilAnanth-MSFT 49,616 Microsoft Employee Moderator

@Shridhar Srinivasan

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

I understand that you would like to know if you could attach VM from EastUS2 to a VNet in EastUS1

I am afraid that is not the case. EastUS2 VM cannot be linked to EastUS VM or any other region except EastUS2

Only regional resources can be associated to each other.

The "unit" used in Azure is "region", not locations (wrt Azure Regions Page)

While some documents may use the terms "location" and "region" interchangeably, it's just contextual and it refers to the list of regions only.

You can get the list of available regions using the command :

https://learn.microsoft.com/en-us/cli/azure/account?view=azure-cli-latest#az-account-list-locations
az account list-locations -o table

Thanks,

Kapil

Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.

Shridhar Srinivasan 220 Reputation points

2023-07-27T11:06:44.22+00:00

TI understand the rationale. But, it may be better to stick to one term to avoid such confusion.

For eg. check below statement under this Section

<<<<<

Each NIC attached to a VM must exist in the same location and subscription as the VM. Each NIC must be connected to a VNet that exists in the same Azure location and subscription as the NIC.

Please share your thoughts.
KapilAnanth-MSFT 49,616 Reputation points Microsoft Employee Moderator

2023-07-27T11:21:14.2266667+00:00
@Srinivasan, Shridhar (Shridhar)

I do understand acknowledge that the documents are using the terms location and region interchangeably.

But you must note that "Virginia" is not a location - as far as an Azure resource is considered. (as long as we are speaking technically for resource management purposes).

The available list of regions/locations is as follows:

Open Azure CLI and run

az account list-locations -o table

If we run this command, we can see "Virginia" is not a part of it.

We should only consider the listing here as regions/locations.

Cheers,

Kapil.
Shridhar Srinivasan 220 Reputation points

2023-07-27T11:50:38.7633333+00:00

Thanks for patiently explaining the differences.
KapilAnanth-MSFT 49,616 Reputation points Microsoft Employee Moderator

2023-07-27T11:52:35.72+00:00

@Srinivasan, Shridhar (Shridhar)

You are most welcome

Thanks for your continued contribution on Q&A and appreciate much for taking the time to share your feedback.

Cheers,

Kapil

Answer 2

Pranathi Panyam_MSFT 1,066 Microsoft Employee

Welcome to Microsoft Q&A, thank you for posting your here!!

we cannot associate resources with different regions. To create a VM, all its resources should be within same region (Either East US or East US2).

Hope this answer helps.

Please "Accept as Answer" if it helped so it can help others in community looking for help on similar topics.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Share via

Azure Geography Vs Region Vs Location impact on Azure VMs

1 additional answer

Your answer