Forum Discussion
Helper IVSharePoint Shortcut showing no Content
Hi mkjit256,
That extra URL helps quite a lot.
I would not move the files into Shared Documents yet. Microsoft's current OneDrive/SharePoint shortcut documentation does not state that shortcuts are limited to the default Documents library. In fact, Microsoft recommends creating the shortcut at the most specific folder level rather than at the document-library root.
From the URL you posted, it looks like:
- BIA is the SharePoint site
- Operations is the display name of the document library
- Ops is probably the library's internal URL name
- PowerBI Data/Output is the folder you actually want
So the target path appears to be something like:/sites/BIA/Ops/PowerBI Data/Output
The fact that the Fabric picker only exposes Shared Documents therefore looks more like a library-enumeration issue than proof that your custom library is unsupported.
One useful isolation test would be to create a fresh connection against the exact site URL:
using the same organizational account that can browse the Ops library in SharePoint, then check whether Ops appears in the shortcut browser.
If it still only shows Shared Documents, I would capture that as the repro.
There is also a OneLake Shortcuts REST API where a SharePoint shortcut is represented by a location and subpath. That may be worth testing as a workaround because the API lets you specify the SharePoint subpath directly rather than relying on the folder picker.
I would use the library's URL/internal name (Ops) rather than its display name (Operations) when testing the path.
Also confirm that BIA is a normal SharePoint site rather than a subsite or hub site, because Microsoft currently lists SharePoint subsites and hub sites as unsupported for OneLake shortcuts.
AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.
Advocate IIIHey 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.