Fabric Workspace Private Link enabling issue on workspace

Question

Fabric Workspace Private Link enabling issue on workspace

ajithgeenukunta 20

We created a Private Link Service (PLS) using a custom deployment and then configured a Private Endpoint for the Fabric workspace, following the Microsoft documentation.

However, when attempting to enable Workspace-level Inbound Networking (Selected Networks + Workspace Private Links) on the Fabric workspace, we receive the following error:

{
 "errorCode": "InboundRestrictionNotEligible",
 "message": "The workspace might contain unsupported items, or the tenant-level setting 'Configure workspace-level inbound network rules' might be disabled."
}

We have already verified that the tenant-level setting "Configure workspace-level inbound network rules" is enabled. Despite this, the workspace continues to return the above error when enabling workspace-level inbound networking.

Could you help us determine whether there are any additional prerequisites, unsupported workspace items, or configuration requirements that could be causing this issue?

User's image

0 comments

2 answers

Your answer

Answer 1

Gérard Oomens 131.8K Volunteer Moderator

Post/ask in the Fabric community:

https://community.fabric.microsoft.com/

0 comments

Answer 2

For InboundRestrictionNotEligible just the tenant setting alone is not sufficient but you have to check whether the workspace is on a Fabric F SKU and not a Trial/P SKU. Also check that whether "unsupported items" in the workspace are attached to a "Deployment Pipeline"

Check by re-registering the Microsoft.Fabric resource provider in the Azure subscription because sometimes the resource provider isn't registered. Check that the PLS must use the exact Fabric workspace ID and tenant ID.

Check that the Private Endpoint should target Microsoft.Fabric/privateLinkServicesForFabric with the sub resource workspace

Allow ~15 minutes for propagation if the tenant setting was recently enabled.

To diagnose properly, create an empty F-SKU workspace and try by enabling inbound networking. If it works fine then it means that the original workspace may have an unsupported configuration/item. If it doesn't work then check the tenant/PLS configuration.

You can check the resource: https://learn.microsoft.com/en-us/fabric/security/security-workspace-level-private-links-set-up