Dataverse to Fabric Synapse Link Sync not randomly stops working

[Swapnil_CR]

Hi,

Thank you in advance.

I have setup a Azure Synapse Link (aka Fabric Link) directly from Power Apps Dataverse to sync data from Dataverse to Fabric Lakehouse. This setup was working flawlessly until this week. I noticed issues around 8 to 11 Oct 2025 in India region ( West Europe Capacity).

From my understanding, the sync has a refresh interval of 60 mins and only syncs if there's new data available. I promptly validated there was always new data available in the system then too the 'last synced on time' was 1 day prior. 

I would appreciate if i could get some help understanding these below pointers

1. Reason for the sync issues

2. Any way to check if it's not from the organization but from Microsoft and its status

3. Any alternative towards building a system such that the data movement (from Dataverse to Fabrics) always happens on priority despite these issues.

[v-tsaipranay]

Hi @Swapnil_CR ,

We haven’t received an update from you in some time. Could you please let us know if the issue has been resolved?
If you still require support, please let us know, we are happy to assist you.

Thank you.

[v-tsaipranay · Accepted solution]

Hi @Swapnil_CR ,

Thanks for the update. Since the sync is still happening but delayed by 6–12 hours instead of the usual 1-hour interval, it sounds like Dataverse change tracking isn’t updating correctly for one or more linked tables.

Please try re-enabling change tracking to refresh it:

1. Go to the Power Apps Maker Portal → open your environment.

2. Under Tables, select each table used in your Fabric Link.

3. Open Settings > Change tracking, turn it off and back on, and save the changes.

4. Wait around 30 minutes for the changes to propagate, then monitor the next sync.

If the delay continues, try recreating the Fabric Link this resets the metadata mapping and often clears stalled sync states. Also, check the Power Platform admin center → Resources → Background jobs for any backlog that might be slowing things down.

These steps usually help restore the expected 1-hour sync. Please let us know if re-enabling change tracking improves the refresh timing so we can assist further if needed.

Thank you.

[v-tsaipranay]

Hi @Swapnil_CR ,

I wanted to follow up on our previous suggestions. We would like to hear back from you to ensure we can assist you further.

Thank you.

[Swapnil_CR]

Hi @v-tsaipranay ,

The issue still persists.

Things to note:

1. While the sync is occurring, it is delayed—observed at approximately 6 to 12 hours.

2. Although the data changes are present, the sync is not being triggered according to the minimum 1-hour interval, as it has consistently been over the past six months.

I would appreciate if you could give me a reference or guide me towards re-enabling change tracking or any alternative way to fix this

[v-tsaipranay]

Hi @Swapnil_CR ,

Thanks for reaching out to the Microsoft fabric community forum. Also thank you @vrsanaidu2025  for your response.

Also thank you for your update. The sync from Dataverse to your Fabric Lakehouse may be delayed due to issues such as Dataverse change tracking being stalled or disabled, pending export jobs, temporary service interruptions in West Europe, or link permission or configuration problems.

With the current delay of about 6 hours, please check that change tracking is enabled and working properly, look for any stalled export jobs, and review the Azure Synapse Link job status in the Power Platform admin center for any backlog. To restore sync, you can reinitialize change tracking, manually trigger a sync, and monitor job queues to clear any pending tasks.

If problems continue, try recreating the link or contact Microsoft Support. For ongoing reliability, consider setting up monitoring and alerts, using incremental refresh, implementing retry or auto-restart features, and for critical workloads, using hybrid pipelines that combine Fabric Link with custom Dataflows.

These steps should help identify the cause of the delay, restore sync, and ensure consistent data movement from Dataverse to Fabric.

To check if this is a Microsoft-related issue, review the Microsoft Fabric Service Status at Microsoft Fabric service status and look for any tenant-specific alerts in Azure Service Health.

Hope this helps. Please feel free to reach out for any further questions.

Thank you.

[Swapnil_CR]

Hi, Thank you!

Current Status : The sync is delayed for undisclosed time. Generally I have 1 hr buffer for data entry to data visible in Fabrics, but now it randomly is visible after 6 hrs. The current gap between latest data modified (Date Time of Entry) to latest sync date (Synapse Link Latest Sync) is around 6 hrs.

It has not yet resolved, which i suspect has something to do with change tracking ? Or something else ?

[vrsanaidu2025]

Looks like the sync stalled due to Dataverse change tracking or background export job hang, possibly combined with a temporary Fabric service interruption in West Europe capacity. We can re-enable change tracking, verify link permissions, and monitor Fabric health to get the sync running stable again.

[vrsanaidu2025]

Looks like the sync stalled due to Dataverse change tracking or background export job hang, possibly combined with a temporary Fabric service interruption in West Europe capacity. We can re-enable change tracking, verify link permissions, and monitor Fabric health to get the sync running stable again. and Possibly from MS Side, reach out.