Data & Analytics
Dataverse tables appear in Fabric but cannot be read: check the link identity
Visible lakehouse shortcuts can still fail at the Dataverse connection. Verify environment role, connection identity and region.
October 21, 2026
The Link to Fabric wizard created a lakehouse and shortcuts, but a query fails with “access to target location denied.” A Fabric user report describes a link that looked complete while the identity used for access lacked the needed rights. An object appearing in the catalog proves metadata was created, not that its data path works.
Confirm which identity built and runs the link
Record the Dataverse environment, Fabric workspace, link creator, configured connection and authentication method. Microsoft's Link to Fabric setup guide requires appropriate Dataverse administration rights to create the link and describes how to inspect the connection under Manage connections and gateways. It recommends workspace identity where supported, which avoids dependence on a person's refresh token. That identity still needs to be onboarded as a Dataverse application user with the appropriate role.
Separate setup, authorization and geography
Check the wizard's prerequisite result, the link's connection state, then query one known table as the connection identity and as the intended reader. Verify the role on the Dataverse side and the Fabric item permissions. Also confirm the capacity and environment location meet the documented geography requirement. These failures can produce similar user-facing symptoms but have different owners.
Make the link operable after handoff
Document who can rotate or change the connection, how to test a newly added table and which sample query acts as a health check. If an organizational account is used, include a process for MFA or Conditional Access changes. Do not grant broad roles merely to make the wizard green; validate the intended identity and least-privilege path with the administrators who own Dataverse and Fabric.
Adovo’s view
A visible table is a promise to analysts. The link is production-ready only when a named operating identity can keep that promise after the original builder leaves. Treat connection ownership as part of the data product, not a setup detail.