Power BI consulting services: the F64 threshold that sets your 2026 licence bill

Summary. Power BI Pro lists at $14 per user per month and Premium Per User at $24, paid yearly, on Microsoft's pricing page as of 18 August 2026. Microsoft removed Power BI Premium per-capacity SKUs from the purchase flow for new customers on 1 July 2024, and existing customers without an Enterprise Agreement could renew only until 1 January 2025. What replaced that is a Fabric F SKU, and the choice of size decides your licensing model outright: on capacities below F64 every person viewing a report needs a Pro or PPU licence, while on F64 and larger a user with a free licence and the Viewer role can open the same report. That one rule is worth more than any discount you will negotiate. Run it against Microsoft's own published F64 reserved rate and the crossover sits near 358 viewers.

The other thing worth knowing before you sign anything: the P SKU retirement has no fixed end date. Microsoft's current migration guidance, updated on 22 July 2026, describes a clock that starts when your own agreement term expires, not a date in a press release.

The retirement is a clock, not a deadline

Most of the P SKU advice circulating in 2026 quotes calendar dates. Microsoft's current migration decision guide does not give one. It gives a sequence measured from the end of your own agreement.

Phase	Timing	What happens
Retirement	End of your current agreement term	The P SKU subscription ends and cannot be renewed
Grace period	Days 1 to 30 after it ends	Capacity keeps running at its current size at no charge
Throttled access	Days 31 to 90	Interactive operations are delayed, export and recovery still work
Full block	Day 91 onward	All operations rejected, data retained but inaccessible

Microsoft states the position directly on that page: "Microsoft no longer sells new P SKUs, and customers with expiring Enterprise Agreements or Microsoft Cloud Agreements can't add or renew P SKU capacity through their agreement." The earlier P SKU retirement notice, dated 14 March 2024, sets the two dates that have already passed: removal from the purchase flow for new customers on 1 July 2024, and renewal for existing non-EA customers until 1 January 2025. Customers with an existing EA can keep renewing annually until that agreement ends, and sovereign cloud customers are not affected because Fabric is not available to them.

Two clarifications matter because both are routinely got wrong in vendor pitches. The retirement covers per-capacity SKUs P1 to P5 only. Power BI Pro and Premium Per User are not being retired. And migration is not automatic: Microsoft's guidance is that you purchase the F SKU capacity in Azure yourself and reassign each workspace by hand.

The capacity mapping is fixed, with each P SKU v-core corresponding to 8 capacity units.

P SKU	Fabric equivalent	Free viewers?
P1	F64	Yes
P2	F128	Yes
P3	F256	Yes
P4	F512	Yes
P5	F1024	Yes

The F64 threshold, stated exactly

This is the rule that decides your bill, and it is worth quoting rather than paraphrasing. Microsoft's Fabric licences documentation puts it this way: "On F SKUs smaller than F64, each user viewing Power BI content must have Pro, PPU, or an individual trial. On F64 or larger, users with only a Free license and a viewer role can view Power BI content."

The migration FAQ adds the constraint people miss: "Authors and editors always need Pro or PPU license regardless of capacity size." So a 400-person organisation with 12 report authors on an F64 pays for 12 licences, not 412. On an F32 it pays for 412.

Two qualifiers travel with the rule. The free user must hold the Viewer role specifically, because any other workspace role requires Pro or PPU. And Microsoft notes that Fabric Trial capacity behaves like F64 for viewing, which is why proof-of-concept costs never predict production costs.

Where the crossover actually sits

Microsoft's Power BI pricing page lists Pro at $14.00 per user per month paid yearly and Premium Per User at $24.00, with a $14.00 add-on available to step Pro, Microsoft 365 E5 and Office 365 E5 users up to PPU. The page carries its own warning that "Prices shown are for marketing purposes only and may not be reflective of actual list price due to currency, country, and regional variant factors," which is exactly why an Indian buyer should confirm rupee pricing in their own tenant rather than trusting any published figure, this one included.

For capacity, the only Microsoft-published F SKU price list we could retrieve is the Power BI licensing deck of April 2025, and it states its region explicitly as US West 2: 1 capacity unit at $0.18 per hour pay-as-you-go, giving F2 at $262.80 per month and F64 at $8,409.60, against reserved rates of $156.334 and $5,002.667. Treat those as a shape, not a quote. Microsoft's documentation is clear that the same SKU size costs different amounts in different Azure regions, and the Azure Fabric pricing page renders every price cell as a placeholder to an automated fetch, so no India figure is publicly readable without opening the calculator in your own tenant.

