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 read that doc before and according to it I thought it should work. I'm in US East2 and tried F2 and F4 capacity. The PLS and capacity are both in US East2.
According to this it says Private Link Service is an option for Managed Private Endpoint https://learn.microsoft.com/en-us/fabric/security/security-managed-private-endpoints-create#supported-data-sources.
I can create managed pe's for Azure SQL fine. Appears to just be a Private Link Service that gets the error.
I have a PLS configured to a load balancer that routes sql traffic to an onprem sql server through a VM. The PLS works fine in a VM and onprem servers. If this won't work do you suggest anything else I could try to access my onprem sql server in spark? I don't want to use a Pipeline. I already have that working fine with the onprem data gateway. I'm wanting to do this in Spark specifically. Creating a PE to fabric is not an option at the moment due to some of the limitations it defined here: https://learn.microsoft.com/en-us/fabric/security/security-private-links-overview#other-considerations-and-limitations.
HI Digidank,
I check the document of PLS limitations part and find it include one scenario for fabric users:
For Fabric users: On-premises data gateways aren't supported and fail to register when Private Link is enabled. To run the gateway configurator successfully, Private Link must be disabled. Learn more about this scenario. VNet data gateways will work. For more information, see these considerations.
If that is the case, it means the private link service will conflict with on-premises data gateway usages.(based on your description, you already use this on-premise data gateway mapping an on premise source to the azure SQL)
Regards,
Xiaoxin Sheng
I read that doc and understand the limitations of "Private Link" into Fabric. The limitation you mentioned along with others is the reason we cannot enable the Private Link into Fabric and it must remain Public. But, that is not a PLS (Private Link Service).
I think there is some confusion between "Private Link" for Fabric and using a "Private Link Service" as a datasource for a "Managed Private Endpoint".
I am not trying to enable "Private Link" for INBOUND access to Fabric privately. That is documented here: https://learn.microsoft.com/en-us/fabric/security/security-private-links-overview and what the tenant admin setting for "Private Link" is for. I am referring to OUTBOUND using the actual Azure Resource/Service called "Private Link Service" as a datasource for a "Managed Private Endpoint".
I can create a "Managed Private Endpoint" perfectly fine for a private Azure SQL server and already am using it in a spark job. It works great. It is solely adding the specific azure resource called "Private Link Service" that i have a problem doing. “Private Link Service” is not the same thing as "Private Link" in Fabric settings as they are 2 completely different things. "Private Link Service" is really just a service that leverages a load balancer and private link capabilities for private access similar to how Azure SQL, Cosmos, etc do.