Fabric Planning capacity & cost

A session starts the first time someone opens or works in a plan item, in reading view or edit mode, and lasts 30 days (730 hours). It can't be ended early. You never pick a role: everyone typically starts as a Viewer, and actions upgrade you automatically. Opening any item to look, whether a Planning sheet, a PowerTable or an Intelligence sheet, keeps you a Viewer. Only creating a Planning sheet or editing its design (structure, rules, write-back destinations) makes you a Planner. Almost everything else makes you a Stakeholder: entering or changing plan numbers, approving, writing back, and creating or editing PowerTables and Intelligence sheets. (Microsoft's roles page adds one exception: creating a new plan item upgrades the creator to Planner; see the PowerTable-only question below.) A user holding several roles on one capacity is billed once, at the highest. An upgrade closes the lower session, prorated, and opens a new 30-day session at the higher rate.

For what each role can do and who should hold it, see the roles page.

No, not since August 19, 2026. Microsoft's roles page states it in an Important note: "Planning assigns the Planner persona only when you create or edit planning sheets." Building PowerTable data apps and Intelligence reports is Stakeholder work, at 0.23 CU instead of 1.16 CU.

A Viewer session: 0.05 CU held for 30 days, under $7 at US list rates. Microsoft's billing documentation says opening a plan item in reading view starts a session, so the peek is billable. The upgrade is what to govern: entering one number makes that person a Stakeholder (about $30), and creating a Planning sheet or editing its design makes them a Planner (about $152). Building a PowerTable or Intelligence sheet stays at Stakeholder.

No cap. Within the 30-day session the charge is fixed however much you do: a hundred scenarios, thousands of edits, as many PowerTable data apps and Intelligence reports as you like. What scales with usage is the compute underneath, drawn from the Fabric capacity you already own. The one line you can't cross without an upgrade is creating a Planning sheet or editing its design, which makes you a Planner.

You're billed for the window, not the volume. Once you engage, that 30-day window is committed at your role's rate, and ten entries cost the same as ten thousand. The same fixed charge that removes the ceiling also puts in a floor. The useful question isn't the bill, it's whether that person belongs in the plan at all: if they do, the session cost is a rounding error next to what their time costs; if they don't, that's a governance question, not a billing one.

No. Microsoft states a session can't end early and a role can't be downgraded inside one, so the window runs out at the rate it opened at. Cost control happens before the click, by governing who creates Planning sheets.

No. Billing is based entirely on sustained CU, and sustained CU only starts when there's activity. The first time someone acts, that sets their role and starts a 30-day billing window for it. If nobody opens a plan item, no role is triggered and there is no charge. No activity, no cost.

The one nuance is automation: a background automation job that fires in an otherwise idle month still bills its small per-job draw (see the Automation Jobs section). No sessions and no jobs means no charge.

Microsoft's roles page says items with only PowerTable sheets, or only Intelligence sheets, offer just the Stakeholder and Viewer roles, and its August 19 announcement says editors of such items bill at Stakeholder. The same roles page also says creating a new plan item upgrades the creator to Planner. Until Microsoft reconciles the two, budget one Planner session for whoever sets the item up, then Stakeholder and Viewer for everyone else. The first Planning sheet anyone creates opens a Planner session as usual.

Only if an admin turns it on. Microsoft's roles page documents a workspace setting, Prompt on Session Upgrade, which is off by default. The same page says creating a new plan item upgrades the creator to Planner with no prompt. Lumel's documentation also describes tenant settings that control who can upgrade to Planner or Stakeholder sessions.

A sustained CU is a reserved seat. The first time a user acts in a role, they open a 30-day session for that role, and that session occupies a fixed share of your F-SKU for the 30-day period, whether they log in every day or once. It is not a running meter: no CU per hour, no accumulating CU-seconds to add up. The number maps directly to the F-SKU scale. A concrete example: one Planner holds 1.16 CU, which is 58% of an F2's total 2 CU. That is why one Planner alone nearly fills the smallest SKU, and why F4 is the realistic floor for production planning.

The calculator adds up sustained CU across your users and recommends the F-SKU that fits.

Because they are billed differently. Automation jobs bill transactionally, per successful job (2 CU-hours each), the same way other Fabric capabilities such as notebooks, pipelines, and Power BI refreshes are metered. There are two job types, PowerTable automation and connected planning in Infobridge. Failed jobs aren't billed, and job billing is the same whatever the user's role. Sustained CU is different: it is a continuously held reserved seat for the full 30-day session, held by Viewer, Stakeholder, and Planner roles regardless of how often they act.

To size your F-SKU, the calculator still needs one number, so it converts total automation CU-hours over the 30-day period into a CU-equivalent: total CU-hours divided by the hours in the period, the same conversion that defines the sustained CU rates themselves. That equivalent is what shows up in the capacity tank and dollar breakdown alongside the roles, even though automation jobs are not held continuously the way a role's session is.

