Customer experience | Sales, Customer Insights,...

CDS Region vs CI Region

(0) Share

Report

Posted on by Bill Ryan

I am trying to setup a Gateway and know that I can't use the Default environment to facilitate that. However, I set up a new Environment, set the Region to US and was presented with the following error... We're using the Managed lake not our own, but aren't EastUS /WesUs availability zones inside of Region North Central US and West Central US? Is there a way to change these on our end, I'm not seeing an option in either CI or Power Platform admin.

Customer Insights Error Message CDS

I have the same question (0)

All responses (5)

Answers (0)

MichelleD on at

Like (0)

Report

Thanks Bill, I will connect with the team and come back to you.

Was this reply helpful? Yes No
Suggested answer

Aditya Kuppa 320 on at

Like (0)

Report
Hello Bill,

Lets see this into two parts - region affinity between CI and Dataverse, and gateways availability.

We recommend region affinity between CI and Dataverse with a 1:1 cardinality as well for various logistics reasons.

For us to leverage gateways we need Power Platform dataflows and therefore need to associate a Dataverse environment to CI.

Gateways from all US regions also should be available for consumption in all US environments - meaning, even if the gateway is from a WCUS, should be available to be consumed in a WUS Power Platform environment and the associated CI instance.

If you go to Power Platform Admin Center > Data (preview) Power Platform admin center (microsoft.com) you will find Azure region specific gateways with ability to filter per Azure region, and if you to the maker portal https://make.powerapps.com > Data > Gateways, you will find gateways from all US Azure regions. These gateways are available for all US PowerApps environments.

So our suggestion would be to associate a Dataverse environment from EastUS to CI East US instance and all gateways from all US regions should be available for your consumption in CI.

Thank you!

Aditya Kuppa

Customer Insights team.

Was this reply helpful? Yes No
Bill Ryan 8 on at

Like (0)

Report

Aditya - again as always, thank you for your help. I might be misunderstanding but I think the primary issue is that CI is refusing to accept the environment URL b/c of the regions. Agreed on the Affinity I just wasn't sure if I was able to do that. If we take Gateway out of the discussion for a second, it's the association of the DataVerse URL that keeps getting rejected. I created the new DataVerse environment, but the only option I had for region was US. It looks like that's where the conflict is. I went in CI and I know when troubleshooting yesterday it looked like there might be different options for Regions in different versions. This is what I'm getting so I can't specify West and default is East for this tenant - so CI is rejecting it. The Gateway looks to be visible from Admin, it's just that association between Dataverse and CI. Maybe it's something we need to change on backend?

Was this reply helpful? Yes No
Suggested answer

PerezAguiar Microsoft Employee on at

Like (0)

Report

Hey Bill!

You can also use Powershell to provision instances. When using New-AdminPowerAppEnvironment (Microsoft.PowerApps.Administration.PowerShell) | Microsoft Docs (new-adminPowerAppEnvironment) you can specify both parameters: LocationName (unitedstates, europe, etc) and also the datacenter (eastus, westeurope, etc)

Was this reply helpful? Yes No
Suggested answer

Bill Ryan 8 on at

Like (1)

Report

I did not know that, but this was tremendously useful (not sure How i missed it but I did). Much thanks to you and Aditya both.

Was this reply helpful? Yes No