Check out the latest Customer Service Insights updates!Learn about the key capabilities and features of Dynamics 365 Customer Service Insights and experience some of the new features.
Download overview guide | Watch Customer Service Insights video
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We receive this message every day, but how to handle it? We do not need and use this service.
You’re receiving this email because the latest data refresh for your Dynamics 365 Customer Service Insights workspace, ***, failed for the following reason:
Something went wrong, and we can’t find this environment. (Job ID: 6a2d4908-5094-4959-83cf-f365c0b8952a)
Your workspace will refresh again tomorrow.
If an action is listed above, correct the problem in your workspace.
I have a user receiving this as well. need solution
Thanks for reaching out, this email indicates that a workspace created in Customer Service Insights (https://csi.ai.dynamics.com) is no longer able to connect and pull data from the Dynamics instance it was created from. If you return to the application and either update or delete the workspace, you should no longer receive the error message.
If you're interesting in knowing more about the product and what capabilities it offers please let us know, more details can be found in the documentation as well: docs.microsoft.com/.../overview
You can easily solve this problem by deleting the workspace and then creating it again.
Or you can try updating the workspace.
That would also solve the problem.
Business Applications communities