Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
I want some clarifications regarding how the permissions are managed using deployment pipelines in power bi. Does the access permission to a dataset get overwritten when an updated dataset is deployed after being changed from test to prod?
Similar questions for the reports as well.
Then what would be the use of the deployment pipeline if we have to again and again all the access rights to reports and datasets?
Solved! Go to Solution.
Hi @Rosy081,
Thanks for reaching MS Fabric community support.
When content from the source stage is copied to the target stage, Fabric identifies existing content in the target stage and overwrites it. To identify which content item needs to be overwritten, deployment pipelines uses the connection between the parent item and its clones. This connection is kept when new content is created.
The overwrite operation only overwrites the content of the item. The item's ID, URL, and permissions remain unchanged. This behavior ensures that while the dataset's content is updated, the access permissions you've configured are preserved, preventing the need to reassign permissions after each deployment. However, it's important to note that while item-level permissions remain intact, workspace-level permissions are managed separately and are not affected by deployments. Therefore, if you need different users to have access to datasets in different stages (e.g., testers in Test, end-users in Production), you'll need to manually manage workspace permissions accordingly.
In Power BI's deployment pipelines, when deploying updated reports from Test to Production, the existing access permissions on those reports in the Production workspace are retained and not overwritten. This ensures that any user-specific permissions you've configured remain intact after deployment.
Regarding the necessity to reassign access rights repeatedly, it's important to note that Deployment Pipelines are designed to streamline the content promotion process across different stages while preserving existing permissions. This means that once you've set up access permissions in the Production workspace, they remain consistent, even as you deploy updates.
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
@Rosy081, As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
@Rosy081, As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
@Rosy081 As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
Hi @Rosy081,
Thanks for reaching MS Fabric community support.
When content from the source stage is copied to the target stage, Fabric identifies existing content in the target stage and overwrites it. To identify which content item needs to be overwritten, deployment pipelines uses the connection between the parent item and its clones. This connection is kept when new content is created.
The overwrite operation only overwrites the content of the item. The item's ID, URL, and permissions remain unchanged. This behavior ensures that while the dataset's content is updated, the access permissions you've configured are preserved, preventing the need to reassign permissions after each deployment. However, it's important to note that while item-level permissions remain intact, workspace-level permissions are managed separately and are not affected by deployments. Therefore, if you need different users to have access to datasets in different stages (e.g., testers in Test, end-users in Production), you'll need to manually manage workspace permissions accordingly.
In Power BI's deployment pipelines, when deploying updated reports from Test to Production, the existing access permissions on those reports in the Production workspace are retained and not overwritten. This ensures that any user-specific permissions you've configured remain intact after deployment.
Regarding the necessity to reassign access rights repeatedly, it's important to note that Deployment Pipelines are designed to streamline the content promotion process across different stages while preserving existing permissions. This means that once you've set up access permissions in the Production workspace, they remain consistent, even as you deploy updates.
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
Hi @v-prasare
Your reply is really helpful.
Can I ask if Fabric deployment pipeline support Power BI Dataflow Gen1? Does it support to deploy Gen1 to the target stage workspace or only Gen2?
Thanks!
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 58 | |
| 56 | |
| 35 | |
| 18 | |
| 14 |