Thanks for the video! Simple and clear explanation. My mistake was considering this topic as not worth paying too much attention to. Indeed it really requires a lot of thinking to organize workspaces properly.
Thanks for sharing, now I know that we are on the right path :) We separate workspaces by business units, B2B user types, dev pipeline... and also having RLS implemented in some cases.
Thanks for sharing Reza, Imagine you have 20 folders in PowerBI Server with average of 10 dashboards in each, you have 3 separate servers (Dev,UAT and Prod). How would you organise these dashboards in PowerBI Service? One scenario is to have 20 workspaces and two extra workspace used as Development and Test. Then you would lose the ability to use Deployment pipelines.
Thanks for the video @RADACAD ! Great insights as always. So I have a follow up question. What is the best practice to use when you have workspaces set up for different functional areas (e.g. Sales, HR, Project, Maintenance, Production) but want to create a crossfunctional (e.g. site management) dashboard or app with chart & KPIs based on content from the different functional Power BI reports.
Hi! We're struggling with the point where several reports need to be shared between multiple otherwise separate groups of users (different workspaces). What would be the best way to share the reports? Will it be to manually publish a report to each of the workspaces? Or use the Copy report function from the service? Or smith else?
Hello Reza, Nice Video. I am building a new Power BI environment and plan on having 3 SQL servers as the main data sources (Dev, UAT, Prod). Right now we are going to use Power Bi Pro and then later scale up to Premium capacity, If I use 3 workspaces as you suggest (Dev, Test, Prod) in the Power BI Service, can I manually change the data sources for reports as I push them from Dev to UAT to Prod to the related SQL Server? I know I will be able to do this automatically with deployment pipelines at some point, but any risks trying to do this manually for now? Thanks for any insight.
What if I like to share a dataset to report creators but the dataset itself should have security build in so that already the creators who use the dataset (single source of truth) can only work with their limited access to the dataset (kind of subdataset) and not see everything? Thnanks
Very interesting topic. if we sharing the related dashboard ( lets say financial dashboards) for different users using row level security does it have to be in a different workspace? Many thanks in advance
RLS itself controls the access of the users. different users will see different things in the report based on their roles. no need to be in a different workspace, but can be.
Thanks for this video. If you use cascading layers and, let's say, I want to query a table that is 3 layers down, wouldn't that mean that my report sends a query to the outer layer and that one to the next layer and so on? Wouldn't that create inefficiency and higher latency?
It depends on what connection method you use. If you are importing data, then the queries will be sent only at the time of refresh, not all at once, and no performance impact.
Hello Reza, I have multiple clients and I am creating / managing all of their reports under my tenant. I am separating each client by using a different workspace. I have turned off 'Sharing dataset between workspaces'. Could you please provide more information, if there is anything I am missing or should implement. Thank you!
Hi Vishesh I would suggest to have their reports under their own tenants. then if you are using shared datasets etc it would be just for their own tenant and you don't need to worry about the rest. However, this is a general advise and might be different case by case. Cheers Reza
@@RADACAD Thank you for responding. Apart from not being able to share dataset between workspaces, do you think anything else that could go wrong with my approach? I have all control and I just provide the clients with the ‘viewer’ or ‘contributor’ roles in their specific workspaces.
@@visheshjjain I wouldn't say this is wrong, but I would not recommend this method. this means you are tied up all in one workspace. and the client also doesn't have full control over their environment.
A good video but the use case scenarios you dismissed do have merit where you have potentially hundreds of external access groups. Say analytical reports for customers as opposed to internal consumers.
Hi Peter. I would need more details to understand what do you mean by analytical reports for customers. but generic advice is that: If your customer's data structure is the same, and their reporting need is also the same, the difference is just the data for every customer. then all of that can be in one workspace shared using apps and row-level security.
Thanks for the video! Simple and clear explanation. My mistake was considering this topic as not worth paying too much attention to. Indeed it really requires a lot of thinking to organize workspaces properly.
Thanks for sharing, now I know that we are on the right path :)
We separate workspaces by business units, B2B user types, dev pipeline... and also having RLS implemented in some cases.
Very interesting topic and clearly described. Thank you!
Legend! Exactly what I needed
Thanks for sharing Reza,
Imagine you have 20 folders in PowerBI Server with average of 10 dashboards in each, you have 3 separate servers (Dev,UAT and Prod). How would you organise these dashboards in PowerBI Service?
One scenario is to have 20 workspaces and two extra workspace used as Development and Test. Then you would lose the ability to use Deployment pipelines.
You are very interesting the topic you comes up every times.
Thanks for the video @RADACAD ! Great insights as always.
So I have a follow up question. What is the best practice to use when you have workspaces set up for different functional areas (e.g. Sales, HR, Project, Maintenance, Production) but want to create a crossfunctional (e.g. site management) dashboard or app with chart & KPIs based on content from the different functional Power BI reports.
Do you have any recommendation on how to organize a Premium Capacity. Is it possible creating folders to organize the reports per argument?
Hi! We're struggling with the point where several reports need to be shared between multiple otherwise separate groups of users (different workspaces). What would be the best way to share the reports? Will it be to manually publish a report to each of the workspaces? Or use the Copy report function from the service? Or smith else?
Can you cascade dataflow auto refresh from linked workspaces?
Hello Reza,
Nice Video. I am building a new Power BI environment and plan on having 3 SQL servers as the main data sources (Dev, UAT, Prod). Right now we are going to use Power Bi Pro and then later scale up to Premium capacity, If I use 3 workspaces as you suggest (Dev, Test, Prod) in the Power BI Service, can I manually change the data sources for reports as I push them from Dev to UAT to Prod to the related SQL Server? I know I will be able to do this automatically with deployment pipelines at some point, but any risks trying to do this manually for now?
Thanks for any insight.
What if I like to share a dataset to report creators but the dataset itself should have security build in so that already the creators who use the dataset (single source of truth) can only work with their limited access to the dataset (kind of subdataset) and not see everything? Thnanks
Great content! Thanks for sharing👏👏
DO you have a blog or any that shows how can combine multiple workspace in to one.
do you mean moving the content of two workspaces into one?
I have six workspaces and the management want to consolidate all the six in to three workspaces. How can I do ?
@@andykebede1133 you can use Power BI Helper to move the content of old workspaces into the new ones
@@RADACAD thank you I will do it. Thank u so much again .Do you have power helper blogs .
@@andykebede1133 powerbihelper.org/ we will create some guide videos for it soon
Very interesting topic. if we sharing the related dashboard ( lets say financial dashboards) for different users using row level security does it have to be in a different workspace?
Many thanks in advance
RLS itself controls the access of the users. different users will see different things in the report based on their roles. no need to be in a different workspace, but can be.
how can we migrate / move dashboards from Premium to another Premium workspace ?
Thanks for this video. If you use cascading layers and, let's say, I want to query a table that is 3 layers down, wouldn't that mean that my report sends a query to the outer layer and that one to the next layer and so on? Wouldn't that create inefficiency and higher latency?
It depends on what connection method you use. If you are importing data, then the queries will be sent only at the time of refresh, not all at once, and no performance impact.
Hello Reza,
I have multiple clients and I am creating / managing all of their reports under my tenant.
I am separating each client by using a different workspace. I have turned off 'Sharing dataset between workspaces'.
Could you please provide more information, if there is anything I am missing or should implement.
Thank you!
Hi Vishesh
I would suggest to have their reports under their own tenants. then if you are using shared datasets etc it would be just for their own tenant and you don't need to worry about the rest. However, this is a general advise and might be different case by case.
Cheers
Reza
@@RADACAD Thank you for responding. Apart from not being able to share dataset between workspaces, do you think anything else that could go wrong with my approach?
I have all control and I just provide the clients with the ‘viewer’ or ‘contributor’ roles in their specific workspaces.
@@visheshjjain I wouldn't say this is wrong, but I would not recommend this method. this means you are tied up all in one workspace. and the client also doesn't have full control over their environment.
@@RADACAD that’s true! Thank you for your insights!
Nice video!
A good video but the use case scenarios you dismissed do have merit where you have potentially hundreds of external access groups. Say analytical reports for customers as opposed to internal consumers.
Hi Peter. I would need more details to understand what do you mean by analytical reports for customers.
but generic advice is that: If your customer's data structure is the same, and their reporting need is also the same, the difference is just the data for every customer. then all of that can be in one workspace shared using apps and row-level security.
Why do we need layers ? I could just put all my Dataflows into one workspace