Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
We need your help in resolving an issue with our deployment pipeline. We have created a pipeline to deploy a report from one workspace to another, and these workspaces use different data sources (e.g., QA, Sandbox). When the report and semantic model are moved from one workspace to another, we need to change the data source accordingly.
However, when we attempt to do this using the data source rules, the fields are disabled. Could you please help us understand why this might be happening and how we can resolve it? I tried similar posts but none of the answers is working for me. At access level I have access of workspace, data source everything
Additional info: We are connecting through on premise gateway
Solved! Go to Solution.
Hi @nileshkemse ,
Thanks for the follow up and detailed explanation! Based on what you mentioned, your semantic model is using Direct Query mode and deployment rules have more limited support in Direct Query mode.
But not to worry, you can consider the following ways to move forward:
If acceptable in your scenario, switching the model from Direct Query to import mode will allow you to use the full power of deployment rules. This gives you more flexibility to handle switching data sources in different environments.
Fabric lifecycle management tools Frequently asked questions - Microsoft Fabric | Microsoft LearnIf switching modes is not quite feasible, you may consider manually adjusting the data source configuration in the target workspace. In Gateway Management in Power BI Services, you can manually set up and change data source connections for each workspace.
Even in Direct Query mode, although you cannot automatically change the data source by rule, you can still redeploy the model by manually reconfiguring the data source.
Solved: Re: Deployment rules in deployment pipeline - Microsoft Fabric Community
These are a few of the viable options available at this time, and I hope this helps with your question!
Hi All,
Firstly, blopez11 thank you for your solution!
And @nileshkemse ,From your description, it seems that you already have access to all the data, to make sure that you can figure out your problem, you see if you have the permissions for setting up the rules as follows.
After making sure that you have the right permissions, I would recommend that you look at your data sources next, as data source rules only apply to certain types of data sources. If the semantic model is using an unsupported data source (such as certain data streams or file types), the rules will be disabled.
Solved: Re: Data source rules are disabled power BI server - Microsoft Fabric Community
Finally, based on your picture, you really have a problem in deploying the semantic model, you need to make sure that the configuration of the semantic model is compatible with the pipeline deployment because if the semantic model contains complex configurations (e.g., DirectQuery, change tables, etc.), this may lead to limitations in the deployment process.
The Microsoft Fabric deployment pipelines process - Microsoft Fabric | Microsoft Learn
I hope the above solution ideas can help you solve the problem, if I can solve your problem perfectly I will be honored!
Hope it helps!
Best regards,
Community Support Team_ Tom Shen
If this post helps then please consider Accept it as the solution to help the other members find it more quickly.
Thanks for your reply. We have actually created a semantic model with Direct Query, so is it not possible to edit the deployment rules now? We have done a lot of work on these reports. Is there any other way to use deployment rules with this semantic model?
Hi @nileshkemse ,
Thanks for the follow up and detailed explanation! Based on what you mentioned, your semantic model is using Direct Query mode and deployment rules have more limited support in Direct Query mode.
But not to worry, you can consider the following ways to move forward:
If acceptable in your scenario, switching the model from Direct Query to import mode will allow you to use the full power of deployment rules. This gives you more flexibility to handle switching data sources in different environments.
Fabric lifecycle management tools Frequently asked questions - Microsoft Fabric | Microsoft LearnIf switching modes is not quite feasible, you may consider manually adjusting the data source configuration in the target workspace. In Gateway Management in Power BI Services, you can manually set up and change data source connections for each workspace.
Even in Direct Query mode, although you cannot automatically change the data source by rule, you can still redeploy the model by manually reconfiguring the data source.
Solved: Re: Deployment rules in deployment pipeline - Microsoft Fabric Community
These are a few of the viable options available at this time, and I hope this helps with your question!
Do your reports/semantic models already exist in the target workspace? One nuance when using deployment rules is that the report/semantic model must already exist in the target.
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
| User | Count |
|---|---|
| 49 | |
| 24 | |
| 12 | |
| 11 | |
| 10 |