There the regions for the D365 HR deployment must be aligned with the Azure regions.
Comments
Hello,
4 Years later, there is still the same issue.
Regions are missing when creating environments on power platform.
If you are lucky the environment will be created in the region you want, otherwise you have to create and delete environments in the chain to hope to have the desired region.
How many vote an idea need to be considered ? While this issue impacts everyone with multiple Azure datacenters but less choice in PowerPlatform.
Category: General
Any update on this item?
Category: General
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
For integration with F&O/CE the same region is also required.
Category: General
Administrator on 3/26/2024 6:49:12 PM
Thank you for your suggestion. We’re considering this functionality for a future release. This posting is provided “as is” with no warranties, and confers no rights.