topic Re: How to create lakehouse shortcut on publicly accessible ADLS gen2 account in Data Engineering

How to create lakehouse shortcut on publicly accessible ADLS gen2 account

Sachin_Janani — Wed, 21 May 2025 10:17:28 GMT

I have to create shortcut to publicly accessible ADLS gen2 storage account. i have to create lakehouse shortcut but i didnt find option to provice anonymous access

Re: How to create lakehouse shortcut on publicly accessible ADLS gen2 account

v-veshwara-msft — Thu, 22 May 2025 05:05:39 GMT

Hi Sachin_Janani ,
Thanks for reaching out to Microsoft Fabric Community.

Currently, creating a Lakehouse shortcut to a publicly accessible ADLS Gen2 container using anonymous access is not supported in Fabric. The shortcut creation UI supports authentication through Azure AD, account key, SAS token, service principal, or workspace identity, but does not offer an option for anonymous access.

Unify data sources with OneLake shortcuts - Microsoft Fabric | Microsoft Learn

As a workaround, if the container is publicly accessible, you can generate a SAS token with read permissions and use the SAS authentication option while creating the shortcut. You can refer to this document on how to create a shortcut to ADLS Gen2 in Fabric.

Alternatively, you can download the public data using tools like Azure Storage Explorer, Power BI, or scripts, and then upload it into your Lakehouse.

Hope this helps. Please reach out for further assistance.
If this post helps, then please consider to give a kudos and Accept as the solution to help the other members find it more quickly.

Thank you.

Re: How to create lakehouse shortcut on publicly accessible ADLS gen2 account

Sachin_Janani — Thu, 22 May 2025 07:13:53 GMT

Is it possible to create SAS token for a container with large expiry of more that 1 year?

Re: How to create lakehouse shortcut on publicly accessible ADLS gen2 account

v-veshwara-msft — Thu, 22 May 2025 08:49:01 GMT

Thanks for getting back.

Yes, if you're using a Service SAS (i.e., a SAS token signed using the storage account key), you can set an expiry duration of more than one year. Azure does not enforce a maximum expiry limit for Service SAS tokens. However, it's recommended to follow best practices by configuring a reasonable expiration policy to reduce potential security risks.

You can refer to the official documentation here for more details:

Account key Expiry Details

Configure an expiration policy for shared access signatures (SAS) - Azure Storage | Microsoft Learn

Re: How to create lakehouse shortcut on publicly accessible ADLS gen2 account

rayalwarkamal — Thu, 22 May 2025 09:00:27 GMT

Hi Sachin_Janani Yes, it is technically possible to create a SAS token with an expiry longer than 1 year, but whether you can actually do it depends on the method and configuration you use
Account SAS or Service SAS (via storage account key)

Max expiry: No official limit you can set it for multiple years.
Commonly used for scenarios needing long-lived access.
Yes, this can be used for tokens valid 1 year or longer.

Example: You can generate a SAS that expires in 2030 if you want.

If you found this post helpful, please consider giving it a kudos and marking it as the accepted solution to help others find it more easily.