Configuring Linked Service for Dev to Prod Movement in Azure Synapse Analytics

Question

In Azure Synapse Analytics, I have a linked service of type Azure SQL Database Managed Instance, and I have two linked services, one for dev and one for prod. How can I move from dev to prod without changing the linked service manually? How can I make it configurable?

Answer 1

This article suits well your case :

Create global parameters for server name, database name, Username, and Password. It is recommended to encode the credential information in base64 format to prevent misuse. Global parameters can be passed when referencing the linked service in the dataset or pipeline.

Create parameters for server name, database name, username, and password in the linked service parameter section.

Select the server name parameter for the server name field and choose the appropriate parameters for the other fields.

For the password, it is possible to store it in Azure Key Vault and retrieve it by specifying the secret name.

The connection details have now been parameterized. Use the test connection feature to verify the success of the connection. Pass the parameters and click on test connection.

More links :

https://stackoverflow.com/questions/69281596/creating-multiple-environment-parameters-for-azure-data-factory-linked-services

https://learn.microsoft.com/en-us/azure/data-factory/parameterize-linked-services?tabs=data-factory

Answer 2

Hi Aditya Singh ,

Thankyou for using Microsoft Q&A platform and thanks for posting your query here.

ADF will automatically parameterize certain things for you. To see all of the items that ADF parameterizes for you, then you can look at the file ARMTemplateParametersForFactory.json. One of the most obvious ones is the name of the ADF instance itself, as you can't have the Prod ADF instance named the same as the Dev ADF instance.

When deploying the ARM Templates, you can pass override parameters that include custom values that are specific to each of your environments. This way you can still use 1 set of ARM Templates for all of your environments. But, when deploying to Test you'll pass in overrides that are specific to Test, when deploying to Prod you'll pass in overrides that are specific to Prod, etc.

You can also create your own custom parameters too : Use custom parameters with the Resource Manager template

Hope it helps. Kindly accept the answer by clicking on Accept answer button. Thankyou