There was a case when the Azure Subscription was moving from one owner to another. It was accidentally move another tenant's subscriptions. There was interesting thing happened. Azure Synapse System Assigned Manage Identity (MID) was missing. All other linked jobs were failed to connected to Synapse.
Usually MID missing is easy to fix. But since Synapse is managed by Microsoft and there's not simple way to just apply back MID.
So I contacted Microsoft Technical Support. Initial troubleshooting was not straight forward, the support guy was trying to help using existing Microsoft Documentation. But all were outdated, later on he managed to find internal article which is not published yet in Public Microsoft Documentation.
So here is the command to fix the missing MID.
Firstly, Delete all identities on the Synapse Analytics.
az rest --method patch --url https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Synapse/workspaces/{workspaceName}?api-version=2021-06-01 --headers Content-Type=application/json --body '{ \"identity\":{\"type\":\"None\"}}'
Next recreate the system assigned managed identity
az rest --method patch --url https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Synapse/workspaces/{workspaceName}?api-version=2021-06-01 --headers Content-Type=application/json --body '{ \"identity\":{\"type\":\"SystemAssigned\"}}'
Comments
Post a Comment