Could not fetch access token for Managed Service Principal During DevOps Implementation

0
votes

I have tried to deploy an Azure Data Factory ARM template into an instance using DevOps.

To deploy there are three steps.

  1. Stop the trigger with pre deployment scripts provided by microsoft.
  2. ARM template deployment
  3. Post deployment scripts by microsoft to refresh resources and restart trigger.

pre and post deployment script available from below microsoft link. https://docs.microsoft.com/en-us/azure/data-factory/continuous-integration-deployment

enter image description here

But while running the task I am getting below error. enter image description here

I did a debug and find out that might be the issue with service connection in the DevOps project settings.

The above issue was because of service connection from devops project. It was resolved when I create a new service connection.

1
azureazure-devopsazure-pipelinesazure-data-factoryazure-data-factory-2
Are you running the job on a self-hosted agent? As far as I know, the Managed Identity option only works if it is your own agent with Managed Identity configured on it. – juunas
Selected agent from Azure Pipeline, Think it is Microsoft hosted one. – Antony
" But while running the task I am getting below error." What's the first error task in your pipeline? Looks like a powershell task which you mentioned Stop the trigger with pre deployment scripts. Are you using your own script to handle this. Are you able to deploy an Azure Data Factory ARM template locally instead through Azure DevOps. – PatrickLu-MSFT
First task is to stop the trigger with pre deployment scripts provided by data factory. I am able to do a custom deployment through azure portal – Antony
Hi @Antony Sorry for not make it more clearly. We could not create test pipeline with this "Azure Data Factory ARM template" by default either through Classic UI or YAML. Could you share the screenshot of your related task setting or YAML code. ? – PatrickLu-MSFT

1 Answers

1
votes

The above issue was because of service connection from devops project when I try to create a connection to the ADF instance using Managed Identity as Authentication method. It was resolved when I create a new service connection with Authentication method as Service Principal.