Internal error when trying to add user assigned managed identity to Azure Data Factory

Question

I am trying to add a User Assigned Manager Identity to my Azure Data Factory instance, but I keep getting an InternalError.

I am generally trying to follow this guide https://techcommunity.microsoft.com/t5/azure-data-factory-blog/support-for-user-assigned-managed-identity-in-azure-data-factory/ba-p/2841013 .

It is the step where I add the managed identity as a User Managed Identity to the Azure Data Factory resource in Azure Portal where I am getting the InternalError. Has anyone else had this problem or know how I can overcome it?

The JSON response in the log is the following (with some bits removed):

{
"authorization": {
"action": "Microsoft.DataFactory/factories/write",
"scope": "/subscriptions/<subscription id>/resourceGroups/<resource group id>/providers/Microsoft.DataFactory/factories/<azure data factory name>"
},
"caller": "<email address>",
"channels": "Operation",
"claims": {
"aud": "https://management.core.windows.net/",
"iss": "https://sts.windows.net/<subscription id>/",
"iat": "",
"nbf": "",
"exp": "",
"http://schemas.microsoft.com/claims/authnclassreference": "1",
"aio": "",
"http://schemas.microsoft.com/claims/authnmethodsreferences": "pwd,rsa,mfa",
"appid": "",
"appidacr": "2",
"http://schemas.microsoft.com/2012/01/devicecontext/claims/identifier": "",
"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname": "",
"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname": "",
"groups": "",
"ipaddr": "",
"name": "",
"http://schemas.microsoft.com/identity/claims/objectidentifier": "",
"puid": "",
"rh": "",
"http://schemas.microsoft.com/identity/claims/scope": "user_impersonation",
"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier": "",
"http://schemas.microsoft.com/identity/claims/tenantid": "",
"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name": "",
"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn": "",
"uti": "",
"ver": "1.0",
"xms_tcdt": ""
},
"correlationId": "",
"description": "",
"eventDataId": "",
"eventName": {
"value": "EndRequest",
"localizedValue": "End request"
},
"category": {
"value": "Administrative",
"localizedValue": "Administrative"
},
"eventTimestamp": "2022-07-19T16:00:36.7005541Z",
"id": "/subscriptions/<subscription id>/resourceGroups/<resource group name>/providers/Microsoft.DataFactory/factories/wenl-rdsm-00-adf/events/",
"level": "Error",
"operationId": "c5515f3c-40d3-457e-a689-b158cbf9a451",
"operationName": {
"value": "Microsoft.DataFactory/factories/write",
"localizedValue": "Create or Update any Data Factory."
},
"resourceGroupName": "<resource group name>",
"resourceProviderName": {
"value": "Microsoft.DataFactory",
"localizedValue": "Microsoft.DataFactory"
},
"resourceType": {
"value": "Microsoft.DataFactory/factories",
"localizedValue": "Microsoft.DataFactory/factories"
},
"resourceId": "/subscriptions/<subscription id>/resourceGroups/<resource group name>/providers/Microsoft.DataFactory/factories/<azure data factory name>",
"status": {
"value": "Failed",
"localizedValue": "Failed"
},
"subStatus": {
"value": "InternalServerError",
"localizedValue": "Internal Server Error (HTTP Status Code: 500)"
},
"submissionTimestamp": "2022-07-19T16:01:37.2973463Z",
"subscriptionId": "",
"tenantId": "",
"properties": {
"statusCode": "InternalServerError",
"serviceRequestId": null,
"statusMessage": "{\"error\":{\"code\":\"InternalError\",\"message\":\"Internal error has occurred.\"}}",
"eventCategory": "Administrative",
"entity": "/subscriptions/<subscription id>/resourceGroups/<resource group name>/providers/Microsoft.DataFactory/factories/<data factory name>",
"message": "Microsoft.DataFactory/factories/write",
"hierarchy": ""
},
"relatedEvents": []
}

Answer 1

My colleague was able to figure out the problem here.

We had a User Assigned Managed Identity added to the Azure Data Factory instance that had been deleted/no longer existed. Once we removed the inexistent User Assigned Managed Identity from the Azure Data Factory Managed Identities, we were then able to add the one that I wanted to add.