Unable to connect MS Fabric and Azure database for Postgres using copy activity

Hi All,

Thanks for your support , the issue has now been resolved. With the same tech stack, the on-premises data gateway works as expected.

Below is the additional action required:

Microsoft Fabric currently does not support mutual TLS (mTLS) when connecting to PostgreSQL. It only supports standard TLS with username/password authentication and cannot present the client certificate and key required by our mTLS-enabled PgBouncer endpoint. Due to this limitation, Fabric fails during the handshake phase, resulting in the error observed.

To enable Fabric connectivity while preserving our existing security posture, we will proceed with Alternative 1 from our internal analysis:

✅Planned Approach
We will relax mTLS enforcement only for Fabric by setting up a dedicated PgBouncer listener/pool that:

• does not require client certificates,

• is accessible from Fabric’s data gateway public IP range, and IP address of on prem data gateway.

• retains full mTLS enforcement for all other traffic.This approach allows us to maintain strong security controls while ensuring Fabric can connect successfully.