Forum Discussion
Microsoft EmployeePermission requirements for OneLake Shortcuts
The problem is/was: when creating shortcuts to something that points to ADLS2, the current user's permissions are used. In other words: if Alice creates a shortcut from from Lakehouse A to Lakehouse B and Bob uses the shortcut, Bob's permissions will be applied, not Alice's.
This is true all the way down to where the shortcut ultimately points to an external ADLS2 via a connection. At this point, the permissions of the connection will be used (SPN, OAuth, ...).
Microsoft EmployeeThe problem is/was: when creating shortcuts to something that points to ADLS2, the current user's permissions are used. In other words: if Alice creates a shortcut from from Lakehouse A to Lakehouse B and Bob uses the shortcut, Bob's permissions will be applied, not Alice's.
This is true all the way down to where the shortcut ultimately points to an external ADLS2 via a connection. At this point, the permissions of the connection will be used (SPN, OAuth, ...).