Forum Discussion
Power BI Dataflow Failing Every 1 Minute - Azure Blob Storage Connection Error
Problem: Our Power BI dataflow keeps failing to refresh every 1 minute with timeout errors. We've checked the gateway and SQL connections - both are online and working. We can successfully connect to the SQL database from the gateway server, but the dataflow still fails.
Error Message:
GatewayPipelineErrorCode=DM_GWPipeline_Gateway_MashupDataAccessErrorInnerMessage=<pi>AzureBlobs failed to get the response: 'The underlying connection was closed: An unexpected error occurred on a send.'.</pi>
What We've Tried:
- Verified gateway is online and running
- Verified SQL database connections work fine from gateway server
- Checked connection credentials - all valid
- Reviewed error logs - only showing generic timeout/connection closed errors
Current Understanding:
- The issue appears to be with the gateway's connection to Azure Blob Storage (where Power BI stores dataflow data), NOT with the SQL Server connection
- The error "underlying connection was closed" typically indicates a TLS/SSL handshake failure
- Power BI dataflows store data in Azure Blob Storage behind the scenes, which requires TLS 1.2
- The gateway server may be using an older TLS version (1.0 or 1.1) that Azure no longer accepts
Questions
- Are there any other causes for "AzureBlobs failed to get the response" errors besides TLS issues?
Environment:
- On-premises data gateway
- Power BI dataflows connecting to SQL Server
- Gateway can connect to SQL Server successfully
- Fails when trying to write results to Azure Blob Storage
Additional Context: We initially thought this was a SQL query timeout issue, but the error specifically mentions Azure Blobs, not SQL Server. The failure happens consistently every 1 minute, suggesting a connection-level issue rather than a query performance problem.
Any help would be greatly appreciated!
Hi Anonymous , Thank you for reaching out to the Microsoft Community Forum.
Given that the connection to SQL Server works fine, this suggests the problem is not with the SQL connection but specifically with the Azure Blob Storage connection. Azure requires TLS 1.2 for secure communication and if your gateway is still using an older TLS version (like TLS 1.0 or 1.1), this would cause the error. Check that the On-Premises Data Gateway is using TLS 1.2. If your system is outdated, it may still be defaulting to an unsupported TLS version.
Also, verify that the gateway has the necessary permissions to write to Azure Blob Storage. It’s possible that the credentials or roles assigned to the gateway don’t allow it to successfully store data. Ensure that the gateway has appropriate storage permissions such as Storage Blob Data Contributor.
In addition, consider checking your network configuration. The issue could stem from network related problems, like firewall settings or proxy configurations, that prevent stable communication between the gateway and Azure services. Ensure that outbound traffic on port 443 is open and the gateway can reach Azure Blob Storage without restriction.
Troubleshoot the on-premises data gateway | Microsoft Learn
Adjust communication settings for the on-premises data gateway | Microsoft Learn
On-premises data gateway in-depth - Power BI | Microsoft Learn
3 Replies
v-hashadapuCommunity Support
Hi Anonymous , Thank you for reaching out to the Microsoft Community Forum.
Given that the connection to SQL Server works fine, this suggests the problem is not with the SQL connection but specifically with the Azure Blob Storage connection. Azure requires TLS 1.2 for secure communication and if your gateway is still using an older TLS version (like TLS 1.0 or 1.1), this would cause the error. Check that the On-Premises Data Gateway is using TLS 1.2. If your system is outdated, it may still be defaulting to an unsupported TLS version.
Also, verify that the gateway has the necessary permissions to write to Azure Blob Storage. It’s possible that the credentials or roles assigned to the gateway don’t allow it to successfully store data. Ensure that the gateway has appropriate storage permissions such as Storage Blob Data Contributor.
In addition, consider checking your network configuration. The issue could stem from network related problems, like firewall settings or proxy configurations, that prevent stable communication between the gateway and Azure services. Ensure that outbound traffic on port 443 is open and the gateway can reach Azure Blob Storage without restriction.
Troubleshoot the on-premises data gateway | Microsoft Learn
Adjust communication settings for the on-premises data gateway | Microsoft Learn
On-premises data gateway in-depth - Power BI | Microsoft Learn
- v-hashadapu
Hi Anonymous , Hope you're doing okay! May we know if it worked for you, or are you still experiencing difficulties? Let us know — your feedback can really help others in the same situation.
- v-hashadapu
Hi Anonymous , Hope you're doing fine. Can you confirm if the problem is solved or still persists? Sharing your details will help others in the community.