SharePoint to Microsoft Fabric file sync
Order workbooks arrived in SharePoint every day and had to reach a Fabric lakehouse for the forecasting team. I automated the transfer.
18 → 1an 18-step flow replaced by one scheduled copy job
SharePointFabric Copy Jobincremental, scheduledLakehouse
Checked: files read against files written, not the job status
Method and results
- The first design was an 18-step Power Automate flow that wrote to OneLake through its API. I resolved eight faults before reaching one that would not move.
- A control test isolated it. Sending the word HELLO succeeded and sending a file failed. The connector wraps binary content in JSON, so it cannot send a raw file. I stopped debugging and changed approach the same day.
- The sync was rebuilt as a scheduled Fabric Copy Job with incremental copy, and it keeps the year and month folders.
- Two configuration errors each reported "Succeeded" while copying zero files. Since then I check the number of files read and written, whatever the job status says.
- I also wrote a notebook that loads the files into raw Delta tables, reading every column as text and recording the source file on each row.