Azure Synapse :- ManagedIdentityCredential authentication failed

Question

Azure Synapse :- ManagedIdentityCredential authentication failed

Prashant Rewatkar 101

Hello team,

Issue :- ManagedIdentityCredential authentication failed: No MSI found for specified ClientId/ResourceId. Status: 400 (Bad Request)

We are facing one issue with azure synapse activity.
We are trying to creates LinkedServices and datasets using azure synapse analytics API(Using Azure.Analytics.Synapse.Artifacts) from Dot Net environment(Dot net core).

We are able to create those resources from local On the server we are facing above mentioned issue.
We have tried lots but we haven't had success with it.

Code for creating a credential

var credential = new DefaultAzureCredential(new DefaultAzureCredentialOptions { ManagedIdentityClientId = "<your client id>" });

What are we missing?
Thank you!

PRADEEPCHEEKATLA 91,831 Reputation points

2022-05-31T06:16:31.437+00:00

Hello @PrashantRewatkar-4915,

Thanks for the question and using MS Q&A platform.

Based on the error message it does not look like SDK specific issue. As you are experiencing the 400 (Bad Request) from the server, which means missing some configuration issue.

Could you please check the configuration details like clientID which you are passing.

Meanwhile, you can check the Azure Identity client library for .NET.
Prashant Rewatkar 101 Reputation points

2022-06-01T07:49:26.203+00:00

Ok fine. what about DefaultAzureCredential ?

LinkedServiceClient client = new LinkedServiceClient(endpoint: new Uri(""), credential: new DefaultAzureCredential());

This code is working fine if we publish LinkedService from local but not after deployed on the server.

We don’t want to use ManagedIdentityClientId for create a client. That should be pickup from the server directly.

How could we manage that? It was working fine earlier. Now its throwing an error.

We are able to create a linked service from the server by using below code. We don’t want to use ManagedIdentityClientId.

var credential = new DefaultAzureCredential(new DefaultAzureCredentialOptions { ManagedIdentityClientId = "abcdef" });
var client = new DatasetClient(endpoint: new Uri("abc"), credential: credential);

1 answer

Your answer

PRADEEPCHEEKATLA 91,831 Reputation points

2022-05-31T06:16:31.437+00:00

Hello @PrashantRewatkar-4915,

Thanks for the question and using MS Q&A platform.

Based on the error message it does not look like SDK specific issue. As you are experiencing the 400 (Bad Request) from the server, which means missing some configuration issue.

Could you please check the configuration details like clientID which you are passing.

Meanwhile, you can check the Azure Identity client library for .NET.
Prashant Rewatkar 101 Reputation points

2022-06-01T07:49:26.203+00:00

Ok fine. what about DefaultAzureCredential ?

LinkedServiceClient client = new LinkedServiceClient(endpoint: new Uri(""), credential: new DefaultAzureCredential());

This code is working fine if we publish LinkedService from local but not after deployed on the server.

We don’t want to use ManagedIdentityClientId for create a client. That should be pickup from the server directly.

How could we manage that? It was working fine earlier. Now its throwing an error.

We are able to create a linked service from the server by using below code. We don’t want to use ManagedIdentityClientId.

var credential = new DefaultAzureCredential(new DefaultAzureCredentialOptions { ManagedIdentityClientId = "abcdef" });
var client = new DatasetClient(endpoint: new Uri("abc"), credential: credential);

Answer 1

ShaikMaheer-MSFT 38,631 Microsoft Employee Moderator

Hi @PrashantRewatkar-4915,

Thanks for posting query in Microsoft Q&A Platform.

From error message it seems you are supplying correct user assigned managed identity. Hence resulted in bad request.

I have gone through documentation SDK for concerned classes and properties. It seems ManagedIdentityClientId property specifies the client id of a user assigned Managed Identity. Click here to know more about same.

Kindly make sure you pass user assigned managed identity to that property. Managed Identities are two types System assigned and User assigned. Click here to know more about these.

Hope using user assigned managed identity will solve issue here.

----------

Please consider hitting Accept Answer button. Accepted answers help community as well.

Prashant Rewatkar 101 Reputation points

2022-06-08T04:22:44.037+00:00

Hello @ShaikMaheer-MSFT

Ok Accepted. But what we are looking as we do not want to mention managed identity or any ID while creating DefaultAzureCredential object.

This should be pickup from the server by default without explicitly mention and its working as well before.

Thanks

Share via

Azure Synapse :- ManagedIdentityCredential authentication failed

1 answer

Your answer