Planning in Microsoft Fabric: Budgets on Power BI Models

Navy Solv Systems title card reading 'Planning in Microsoft Fabric' with a forecast line and grid motif.

In Short: Planning in Microsoft Fabric Puts the Budget Next to the Actuals

Planning in Microsoft Fabric lets finance and operations teams build budgets, forecasts, targets and scenarios directly on the Power BI semantic models they already report from, and write the results back into Fabric. Microsoft Learn describes it as an enterprise and corporate performance management (EPM and CPM) solution built into Fabric, and it sits inside Fabric IQ as what Microsoft calls "the forward-looking layer".

At FabCon Europe 2026 (29 September 2026), Microsoft announced a set of additions: a faster planning engine in preview, simpler setup, write-back into the semantic model, event triggers and planning inside org apps. This post covers what Planning is, where its status actually stands, what was announced and how to adopt it without building a new spreadsheet problem. For the rest of the week, see our FabCon Europe 2026 recap.

What Planning in Fabric Is

The problem it targets is familiar: actuals live in Power BI, the budget lives in a separate planning tool or a web of spreadsheets, and someone reconciles the two every month. Microsoft's Planning post puts it plainly: planning "is no longer a separate system that data is copied into, and results copied back out of."

Microsoft Learn lists four components:

Planning sheets - budgeting, forecasting and scenario modelling in a spreadsheet-like grid
PowerTable sheets - structured, dimensional data management and data applications at scale
Intelligence sheets - reporting and automated variance analysis over planning data
Infobridge - integration that keeps planning data aligned with Fabric workloads and source systems

Because plans are built on a semantic model, they inherit its measures, hierarchies and security. Existing permissions continue to apply, so the model's access rules govern planning as well as reporting.

Who it is for: FP&A teams running budget and forecast cycles, finance business partners collecting input from budget holders, and operations planners working on volumes, capacity and cost. Microsoft's billing documentation maps these to three roles: Planners (FP&A analysts, modellers, administrators), Stakeholders (business users, reviewers, approvers) and Viewers (executives and report consumers).

Status: GA or Preview? Microsoft Says Both

This needs stating plainly, because Microsoft's own sources do not agree.

The Planning post (29 September 2026) says: "When Planning in Microsoft Fabric became generally available in July 2026".
Microsoft Learn's overview says Planning in Fabric IQ "is now available worldwide as part of the Microsoft Fabric SKU", with billing meters live.
Microsoft's OneLake roundup, published the same day, links to "Planning in Fabric (Preview)".

We are not going to pick one. Check the current position on Microsoft Learn, and with your Microsoft contact, before committing a budget cycle to it. What is not in doubt is that several of the new capabilities are explicitly in preview.

What Was Announced at FabCon Europe 2026

Status is as the Planning post gives it. Where the post gives no status label, we say so.

Native Planning Engine (preview). Built on Rust and Apache Arrow with OneLake integration, Microsoft says it delivers "up to 10x improvements in performance and scale", with teams working across "tens of millions of cells". The OneLake roundup adds that planning data and write-back can now be stored directly in OneLake.
Connect with your own identity. Planners can connect to a semantic model with their signed-in identity instead of configuring a shared cloud connection. No status label is given.
Write-back into the semantic model. A new write-back configuration experience adds budgets, forecasts and scenarios back into the same semantic model the plan is built on. No status label is given. Note that Learn's overview still describes write-back to a SQL database in Fabric.
Ontology integration. Plans can be incorporated into a Fabric IQ ontology, so targets, forecasts and assumptions become business entities that Copilot and agents can reason over. No status label is given; our guide to what Fabric IQ is covers the wider picture.
Event triggers. When write-back starts, succeeds or fails, a planning sheet can trigger Fabric pipelines, Dataflow Gen2, semantic model refreshes, notebooks, and Teams and Outlook notifications, with write-back details passed as parameters. No status label is given.
Planning in org apps. Planning and Intelligence sheets can be embedded in an organisational app alongside Power BI reports, governed by existing app audiences. No status label is given.
Multi-driver simulations. Multi-driver, multi-measure simulations trace volume, price and cost changes through to profit, with named scenarios such as Best Case. No status label is given.
Custom fiscal years, plus Stepped, Outline and Tree layouts and XLookup-style lookups in the grid. No status label is given.
PowerTable-only editors billed as Stakeholders. Described as recently announced: editors doing PowerTable-only data management are billed as Stakeholders and consumers as Viewers, not as Planners. The linked Microsoft post title labels it generally available.
Admin session controls (preview). Tenant-level settings let administrators control who can upgrade to Planner or Stakeholder sessions and warn users before an action is likely to oversubscribe capacity.

Microsoft also says an API surface for the planning lifecycle, so agents can work inside a plan, is the next step. No date was given.

