We encountered a blocking issue today when trying to upsert Dynamics 365 (CE) Online records from an on-premises enterprise database through Azure Data Factory (ADF). When running the ADF pipeline, we were presented with these not-so-helpful error details:
ErrorCode=DynamicsFailedToConnect,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Failed to connect to Dynamics: Unable to Login to Dynamics CRM: Unable to connect to CRM: Method not found: 'System.Threading.Tasks.Task`1<Microsoft.IdentityModel.Clients.ActiveDirectory.AuthenticationParameters>
Microsoft.IdentityModel.Clients.ActiveDirectory.AuthenticationParameters.CreateFromResourceUrlAsync(System.Uri)'. ExternalTokenManagement Authentication Requested but not configured correctly. 003 => Method not found: 'System.Threading.Tasks.Task`1<Microsoft.IdentityModel.Clients.ActiveDirectory.AuthenticationParameters>
Microsoft.IdentityModel.Clients.ActiveDirectory.AuthenticationParameters.CreateFromResourceUrlAsync(System.Uri)'.Unable to Login to Dynamics CRM Unable to Login to Dynamics CRM,Source=Microsoft.DataTransfer.ClientLibrary.DynamicsPlugin,''Type=System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=9.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]],Message=The creator of this fault did not specify a Reason.,Source=Microsoft.DataTransfer.ClientLibrary.DynamicsPlugin,'
In ADF, the "Test connection" was successful for the Linked Services: the on-prem database and Dynamics 365. We reduced the mapping from the on-prem database to D365 to only two columns, the primary key and one other string column, but the same error appeared.
Pressed for time, we didn't open a support case with Microsoft. Instead, we first copied the on-prem data to Azure SQL with ADF and then created a pipeline to copy the data to D365.
The only explanation we could find online was in the following forum posts, where a Microsoft employee said that the integration runtime's locations might not be supported. However, ours are set up within the United States, so that doesn't sound right, but it could be related. In any case, this was frustrating. Here's hoping that Microsoft updates ADF to support this direct on-prem to D365 scenario.
Comments