To create a Microsoft Fabric capacity, sign in to the Azure portal, search for Microsoft Fabric and select Create Fabric Capacity. On the Basics tab, choose a subscription and resource group, name the capacity, pick a region and a size (an F SKU such as F2), and choose a Fabric capacity administrator. Then select Review + create. When it’s deployed, assign a workspace to it from the workspace settings in Fabric. You can pause, resume and resize the capacity from the Azure portal at any time, and you pay per second only while it’s running.
This guide is up to date as of November 2026 and follows Microsoft Learn. It uses one example throughout: Riverside Retail, a UK company with a six-person data team. They want one small capacity for development, so they create an F2 in UK South called riversidef2uks, put it in a resource group called rg-riverside-fabric, and assign their Sales Analytics workspace to it.
If you’re new to Fabric, our Microsoft Fabric and Power BI tutorial shows what to build once the capacity is running.
What a Fabric capacity is
A capacity is a pool of compute for Fabric. Its size is measured in capacity units (CUs), and the number in the SKU name is the number of CUs. So an F2 has 2 CUs and an F64 has 64. Every workspace assigned to the capacity shares that pool: Power BI, pipelines, notebooks, lakehouses, warehouses and the rest.
There are two kinds you can use for Fabric:
- F SKUs, bought in Azure. Microsoft recommends these. Azure bills per second with a one-minute minimum, with no commitment, and you can reserve them for a year to save money.
- P SKUs (Power BI Premium). Microsoft is retiring these, and they’re available only to customers who already have them on an Enterprise Agreement. New customers buy F SKUs.
This guide covers F SKUs. Here are the smaller sizes from Microsoft’s SKU table:
| SKU | Capacity units | Comparable Power BI SKU | Free users can view Power BI content? |
|---|---|---|---|
| F2 | 2 | – | No |
| F4 | 4 | – | No |
| F8 | 8 | EM1/A1 | No |
| F16 | 16 | EM2/A2 | No |
| F32 | 32 | EM3/A3 | No |
| F64 | 64 | P1/A4 | Yes, with a Viewer role on the workspace |
Microsoft says to use the table to compare compute, not as a statement that the SKUs are equivalent in features or licensing. Sizes go up to F8192.
The licence rule that catches small teams
On any F SKU smaller than F64, everyone who views Power BI content needs a Power BI Pro, Premium Per User or individual trial licence. A free Fabric licence isn’t enough to view reports. From F64 upwards, users with a free licence and a Viewer role can view Power BI content.
A free licence does let people create and share non-Power BI items, such as lakehouses, notebooks and pipelines, in a workspace on an F capacity of any size. To create Power BI items outside My workspace, they still need Pro or PPU.
Riverside Retail’s six analysts already have Power BI Pro, so an F2 works for them. If they later wanted 200 staff with free licences to read reports, they would need an F64. Our guide to Power BI licences explains the per-user options in more detail.
Before you start
Check these first. Most failed setups miss one of them.
- A licence for yourself. Microsoft lists Microsoft Fabric (Free) or a Power BI licence as a prerequisite.
- An Azure subscription in the same Microsoft Entra tenant as your Fabric and Power BI users. Pay-as-you-go or an agreement subscription both work.
- Permission to create the capacity in that subscription. Microsoft suggests a custom Azure role with just these actions, rather than the broad Owner or Contributor roles:
Microsoft.Fabric/capacities/read Microsoft.Fabric/capacities/write Microsoft.Fabric/capacities/suspend/action Microsoft.Fabric/capacities/resume/action - The
Microsoft.Fabricresource provider registered in the subscription. You need to do this once, before the first capacity. In the Azure portal, open the subscription, then Resource providers, findMicrosoft.Fabricand register it. - Enough CU quota in the subscription and region for the size you want. An F2 needs 2 available CUs. If the quota is too low, request an increase first.
- A region where Fabric runs. Microsoft’s region list shows UK South and UK West with all Fabric workloads available. UK South’s only listed gap is the Fabric App preview.
- Fabric turned on in your tenant. Buying a capacity gives you compute, but a Fabric administrator must also allow users to create Fabric items (the Users can create Fabric items tenant setting).
Choose the region carefully
Your tenant has a home region, set when the tenant was created. To find it, sign in to Fabric, open the Help pane, select the About link and look at Your data is stored in.
You can create a capacity in a different region. Microsoft calls this Multi-Geo. Compute and storage, including OneLake, then sit in the capacity’s region, although some tenant metadata stays in the home region.
Pick the region you’ll keep. A workspace that holds non-Power BI Fabric items, such as a lakehouse, can’t be moved to a capacity in another region until you delete those items. Microsoft also recommends putting the capacity where your other data already lives, to cut latency and data transfer charges.
Riverside Retail’s home region is UK South, and its Azure SQL database is in UK South too, so UK South is the obvious choice.
How to create a Fabric capacity in the Azure portal
- Sign in to the Azure portal.
- Search for Microsoft Fabric and open the service.
- Select Create Fabric Capacity.
- On the Basics tab, fill in the fields (see the table below).
- Select Next: Tags if you want to add tags. Tags such as
team = dataandenvironment = devhelp you find the cost later in Azure Cost Management. - Select Review + create, check the summary, then select Create.
Deployment usually takes a short time. When it finishes, open the resource and check that the Overview shows the size you chose and that the capacity is active.
This is what Riverside Retail enters:
| Field | What it means | Riverside Retail |
|---|---|---|
| Subscription | The Azure subscription that pays for the capacity | Riverside Retail – Data (pay-as-you-go) |
| Resource group | A folder for related Azure resources. Choose an existing one or select Create new. | rg-riverside-fabric (new) |
| Capacity name | The capacity’s name in Azure and Fabric. You can’t rename a Fabric capacity later, so choose carefully. | riversidef2uks |
| Region | Where the capacity’s compute and the workspace data live | UK South |
| Size | The F SKU. Select Change size to see the list. | F2 |
| Fabric capacity administrator | The people who manage the capacity in Fabric | The data team lead and one other team member |
Two rules apply to the capacity administrator. They must belong to the tenant where you create the capacity, and B2B guest users can’t be capacity administrators. So if a consultant from another company is setting this up for you, they can’t make themselves the capacity admin with their guest account. Add at least two of your own people, so the capacity isn’t stuck if one of them leaves.
Keep capacity names to lowercase letters and numbers. The portal checks the name as you type and tells you if it isn’t allowed.
You can also start from Fabric. In the admin portal, go to Capacity settings, select the Fabric capacity tab and select Set up a new capacity in Azure. That opens the same Azure page.
How to assign a workspace to the capacity
A new capacity does nothing until a workspace uses it. Workspaces start on shared capacity, so you move them across with the workspace type setting. (Microsoft used to call this “licence mode”.)
- In Fabric, open the workspace, here Sales Analytics.
- Open Workspace settings and select Workspace type.
- Select Edit.
- Choose the Fabric workspace type, then choose
riversidef2uksas the capacity. - Apply the change.
For a new workspace, select Workspaces > New workspace, expand Advanced and set the workspace type there.
To do this you need to be an admin of the workspace and have rights on the capacity: capacity admin, or capacity contributor. Capacity admins control who counts as a contributor, either the entire organisation or specific users and security groups. Riverside Retail limits contributors to its data team’s security group, so other departments can’t quietly add workspaces to the F2.
Your Azure subscription and resource group don’t affect who can use the capacity. That’s controlled in Fabric by the capacity admins and contributors.

