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

[Ramkishor]

Hello @Anonymous ,

We are using Microsoft Fabric in our Production environment and have been successfully consuming Dynamics 365 Finance & Operations data through Link to Fabric and Azure Synapse Link for several months.

Recently, we encountered an unexpected issue where multiple tables suddenly stopped syncing to Fabric. The affected tables include several custom tables as well as some standard D365 F&O tables.

What's puzzling is that:

• No changes were made to the Link to Fabric configuration.

• No one manually removed these tables from the synchronization setup.

• The tables were syncing successfully for months before the issue occurred.

• The missing tables are no longer available in the Fabric Lakehouse, causing downstream Power BI reports and data pipelines to fail.

We would like to understand:

1. Has anyone experienced tables becoming unsynced automatically without manual intervention?

2. Are there known scenarios where Link to Fabric or Azure Synapse Link removes tables from synchronization?

3. Are there logs available that can identify why a specific table was removed or stopped syncing?

4. What is the recommended approach to prevent such issues in a production environment?

Any insights, recommendations, or similar experiences would be greatly appreciated.

Thank you.

[v-anbandari]

Hi @Ramkishor,

Just checking in again on your issue. Could you please confirm if the solution worked?

Please let us know if you need any further assistance.

Thank you.

[v-anbandari]

Hi @Ramkishor,
 

Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to @Murtaza_Ghafoor and @deborshi_nag  super user for sharing valuable insights.
 

Could you please confirm if your issue has been resolved using the suggested approach? This will help other community members facing similar scenarios.

Thank you.

[Murtaza_Ghafoor]

@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

[Ramkishor]

Hi @Murtaza_Ghafoor ,

Could you please let me know where can I find the Admin logs and Diagnostic logs ? 

Regards,

Kishor.

[Murtaza_Ghafoor]

@Ramkishor 

1-Azure Synapse Link / Fabric Link to Fabric Monitoring (First Place to Check)

In D365 F&O:

Go to System administration(if you have access to Power Platform admin Portal) → Setup → Azure Synapse Link (or Link to Fabric).

Open your link profile.

Review:

Table status

Failed tables

Synchronization status

Error messages

Recent refresh activity

If a table was removed due to a schema validation, the error often appears in here.
2-D365 F&O Batch Job History

Many synchronization activities run as batch jobs.

Navigate to:

System administration (if you have access to Power Platform admin Portal) → Inquiries → Batch jobs

Review:

Failed jobs

Cancelled jobs

Jobs related to Synapse/Fabric Link, Export to Data Lake, or Fabric

You may find downstream failures even when the source synchronization appears healthy.

If this helps, ✓ Mark as Kudos | Help Others

[deborshi_nag]

Hello @Ramkishor 

F&O tables need specific indexes for Synapse Link, which can be removed during environment refresh or invalidated by schema changes.

To resolve this, run the "Enable Entity Indexes for Synapse Link" batch job in your Finance and Operations environment. Navigate to System Administration > Setup > Azure Synapse Link > Enable Entity Indexes. Choose the tables or entities to re-index, or select all, then run the job to recreate the indexes. This restores the indexing structure for data synchronization with Synapse. Afterward, check your Azure Synapse Link configuration in the Power Platform Admin Center to ensure the tables are syncing and the required indexes are present.