D365 F&O Tables Randomly Getting Unsynced from Fabric via Link to Fabric / Azure Synapse Link

Ramkishor 
Why this happens:

Microsoft service updates to D365 F&O — When Microsoft pushes updates that alter a table's schema (adding/removing fields, changing data types), the sync link for that table can break or get dropped automatically.

Customs Tables metadata changes- Any AOT change to a custom table (even a recompile or a new field) can cause the link to drop.

Lakehouse schema drift — If the Delta table schema in Fabric diverges from what D365 is pushing, the link self-terminates for that table to avoid data corruption.

You can find the admin log & dignostics logs(if enabled by PowerPlatform Admin) and check the table status and find further detail in there.

Recommended approach:

1-Set up alerting on table row counts in Fabric (via a simple notebook or pipeline) — if a table's count doesn't update within your expected refresh window, fire an alert before downstream reports fail.
2-For custom tables, freeze schema changes in production.
3-After any D365 F&O update cycle, actively verify your full table list in the Link to Fabric setup.

4-Keep a documented inventory of all synced tables so you can swiftly spot what's missing after the link broken.

The quick fix for all the dropped tables, you'll need to re-add them to the Link to Fabric configuration manually and trigger an initial sync.

If this helps, ✓ Mark as Kudos | Help Others