“For us, the biggest benefit of Fabric Planning is speed: it lets us turn the semantic models and trusted business logic we have already invested in into planning applications, rather than rebuilding that foundation in a separate planning platform.”
“What used to take three to four weeks... can now be completed in about a week.”
“Fabric Planning lets us tailor forecasting to each area of the business... without forcing everyone into the same methodology.”
“Planning in Microsoft Fabric closes that gap”
| User group | # Users | Fabric Planning 1-year reserved price per 30-day session † | Pigment Net rate you pay · $/user/yr |
|---|---|---|---|
| Planners / Admins Build & maintain models |
Planner
$90.67/session
|
Editor
$ |
|
| Stakeholders / Contributors Enter values, approve, comment |
Stakeholder
$17.98/session
|
Contributor
$ |
|
| Read-only / Viewers Consume plans & reports |
Viewer
$3.91/session
|
Explorer
$ |
|
| Licenses or capacity, annual | 210 |
$60,032
F64 capacity, 1-year reserved, about 80% used
|
$225,000 |
† Fabric Planning runs on Fabric capacity. A session runs for 30 days from the first time a user engages with a plan, and each session type draws capacity at a fixed rate. A user who does not engage in a month starts no session and draws no capacity. The calculator prices the smallest Fabric capacity that holds a session for every user entered plus the allowance below, at the 1-year reserved East US price. The session prices are shown for reference. CU consumption by session type is set by Microsoft and is the same in every region, while the price per CU varies by region: see the capacity calculator.
Pigment rates are estimates. Enter the net rate you pay per seat, after discounts.
The Pigment figures are USD list prices and have not been converted to USD.
| Line item | Fabric Planning | Pigment |
|---|---|---|
| Platform / workspace fee optional Pigment's annual platform fee, charged on top of licenses. The default is community's estimate; replace it with your quote. | $ |
$ |
| Other resources / infra overhead Fabric: an allowance for Fabric SQL, OneLake and Power BI XMLA consumption, entered as a % of session load; the capacity is sized to hold it. The competitor: integration and hosting resources, entered as an annual amount. | % |
$ |
| Premium support optional Vendor premium / enterprise support tier, if quoted separately. | $ |
$ |
| Add-ons optional Pigment prices by the use cases in scope, such as workforce or sales planning, so each added use case can raise the contract. Enter any amount quoted. Fabric Planning includes PowerTable and Intelligence at no additional cost. | $ |
$ |
| Annual cost, Year 1 | $60,032 | $265,000 |
Fabric Planning runs on a Microsoft Fabric capacity (an F SKU). Reserved for a year, capacity costs about 41% less than pay-as-you-go, and part of a capacity can be reserved with the rest on pay-as-you-go. Fabric capacity is MACC-eligible where applicable, so it can draw down Azure spend your organization has already committed. The calculator prices the capacity the sessions and the allowance need, for a like-for-like comparison. Lumel's sizing guidance adds headroom for growth by giving planning its own capacity and keeping sessions under 75% of it. Whatever the sessions do not consume stays available to other Fabric workloads.
The Pigment figures are USD list prices and have not been converted to USD.
| One-time / annual increase | Fabric Planning | Pigment |
|---|---|---|
| Training One-time enablement for your team. | $ |
$ |
| Implementation time Weeks to go live, which drives time to value. | wk |
wk |
| Implementation cost One-time services / build cost. | $ |
$ |
| Annual price increase (CPI / renewal) Applied to Years 2 to 3 of the TCO. Enter the escalator in your contract. | % |
% |
| Component | Fabric Planning | Pigment |
|---|---|---|
| Annual cost (3 yrs, incl. uplift) | $180,096 | $860,296 |
| Training (one-time) | $12,000 | $40,000 |
| Implementation (one-time) | $40,000 | $100,000 |
| 3-year TCO | $232,096 | $1,000,296 |
Years 2 to 3 apply the renewal uplift: Year n = Year 1 × (1 + uplift)^(n−1). Fabric reserved defaults to 0% (flat annual commitment); Pigment defaults to 8%.
The Pigment figures are USD list prices and have not been converted to USD.
This page offers a directional comparison, not a quote. Figures are illustrative under the stated assumptions; actual costs depend on contract terms, region, session-type mix and utilization.
There is nothing to install and no new vendor contract. Fabric Planning is Microsoft's own planning capability in Microsoft Fabric, and a Fabric administrator turns it on in tenant settings. Plans run on Fabric capacity, and any extra capacity you need comes through your existing Azure subscription. Pigment is a separate platform with its own contract, sold directly or through Google Cloud Marketplace.
A first plan takes minutes once the semantic model is in place, and implementations typically go live in days. Plan owners make later changes themselves, so they do not wait for a modeling team.
They work in the plan itself, in Stakeholder sessions: they enter their numbers, run scenarios, approve and comment. Plan security roles decide which sheets and measures each person can see and change.
Yes. Fabric Planning covers sales planning (quotas by territory, with top-down targets and bottom-up input), S&OP and demand planning (statistical forecasts with inventory and supply drivers) and workforce planning (headcount at employee level), alongside FP&A. Teams use it for standard processes such as the annual budget and rolling forecasts, and for ad-hoc what-if questions between cycles, all on the same governed data. Statutory consolidation, with intercompany eliminations and currency translation adjustments, stays in your consolidation system.
No. In Fabric Planning, a Measure Model builds the plan directly from the measures and KPIs your semantic model already exposes. The DAX logic your data team maintains is reused as it stands. Logic that belongs to the plan itself, such as a balance carried from one period to the next, is written as Planning Formulas inside the plan, with no change to the semantic model. In Pigment, calculations your semantic model already defines are written again as formulas in Pigment's own language wherever the plan recalculates them.
Yes. With the Native Planning Engine, a single planning model handles about 12 million cells for one user, and Cube extends a plan to as many as 100 million. PowerTable plans at row level, up to 1 billion rows, with the ceiling set by the capacity behind the database. Most plans need no more than 1 million cells, well inside these limits. When many people plan at once, performance follows the size of your Fabric capacity and the design of the semantic model underneath. Capacity can be scaled up as usage grows. Our article on planning at scale covers the range of each method.
In Fabric Planning, the plan measures are published to the existing semantic model for Power BI reports to pick up, alongside the dimensions already maintained for reporting. Plan data becomes part of the reporting estate without recreating dimensions or standing up a second model. Within Fabric Planning itself, Intelligence sheets report on plan data as it is entered, including variances against actuals. Pigment data reaches Power BI through Pigment's export API: a query in Power BI Desktop reads each saved Pigment view with a key a Pigment admin creates. Views too large for the export API need a separate pipeline.
Fabric Planning does, for organizations whose data is in Microsoft Fabric. Budgets, forecasts and scenarios are written to the same platform where the detailed performance data resides, with the same definitions and security. Plan data is ready for AI where it is, and Fabric data agents work with the plan and the actuals together at full detail, including the comments and approvals that writeback records. Pigment's AI agents, and outside AI tools that connect through Pigment's MCP server, work with the data held in Pigment, plus attached files and connected apps. The ERP and warehouse data they can draw on is whatever has been imported and kept current there.
In Fabric Planning, Planning, PowerTable and Intelligence are all included in one session, with no separate add-ons to buy. Other Fabric resources, such as Fabric SQL, OneLake and semantic model activity, are not part of the session. They use your Fabric capacity like any other workload. Allow about 30% of session load for them, the default in the calculator on this page. Automation jobs also draw capacity per successful run. Pigment's pricing combines a platform fee, licenses by type and the use cases in scope, such as workforce or sales planning.
Fabric Planning licenses them by use. A session starts only when someone engages with a plan and runs for 30 days. A budget holder who contributes during the planning cycle, or an approver who signs off once a quarter, draws capacity only in the months they take part. Contributors and approvers use Stakeholder sessions, which draw about a fifth of the capacity of a Planner session. A reserved capacity is paid for all year, so in the months they do not plan it is free for other Fabric workloads. Capacity added on pay-as-you-go for the planning season can be scaled back afterwards. Pigment licenses each user for the license term, so a contributor who works one month a year costs the same as one who works every month. A Pigment user who creates scenarios needs an Editor license.