With that caveat stated, the arithmetic is the useful part.

Viewers needing access	Annual cost on Pro at $14	F64 reserved, annual	Cheaper option
50	$8,400	$60,032	Pro licences
150	$25,200	$60,032	Pro licences
358	$60,144	$60,032	Break-even
600	$100,800	$60,032	F64 capacity
1,000	$168,000	$60,032	F64 capacity

At the April 2025 US West 2 reserved rate, F64 costs about the same as 358 Pro licences. Against the pay-as-you-go rate the crossover moves out to roughly 600 viewers. Below those numbers, capacity is a workload decision rather than a licensing saving, and buying F64 purely to avoid per-user licences loses money. Above them, the free-viewer rule is the single biggest line item in the analysis.

Note also that Microsoft's own pages disagree slightly on the reservation discount, at 40.5% in the licensing deck and about 41% on the Azure pricing page. Azure bills per second with a one-minute minimum, so short bursts do not round up the way they do on some other services.

The 2026 changes that alter a running bill

Three things moved recently, and none of them appear in most Power BI proposals.

Capacity overage is in preview. Microsoft documented it on 15 June 2026, updated 10 July 2026. It lets a capacity exceed its limit rather than throttle, and it charges "capacity overage charges at 3 times the pay-as-you-go rate" for the excess. An administrator sets a rolling 24-hour capacity-unit-hour limit that Fabric evaluates every five minutes, and the quota consumed is one twenty-fourth of that limit, so a 48 CU-hour limit adds 2 CUs. Microsoft recommends keeping the limit below one third of daily capacity-unit hours, which are 48 for an F2 and 1,536 for an F64. It is billed on a separate Azure meter and it was still labelled preview at the July 2026 update.

Autoscale did not survive the move. Microsoft's migration guidance states plainly that P SKU Autoscale "Doesn't exist on F SKUs," and points to on-demand resizing plus overage protection instead. Autoscale Billing for Spark is a separate opt-in, and reserved capacity discounts do not apply to it. If your P1 has been quietly autoscaling through month-end reporting peaks, that behaviour disappears on migration day and needs a plan.

Default semantic models changed. Since 5 September 2025 Power BI default semantic models are no longer created automatically when a warehouse, lakehouse or mirrored item is created, and by 30 November 2025 all existing default semantic models were disconnected from their item and became independent models. Any report or pipeline that assumed a default model exists needs checking.

One more correction worth making, because it appears in partner content regularly: Power BI Embedded A SKUs have not been retired. Microsoft's embedded capacity documentation, updated 12 May 2026, still lists A, EM, P and F SKUs as valid for publishing embedded content, with A SKUs billed hourly and pausable. What changed is that embedded is included with every F SKU, so separate EM or A capacity becomes unnecessary after migration rather than unavailable. The same page confirms the licence rule applies there too: below F64, or on an A SKU, every viewer of embedded content needs Pro or PPU.

India-specific considerations

Microsoft's Azure region list for Fabric includes Central India, India South Central, South India and West India, and the Azure pricing page offers rupee billing, but no India F SKU figure is retrievable from a public page. Any consultant quoting you a precise Central India F64 rate from memory is guessing. The correct step is to price it in the Azure pricing calculator with region and currency set, then hold the vendor to that number.

Two other local points shape scope. Data residency choices interact with capacity placement, because the capacity region determines where the workspace data sits, and that decision is difficult to reverse cleanly. And any semantic model containing customer or employee records falls within the scope of the Digital Personal Data Protection Act 2023, so row-level security design, workspace access and retention belong in the build rather than in a later hardening phase. We design Power BI deployments aligned with DPDP requirements; we do not describe any deployment as certified compliant.

What a Power BI engagement should cover

Most Power BI spend goes wrong in two places: a capacity bought without the viewer math, and semantic models nobody owns. A scope worth paying for covers five things.

Licence and capacity model. Viewer count, author count, and the F64 arithmetic above, priced in your region and currency, with the overage and autoscale changes accounted for.

Semantic model design. One governed model per subject area with defined ownership, rather than a model per report. This is what keeps refresh cost and capacity units under control as usage grows.

