Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hi All,
We are trying to setup workspace and wanted to know your recommendation.
Do you suggest creating
Approach 1:
Dev, QA and Prod workspace and publish the contents on each depending on where we want to publish. So if we are in development phase we can publish it to Dev Workspace and once we want to open it for QA testing, we can publish the same to QA Workspace. And similarly for Prod.
OR
Approach 2:
Create workpace for various data categories like
for HR, we create HR Dev, HR Qa and HR Prod
For Marketting team, we create Marketting Dev, Qa and Prod
and so on.
You can suggest any other approach if you have.
Regards,
Akash
That really depends on your security considerations, does it matter if HR people see all of the dashboards/reports? If so, then use the second approach, otherwise I always believe that simpler is better.
Yes we don't want HR people to see other dashboards. But can't we control the access at individual dataset and dashboard level even if we have everything on Dev workspace ?
I just want to understand best practice followed in other real time projects.
While you could, again, going back to simplicity, I would do it by workspace.
So you suggest approach 2. But will not end up having too many workspace if we have various BUs like HR, Finance, Marketing, Consulting etc..
Also how do we deploy the code from one workspace to other. Lets say we develop something on HR Dev Workspace. Now I want the infrastructure admins to deploy the code from Dev workspace to Prod workspace.
That all depends on how you are doing your development. If you are using Desktop and then Publishing, you would just publish to a different workspace.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.