Do I pay per workspace inside capacity?

Hello fabricpribeiro,

Short answer: No, Fabric does not charge you per workspace.

If you purchase an F16 capacity, you are paying for the capacity compute pool. Multiple workspaces can be assigned to that capacity and share its available CUs. Microsoft describes Fabric capacity as a shared pool of compute, and workspaces are assigned to a capacity for billing and sizing.

So, in your example:

F16 + 1 workspace = same base F16 capacity cost.

F16 + 11 empty workspaces = same base F16 capacity cost.

Simply creating or assigning those additional empty workspaces does not increase the F16 compute price.

Where the additional cost or capacity impact can appear is when those workspaces start storing data or running operations.

For compute, pipelines, Dataflows, Warehouse queries, Spark jobs, semantic model operations and other Fabric workloads consume CUs from the same F16 capacity. Therefore, more active workspaces can increase shared capacity utilization and potentially lead to throttling, but you are not billed a separate workspace fee.

For storage, OneLake storage is billed based on the amount of data stored and doesn't consume Fabric CUs. Lakehouses and Warehouses, for example, consume OneLake storage. Therefore, an empty workspace by itself doesn't create meaningful OneLake storage cost, but the Fabric items and data created inside it can.

One nuance I would add is licensing. Depending on the Fabric SKU and Power BI consumption scenario, users may still require the appropriate per-user Power BI license. That is separate from the number of workspaces.

So I would summarize it as:

Workspace = organizational/security container, no per-workspace charge.

Capacity = shared compute pool you purchase, for example F16.

Workloads = consume CUs from that shared capacity.

OneLake data = storage billed based on data stored.

Users = licensing requirements can apply separately.

Therefore, from a cost perspective, I would not avoid creating a properly designed workspace simply because of a fear of a per-workspace Fabric charge. With your 6K+ workspace environment, the bigger concerns are governance, capacity contention, workspace sprawl and storage growth, rather than a direct workspace fee.

Microsoft references:

Microsoft Fabric pricing

OneLake consumption and billing

Understand Fabric capacity throttling

Best regards,
Omkar Shinde
Microsoft Fabric Enthusiast | Power BI Consultant

💡 If you found this response helpful, please consider giving it a Kudos.
✅ If this resolves your question, please mark it as the Accepted Solution to help others in the community.

Creating EMPTY Workspaces won't consume CUs on the capacity until you assign WS to the capacity and start building/deploying models, and later consume the models.