AzureBlobs failed to get the response: 'The underlying connection was closed: Could not establish

[TorresJA]

HI everyone:

I hope you are doing well. I have installed and configured the On-premises data gateway, but whenever I try to refresh any Dataflow, the status shows as failed. I checked the logs and found the following message:
Non-gateway exception encountered in activity scope: Microsoft.Data.Mashup.MashupValueException (0x80004005): AzureBlobs failed to get the response: 'The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.'.

Could you help me please?

[v-tsaipranay]

Hi @TorresJA ,

Thank you for reaching out to the Microsoft Fabric Community

As highlighted by @Nasif_Azam , the issue is likely due to a certificate trust or TLS configuration problem on the gateway machine. Please verify SSL certificate trust, enforce TLS 1.2 via registry, and ensure your gateway is up to date and correctly mapped in the Dataflow settings.

For more details, you can also refer to this doc: Install an on-premises data gateway | Microsoft Learn

Hope this helps. Please reach out for further assistance.

If this post helps, then please consider to Accept as the solution to help the other members find it more quickly and a kudos would be appreciated.

Thank you.

[Nasif_Azam]

Hey @TorresJA ,

The error message typically indicates a certificate trust issue between your on-premises data gateway and Azure services like Azure Blob Storage. It occurs may: 

1. Invalid or Untrusted Root Certificates

2. Outdated TLS Version Support

3. Interception by Antivirus/Firewall

4. Missing Gateway Configuration or Mismatch

Solutions

1. Check the SSL/TLS Certificate Trust Chain

• Open a browser on the gateway machine.

• Go to the Blob Storage URL you're trying to connect to (e.g., https://<yourstorageaccount>.blob.core.windows.net).

• See if it loads without certificate errors.

• If it doesn’t, install the missing intermediate/root certificates.

2. Force TLS 1.2 Support (Windows Registry)

Make sure your OS is using TLS 1.2 by default:

• Open regedit and navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319

• Add or update these DWORD values:

  SchUseStrongCrypto = 1
  SystemDefaultTlsVersions = 1

• Repeat the same under: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319
• Then reboot your system.

3. Update Gateway and OS

• Make sure you’re running the latest version of the On-premises Data Gateway.

• Update Windows, especially the root certificate store.

• If possible, update to the latest .NET Framework runtime.

Verify Dataflow Gateway Usage

In the Power BI Service:

1. Go to the workspace where your Dataflow is.

2. Edit the Dataflow → Check the data source settings.

3. Ensure the gateway is mapped correctly to the source.

If you found this solution helpful, please consider accepting it and giving it a kudos (Like) it’s greatly appreciated and helps others find the solution more easily.

Best Regards,
Nasif Azam