Error in Linked Service connected to azure sql db using Azure Key vault

Sudip Bala 20

User's image

The linked service is not working after performing CICD from dev to qa branch. All the resources are copied along with linked service. However, The linked service could not setup correctly with this error.

What does this error indicate and how to resolve this?

Marilee Turscak-MSFT 36,891 Reputation points Microsoft Employee

2024-05-09T16:40:26.5033333+00:00

@Sudip Bala Thanks for sharing the details. We are looking into this and will get back to you.

1 answer

Marilee Turscak-MSFT 36,891 Reputation points Microsoft Employee

2024-05-09T23:08:25.34+00:00
Hi @Sudip Bala ,

The error message indicates that there is no managed identity provisioned for the data factory. You can enable the managed identity via Azure CLI with this command:

az resource update --name <factoryname> --resource-group <group-name> --namespace Microsoft.DataFactory --resource-type factories --set identity.type=SystemAssigned

Let me know if this resolves the error and if you still run into any errors.
Please sign in to rate this answer.
Sudip Bala 20 Reputation points

2024-05-10T06:16:03.64+00:00

Hi @Marilee Turscak-MSFT

This issue got resolved once i edited the linked service and saved it again.

However, I am stuck with another issue related with linked service.

I have managed to push ADF from dev env to stage env. I have all the services in adf-stage on live mode. After , I make the git configuration with stage branch. The linked service is not to be seen.

In Live mode, I have 4 linked service. But in stage branch , There is only 2. The LS connected to azure sql db didn't come up.

What could be the possible reasons??
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Error in Linked Service connected to azure sql db using Azure Key vault

1 answer

Your answer