Connection to ADLS Gen2 shortcut in Fabric lakehouse using abfss path is failing

[Sreeja_G]

Hi,

I have tried connecting to ADLS Gen 2 path of below format using shortcut with Serive Principal authentication in Lakehouse of Fabric but ended up with the below error. Can you please help me trouble shoot it.

abfss://Filesystem@StorageAccountName.dfs.core.windows.net/

Error - An exception occurred: DataFormat.Error: The Account URL is not a valid URL.

Again I converted the URL into the below https format to see it this work, but ended up with a different error.

https://StorageAccountName.dfs.core.windows.net/Filesystem

Error - Connection could not be created. This may mean it is not accessible from this network or at this URI, or that a gateway is required to access this data source.

Can you please help on this?

[Sreeja_G]

Thanks @Anonymous! Can you help me understand how onpremise gateway or proxy setting or firewall come into picture to connect to Azure storage endpoints Do we need on-premise gateway in this case where I am trying to connect to ADLS Gen2 via shortcut from Fabric lakehouse? Is it related to the source storage account endpoint or is it from Fabric lakehouse that we are trying to connect or is it because of the firewall limitation that source has restricted?

Does VNet omit the dependency of onpremise gateway?

You help in resolving my questions is greatly appreciated!

[Anonymous · Accepted solution]

Hi @Sreeja_G ,

To connect to ADLS Gen2 through the Fabric Lakehouse shortcut, you don't need a local gateway, you can use VNet to connect to ADLS Gen2.

To bring your own ADLS Gen 2 account, you must have permission at the storage account layer. 

Currently not supporting ADLS Gen2 Storage Accounts behind a firewall.

Below is the official link will help you:

Configuring dataflow storage to use Azure Data Lake Gen 2 - Power BI | Microsoft Learn

Use virtual network (VNet) data gateway and data sources in Power BI | Microsoft Learn

Best Regards,

Xianda Tang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Hi @Sreeja_G ,

The error "Connection could not be created. This may mean it is not accessible from this network or at this URI, or that a gateway is required to access this data source" essentially tells us that there is no network connection or that a gateway configuration is required.

When you create a dataflow using a gateway, you might need to change some of your proxy settings or firewall ports to successfully connect to your Azure data lake. If a dataflow fails with a gateway-bound refresh, it might be due to a firewall or proxy issue on the gateway to the Azure storage endpoints.

If you're using a proxy with your gateway, you might need to configure the Microsoft.Mashup.Container.NetFX45.exe.config file in the on-premises data gateway.

Below is the official link will help you:

Azure Data Lake Storage Gen2 - Power Query | Microsoft Learn

Configure proxy settings for the on-premises data gateway | Microsoft Learn

Best Regards,

Xianda Tang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.