Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

July 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more

Reply
rsrwebsupport
Frequent Visitor

Development / Test / Prod Environments

I'm trying to figure out the best way to support multiple development environments in Power BI.  Specifically, we have completely separate Development / Test / Prod web servers, each with their own databases and their own copies of source code.  From a coding perspective, we write code on our local, push to the git repo, deploy the code to Development, test it, deploy the code to Test, perform more testing, and then finally deploy to Prod.  Each server has its own separate database, and the source code is all managed by Git.

 

Ideally, we would follow this same work flow in Power BI.  This is essentially what we would want if it were possible for new reports:

  • Any time there's a new report, we would create the report on Development.
  • We would embed this report on the Development server, and it would use data from the Development database.
  • After the report gets tested, we would want to move the report to the Test environment without having to recreate the report from scratch.  The report would use data from the Test database.  Meanwhile, if you still wanted to view the report on Development, it would still be there and still use data from the Development database.
  • Once the report goes to Prod, it would use data from the Prod database.  Meanwhile, the report would still be on both lower environments using the lower envionment databases.

We would also ideally want a similar workflow when updating the source data model.  For example, this is what we would want if, hypothetically, we had to change the calculation on one of the calculated columns used in reports:

  • We would make the change on Development, and it would be reflected in all reports in Development.
  • After the change is tested, we would copy the change to the Test environment, ideally without having to recreate the change manually.  The new calculation would then be reflected in all reports on both Development and Test, but not yet on Prod.
  • Repeat again for Prod.

Is a workflow like this possible in Power BI?  Or will we have to modify how we approach things?  Thanks.

1 ACCEPTED SOLUTION
rsrwebsupport
Frequent Visitor

After doing some more research, it looks like Deployment Pipelines basically do this, so that seems to be the best solution in this case.

View solution in original post

1 REPLY 1
rsrwebsupport
Frequent Visitor

After doing some more research, it looks like Deployment Pipelines basically do this, so that seems to be the best solution in this case.

Helpful resources

Announcements
FabCon and SQLCon Barcelona 2026

FabCon & SQLCon – Barcelona 2026

Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.

Fabric Community Sticker Design Challenge Barcelona Carousel

Fabric Community Sticker Challenge - Barcelona 2026

If you love stickers, then you will definitely want to check out our community sticker challenge, Barcelona edition!

July Power BI Update Carousel

Power BI Monthly Update - July 2026

Check out the July 2026 Power BI update to learn about new features.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.