英文:
Azure CLI - Synapse linked service not accepting user assigned managed identity credential
问题
我正在尝试通过Azure CLI在Synapse中创建一个与Key Vault关联的链接服务。
我使用类似以下定义文件的内容：
{
"properties": {
"annotations": [],
"connectVia": {
"referenceName": "AutoResolveIntegrationRuntime",
"type": "IntegrationRuntimeReference"
},
"type": "AzureKeyVault",
"typeProperties": {
"credential": {
"referenceName": "SynapseUserAssignedManagedIdentity",
"type": "CredentialReference"
},
"baseUrl": "{baseUrl}"
}
}
}
并且使用Azure CLI如下：
az synapse linked-service create `
--workspace-name $SynapseWorkspaceName `
--name $LinkedServiceName `
--file $LinkDefinition
其中$LinkDefinition是包含定义的JSON字符串。referenceName 链接到预先创建的Synapse凭据 SynapseUserAssignedManagedIdentity。
然而，当我执行此操作时，链接服务最终会被创建，但默认使用了“系统分配的托管标识”。我尝试了各种变化来使其工作，但它总是恢复到使用系统分配的托管标识。
如果您查看API文档，定义文件看起来是正确的，所以我不确定为什么它不像预期的那样工作。
是否有人知道为什么对我而言这不起作用？
英文:
I'm trying to create a Key Vault linked service in Synapse through the Azure CLI.
I use a definition file like
{
"properties": {
"annotations": [],
"connectVia": {
"referenceName": "AutoResolveIntegrationRuntime",
"type": "IntegrationRuntimeReference"
},
"type": "AzureKeyVault",
"typeProperties": {
"credential": {
"referenceName": "SynapseUserAssignedManagedIdentity",
"type": "CredentialReference"
},
"baseUrl": "{baseUrl}"
}
}
}
and use the Azure CLI like
az synapse linked-service create `
--workspace-name $SynapseWorkspaceName `
--name $LinkedServiceName `
--file $LinkDefinition
where the $LinkDefinition is a JSON string with the definition. The referenceName links to a Synapse Credential SynapseUserAssignedManagedIdentity that was created in advance.
However, when I perform this action, the linked service ends up being created but uses the 'System Assigned Managed Identity' by default. I tried all sorts of variations to get it to work, but it always reverts to using the system assigned managed identity.
If you look at the API documentation the definition file does look correct, so I'm not sure why this doesn't work as expected.
Does anyone have a clue why this is not working for me?
答案1
得分: 1
PG确认这是一个已知问题，他们正在修复这个问题。 预计修复日期为8月1日。
英文:
PG confirmed that this is a known issue, and they are in the process of fixing the issue.
ETA would be Aug 1st.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论