Confirmation Required – Snowflake Warehouse & Schema Parameter Rules in Power BI Deployment Pipeline

Hi manoj_0911 , Thank you for reaching out to the Microsoft Community Forum.

Yes, your proposed approach is supported, provided that whname and schemaname are Power Query parameters and are exposed for Deployment Pipeline Parameter Rules.

For your first question, Deployment Pipeline Parameter Rules can override Power Query parameter values during deployment. Since your Snowflake connection references the whname parameter in Snowflake.Databases(), the pipeline can apply different warehouse values in each stage. This is commonly used for Snowflake environment switching because deployment pipelines do not provide a dedicated Snowflake data source rule.

Regarding refresh behavior, the deployment rule updates the parameter value in the target stage, but the semantic model must be refreshed before queries run against the new warehouse. Deployment copies metadata and applies rules, but data itself is not copied between stages. A refresh is therefore required after deployment.

For Snowflake connector Implementation="2.0", Microsoft documentation does not list any known restrictions or unsupported scenarios related to Deployment Pipeline Parameter Rules. As long as the warehouse and schema are driven by Power Query parameters, the deployment pipeline should treat them like any other parameterized connection setting.

For Incremental Refresh, changing only the Snowflake warehouse typically changes the compute resource used to execute queries and should not by itself require a full refresh. However, if the deployment also changes the schema, database or underlying source data, I suggest a full refresh after deployment to ensure all partitions are aligned with the target environment.

Create deployment rules for Fabric's ALM - Microsoft Fabric | Microsoft Learn

The Microsoft Fabric deployment pipelines process - Microsoft Fabric | Microsoft Learn

Power Query Snowflake connector - Power Query | Microsoft Learn