Deployment Pipeline with Fabric Link (Dataverse) – Lakehouse

hi SHAccion 

We cant control tjis atm , Fabric Link always creates a new Lakehouse and cannot attach to an existing one deployed via pipeline

Use Fabric Link separately in each environment and do not deploy the auto-created raw Lakehouse through Deployment Pipeline. The better approach is to let Dev, Test, and Prod each have their own Dataverse-to-Fabric raw layer, then deploy only the Gold views/logic, semantic model, and reports across environments. This fits Fabric guidance that environment-specific configuration should be handled per stage, not automatically converted during deployment


For Gold layer automation, keep the SQL/view logic in source control and deploy or run the same scripts in each environmen

don’t recreate it manually. Promote the semantic model through the pipeline, then use a data source rule so Test points to the Test SQL endpoint.

Hi SHAccion,

We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.

nilendraFabric ,Thanks for your prompt response

Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community support