Semantic model refresh failed - Snowflake Key Pair cloud connection

Hi julsr​,

Based on that specific error, I would investigate the semantic model-to-cloud-connection binding before changing the Snowflake key pair.

Power BI treats the semantic model data source and the shareable cloud connection as separate objects. In the semantic model's Gateway and cloud connections settings, I would verify that the Snowflake source explicitly Maps to the intended shareable cloud connection. Microsoft documents that mapping here: Connect to cloud data sources in Power BI.

The fact that some models refreshed successfully with the same connection while others failed, then recovered without a credential change, makes a permanently invalid key pair less likely. It is more consistent with a transient binding/connection-resolution issue, although I don't think there is enough evidence to call that the confirmed root cause.

I would also verify that the semantic model owner has permission to use the shareable connection and that all affected models are mapped to the same connection object rather than Personal/Default connections.

For Snowflake, Key Pair authentication is supported through the ADBC implementation, so I would not switch authentication methods simply because of this error.

One useful newer option is the Fabric REST API for binding semantic model connections. If these models are deployed or republished regularly, explicitly validating or applying the connection binding after deployment can make that configuration deterministic.

If this happens again while the mapping still shows the correct shareable connection, I would capture the semantic model ID, connection ID, refresh timestamp/request details and raise it with Microsoft Support. I couldn't find a documented known issue for this exact intermittent Key Pair scenario.

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