Semantic Model Breaks After DirectQuery to Direct Lake Migration Refresh

Hi Shreya_Barhate,

The fact that the model looks correct immediately after the migration is an important clue.

Based on the error message, I wonder if the relationships are actually a symptom rather than the root cause. The refresh error mentions that multiple source tables either do not exist or access was denied. If some Direct Lake tables become invalid during refresh, Fabric may no longer be able to maintain the relationships that depend on them.

A few things I would check :

•  Do all source tables still exist in the target Lakehouse/Warehouse?
•  Has anything been renamed (table name, schema, workspace, warehouse)?
•  Does the semantic model owner still have access to all underlying tables?
•  Are all relationships removed, or only those involving specific tables?
•  How was the migration performed (Desktop, XMLA, Tabular Editor, TMDL, etc.)?

The fact that everything looks fine before refresh but breaks afterwards makes me suspect a table binding, lineage, or permission issue rather than a relationship issue itself.

Hope this helps narrow it down