Microsoft Dynamics 365 | Integration, Dataverse...

Failed to connect to Dataverse ExternalTokenManagement Authentication Requested Azure Data Factory

(2) Share

Report

Posted on by CU16111415-0

I am having below error when connecting to dataverse in he ADF. I have enabled the MFA for this user and yet still got this issue. I am using the Office365 Authentication type. Any kind of help will be appreciated.

Failed to connect to Dataverse
ExternalTokenManagement Authentication Requested but not configured correctly. 003
AADSTS50076: Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access '00000007-0000-0000-c000-000000000000'. Trace ID: 2a845c3d-3c24-4958-a9fd-cd00600 Correlation ID: c07f2122-5ba1-4988-b252-1b68a7b6da0c Timestamp: 2024-11-16 14:05:32Z

Categories:

Power Platform integration

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

Amit Katariya007 10,409 Super User 2025 Season 2 on at

Like (3)

Report

Failed to connect to Dataverse ExternalTokenManagement Authentication Requested Azure Data Factory

Using a Service Principal To effectively address this issue and ensure secure authentication, it's recommended to switch to using a Service Principal. A Service Principal is a non-interactive user account in Azure AD that can be granted specific permissions to access resources.

Was this reply helpful? Yes No
Suggested answer

Abhishek Dhoriya 1,013 on at

Like (0)

Report
Failed to connect to Dataverse ExternalTokenManagement Authentication Requested Azure Data Factory

It sounds like you're encountering an issue with Multi-Factor Authentication (MFA) when trying to connect to Dataverse in Azure Data Factory (ADF). This error typically occurs when MFA is required but not properly configured for the authentication method you're using. Here are some steps to help you resolve this issue:

From your company

Switch to Using a Service Principal or Managed Identity:

Since MFA is enabled, the previous method of authentication using just a username and password is no longer sufficient. You need to switch to using a service principal or a managed identity for authentication, which supports MFA.

Create a Managed Identity:

In the Azure portal, go to the Azure Data Factory’s Identity section.

Enable a System-assigned managed identity or create a User-assigned managed identity.

Grant Permissions to the Managed Identity:

Assign the necessary permissions to the managed identity in Dynamics 365. This typically involves Azure AD roles and Dynamics 365 security roles.

Update the ADF Linked Service:

Navigate to the ADF instance and go to the Linked services section.

Find the linked service that connects to Dynamics 365 and update it to use the managed identity for authentication[1].

From the Web

Check Security Defaults and Conditional Access Policies:

Ensure that security defaults are turned on, which enforces MFA.

Check for any Conditional Access Policies that enforce MFA on your account[2].

Re-authenticate the Linked Service:

You may need to re-authenticate the linked service with Dynamics/Dataverse. This involves updating the authentication method to support MFA[1].

Use the Microsoft Authenticator App:

It is recommended to switch to using the Microsoft Authenticator app for MFA. This can be set up in your profile settings[3].

By following these steps, you should be able to resolve the MFA-related authentication issue and successfully connect to Dataverse in ADF. If you need further assistance, feel free to ask[2][5]

References

[1] ADF lost access to Dynamics CRM / Dataverse after MFA was turned on

[2] How to fix the error "AADSTS50076: Due to a configuration change made ...

[3] Identity Access Management Support

[4] Dynamics Community Forum Thread Details - Dynamics 365 Community

[5] new ServiceClient => "Failed to Connect to Dataverse" error after 20 ...

Was this reply helpful? Yes No