MS Fabric User Permission Segmentation by Artifacts
Currently, when we grant users permission to create Fabric artifacts, they can create anything available in the workspaces they have access to. This unrestricted access can lead to an unstructured environment, particularly with the uncontrolled creation of Lakehouses.
We need to refine user permissions at the subscription or workspace level, allowing us to define exactly what each user can create. For example:
- Some users can create Lakehouses and Notebooks.
- Others can only create Dashboards.
- Others may be restricted to creating Dataflows.
This segmentation will help maintain better governance and organization within MS Fabric. Could you review and implement these restrictions?
2 Comments
- I support this idea. We urgently need it—the increased usage is making the workspaces very cluttered.
This is exactly what we need to support adoption. If I have a Data Science Persona with a group of people, they should be allowed to create notebooks and other things relevant to their role, but not mirrors and snowflake and anything in fabric. Admin persona, Data Analyst Persona, Advanced Analyst Persona with the ability for use to allow them to create Fabric Artifacts based on our dev and support patters of supported tools.
