Forum Discussion
DataSource.Error: AzureBlobs failed to get the response: 'The underlying connection was closed
I cannot add any dataflow as a data source and this only happend to me. My colleagues are able to add dataflows I created as normal. I can still do direct query.
DataSource.Error: AzureBlobs failed to get the response: 'The underlying connection was closed: An unexpected error occurred on a send.'.
Details:
DataSourceKind=PowerPlatformDataflows
DataSourcePath=PowerPlatformDataflows
DataSourceKind.2=AzureBlobs
Hi ShuyingYin99,
This error, DataSource.Error: AzureBlobs failed to get the response: The underlying connection was closed: An unexpected error occurred on a send”, when adding Power Platform Dataflows as a data source, usually indicates a client-side connectivity issue rather than a problem with the dataflow itself. This is especially likely since others can connect without issue and DirectQuery is still working. Common causes include TLS configuration, network restrictions, an outdated Power BI Desktop version, or corrupted local credentials that block communication with the Azure Blob Storage endpoint used by dataflows.
To troubleshoot, make sure Power BI Desktop is up to date and that TLS 1.2 is enabled in your Internet Options, as Azure Storage requires secure protocols. Also, check that no corporate proxy, firewall, or VPN is blocking endpoints like *.blob.core.windows.net, *.dfs.core.windows.net, *.powerplatform.com, or *.analysis.windows.net. Clearing cached credentials by going to File -- Options and settings -- Data source settings -- Global permissions -- Clear permissions, then signing out and back in, and restarting Power BI Desktop can also help.
If the problem remains only on your device after these steps, it likely points to a local configuration or network policy issue. In that case, capturing Power BI Desktop logs and consulting with your IT or network team is recommended.
Thank you.
3 Replies
Hi ShuyingYin99,
This error, DataSource.Error: AzureBlobs failed to get the response: The underlying connection was closed: An unexpected error occurred on a send”, when adding Power Platform Dataflows as a data source, usually indicates a client-side connectivity issue rather than a problem with the dataflow itself. This is especially likely since others can connect without issue and DirectQuery is still working. Common causes include TLS configuration, network restrictions, an outdated Power BI Desktop version, or corrupted local credentials that block communication with the Azure Blob Storage endpoint used by dataflows.
To troubleshoot, make sure Power BI Desktop is up to date and that TLS 1.2 is enabled in your Internet Options, as Azure Storage requires secure protocols. Also, check that no corporate proxy, firewall, or VPN is blocking endpoints like *.blob.core.windows.net, *.dfs.core.windows.net, *.powerplatform.com, or *.analysis.windows.net. Clearing cached credentials by going to File -- Options and settings -- Data source settings -- Global permissions -- Clear permissions, then signing out and back in, and restarting Power BI Desktop can also help.
If the problem remains only on your device after these steps, it likely points to a local configuration or network policy issue. In that case, capturing Power BI Desktop logs and consulting with your IT or network team is recommended.
Thank you.
Hi ShuyingYin99,
we haven't heard back from you regarding our last response and wanted to check if your issue has been resolved.
Should you have any further questions, feel free to reach out.
Thank you for being a part of the Microsoft Fabric Community Forum!Hi ShuyingYin99,
I wanted to follow up on our previous suggestions regarding the issue. We would love to hear back from you to ensure we can assist you further.
Thank you.