Access Fabric Lakehouse sql endpoint from different microsoft tenant

[Eric7]

We have two Microsoft tenants, hereby called T1 and T2. In T1 we have a lakehouse. We want to call the T1 lakehouse via the SQL endpoint from a customer accessible api which resides in T2. From our experience it seems not possible to do this directly. Is there any way to accomplish this?

Perhaps this option:

External data sharing (preview): https://blog.fabric.microsoft.com/es/blog/introducing-external-data-sharing-a-new-way-to-collaborate...

But I assume this requires us to create a Fabric capacity for T2, which has a cost.

We could also use a dataflow gen2 in T1 which will read the lakehouse data and write the data down to a sql server database in T2. But this is an extra step to maintain, obviously.

[Anonymous · Accepted solution]

Hi, @Eric7 

As you mentioned, if you're using external data sharing (preview), you'll need to set up fabric capacity for T2, which will incur additional charges.

The use of gen2 that you mentioned is indeed a viable alternative solution. While this does add an extra layer of maintenance, it can act as a bridge until a more straightforward solution becomes available or feasible. This approach ensures cross-tenant access to data while maintaining control over data flows and transformations.

I think you should make the right decision based on your actual situation, such as costs and benefits.

How to Get Your Question Answered Quickly

Best Regards

Jianpeng Li

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.