Capacity Throttling

In Fabric/Power BI, a workspace is assigned to exactly one capacity at a time. So “two capacities” really means: two sets of workspaces, each mapped to a different capacity.

1) Buy / provision a second capacity

You’ll need:

• Capacity A (existing): e.g., F16

• Capacity B (new): e.g., F4/F8 (often enough for pipelines)

2) Split by workspace (the only supported way)

Create two workspace groups:

A) “Data Engineering” workspace(s) → Capacity B

Put pipelines / ingestion / staging here:

• Data pipelines that load from Dataverse

• Lakehouses / Warehouses used for staging and transformations

• Scheduled jobs

Assign these workspaces to Capacity B.

B) “BI / Consumption” workspace(s) → Capacity A (F16)

Put user workloads here:

• Semantic models

• Reports

• Paginated reports

• Apps

Assign these workspaces to Capacity A.

Hi Hussein_charif, 

There are two options to resolve this: 
1: Optimize the reports/semantic models so they are more efficient and use less capacity, or

2: get a bigger capacity. 

It is very common for the Fabric ETL pipelines to be on a different capacity than the end user reports so that end users can't cause the ETL to fail. 

What I would do: 

1: create a new workspace for the Power BI reports

2: move all reports into that new workspace 

3: Either optimize the reports, or purchase a second capacity, and assign the report workspace to the new capacity.