Share
Report
142Hi,
We have a client with a Dynamics 365 environment in the United Kingdom region. Twice within the past year, the environment has experienced an unexplained re-import of an existing unmanaged solution in Production that the client frequently deploys via an Azure DevOps pipeline. The pipeline has no history of running on the dates that this occurred though. Strangely, an export of the solution occurred shortly after the first time this occurred. MS support has no telemetry logs of the unexplained imports (although the logs show every explainable import!) and they are not able to assist with identifying the cause nor how to prevent this from occurring again (we've opened multiple MS support tickets). One thing I noticed is that there is no 'activityid' tied to the 2 unexplained imports. From research, it appears that sometimes when MS imports their solutions, they also have no activityid.
The client has Dynamics orgs that reside in other regions of the world which have not experienced this issue. It's unclear what has caused the 2 imports and how to prevent them, other than blocking all unmanaged customizations via the settings. This setting will need to be temporarily disabled each month to allow the client to deploy the latest version though. Our team moved away from using managed solutions for various reasons.
Has anyone else seen this or know how we can capture information on who/what triggered these imports? Thanks for any insights.
Categories:
All responses (
Answers (
