You’re offline. This is a read only version of the page.
Hello!
As a live product that is constantly evolving, Dynamics 365 CRM and Dataverse are constantly receiving new features and functionalities. Some of these are related to integration with other products like Azure Data Lake (Connect to tables in Microsoft Dataverse - Dynamics 365 Customer Insights | Microsoft Docs), connecting to Finance and Operation environments or connecting a Dataverse with Azure Synapse (Create an Azure Synapse Link for Dataverse with Azure Data Lake - Power Apps | Microsoft Docs)
One common requirement for these integrations is that both the Dynamics 365 Environment / Dataverse environment are provisioned on the same Datacenter as the product that you're integrating with (FinOps, SCM, Azure Synapse, Azure Data Lake, etc). However, when you go to Power Platform Admin Center and you try to provision using the graphic interface, you're allowed to select the region (Europe, North America, Canada, APAC, etc) but not the specific datacenter:
How to overcome this situation? one possibility is to use Powershell. ON New-AdminPowerAppEnvironment (Microsoft.PowerApps.Administration.PowerShell) | Microsoft Docs we have a command that allows to create an environment:
New-AdminPowerAppEnvironment
One of the parameters this command accepts is related to location. If you run
Get-AdminPowerAppEnvironmentLocation
The first thing that you're going to see is that you receive the name of the location but also the datacenters that are associated with this region:
So when you're creating the environment, you have to use two parameters: -LocationName and -RegionName:
By using these 2 parameters, we can force the creation of our environments in a specific datacenter of our choice. Please remember to use lowercase when using the text on the powershell!
Additional information on these commands is located on https://docs.microsoft.com/en-us/powershell/module/microsoft.powerapps.administration.powershell/new-adminpowerappenvironment?view=pa-ps-latest and https://docs.microsoft.com/en-us/powershell/module/microsoft.powerapps.administration.powershell/get-adminpowerappenvironmentlocations?view=pa-ps-latest
Thanks Daniel for the great workaround. I'm sure the PowerShell org. provisioning with specific location will come handy to a lot of end customers!
Share
Report
All responses (
Answers (
93
