Forum Discussion

Digidank's avatar
Digidank
Icon for Helper I rankHelper I
2 years ago
Solved

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

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...
data engineering
  • Digidank's avatar
    Digidank
    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.

msundman78's avatar
msundman78
Regular Visitor
2 years ago

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

Digidank's avatar
Digidank
Icon for Helper I rankHelper I
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.

  • Digidank's avatar
    Digidank
    Icon for Helper I rankHelper I
    2 years ago

    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.

    • msundman78's avatar
      msundman78
      Regular Visitor
      2 years ago

      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. 

       

      • msundman78's avatar
        msundman78
        Regular Visitor
        2 years ago

        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.

    • dbeavon3's avatar
      dbeavon3
      Icon for Memorable Member rankMemorable Member
      1 year ago

      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:


       


      https://learn.microsoft.com/en-us/fabric/security/security-managed-private-endpoints-overview#limitations-and-considerations

       

      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's avatar
        dbeavon3
        Icon for Memorable Member rankMemorable Member
        1 year ago

        I found a full list of supported connections via MPE, and private-link service is not one of them:

        https://learn.microsoft.com/en-us/fabric/security/security-managed-private-endpoints-create#supported-data-sources



        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.

         

         

         

  • Anonymous's avatar
    Anonymous
    Not applicable
    2 years ago

    Hi Digidank,

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

    Regards,

    Xiaoxin Sheng

  • dbeavon3's avatar
    dbeavon3
    Icon for Memorable Member rankMemorable Member
    1 year ago

    Thank you so much for posting.  I was probably about to waste a month of time with support as well.  Any chance you have a case identifier, like an SR number or ICM number?  I may want to follow-up but don't necessarily want to start from scratch.