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

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Learn more

Reply
akj2784
Post Partisan
Post Partisan

Workspace Setup recommendation in Service

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

5 REPLIES 5
Greg_Deckler
Community Champion
Community Champion

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.



Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!:
DAX For Humans

DAX is easy, CALCULATE makes DAX hard...

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.



Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!:
DAX For Humans

DAX is easy, CALCULATE makes DAX hard...

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.



Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!:
DAX For Humans

DAX is easy, CALCULATE makes DAX hard...

Helpful resources

Announcements
Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

October Power BI Update Carousel

Power BI Monthly Update - October 2025

Check out the October 2025 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Kudoed Authors