Read files Lakehouse

Hi Anonymous,

Thanks for the update and the detailed error. The error “The remote name could not be resolved” typically points to a DNS or network access issue when trying to create a One Lake Shortcut to Azure Blob Storage. Here’s a checklist to help resolve it:

Verify Storage Account Accessibility: Open this URL in a browser: https://<your-storage-account>.blob.core.windows.net/

If the page does not load or times out, the storage account is either firewalled or not publicly accessible. Review Firewall Settings in the Azure Portal: Navigate to Storage Account > Networking. Ensure public access is allowed or configure access using a Private Endpoint + Managed VNet (currently in preview for Microsoft Fabric).

Verify Shortcut Configuration: Use only the storage account name and container name in the shortcut dialog do not paste full URLs. Example: Storage account: mystorageacct. Container: my-json-data.

Test DNS Resolution: On your machine, run: 

Resolve-DnsName mystorageacct.blob.core.windows.net

If this fails, Fabric cannot resolve it either, indicating a networking or name resolution issue. Try Different Authentication Methods: Test with both Azure AD (ensure your user or service principal has Storage Blob Data Reader permissions) and account key (ensure the key is valid and access is enabled).

Kindly refer to the below following link for more information:
Set up your Azure Blob Storage connection - Microsoft Fabric | Microsoft Learn

This issue is discussed and resolved in the Fabric Community forum here:
Solved: Dataflow refresh Failed - AzureBlobs failed to get the response

In that thread, users reported the same error and resolved it by addressing firewall/network restrictions and DNS accessibility.

If your storage account is private or behind a firewall, try temporarily enabling public access to test the shortcut creation. If it works, then move forward with setting up secure access using private endpoints or managed networks.

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

Thank you for using Microsoft Community Forum.