azure-devopsazure-data-factory

Unable to deploy Azure Data Factory Pipelines in Azure DevOPs: Configuration issue is preventing Authentication

I am trying to execute Azure Devops Pipelines from my Azure Data Factory. I created the YAML code successfully and I believe I have created the sufficient permissions to from the App Registration from Microsoft Entra ID. However, I'm keep on getting the error message:

Exception message: A configuration issue is preventing authentication -

Original exception: AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret added to app 'c572961f-da6c-4731-85xxxxxxxxxx'. Trace ID: a4f2362f-17ad-4xxxx-be79-420e32153c00 Correlation ID: ac028d9d-7834-4b80-baa4-4e6bxxxxxx Timestamp: 2025-02-23 21:00:36Z

The full error message is

enter image description here

I checked out the Service Connections and I'm not seeing any issues: enter image description here

And my verification has succeeded

enter image description here

So can someone let me know why I'm still unable to authenticate with the service principle

Solution

  • There are some suggestions for you to resolve the issue.

    1. Create a new ARM service connection automatically with workload identity federation credential.

      enter image description here

    2. Create a new ARM service connection manually using the same app registration.

      enter image description here

    3. Edit your affected service connection.

      Try to make some changes to the "Description" field of your affected SC, then check if you can save and update it successfully.

      If there is the same issue, press F12 and open the network trace window -> Edit your SC -> Update the description -> Click on save button -> Check the failed call which is a PUT call and used to update the SC. Check whether there is "accesstoken":null property in the request body. If there is, copy the request body and remove "accesstoken":null or "accesstoken":"" from the authorization header, then use this request body to make a service connection update PATCH REST call.

    4. Contact others having permissions in your organization to create a new SC. Sometimes, you may have this error when your account has some issues.