ADLSv2 some Shortcuts fails with "Not authorized" message using same connection

[Jarrinf]

I have this "MyLakehouse" Lakehouse with several shortcuts pointing to my Azure Datalake Storage V2 storage, most of my almost 100 shortcuts works pretty fine but there are 4 shortcuts that suddenly fails.

Data source errorCOM error: Azure.Storage.Blobs, Error in Stored Credential Operation - {"error":{"code":"ArtifactConnection_InsufficientPermission","pbi.error":{"code":"ArtifactConnection_InsufficientPermission","details":[{"code":"ArtifactConnection_InsufficientPermission","detail":{"type":1,"value":"User does not have sufficient artifact permission Read to perform the artifact connection operation."}}],"exceptionCulprit":1}}}. Status: 401 (Unauthorized) ErrorCode: Unauthorized Content: <?xml version="1.0" encoding="utf-8"?> <Error> <Code>Unauthorized</Code> <Message>Error in Stored Credential Operation - {"error":{"code":"ArtifactConnection_InsufficientPermission","pbi.error":{"code":"ArtifactConnection_InsufficientPermission","details":

When checking the SQL Endpoint for this fails, I can see this error:

Table name

mae_tiempodia_1

Error code

BadRequest

Error subcode

"Bad Request".. 

Trying to query the table this is the error:

But, other tables in the same storage using same connection works pretty fine.. 

Any idea?

[Murtaza_Ghafoor]

You can also test access by opening the same shortcut paths through the Synapse SQL Endpoint using the same credentials.
If the request returns a Bad Request error, that typically indicates a permission issue on the storage side.

Next, try the “Check Access” feature in Azure Storage Explorer to confirm whether your account or service principal has the required rights for those folders or files.

Finally, it’s a good idea to review the Azure Activity Logs to see if there have been any recent “Deny” entries or access-related events for that storage account.

[v-hjannapu]

Hi @Jarrinf,

Thank you  for reaching out to the Microsoft fabric community forum.

This error usually comes when the user or connection used for the shortcut doesn’t have proper access to the folder in your Azure Data Lake. The message “ArtifactConnection_InsufficientPermission” means the read permission is missing for those particular folders.

Since other shortcuts are working fine, please check if the permissions for these 4 folders are different or if the stored credentials might have expired. Make sure the same user or service principal used in Fabric has Read and List access on those folders.

After fixing the permissions, refresh the shortcut connection and try again. It should start working.

Let me know if you still face the issue after checking this.
Regards,
Community Support Team.

[Jarrinf]

Hello, thanks for your reply.

Folders seems okay, I dropped and create them again, now the shortcuts seems good but the sql endpoint for those tables no.  Look at this:

This is the SQL Endpoint

And this is the shortcut

The error in the endpooint shows an error:

When I try to resync, (using an admin account), it just raise a DatamartUserNotAuthorized message.

[v-hjannapu]

Hi @Jarrinf,
 The error “DatamartsUserNotAuthorized” usually happens when the user doesn’t have the required permission to refresh or manage the SQL endpoint. Please make sure that the account being used has either Contributor or Admin access in the Fabric workspace. If the access is correct, try refreshing the schema from the SQL endpoint once. In some cases, this error can also appear due to a temporary sync issue between the Lakehouse and its SQL endpoint.
If the issue continues, please confirm if there were any recent workspace permission or role changes so we can help check further.

Regards,
Community Support Team.

[Jarrinf]

We still have the problem, I tried by removing and creating again the shortcut.  The shorcut to ADLSv2 works pretty fine but the SQL Endpoint does not.  

When I deleted the shortcut, I noticed that the SQL Endpoing was not deleted.. so I tried to drop it by hand but I cant.. then I created the shortcut.. and again shortcut works but the sql endpoint does not.

Now we are raising a case to MS Support.

[v-hjannapu]

Hello @Jarrinf,
Thanks for the update. Hope your issue gets resolved soon after reaching out to microsoft support. when it does, please share the insights with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Regards,
Community Support Team.