Fabric to ADLS Gen2 shortcut Error - No Vnet/all roles given still getting login credentials error

[neucharan]

We are encountering an "invalid credentials" error while attempting to create a shortcut to ADLS Gen2 in our Fabric workspace.

We followed the steps outlined in this resource Create an Azure Data Lake Storage Gen2 shortcut - Microsoft Fabric | Microsoft Learn .

The process works fine in our trail account environment. However, in the new workspace, where we created Fabric capacity from the portal and attached it to the Fabric workspace, it throws this error.

I have already have all roles like Storage Blob Owner, Contributor, Reader roles etc . and this storage account is not configured any Vnet.

Any suggestions? @Anonymous @Anonymous 

[Mohan_Fab]

Hi @neucharan 

did you tried to connecting to storage account through SAS and also try to check the validitiy of the account key.

Also, try to create new connection and clear your browser cache. This has resolved my issue. Hope it helps

[AdilH]

@neucharan We have the same issue, did you manage to find a solution for this?

[neucharan]

No still troubleshooting with the Team.

[neuskmgr]

Hi Team,

Support Ticket# 2401180010001450 has been opened with the Fabric Support team.

[Anonymous]

Hi @neucharan ,

Thanks for using Fabric Community.
I would like to know whether you are still facing this issue? And you were able to connect to ADLS Gen2 when using trail account?

[neucharan]

Hi @Anonymous 

Yes we are still getting the error. yes we are able to connect while using the trail account. But once we create Fabric Capacity in actual subscription and created workspace there we were unable to connect.

[Anonymous]

Hi @neucharan ,

Apologies for the issue you have been facing.

This might require a deeper investigation from our engineering team and they can guide you better.

Please go ahead and raise a support ticket to reach our support team:

https://support.fabric.microsoft.com/support
Please provide the ticket number here as we can keep an eye on it.

Hope this is helpful. Please let me know incase of further queries.

[Anonymous]

Hello @neucharan ,

We haven’t heard from you on the last response and was just checking back to see if you got a chance to create a support ticket. If yes, please provide the ticket number here as we can keep an eye on it.