Cross Workspace access

[Kryt0n]

I'm trying to test out access control so have created some tables in one workspace and I want to try access them from another. I have created the second workspace and my user has permissions to both of these workspaces, however, when trying to query the table, I get "Invalid object name" error.

The first potential source of issue:

We are running on trial, when I created the second workspace and tried to create the lakehouse, it went through a process of create a trial capacity and once done, gives the message "59 days left" whereas our current trial has 47 days left, should they both be on the same "trial capacity" (whatever the correct terminology is there) and, if so, how do I put them to the same capacity?

[Anonymous · Accepted solution]

Hi @Kryt0n 
Thanks for using Fabric Community.

Currently, directly accessing tables across different workspaces in Microsoft Fabric isn't supported. This means you cannot query a table from one workspace in a notebook or other tool associated with another workspace, even if you have permissions to both.

This limitation exists due to the way Fabric manages data and workspaces. Each workspace acts as a separate container with its own data and configurations. While you can have access to multiple workspaces, data access remains isolated within each workspace.
You cannot directly query the tables from a different workspace. You can however create shortcuts that point to the tables in a different workspace and then query the shortcut.

Hope this helps. Please let me know if you have any further queries.

[Krishana_123]

Can we also consume views created in a warehouse using the Shortcuts directly into the other workspaces if not then any other way around to achieve this.

[Anonymous]

It really helped, Thank you. In our case too we have 2 workspaces and we trying to run a spark streaming job reading delta table1 from workspace-1 to table2 of workspace-2. Like recommended we created shortcut for workspace-1 table1 in workspace-2. so we can  point the input stream of streaming job to the shortcut we created in workspace-2. since it is streaming the new records that are writting to workspace-1 table1 are not automatically refreshed in the shortcut. so, stream is not detecting the data changes. when we click 'refresh' in table section in workspace-2 then the new records are picked up from shortcut we created in workspace-2, even if we query directly against shortcut new records are not shown without hitting refresh button. any suggestion in this streaming case?

[Kryt0n]

Yes, I had implemented shortcuts to solve this