Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2023 Release Wave 1Check out the latest updates and new features of Dynamics 365 released from April 2023 through September 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I'm unable to setup Insights on a PRODUCTION instance of CRM Dynamics.
It is working correctly in the SANDBOX environment. The person who is setting this up is a O365 Global Admin and has Professional License assigned and setup correctly in my PROD instance.
I have System Customizer, System Administrator, and Insights User roles. So does my global admin. I've followed instructions in this KB Article (minus the installation of the zip file and setting the trusted IPs) to install it, but i get this error message:
The very strange part is that i have the following notification showing up in my browser:
When i click it, it takes me to the previous CRM Dynamics Administration screen.
The new Dynamics 365 dashboard doesn't let me or at least i don't see an option to install a solution. The Insights solution is installed so I'm puzzled why I can't get this setup. Can my global admin assign a basic license to themselves even if the licensing is professional / enterprise?
Here is a quick update: We managed to get it resolved! It works both in Sandbox and Production environment. However, you will have to contact Microsoft Support or submit a ticket through Azure. It is security related issue and only one instance of Insights will work in either sandbox or production but not both by default. Meaning that if you had a user who logged into the sandbox environment first, or vice versa into production, it would only know to work within that environment. They would get an error in the other.
Hopefully there is going to be a way to manage this in the future without contacting support.
Business Applications communities