Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers. Get Fabric certified for FREE! Learn more
Hello everyone, I need some help. From last week, I am guessing due to some update, our automatic updates starting failing, especially all the ones that contains links to Sharepoint. It seems to be something security related to SSL, do anyone else have the same error, or know a way to potentially fix it? Everything was working before and nothing was changed, so we are at a loss here.
Thanks a lot!
{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"SharePoint: Request failed: The request was aborted: Could not create SSL/TLS secure channel."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}}
Hi @Danort123 - This type of error often indicates that there’s been a change in security protocols—either on SharePoint’s side or due to system or Power BI service updates.
Ensure that your environment (Power BI Desktop or Gateway) supports TLS 1.2 or higher, as Microsoft has deprecated earlier versions (TLS 1.0 and 1.1).
To check this, make sure your system is configured to use TLS 1.2 by default. On Windows:
Open Internet Options → Advanced tab.
Under “Security,” check that "Use TLS 1.2" is enabled.
If the update involves connecting to a SharePoint site, verify that the credentials used for the connection are still valid and have the necessary permissions.
Re-authenticate the SharePoint data source in Power BI Service by going to Settings → Datasets → Data source credentials, and re-entering the credentials for the SharePoint connection.
If you're using an On-Premises Data Gateway, you might need to configure it to use TLS 1.2 by default. You can do this by modifying the system registry on the machine where the gateway is installed. Here’s how:
Open the Registry Editor.
Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols.
Ensure that TLS 1.2 is enabled in both the "Client" and "Server" subkeys.
Restart the gateway machine after making changes.
still issue exist, consider using Power Automate to pull SharePoint data into a more accessible location (e.g., an Azure SQL database or a CSV file in a secure storage account), then connect Power BI to this intermediary source instead of SharePoint directly.
Hope this helps.
Proud to be a Super User! | |
Thank you for your answer! It seems indeed that we have issues with the security protocols, but we still did not manage to make it work. We tried your solution with the registry and the gateway failed. We'll keep working on it.
Check out the April 2025 Power BI update to learn about new features.
Explore and share Fabric Notebooks to boost Power BI insights in the new community notebooks gallery.
User | Count |
---|---|
29 | |
25 | |
19 | |
15 | |
10 |
User | Count |
---|---|
48 | |
29 | |
22 | |
19 | |
13 |