question

MichalMlka-6672 avatar image
0 Votes"
MichalMlka-6672 asked PRADEEPCHEEKATLA-MSFT commented

Parametrization template: Databricks linked service

Hi,

I tried to reuse our Parametrization template from ADF for Synapse.
It works for database, storage, keyvault, .... but does not for Databricks cluster connection.

Databricks linked service properties are not parametrized after publish and template generation.

Used definiton is:

 *"AzureDatabricks": {
     "properties": {
         "typeProperties": {
             "domain": "-:-domain:string",
             "workspaceResourceId": "-:-dbxWorkspaceId:string",
             "existingClusterId": "-:-clusterId:string"
         }
     }
 },*

Should be there something different for Synapse?

Thanks



azure-synapse-analytics
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

PRADEEPCHEEKATLA-MSFT avatar image
0 Votes"
PRADEEPCHEEKATLA-MSFT answered PRADEEPCHEEKATLA-MSFT commented

Hello @MichalMlka-6672,

Welcome to the Microsoft Q&A platform.

Only certain fields are parameterized by default. But you can set a template to customize them by forcing to override it at deployment time.

For more details, refer to Use custom parameters with the Resource Manager template.

You may checkout this article Fixing ADF Databricks Linked Service which addressing the same issue.

Hope this helps. Do let us know if you any further queries.


  • Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.

  • Want a reminder to come back and check responses? Here is how to subscribe to a notification.

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello @MichalMlka-6672,

Just checking in to see if the above answer helped. If this answers your query, do click Accept Answer and Up-Vote for the same. And, if you have any further query do let us know.

0 Votes 0 ·

Hi, thanks for your answer. As you can see in my query, We use this parametrization approach.

I changed it, according to shared article, and defined parametrization for '*' linked service and not specific for Databricks:

 "*": {
     "properties": {
         "typeProperties": {
             "domain": "=::string",
             "workspaceResourceId": "=::string",
             "existingClusterId": "=::string"
         }
     }
 }

But the result is same. Databricks' properties are not parametrized in a published ARM template.

0 Votes 0 ·

Hello @MichalMlka-6672,

This issue looks strange. For a deeper investigation and immediate assistance on this issue, if you have a support plan you may file a support ticket.

0 Votes 0 ·