Power BI Deployment Pipeline - Manual effort related to deploying to different workspaces

Question

Hello, I'm new to deployment pipelines and am just researching considerations in creating a deployment pipeline with multiple Premium workspaces (development, test, production). The benefits seem clear, although any specific benefit bullet points on the benefits are welcome as part of my question. But my focus is on understanding any additional manual effort involved with having a pipeline that deploys from development to test, and finally production where those workspaces are already created and could be easily assigned. Specifically:

Would the connections from a desktop PBIX file to the the dataflows need to be manually updated in deploying to a new workspace? Does auto-binding take care of that?

If a report is updated in development, is it possible to maintain the existing business user bookmarks for that report or would they need to be reset by the users for the updated report?

Is there any other manual effort involving connections to data sources, workflows, and published reports that should be considered in having a multiple workspace pipeline vs. a single workspace one?

Thank you.

Answer 1

Hi @Neil Hurwitz

Unfortunately Power BI is not supported on this forum at this time. It is best that you reach out to PowerBI experts at https://community.powerbi.com/t5/Power-Query/bd-p/power-bi-services and they will gladly assist with more expertise.

----------------------------------------------

If this is helpful please accept answer.