How to: create a Dataverse environment in a specific Azure Region

In my previous post we've seen how to detect the actual Azure Region where a specific Dataverse instance is physically located, and we briefly explained the difference between Dataverse location and Azure region. This knowledge is useful in at least 2 scenarios: When you need to create an Azure Synapse / Fabric link from your Dataverse environment When you want to deploy and configure Microsoft Connected Field Service solution integrated with IoT hub ⚠️ If your environment location doesn't matches the azure region of the external services you want to connect with, the only possible solution is to ask Microsoft to move your environment via service request. Please note: I'm not talking about Geo-to-geo migrations. Geo-to-geo migrations means to move an environment between locations. In this scenario we need to move an existing environment between regions belonging to the same location: for instance, from northeurope to westeurope.

Mar 27, 2025 - 18:45

How to: create a Dataverse environment in a specific Azure Region

In my previous post we've seen how to detect the actual Azure Region where a specific Dataverse instance is physically located, and we briefly explained the difference between Dataverse location and Azure region.

This knowledge is useful in at least 2 scenarios:

When you need to create an Azure Synapse / Fabric link from your Dataverse environment
When you want to deploy and configure Microsoft Connected Field Service solution integrated with IoT hub

⚠️ If your environment location doesn't matches the azure region of the external services you want to connect with, the only possible solution is to ask Microsoft to move your environment via service request.

Please note: I'm not talking about Geo-to-geo migrations. Geo-to-geo migrations means to move an environment between locations. In this scenario we need to move an existing environment between regions belonging to the same location: for instance, from northeurope to westeurope.