18
When creating a new environment only a few regions can be selected. The West Europe and North Europe regions are not available. If you choose Europe - Default the environment might be provisioned in either West Europe or North Europe. Not knowing which Azure region is used is a problem when you want to export data to the Data Lake. The storage account must be in the same region as the CDS environment. If you have all Azure resources and other D365 environments in another region the data must be transferred between regions for integrations which is slower than having everything in the same region.
There the regions for the D365 HR deployment must be aligned with the Azure regions.
Category: General
STATUS DETAILS
Needs Votes

Comments

T

Any update on this item?

Category: General

T

Likewise, if we wanted to use the Export to Data Lake feature, the only Azure region is chosen for us, and if that is not the region where your data analytics resources are located then that is a small problem.

EG when creating a Dynamics instance, I can choose "Australia", but there are two main Azure regions in Australia, and it's seemingly random which DC the Dynamics instance is located. If we usually have all our data analytics in Australia East region, but Dynamics gets created in Australia SouthEast region, then there is no way to change that (apparently) and this is a problem.

The best solution I can think of is keep creating new Dynamics instances until one randomly gets created in the correct region, then deleted all the others I created and migrate all the data and URL to that new instance. What a pain. See issue TrackingID#2011100030000395

Category: General

T

For integration with F&O/CE the same region is also required.

Category: General