Share warehouse/lakehouse between Workspaces

[RajeshKapur]

Hi All,

We have a situation in our project where we have DataPipelines and Lakehouse/Warehouse in Workspace A. Now for each departments we have different workspaces say WorkspaceDeptA,WorkspaceDeptB,WorkspaceDeptC. All the users wants to access the data stored in Workspace A without having access to Workspace A.

Could you please let me know the best possible way to do the same. I have tested this with creating Fabric Shortcut option for lakehouse and that seems to be working fine, apart from issue that we need to select table by table which we want to share. So do let us know if we can share the tables by checking the dbo of Warehouse in Workspace A only.

Also we want to perform this operation with the help of devops pipeline, do let us know if that is also possible or not. I tried checking the JSON of the lakehouse in WorkspaceB from where we have created the shortcut but that seems to be blank so no idea how to automate this.

Thanks,

Rajesh Kapur

[v-huijiey-msft]

Hi @RajeshKapur ,

Is my follow-up just to ask if the problem has been solved?

If so, can you accept the correct answer as a solution or share your solution to help other members find it faster?

Thank you very much for your cooperation!

Best Regards,
Yang
Community Support Team

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

[v-huijiey-msft · Accepted solution]

Hi @RajeshKapur ,

Thanks for the reply from DataBard .

You can use the Deployment pipeline to deploy the data you need to share in WorkspaceDeptA (e.g. lakehouse, warehouse) to WorkspaceDeptB, WorkspaceDeptC.

This approach enables data sharing without opening up access to Workspace A to all users.

For more information about the Deployment pipeline, please refer to the official documentation below:

Get started using deployment pipelines, the Fabric Application lifecycle management (ALM) tool - Mic...

If you have any other questions please feel free to contact me.

Best Regards,
Yang
Community Support Team

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

[DataBard]

Hi @RajeshKapur,

For lakehouses, Shortcuts would be the recommended approach. Yes you do have to select what to shortcut table-by-table, but it's a more efficient approach than having to write a process to do the same.

For warehouses, it depends on what destination you want to go to.

• Lakehouse? Under tables, you can see a schema shortcut option. This would let you select a schema and shortcut all tables in the schema.
• 
• Warehouse? You can't shortcut per se, but within a warehouse, you can hit the plus sign in a warehouse to add a connection to another warehouse. It's not technically a shortcut (assuming you have access, you would be able to modify data/objects in the source), but it's an option depending on your use case. I haven't looked at this yet from the lens of security, so testing would be needed to assess whether this approach persists security or not.
• 

As to your question about devops pipeline, are you looking to deploy warehouses/lakehouses that have the shortcuts defined? If so, in my testing, shortcuts in lakehouses and warehouses are not retained. You would have to set the shortcuts up again in each workspace.

Once you have your answer, be sure to select it so others in the community can learn from it.