Tables synchronization issue

If the sync status of your D365 F&O UserInfo table to the Fabric lakehouse remains stuck at "Initial sync in progress" for hours, this is a known issue often related to the initial synchronization process getting stuck or delayed in Fabric or Synapse Link.

Common causes and fixes:

• The initial sync can take a long time depending on table size and system throughput. Sometimes it appears stuck but is still processing.

• There could be metadata inconsistencies or tracking issues causing the sync to hang.

• Removing the affected table from Fabric Link and re-adding it can reset change tracking and resume sync.

• Ensure change tracking is properly enabled in D365 F&O for the table.

• Verify no permissions or connection issues between D365 and Fabric.

• Check OneLake to see if any data files are created for the table.

• Sometimes a manual refresh or trigger can restart the sync.

Recommended approach:

1. Remove the UserInfo table from your Fabric Link synchronization setup.

2. Wait a bit, then add it back to force a fresh initial sync.

3. Monitor the sync progress in the Fabric portal and in OneLake.

4. If it still hangs, open a Microsoft support ticket as this might be an internal backend issue.

Additional tips:

• Keep an eye on Fabric community forums for updates, as Microsoft is actively working to address such sync issues.

• Watch for sync errors or warnings that could indicate schema mismatches or unsupported data types.

This approach aligns with community and official docs for troubleshooting stuck initial syncs when pushing F&O data to Fabric lakehouses.