Data engineering underneath. Reports are the visible end of a pipeline. Our data engineering services cover the ingestion and transformation layer, and our comparison of warehouse-native transformation approaches sets out the trade-offs that decide refresh cost.

Governance and access. Workspace roles, row-level security, and the Viewer-role discipline that the free-licence rule depends on.

Capacity monitoring. Capacity unit consumption tracked against the daily budget, so throttling is predicted rather than discovered during a board pack refresh.

Our delivery process: audit the current estate and licence position; model the capacity and licence options with real numbers; build the semantic layer and pipelines; migrate workspaces with a rollback plan; then monitor capacity through the first two reporting cycles, which is when the real consumption pattern appears.

Why eCorpIT

eCorpIT is eCorp Information Technologies Private Limited, founded in 2021 and based in Gurugram. We are a senior-led, multi-disciplinary engineering organisation, CMMI Level 5 appraised, MSME certified and ISO 27001:2022 certified, and a Microsoft technology partner.

For Power BI that means we start from the licence arithmetic rather than from a dashboard mock-up. If your viewer count sits below the crossover, we will tell you to stay on per-user licences and spend the difference on the data layer, because a capacity bought for the wrong reason is a permanent line in the budget. Engagements run either as a fixed-scope implementation covering a defined set of models and reports, or as a dedicated senior team retained monthly. We quote against your actual viewer and author counts, your region, and your existing estate. Our broader custom software development work covers the applications that feed these models.

FAQ

How much do Power BI licences cost?

Microsoft's pricing page lists Power BI Pro at $14.00 per user per month paid yearly and Premium Per User at $24.00, with a $14.00 add-on for Pro, Microsoft 365 E5 and Office 365 E5 users to step up to PPU. Microsoft warns those figures may not reflect actual list price in every currency and country.

When do Power BI viewers stop needing a paid licence?

At Fabric F64 and above. Microsoft states that on F SKUs smaller than F64 each user viewing content needs Pro, PPU or a trial, while on F64 or larger a user with only a free licence and the Viewer role can view content. Authors and editors always need Pro or PPU regardless of capacity size.

When exactly do Power BI Premium P SKUs stop working?

There is no single published date. Microsoft's migration guidance runs from the end of your own agreement term: days 1 to 30 are a free grace period at current capacity, days 31 to 90 are throttled with export still possible, and from day 91 all operations are rejected while data is retained but inaccessible.

Which Fabric SKU replaces my P SKU?

The mapping is P1 to F64, P2 to F128, P3 to F256, P4 to F512 and P5 to F1024, with each P SKU v-core corresponding to 8 capacity units. Microsoft states migration is not automatic: you purchase the F SKU capacity in Azure yourself and reassign each workspace manually.

At what point is capacity cheaper than per-user licences?

Using Microsoft's April 2025 US West 2 reserved rate of $5,002.667 per month for F64, capacity costs roughly the same as 358 Pro licences at $14. Against the pay-as-you-go rate of $8,409.60 the crossover moves to about 600 viewers. Regional pricing differs, so confirm your own region.

What is Fabric capacity overage?

A preview feature that lets a capacity exceed its limit instead of throttling, charged at three times the pay-as-you-go rate for the excess. An administrator sets a rolling 24-hour capacity-unit-hour limit evaluated every five minutes, and the quota consumed is one twenty-fourth of that limit. It was still in preview at the July 2026 documentation update.

Does Autoscale still work after migrating to Fabric?

No. Microsoft states that P SKU Autoscale does not exist on F SKUs, and recommends on-demand resizing plus capacity overage protection instead. Autoscale Billing for Spark is a separate opt-in feature, and reserved capacity discounts do not apply to it, so month-end peaks need planning rather than automatic absorption.

Has Power BI Embedded been retired?

No. Microsoft documentation updated in May 2026 still lists A, EM, P and F SKUs as valid for publishing embedded content, with A SKUs billed hourly and pausable. Embedded is now included with every F SKU, which makes separate A or EM capacity unnecessary after migration rather than unavailable.

How eCorpIT can help

We model the Power BI licence and capacity decision with your real viewer and author counts before anyone designs a report, then build the semantic layer, pipelines and governance underneath it and monitor capacity consumption through the first reporting cycles. If per-user licences are cheaper than capacity for your headcount, we will say so. To have the F64 arithmetic run against your own estate and region, contact us.