Forum Discussion
InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint"
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'm having the exact same problem.
I've created a PLS in region Sweden, but get InvalidRequest when trying to add it as Managed Private endpoint in Fabric. I've tried both with my Trial capacity in region North Europe, and with a WS connected to a F2 capacity in region Sweden.
Also tried changing the Visibility on the PLS to "Anyone with your alias". But still same error no matter.
Sounds like we are both struggling with the same thing. My ongoing support ticket with PowerBI/Fabric support keeps saying that "Private Link" in admin tenant settings needs to be enabled, which is for enabling private access into Fabric. But they also keep referring me to documentation about creating a PL into Fabric, which is not what I am trying to do. So, I really do not think that is the issue. Seems like support cannot differentiate PL for Fabric vs a PLS.
Are you able to try enabling "Private Link" in your Tenant Admin settings? Our PowerBI admins will not enable it because some of the limitations defined here: https://learn.microsoft.com/en-us/fabric/security/security-private-links-overview#other-considerations-and-limitations
I am going to try on my personal Azure account later today when i get a chance. I just want to rule that out.
I've tried now to enable Private Link under Tenant Admin settings, waited 30 min, but still get the same error.
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.
Most recent update:
Hello Josh,Hope you are doing well!
The Product team has informed us that currently, there is no estimated time of arrival (ETA) for updating of the Document. There's a possibility we might receive an update on the ETA by the end of this month, but this is a provisional internal timeline and not guaranteed. Once the ETA is established, the public documentation will be updated accordingly.
Please let me know if you have any other concerns. Based on your response we will proceed with the case.
Thanks for trying! I too tried on my personal tenant with the exact same result. It cannot be the setting. I have forwarded this thread along with my personal tenant requestId to see if they can troubleshoot further. I will be sure to update you if i get anywhere.
I can also confirm that just as you Digidank , I have no problem creating Private Endpoints in Fabric to other Azure services. Just successfully added one to a storage account without problem.
I've also tried to create a spark pool in Synapse in the same Azure tenant as my PLS, and from Synapse, I can successfully connect to my PLS (even manually, using the exact same Resource ID as I'm trying to use from Fabric.
All my attempts from Fabric returns HTTP error 400 (InvalidRequest, pbi.error), regardless if I misstype the servicename or enter the correct servicename.
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.