Forum Discussion
Helper IInvalidRequest 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.
Helper IThis 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.
Helper IMost 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 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.
After a long discussion with support I finally got the exact same answer as you, that it is currently not supported, and there is no ETA when it will be available.
So, I can just conclude that Fabric is not production ready yet for customers that needs connectivity from Spark notebooks to on-prem services/systems, which is a pity.
Our current work-around is to use local python scripts executing on the on-prem data-gateway server that produces CSV files in a local folder that can then copied to OneLake via a Fabric Pipeline, and later processed by Fabric Spark Notebooks.
- Digidank
Yeah it is very unfortunate. I have been using a small compute cluster in Databricks to write as a delta table to an ADLSv2 storage account. Then created a shortcut in Fabric to read it. Was my fastest solution so far. It was my first time working with Databricks and it was extremely simple to get running with onprem access. Hopefully the Fabric team gets this sorted out soon.
- Digidank
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.
dbeavon3Memorable Member
Digidank
Do you have a ticket open? DId they update the docs to say that PLS is not supported?
The docs are pretty poor. The only relevant thing I can find is like so:Creating a managed private endpoint with a fully qualified domain name (FQDN) is not supported. These limitations and considerations might affect your use cases and workflows. Take them into account
This doesn't specifically talk about PLS, but the FQDN part is often a show-stopper for PLS.- dbeavon3
I found a full list of supported connections via MPE, and private-link service is not one of them:
I can say from my past experience (in Synapse) that it took far longer then I thought it would to add support for MPE's to private link service. I think we were talking to Microsoft for almost 18 months before they finally added MPE's to PLS. The additional complexity (compared to other types of data sources) is very minimal, eg. the ability to specify FQDN's. I think the folks who are the biggest bottlenecks are the ones writing the U/I interactions. Perhaps we should be asking for a REST API to manage our MPE's and that might allow us to get to the finish line a lot sooner, without placing a dependency on any of the front-end web developers. - dbeavon3
Not sure if anyone else has tried to create a PLS private endpoint by going around the back door. But it doesn't work, from what I've tried. Image:
I've been able to create PE requests for blob and other resources, but it never succeeds when I try to create one for PLS, with a blank group ID and a FQDN. I think we are at the mercy of whatever team is sitting on this request.
IMO, It seems like a pretty basic requirement. Private link service is a pretty fundamental component in azure nowadays, and was intended to be used for precisely this sort of scenario.
Again, it took the Synapse team about a year to create the U/I that allows this PLS connectivity to work, and I am guessing the Fabric team will take the same a similar amount of time. It would be nice if they could give a "back-door" approach that circumvents the U/I, as a temporary solution. For some reason U/I teams in the cloud seem to be extremely slow at what they do. Back-door options include a REST api, or powershell command or similar.- dbeavon3
Wahted to re-iterate that a pipeline activity "copy activity" might be the best way to work around the missing PLS. Ie. you have to go thru a round-about approach that sends the data from a service thru an ADLS storage account (temp files) before it is accessible from Fabric.
This unfortunately can cost more money, and has more moving parts (on premise gateway).
More details on reddit:
https://www.reddit.com/r/MicrosoftFabric/comments/1er2z51/invalidrequest_when_adding_a_private_link_service/
