What Really Happens When You Enable Private Link on a Fabric Workspace
In this blog post I am going to explain what happens when you enable Private Link on a Fabric Workspace.
I am currently working with an Enterprise customer who is implementing Private Link Workspaces, and I found that there is a lot of information required to understand how to get it successfully planned and implemented for Microsoft Fabric.
A lot of the information below is from a real world implementation based off of the Microsoft Learn Documents and working directly in Microsoft Fabric.
There are quite a few things that change when you enable this feature.
The initial question would be why you would want to enable a Private Link Workspace.
NOTE: It is also possible to enable a Tenant-Level Private Link, but I would not recommend this as there are a lot of limitations in doing so!
Common scenarios include:
- Restricting access to Fabric data from a corporate network.
- Providing access through an Azure virtual network.
- Allowing access from on-premises networks connected through ExpressRoute or a site-to-site VPN.
- Protecting regulated or sensitive data workloads.
- Separating highly secured data workspaces from general-purpose Fabric workspaces.
- Allowing private access to specific workspaces without applying Private Link to the entire tenant.
- Build agents and automation services using public Fabric endpoints.
What happens when Private Link is Enabled
As shown below, this is the typical path when accessing a Fabric Workspace.

When enabling a Private Link Workspace, what it means is that you can NO LONGER access the Workspace from the Internet. You must go via the Azure VNET as shown below.
This is a high-level overview there are quite a few steps to get this working (here is my previous blog post where I detail those exact steps https://www.fourmoo.com/2026/05/28/creating-a-private-link-in-microsoft-fabric-no-public-access/

As shown above, this ONLY controls all inbound access to the workspace.
All data leaving a Fabric Private Link workspace by default will still go out directly to the Internet as shown below.
NOTE: This is very important because it is sometimes assumed that Inbound access is restricted, that the same applies for Outbound connections, this is not the case!

When a user tries to access a private Link workspace once enabled, they get the following as shown below.

Unsupported Items when creating a Private Link Workspace
It is critical to understand when a Private Link Workspace is created the following items CANNOT be created.
NOTE: This is the unsupported items as of Nov 2026 and I am sure this will change going forward.

Item Sharing is not Supported
As it stands today Nov 2026 it is not possible to share Items in a Private Link Workspace.
For example, you cannot use the Share Item in a Private Link Workspace.
This is important for example if you are using Shortcuts between workspaces, because to connect you must Share the Lakehouse Read permissions to the users (ideally via Entra ID Security Group) for the user to see the Lakehouse.
NOTE: This is something to take into consideration for your Private Link Workspace design.
DirectLake is currently not supported
As it stands today Nov 2026 it is not possible to access DirectLake between workspaces.
There is another way to do this, which is to create a Lakehouse in a Public Workspace and create a shortcut to the Private Link Workspace with the combination of a Managed Private Endpoint (If this is something of interest please let me know as I can create a blog post on how to do this).
For getting data into a Semantic model the options are Import or DirectQuery.
Workspaces cannot change Capacity
When a Workspace has got Private Link enabled it is not possible to change to a different Fabric Capacity.
It is possible to scale the Capacity to a larger or smaller SKU.
If there is a requirement to change Capacity the Private Link needs to be deleted before the capacity change can take place. Which requires careful planning before implementing a Private Link Workspace.
How to Access Private Link Workspace
To access a Private Link Workspace the user must come through the Azure VNET which will then create an internal path to access the workspace.
As in my prior diagram this could be via GSA or a Virtual Desktop Interface or Virtual Machine where it is running within the VNET of the Private Link Workspaces.
As shown below, the Fabric UI looks identical when accessing a Private Link Workspace via a Virtual Machine.

How to connect to Items in a Private Link Workspace
One of the things to understand is when using a Private Link Workspace this now is using a Private DNS server which sits inside the VNET.
Below is what it looks like in Azure to give you an understanding of the Internal DNS.

What this means is if I want to connect to using a SQL Analytics Endpoint in a Private Link Workspace, I need to use the internal FQDN otherwise the connection will fail.
Be default when looking for the SQL Analytics Endpoint it would be the following below:
kvgqxv4suxzelgptfgnol3t21y-1r3dm3togigetjhqa4k5mo7h6m.datawarehouse.fabric.microsoft.com
The pattern for the internal FQDN is it needs to have the + z + the first to letters of the workspace GUID added before the .datawarehouse
For example, this is the workspace GUID “6e3676e4-326e-490c-a4f1-1715d63be7f3”
The internal FQDN for a connection to a SQL Analytics Endpoint would then be the following:
- Workspace GUID
- 6e3676e4-326e-490c-a4f1-1715d63be7f3
- Plus, the “z”
- Appending to the “z” is the first 2 letters
- z6e
- The final FQDN would then be
- kvgqxv4suxzelgptfgnol3t23y-4r3dm3togigetjhqa4k5mo7h6m.z6e.datawarehouse.fabric.microsoft.com
As shown below from the Virtual Machine I have in the VNET I can do an NSLOOKUP to confirm that it is resolved correctly

For the above example of using a SQL Analytics Endpoint it would still need to route via an On-Premises Data Gateway or VNET Data Gateway.
This is because the source is SQL Server which cannot route via a Managed Private Endpoint.
Connecting between Workspaces using Managed Private Endpoint
Once Private Link is enabled because it is now using a private VNET you now must create Managed Private Endpoints (MPE) to communicate between workspaces.
For example, if I have got a Public Workspace with a Semantic Model and I want to query data from a Private Link Workspace, for this to work I would need to create an MPE in the Public Workspace where it is connected to the Private Link Workspace.
To do this I created the MPE in the Public Workspace as shown below

Just to note that in the above image, to create the MPE I had to get the Resource ID from Azure.
Example of Resource ID highlighted below.

Once I created the MPE, it then had to be approved in the pending connections in Azure before it was successfully Activated and Approved.
NOTE: If you wanted to connect to Azure Key Vault, that would need another MPE to be created where it is using the Azure Key Vault Resource ID.
Fully Private Connectivity
If there is a requirement for all data to travel via Private Networks, this must be taken into consideration.
For example, if there is a requirement to get data from AWS S3 and it all must go via private networks, what this means is that the path it would need to travel to do this would be:
Fabric Notebook → Fabric MPE → Azure Private Link Service → Express Route → Megaport → AWS Direct Connect → AWS S3
This adds in extra Azure Configurations and connectivity requirements and something to consider in your design.
Costs
There are additional costs for setting up Private Link Workspace which are attributed to the required items to be created in Azure.
An Azure Virtual Network itself has no base charge, but the components around it may be chargeable. Current Azure list pricing shows a private endpoint hourly charge and data-processing charges. VNET peering is charged for inbound and outbound data at both ends, and VPN Gateway, ExpressRoute, Azure Firewall, NAT Gateway, DNS Resolver and VM’s as an example.
VNET Data Gateway
It is also imported to understand that the running of a VNET Data Gateway has additional costs which are directly attributed to the Fabric Capacity SKU.
For each VNET Data Gateway running it will consume 4 CUs when it is running.
It is critical to understand how many VNET Data Gateways you will need, how long they will be running for etc.
If this is something of interest and how this will potentially impact your capacity let me know as I could run through this a future blog post.
Recommendation to decide on a Workspace Pattern
As shown below this is a recommendation to decide which workspace to be used.
Yes, I did use an LLM to create this image below, it is way better and easy to read that an old school table 😊

Summary
Thanks for reading I hope that you found this useful.
There is a lot of content here and due to working with my customer there are additional considerations and planning to get this implemented successfully.
Any questions or comments are most welcome.