topic Re: InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint& in Data Engineering

InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint"

Digidank — Mon, 05 Aug 2024 18:16:53 GMT

I get a simple error saying "InvalidRequest" when i try to add my Private Link Service as a Managed Private Endpoint in the Workspace Setttings Network Security page. I can add others fine like a PE for my Azure SQL server. It just seems to be an issue with "Private Link Service" specifically. Is this possibly a bug with adding PLS as a Managed Private Endpoint?

Re: InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint&

Anonymous — Tue, 06 Aug 2024 01:01:48 GMT

Hi @Digidank,

What type of capacity are you worked? Trial or fabric capacity? Which region are you host to configure the private link service? Please share some more detail information about these.

BTW, the document mentioned some of regions not support PLS feature, perhaps you can take a look at the following link to know more about these:

Overview of managed private endpoints for Microsoft Fabric - Microsoft Fabric | Microsoft Learn

Regards,

Xiaoxin Sheng

Re: InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint&

Digidank — Tue, 06 Aug 2024 03:08:55 GMT

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.

Re: InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint&

Anonymous — Wed, 07 Aug 2024 09:05:19 GMT

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

Re: InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint&

Digidank — Wed, 07 Aug 2024 13:59:05 GMT

Yeah, I read that in the documentation as well. That was why i was saying we cannot use it.

However, 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 Azure resource called "Private Link Service" as a datasource for a "Managed Private Endpoint" documented here: https://learn.microsoft.com/en-us/fabric/security/security-managed-private-endpoints-create.

I can create "Managed Private Endpoint" perfectly fine for Azure SQL and already am using it in a spark job. It works great. It is solely adding the specific azure resource called "Private Link Service". "Private Link Service" is not the same thing as "Private Link" in Fabric settings as they are 2 completely different things.

Re: InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint&

Digidank — Wed, 07 Aug 2024 14:39:40 GMT

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.

Re: InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint&

msundman78 — Wed, 07 Aug 2024 15:21:51 GMT

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.

Re: InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint&

Digidank — Wed, 07 Aug 2024 15:41:12 GMT

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.

Re: InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint&

msundman78 — Wed, 07 Aug 2024 16:29:46 GMT

I've tried now to enable Private Link under Tenant Admin settings, waited 30 min, but still get the same error.

Re: InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint&

msundman78 — Wed, 07 Aug 2024 17:33:09 GMT

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.

Re: InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint&

Digidank — Wed, 07 Aug 2024 19:33:40 GMT

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.

Re: InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint&

Anonymous — Thu, 08 Aug 2024 06:37:07 GMT

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

Re: InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint&

Digidank — Thu, 08 Aug 2024 13:45:41 GMT

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.

Re: InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint&

Digidank — Fri, 09 Aug 2024 18:56:16 GMT

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.

Re: InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint&

Digidank — Mon, 12 Aug 2024 19:57:18 GMT

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.

Re: InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint&

msundman78 — Mon, 12 Aug 2024 20:07:02 GMT

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.

Re: InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint&

Digidank — Mon, 12 Aug 2024 20:16:24 GMT

From my understanding this is entirely about an ETA updating the documentation and nothing to do with an ETA to actaully solve it. I am responding asking for that clarification though.

I hope you get further than I have! Let me know if you get any better news please.

Re: InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint&

kthr — Tue, 13 Aug 2024 13:10:36 GMT

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.

Re: InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint&

msundman78 — Tue, 13 Aug 2024 13:40:01 GMT

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?

Re: InvalidRequest when adding "Private Link Service" as a "Managed Private Endpoint&

Anonymous — Thu, 15 Aug 2024 01:29:32 GMT

Hi @Digidank,

Thanks for sharing these detail information here. I think they will help other user to clarify this scenario.

Regards,

Xiaoxin Sheng