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.
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.
- Digidank2 years agoHelper I
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.
- Digidank2 years agoHelper I
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.
- msundman782 years agoRegular Visitor
Thanks for the update, Josh.
Do they mean that they might get back with an ETA when documentation is updated to clearly say PLS is *not* supported, or do they mean they might get back with an ETA when it *will be* supported?
I've also opened a support ticket, which first came back with the same suggestion to enable Private Link ect. It's now been escalated to "next level", but I assume they will get back with same info as you got, but hopefully it can help raise the priority on the issue if more people report it as a major showstopper.
- Anonymous2 years agoNot applicable
Hi Digidank,
Thanks for sharing these detail information here. I think they will help other user to clarify this scenario.
Regards,
Xiaoxin Sheng
- mikecmpbll1 year agoRegular Visitor
I also assumed that this would work, and I see no way of connecting Fabric to our VNet integrated Azure MySQL without it.
I've created an Ideas submission here, please upvote it! https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=a2c6eb27-727a-ef11-a4e6-000d3a7b101f
- Digidank2 years agoHelper I
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.