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.
HI Digidank ,
Sorry it seems like I confused the Azure private link service and private links. For your scenario, perhaps you can open a ticket on support page to contact the Dev team to ensure if managed Private Endpoint supports azure private link service.
Microsoft Fabric Support and Status | Microsoft Fabric
Regards,
Xiaoxin Sheng
No worries Anonymous! I have an open ticket i've been going back and forth on. Will be doing a teams/screensharing call today with support. I will be sure to keep updating this as i get more info.