Capacity and Billing

Microsoft Learn is specific here. Semantic models used in planning must sit on Fabric capacity (F SKUs) or Power BI Premium capacity; Power BI Pro and Premium Per User are not supported for the scenarios that rely on XMLA endpoints and embed tokens, and the XMLA endpoint must be Read Only or Read Write.

Billing is session-based rather than per-user licences. Each 30-day session consumes 847 CU-hours for a Planner, 168 for a Stakeholder and 37 for a Viewer; a session starts when a user opens, creates or edits a planning item and cannot be ended early. Successful PowerTable automation jobs consume 2 CU each, and Learn suggests an estimated 30% capacity buffer for the other Fabric workloads planning uses. It warns that smaller SKUs such as F2 and F4 are easy to overcommit - which is exactly what the new admin controls are for. Our capacity sizing guide covers the wider sizing decision.

Planning vs Excel and vs Fabric Apps

Against Excel budgeting. The spreadsheet cycle - export actuals, build the budget offline, email files to budget holders, consolidate the replies - is where versions multiply and definitions drift. Planning keeps an Excel-like grid but builds it on the governed model, so the budget and the actuals share one definition of revenue. Excel still has a place for one-off modelling, as our guide to moving finance from Excel to Power BI sets out.

Against Fabric Apps write-back. Microsoft also announced that apps in Power BI, built on Fabric Apps, will reach Power BI Pro and PPU in preview in the coming weeks. Microsoft's September feature summary says Fabric Apps write to Fabric SQL databases and warehouses, with semantic models read-only, and they suit lighter capture: a forecast adjustment, a correction, an approval. Planning is a purpose-built performance management tool with drivers, scenarios, allocations and role-based billing, and it needs capacity. If you need a few input screens next to a report, look at Fabric Apps for Power BI Pro; if you run a budget cycle, look at Planning.

How to Adopt It Without Creating a New Mess

Fix the model and definitions first. Planning inherits whatever the model says. If departments still report different numbers, a budget on top will not settle the argument - start with one source of truth for reporting.
Build the fiscal calendar properly. Custom fiscal years help, but the model's date dimension must match how finance closes.
Pilot one cycle. A single departmental forecast is enough to learn the tool and measure consumption.
Size and govern sessions. Count likely Planners, Stakeholders and Viewers, and use the admin controls to stop casual upgrades to Planner.
Own the written-back data. Decide who owns plan tables, how versions are retained and which triggers are allowed to fire.
Keep preview features out of the critical path. Test the Native Planning Engine, but do not run your year-end budget on it until it is generally available.

Where Solv Systems Comes In

Most of the effort in a planning rollout is not the planning tool. It is the semantic model, the definitions finance agrees to, and the capacity underneath. Our Power BI and analytics team prepares models for planning, runs the definitional work with finance, and pilots a first cycle so you know what it costs before rolling it out.

Sources and Further Reading

Frequently asked

Microsoft Learn describes it as an enterprise and corporate performance management solution built into Microsoft Fabric. Teams create budgets, forecasts and scenarios on existing Power BI semantic models, write planning results back, and compare plans with actuals in the same governed platform. It is part of Fabric IQ and combines planning sheets, PowerTable sheets, Intelligence sheets and Infobridge.

Microsoft's sources disagree. The Planning post of 29 September 2026 says Planning became generally available in July 2026, and Microsoft Learn says it is available worldwide as part of the Fabric SKU. Microsoft's OneLake roundup published the same day labels Planning in Fabric as Preview. Several of the FabCon Europe 2026 additions, including the Native Planning Engine and the new admin settings, are explicitly in preview.

Microsoft Learn says semantic models used in planning must be hosted on Fabric capacities (F SKUs) or Power BI Premium capacities, and that Power BI Pro and Premium Per User are not supported for the scenarios that rely on XMLA endpoints and embed tokens. The XMLA endpoint must be set to Read Only or Read Write.

By active 30-day sessions against your Fabric capacity, not per-user licences. Microsoft Learn gives 847 CU-hours per session for a Planner, 168 for a Stakeholder and 37 for a Viewer. Sessions start when a user opens, creates or edits a planning item and cannot be ended early. Successful PowerTable automation jobs consume 2 CU each.

It replaces the spreadsheet cycle of exporting actuals, building a budget offline and emailing files back for consolidation. It keeps an Excel-like grid, so planners do not lose the working style they know. Genuine one-off modelling can still sit in Excel, as long as it consumes governed numbers.

A governed semantic model with agreed definitions, a fiscal calendar, clear ownership of the written-back data, and a capacity sized for the number of Planners, Stakeholders and Viewers. Without agreed definitions, Planning puts a budget on top of numbers people still argue about.