Power BI Premium to Microsoft Fabric: What the Migration Really Costs

New customers could not purchase P SKUs after July 2024, and most renewals closed by February 2025 — though existing EA customers can continue renewing until the end of their current agreement. This guide covers what that transition actually involves: the SKU mapping, the costs Microsoft's documentation downplays, the technical gotchas that catch organisations off-guard, and how to think about the migration as more than a licence swap.

What "Power BI Premium to Fabric" actually means

Power BI Premium was always a capacity licence — you bought dedicated compute, your reports ran on it, your users consumed content without needing individual Pro licences. That concept still exists in Microsoft Fabric. The difference is that the compute now runs the entire Fabric platform: data engineering, data warehousing, real-time analytics, and Power BI, all sharing the same pool.

The old SKU names (P1, P2, P3) are replaced with F SKUs (F64, F128, F256). The compute equivalence is direct:

Power BI Premium	Microsoft Fabric	Capacity Units (CUs)	Power BI v-cores
P1	F64	64	8
P2	F128	128	16
P3	F256	256	32

If you are running P1 today, your migration destination is F64. Not F32 — and this distinction matters more than it looks.

The F32 trap

The most common mistake in migration planning: an organisation sees that F32 costs roughly half of F64 and assumes it is the budget-friendly P1 equivalent. It is not.

Free viewer access — the feature that lets report consumers read Power BI content without a Pro licence — only activates at F64 and above. On F32, every consumer still needs a Power BI Pro licence (approximately £11/user/month as of 2025 pricing).

For an organisation with 500 report consumers, that is around £5,500–7,000/month in licence costs that did not exist on P1. The "savings" from choosing F32 over F64 are wiped out by the user licence bill before the first month is done.

The P1 → F64 mapping exists for a reason. Trust it.

Hidden costs Microsoft's docs bury

Power BI Report Server

P SKUs included dual-use rights: the same licence covered both cloud Power BI Premium and on-premises Power BI Report Server. F SKUs do not include this as standard. Organisations running PBIRS on-premises need either a Fabric reserved capacity licence (F64+) or SQL Server Enterprise Edition with Software Assurance. If you have an on-premises reporting footprint, budget for this separately before committing to migration.

Pro licence price increases

Standalone Power BI Pro increased approximately 40% at EA renewal from April 2025. Microsoft 365 E5 subscribers are protected — Pro is included in E5. Microsoft 365 E3 subscribers are not protected: E3 does not include full Power BI Pro, so E3 users typically need separate Pro or Premium Per User (PPU) licensing unless content is hosted in P or F64+ capacity and they are viewers only. If you are on E3 with a large user base, the combined effect of PBIRS relicensing and Pro price increases can add meaningful cost to the migration total.

Azure region complexity

This is the one that catches migration projects at the worst possible moment. Fabric items — lakehouses, warehouses, Data Factory pipelines — may block workspace reassignment across regions or require deletion and recreation. Cross-region moves are not guaranteed for all Fabric item types, and the implications vary depending on what your workspaces contain.

Define your regional strategy before you touch a single workspace. Discovering a cross-region conflict mid-migration is expensive.

What you actually gain

The case for moving beyond a simple licence swap is real. Fabric is not just Premium with a new name — it adds capabilities that Power BI Premium never had:

• Direct Lake mode removes the traditional import/refresh cycle for Power BI datasets. Instead of copying data into a semantic model on a schedule, the model reads directly from Delta files in OneLake. This improves data freshness and reduces operational overhead — performance benefits depend on how well your Delta tables and semantic models are optimised.
• OneLake gives every Fabric experience — Power BI, Data Engineering, Data Warehouse, Real-Time Intelligence — a shared storage layer. Data loaded once is available everywhere without duplication. For organisations running separate Azure Data Lake, Synapse, and Power BI Premium today, this collapses three storage costs into one.
• Pause and resume lets dev and test environments run only during business hours. On a P1, the £5,000/month clock runs 24/7. An equivalent F64 reserved at discount can be paused nights and weekends, cutting effective cost significantly for non-production environments.
• MACC eligibility means Fabric capacity spend counts toward Microsoft Azure Consumption Commitments. If your organisation has a large Azure commitment, check whether this applies before paying list price.

The four migration steps

Regardless of organisation size, the migration follows the same sequence.

1. Assess — Inventory every P SKU capacity and workspace. Note which workspaces already contain Fabric items (these require more careful handling). Identify PBIRS users, standalone Pro and PPU headcount, and any cross-region workspace assignments. Measure current capacity consumption using the Fabric Capacity Metrics App.
2. Plan — Choose your F SKU tier (P1 maps to F64 minimum). Choose commitment type: pay-as-you-go for the first 60 days while you validate, then reserved for the 40% discount. Confirm your Azure region matches existing workspace regions. Identify workspaces that can be bulk-migrated vs. those needing individual attention.
3. Migrate — Purchase Fabric capacity in the Azure Portal. Pause all scheduled data refreshes before reassigning workspaces — active jobs cancel on reassignment, which causes data loss if you are mid-refresh. Reassign workspaces to the new capacity in bulk (admin portal for under 50 workspaces; Fabric REST APIs for larger estates). Restart refreshes and validate.
4. Clean up — Delete unused old P SKU capacities after validating the new setup. Leaving them active creates unnecessary cost, confusion, and the risk of workspaces being accidentally assigned to the wrong capacity. Configure capacity monitoring, set an 80% utilisation alert, and establish resizing and pause/resume procedures for your environment.

A note on timing

When your P SKU expires, Microsoft provides 30 days of free matching Fabric capacity. Power BI item access continues during a transition period, but continuity after day 90 is at risk — Microsoft's documentation on throttling behaviour and data retention during and after the grace period is not fully detailed in public docs. Confirm the specifics with your Microsoft account team before expiry rather than relying on a fixed timeline.

This is enough time to migrate if you have planned in advance. It is not enough time to plan and migrate simultaneously. Start the assessment at least two to three months before your EA renewal date.

"The migration itself takes weeks. The architecture thinking that makes the migration worthwhile takes a few days of structured work upfront."

Treating migration as an architecture decision

The organisations that get the most out of Fabric migration are not the ones that lift and shift their existing Premium setup unchanged. They use the transition moment to ask: what should our data architecture look like now that we have OneLake, Direct Lake, and native data engineering on the same platform?

That does not mean rebuilding everything. For most mid-market organisations it means consolidating data movement tools into Fabric Pipelines, redesigning one or two high-value datasets to use Direct Lake, and establishing a medallion architecture in OneLake as the canonical data layer going forward.

When to bring in outside help

Most Power BI Premium migrations are straightforward for organisations with under 20 workspaces and no Fabric items yet. Complexity increases significantly when:

• You have 50+ workspaces across multiple business units
• You are running Power BI Report Server on-premises
• Workspaces already contain Fabric items (pipelines, lakehouses)
• Your EA renewal is within 90 days
• You want to use migration as a moment to modernise, not just swap licences

---

Frogsbyte helps mid-market companies in the UK, DACH region, and Nordics build analytics platforms on Microsoft Fabric. If your organisation is approaching an EA renewal and weighing the move, the cheapest hour you can spend is the one that scopes the migration before the deadline forces it.