Who manages what: Azure roles and the capacity admin role
Two separate permission systems apply to a Fabric capacity, and people often mix them up.
| Role | Where it’s set | What it lets you do |
|---|---|---|
Azure role with the Microsoft.Fabric/capacities actions (or Owner/Contributor) |
Azure portal, access control on the subscription, resource group or capacity | Create, pause, resume and resize the capacity. Delete it. |
| Capacity administrator | Chosen when you create the capacity. Changed later in the Fabric admin portal. | Assign workspaces, manage who can use the capacity, set contributor permissions, change capacity settings and workloads |
| Capacity contributor | Fabric admin portal, Contributor permissions | Assign workspaces to the capacity. Can’t change settings or delete the capacity. |
| Fabric administrator | Microsoft 365 admin centre | Tenant-wide Fabric settings, such as turning Fabric on. It isn’t the same as being the capacity admin. |
To add or remove capacity admins after creation, open the Fabric admin portal (Settings > Admin portal), select Capacity settings, then the Fabric capacity tab. Select the capacity, expand Admin permissions on the Details tab, change the list and select Apply. Newer Microsoft pages call the same area OneLake catalog > Govern > Capacities.
Being capacity admin doesn’t let you pause the capacity in Azure. Microsoft’s scaling instructions ask for both the capacity admin role and the Azure permissions. At Riverside Retail, the data team lead has both. The second admin has only the Fabric role.
How to pause and resume a Fabric capacity
Pausing stops the hourly charge for compute. It’s the main way to save money on a development capacity.
To pause:
- In the Azure portal, open the Microsoft Fabric service.
- Select the capacity.
- Select Pause, then Yes to confirm.
To resume, follow the same steps and select Resume, then Yes. Billing starts again, and content on the capacity becomes available again.
Know these before you pause:
- Content on a paused capacity isn’t available. Reports, refreshes and notebooks in its workspaces stop working until you resume. Make sure nobody is using it.
- Usage you’ve built up is billed when you pause. Fabric spreads heavy jobs over time (smoothing). When you pause, any smoothed usage and overage still owed is added up and charged to your Azure bill. So a pause straight after a big job doesn’t make that job free.
- Pausing ends throttling at once. If the capacity is overloaded and throttled, pausing returns it to a healthy state. Microsoft describes this as a self-service way to end throttling, but you still pay for the carried-forward usage.
- You can schedule it. Microsoft points to Azure Automation runbooks and the Fabric capacity REST API for suspend and resume. Our guide to turning off Fabric capacities with Azure Data Factory shows a scheduled pipeline that pauses every running capacity.
What pausing saves Riverside Retail
On 8 November 2026, the Azure Retail Prices API listed the UK South pay-as-you-go rate for Fabric capacity at £0.1579 per CU hour, excluding VAT. An F2 has 2 CUs, so it costs £0.3158 an hour while it runs.
- Left running all month (730 hours), that’s about £230.
- Riverside Retail runs it only from 08:00 to 18:00 on weekdays: 10 hours × 22 working days = 220 hours. 220 × £0.3158 = £69.48 for the month, plus any carried-forward usage billed at each pause.
OneLake storage is billed separately from compute. Prices also move with exchange rates, so check the current figure before you budget. Our Microsoft Fabric and Copilot costs guide has the full price list by SKU, reservations versus pay-as-you-go, storage costs and a worked budget.
How to scale a Fabric capacity
If the F2 is too small, change its size. You don’t need to create a new capacity.
- In the Azure portal, open the Microsoft Fabric service and select the capacity.
- Under Scale, select Change size.
- Pick the new size and select Resize.
- Check the Overview tab shows the new size.
What to expect:
- You pay the pay-as-you-go rate for the new size from the change. Scaling below a size you’ve reserved doesn’t reduce your bill.
- Scaling up a capacity that’s smaller than F64 happens almost immediately. Licence-related updates usually take up to a day.
- Crossing the line between F256 and F512, in either direction, can briefly interrupt the capacity and cancel running jobs. That doesn’t affect small capacities, but plan big changes for a quiet time.
- Avoid resizing often. Running operations can be delayed while the new size applies.
- Microsoft’s capacity settings page says autoscale isn’t available for Fabric capacities, so resizing is a manual or scripted job.
Riverside Retail scales its F2 to an F4 for one week each month while it loads month-end data, then back to F2. At £0.1579 per CU hour, the F4 costs £0.6316 an hour while it runs.
Monitor usage with the Capacity Metrics app
Before you scale up, find out what’s using the capacity. Microsoft’s tool for this is the Microsoft Fabric Capacity Metrics app.
To install it, you need to be a capacity admin and have a Power BI Pro, Premium Per User or individual trial licence.
- In Fabric, select Apps > Get apps, search for Microsoft Fabric, select Microsoft Fabric Capacity Metrics and select Get it now. Then select Install.
- Open the app and select Connect.
- Enter UTC_offset. For the UK, enter
0. Microsoft asks for your organisation’s standard time, so you don’t change it for British Summer Time. - Select OAuth2 as the authentication method and Organizational as the privacy level, then Sign in and continue.
- Choose the capacity from the Capacity Name list. The first load can take a few minutes. If you see no data, refresh the app.
Microsoft recommends installing the app in a Pro workspace, not on the capacity you’re monitoring, so it doesn’t add to throttling.
The default report is generally available. The Compute page shows 14 days of CU use, split into interactive and background operations, with throttling events. The Timepoint pages show which items used the most compute in a 30-second window. Usage normally appears within 10 to 15 minutes. New capacities, workspaces and items show up after the app’s midnight refresh, unless you refresh it yourself. Since version 3.0 the app also includes a redesigned Fabric Capacity Metrics Preview report, which is still in preview. The app has no alerts of its own.
Try the Fabric trial first
If you only want to explore Fabric, you may not need to pay for a capacity yet. The Fabric trial gives you a trial capacity free for 60 days.
- To start it, select your profile picture in the top-right corner of Fabric to open the Account manager, and select Start trial. Choose a trial region (it defaults to your home region) and select Activate. You can also trigger a trial by trying to create a Fabric item in a workspace that doesn’t support one.
- Size: the trial is either an F4 or an F64. If yours has 4 CUs, you may be able to change it to 64.
- What’s not included: Copilot, Fabric data agents, AI functions and Trusted Workspace Access aren’t supported, and Private Link is turned off. Storage is limited to 1 TB.
- Who manages it: whoever starts the trial becomes its capacity admin. You can’t add other admins to a trial capacity.
- When it ends: workspaces go back to Power BI Pro, and non-Power BI Fabric items stop working. You have seven days to move the workspaces to a paid F or P capacity before those items may be deleted.
- Not for production. Microsoft says a trial is for evaluation and testing only, and limits how many trials a tenant can have.
A sensible route is to learn on a trial, then create a paid F2 in the same region and move the workspaces across before the 60 days end. Riverside Retail did exactly that. Its trial ran in UK South, so the move to riversidef2uks was a same-region change.
Common mistakes
- Picking the region without thinking. Workspaces with lakehouses or other Fabric items can’t move to a capacity in another region until those items are deleted.
- Expecting free users to see reports on an F2. Below F64, every Power BI viewer needs Pro, PPU or an individual trial.
- Making one person the only capacity admin. If they leave, nobody can manage the capacity in Fabric. Add at least two.
- Using a guest account as the capacity admin. B2B users can’t be capacity administrators.
- Forgetting the resource provider or quota. If creation fails straight away, check that
Microsoft.Fabricis registered and that the region has enough CU quota. - Creating the capacity and stopping there. Nothing runs on it until you change a workspace’s type to Fabric and pick the capacity.
- Leaving a development capacity running every night and weekend. For an F2 in UK South, that’s most of the £230 a month.
- Pausing to “reset” a big bill. Pausing charges the smoothed usage you’ve built up. It doesn’t cancel it.
- Pausing during a refresh or while people are working. Everything on the capacity becomes unavailable.
- Scaling up before you look at the Metrics app. One badly designed refresh can look like a capacity that’s too small.
- Granting Owner on the subscription to everyone who needs to pause. A custom role with the four
Microsoft.Fabric/capacitiesactions is enough.
FAQ
How long does it take to create a Fabric capacity?
The Azure deployment itself is usually quick. Allow extra time for the one-off steps: registering the Microsoft.Fabric resource provider, getting the right Azure permissions, and asking for more CU quota if the region needs it.
Which Fabric capacity size should a small team start with?
An F2 is the smallest size and is enough for many development and learning workloads. Check the Capacity Metrics app after a few weeks and scale up only if the Compute page shows sustained high use or throttling. If many people with free licences need to view reports, you need F64 or larger.
Can I pause a Fabric capacity to save money?
Yes. F SKU capacities can be paused and resumed in the Azure portal, and you don’t pay the hourly compute charge while paused. Any smoothed usage still owed is billed when you pause, and OneLake storage is still charged.
What’s the difference between a capacity admin and a Fabric admin?
A capacity admin manages one capacity: which workspaces use it, who can add workspaces, and its settings. A Fabric administrator manages Fabric settings for the whole tenant. Pausing, resuming and resizing need Azure permissions on top of the capacity admin role.
Can I use a Fabric trial instead of buying a capacity?
Yes, for 60 days of evaluation. The trial is an F4 or F64, but it doesn’t include Copilot or data agents and isn’t meant for production. Move your workspaces to a paid capacity in the same region before it ends.
Can I rename or move a Fabric capacity after I create it?
You can’t rename a Fabric capacity, and it stays in the region you created it in. To change region, create a new capacity in the new region and move the workspaces. Workspaces with non-Power BI Fabric items need those items deleted first.
To set up and run Fabric with a trainer on hand, from capacities and workspaces to lakehouses and pipelines, see our live Microsoft Fabric training. To build the Power BI reports and models that run on your capacity, browse our Power BI training courses.


