How to handle changing of connection in lookup activity in data pipeline between TEST and PROD

[KimTutein]

Hi Community

I cannot figure out how to change a connection in a lookup activity from in a data pipeline when going from TEST to PROD workspace. I have a simple lookup activity which tells me the latest load time if some data in my lakehouse.

I have used the connection type Azure SQL Database (I cannot just point to the lakehouse as that only support selecting Tables or Files and not a query). The Azure SQL Database connection works fine however I am not able to change the connection to PROD setup when using deployment pipeline to move this data pipeline to PROD workspace.

If anyone that has input on how to handle this it will be much appreciated – and perhaps a small example.

Friendly regards

Kim Tutein

Appendix - the lookup activity:

[KimTutein]

Hi @v-vpabbu 

Thank you for your answer. Rerarding using parameters in deployment rules - as far as I can see we cannot setup rules for data pipelines. See this table from Microsoft learn (link: Create deployment rules for Fabric's ALM - Microsoft Fabric | Microsoft Learn😞 

[v-vpabbu · Accepted solution]

Hi @KimTutein,

Thanks for highlighting the limitation. Please proceed with a manual copy for now. I also suggest posting it in the Ideas platform so that Microsoft may consider implementing it in the future.
https://ideas.fabric.microsoft.com/ideas/search-ideas/  

Feedback submitted through these channels is frequently reviewed by the product teams and can contribute to meaningful improvements.

Regards,
Vinay Pabbu

[v-vpabbu]

Hi @KimTutein,

Thank you for reaching out to Microsoft Fabric Community Forum.

To achieve the switching of connections in the Lookup activity between TEST and PROD in a Data Pipeline, can be achieved using parameters

After extensive research, I found that parameterizing connections in Microsoft Fabric Data Pipelines is not currently supported. manually we can update the connection but they are not recommended due to lot of manual intervention and inefficiency involved.

The best approach is to use Deployment Pipeline Rules. This ensures that the connection settings (server name, database name) are updated automatically when transitioning the pipeline from TEST to PROD. This ensures the correct connection settings are applied without manual intervention.

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!

Regards,

Vinay Pabbu