Forum Discussion
Fabric Sharepoint Shortcut not Refreshing
We are using the sharepoint shortcut with Fabric to load data from csv's into our data warehouse. The data is alwasys correct on the initial load after creating the sharepoint shortcut. However, after updates are made to the files, it is very inconsistent whether or not those changes are picked up. These are files that are often updated each month, some may be updated daily in the future. To update these files I have tried:
- Opening the file directly from file explorer, editing and saving (Updates sometimes, not always. No clear reason why)
- Updated data in a brand new csv file, performed a "save as" to save over top of the existing file (Data didn't update)
- Updated data from a brand new file, deleted the existing file, saved the new file with the same name as the original file (Data didn't update)
Has anyone else experienced this issue? I am close to abandoning the sharepoint shortcut as deleting and re-adding the shortcut each time is not a viable solution.
Hello markhaiar,
I've seen similar behavior with SharePoint shortcuts.
A OneLake shortcut provides access to the SharePoint files, but updates aren't always reflected immediately. Metadata and file changes can take some time to propagate, so replacing a file with the same name or overwriting an existing file may not be detected consistently.
A few things you could try:Verify that the SharePoint file's Modified timestamp is updated after each change.
If possible, avoid replacing files with the same name. Creating a new file (or version) is often detected more reliably than overwriting an existing one.
If you're using the shortcut as the source for a Lakehouse table, refresh or rerun the downstream ingestion process after the SharePoint update.
If consistent and near real-time updates are a requirement, you may find a more reliable approach is to use Power Automate or a Fabric Pipeline triggered by SharePoint file changes to ingest the updated file into the Lakehouse, rather than relying solely on the shortcut to detect changes.
If multiple users are experiencing the same inconsistent refresh behavior, it may also be worth raising a Microsoft support ticket, as this could be related to the current implementation of SharePoint shortcuts.
Best regards,
Omkar Shinde
Microsoft Fabric Enthusiast | Power BI Consultant
💡 If you found this response helpful, please consider giving it a Kudos.
✅ If this resolves your question, please mark it as the Accepted Solution to help others in the community.
5 Replies
- Omkar_1712
Solution Sage
Hello markhaiar,
I've seen similar behavior with SharePoint shortcuts.
A OneLake shortcut provides access to the SharePoint files, but updates aren't always reflected immediately. Metadata and file changes can take some time to propagate, so replacing a file with the same name or overwriting an existing file may not be detected consistently.
A few things you could try:Verify that the SharePoint file's Modified timestamp is updated after each change.
If possible, avoid replacing files with the same name. Creating a new file (or version) is often detected more reliably than overwriting an existing one.
If you're using the shortcut as the source for a Lakehouse table, refresh or rerun the downstream ingestion process after the SharePoint update.
If consistent and near real-time updates are a requirement, you may find a more reliable approach is to use Power Automate or a Fabric Pipeline triggered by SharePoint file changes to ingest the updated file into the Lakehouse, rather than relying solely on the shortcut to detect changes.
If multiple users are experiencing the same inconsistent refresh behavior, it may also be worth raising a Microsoft support ticket, as this could be related to the current implementation of SharePoint shortcuts.
Best regards,
Omkar Shinde
Microsoft Fabric Enthusiast | Power BI Consultant
💡 If you found this response helpful, please consider giving it a Kudos.
✅ If this resolves your question, please mark it as the Accepted Solution to help others in the community. - ParchitectI would add one important architecture distinction here:
a SharePoint shortcut is not the same thing as a controlled ingestion pipeline.A OneLake shortcut is essentially a reference to files that still live in SharePoint/OneDrive. That is very useful for discovery and zero-copy access, but I would be careful relying on it as the main mechanism for detecting overwritten CSV content and loading a warehouse consistently.In your case, the risky part is that the file name stays the same while the file content is being overwritten/replaced. Depending on caching, metadata propagation, and how the downstream process reads the file, Fabric may not always treat that as a new ingestion event in the way you expect.For production-style monthly or daily CSV loads, I would normally use the shortcut only as a landing/reference location, then run a controlled ingestion step:SharePoint folder→ OneLake shortcut / or SharePoint connector→ Fabric pipeline / Dataflow / Notebook→ write to Lakehouse table or Warehouse staging table→ load curated Warehouse tablesThat gives you a deterministic refresh process instead of relying on the shortcut view to behave like a file-change trigger.A few practical recommendations:- Avoid overwriting the same file in-place if possible.- Use versioned file names, for example Sales_2026_06_27.csv.- Add a control table or ingestion log with file name, modified timestamp, row count, and load timestamp.- Trigger or schedule a Fabric pipeline after SharePoint updates.- If the Warehouse is the target, load through a staging table first, then merge/replace into the final table.- If you must keep the same file name, validate the SharePoint “Modified” timestamp and rerun the downstream ingestion explicitly.So short answer: yes, others have seen inconsistent behavior with file replacements/overwrites. For reliable daily/monthly warehouse loads, I would not rely only on the SharePoint shortcut. I would use a pipeline/Dataflow/Notebook ingestion pattern and treat the shortcut as access to the source files, not as the refresh mechanism itself.If this remains inconsistent even after explicit downstream reruns, I would open a Microsoft support ticket because SharePoint/OneDrive shortcuts are now GA, but overwrite/change-detection behavior should still be validated for your exact scenario.🔍Parchitect
Solutions Architect · Microsoft Fabric Specialist💡Helpful? Kudos are appreciated.
✔️Solved? Mark as Solution so others can find it faster. Keep your files on auto save mood in this way you will not face any trouble for file update
v-achippaCommunity Support
Hi markhaiar,
Thank you for reaching out to Microsoft Fabric Community.
Thank you Omkar_1712, malaikanadeem12 and Parchitect for the prompt response.
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the user's for the issue worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa
- v-achippa
Hi @markhaiar,
We wanted to kindly follow up to check if the solution provided by the user's for the issue worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa
