Forum Discussion
InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint"
- 2 years ago
This is extremely frustrating. Here is the support response:
Hello Josh,
I hope you are having an amazing day.
We have shared the issue with all collected details in our SME channel. They responded that currently, private endpoints targeting Private Link Service are not supported. Additionally, we do not support creating managed private endpoints with FQDNs at this time and there is no ETA. The product team will add this limitation to public documents once they have an ETA.
I am pleased to inform you that there is no issue from your side; however, the actual feature is not supported currently. We have already created an incident with the product team, and they are working on updating the feature.
I apologize for any inconvenience this may cause. Rest assured, you will be able to access this feature soon.
Please feel free to reach out to me if you have any questions, concerns, or additional information that you would like to share. I'll be more than happy to assist you.
Thank you for your understanding.
I have the same issue. When entering the details in Fabric->Workspace settings->Network Security it passes all input validation. But when I click create, I get "InvalidRequest". I know the target resource is working because I can create a private link from Azure and that works just fine - the request is sent and can be approved just fine. But that doesn't help me connect Fabric to the managed private endpoint.
Are you also trying to create a PE linked to a "Private Link Service", or what backend service type are you trying to connect to?
- kthr2 years agoFrequent Visitor
Sorry for the delay. Yea, the resource type is an Azure "Private Link Service" that I'm trying to connect to with Fabric's private endpoint.