Fabric - Content of Directory on Path ... Cannot Be Listed

[ScottSF]

We have an SAP replication tool delivering data into a blob container which is then meant to be copied into a bronze schema within our Fabric warehouse. The process fires off a COPY INTO script using Shared Access Signature credential and we immediately get back the following error. If we make typo's in the path or in the SAS we still get the same response and it's almost immediate without any hesitation from a timeout. Our Azure environment is behind our corporate firewall and the storage container has no public access. Stragely enough we had this working previously and not sure what changed or if this error is not reflective of the acutual problem.

Content of directory on path '<removed>/*.snappy.parquet' cannot be listed.

Msg 13807, Level 16, State 1, Code line 1

[v-jianpeng-msft]

Hi, @ScottSF 

If you use a Microsoft Entra login without explicit credentials, make sure that your Microsoft Entra identity can access the files in storage. To access the files, your Microsoft Entra identity must have the Blob Data Reader permission, or permissions to List and Read access control lists (ACL) in ADLS. For more information, see Query fails because file cannot be opened.

If you access storage by using credentials, make sure that your managed identity or SPN has the Data Reader or Contributor role or specific ACL permissions. If you used a shared access signature token, make sure that it has permission and that it hasn't expired.

If you use a SQL login and the function without a data source, make sure that you have a server-level credential that matches the storage URI and has permission to access the storage.

In addition, you can also check the following:

Serverless SQL pool self-help - Azure Synapse Analytics | Microsoft Learn

How to Get Your Question Answered Quickly

Best Regards

Jianpeng Li

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

[ScottSF]

Thank you, but we have verified the Key that is used to generate the SAS is correct and have also tested by creating a new SAS and manually entering the value. I should have mentioned that an earlier part of the process uses the same key to create the files in the container, it's only when Fabric tries to access the container directly that the failure occurs. 

Other thoughts, is it potentially a public IP listed by Microsoft that we are blocking, but these are challenging to track down. It's very confusing because regardless of what we change the error is almost immediate and if it was a firewall issues we would assume it would have to go through a timeout.

[v-jianpeng-msft]

Hi, @ScottSF 

Thank you very much for your reply, if it is a firewall problem, you can follow the steps below to solve it:

Configure Azure Storage firewalls and virtual networks | Microsoft Learn

Here are a few related articles that will help you fix your firewall issues:

Storage configuration for external table is not accessible while query on Serverless - Microsoft Com...

Synapse Studio error while trying to read data from Storage Account using SQL On Demand - Microsoft ...

How to Get Your Question Answered Quickly

Best Regards

Jianpeng Li

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

[ScottSF]

Jianpeng,

Thank you again for the response, but the firewall issue is not at the resource level. Our Azure infrastructure is behind our corporate firewall and it appears that Fabric is unable to function in this configuration for the time being. I have a meeting tomorrow with Microsoft to look at options, but this may just have to wait until it can work with private VNETs.

[v-jianpeng-msft]

Hi, @ScottSF 

Thank you very much for your reply. You can discuss these questions with Microsoft and expect you to solve them.

Best Regards

Jianpeng Li