Linked Service to specific ADLS Gen2 container/filesystem
Is it possible to create a Linked Service in Synapse to a specific container/filesystem in an ADLSg2 account?
The ServicePrincipal I’m connecting with is only authorised on a specific container in the storage account, so I’m unable to link to the storage account itself.
If I ignore the Test Connection warning, I can create the LS, and then create a DS towards a file in the container I have permissions to – that works. However, many users give up when they’re unable to test the LS itself, and it would be very nice to be able to browse the container in the Data pane in Synapse, just like you can browse a whole linked ADLSg2 account.
I was hoping there should be an Advanced JSON parameter to define the container/filesystem on LS level, but I’ve been unable to find any in the documentation.
Is it possible to create a Linked Service in Synapse to a specific container/filesystem in an ADLSg2 account? The ServicePrincipal I’m connecting with is only authorised on a specific container in the storage account, so I’m unable to link to the storage account itself. If I ignore the Test Connection warning, I can create the LS, and then create a DS towards a file in the container I have permissions to – that works. However, many users give up when they’re unable to test the LS itself, and it would be very nice to be able to browse the container in the Data pane in Synapse, just like you can browse a whole linked ADLSg2 account. I was hoping there should be an Advanced JSON parameter to define the container/filesystem on LS level, but I’ve been unable to find any in the documentation. Read More