Fabric Snowflake connector returns "Invalid credentials" with Key-Pair despite valid key pair

Hi melsheikh​,

Since the same key works through the Snowflake Python connector, I would try one test connection without the gateway using the same Fabric settings. Microsoft’s Snowflake connector capability matrix confirms that key-pair authentication is supported with an on-premises gateway, so this does not appear to be an unsupported combination.

That test should help isolate the path:

• If the cloud connection succeeds, I would focus on the gateway host, its network route, clock synchronization, and any Snowflake network policy applied to the gateway’s outbound IP.
• If both fail, I would check the exact Snowflake LOGIN_NAME, account hostname, and uploaded private key again.

I would also retrieve the underlying Snowflake login failure rather than relying on Fabric’s generic Invalid credentials message. Snowflake documents how to use SYSTEM$GET_LOGIN_FAILURE_DETAILS in its key-pair authentication troubleshooting guidance, which can help distinguish an account mismatch, login-name mismatch, public-key fingerprint mismatch, invalid signature, or token timing issue.

One detail worth checking on the gateway server is its system clock. Snowflake rejects a JWT when the issue time is too far out, so clock skew can appear as an authentication failure even when the key itself is correct.

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.