topic Work around for Azure vault in DataflowsGen2 to store source and destination in Dataflow

Work around for Azure vault in DataflowsGen2 to store source and destination

DSanthoshKumar — Wed, 10 Jul 2024 15:10:52 GMT

Hi,

We are using SQLServer server, username and password details manually to connect source from each DataflowsGen2 in fabric.

from the below link we understand that Azure key vault is not supported.

https://learn.microsoft.com/en-us/fabric/data-factory/data-factory-limitations#data-pipeline-limitations-in-microsoft-fabric

can you suggest the work around on changing server,username and password so that it should reflect to all DataflowsGen2 sources.

Re: Work around for Azure vault in DataflowsGen2 to store source and destination

miguel — Wed, 10 Jul 2024 18:27:44 GMT

Hi!

im not sure I follow. What's the expectation or the specific gap that you're trying to address?

currently the destination in a Dataflow Gen2 is fully driven by the UI. It can't be dynamically passed.

If you find any gaps or have suggestions, be sure to post them in the ideas portal: https://aka.ms/FabricIdeas

Re: Work around for Azure vault in DataflowsGen2 to store source and destination

Anonymous — Thu, 11 Jul 2024 03:27:53 GMT

Hi DSanthoshKumar ,

Since Dataflow Gen2 in Microsoft Fabric doesn't support Azure Key Vault, I think you can use the parameters in Dataflows Gen2 to store server, username, and password details.

If you're also using Azure Data Factory, you can create a linked service in ADF that connects to SQL Server. Then, use this linked service in DataflowsGen2.

Of course, you can also check out this document for more information: Enable Azure Key Vault for airflow - Azure Data Factory | Microsoft Learn

Best Regards

Yilong Zhou

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.