Forum Discussion
Cloud PostreSQL set as without encryption still forces encryption
Hi vojtechsima
Yeah, this is one of those cases where things work differently behind the scenes. Dataflow Gen1 could connect to PostgreSQL without SSL because it didn’t strictly enforce encryption. But when you use Import or DirectQuery in Power BI (outside Dataflow), it goes through the standard PostgreSQL connector and that does require SSL, even if your server allows unencrypted access.
So even though the same connection works in Dataflow, it fails in Import/DirectQuery unless SSL is enabled.
Unfortunately, there’s no official way to bypass that. You’d need to:
-
Enable SSL on the PostgreSQL server
-
Or set up a gateway that allows internal, secured access
References:
https://learn.microsoft.com/en-us/power-query/connectors/postgresqlhttps://community.fabric.microsoft.com/t5/Service/Dataflow-connection-to-PostgreSQL/m-p/4698357
-
Hi vojtechsima
Yeah, this is one of those cases where things work differently behind the scenes. Dataflow Gen1 could connect to PostgreSQL without SSL because it didn’t strictly enforce encryption. But when you use Import or DirectQuery in Power BI (outside Dataflow), it goes through the standard PostgreSQL connector and that does require SSL, even if your server allows unencrypted access.
So even though the same connection works in Dataflow, it fails in Import/DirectQuery unless SSL is enabled.
Unfortunately, there’s no official way to bypass that. You’d need to:
-
Enable SSL on the PostgreSQL server
-
Or set up a gateway that allows internal, secured access
References:
https://learn.microsoft.com/en-us/power-query/connectors/postgresql
https://community.fabric.microsoft.com/t5/Service/Dataflow-connection-to-PostgreSQL/m-p/4698357
rohit1991 all right, thanks.
