I’m requesting that Microsoft add native support for SharePoint document libraries (files/folders) in Fabric pipelines and OneLake shortcuts.
Right now:
Fabric pipelines do not support the SharePoint folder connector.
You can only access SharePoint via lists or in Dataflow Gen2 (Power Query) for folders, not in Copy/pipeline operations.
A community idea already exists to add OneLake shortcuts for SharePoint/OneDrive, which shows there’s demand.
Why this is important:
Many organizations store CSV/data files in SharePoint libraries due to governance, auditing, or collaboration needs.
Without native pipeline support, teams are forced to build workaround solutions (Graph API, Power Automate, staging zones), which incur cost, complexity, and maintenance overhead.
Having a built-in connector or shortcut would streamline data ingestion into ADLS/Lakehouse with lower friction and fewer moving parts.
Suggested capabilities:
A SharePoint/OneDrive shortcut type in OneLake, similar to ADLS shortcuts, to allow seamless "mounting" of document libraries.
In pipelines: a "SharePoint Document Library" source (binary file mode) that supports reading from specified folder paths, recursive traversal, filtering, and incremental file ingestion.
Metadata support: ability to fetch custom columns metadata properties on files (e.g., tags, content types).
Support for common authentication methods (OAuth2, service principals, managed identity) and robust error handling for large volumes of files.
Fine-grained path filters (include/exclude file types, subfolders) to avoid ingesting entire site content.
on:
Improve error message when dataset mixes cloud and...
on:
Org apps per app and workbooks with custom message...
on:
Deployment pipeline rule for data factory pipeline...
on:
Epic Idea: Show visual dependencies for bookmarks
dm-p
on:
Allow standard Focus Mode for custom visuals that ...