Create data destination to a lakehouse within the current tenant

[Deagle]

I want to create a data destination in my Dataflow Gen2 to a lakehouse within my current tenant, however i cannot see the lakehouses within my current tenant, instead i can see only the lakehouses in another tenant. What should I do to be able to connect with lakehouses within my current tenant?

[Hakesh · Accepted solution]

Hii @Deagle 

My stong recomendation is that make sure you have required permissions for the current tenent and the required lakehouse is present in the tenent. or go through the documentation once and explore everything regarding the problem you are facing. 

[v-csrikanth · Accepted solution]

Hi @Deagle 

We haven't heard from you since last response and just wanted to check whether the solution provided has worked for you. If yes, please Accept as Solution to help others benefit in the community.
Thank you.

If the above information is helpful, please give us Kudos and mark the response as Accepted as solution.
Best Regards,
Community Support Team _ C Srikanth.

[Hakesh · Accepted solution]

Hii @Deagle 

My stong recomendation is that make sure you have required permissions for the current tenent and the required lakehouse is present in the tenent. or go through the documentation once and explore everything regarding the problem you are facing. 

[v-csrikanth]

Hi @Deagle  
​If you're unable to see Lakehouses within your current tenant when setting a data destination in Dataflow Gen2, here are some steps you can take to troubleshoot and resolve the issue:

• Ensure you're in the correct workspace that contains the Lakehouse you want to use.

• Confirm you have the necessary permissions to access the Lakehouse in that workspace.

• If you're a guest user from another tenant, note that guest users often cannot set Lakehouses as destinations in Dataflow Gen2 and may see resources from their original tenant instead.

• Try creating the Dataflow Gen2 directly from the Lakehouse interface—this can help properly bind the two.

• Clear your browser cache or use an incognito window to rule out UI caching issues.

If the above information is helpful, please give us Kudos and mark the response as Accepted as solution.
Best Regards,
Community Support Team _ C Srikanth.

[Deagle]

The steps that are mentioned were taken, but somehow it was not worked out. The main issue was about using the tenant from another account as guest, so it does not allow you to access the lakehouses or any other sources. Using the main account and tenant not as a quest allowed me to access all lakehouses. Thanks for the replies.