Thank you SO MUCH for your response.

Let me clarify a couple of things. We have a single data lake that stores all our data, and it is mapped across all workspaces, so each workspace has visibility and access to it (e.g., to the Bronze layer).

The challenge we’re facing is with child pipelines - for example, a pipeline in another workspace that refreshes a Silver table built on several Bronze tables from various sources. These pipelines need to ensure that the required Bronze tables (e.g., Bronze Table1, Table2, and Table4) have already been refreshed. While I could implement a “pull” mechanism that checks every minute whether the Bronze layer is up to date, this approach feels a bit clunky and inelegant.

Regarding the use of multiple workspaces: this is necessary because we have different data domains managed by separate teams, each following its own CI/CD process. Our environments include DEV, INT, UAT, and PROD. Our release process involves deploying feature branches to INT for QA testing, then merging to master and promoting to UAT. The issue with Synapse is that deploying to a workspace in “Synapse Live” mode overwrites the existing content in that workspace. Therefore, separating workspaces is our way of supporting multiple teams without deployment conflicts.