Forum Discussion

heiko_heuser's avatar
heiko_heuser
Regular Visitor
1 year ago
Solved

Data provisioning to external service providers

Hello Fabric Community,


I am currently working on building a central data platform in Fabric for my company.

 

In a specific use case, I now have the challenge of providing data in Fabric (Onelake Lakehouse / Semantic Model) for an external service provider. As far as I know, the service provider uses Azure resources (tenant of the service provider, not ours) to train ML models with our data. The data should be able to be pulled by the provider, not pushed by us.


Now the question: What options do I have to provide the data? Which interface makes sense here? What is your recommendation in terms of security (data is confidential) and simplicity of implementation?

 

  • v-aatheeque's avatar
    v-aatheeque
    1 year ago

    Hi heiko_heuser 

    Best Practices for Sharing Fabric Data with External Tenants :

    When tenant-wide public access is disabled, you can still share specific data externally using controlled mechanisms.

    • you can use OneLake shortcuts to share the data.


    As of now, workspace-level public access settings are not available. All external sharing is governed at the tenant level, and Microsoft has not announced granular workspace-level overrides.

    Hope this helps !!

     

    Thank You.

     

5 Replies

    • v-aatheeque's avatar
      v-aatheeque
      Community Support

      Hi heiko_heuser 

      Just following up on your question regarding secure data sharing from Fabric (OneLake Lakehouse/Semantic Model) with an external service provider using Azure resources.

       

      lbendlin  shared some possible approaches along with official documentation just wanted to check if you had a chance to review those suggestions. 

      Were they helpful in addressing your use case, or is there anything you’re still unsure about in terms of interface selection, security, or ease of implementation?

       

      We’d be happy to assist further if needed just let us know!

  • heiko_heuser's avatar
    heiko_heuser
    Regular Visitor

    Hello everyone,

    yes, that definitely helped. We checked the setting again to make sure it is disabled. 🙂

     

    However, I am still looking for best practices that describe how to make specific data in fabric publicly available even though the tenant-wide setting is disabled. For example, is the best way to do this via function app?

     

    In addition, the question arose internally as to whether such a global setting for public access is also planned at the workspace level in the future. Does anyone have any information on this?

     

    In any case, many thanks so far to lbendlin 

     

    Regards

    Heiko

    • v-aatheeque's avatar
      v-aatheeque
      Community Support

      Hi heiko_heuser 

      Best Practices for Sharing Fabric Data with External Tenants :

      When tenant-wide public access is disabled, you can still share specific data externally using controlled mechanisms.

      • you can use OneLake shortcuts to share the data.


      As of now, workspace-level public access settings are not available. All external sharing is governed at the tenant level, and Microsoft has not announced granular workspace-level overrides.

      Hope this helps !!

       

      Thank You.

       

      • v-aatheeque's avatar
        v-aatheeque
        Community Support

        Hi heiko_heuser 

        Just a quick reminder that we have already provided guidance on this earlier, regarding best practices for sharing Fabric data externally when tenant-wide public access is disabled.

        To recap:

        • OneLake shortcuts are a recommended approach for controlled external data sharing.

        • Workspace-level public access settings are currently not available, and all such configurations remain at the tenant level.

        • For future updates, we recommend monitoring the official Fabric roadmap: https://roadmap.fabric.microsoft.com/

        Let us know if you have any new scenarios or need further clarification beyond what’s already addressed.