Please make it possible to use different connections (different identities), different source paths and different destination paths in dev/test/prod of a Dataflow Gen2.
When using Fabric Lakehouse as source or destination, it is already possible to use different source lakehouses and destination lakehouses in dev/test/prod, because they all use the same Lakehouse connection.
However, we need dynamic ability also for other source and destination types, like Azure SQL Database, where we want to use different connections (credentials) in dev/test/prod.
We also want the option to specify different connections (credentials) for dev/test/prod when using Lakehouse as source or destination.
This could be made dynamic either through deployment rules or variable library.
frithjof_v
on:
Job scheduler API: List failed runs
SriV
on:
Connecting to AML Workspace from Fabric Notebook u...