See the calculator's Automation Jobs section for what counts as a job and two concrete examples.

One Planner holds 1.16 of an F2's 2 CU, so F4 is the practical floor once real planning starts. Microsoft notes that small SKUs like F2 and F4 are the easiest to overcommit. A data-management-only deployment, with no Planning sheets, is mostly Stakeholders and Viewers; budget one Planner session for setup (see the PowerTable-only question). Put your numbers in the calculator.

They share the same pool, so size for the planning peak on top of your existing peak rather than as a separate allocation. The calculator's buffer setting is one way to build that headroom in deliberately.

Microsoft recommends about a 30% buffer for the other Fabric workloads on the capacity, which is the calculator's default. Planning sessions keep being recorded even when other workloads exhaust the capacity.

The same thing that happens on pay-as-you-go: both capacity types hard-cap at the CU limit, and both offer overage billing as a toggleable setting. With overage on, additional CU-seconds are charged at 3x the pay-as-you-go rate. With overage off, the capacity throttles. Reserved and PAYG behave identically here; the difference between them is price and commitment, and the way to avoid the question entirely is to size with headroom (see the calculator's buffer setting).

Yes. Microsoft's billing documentation tracks sessions per tenant, user and capacity, so one person active on two capacities has two sessions. Within one capacity it is the reverse: several workspaces roll up, and the user is billed once at the highest role they hold.

Traditional EPM tools charge an annual license for every seat, and a viewer seat often costs nearly as much as a builder seat, regardless of how much anyone uses the tool. Fabric Planning is consumption-based: you pay for active use only, and the Viewer and Stakeholder tiers are priced deliberately low to make broad participation cheap. Think of it as SaaS within SaaS: the planning workload draws from the same Fabric capacity you already run analytics on, and unused capacity stays available to the rest of Fabric. The comparison favors Fabric Planning most for seasonal cycles with many occasional participants, which is what most planning processes look like. Put your own numbers in the calculator to see where you land.

A fair question with an honest answer: we have not confirmed whether Copilot and AI features in Fabric Planning draw from the same CU pool or bill separately. Microsoft's billing documentation does not address it. Check Lumel's pricing page for the latest before committing, and treat AI usage as a line item to verify during a POC.

The rest of every active session is billed at the pause. Microsoft's billing documentation says the remaining CU for every active Planner, Stakeholder and Viewer session on that capacity is summed and added to your Azure bill. Any overage and smoothed usage carried forward on the capacity is billed at the same moment.

A restart is a pause and a resume. The pause bills the rest of every open session. The resume does not bill it again for people who come back in the same role: Microsoft's documentation says users "assuming the same role, under the same tenant and capacity returning within the 30 day period will not start a new session." So a restart pulls the bill forward; it does not grow it. Say a session started on the 1st and you restart on the 16th: the remaining days bill on the 16th, and that person works through the end of their original 30 days at no new charge. Coming back at a higher role is an upgrade and opens a new session as usual.

The same bill-out as a pause: every active session's remaining CU is added to your Azure bill, and there is nothing to resume. Sessions belong to the capacity they started on, so when those people start working on another capacity they open new sessions there.

Deleting the item does not end its sessions. Microsoft states they keep running and billing to the end of their 30 days.

Expect to pay twice for up to 30 days. Sessions are tracked per capacity and can't end early, so the sessions on the old capacity still bill in full, and the same people open new sessions the first time they work on the new one. Lumel's pricing estimator says the same: "You pay twice for the same users." If you need more room, Lumel recommends scaling the existing capacity instead of moving workspaces.

Yes. Scaling a capacity up has no effect on planning sessions, and scaling it down doesn't either, as long as the smaller size still covers the CU your active sessions need; go below that and you overcommit the capacity. Only pausing and deleting bill sessions early. On pay-as-you-go you pay the hourly rate of the new size; scaling below a reservation does not lower the bill. One caution from Microsoft: crossing between F256 and F512 in either direction can briefly interrupt the capacity and cancel running jobs.

Two things land at the pause: the smoothed usage and any overage carried forward from whatever maxed you out, billed at the pause instead of burning down, and the rest of every active planning session, pulled forward. The pause also ends the throttling. When you resume, people returning in the same role inside their window add nothing new.

The other way out is to scale up: a bigger size gives the capacity room without pulling any planning charges forward, and on pay-as-you-go you pay the larger size's hourly rate while you run it. The expensive version is recovering onto a different capacity instead; see the question on moving a workspace.

Microsoft hasn't published how the pause or delete bill-out is priced on a reservation-covered capacity. Its reservation terms say the discount applies hour by hour and doesn't carry over. If you're on a reservation, confirm with Microsoft before pausing or deleting a capacity with active planning sessions.