Forum Discussion
Power BI Life cycle Management
This blog entry describes a way to achieve a DEV, TEST and PROD environment in power bi as well: http://angryanalyticsblog.azurewebsites.net/index.php/2016/04/17/power-bi-content-workflow/
So in a corporate Power BI environment, I currently think you basically have the following options: Let you end users access reports and dashboards through content packs or throught a PROD group workspace (with privacy set to members can only view Power BI content).
With content packs you can include just the content that fits your user profile, but if they for example need access to a lot of reports from multiple business areas (ie. TEST workspaces) it gets messy in their personal workspace, since the separation is not visible in their personal worspace. Another difference is that with content packs, the end user can create a copy of the reports and modify it.
Hi Konstantinos/Ankit :
Thanks for your help and information. It was definitely good to come across those information.
So I think as best practice, we can have 2 models :
In a Corporate BI environment, multiple environments typically exist for managing the lifecycle of BI assets:
- Development: Available to IT BI developers only
- Quality Assurance (QA): Available to a select group of users for purposes of user acceptance testing
- Production: Available to relevant functional users based on job role, subject area, department, project, etc.
Typically separate Power BI group workspaces are utilized for Dev, QA, and Prod purposes.
2. IT-Managed Self-Service BI: This is where IT will be responsibile for providing the data. However the data managed by IT will enable Self-Service reporting. In this case we will have no Dev, QA and Prod cycle.
What do you guys think? I want to continue this discussion.
Regards,
Anindya
Any further comment on this one?
Would love to see how people deal with the scenario in real life and what sort of governance/process they have set up.
Thanks and regards,
Anindya