Forum Discussion
Understanding Limits for Creating Workspaces, Lakehouses, Warehouses, Data pipelines and other items
It's not a tenant limit, it's a user and item limit
In practice, we usually avoid creating too many items in a single workspace to reach the 1000-item limit, as it can negatively impact the efficiency of managing data and permissions.
Additionally, storage and compute capacity limitations can affect the number of items you can actually create. Since items within the same workspace or capacity share the corresponding resources, you may not be able to create more items once the storage or compute reaches its limit. Higher capacity workspaces can handle more items and larger workloads. You may pay more attention to capacity SKU and workspace license mode. Microsoft Fabric concepts - Microsoft Fabric | Microsoft Learn
You will find some suggestions and guidance about the deployment patterns at the tenant level from the document: Deployment patterns for Microsoft Fabric - Azure Architecture Center | Microsoft Learn
Hope this would be helpful.
Best Regards,
Jing
We have hit the 1000 items limit for users. Most of the time it was due to them being unorganized but there were valid reasons too for removing that limit.
what do you mean 1000 items limit for users? it means you can create 1000 items within a workspace and another person (assigned to that workspace) can create another 1000 items in the same workspace?
Each user can only create 1000 items, regardless of the number of workspaces involved. in addition, each workspace can only contain 1000 items, regardless of number of users.
Those are independent limits.