Views in Warehouse Breaks Source Control Sync

Hi kozman​,

I think you have run into a documented Warehouse CI/CD limitation rather than an issue with the view definition itself.

Microsoft's current Warehouse Git integration documentation explicitly says that cross-item dependencies between Warehouses and SQL analytics endpoints are not currently supported reliably in development workflows. It also calls out item-sequencing and synchronization gaps during branch-out and branch switching.

That matches your scenario quite closely: the Warehouse view depends on the Lakehouse SQL analytics endpoint, but in a newly created workspace that dependency might not exist yet when Fabric tries to validate/apply the Warehouse definition.

One distinction I would make around the suggested workaround is that normal Update from Git is not selective. Microsoft's Git integration process documentation states that Update always synchronizes the entire branch; you cannot choose individual items during the update.

Selective item deployment is currently available during Branch out to workspace through Selective Branching. So for a feature workspace, a possible bootstrap sequence is:

1. Branch out with only the Lakehouse selected.
2. Wait for the Lakehouse and SQL analytics endpoint to be provisioned.
3. Add the Warehouse afterward once the dependency exists.

For a CI/CD pipeline outside that branch-out flow, I would probably separate provisioning from schema deployment: create/provision the Lakehouse first, then deploy the Warehouse/view after the SQL analytics endpoint exists.

I also could not find a documented option to disable Fabric's dependency validation during Update from Git.

So I agree that this is currently awkward for Warehouse views that depend on Lakehouse SQL endpoints. Until Microsoft improves cross-item dependency sequencing/rebinding, I would treat it as a deployment-order problem and make that order explicit in the CI/CD process rather than relying on a single workspace Git sync.

Warehouse Git integration is also still documented as Preview, so I would definitely raise this as product feedback if this pattern is central to your deployment architecture.

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.