Forum Discussion
mkjit256
Helper IV
5 days agoSharePoint Shortcut showing no Content
Hello I am trying to set a shortcut in Lakehouse (tried both the create table shortcut, and create shortcut from files section) to a SharePoint folder, I can see the site, and also the connection aut...
DreamITLearn
1 day agoRegular Visitor
Hey mkjit256 ,
this is usually one of these:
- Delegated vs. app permissions – If your SharePoint connection is using an app-only/service principal auth method rather than your own delegated login, it can browse the site and see the folder structure but fail to enumerate files if permissions weren't explicitly granted at the library level, not just the site level.
- Broken/synced files showing as empty – If the "Shared Documents" folder has files synced via OneDrive client or has some in a "pending" state, the shortcut browser sometimes shows nothing even though the web UI displays content, this is a caching mismatch between SharePoint's Graph API response and what you see in browser.
- URL trailing slash or casing – Since you're using the sites/sitename pattern, double check there's no trailing slash and the site name casing matches exactly. Fabric's shortcut connector can silently fail to traverse if there's a mismatch.
- Folder-level unique permissions – If someone broke inheritance on subfolders inside Shared Documents (common in larger orgs), the connector account may see the parent folder exists but can't read into it, this shows as "No Content" rather than an access-denied error, which is misleading.
Fastest way to isolate it: try creating the shortcut against a brand new, simple test folder with no nested subfolders or broken permissions. If that works, it confirms it's a permissions/inheritance issue on your actual folder, not a connector bug.