Dataflows Gen2 and Pipelines Break After Ownership Transfer or Workflow Owner Leaves Organization
I have a question regarding Dataflows Gen2 and pipelines. We are experiencing an issue where workflows break when the original creator (owner) of a workflow, lakehouse, or pipeline leaves the organization. After this happens, the workflows are no longer able to read data from lakehouse tables. When investigating, it is not clear whether the issue is related to: - the lakehouse itself, - the dataflow gen2 itself, - the connection to the lakehouse, - the connection between the lakehouse and Dataflows Gen2, - or the dataflow configuration and permissions. - ...? Even after taking ownership of both the existing dataflows and the lakehouse, the problem still persists. In addition, creating a brand-new Dataflow Gen2 does not resolve the issue: when we try to read data from a specific lakehouse table, the dataflow fails during refresh with the same behavior. Is there a known reason why this issue affects both existing and newly created dataflows, and is there a recommended way to properly restore lakehouse connectivity or reconfigure permissions to resolve this problem? Thank you!