Open nbarichev opened 2 months ago
Thank you for opening this issue, we will look into it.
Here are some similar issues that might help you. Please check if they can solve your problem.
Faced similar issue with AzureSQLMI. It works if you choose legacy connection string.
"name": "AzureSQLServerMI",
"type": "Microsoft.Synapse/workspaces/linkedservices",
"properties": {
"type": "AzureSqlMI",
"connectVia": {
"referenceName": "AutoResolveIntegrationRuntime",
"type": "IntegrationRuntimeReference"
},
"annotations": [],
"typeProperties": {
"connectionString": "Integrated Security=False;Encrypt=True;Connection Timeout=30;Data Source=<ServerName>;Initial Catalog=<DBName>",
"credential": {
"type": "CredentialReference",
"referenceName": "MI"
}
}
}
}```
Describe the bug
Using
az synapse linked-service create
I'm not able to create Synapse linked service of type AzureSqlDW. Though the json code of linked service is the same as the one I see in Synapse Web UI for already existing linked service created via click-ops.Command used
ls_definition.json
Related command
az synapse linked-service create --subscription xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx --workspace-name WORKSPACE_NAME --name LINKED_SERVICE_NAME --file "@FILE"
Errors
Issue script & Debug output
Expected behavior
Synapse linked service created using json file provided
Environment Summary
azure-cli 2.64.0
core 2.64.0 telemetry 1.1.0
Extensions: account 0.2.5 automation 1.0.0b1 containerapp 0.3.53
Dependencies: msal 1.30.0 azure-mgmt-resource 23.1.1
Python (Darwin) 3.11.10 (main, Sep 7 2024, 01:03:31) [Clang 15.0.0 (clang-1500.3.9.4)]
Legal docs and information: aka.ms/AzureCliLegal Your CLI is up-to-date.
Additional context
From the debug output I see one strange thing to me –
providers/Microsoft.DataFactory/factories/
Also the same issue I face for linked service of type
AzureSqlMI