Wed, Dec 2 · 6:00 PM AEST
Private Link Workspaces in Fabric: Not a Drop-In Replacement
Private Link workspaces in Microsoft Fabric create a specialised private connectivity boundary rather than a direct replacement for public workspaces. Key constraints include the lack of item-level OneLake sharing (forcing a broader Viewer role that exposes all source-workspace items), unsupported semantic models, and item-specific routing: notebooks use Managed Private Endpoints while gateway-supported items follow separate paths with delegated credentials and no Kerberos SSO.
Outbound Access Protection rules must be defined per path (MPE, direct cloud or gateway), and capacity moves require a full remove–recreate sequence. Gateway idle windows can dominate capacity unit consumption, so design must account for query frequency as well as active runtime. Treat Private Link workspaces as a deliberate security boundary with explicit path mapping, workspace segmentation and operational planning.