Personalized Community is here!
Quickly customize your community to find the content you seek.
For the 2020 wave 2 release, Dynamics 365 Customer Insights introduced two new capabilities:
* Audience insights (Generally Available)
* Engagement insights (available to public preview as of 10/30/20)
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
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.
Thanks Bill, I will connect with the team and come back to you.
Lets see this into two parts - region affinity between CI and Dataverse, and gateways availability.
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.
Customer Insights team.
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?
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)
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.
Business Applications communities