How to get files landed/dropped to OneLake instead of ADLS?

[Madhusudan_P]

Hi,

We currently have a container named 'vendor' in ADLS, where a vendor drops files daily. The vendor has been given access using SAS (Shared Access Signature).

• With the introduction of Microsoft Fabric, we're considering whether this step with ADLS can be replaced by OneLake. Specifically, can we create a container in OneLake and give the vendor access in a similar way to how it's done with ADLS
• Additionally, we're unsure if the Files option within a Lakehouse in Fabric functions the same way as a container does in ADLS. Would it be better to stick with ADLS for the initial file landing and then create a shortcut to Fabric for processing?
• Is OneLake intended to fully replace ADLS?

Looking for advice on whether OneLake can fully replace ADLS for this use case or if a hybrid approach would be more effective.

[FabianSchut · Accepted solution]

Hi @Madhusudan_P,

As of today, it is not possible to give a user Write permissions to a specific folder in OneLake. Therefore, OneLake does not acts the same way as a container in ADLS. Read permission could be set to a specific folder in OneLake (preview), as can be seen here: https://learn.microsoft.com/en-us/fabric/onelake/security/get-started-data-access-roles.

Since your vendor needs Write access, you could consider creating a separate workspace and lakehouse for that vendor that has Write permission to the lakehouse in total. You could then create shortcuts from your other lakehouse to that vendor lakehouse.

Kind regards,

Fabian

[Madhusudan_P]

Hi @FabianSchut ,

Thanks for your input.
Vendor simply transfers parquet file generated from his ETL process into ADLS container. 
I think creating separate workspace and lakehouse for vendor would be overcomplicating.
Seems like staying with ADLS would be best approach.

[Anonymous]

Hi @Madhusudan_P 

Thanks to Fabian for the valuable insights. 

As of now, Files in Lakehouse and containers in ADLS are not exactly the same, with some differences in files management and permission/access management. According to your description, staying with ADLS would be best approach currently. It would be better to stick with ADLS for the initial file landing and then create a shortcut to Fabric for processing. 

Below are some features on the roadmap which you may have interest. What's new and planned for OneLake in Microsoft Fabric - Microsoft Fabric | Microsoft Learn

I believe it will be possible to let OneLake take care of the initial file landing process in the future as this is one of the goals of OneLake. Actually, you can do it now, however, some experience may not be as good as in ADLS. 

Best Regards,
Jing
If this post helps, please Accept it as Solution to help other members find it. Appreciate your Kudos!

[Madhusudan_P]

Thank you @Anonymous, I'll stick with ADLS for the time being. And I hope going next year we would be able to see ADLS features in OneLake.