Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
1 year ago
Solved

Creating Shortcuts With Limited Access in Lakehouse Source

We have a service account that we want to use to create a shortcut from Lakehouse Source, located in Workspace Source, to Lakehouse Target, located in Workspace Target. The admin of Workspace Source ...
data engineering
lakehouse
  • v-veshwara-msft's avatar
    v-veshwara-msft
    1 year ago

    Hi Anonymous ,
    Just wanted to check if the response provided was helpful. If further assistance is needed, please reach out.
    Thank you.

v-veshwara-msft's avatar
v-veshwara-msft
Community Support
1 year ago

Hi Anonymous ,
Just wanted to check if the response provided was helpful. If further assistance is needed, please reach out.
Thank you.

Anonymous's avatar
Anonymous
Not applicable
1 year ago

Hi all,

Thanks for the input so far.

Just to clarify a couple of points:

  • Requiring ReadAll on the source Lakehouse defeats the purpose of restricting access to specific tables. It grants visibility into all metadata and objects, which goes against the goal of least-privilege access.

  • Regarding shortcut placement: I believe there was a misunderstanding. I wasn’t referring to creating a shortcut in a subfolder under Files, but rather within a schema (e.g. dbo) in the Tables section. Schemas and subfolders are not the same, schemas are logical groupings within Tables, supported in preview. So the “must be at the top level of Tables” statement likely stems from confusing these two.

If shortcuts can’t support scoped access or respect schema-level targeting, I’ll consider alternative items like data pipelines or copy jobs.

Thanks