Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
2,884 questions
Getting InvalidUserAssignedMiCredential when trying to deloy Synapse Artifacts
kk
41
Reputation points
Hi,
I am trying to deploy synapse artifacts. I am getting error
{
"ArtifactName": "DevUserAssignedMI",
"ArtifactType": "Credentials",
"StatusCode": "InvalidUserAssignedMiCredential",
"ErrorMessage": "The referenced user assigned managed identity in the credential is not associated with the factory. Credential name: DevUserAssignedMI, Managed identity resource id: /subscriptions/
{count} votes
-
AnnuKumari-MSFT 21,406 Reputation points Microsoft Employee2022-09-12T18:00:59.953+00:00 Hi @kk ,
Thankyou for using Microsoft Q&A platform and thanks for posting your question.
Kindly make sure the User defined managed identity is created/ deployed into the higher environment before you deploy the credentials.
If you still face the same issue by taking care of the sequence of deployment, then I would investigate further on this by trying to reproduce the same. Kindly let me know how it goes. Thankyou.
Hi @kk ,
We haven’t heard from you on the last response and was just checking back to see if the issue got resolved . Would really appreciate if you could share the updates with the community.
I am getting same error. What is the solution for this?
In my case, the issue happened because I was using User managed identity in the Azure Synapse workspace. The workspace was encrypted using a Key in key vault and access policy to the key vault was based on user managed identity. I changed the key vault access to use System assigned managed identity and removed the user managed identity from workspace. I was able to publish the artificat after that. I was originally trying to publish a credential which was using User managed identity.
Had same issue. Apparently, assigning the user managed identity to workspace + using that to encrypt data using Key vault causes some issues. To resolve, please remove the user managed identity and change the workspace to use System managed identity to access the Key in Key vault. You can add the user managed identity again after publishing the results.
Sign in to comment